12-01-2017 09:52 AM - edited 03-08-2019 12:57 PM
Hi,
We have Cisco 4510R+E switch with dual SUP8E, we have configured SSO and it was running IOS XE 03.03.00.XO from very longtime and ROMMON-15.1(1r)SG1, last week we have tried upgrading it to IOS XE-3.6.7E, as per the release notes if we want to upgrade from 03.03. to 3.X we have need to upgrade rommon to 5.1(1r)SG4 which we have upgraded and tried upgrading the IOS 3.6.7E, we have copied the ios bootflash and slavebootflash and set the boot system and after we have rebooted the secondary SUP engine, it went to rommon mode, we have tried booting it from there and after that at last we used see this below message and it will stop there, we have tried with different version on 3.6.X but still were unable to upgrade the supervisor engines.
Platform Manager: starting in standalone mode (standby)
Please let me now if any one has faced same problem during upgrade.
Thanks
Basavaraj
Solved! Go to Solution.
12-02-2017 01:30 AM - edited 12-02-2017 01:31 AM
Console into the primary and secondary card before reloading.
Make sure you enable console logging. We would like to see what goes on when you do a reboot. It makes troubleshooting a lot easier.
Another thing, if one of the two is booting the old IOS check the config registry value is correct. It should be 0x2102. Brand new supervisor cards are normally shipped with a config-registry value of 0x2101.
12-01-2017 11:44 AM
Basavaraj,
Could you check if the rommon upgrade was actually applied on both supervisors? You should be able to verify that with either the 'show version' or 'show module' commands. If the system currently isn't bootable to IOS, the version should be displayed automatically once you go into rommon, or you can use the 'showmon' command.
12-01-2017 11:55 AM
Have a look at this post:
HTH
12-01-2017 11:12 PM
12-01-2017 02:11 PM
@Basavaraj Ningappa wrote:
we have copied the ios bootflash and slavebootflash and set the boot system and after we have rebooted the secondary SUP engine, it went to rommon mode
This is the reason why the secondary card went into ROMmon: Because when the secondary was rebooted, it was loading a DIFFERENT IOS version compared to the primary supervisor card.
The only way is to reboot both line cards.
And post the complete output to the command "sh version" because we want to see if the ROMmon was correctly upgraded or not.
12-01-2017 11:10 PM
Hi Leo,
We have upgraded only secondary SUP initially, after that i was trying to boot using new IOS from rommon mode, then we have upgraded primary SUP rommon also, even then also it use to go to rommon mode and from there we tried to boot manually but still it was not working, below is the log messages from the console
================================================================================
rommon 0 >dir
usage: dir { [ bootflash: ] | [ slot0: ] | [ usb0: ] }
rommon 1 >dir bootflash:
Date Time Attribute Size Name
========== ===== ========== ========== ================
2013/12/06 04:30 -rwxrwxrwx 181583336 cat4500es8-universal.SPA.03.03.00.XO.151-1.XO.bin
2017/11/26 01:23 -rw-rw-rw- 200253532 cat4500es8-universalk9.SPA.03.06.07.E.152-2.E7.bin
2017/11/26 02:40 -rw-rw-rw- 621504 cat4500-e-ios-promupgrade-151-1r-SG4
Total space = 1660959 KB
Available = 1291332 KB
rommon 2 >boot bootflash:cat4500-e-ios-promupgrade-151-1r-SG4
Loading image !
Checking digital signature....
[bootflash:/cat4500-e-ios-promupgrade-151-1r-SG4]
Digitally Signed Release Software with key version A
************************************************************
* *
* Unified FPGA Upgrade Utility *
* Copyright (c) 2012-2014 by Cisco Systems, Inc. *
* All rights reserved. *
* *
************************************************************
Version 15.1(1r)SG4
Compiled Thu 05-Jun-14 11:18 [RLS]
WS-X45-SUP8-E system detected
Unpacking FPGA:>
Image Name : Cat4K_WSX45SUP8E_FPGA_SIG
Image size : 692 bytes
Uncompressing image...
Image Name : Cat4K_WSX45SUP8E_FPGA_BIN
Image size : 1484960 bytes
Uncompressing image...
Validating FPGA:>
Cat4K_WSX45SUP8E_FPGA_BIN: Digitally signed image Release with key version A
FPGA[R] MD5 : d6106d9343b9595a0465449bf6c77f9b
Programming FPGA:>
-----------------------
***********************
Verifying FPGA:>
.......................
FPGA[W] MD5 : d6106d9343b9595a0465449bf6c77f9b
Unpacking ROMMON:>
Image Name : Cat4K_WSX45SUP8E_PROM_SIG
Image size : 692 bytes
Uncompressing image...
Image Name : Cat4K_WSX45SUP8E_PROM_BIN
Image size : 524288 bytes
Uncompressing image...
Validating ROMMON:>
Cat4K_WSX45SUP8E_PROM_BIN: Digitally signed image Release with key version A
ROMMON[R] MD5 : b92b79fc3566c3700d3b2b87c5d0898f
Programming ROMMON:>
---------
*********
Verifying ROMMON:>
.........
ROMMON[W] MD5 : b92b79fc3566c3700d3b2b87c5d0898f
[S] Resetting System !!!!
Verifying FPGA (P) Signature ....................... PASSED
Verifying ROMMON (P) Signature ......... PASSED
************************************************************
* *
* Rom Monitor *
* Copyright (c) 2012-2014 by Cisco Systems, Inc. *
* All rights reserved. *
* *
************************************************************
Rom Monitor (P) Version 15.1(1r)SG4
Compiled Thu 05-Jun-14 11:15 [RLS]
System : WS-X45-SUP8-E Slot [5] Peer [6] Active
Chassis : WS-C4510R*E Mod [1][2][3][4][7]
Revision : CPU 2.0 BOARD 4.0 FPGA 3.1C4A.9621
Memory : 4096 MB
Date : Sun Nov 26 07:04:23 2017
***** The system will autoboot in 5 seconds *****
Type Control-C to prevent autobooting....
. . . . .
config-register = 0x2102
Autobooting using BOOT variable specified file.....
Current BOOT file is --- bootflash:cat4500es8-universalk9.SPA.03.06.07.E.152-2.E7.bin
Loading image !!!!!!!!!!!!!!!!!!!!!!
Checking digital signature....
[mem:/cat4500es8-firmware]
Digitally Signed Release Software with key version A
Rommon reg: 0x00084F80
Reset2Reg: 0x0C200000
########
Conan controller 0x36A95518..0x36D2C331 Size: 0x00CAC5EC @
####
Radtrooper controller 0x368F997C..0x36A95516 Size: 0x00661EDC @
Link: 0x00000080-0x16000000
Program Done!
Checking digital signature....
[mem:/cat4500es8-base]
Digitally Signed Release Software with key version A
###########
pci 0000:00:00.0: ignoring class b20 (doesn't match header type 01)
pci 0001:02:00.0: ignoring class b20 (doesn't match header type 01)
pci 0002:04:00.0: ignoring class b20 (doesn't match header type 01)
audit: cannot initialize inotify handle
mmc0: Got command interrupt 0x00030000 even though no command operation was in progress.
PME2: fsl_pme2_db_init: not on ctrl-plane
All packages are Digitally Signed
Starting System Services
Nov 26 07:05:26 %IOSXE-3-PLATFORM: process kernel: mmc0: Got command interrupt 0x00030000 even though no command operation was in progress.
Nov 26 07:05:26 %IOSXE-3-PLATFORM: process kernel: PME2: fsl_pme2_db_init: not on ctrl-plane
diagsk10-post version 6.1.0.0
prod: WS-X45-SUP8-E part: 73-14915-04 serial: CAT1746L45Q
Power-on-self-test for Module 5: WS-X45-SUP8-E
CPU Subsystem Tests ...
seeprom: Pass
Traffic: L3 Loopback ...
Test Results: Pass
Traffic: L2 Loopback ...
Test Results: Pass
post done(63 secs)
Exiting to ios...
Loading gsbu64atomic as gdb64atomic
Using 5 for MTS slot
Platform Manager: starting in standalone mode (standby)
==============================================================================
after upgrading the both sup's we even tried the reload the whole switch using reload command, but it didnt reload the whole switch, it only reloaded the primary SUP and secoadnry become active with the old IOS. at the moment new IOS is copied to both flashes and rommon upgraded to SG4. do you think if i do hard reboot both SUP will upgraded same time ?
Thanks
Basavaraj
12-02-2017 12:30 AM
12-02-2017 01:05 AM
12-02-2017 01:30 AM - edited 12-02-2017 01:31 AM
Console into the primary and secondary card before reloading.
Make sure you enable console logging. We would like to see what goes on when you do a reboot. It makes troubleshooting a lot easier.
Another thing, if one of the two is booting the old IOS check the config registry value is correct. It should be 0x2102. Brand new supervisor cards are normally shipped with a config-registry value of 0x2101.
12-24-2017 10:03 PM
Hi All,
Reloading the whole switch fixed the problem and i was able to upgrade the core switch with new IOS 3.6.7E.
Thanks for your valuable feedback
Regards
Basavaraj
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