Nexus 5596 boot variable on next reload

Dave Mumford · ‎11-10-2015

Hi , Im worried that a previous upgrade on Nexus 5596UP did not work correctly as the boot variable on next reload does not reflect the running version, see below:

>>>>>> From sh vers:

Software
BIOS: version 3.6.0
loader: version N/A
kickstart: version 7.0(6)N1(1)
system: version 7.0(6)N1(1)
Power Sequencer Firmware:
Module 1: version v7.0
Module 2: version v1.0
Module 3: version v1.0
Microcontroller Firmware: version v1.0.0.2
SFP uC: Module 1: v1.0.0.0
QSFP uC: Module not detected
BIOS compile time: 05/09/2012
kickstart image file is: bootflash:///n5000-uk9-kickstart.7.0.6.N1.1.bin
kickstart compile time: 4/7/2015 4:00:00 [04/07/2015 13:05:58]
system image file is: bootflash:///n5000-uk9.7.0.6.N1.1.bin
system compile time: 4/7/2015 4:00:00 [04/07/2015 18:04:26]

Hardware
cisco Nexus 5596 Chassis ("O2 48X10GE/Modular Supervisor")

>>>>> From show boot :

Current Boot Variables:

kickstart variable = bootflash:/n5000-uk9-kickstart.7.0.6.N1.1.bin
system variable = bootflash:/n5000-uk9.7.0.6.N1.1.bin
Boot POAP Disabled

Boot Variables on next reload:

kickstart variable = bootflash:/n5000-uk9-kickstart.5.2.1.N1.4.bin
system variable = bootflash:/n5000-uk9.5.2.1.N1.4.bin
Boot POAP Disabled

I would also like to know if we should perform another install all of the system and kickstart files ?

Any help appreciated.

alessandro.s · ‎11-10-2015

Hi Dave,

as i know, you don't need do perform another install all because the upgrade seems to worked correctly (infact current running images are kickstart image file is: bootflash:///n5000-uk9-kickstart.7.0.6.N1.1.bin and system image file is: bootflash:///n5000-uk9.7.0.6.N1.1.bin .

Probably you need to re-set the boot variables reflecting new images using those commands :

no boot system bootflash:n5000-uk9.5.2.1.N1.4.bin

system bootflash:n5000-uk9.7.0.6.N1.1.bin

no boot kickstart bootflash:n5000-uk9-kickstart.5.2.1.N1.4.bin

boot kickstart bootflash:n5000-uk9.7.0.6.N1.1.bin

and then verify the boot variables on next reload issuing the show boot command.

Hope this helps.

Regards

Dave Mumford · ‎11-11-2015

Hi Alessandro,

This is resolved now, the problem i had initially is that I did the system boot statement first and it tell me this (to use an install all command):

MEDC2ASW01(config)# boot system bootflash:n5000-uk9.6.0.2.N2.6.bin

Warning: Changing bootvariables and reloading is not recommended on this platform. Use install all command for NX-OS upgrades/downgrades.

Performing image verification and compatibility check,please wait....

But if i do the kickstart first it works fine , but you must do a copy r s before you can see the results in a show boot. See below:

MEDC1ASW01(config)# boot kickstart bootflash:n5000-uk9-kickstart.6.0.2.N2.6.bin
Performing image verification and compatibility check,please wait....
Note: system and kickstart bootvars are pointing to incompatible images
MEDC1ASW01(config)# boot system bootflash:n5000-uk9.6.0.2.N2.6.bin
Performing image verification and compatibility check,please wait....
MEDC1ASW01(config)#
MEDC1ASW01# copy r s
[########################################] 100%
Copy complete, now saving to disk (please wait)...

alessandro.s · ‎11-11-2015

Hi Dave,

i'm happy to know you solved the issue, but why are you setting 6.0.2.N2.6.bin and not 7.0.6.N1?

Regards,

Alessandro