cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2645
Views
5
Helpful
15
Replies

Cisco 6880-X ISSU Boot Loop

jpl861
Level 4
Level 4

Hi,

 

I am trying to upgrade 6880-X using ISSU and it just goes back to old IOS.

 

Currently running 15.2(1)SY4 and upgrading to 15.2(1)SY7

 

I tried to issue this command and it upgraded the secondary chassis.

 

issu loadversion 1/5 bootdisk:c6880x-adventerprisek9-mz.SPA.152-1.SY7.bin 2/5 slavebootdisk:c6880x-adventerprisek9-mz.SPA.152-1.SY7.bin

 

I can see that the secondary chassis upgraded to SY7 then after a FPGA upgrade, it boots the chassis back to SY4. I get this message every time.

 

*Feb 14 22:03:59.355: %ISSU_PROCESS-SW2-3-IMAGE: Active is loading the wrong image [ bootdisk:c6880x-adventerprisek9-mz.SPA.152-1.SY7.bin ], expected image [ bootdisk:/c6880x-adventerprisek9-mz.SPA.152-1.SY4.bin ]
*Feb 14 22:03:59.359: %RF-SW2-5-RF_RELOAD: Shelf reload. Reason: Active is loading the wrong image
!
*Feb 14 22:04:00.891: %LINEPROTO-SW2-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up
*Feb 14 22:04:01.391: %SYS-SW2-5-RELOAD: Reload requested by Delayed Reload. Reload Reason: Active is loading the wrong image.
Cisco Governator Rommon version 1.1

 

It will then go to recovery-mode then it will then reboot again after 10-15 minutes then boot back to SY4.

 

The VSS chassis are back to operational state without getting upgraded.

 

Any idea guys?

Thanks!

15 Replies 15

balaji.bandi
Hall of Fame
Hall of Fame

We have seen this issue while we doing ISSU upgrade, i prefer doing old plain method as below.

 

Some of us prefer to use a different method: 

  1. Copy the IOS to the primary bootflash:
  2. Copy the IOS to the secondary bootflash: 
  3. Remove the boot variable string pointing to the old IOS
  4. Add the new boot variable string pointing to the new IOS
  5. Insert the boot variable string pointing to the old IOS
  6. Make sure the config-registry is 0x2102
  7. Save the config
  8. Reboot

 

Notes : make sure you have backup all the config.

            Make sure you read the release notes before upgrading

            Perform upgrade in maintenance window, this required some reboots.

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

I am trying to upgrade using ISSU to learn how to do it again in the future. I want to do the traditional way but just checking if I can do this using ISSU for future purposes.

Thanks!

Steps for ISSU: (any issue, connect console and post all the logs to understand the issue).

Steps :


1. Upload IOS to both Chassis

copy tftp://1.1.1.9/yourversion-new.bin bootdisk:

and same for slavebootdisk:

copy tftp://1.1.1.9/yourversion-new.bin slavebootdisk:

2. Check if you have this new image on both chassis (dir bootdisk, dir slavebootdisk)

#dir bootdisk:

3, Check MD5
verify /md5 disk:yourversion-new.bin

4. Use these commands in order to verify that the VSS is ready to run the upgrade procedure:

show issu state detail
show redundancy
show module switch all
show issu state detail

6. Start ISSU Upgrade

#issu loadversion 1/2 bootdisk:yourversion-new.bin 2/2 slavebootdisk:yourversion-new.bin

7. Switchover to upgraded chassis.
#issu runversion

8.ISSU Upgrade Accept new IOS on upgraded chassis.
#issu acceptversion

9. ISSU Upgrade of Standby Chassis
#issu commitversion

Last Verify:

To verify that you succeeded with the upgrade check the output of:

show issu state detail
show redundancy
show module switch all

 

 

Good refrence also :

 

https://www.cisco.com/c/en/us/support/docs/switches/catalyst-6500-series-switches/117564-technote-issu-00.html

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

That's what I did. After the secondary chassis upgrades to new version, it will revert back to old.

Thanks for the confirmation you followed the steps. when you get chance, while upgrading using ISSU, please connect the console and post all the logs to understand what went to wrong.

 

May be this information help you, may be your case please check.

 

3.1. Possible Issue

C-6880X#issu loadversion 1/5 bootdisk:c6880x-adventerprisek9-mz.$
 % CV [ bootdisk:/c6880x-adventerprisek9-mz.SPA.151-2.SY4a.bin ] must be named first in BOOT [ bootdisk: ]

You can check the config of boot system image like this:

C-6880X#sh runn | i boot
boot-start-marker
 boot system bootdisk:
boot-end-marker

If you have similar boot system bootdisk: without the image name c6880x-adventerprisek9-mz.SPA.151-2.SY4a.bin or similar in it you should delete that row and enter it with old IOS image mentioned in it:

C-6880X#conf t
Enter configuration commands, one per line. End with CNTL/Z.
C-6880(config)#no boot system bootdisk:
C-6880(config)#no boot system bootdisk:/c6880x-adventerprisek9-mz.SPA.151-2.SY4a.bin
C-6880(config)#do wr
Building configuration...
[OK]

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

If I delete the entry of the current IOS in boot system command it won't let me proceed with ISSU. I tried to follow Cisco's guide as well.

I am upgrading the switches via console and that's all the error I am getting before reloading and booting the old image again. It says that there is an IOS mismatch so it is loading the old firmware.

I have not come across this issue, since we done some ISSU upgrades. to understand better

 

can you post below output :

 

show version

show modules

show switch virtula

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Leo Laohoo
Hall of Fame
Hall of Fame
If you are into a boot loop then ISSU isn't suitable for this situation and go with the "old fashion" way:
1. Copy the IOS to the Active Supervisor;
2. Copy the IOS to the Secondary Supervisor;
3. Change the boot variable string to point to the new IOS;
4. Add a boot variable string to point to the OLD IOS (just in case);
5. Make sure the config-registry value is 0x2102;
6. Save the config; and
7. Reboot

jpl861
Level 4
Level 4

For those who want to see the logs here it is. I am upgrading traditional way.

Post the complete output to the command "sh version".

It’s now running SY7. I upgraded traditional way.

This proves, OLD is GOLD.

 

But still we expect ISSU to be streamlined, May be Dev team required more testings.

 

personally 10 out 6 failed my experience, i can only try if this is green Field, if live environment, Traditional way good and fast fix.

 

If this is resolved, mark as resolved, so it will be helpful for other community members

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Thanks. I just don't get it why the secondary chassis would reboot twice because of DAD. It prolongs the downtime of secondary VSS switch.

Can you post that log, that only tell why it was rebooting.

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Getting Started

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: