Step 1
| Log in to the
active VSM.
|
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://software.cisco.com/download/navigator.html
|
Step 4
| Navigate to the
download site for your system.
You see links to
the download images for your switch.
|
Step 5
| Choose 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 file(s) 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
| Verify that
there is space available on the standby VSM.
switch# dir bootflash://sup-standby/
.
.
.
Usage for bootflash://
485830656 bytes used
1109045248 bytes free
1594875904 bytes total
|
Step 8
| Delete any
unnecessary files to make space available if you need more space on the standby
VSM.
|
Step 9
| If you plan to
install the images from the bootflash:, copy the Cisco Nexus 1000V kickstart
and system images
to the active VSM by 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.
|
-
Copy
kickstart and system images.
switch# copy scp://user@scpserver.cisco.com/downloads/n1000v-dk9-kickstart.5.2.1.SV3.3.1.bin
bootflash:n1000v-dk9-kickstart.5.2.1.SV3.3.1.bin
switch# copy scp://user@scpserver.cisco.com/downloads/n1000v-dk9.5.3.1.SV3.v.bin
bootflash:n1000v-dk9.5.2.1.SV3.3.1.bin vnmpa bootflash:vsmcpa.3.2.3a.bin
|
Step 10
| Check on the
impact of the ISSU upgrade for the kickstart and system images.
-
kickstart
and system
switch# show install all impact kickstart bootflash:nexus-1000v-kickstart.5.2.1.SV3.3.1.bin system bootflash:nexus-1000v.5.2.1.SV3.3.1.bin
Verifying image bootflash:/nexus-1000v-kickstart.5.2.1.SV3.3.1.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/nexus-1000v-5.2.1.SV3.3.1.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/nexus-1000v.5.2.1.SV3.3.1.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/nexus-1000v-kickstart.5.2.1.SV3.3.1.bin.
[####################] 100% -- SUCCESS
Notifying services about system upgrade.
[####################] 100% -- SUCCESS
Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes non-disruptive reset
2 yes non-disruptive reset
Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------- ---------------------- ---------------------- ------------
1 system 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
1 kickstart 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
2 system 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
2 kickstart 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
Module Running-Version ESX Version VSM Compatibility ESX Compatibility
------ ---------------------- ---------------------------------------------------- ---------------------- ----------------------
3 5.2(1)SV3(3.1) VMware ESXi 5.0.0 Releasebuild-469512 (3.1) COMPATIBLE COMPATIBLE
4 5.2(1)SV3(3.1) VMware ESXi 5.0.0 Releasebuild-469512 (3.1) COMPATIBLE COMPATIBLE
|
Step 11
| Read the release
notes for the related image file. See the
Cisco Nexus 1000V Release Notes.
|
Step 12
| Determine if
Virtual Security Gateway (VSG) is configured in the deployment:
|
Step 13
| Save the running
configuration to the startup configuration.
switch# copy running-config startup-config
|
Step 14
| Save the running
configuration on the bootflash and externally.
switch# copy running-config bootflash:run-cfg-backup
switch# copy running-config scp://user@tftpserver.cisco.com/n1kv-run-cfg-backup
Note
|
You can also
run a VSM backup. See the “Configuring VSM Backup and Recovery” chapter of the
Cisco Nexus 1000V System Management Configuration Guide.
|
|
Step 15
| Perform the
upgrade on the active VSM using the
kickstart and system images.
-
Upgrade
using the kickstart and system images.
switch# install all impact kickstart bootflash:///n1000v-dk9-kickstart.5.2.1.SV3.3.1.bin system bootflash:n1000v-dk9.5.2.1.SV3.3.1.bin vnmpa bootflash:vsmcpa.3.2.3a.bin
Verifying image bootflash:/nexus-1000v-kickstart.5.2.1.SV3.3.1.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS
Verifying image bootflash:/nexus-1000v.5.2.1.SV3.3.1.bin for boot variable "system".
[####################] 100% -- SUCCESS
Verifying image type.
[####################] 100% -- SUCCESS
Extracting "system" version from image bootflash:/nexus-1000v.5.2.1.SV3.3.1.bin.
[####################] 100% -- SUCCESS
Extracting "kickstart" version from image bootflash:/nexus-1000v-kickstart.5.2.1.SV3.3.1.bin.
[####################] 100% -- SUCCESS
Notifying services about system upgrade.
[####################] 100% -- SUCCESS
Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes non-disruptive reset
2 yes non-disruptive reset
Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------- ---------------------- ---------------------- ------------
1 system 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
1 kickstart 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
2 system 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
2 kickstart 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
Module Running-Version ESX Version VSM Compatibility ESX Compatibility
------ ---------------------- ---------------------------------------------------- ---------------------- ----------------------
3 5.2(1)SV3(3.1) VMware ESXi 5.0.0 Releasebuild-469512 (3.0) COMPATIBLE COMPATIBLE
4 5.2(1)SV3(3.1) VMware ESXi 5.0.0 Releasebuild-469512 (3.0) COMPATIBLE COMPATIBLE
Do you want to continue with the installation (y/n)? [n]
Note
|
Ensure
that you provide the
vnmpa parameter for the
install all command while upgrading VSM.
|
|
Step 16
| Continue with
the installation by pressing
Y.
Note
|
If you press
N, the installation exits gracefully.
|
Install is in progress, please wait.
Syncing image bootflash:/nexus-1000v-kickstart.5.2.1.SV3.3.1.bin to standby.
[####################] 100% -- SUCCESS
Syncing image bootflash:/nexus-1000v.5.2.1.SV3.3.1.bin to standby.
[####################] 100% -- SUCCESS
Setting boot variables.
[####################] 100% -- SUCCESS
Performing configuration copy.
[####################] 100%2017 Feb 03 03:49:42 BL1-VSM %SYSMGR-STANDBY-5-CFGWRITE_STARTED: Configuration copy started (PID 3660).
[####################] 100% -- SUCCESS
Note
|
As part of
the upgrade process, the standby VSM is reloaded with new images. Once it
becomes the HA standby again, the upgrade process initiates a switchover. The
upgrade then continues from the new active VSM with the following output:
|
Continuing with installation, please wait
Module 2: Waiting for module online
-- SUCCESS
Install has been successful
|
Step 17
| After the
installation operation completes, log in and verify that the switch is running
the required software version.
switch# show version
Nexus1000v# show version
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2016, 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 5.2(1)SV3(3.1) [build 5.2(1)SV3(3.1)]
system: version 5.2(1)SV3(3.1) [build 5.2(1)SV3(3.1)]
kickstart image file is: bootflash:/nexus-1000v-kickstart.5.2(1)SV3(3.1).bin
kickstart compile time: 03/30/2017 3:00:00 [03/30/2017 12:49:49]
system image file is: bootflash:/nexus-1000v.5.2.1.SV3.3.1.bin
system compile time: 03/30/2017 3:00:00 [03/30/2017 13:42:57]
Hardware
cisco Nexus 1000V Chassis ("Virtual Supervisor Module")
Intel(R) Xeon(R) CPU with 2075740 kB of memory.
Processor Board ID T5056B1802D
Device name: Nexus1000v
bootflash: 1557496 kB
Kernel uptime is 4 day(s), 8 hour(s), 31 minute(s), 3 second(s)
plugin
Core Plugin, Ethernet Plugin, Virtualization Plugin
...
|
Step 18
| Copy the
running configuration to the startup configuration to adjust the startup-cgf
size.
switch# copy running-config startup-config
[########################################] 100%
switch#
|
Step 19
| Display the
log of the last installation.
switch# show install all status
This is the log of last installation.
Verifying image bootflash:/nexus-1000v-kickstart.5.2.1.SV3.3.1.bin for boot variable "kickstart".
-- SUCCESS
Verifying image bootflash:/nexus-1000v.5.2.1.SV3.3.1.bin for boot variable "system".
-- SUCCESS
Verifying image type.
-- SUCCESS
Extracting "system" version from image bootflash:/nexus-1000v.5.2.1.SV3.3.1.bin.
-- SUCCESS
Extracting "kickstart" version from image bootflash:/nexus-1000v-kickstart.5.2.1.SV3.3.1.bin.
-- SUCCESS
Notifying services about system upgrade.
-- SUCCESS
Compatibility check is done:
Module bootable Impact Install-type Reason
------ -------- -------------- ------------ ------
1 yes non-disruptive reset
2 yes non-disruptive reset
Images will be upgraded according to following table:
Module Image Running-Version New-Version Upg-Required
------ ---------- ---------------------- ---------------------- ------------
1 system 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
1 kickstart 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
2 system 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
2 kickstart 5.2(1)SV3(2.8) 5.2(1)SV3(3.1) yes
Images will be upgraded according to following table:
Module Running-Version ESX Version VSM Compatibility ESX Compatibility
------ ---------------------- ---------------------------------------------------- ---------------------- ----------------------
3 5.2(1)SV3(3.1) VMware ESXi 5.0.0 Releasebuild-469512 (3.0) COMPATIBLE COMPATIBLE
4 5.2(1)SV3(3.1) VMware ESXi 5.0.0 Releasebuild-469512 (3.0) COMPATIBLE COMPATIBLE
Install is in progress, please wait.
Syncing image bootflash:/nexus-1000v-kickstart.5.2.1.SV3.3.1.bin to standby.
-- SUCCESS
Syncing image bootflash:/nexus-1000v.5.2.1.SV3.3.1.bin to standby.
-- SUCCESS
Setting boot variables.
-- SUCCESS
Performing configuration copy.
-- SUCCESS
Module 2: Waiting for module online.
-- SUCCESS
Notifying services about the switchover.
-- SUCCESS
"Switching over onto standby".
switch#
switch#
switch#
switch# attach module 2
Attaching to module 2 ...
To exit type 'exit', to abort type '$.'
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2017, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
switch(standby)#
switch(standby)# show install all status
This is the log of last installation.
Continuing with installation, please wait
Trying to start the installer...
Module 2: Waiting for module online.
-- SUCCESS
Install has been successful.
switch(standby)#
|