Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Catalyst 6500/6000 standby supervisor engine module is not online, or status indicates Unknown
If the standby supervisor engine module is not coming online (indicated by the status of other or faulty in the output of the show module command, or indicated by amber status LED), it may be due to one of the common reasons indicated in this document.
To resolve this problem, perform these steps:
Console into the standby supervisor engine to determine whether it is in ROM Monitor (ROMmon) or in continuous reboot.
As an example, this output shows the supervisor engine in slot2 in ROMmon mode.
Make sure that both supervisor engines are running the same Cisco IOS Software level.
Check whether the active and standby supervisor engines are running the same Cisco IOS Software release. If not, it is possible that the standby supervisor may not come online. For example, if the active supervisor engine is running RPR+ mode (available since Cisco IOS Software Release 12.1EX) and the standby supervisor engine is running a version prior to RPR/RPR+ mode (such as Cisco IOS Software Release 12.1[8b]E9), the second supervisor engine fails to come online, as the redundancy mode is EHSA (by default). The standby supervisor engine would fail to negotiate with the active supervisor engine.
Make sure the supervisor engine module is properly seated in the backplane connector.
Make sure that the supervisor engine's installation screw is completely tightened.
For more information, refer to the Catalyst 6500 series switch module installation note.
Determine whether the standby supervisor engine is faulty.
To do so, issue the redundancy reload peer command from the active supervisor engine. Through the console to the standby supervisor engine, observe the boot up sequence to identify any hardware failures.
If the standby supervisor engine still does not come online, run this Generic Online Diagnostics (GOLD) test.
Issue the diagnostic start module test complete command to retest the module in the runtime environment and to observe if the module still shows failure status. If so, capture the log from the above troubleshooting steps and create a service request with Cisco Technical Support.