Can you share the part no. of B3 & B5 switch e.g. B3G124-24 or B5G124-24 etc.

Regards,
Shashank 

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Kaiser, Markus
Sent: Wednesday, January 12, 2011 4:59 PM
To: Enterasys Customer Mailing List
Cc: Enterasys Customer Mailing List
Subject: Re: [enterasys] B3&B5 issue

Hi,

the SFP ports of most B3/B5 and other SecureStack devices are "shared" ports 
and no additional ports (safest way is to look at the front panel port 
descriptions).

You can use either the RJ45/copper port OR the SFP port. So if you use i.e. 
ports 21-24 of a 24 port switch with SFP, you can't use the same ports 21-24 in 
copper. But you can use port 21-22 with SFP and port 23-24 as copper port.
If you, by mistake, connect all ports (port 21-24 SFP and port 21-24 with 
copper), then the copper ports will be prioritized and active, while the SFP 
ports stay down - as far as I remember.

A 24 port switch has a maximum of 24 active ports, not 24+4, except with 10G 
switches (SFP+), there the 2 or 4 uplink ports are additional ports.

Hope this helps. If there's a detail missing, please ask.

Cheers,

Markus


Sent via iPhone.

On 12.01.2011, at 11:50, Wenceslao Poveda Sánchez 
<[email protected]<mailto:[email protected]>> wrote:

Hi,

First of all thank you for your attention.

In B3 and B5 switches  we've adquired recently I have notice that SFP port 
aren't independent from GE ports.

Can anyone tell how to work with SFP ports like additional ports and avoid 
overlapping with GE ones, like other enterasys series.

Thanks.

  *   --To unsubscribe from enterasys, send email to <mailto:[email protected]> 
[email protected]<mailto:[email protected]> with the body: unsubscribe enterasys 
[email protected]<mailto:[email protected]>


---
To unsubscribe from enterasys, send email to [email protected] with the body: 
unsubscribe enterasys [email protected]

---
To unsubscribe from enterasys, send email to [email protected] with the body: 
unsubscribe enterasys [email protected]

Reply via email to