09-26-2014 09:31 AM - edited 03-04-2019 11:50 PM
I copied the ios to bootdisk, but when I change the boot system and reload my standby peer de standby peer starts up in rommon mode. I need the correct parameters for the boot command for a 6880. On the cisco site I can only find how to upgrade a 6500 with vss,but I need the documentation how to upgrade a cisco 6880. Can someone please help me to find this . Thank you.
Solved! Go to Solution.
09-26-2014 06:18 PM
There are several methods. Both methods has downtime. One method is FSU/eFSU, which I will NOT go into, is an "automated" method of upgrade. The automation, if it works, include booting each chassis one at a time.
The second method works well for me. Before I begin, it is very, very important that you check the MD5 hash value of the IOS file you've downloaded against the MD5 hash value found in the Cisco website.
1. Copy the IOS to the sup-bootdisk:.
2. Copy the IOS to the slavesup-bootdisk:
3. Change the boot variable string to point to the IOS of your choice. Additionally, you can specify a second boot variable string to point to your OLD IOS. This is very handy/important if your chassis attempts to boot the new IOS you've copied and failed. It is important to remove the old boot variable string before changing.
4. Ensure your config-registry is 0x2102.
5. Save the config first and copy the startup-config to an external media: CF or TFTP
6. Reboot the chassis.
Hope this helps.
09-26-2014 06:18 PM
There are several methods. Both methods has downtime. One method is FSU/eFSU, which I will NOT go into, is an "automated" method of upgrade. The automation, if it works, include booting each chassis one at a time.
The second method works well for me. Before I begin, it is very, very important that you check the MD5 hash value of the IOS file you've downloaded against the MD5 hash value found in the Cisco website.
1. Copy the IOS to the sup-bootdisk:.
2. Copy the IOS to the slavesup-bootdisk:
3. Change the boot variable string to point to the IOS of your choice. Additionally, you can specify a second boot variable string to point to your OLD IOS. This is very handy/important if your chassis attempts to boot the new IOS you've copied and failed. It is important to remove the old boot variable string before changing.
4. Ensure your config-registry is 0x2102.
5. Save the config first and copy the startup-config to an external media: CF or TFTP
6. Reboot the chassis.
Hope this helps.
09-27-2014 11:31 PM
Hi Leo,
Thank you for your help, i will try this and lett you know if it worked.
Kind regards,
Glenn
09-28-2014 12:49 AM
Thanks for taking the time to rate our posts, Glenn. :)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide