02-03-2012 04:06 AM - edited 03-07-2019 04:43 AM
After trying to downgrade a Nexus 7K from 5.2.1 to 5.1.5 by updating the boot & kickstart boot statements and reloading, I'm now stuck in an endless cycle of reloading. See below:
Is there a break sequence which will allow me to modify the boot statement back to the original via ROMMON or something similar?
This is what I'm getting on the terminal at the moment:
INIT: version 2
Checking all filesystems...... done.
WARNING! WARNING! WARNING! *************
This kickstart image is not compatible with *
the current hardware platform *
Rebooting system *
WARNING! WARNING! WARNING! *************
Sending all processes the TERM signal...
Sending all processes the KILL signal...
Unmounting filesystems...
Restarting system.
NX7 SUP Ver 3.22.0
Serial Port Parameters from CMOS
PMCON_1: 0x200
PMCON_2: 0x0
PMCON_3: 0x38
PM1_STS: 0x1
Performing Memory Detection and Testing
Total mem found : 8192 MB
Performing memory test... Passed.
NumCpus = 2.
Status 61: PCI DEVICES Enumeration Started
Status 62: PCI DEVICES Enumeration Ended
Status 9F: Dispatching Drivers
Status 63: Soft Resetting Board
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
02-03-2012 04:44 AM
Do you see any checks failing within all the logs you see on screen? In some case that ended up as SUp HW fault. Possibly worth trying to reaset SUP within slot and boot again. May get different result.
Also you can opene priority TAC case for engineer to check this online.
Nik
02-27-2012 12:09 PM
Ok, this thread got revived recently and I hope the following helps others in the future.;-)
Jim's question was
Snip >>>>>
Is there a break sequence which will allow me to modify the boot statement back to the original via ROMMON or something similar?
Snip >>>>>
Ans: Yes. ctrl+c is the escape sequence which is the equivalent of sending break during boot phase (in IOS) to drop into "Loader" prompt.
Press ctrl+c when you see kickstart image is booting and you should drop into loader prompt.
Snip >>>>>
GNU GRUB version 0.97
Autobooting bootflash:/n7000-s1-kickstart.5.1.3.bin bootflash:/n7000-s1-dk9.5.1
.3.bin...
Filesystem type is ext2fs, partition type 0x83
Booting kickstart image: bootflash:/n7000-s1-kickstart.5.1.3.bin....
..................................................................Aborting Image Boot
Snip >>>>>
You can expect to see:
Snip >>>>>
GNU GRUB version 0.97
Loader Version 3.22.0
loader>
Snip >>>>>
Here, you have the familar ? to help you through.
loader> ?
? Print the command list
boot Boot image
dir List file contents on a device
help Print the command list or the specific command usage
reboot Reboot the system
set Set network configuration
show Show loader configuration
loader>
loader> help boot
boot: boot Boot image
usage: boot
kickstart_image:
system_image :
tftp_file : tftp://
server_ip : tftp server IP address
filename : file on tftp server
device_file : [
device : bootflash: | slot0: | usb1:| usb2:
partition : Partition number
path : File name on device
Description: Boot the specified image.
loader>
loader> boot
The above cmd will get you going back to the older/working version.
If you run into this problem and need further assist, kindly provide the basic sh cmds (sh ver, sh inv, sh mod, sh run etc) while running the older ver along with the console log when you see the problem.
Also include the precise cmds typed to change the boot statement, save the config and include the output of sh boot
Palani
02-28-2012 05:33 AM
I can confirm that the ctrl+c break command does the trick. However, I think in future I will pay heed to our Cisco rep and only use the ISSU feature to upgrade/downgrade to different versions of software. This way, you should never end up at this point.
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: