Question

Show Chassis Post Firmware Update

  • 15 September 2020
  • 4 replies
  • 60 views
R

Hi All,

Did a FW update from 7.2.0c to 7.2.0e on VDX6740 Platform on the weekend and post FW update RB1 when you run the show chassis only outputs the below. Running show chassis on the remaining members of the LC outputs normal. Please advise what the problem could be and the possible resolution.

Thanks. 

 

SWITCH_NAME# show chassis
Rbridge-id: 1

Chassis Name:
Unable to retrieve chassis information
Airflow direction : Port side INTAKE
 

 

Show System takes a looooong time to run and outputs the below.

SWITCH_NAME# show system
Stack MAC                     : to get WWN infor

  -- UNIT 0 --
Unit Name                     : SWITCH_NAME
Switch Status                 : Online
Hardware Rev                  : 131.7
TengigabitEthernet Port(s)    : 52
FortyGigabitEthernet Port(s)  : 3
Up Time                       : up 2 days 1:44
Current Time                  : 11:35:18 AEST
NOS Version                   : 7.2.0e
Jumbo Capable                 : yes
Burned In MAC                 : SW/0 , SW/1 
Management IP                 : 
Management Port Status        : UP

  -- Power Supplies --

  -- Fan Status --
Unable to display fan information (-5)

SWITCH_NAME#
 

SWITCH_NAME# show system monitor rb 1
** System Monitor Switch Health Report **
RBridge 1       switch status            : HEALTHY
                Time of Report           : 2020-09-15 11:50:59
                Power supplies monitor   : HEALTHY
                Temperatures monitor     : HEALTHY
                Fans monitor             : HEALTHY
                Flash monitor            : HEALTHY
SWITCH_NAME#

 

4 replies

T
Rank
Userlevel 3

Hi Russ,

 

From the output, it appears there’s an issue with the i2c bus communication. The CLI is trying gather the system information thru the i2c bus which could be timing out which results in the long wait for the outputs. 

 

Did you upgrade multiple switches? If so, are both having the same issue? 

Have you tried doing a ‘reload system’ on the RB1 to have the i2c bus clear and re-initialize? 

 

 

R

Hi Russ,

 

From the output, it appears there’s an issue with the i2c bus communication. The CLI is trying gather the system information thru the i2c bus which could be timing out which results in the long wait for the outputs. 

 

Did you upgrade multiple switches? If so, are both having the same issue? 

Have you tried doing a ‘reload system’ on the RB1 to have the i2c bus clear and re-initialize? 

 

 

Thanks Truyen, yeah multiple switches in the stack, 4 in total and the entire stack was upgraded. RB 1 appears t be the only switch exhibiting this behaviour. Is a switch reload the only method to re-initialise? 

T
Rank
Userlevel 3

Yes, ‘reload system’ will clear the bus if it’s a stuck bus. 

There’s a possibility that a device (typically SFP) that could be causing the bus to be busy too. 

Please run ‘show logging raslog’ to see if there’s any repeating log messages relating to SFPs since the upgrade. 

Beyond that, we would need you to collect the supportsave logs and open a case with GTAC to take a deeper look at the logs. 

R

Thanks Truyen.

No Entries in the raslog for ‘SPF’. I guess I’ll have to arrange an outage for a reload of the switch. 

Reply