Problems with the GUI Upgrade
The following are symptoms, possible causes, and solutions for problems with software upgrade using the GUI upgrade application.
Note If you are upgrading directly from SV1(4) to SV1(4a), the GUI is not used and this section does not apply. This section is applicable only if you use the GUI for an intermediate upgrade from a SV1(3x) release to SV1(4), prior to upgrading to SV1(4a).
Table 5-3 Problems with the GUI Upgrade
|
|
|
The upgrade GUI stops and times out after 10 minutes and displays the following message: Error: Could not contact the upgraded VSM at n.n.n.n. Please check the connection. |
During the upgrade, you configured an unreachable IP address for the mgmt0 interface. In this case, one VSM in the redundant pair has new software installed and is unreachable. The other VSM has the original pre-upgrade software version installed and is reachable. |
1. Use one of the following sets of procedures to return your VSM pair to the previous software version: – “Recovering a Secondary VSM with Active Primary” section – “Recovering a Primary VSM with Active Secondary” section 2. Restart the software upgrade using the instructions in the Cisco Nexus 1000V Installation and Upgrade Guide. |
The upgrade GUI stops and times out after 10 minutes and displays the following message: Error: Could not contact the upgraded VSM at 10.104.244.150. Please check the connection. After timing out, one VSM comes up in switch(boot) mode. |
You have selected incompatible or incorrect VSM software images for the upgrade. The software images you selected from the GUI selection list included a system image for one software version and a kickstart image for another software version. These images must be for the same software version. For an example of how software images are selected during the upgrade, see Example 5-1. |
1. To continue the upgrade, first recover the VSM using one of the following: – “Recovering a Secondary VSM with Active Primary” section – “Recovering a Primary VSM with Active Secondary” section 2. Restart the software upgrade using the instructions in the Cisco Nexus 1000V Installation and Upgrade Guide. |
Example 5-1 Upgrade: Enter Upgrade Information
This example shows how to specify system and kickstart images during the upgrade process. In this example, the images specified are from the same release, SV1.4. If you specify a kickstart image from one release, and a system image from another, then the upgrade cannot proceed.
Recovering a Secondary VSM with Active Primary
You can recover a secondary VSM when the primary VSM is active.
Note The information in this section does not apply when upgrading from Release 4.2(1)SV1(4) to
Release 5.2(1)SV3(4.1).
Step 1 Stop the upgrade on the VSM, using the “Stopping a VSM Upgrade” section
Step 2 Change the boot variables back to the previous version using the “Changing Boot Variables” section
Step 3 From the vCenter Server left-hand panel, right-click the secondary VSM and then choose Delete from Disk.
The secondary VSM is deleted.
Step 4 Create a new VSM by reinstalling the software using the vSphere Client Deploy OVF Template wizard, specifying the following:
- The Cisco Nexus 1000V secondary configuration method
(configures the secondary VSM in an HA pair using a GUI setup dialog).
- The host or cluster of the primary VSM.
- The same domain ID and password as that of the primary VSM.
For a detailed procedure, see the Cisco Nexus 1000V Installation and Upgrade Guide.
The VSM comes up and forms an HA pair with the newly created standalone VSM. The VSMs have the previous version of the software installed.
Stopping a VSM Upgrade
You can stop a VSM upgrade that is in progress.
BEFORE YOU BEGIN
- Log in to the CLI in EXEC mode.
Note The information in this section does not apply when upgrading from Release 4.2(1)SV1(4) to
Release 5.2(1)SV3(4.1).
DETAILED STEPS
Step 1 Display upgrade status.
show svs upgrade status
switch# show svs upgrade status
Upgrade mgmt0 ipv4 addr: 1.1.1.1
Upgrade control0 ipv4 addr:
Step 2 Stop the upgrade.
a. configure terminal
b. no svs upgrade start
switch# configure terminal
switch#(config)# no svs upgrade start
WARNING! VSM upgrade process is aborted
Step 3 Display the upgrade status.
show svs upgrade status
switch#(config)# show svs upgrade status
Upgrade control0 ipv4 addr:
Step 4 You have completed this procedure. Return to one of these sections:
Changing Boot Variables
You can replace the software images used to boot the VSM.
BEFORE YOU BEGIN
- Log in to the CLI in EXEC mode.
- Know the filenames of the pre-upgrade system and kickstart image files to apply.
DETAILED STEPS
Step 1 Display the current boot variables.
show boot
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
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
Step 2 Remove the current system and kickstart boot variables.
a. configure terminal
b. no boot system
c. no boot kickstart
switch# configure terminal
switch(config)# no boot system
switch(config)# no boot kickstart
Step 3 Restore the system and kickstart boot variables to the original pre-upgrade filenames.
a. boot system bootflash: system-boot-variable-name
b. boot system bootflash: kickstart-boot-variable-name
switch#(config)# boot system bootflash:nexus-1000v-mz.4.0.4.SV1.3a.bin
switch#(config)# boot kickstart bootflash:nexus-1000v-kickstart-mz.4.0.4.SV1.3a.bin
Step 4 Copy the running configuration to the startup configuration.
copy run start
switch#(config)# copy run start
[########################################] 100%e
Step 5 Verify the change in the system and kickstart boot variables.
show boot
switch#(config)# show boot
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
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
No module boot variable set
Step 6 You have completed this procedure. Return to one of these sections:
Powering On the VSM
You can power on the newly created VSM.
Step 1 From the vCenter Server left-hand panel, right-click the VSM and then choose Power > Power On.
The VSM starts.
Step 2 You have completed this procedure. Return to the “Recovering a Primary VSM with Active Secondary” section.
Changing the HA Role
You can change the HA role of the VSM.
BEFORE YOU BEGIN
- Log in to the CLI in EXEC mode.
- Know the domain ID of the existing VSM.
DETAILED STEPS
Step 1 Go to the domain of the existing VSM.
a. configure terminal
b. svs-domain
c. domain id domain-id
switch(config)# svs-domain
switch(config-svs-domain)# domain id 1941
Warning: Config saved but not pushed to vCenter Server due to inactive connection!
Step 2 Change the HA role.
system redundancy role [primary | secondary | standalone]
switch(config-svs-domain)# system redundancy role secondary
Setting will be activated on next reload.
switch(config-svs-domain)#
switch(config-svs-domain)# system redundancy role primary
Setting will be activated on next reload.
switch(config-svs-domain)#
Step 3 Copy the running configuration to the startup configuration.
copy run start
switch#(config-svs-domain)# copy run start
[########################################] 100%e
switch#(config-svs-domain)#
Step 4 You have completed this procedure. Return to the “Recovering a Primary VSM with Active Secondary” section.
Recovering a Primary VSM with Active Secondary
You can recover a primary VSM when the secondary VSM is active.
Step 1 Stop the upgrade on the secondary VSM by completing the Stopping a VSM Upgrade
Step 2 Change the boot variables back to the previous version by completing the Changing Boot Variables
Step 3 From the vCenter Server left-hand panel, right-click the primary VSM and then choose Delete from Disk.
The primary VSM is deleted.
Step 4 Create a new VSM by reinstalling the software from the OVA and specifying the following:
- Manual (CLI) configuration method instead of GUI.
- The host or cluster of the existing secondary VSM.
For detailed installation procedures, see the Cisco Nexus 1000V Installation and Upgrade Guide.
Step 5 Make sure that the port groups between the host server and VSM are not connected when the new VSM is powered on by completing the Disconnecting the Port Groups.
Step 6 Power on the newly-created VSM by completing the Powering On the VSM.
The VSM comes up with the standalone HA role.
Step 7 Change the HA role of the newly created standalone VSM to primary and save the configuration by completing the Changing the HA Role.
Step 8 Power off the newly created VSM by completing the Powering Off the VSM.
Step 9 Make sure that the port groups between the host server and VSM are connected when the new VSM is powered on by completing the Connecting the Port Groups.
Step 10 Power on the newly created VSM by completing the Powering On the VSM.
The VSM comes up, connects with the host server, and forms an HA pair with the existing primary VSM.
Disconnecting the Port Groups
You can disconnect and prevent port groups to the VSM from connecting to the host server.
Step 1 In vCenter Server, select the VSM and then choose Edit > Settings.
The Virtual Machine Properties dialog box opens.
Step 2 Select the Control port group and uncheck the following Device Settings:
- Connected
- Connect at Power On
The connection from the VSM to the host server through the control port is dropped and is not restored when you power on the VSM.
Step 3 Select the Management port group and uncheck the following Device Settings:
- Connected
- Connect at Power On
The connection from the VSM to the host server through the management port is dropped and is not restored when you power on the VSM.
Step 4 You have completed this procedure. Return to the “Recovering a Primary VSM with Active Secondary” section.
Powering Off the VSM
You can power off the newly created VSM.
Step 1 From the vCenter Server left-hand panel, right-click the VSM and then choose Power > Power Off.
The VSM shuts down.
Step 2 You have completed this procedure. Return to the “Recovering a Primary VSM with Active Secondary” section.
Connecting the Port Groups
You can make sure that the port groups to the host connect when you power on the VSM.
Step 1 In vCenter Server, select the VSM and then choose Edit > Settings.
The Virtual Machine Properties dialog box opens.
Step 2 Select the Control port group and check the following Device Settings:
When you power on the VSM, it will connect to the host server through the control port.
Step 3 Select the Management port group and check the following Device Setting:
When you power on the VSM, it will connect to the host server through the management port.
Step 4 You have completed this procedure. Return to the “Recovering a Primary VSM with Active Secondary” section.
Upgrade Troubleshooting Commands
You can troubleshoot problems related to upgrades.
Example 5-2 show boot Command
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
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
Example 5-3 show module Command (VSM upgraded first with ISSU, VEM upgrade pending)
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
1 0 Virtual Supervisor Module Nexus1000V ha-standby
2 0 Virtual Supervisor Module Nexus1000V active *
3 248 Virtual Ethernet Module NA ok
--- --------------- ------
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
2 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
3 02-00-0c-00-03-00 to 02-00-0c-00-03-80 NA
Mod Server-IP Server-UUID Server-Name
--- --------------- ------------------------------------ --------------------
3 10.78.109.51 4220900d-76d3-89c5-17d7-b5a7d1a2487f 10.78.109.51
Example 5-4 show module Command (VEM and VSM upgraded)
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
1 0 Virtual Supervisor Module Nexus1000V ha-standby
2 0 Virtual Supervisor Module Nexus1000V active *
3 248 Virtual Ethernet Module NA ok
--- --------------- ------
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
2 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
3 02-00-0c-00-03-00 to 02-00-0c-00-03-80 NA
Mod Server-IP Server-UUID Server-Name
--- --------------- ------------------------------------ --------------------
3 10.78.109.51 4220900d-76d3-89c5-17d7-b5a7d1a2487f 10.78.109.51
Example 5-5 show running-config | include boot Command
switch# show running-config | include boot
boot kickstart bootflash:/nexus-1000v-kickstart-mzg.4.2.1.SV1.4a.bin sup-1
boot system bootflash:/nexus-1000v-mzg.4.2.1.SV1.4a.bin sup-1
boot kickstart bootflash:/nexus-1000v-kickstart-mzg.4.2.1.SV1.4a.bin sup-2
boot system bootflash:/nexus-1000v-mzg.4.2.1.SV1.4a.bin sup-2
Example 5-6 show startup-config | include boot Command
switch# show startup-config | include boot
boot kickstart bootflash:/nexus-1000v-kickstart-mzg.4.2.1.SV1.4a.bin sup-1
boot system bootflash:/nexus-1000v-mzg.4.2.1.SV1.4a.bin sup-1
boot kickstart bootflash:/nexus-1000v-kickstart-mzg.4.2.1.SV1.4a.bin sup-2
boot system bootflash:/nexus-1000v-mzg.4.2.1.SV1.4a.bin sup-2
switch#
Example 5-7 show svs connections Command
switch# show svs connections
protocol: vmware-vim https
datacenter name: Hamilton-DC
DVS uuid: 9b dd 36 50 2e 27 27 8b-07 ed 81 89 ef 43 31 17
operational status: Connected
Example 5-8 show svs upgrade status Command
switch# show svs upgrade status
Upgrade mgmt0 ipv4 addr: 1.1.1.1
Upgrade control0 ipv4 addr:
Example 5-9 show system redundancy status Command
switch# show system redundancy status
Internal state: Active with HA standby
Redundancy state: Standby
Supervisor state: HA standby
Internal state: HA standby
Example 5-10 show vmware vem upgrade status Command
switch# show vmware vem upgrade status
Upgrade VIBs: System VEM Image
Upgrade Notification Sent Time:
Upgrade Status Time(vCenter):
Upgrade End Time(vCenter):