Upgrading a Standalone VSM
This chapter contains the following sections:
Upgrading a System with a Standalone VSM
Upgrading a Standalone VSM
 Note | The example may contain Cisco Nexus 1000V versions and filenames that are not relevant to your release. Refer to the Cisco Nexus 1000V and VMware Compatibility Information for your specific versions and filenames. |
| 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, go to the URL http://www.cisco.com/ and click Log In at the top of the page. Enter your Cisco username and password.
| ||
| 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
| ||
| 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:.
| ||
| Step 9 | Read the release notes for the related image file. See the Cisco Nexus 1000V Release Notes. | ||
| 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 system bootflash:nexus-1000v.5.2.1.SV3.1.5b.bin kickstart
bootflash: nexus-1000v-kickstart.5.2.1.SV3.1.5b.bin
Verifying image bootflash:/nexus-1000v-kickstart-5.2.1.SV3.1.5b.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/nexus-1000v-5.2.1.SV3.1.5b.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/nexus-1000v.5.2.1.SV3.1.5b.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/nexus-1000v-kickstart.5.2.1.SV3.1.5b.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)SV2(2.1) 5.2(1)SV3(1.5b) yes
1 kickstart 4.2(1)SV2(2.1) 5.2(1)SV3(1.5b) yes
Module Running-Version ESX Version VSM Compatibility ESX Compatibility
------ ------------------ --------------------------- ------------------ ----------------------
3 4.2(1)SV2(2.1) VMware ESXi 5.0.0 COMPATIBLE COMPATIBLE
Releasebuild-1311175 (3.0)
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.
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.
Example: switch# show version
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2015, 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
kickstart: version 5.2(1)SV3(1.5b)
system: version 5.2(1)SV3(1.5b)
kickstart image file is: bootflash:///n1000v-dk9-kickstart.5.2.1.SV3.1.5b.bin
kickstart compile time: 3/25/2015 22:00:00 [07/26/2015 05:51:47]
system image file is: bootflash:///n1000v-dk9.5.2.1.SV3.1.5b.bin
system compile time: 3/25/2015 22:00:00 [07/26/2015 06:46:26)
Hardware
cisco Nexus 1000V Chassis ("Virtual Supervisor Module")
Intel(R) Xeon(R) CPU E5-2660 with 4126584 kB of memory.
Processor Board ID T5056A10FC9
Device name: vsm
bootflash: 2059572 kB
System uptime is 2 days, 17 hours, 13 minutes, 16 seconds
Kernel uptime is 2 day(s), 17 hour(s), 14 minute(s), 22 second(s)
plugin
Core Plugin, Ethernet Plugin, Virtualization Plugin
...
|
What to Do Next
Continue to Upgrading the VEMs Manually from Release 4.2(1)SV2(1.1x) and Later Releases to the Current Release.
Feedback