Recovering A Secondary Vsm With Active Primary - Cisco Nexus 1000V Troubleshooting Manual

Chapter 5 Upgrades
Example 5-1
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.
The information in this section does not apply when upgrading from Release 4.2(1)SV1(4) to
Note
Release 4.2(1)SV2(1.1).
Stop the upgrade on the VSM, using the
Step 1
Change the boot variables back to the previous version using the
Step 2
page 5-9
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:
•
•
•
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.
OL-31593-01
Upgrade: Enter Upgrade Information
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.
"Stopping a VSM Upgrade" section on page 5-8
"Changing Boot Variables" section on
Cisco Nexus 1000V Troubleshooting Guide, Release 5.2(1)SV3(1.1)
Problems with the GUI Upgrade
5-7