03-28-2011 09:06 AM - edited 03-06-2019 04:18 PM
Gents,
we were unable to save the running-configuration of our Nexus7000 due to the error:
"Configuration update aborted: another request for config change is already in progress"
I was assuming that we were hitting a known bug with the NXOS 5.1.1(a) (CSCtj44206) I tried to reload the standby supervisor (N7K-SUP1).
Unfortunately the standby doesn't come online again. I get stuck at INIT 3 and I now have a bash prompt and no idea how to get out of it.
Latest syslog message is:
2011 Mar 28 14:24:41 de5ifbsw004 %$ VDC-1 %$ %SYSLOG-2-SYSTEM_MSG: Did not receive supstate notification in 180 seconds. Still waiting
---
Monitor-Output (from CMP) while booting:
NX7 SUP Ver 3.22.0
Serial Port Parameters from CMOS
PMCON_1: 0x200
PMCON_2: 0x0
PMCON_3: 0x3a
PM1_STS: 0x101
Performing Memory Detection and Testing
Total mem found : 4096 MB
Performing memory test... Passed.
NumCpus = 2.
Status 61: PCI DEVICES Enumeration Started
Status 62: PCI DEVICES Enumeration Ended
Status 9F: Dispatching Drivers
Status 9E: IOFPGA Found
Status 9A: Booting From Primary ROM
Status 98: Found Cisco IDE
Status 98: Found Cisco IDE
Status 90: Loading Boot Loader
Reset Reason Registers: 0x0 0x8
Filesystem type is ext2fs, partition type 0x83
GNU GRUB version 0.97
Autobooting bootflash:/n7000-s1-kickstart.5.1.1a.bin bootflash:/n7000-s1-dk9.5.
1.1a.bin...
Filesystem type is ext2fs, partition type 0x83
Booting kickstart image: bootflash:/n7000-s1-kickstart.5.1.1a.bin....
...............................................................................
....................Image verification OK
INIT:
Checking all filesystems...... done.
Loading system software /bootflash//n7000-s1-dk9.5.1.1a.bin read done
Uncompressing system image: bootflash:/n7000-s1-dk9.5.1.1a.bin Mon Mar 28 15:06:35 CEST 2011
blogger: nothing to do.
..done Mon Mar 28 15:06:38 CEST 2011
Load plugins that defined in image conf: /isan/plugin_img/img.conf
Loading plugin 0: core_plugin...
0: swid-core-supdc3, swid-core-supdc3
num srgs 1
0: swid-supdc3-ks, swid-supdc3-ks
INIT: Entering runlevel: 3
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
2011 Mar 28 15:09:52 de5ifbsw004 %$ VDC-1 %$ %SYSLOG-2-SYSTEM_MSG: Did not receive supstate notification in 180 seconds. Still waiting
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
bash-3.2#
2011 Mar 28 15:12:52 de5ifbsw004 %$ VDC-1 %$ %SYSLOG-2-SYSTEM_MSG: Did not receive supstate notification in 180 seconds. Still waiting
2011 Mar 28 15:13:04 switch-cmp 1301314384 CPPROXY Received a CLI request! ID: 20
2011 Mar 28 15:13:23 switch-cmp 1301314403 CPPROXY Received a CLI request! ID: 20
2011 Mar 28 15:13:41 switch-cmp 1301314421 CPPROXY Received a CLI request! ID: 20
Thanks for your thoughts!
Best regards
Philipp Maihoefer
Solved! Go to Solution.
09-20-2011 01:46 AM
You need to reload the entire chassis to rectify this issue. I've just had the same issue myself.
Make sure you have an up to date copy of your running-config before you reload as you will lose any unsaved changes when you boot.
03-29-2011 09:12 AM
Recovery Methods found in the DokuWiki of Cisco showed no success either:
09-20-2011 01:46 AM
You need to reload the entire chassis to rectify this issue. I've just had the same issue myself.
Make sure you have an up to date copy of your running-config before you reload as you will lose any unsaved changes when you boot.
10-09-2011 12:12 AM
You are right. Rebooting the whole chassis is something i wanted to avoid. In addition this was a bug in the software revision i used. This shouldn't happen again, once you upgraded to > 8.1.3.
Phil
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