Ethernet Switches & Routers

Posts: 1
Registered: ‎03-07-2012

Identifying I2C Errors

Hi all - I've got a Brocade MLX NetIron 16-slot switch in my environment that had an I2C error a long time ago but due to changes in staff and bad documentation - I have no history on where this I2C issue is coming from so I've been trying to look for some information.

What I do know is that it had something to do with a line card in Slot 4:

S4: NI-MLX-10Gx4 4-port 10GbE Module  CARD_STATE_UP

What I noticed is that although the card state is "up" on "show module", all the interface configurations are missing and the port is down/down:

show int eth 4/1

10GigabitEthernet4/1 is down, line protocol is down

*note that it's down/down not disabled/down

TAC gave me a command to execute from privileged mode and this is the result:

dm i2c show-flags

Global I2C bad access data:

         status: Clear

         severity: Major

         mux tap: 0x0000000f

         dev ID: 0x00000000

         dev address: 0x00000000

Global I2C last good access data:

         mux tap: 0x00000004

         dev ID: 0x00000004

         dev address: 0x00000001

That last bit doesn't look too good to me - coupled with the fact that all ports on line-card 4 appear down I think there's a problem somewhere. Any ideas?

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