Reset Search
 

 

Article

VDX stuck in "cold recovering" during NOS upgrade

« Go Back

Information

 
TitleVDX stuck in "cold recovering" during NOS upgrade
Symptoms
  • VDX stuck in "cold recovering" during NOS upgrade
  • New firmware not committed on Standby partition for both the Active and Standby partition
    sw0# show version
    Network Operating System Version: 6.0.2
    Copyright (c) 1995-2015 Brocade Communications Systems, Inc.
    Firmware name:      6.0.2g
    Build Time:         14:34:57 Jan  3, 2018
    Install Time:       16:58:00 May 27, 2018
    Kernel:             2.6.34.6
    
    BootProm:           1.0.1
    Control Processor:  e500mc with 4096 MB of memory
    
    Slot    Name    Primary/Secondary Versions                         Status
    ---------------------------------------------------------------------------
    SW/0    NOS     6.0.2g                                             ACTIVE*
                    5.0.1a
    SW/1    NOS     6.0.2g                                             STANDBY
                    5.0.1a
  • CLI commands are not executed. e.g "reload system"
    %INFO : This command is not available in standby state.
  • HA state is not in sync
    sw0# sh ha
    SW/0: Active, Cold Recovering, Dual Partitions, Redundant
    SW/1: Standby, Dual Partitions, Redundant
  • The error below is seen on the console
    2018/05/28-04:22:10, [HASM-1104], 17, SW/0 | Active, INFO, VDX6740T-1G, Heartbeat to SW/1 up.
    2018/05/28-04:22:13, [SULB-1105], 18, SW/0 | Active, WARNING, VDX6740T-1G, Firmware upgrade session (0: dual-MM upgrade continue) starts.
    2018/05/28-04:26:17, [HASM-1002], 19, SW/0 | Active | FFDC, CRITICAL, VDX6740T-1G, Error happens on service instance ethsw 1: command inst failed or timed out (Critical).
    2018/05/28-04:26:17, [RAS-1001], 20, SW/0 | Active, INFO, VDX6740T-1G, First failure data capture (FFDC) event occurred.
    2018/05/28-04:26:25, [EM-1068], 21, SW/0 | Active | FFDC, ERROR, VDX6740T-1G, High Availability Service Management subsystem failed to respond. A required component is not operating.
    cat: /var/log/fsslo.log: No such file or directory
    2018/05/28-04:26:34, [RAS-1001], 22, SW/0 | Active, INFO, VDX6740T-1G, First failure data capture (FFDC) event occurred.

 
Environment
  • VDX series
  • Network OS
Cause
Resolution
Reload the VDX via a power cycle. This might need to be done twice.
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255