Changing Boot Variables - Cisco Nexus 1000V Troubleshooting Manual

Problems with the GUI Upgrade
S e n d d o c u m e n t c o m m e n t s t o n e x u s 1 k - d o c f e e d b a c k @ c i s c o . c o m .

Changing Boot Variables

You can use this procedure to replace the software images used to boot the VSM.
BEFORE YOU BEGIN
•
•
DETAILED STEPS
Display the current boot variables.
Step 1
show boot
Example:
n1000v# show boot
sup-1
kickstart variable = bootflash:/nexus-1000v-kickstart-mz.4.0.4.SV1.3a.bin
system variable = bootflash:/nexus-1000v-mz.4.0.4.SV1.3a.bin
sup-2
kickstart variable = bootflash:/nexus-1000v-kickstart-mzg.4.2.1.SV1.4.bin
system variable = bootflash:/nexus-1000v-mzg.4.2.1.SV1.4.bin
No module boot variable set
n1000v(config)#
Remove the current system and kickstart boot variables.
Step 2
configure terminal
no boot system
no boot kickstart
Example:
n1000v# configure terminal
n1000v(config)# no boot system
n1000v(config)# no boot kickstart
n1000v#(config)#
Restore the system and kickstart boot variables to the original pre-upgrade filenames.
Step 3
boot system bootflash:system-boot-variable-name
boot system bootflash:kickstart-boot-variable-name
Example:
n1000v#(config)# boot system bootflash:nexus-1000v-mz.4.0.4.SV1.3a.bin
n1000v#(config)# boot kickstart bootflash:nexus-1000v-kickstart-mz.4.0.4.SV1.3a.bin
n1000v#(config)#
Copy the running configuration to the startup configuration.
Step 4
copy run start
Example:
n1000v#(config)# copy run start
[########################################] 100%e
n1000v#(config)#
Verify the change in the system and kickstart boot variables.
Step 5
show boot
Cisco Nexus 1000V Troubleshooting Guide, Release 4.2(1)SV2(2.1)
5-10
You are logged in to the CLI in EXEC mode.
You know the filenames of the pre-upgrade system and kickstart image files to apply.
Chapter 5 Upgrade
OL-28795-01