02-14-2019 10:00 PM - edited 03-08-2019 05:21 PM
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!
02-14-2019 10:13 PM - edited 02-14-2019 10:14 PM
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:
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.
02-14-2019 10:18 PM
02-14-2019 10:45 PM - edited 02-14-2019 10:46 PM
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 :
02-14-2019 10:53 PM
02-14-2019 11:01 PM
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.
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]
02-14-2019 11:20 PM
02-14-2019 11:28 PM
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
02-15-2019 01:06 AM
02-15-2019 01:13 AM - edited 02-15-2019 06:21 AM
02-15-2019 01:57 AM
02-15-2019 02:11 AM
02-15-2019 05:36 AM
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
02-15-2019 05:48 AM
02-15-2019 06:15 AM
Can you post that log, that only tell why it was rebooting.
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