Ethernet Switches & Routers

Reply
New Contributor
Posts: 2
Registered: ‎01-19-2011

turboiron 1g fiber uplink to HP switches

Greetings!  We currently have 2 Brocade turboiron switches in our environment.  One of them, in layer 2 running software 4.2.00 is up (and has been forever) successfully linking to several switches in our environment (Cisco, HP, 3COM) all at 1G using Foundry 1g gbics.  Some time ago we upgraded our second turboiron to layer 3 software 7.4.00.  Only 2 vlans exist on the L3 switch right now and it is routing for us.

 

The problem I have is if I move those gbics from the layer 2 switch to the layer 3 switch they won't get links.  Move them back to the layer 2 switch and it's fine.  Not real sure what I'm missing on the config.  Is there an issue with gbic compatibility on the 7.4 software that didn't exist on the 4.2?  Is there some specific issue that one of the software versions requires that the other doesn't?

 

Any guidance would be greatly appreciated.

 

Mark Winemiller

New Contributor
Posts: 2
Registered: ‎01-19-2011

Re: turboiron 1g fiber uplink to HP switches

as an example, here's output from the layer 2 switch (once upon a time named core1):

 

telnet@CORE1(config-if-e10000-6)#show int eth 6
10GigabitEthernet6 is up, line protocol is up
Hardware is 10GigabitEthernet, address is 748e.f820.c12e (bia 748e.f820.c12e)
Configured speed 10Gbit, actual 1Gbit, configured duplex fdx, actual fdx
Member of L2 VLAN ID 1, port is untagged, port state is FORWARDING
BPDU guard is Disabled, ROOT protect is Disabled
Link Error Dampening is Disabled
STP configured to ON, priority is level0
Flow Control is enabled
mirror disabled, monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
IPG XGMII 96 bits-time
IP MTU 1500 bytes
300 second input rate: 101088 bits/sec, 55 packets/sec, 0.00% utilization
300 second output rate: 126952 bits/sec, 79 packets/sec, 0.01% utilization
236288494 packets input, 78672273905 bytes, 0 no buffer
Received 2923577 broadcasts, 1737045 multicasts, 231627872 unicasts
0 input errors, 0 CRC, 0 frame, 0 ignored
0 runts, 0 giants
384266058 packets output, 327449684997 bytes, 0 underruns
Transmitted 20943192 broadcasts, 14254000 multicasts, 349068866 unicasts
0 output errors, 0 collisions

 

and here is the layer 3 switch (core2)

 

telnet@CORE2(config-if-e10000-6)#show int eth 6
10GigabitEthernet6 is down, line protocol is down
Hardware is 10GigabitEthernet, address is 748e.f820.c9e2 (bia 748e.f820.c9e7)
Configured speed 10Gbit, actual unknown, configured duplex fdx, actual unknown
Member of L2 VLAN ID 2, port is untagged, port state is BLOCKING
BPDU guard is Disabled, ROOT protect is Disabled
Link Error Dampening is Disabled
STP configured to ON, priority is level0
Flow Control is enabled
Mirror disabled, Monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
IPG XGMII 96 bits-time
MTU 1500 bytes, encapsulation ethernet
300 second input rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
300 second output rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 multicasts, 0 unicasts
0 input errors, 0 CRC, 0 frame, 0 ignored
0 runts, 0 giants
0 packets output, 0 bytes, 0 underruns
Transmitted 0 broadcasts, 0 multicasts, 0 unicasts
0 output errors, 0 collisions
Relay Agent Information option: Disabled

 

This was done moving the gbic from layer 2 switch eth 6 to layer 3 switch eth 6

Broadcom
Posts: 44
Registered: ‎01-05-2012

Re: turboiron 1g fiber uplink to HP switches

you may want to move off FI 7.4.00 for TurboIron;  the latest for 7.4.00x is 7.4.00f

In earlier 7.4.00x version there were defects related to 1 G  copper SFP, such as ...

 

391531 TI-When a copper SFP is moved from port 1 to 2 and back to 1, the link does not come up and requires a reload.

 

fixed in FI 7.4.00d, and published in ReleaseNote

 

Defect ID:

DEFECT000391531

Technical Severity:

Medium

Summary:

In TurboIron, when a copper SFP is moved from port 1 to 2 and then back to 1, the link does not come up without reloading the device.

Symptom:

In TurboIron, when a copper SFP is moved from port 1 to 2 and then back to 1, the link does not come up without reloading the device.

Workaround:

You can bounce the port to fix the problem – unlike in 7.3.00c where you had to reload the device to recover.

Probability:

High

Risk of Fix:

Low

Feature:

Optics

Function:

OPTICS

Reported In Release:

FI 07.3.00

Service Request ID:

711623

 

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook