Once after a power outage, on Cisco Catalyst 6509-E, instead of the main module WS-SUP720-3BXL, only the backup module was launched.
As I found out later, the memory card stopped working and, accordingly, the module could not start the firmware. At this moment on the module all the indicators glowed red.
Having connected via telnet to Cisco Catalyst 6509-E, I executed the commands:
show module show inventory
And I saw that the module did not start in the fifth slot:
Mod Ports Card Type Model
5 0 Unknown (Other) Unknown
6 2 Supervisor Engine 720 (Active) WS-SUP720-3BXL
Mod Online Diag Status
5 Not Applicable
Then I took the laptop and connected the console cable directly to the non-working module, after which I was delighted, as the “rommon” was displayed, executed the command:
Information was displayed that the exchange of memory is 1024 MB, but the non-working memory card was one and 512 MB, after which I looked at what is in memory:
dev show file systems dir disk0: dir disk1: dir bootdisk:
As it turned out, the built-in memory “bootdisk” had a size of 512 MB and a copy of the firmware was on it, so I did not have to download the TFTP firmware and install a new memory card, so I just executed the launch command:
After that, the module was successfully launched and on Cisco in the information about the modules instead of “Unknown (Other)” it was displayed as “Supervisor Engine 720 (Other)”, and a little later “Supervisor Engine 720 (Hot)”.
If there is only one memory card, you can buy it on ebay.com, then connect it first to the working module, format and copy the firmware file there, then connect it to the non-working module and run it, or run the module directly from the TFTP firmware, make a diagnosis , specify the boot firmware:
boot system flash bootflash:s72033-adventerprisek9_wan-mz.122-33.SXJ7.bin
Check the configuration:
show version show bootvar show redundancy show run
Then connecting via telnet, I looked at what is on the memory cards:
dir disk0: dir disk1: dir bootflash: dir slavedisk0: dir slavedisk1: dir slavesup-bootflash:
Configuration files (startup-config) were in nvram and slavenvram.
If there is enough space for the firmware in the internal memory of the second module, then it is better to copy it there in case of a memory card failure:
show disk0: show bootflash: copy disk0: bootflash:
Later I found out that the adapter or the connector inside the WS-SUP720 turned out to be inoperative, through which the memory card was connected, when I pulled it out and plugged it into the front disk0 slot, then it worked.