The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The following chapter describes how to upgrade a standalone VSM.
This chapter contains the following section:
•Upgrading a System with a Standalone VSM
Note This procedure is applicable only if the VSM is in standalone mode. This procedure does not work if the VSM is primary or secondary and the standby is shut down.
This section describes how to upgrade a Cisco Nexus 1000V standalone VSM.
The best practice for deployment of VSMs is in an HA pair in a production environment. The VSM standalone redundancy role can be used in a test or demo environment, but we recommend that you deploy VSMs in an HA pair in such environments.
Step 1 Log in to the VSM on the console.
Step 2 Log in to Cisco.com to access the links provided in this document. To log in to Cisco.com, go to the URL http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco username and password.
Note Unregistered Cisco.com users cannot access the links provided in this document.
Step 3 Access the Software Download Center by using this URL: http://www.cisco.com/public/sw-center/index.shtml
Step 4 Navigate to the download site for your switch.
You see links to the download images for your switch.
Step 5 Select and download the Cisco Nexus 1000V zip file and extract the kickstart and system software files to a server.
Step 6 Ensure that the required space is available for the image files to be copied.
switch# dir bootflash:
.
.
.
Usage for bootflash://
485830656 bytes used
1109045248 bytes free
1594875904 bytes total
Tip We recommend that you have the kickstart and system image files for at least one previous release of the Cisco Nexus 1000V software on the system to use if the new image files do not load successfully.
Step 7 Delete unnecessary files to make space available if you need more space on the VSM bootflash,
Step 8 If you plan to install the images from the bootflash:, copy the Cisco Nexus 1000V kickstart and system images to the active VSM bootflash using a transfer protocol. You can use ftp:, tftp:, scp:, or sftp:. The examples in this procedure use scp:.
Note When you download an image file, change to your FTP environment IP address or DNS name and the path where the files are located.
switch# copy
scp://user@scpserver.cisco.com//downloads/nexus-1000v-kickstart-4.2.1.SV1.5.1.bin
bootflash:nexus-1000v-kickstart-4.2.1.SV1.5.1.bin
switch# copy scp://user@scpserver.cisco.com//downloads/nexus-10000v-4.2.1.SV1.5.1.bin
bootflash:nexus-1000v-4.2.1.SV1.5.1.bin
Step 9 Read the release notes for the related image file. See the Cisco Nexus 1000V Release Notes, Release 4.2(1)SV1(5.1).
Step 10 Determine the VSM status.
switch# show system redundancy status
Redundancy role
---------------
administrative: standalone
operational: standalone
Redundancy mode
---------------
administrative: HA
operational: None
This supervisor (sup-1)
-----------------------
Redundancy state: Active
Supervisor state: Active
Internal state: Active with no standby
Other supervisor (sup-2)
------------------------
Redundancy state: Not present
Step 11 Save the running configuration to the start configuration.
switch# copy running-config startup-config
Step 12 Update the boot variables and module images on the VSM.
switch# install all kickstart bootflash:nexus-1000v-kickstart-4.2.1.SV1.5.1.bin system
bootflash:nexus-1000v-4.2.1.SV1.5.1.bin
Verifying image bootflash:/nexus-1000v-kickstart-4.2.1.SV1.5.1.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/nexus-1000v-4.2.1.SV1.5.1.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/nexus-1000v-4.2.1.SV1.5.1.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/nexus-1000v-kickstart-4.2.1.SV1.5.1.bin.
[####################] 100% -- SUCCESS
Notifying services about system upgrade.
[####################] 100% -- SUCCESS
Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes disruptive reset Reset due to single supervisor
Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------- ---------------------- ---------------------- ------------
1 system 4.2(1)SV1(4) 4.2(1)SV1(5.1) yes
1 kickstart 4.2(1)SV1(4) 4.2(1)SV1(5.1) yes
Module Running-Version ESX Version VSM Compatibility ESX Compatibility
------ ---------------------- ---------------------------------------------------- ---------------------- ----------------------
3 4.2(1)SV1(4) VMware ESXi 4.0.0 Releasebuild-208167 (1.9) COMPATIBLE COMPATIBLE
Switch will be reloaded for disruptive upgrade.
Do you want to continue with the installation (y/n)? [n]
Step 13 Continue with the installation by pressing Y.
Note If you press N, the installation exits gracefully.
Install is in progress, please wait.
Setting boot variables.
[####################] 100% -- SUCCESS
Performing configuration copy.
[####################] 100% -- SUCCESS
Finishing the upgrade, switch will reboot in 10 seconds.
Step 14 After the switch completes the reload operation, log in and verify that the switch is running the required software version.
switch# show version
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2011, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
loader: version unavailable [last: loader version not available]
kickstart: version 4.2(1)SV1(5.1)
system: version 4.2(1)SV1(5.1)
kickstart image file is: bootflash:/nexus-1000v-kickstart-4.2.1.SV1.5.1.bin
kickstart compile time: 3/27/2011 14:00:00 [03/27/2011 22:26:45]
system image file is: bootflash:/nexus-1000v-4.2.1.SV1.5.1.bin
system compile time: 3/27/2011 14:00:00 [03/28/2011 00:56:08]
Hardware
cisco Nexus 1000V Chassis ("Virtual Supervisor Module")
Intel(R) Xeon(R) CPU with 2075740 kB of memory.
Processor Board ID T5056B050BB
Device name: BL1-VSM
bootflash: 3122988 kB
Kernel uptime is 0 day(s), 0 hour(s), 6 minute(s), 23 second(s)
plugin
Core Plugin, Ethernet Plugin, Virtualization Plugin
...
Step 15 Continue to the "Upgrading the VEMs from Release 4.2(1)SV1(4), 4.2(1)SV1(4a), or 4.2(1)SV1(4b) to Release 4.2(1)SV1(5.1)" section.