05-05-2014 12:17 PM - edited 03-07-2019 07:20 PM
Hello
Happy Cinco De Mayo
A 6509E Primary SUP card crashed and the Secondary card was take over. Techs on site, with Cisco TAC involved determined both Sups were bad.
A new SUP was RMA's and installed. The device is up and running. However TAC stated the reason for the outage was due to "bug" in code 12.2(18) SXF-6. Their recommendation is to upgrade to 12.2(18) SXF-17b (released 3/2011).
It has been awhile, approx 4 years since I upgraded an IOS on the SUP. Can someone provide some expert guidance and refresh my memory on best way to step thru this. Some services have back up via DR, others do not.
I will be implementing this solution today, 5/5/2014 at 11:00 pm CST
Solved! Go to Solution.
05-05-2014 03:47 PM
1. Download the IOS from the Cisco website to your TFTP server.
2. [IMPORTANT]: Compare the IOS' MD5 hash value you've downloaded against the MD5 hash value found in the Cisco website. The values MUST MATCH.
3. Copy the IOS from your TFTP server to the supervisor card: copy tftp://<TFTP IP address>/filename.bin sup-bootflash:
4. [IMPORTANT]: Compare the IOS' MD5 hash value you've downloaded against the MD5 hash value against the file in the supervisor card. The values MUST MATCH. Command: verify /md5 sup-bootflash:filename.bin
5. Change the bootvariable string:
config t no boot system flash sup-bootflash:old_ios.BIN boot system flash sup-bootflash:new_ios.bin boot system flash sup-bootflash:old_ios.bin config-registry 0x2102 end wr
6. Reload.
Please don't forget to rate our posts.
05-05-2014 05:05 PM
05-05-2014 03:47 PM
1. Download the IOS from the Cisco website to your TFTP server.
2. [IMPORTANT]: Compare the IOS' MD5 hash value you've downloaded against the MD5 hash value found in the Cisco website. The values MUST MATCH.
3. Copy the IOS from your TFTP server to the supervisor card: copy tftp://<TFTP IP address>/filename.bin sup-bootflash:
4. [IMPORTANT]: Compare the IOS' MD5 hash value you've downloaded against the MD5 hash value against the file in the supervisor card. The values MUST MATCH. Command: verify /md5 sup-bootflash:filename.bin
5. Change the bootvariable string:
config t no boot system flash sup-bootflash:old_ios.BIN boot system flash sup-bootflash:new_ios.bin boot system flash sup-bootflash:old_ios.bin config-registry 0x2102 end wr
6. Reload.
Please don't forget to rate our posts.
05-05-2014 04:21 PM
Leo
How to verify the hash?
05-05-2014 04:49 PM
Leo
How much downtime is expected to complete the entire process?
My plan tonight is to:
Install a new Secondary SUP. I assume I will have to wait until they synch.
I should be able to install secondary sup without affecting Primary SUP, yes?
How long should that take and what commands should I use to verify sync?
Then I will upgrade the Primary or Secondary SUP first?
Once first upgrade is done, then I will upgrade 2nd SUP.
05-05-2014 05:08 PM
I should be able to install secondary sup without affecting Primary SUP, yes?
Make sure both supervisor cards have the same IOS versions and feature set. The last supervisor card inserted will go into ROMmon if the IOS is incorrect.
Then I will upgrade the Primary or Secondary SUP first?
05-05-2014 07:02 PM
Thanks for taking the time to rate our posts, Steve.
05-05-2014 07:10 PM
My pleasure. Thank you for the guidance
05-05-2014 05:05 PM
How to verify the hash?
I use a free product called HashTab.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: