Upgrading the Cisco VSG and the Cisco Prime NSC

This chapter contains the following sections:

Complete Upgrade Procedure

Table 1 Refer to the Section in Table Based on your Pre-upgrade Product Release
You are Upgrading From Follow The Sequential Steps in the Following Section:

Cisco VSG Release 5.2(1)VSG2(2.0) to Release 5.2(1)VSG2(2.1) and Cisco Prime NSC Release 3.4.2a to Release 3.4.2b

Upgrade Procedures for Cisco VSG Release 5.2(1)VSG2(2.0) to Release 5.2(1)VSG2(2.1) and Cisco Prime NSC Release 3.4.2a to Release 3.4.2b.

This includes upgrade procedures for Cisco Nexus 1000V Release 5.2(1)SV3(2.8) to Release 5.2(1)SV3(3.1).

To upgrade the Cisco PNSC, Cisco VSG, and Cisco Nexus 1000V, follow the steps sequentially:

  1. Stage 1: Upgrading Cisco PNSC

  2. Stage 2: Upgrading a Cisco VSG Pair

  3. Stage 3: Upgrading the VSM pair and the VEMs


Note

We highly recommend that you upgrade the Cisco VSG and the Cisco PNSC in the sequence listed. Any deviation from the ordered steps could cause disruption of your connectivity and data communication. The Cisco PNSC must be upgraded with the corresponding policy agent (PA).

Information About Cisco Prime NSC Upgrades

When you upgrade the Cisco PNSC software, all current command-line interface (CLI) and graphical user interface (GUI) sessions are interrupted, which means that you must restart any CLI or GUI sessions.

Information About Cisco VSG Upgrades

The upgrade procedure for a standalone Cisco VSG is hitful, which means that you must manually reload the Cisco VSG for the new image to become effective. In HA mode, the upgrade is hitless, which means that the standby Cisco VSG is upgraded first and then after a switchover, the previously active Cisco VSG is upgraded.

Because license information is not stored with the Cisco VSG but is maintained between the Virtual Supervisor Module (VSM) and Virtual Ethernet Module (VEM), if packets are received at the Cisco VSG, that means that the license is valid and the packets are processed.

An upgrade affects two bin files: the kickstart file and the system file.

An upgrade does not erase any of the existing information, when the Cisco VSG comes online. Because the Cisco VSG is stateless, it gets all this information from the Cisco PNSC at bootup.

Upgrade Guidelines and Limitations

Before upgrading the Cisco PNSC, Cisco VSG, and Cisco Nexus 1000V, read the following:

  • We highly recommend that you upgrade the Cisco VSG and the Cisco PNSC in the order provided. Any deviation from the ordered steps could cause disruption of your connectivity and data communication. The Cisco PNSC must be upgraded with the corresponding policy agent (PA).

  • We recommend that you take a snapshot or backup (clone) of the original Cisco PNSC and VSM prior to the upgrade process and then perform an ISSU upgrade process on both the VSM and the Cisco VSG. We do not recommend that you perform a manual upgrade.

  • For a full In-service Software Upgrade (ISSU) upgrade on both the Cisco VSG and VSM, follow these rules:

    • Install the Cisco PNSC before installing the Cisco VSG and VSM. The ISSU upgrade installs a new PA.

    • A new PA with an old Cisco PNSC is not supported and there should never be an interim stage in this state.

    • A copy run start is not required after the VSM upgrade.

  • The vn-service command is changed to the vservice command on the VSM port-profile in VSM Release 4.2(1)SV1(5.2).

  • Upgrade instructions include the following information:

    • Different stages of complete upgrade procedures and operations which are supported at different stages.

    • Different component versions after each stage.

    • Different operations supported after each stage.

VSG Environment Upgrade Matrix and Path

Cisco VSG upgrade involves upgrading the VSG, VNMC or PNSC, and Nexus 1000V environment. To upgrade VSG, you need to make sure that compatible versions of VSG, VNMC or PNSC, and Nexus 1000V are installed. This section lists the compatibility information and upgrade path for Cisco VSG, Cisco VNMC/PNSC, and Cisco Nexus 1000V versions.

Table 2 Cisco VSG, Cisco VNMC/PNSC, and Cisco Nexus 1000V Compatibility Matrix

VSG Version

Supported VNMC/PNSC Release

Supported Nexus 1000V Release

VSG 1.4

VNMC 2.0

4.2(1)SV2(1.1a)

VSG 2.1.1

VNMC 2.1

4.2(1)SV2(2.1)

VSG 2.1.1

PNSC 3.0.2e

4.2(1)SV2(2.1a)

VSG 2.1.1

PNSC 3.2.1d

4.2(1)SV2(2.2)

VSG 2.1.1

PNSC 3.2.1d

4.2(1)SV2(2.3)

VSG 2.1.2

PNSC 3.2.2b

5.2(1)SV3(1.1)

VSG 2.1.2a

PNSC 3.2.2b

5.2(1)SV3(1.2)

VSG 2.1.2c

PNSC 3.4.1b

5.2(1)SV3(1.3)

VSG 2.1.2c

PNSC 3.4.1b

5.2(1)SV3(1.4)

VSG 2.1.3

PNSC 3.4.1b

5.2(1)SV3(1.4)

VSG 2.1.3

PNSC 3.4.1c

5.2(1)SV3(1.5x)

VSG 2.1.4

PNSC 3.4.1d

5.2(1)SV3(1.6)

VSG 2.1.4

PNSC 3.4.1d

5.2(1)SV3(1.15)

VSG 2.1.4

PNSC 3.4.1d

5.2(1)SV3(2.1)

VSG 2.2.0

PNSC 3.4.2a

5.2(1)SV3(2.1)

VSG 2.2.0

PNSC 3.4.2a

5.2(1)SV3(2.8)

VSG 2.2.1

PNSC 3.4.2b

5.2(1)SV3(3.1)

Table 3 Cisco VSG Upgrade Path

Initial VSG Version

Intermediate State

Final VSG Version

VSG 1(4.1)

NA

VSG 2(2.1)

VSG 2(1.1)

NA

VSG 2(2.1)

VSG 2(1.2)

NA

VSG 2(2.1)

VSG 2(1.2a)

NA

VSG 2(2.1)

VSG 2(1.1)

NA

VSG 2(2.1)

VSG 2(1.2a)

NA

VSG 2(2.1)

VSG 2(1.2c)

NA

VSG 2(2.1)

VSG 2(1.3)

NA

VSG 2(2.1)

VSG 2(1.4)

NA

VSG 2(2.1)

VSG 2(2.0)

NA

VSG 2(2.1)

Table 4 Cisco VNMC/PNSC Upgrade Path

Initial Version

Intermediate State(s)

Final Version

2.0.3

2.1->3.0.2g->3.2.2a->3.4.1d

3.4.2b

2.1

3.0.2->3.2.2a->3.4.1d

3.4.2b

3.0.2

3.2.2a->3.4.1d

3.4.2b

3.2.1d

3.4.1d

3.4.2b

3.2.2b

3.4.1d

3.4.2b

3.4.1b

3.4.1d

3.4.2b

3.4.1c

3.4.1d

3.4.2b

3.4.1d

NA

3.4.2b

3.4.2a

NA

3.4.2b


Note

For detailed information about Upgrading PNSC, see Upgrading Prime Network Services Controller.

Table 5 Cisco Nexus 1000V Upgrade Path

Initial Version

Intermediate State(s)

Final Version

4.2.1.SV1.5.1a

4.2.1.SV2.2.2

5.2(1)SV3(3.1)

4.2.1.SV1.5.2b

4.2.1.SV2.2.2

5.2(1)SV3(3.1)

4.2.1.SV2.1.1a

NA

5.2(1)SV3(3.1)

4.2.1.SV2.2.1a

NA

5.2(1)SV3(3.1)

4.2.1.SV2.2.2

NA

5.2(1)SV3(3.1)

4.2.1.SV2.2.3

NA

5.2(1)SV3(3.1)

5.2(1)SV3(1.1)

NA

5.2(1)SV3(3.1)

5.2(1)SV3(1.2)

NA

5.2(1)SV3(3.1)

5.2(1)SV3(1.3)

NA

5.2(1)SV3(3.1)

5.2(1)SV3(1.4)

NA

5.2(1)SV3(3.1)

5.2(1)SV3(1.5x)

NA

5.2(1)SV3(3.1)

5.2(1)SV3(1.6)

NA

5.2(1)SV3(3.1)

5.2(1)SV3(1.15)

NA

5.2(1)SV3(3.1)

5.2(1)SV3(2.8)

NA

5.2(1)SV3(3.1)


Note

For detailed information about upgrading VSG/PNSC, see Cisco VSG Install and Upgrade Guides.


Note

For information about Cisco Nexus 1000V and VMware ESX/ESXi upgade compatibility, see Cisco Nexus 1000V and VMware ESX/​ESXi Upgrade Utility

Upgrade Procedure for Cisco VSG Release 5.2(1)VSG2(2.0) to Release 5.2(1)VSG2(2.1), Cisco PNSC Release 3.4.2a to Release 3.4.2b and Cisco Nexus 1000V Release 5.2(1)SV3(2.8) to Release 5.2(1)SV3(3.1)

Cisco VSG Release 5.2(1)VSG2(2.0) to 5.2(1)VSG2(2.1) and Cisco Prime NSC 3.4.2a to 3.4.2b Staged Upgrade

Virtual Appliance

Original State

Stage 1: Cisco PNSC Upgrade only (no PAs upgraded)

Stage 2: Cisco VSG Upgrade (ISSU: PA upgrade)

Stage 3: VSM/VEM Upgrade (ISSU: PA upgrade)

Cisco PNSC

Old Cisco Prime NSC 3.4.2a

New Cisco Prime NSC 3.4.2b

New Cisco Prime NSC 3.4.2b

New Cisco Prime NSC 3.4.2b

Cisco VSG

Old 5.2(1)VSG2(2.0)

Old 5.2(1)VSG2(2.0)

New 5.2(1)VSG2(2.1)

New 5.2(1)VSG2(2.1)

VSG PA

Old 2.1(3b)

Old 2.1(3b)

New 2.1(3i)

New 2.1(3i)

VSM

Old 5.2(1)SV3(2.8)

Old 5.2(1)SV3(2.8)

Old 5.2(1)SV3(2.8)

New 5.2(1)SV3(3.1)

VEM

Old 5.2(1)SV3(2.8)

Old 5.2(1)SV3(2.8)

Old 5.2(1)SV3(2.8)

New 5.2(1)SV3(3.1)

VSM PA

3.2(2d)

3.2(2d)

3.2(2d)

3.2(3a)

Supported operations after upgrading to each stage

All operations supported

  • Existing data sessions (offloaded).

  • New data sessions.

  • Allows Cisco Nexus 1000V switch (non-vn-service) operations including non-vn-service port profiles.

  • Short disruption in new data session establishment during the Cisco VSG upgrade.

  • Other operations are fully supported.

  • Full Layer 3 VSG and VM VXLAN support.

  • All operations are supported if all the upgrades including VEMs are successful.

  • Restricted operations (below) apply only if all VEMs are not upgraded

  • Disruption of data traffic during VEM upgrades.

  • Full service chaining is supported.

  • Layer 3 VSG and VM VXLAN support.

  • VSG on VXLAN is supported.

  • Support for Cisco PNSC policy cfg change (assuming silent drops).

  • Support for VSM/VEM vn-service VM operations (shutdown/bring up existing vn-service VMs, bring down net adapters, etc).

  • Support for new vn-service VMs.

  • Support for Vmotion of vn-service firewalled VMs on N1k.

  • Support for vn-service PP operations or modifications (toggles, removal, changing the PP on VSM).

  • Support for VSG failover, VSM failover (vns-agent) (All VSM to Cisco PNSC to VSG control operations are supported).

  • Support for Cisco PNSC policy cfg change (assuming silent drops).

  • Support for VSM/VEM vn-service VM operations (shutdown/bring up existing vn-service VMs, bring down net adapters, etc).

  • Support for new vn-service VMs.

  • Support for Vmotion of vn-service firewalled VMs on N1k.

  • Support for vn-service PP operations or modifications (toggles, removal, changing the PP on VSM).

  • Support for VSG failover, VSM failover (vns-agent). (All VSM to Cisco PNSC to VSG control operations are supported).

  • Support for Cisco PNSC policy cfg change.

  • Support for VSM/VEM vn-service VM operations (shutdown/bring up existing vn-service VMs, bring down net adapters, etc).

  • Support for new vn-service VMs.

  • Support for boot strap of devices (Cisco PNSC, VSM,VSG).

  • Support for Vmotion of vn-service VMs on N1k.

  • Support for vn-service PP operations or modifications (toggles, removal, changing the PP on VSM).

  • Support for N1k switch (non vn-service) operations, including non-vn-service PPs (VSM+VEM ugraded) (All VSM to Cisco PNSC to VSG control operations are supported).


Note

Because we support full ISSU upgrade on both VSG and VSM that involves installing a new PA, you should install the Cisco PNSC first. The new PA may not support the old VNMC.

Upgrading Cisco Prime NSC 3.4.2a to Cisco Prime NSC 3.4.2b

Before You Begin

  • You are logged in to the CLI in EXEC mode.

  • You have backed up the new software files to a remote server and have verified that the backup file was created on the remote server.

  • You must have the Cisco PNSC Release 3.4.2b downloaded.

Procedure
     Command or ActionPurpose
    Step 1nsc# connect local-mgmt  

    Places you in local management mode.

     
    Step 2nsc (local-mgmt)# show version   (Optional)

    Displays the version information for the Cisco PNSC software.

     
    Step 3nsc (local-mgmt)# copy scp://user@example-server-ip/example-dir/filename bootflash:/   (Optional)

    Copies the Cisco PNSC software file to the VM.

     
    Step 4nsc (local-mgmt)# dir bootflash:/  

    Verifies that the desired file is copied in the directory.

     
    Step 5nsc (local-mgmt)# update bootflash:/filename  

    Begins the update of the Cisco PNSC software.

     
    Step 6nsc (local-mgmt)# service status   (Optional)

    Allows you to verify that the server is operating as desired.

     
    Step 7nsc (local-mgmt)# show version   (Optional)

    Allows you to verify that the Cisco PNSC software version is updated.

    Note   

    After you upgrade to Cisco PNSC Release 3.4.2b, you might see the previous version of Cisco PNSC in your browser. To view the upgraded version, clear the browser cache and browsing history in the browser. This note applies to all supported browsers: Internet Explorer, Mozilla Firefox, and Chrome.

    Note   

    For detailed information about Upgrading PNSC, see Upgrading Prime Network Services Controller.

     

    Configuration Example

    The following example shows how to connect to the local-mgmt mode: 

    nsc# connect local-mgmt
Cisco Prime Network Services Controller
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

    The following example shows how to display version information for the Cisco PNSC: 

    nsc(local-mgmt)# show version

Name Package Version GUI
---- ------- ------- ----
core Base System 3.4(2a) 3.4(2a) service-reg 
Service Registry 3.4(2a) 3.4(2a) policy-mgr 
Policy Manager 3.4(2a) 3.4(2a) resource-mgr 
Resource Manager 3.4(2a) 3.4(2a) vm-mgr 
VM manager 3.4(2a) none vsm-service 
VSM Service 3.4(2a) none cloudprovider-mgr 
Cloud Provider Mgr 3.4(2a) none 
localhost(local-mgmt)#

    The following example shows how to copy the Cisco PNSC software to the VM: 

    nsc(local-mgmt)# copy scp://<user@example-server-ip>/example1-dir/nsc.3.4.2b.bin bootflash:/
Enter password: 
100%  143MB  11.9MB/s   00:12

    The following example shows how to see the directory information for Cisco PNSC: 

    nsc(local-mgmt)# dir bootflash:/
 
    1.1G Dec 05 00:57 nsc.3.4.2b.bin

Usage for bootflash://

             6359716 KB used
            10889320 KB free
            18187836 KB total

    The following example shows how to start the update for the Cisco PNSC: 

    nsc(local-mgmt)# update bootflash:/nsc.3.4.2b.bin
It is recommended that you perform a full-state backup before updating any VNMC component.  Press enter to continue or Ctrl-c to exit.

    The following example shows how to display the updated version for the Cisco PNSC: 

    nsc(local-mgmt)# show version

Name                Package             Version        GUI
---- ------- ------- ----
core                Base System         3.4.2b        3.4.2b
service-reg         Service Registry    3.4.2b        3.4.2b
policy-mgr          Policy Manager      3.4.2b        3.4.2b
resource-mgr        Resource Manager    3.4.2b        3.4.2b
vm-mgr              VM manager          3.4.2b        none
cloudprovider-mgr   Cloud Provider Mgr  3.4.2b        none

    Upgrading Cisco VSG from Release 5.2(1)VSG2(2.0) to 5.2(1)VSG2(2.1) Using a Binary File

    Enter the commands on all Cisco VSG nodes on your network.

    Before You Begin

    • You are logged in to the CLI in EXEC mode.

    • You have copied the new system image, kickstart image and the Cisco VSG policy agent image into the bootflash file system using the following commands: 
      vsg# copy scp://user@scpserver.cisco.com/downloads/nexus-1000v-kickstart.5.2.1.VSG2.2.1.bin bootflash:nexus-1000v-kickstart.5.2.1.VSG2.2.1.bin

vsg# copy scp://user@scpserver.cisco.com/downloads/nexus-1000v.5.2.1.VSG2.2.1.bin bootflash:nexus-1000v.5.2.1.VSG2.2.1.bin

vsg# copy scp://user@scpserver.cisco.com/downloads/nsc-vsgpa.2.1.3i.bin
bootflash:nsc-vsgpa.2.1.3i.bin

    • You have confirmed that the system is in high availability (HA) mode for an HA upgrade using the show system redundancy status command.

    Procedure
       Command or ActionPurpose
      Step 1 configure terminal
       

      Enters global configuration mode.

       
      Step 2 install all kickstart bootflash:nexus-1000v-kickstart.5.2.1.VSG2.2.1.bin system bootflash:nexus-1000v.5.2.1.VSG2.2.1.bin nscpa bootflash:nsc-vsgpa.2.1.3i.bin
       

      Installs the kickstart image, system image, and policy agent (PA) image.

      Note   

      If you do not have a policy agent installed on the Cisco VSG before the install all command is executed, the PA will not be upgraded (installed) with the image. Make sure that the current version of policy agent is installed before you begin the upgrade process.

       
      Step 3show nsc-pa status
       

      Verifies that the new PA is installed and the upgrade was successful.

      Note   

      You must have an existing PA installed before upgrading the PA using the install all command.

       
      Step 4copy running-config startup-config
       

      Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

       

      Configuration Example

      The following example shows how to upgrade Cisco VSG Release 5.2(1)VSG2(2.0) to Release 5.2(1)VSG2(2.1): 

      vsg # configure terminal
vsg (config)# install all kickstart bootflash:nexus-1000v-kickstart.5.2.1.VSG2.2.1.bin system bootflash:nexus-1000v.5.2.1.VSG2.2.1.bin nscpa bootflash:nsc-vsgpa.2.1.3i.bin
vsg (config)# show nsc-pa status
NNSC Policy-Agent status is - Installed Successfully. Version 2.1(3i)-vsg
vsg(config)# copy running-config startup-config

      Upgrading Cisco VSG from Release 5.2(1)VSG2(2.0) to 5.2(1)VSG2(2.1) Using an ISO File

      Enter the commands on all Cisco VSG nodes on your network.

      Before You Begin

      • You are logged in to the CLI in EXEC mode.

      • You have copied the new ISO image into the bootflash file system using the following commands: 
        vsg# copy scp://user@scpserver.cisco.com/downloads/nexus-1000v.5.2.1.VSG2.2.1.iso bootflash:nexus-1000v.5.2.1.VSG2.2.1.iso

      • You have confirmed that the system is in high availability (HA) mode.

      • Cisco VSG upgrade using ISO file supported on Cisco Nexus 1000V Release 5.2(1)SV3(1.1) and later.

      Procedure
         Command or ActionPurpose
        Step 1 configure terminal
         

        Enters global configuration mode.

         
        Step 2 install all iso bootflash:nexus-1000v.5.2.1.VSG2.2.1.iso
         

        Installs the system image.

         
        Step 3show nsc-pa status
         

        Verifies that the new PA is installed and the upgrade was successful.

         
        Step 4copy running-config startup-config
         

        Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

         

        Configuration Example

        The following example shows how to upgrade Cisco VSG Release 5.2(1)VSG2(2.0) to Release 5.2(1)VSG2(2.1) using an ISO file: 

        vsg # configure terminal
vsg (config)# install all iso bootflash:nexus-1000v.5.2.1.VSG2.2.1.iso
vsg (config)# show nsc-pa status
NNSC Policy-Agent status is - Installed Successfully. Version 2.1(3i)-vsg
vsg(config)# copy running-config startup-config

        Upgrading VSMs

        Upgrade Procedures

        The following table lists the upgrade steps.


        Note
        Ensure that you have changed the VSM mode to advanced, before upgrading VSM. VSG services are not available in the essential mode.
        Table 6 Upgrade Paths from Cisco Nexus 1000V Releases

        If you are running this configuration

        Follow these steps

        Release 4.0(4)SV1(1), 4.0(4)SV1(2), 4.2(1)SV1(4), 4.2(1)SV1(5.1), and 4.2(1)SV1(5.2)

        		Direct upgrades from these releases are not supported.

        Releases 4.0(4)SV1(3x) Series

        1. Upgrading from Releases 4.0(4)SV1(3, 3a, 3b, 3c, 3d) to Release 4.2(1)SV1(4b)

        2. Upgrade from Releases 4.2(1)SV2(1.1) and later releases to the current release

        Release 4.2(1)SV1(4x) Series with a vSphere release 4.0 Update 1 or later

        1. Upgrading from VMware Release 4.0 to VMwrae Release 5.0 or later.

        2. Upgrading VSMs from releases 4.2(1)SV1(4x) to 4.2(1)SV2(1.1) or later.

        3. Upgarding VEMs from releases 4.2(1)SV1(4x) to 4.2(1)SV2(1.1) or later.

        4. Upgrading VSMs from releases 4.2(1)SV2(1.1) or later to current release.

        5. Upgrading VEMs from releases 4.2(1)SV2(1.1) or later to current release.

        Release 4.2(1)SV1(4x) Series with a vSphere release 4.1 GA, patches, or updates

        1. Upgrading from VMware Release 4.1 to VMwrae Release 5.0 or later.

        2. Upgrading VSMs from releases 4.2(1)SV1(4x) to 4.2(1)SV2(1.1) or later.

        3. Upgarding VEMs from releases 4.2(1)SV1(4x) to 4.2(1)SV2(1.1) or later.

        4. Upgrading VSMs from releases 4.2(1)SV2(1.1) or later to current release.

        5. Upgrading VEMs from releases 4.2(1)SV2(1.1) or later to current release.

        The following table lists the upgrade steps when upgrading from Release 4.2(1)SV1(5x) and later releases to the current release.

        Table 7 Upgrade Paths from Releases 4.2(1)SV1(5x) and Later Releases

        If you are running this configuration

        Follow these steps

        With vSphere 5.0 GA, patches, or updates.

        1. Upgrading VSMs from releases 4.2(1)SV1(5.1x) to 4.2(1)SV2(1.1) or later.

        2. Upgarding VEMs from releases 4.2(1)SV1(5.1x) to 4.2(1)SV2(1.1) or later.

        3. Upgrading VSMs from releases 4.2(1)SV2(1.1) or later to current release.

        4. Upgrading VEMs from releases 4.2(1)SV2(1.1) or later to current release.

        Software Images

        The software image install procedure is dependent on the following factors:

        • Software images—The kickstart and system image files reside in directories or folders that you can access from the Cisco Nexus 1000V software prompt.

        • Image version—Each image file has a version.

        • Disk—The bootflash: resides on the VSM.

        In-Service Software Upgrades on Systems with Dual VSMs

        The Cisco Nexus 1000V software supports in-service software upgrades (ISSUs) for systems with dual VSMs. An ISSU can update the software images on your switch without disrupting data traffic. Only control traffic is disrupted. If an ISSU causes a disruption of data traffic, the Cisco Nexus 1000V software warns you before proceeding so that you can stop the upgrade and reschedule it to a time that minimizes the impact on your network.


        Note

        On systems with dual VSMs, you should have access to the console of both VSMs to maintain connectivity when the switchover occurs during upgrades. If you are performing the upgrade over Secure Shell (SSH) or Telnet, the connection will drop when the system switchover occurs, and you must reestablish the connection.

        An ISSU updates the following images:

        • Kickstart image

        • System image

        • VEM images

        • Policy Agent image

        All of the following processes are initiated automatically by the upgrade process after the network administrator enters the install all command.

        ISSU Process for the Cisco Nexus 1000V

        The following figure shows the ISSU process.

        Figure 1. ISSU Process



        ISSU VSM Switchover

        The following figure provides an example of the VSM status before and after an ISSU switchover.

        Figure 2. Example of an ISSU VSM Switchover



        ISSU Command Attributes

        Support

        The install all command supports an in-service software upgrade (ISSU) on dual VSMs in an HA environment and performs the following actions:

        • Determines whether the upgrade is disruptive and asks if you want to continue.

        • Copies the kickstart and system images to the standby VSM.

        • Sets the kickstart and system boot variables.

        • Reloads the standby VSM with the new Cisco Nexus 1000V software.

        • Causes the active VSM to reload when the switchover occurs.

        Benefits

        The install all command provides the following benefits:

        • You can upgrade the VSM by using the install all command.

        • You can receive descriptive information on the intended changes to your system before you continue with the installation.

        • You have the option to cancel the command. Once the effects of the command are presented, you can continue or cancel when you see this question (the default is no):

          Do you want to continue (y/n) [n]: y

        • You can upgrade the VSM using the least disruptive procedure.

        • You can see the progress of this command on the console, Telnet, and SSH screens:

          • After a switchover process, you can see the progress from both the VSMs.

          • Before a switchover process, you can see the progress only from the active VSM.

        • The install all command automatically checks the image integrity, which includes the running kickstart and system images.

        • The install all command performs a platform validity check to verify that a wrong image is not used.

        • The Ctrl-C escape sequence gracefully ends the install all command. The command sequence completes the update step in progress and returns to the switch prompt. (Other upgrade steps cannot be ended by using Ctrl-C.)

        • After running the install all command, if any step in the sequence fails, the command completes the step in progress and ends.

        Upgrading VSMs from Releases 4.2(1)SV2(1.1x), 4.2(1)SV2(2.1x), 5.2(1)SV3(1.x), 5.2(1)SV3(x) to 5.2(1)SV3(3.x)

        Procedure
          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:
          • If the following output is displayed, the Cisco VSG is configured in the deployment. You must follow the upgrade procedure in the “Complete Upgrade Procedure” section in Chapter 7, “Upgrading the Cisco Virtual Security Gateway and Cisco Virtual Network Management Center” of the Cisco Virtual Security Gateway and Cisco Virtual Network Management Center Installation and Upgrade Guide. 
            switch# show nsc-pa status 
NSC Policy-Agent status is - Installed Successfully. Version 3.2(3a)-vsm
switch#
          • If the following output is displayed, continue to Step 13. 
            switch# show nsc-pa status 
NSC Policy-Agent status is - Not Installed
switch#
          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)#

          Upgrading VEMs

          VEM Upgrade Procedure

          VEM upgrades fall into three types:

          • An upgrade of stateful ESXi host, without a migration from ESX (with a console OS) to ESXi. This upgrade type is described further in this section.

          • An upgrade of a stateless ESXi host. This involves installing a new image on the host by updating the image profile and rebooting the host. For detailed information about stateless ESXi host upgrade, see Cisco Nexus 1000V Installation and Upgrade Guide.

          An upgrade of stateful ESXi host without a migration from ESX (which has a console OS) to ESXi falls into two separate workflows.

          1. Upgrade the VEM alone, while keeping the ESXi version intact. The first figure shows this flow.

          2. Upgrade the ESX/ESXi without a change of the Cisco Nexus 1000V version.

          If you are using VUM, set up a host patch baseline with the VEM’s offline bundle. Then follow Upgrading the VEMs Using VMware Update Manager from Release 4.2(1)SV1(5x) and Later Releases to the Current Release.

          If you are upgrading from the command line, see Upgrading the VEMs Manually from Release 4.2(1)SV1(5x) and Later Releases to the Current Release.

          • If you are using VUM version 5.0 or later, use the following method (independent of whether the VEM version is being changed as well):

            • If you are upgrading the ESXi host to a new update within a release, use a host upgrade baseline. For example, vSphere 5.0 GA to 5.0 U1.

            • You can upgrade the ESXi version and VEM version simultaneously if you are using VUM 5.0 Update 1 or later. VUM 5.0 GA does not support a combined upgrade.

          VEM Upgrade Methods from Release 4.2(1)SV1(5x), or Release 4.2(1)SV2(1.1x) to the Current Release

          There are two methods for upgrading the VEMs.

          Upgrading the VEMs Using VMware Update Manager from Release 4.2(1)SV1(5x) and Later Releases to the Current Release

          Procedure
            Step 1   switch# show vmware vem upgrade status

            Display the current configuration.

            Note   

            The minimum release of Cisco Nexus 1000V for VMware ESXi 5.0.0 hosts is Release 4.2(1)SV1(5).

            Step 2   switch# vmware vem upgrade notify

            Coordinate with and notify the server administrator of the VEM upgrade process.

            Step 3   switch# show vmware vem upgrade status

            Verify that the upgrade notification was sent.

            Note   

            Verify that the Upgrade Status contains the highlighted text. If the text is not present, check the Upgrade Error line and consult the Cisco Nexus 1000V Troubleshooting Guide.

            Step 4   switch# show vmware vem upgrade status

            Verify that the server administrator has accepted the upgrade in the vCenter. For more information about how the server administrator accepts the VEM upgrade, see Accepting the VEM Upgrade. Coordinate the notification acceptance with the server administrator. After the server administrator accepts the upgrade, proceed with the VEM upgrade.

            Note   

            Verify that the Upgrade Status contains the highlighted text. If the text is not present, check the Upgrade Error line and consult the Cisco Nexus 1000V Troubleshooting Guide.

            Step 5   Initiate the VUM upgrade process with the following commands.
            Note   

            Before entering the following commands, communicate with the server administrator to confirm that the VUM process is operational.

            The vCenter Server locks the DVS and triggers VUM to upgrade the VEMs.

            1. switch# vmware vem upgrade proceed
            2. switch# show vmware vem upgrade status
            Note   

            The DVS bundle ID is updated and is highlighted.

            If the ESXi host is using ESXi 4.1.0 or a later release and your DRS settings are enabled to allow it, VUM automatically VMotions the VMs from the host to another host in the cluster and places the ESXi in maintenance mode to upgrade the VEM. This process is continued for other hosts in the DRS cluster until all the hosts are upgraded in the cluster. For details about DRS settings required and vMotion of VMs, visit the VMware documentation related to Creating a DRS Cluster.

            Step 6   switch# show vmware vem upgrade status

            Check for the upgrade complete status.

            Step 7   Clear the VEM upgrade status after the upgrade process is complete with the following commands.
            1. switch# vmware vem upgrade complete
            2. switch# show vmware vem upgrade status
            Step 8   switch# show module

            Verify that the upgrade process is complete.

            The upgrade is complete.

            The following example shows how to upgrade VEMs using VUM.

            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. 

            switch# show vmware vem upgrade status 

Upgrade VIBs: System VEM Image
Upgrade Status: 
Upgrade Notification Sent Time: 
Upgrade Status Time(vCenter):  
Upgrade Start Time: 
Upgrade End Time(vCenter): 
Upgrade Error: 
Upgrade Bundle ID:
    VSM: VEM500-201401164100-BG
    DVS: VEM410-201301152101-BG
switch# 
switch# vmware vem upgrade notify 
Warning: 
Please ensure the hosts are running compatible ESX versions for the upgrade. Refer to corresponding
"Cisco Nexus 1000V and VMware Compatibility Information" guide.
switch# show vmware vem upgrade status 

Upgrade VIBs: System VEM Image
Upgrade Status: Upgrade Availability Notified in vCenter
Upgrade Notification Sent Time: Tue Jul 27 10:03:24 2014
Upgrade Status Time(vCenter):  
Upgrade Start Time: 
Upgrade End Time(vCenter): 
Upgrade Error: 
Upgrade Bundle ID:
    VSM:  VEM500-201401164100-BG
    DVS:  VEM410-201301152101-BG
switch#
switch# show vmware vem upgrade status 

Upgrade VIBs: System VEM Image
Upgrade Status: Upgrade Accepted by vCenter Admin
Upgrade Notification Sent Time: Tue Jul 27 10:03:24 2014
Upgrade Status Time(vCenter): Tue Jul 27 02:06:53 2014
Upgrade Start Time: 
Upgrade End Time(vCenter): 
Upgrade Error: 
Upgrade Bundle ID:
    VSM: VEM500-201401164100-BG
    DVS: VEM410-201301152101-BG
switch#
switch# vmware vem upgrade proceed 
switch# show vmware vem upgrade status 

Upgrade VIBs: System VEM Image
Upgrade Status: Upgrade In Progress in vCenter
Upgrade Notification Sent Time: Tue Jul 27 10:03:24 2014
Upgrade Status Time(vCenter) : Tue Jul 27 02:06:53 2014 
Upgrade Start Time: : Tue Jul 27 10:09:08 2014
Upgrade End Time(vCenter): 
Upgrade Error: 
Upgrade Bundle ID:
    VSM: VEM500-201401164100-BG
    DVS: VEM500-201401164100-BG
switch#
switch# show vmware vem upgrade status 

Upgrade VIBs: System VEM Image
Upgrade Status: Upgrade Complete in vCenter
Upgrade Notification Sent Time: : Tue Jul 27 10:03:24 2014
Upgrade Status Time(vCenter): : Tue Jul 27 02:06:53 2014  
Upgrade Start Time: : Tue Jul 27 10:09:08 2013
Upgrade End Time(vCenter): : Tue Jul 27 10:09:08 2014
Upgrade Error: 
Upgrade Bundle ID:
    VSM: VEM500-201401164100-BG
    DVS: VEM500-201401164100-BG
switch#
switch# vmware vem upgrade complete 
switch# show vmware vem upgrade status 


Upgrade VIBs: System VEM Image
Upgrade Status: 
Upgrade Notification Sent Time: 
Upgrade Status Time(vCenter):  
Upgrade Start Time: 
Upgrade End Time(vCenter): 
Upgrade Error: 
Upgrade Bundle ID:
    VSM: VEM500-201401164100-BG
    DVS: VEM500-201401164100-BG
switch#
switch# show module 
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
4    248    Virtual Ethernet Module           NA                  ok

Mod  Sw                  Hw      
---  ------------------  ------------------------------------------------  
1    5.2(1)SV3(1.2)      0.0                                              
2    5.2(1)SV3(1.2)      0.0                                              
3    5.2(1)SV3(1.2)      VMware ESXi 5.0.0 Releasebuild-469512 (3.0)      
4    5.2(1)SV3(1.2)      VMware ESXi 5.0.0 Releasebuild-623860 (3.0)      

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
4    02-00-0c-00-04-00 to 02-00-0c-00-04-80  NA

Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    10.104.249.171   NA                                    NA
2    10.104.249.171   NA                                    NA
3    10.104.249.172   7d41e666-b58a-11e0-bd1d-30e4dbc299c0  10.104.249.172
4    10.104.249.173   17d79824-b593-11e0-bd1d-30e4dbc29a0e  10.104.249.173

* this terminal session 
switch#

            Note

            The lines with the bold characters in the preceding example display that all VEMs are upgraded to the current release.

            Upgrading the VEMs Manually from Release 4.2(1)SV1(5x) and Later Releases to the Current Release

            Before You Begin

            Note

            If VUM is installed, it should be disabled.

            To manually install or upgrade the Cisco Nexus 1000V VEM on an ESXi host, follow the steps in Upgrading the VEM Software Using the vCLI.

            To upgrade the VEMs manually, perform the following steps as network administrator:


            Note

            This procedure is performed by the network administrator. Before proceeding with the upgrade, make sure that the VMs are powered off if you are not running the required patch level.

            Procedure
              Step 1   switch# vmware vem upgrade notify

              Coordinate with and notify the server administrator of the VEM upgrade process.

              Step 2   switch# show vmware vem upgrade status

              Verify that the upgrade notification was sent.

              Step 3   switch# show vmware vem upgrade status

              Verify that the server administrator has accepted the upgrade in vCenter Server. For details about the server administrator accepting the VEM upgrade, see Accepting the VEM Upgrade. After the server administrator accepts the upgrade, proceed with the VEM upgrade.

              Step 4   Perform one of the following tasks:

              • If the ESXi host is not hosting the VSM, proceed to Step 5.

              • If the ESXi host is hosting the VSM, coordinate with the server administrator to migrate the VSM to a host that is not being upgraded. Proceed to Step 5.

              Step 5   switch# vmware vem upgrade proceed

              Initiate the Cisco Nexus 1000V Bundle ID upgrade process.

              Note   

              If VUM is enabled in the vCenter environment, disable it before entering the vmware vem upgrade proceed command to prevent the new VIBs from being pushed to all the hosts.

              Enter the vmware vem upgrade proceed command so that the Cisco Nexus 1000V Bundle ID on the vCenter Server gets updated. If VUM is enabled and you do not update the Bundle ID, an incorrect VIB version is pushed to the VEM when you next add the ESXi to the VSM.

              Note   

              If VUM is not installed, the “The object or item referred to could not be found” error appears in the vCenter Server task bar. You can ignore this error message.

              Step 6   switch# show vmware vem upgrade status

              Check for the upgrade complete status.

              Step 7   Coordinate with and wait until the server administrator upgrades all ESXi host VEMs with the new VEM software release and informs you that the upgrade process is complete.

              The server administrator performs the manual upgrade by using the vihostupdate command or the esxcli command. For more information, see Upgrading the VEM Software Using the vCLI.

              Step 8   switch# vmware vem upgrade complete

              Clear the VEM upgrade status after the upgrade process is complete.

              Step 9   switch# show vmware vem upgrade status

              Check the upgrade status once again.

              Step 10   switch# show module
              Verify that the upgrade process is complete.
              Note   

              The line with the bold characters in the preceding example display that all VEMs are upgraded to the current release.

              The upgrade is complete.

              The following example shows how to upgrade VEMs manually.

              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. 

              switch# show vmware vem upgrade status 

Upgrade VIBs: System VEM Image
Upgrade Status: 
Upgrade Notification Sent Time: 
Upgrade Status Time(vCenter):  
Upgrade Start Time: 
Upgrade End Time(vCenter): 
Upgrade Error: 
Upgrade Bundle ID:
    VSM: VEM500-201401164100-BG
    DVS: VEM410-201401152101-BG
switch# 
switch# vmware vem upgrade notify 
Warning: 
Please ensure the hosts are running compatible ESX versions for the upgrade. Refer to corresponding
"Cisco Nexus 1000V and VMware Compatibility Information" guide.

switch# show vmware vem upgrade status 

Upgrade VIBs: System VEM Image
Upgrade Status: Upgrade Accepted by vCenter Admin
Upgrade Notification Sent Time: Tue Jul 28 10:03:24 2014
Upgrade Status Time(vCenter): Tue Jul 28 02:06:53 2014 
Upgrade Start Time: 
Upgrade End Time(vCenter): 
Upgrade Error: 
Upgrade Bundle ID:
    VSM: VEM500-201401164100-BG
    DVS: VEM410-201401152101-BG

switch# 
switch# vmware vem upgrade proceed
switch# show vmware vem upgrade status 

Upgrade VIBs: System VEM Image
Upgrade Status: Upgrade In Progress in vCenter
Upgrade Notification Sent Time: Tue Jul 28 10:03:24 2014
Upgrade Status Time(vCenter): Tue Jul 28 02:06:53 2014 
Upgrade Start Time: Tue Jul 28 10:09:08 2014
Upgrade End Time(vCenter): 
Upgrade Error: 
Upgrade Bundle ID:
    VSM: VEM500-201401164100-BG
    DVS: VEM500-201401164100-BG

switch# show vmware vem upgrade status 
Upgrade VIBs: System VEM Image
Upgrade Status: Upgrade Complete in vCenter
Upgrade Notification Sent Time: Tue Jul 28 10:03:24 2014
Upgrade Status Time(vCenter): Tue Jul 28 02:06:53 2014 
Upgrade Start Time: Tue Jul 28 10:09:08 2014
Upgrade End Time(vCenter): 
Upgrade Error
Upgrade Bundle ID:
    VSM: VEM500-201401164100-BG
    DVS: VEM500-201401164100-BG

switch#
switch# vmware vem upgrade complete 
switch# show vmware vem upgrade status 

Upgrade VIBs: System VEM Image
Upgrade Status:
Upgrade Notification Sent Time: 
Upgrade Status Time(vCenter): 
Upgrade Start Time: 
Upgrade End Time(vCenter): 
Upgrade Error
Upgrade Bundle ID:
    VSM: VEM500-201401164100-BG
    DVS: VEM500-201401164100-BG

switch#
switch# show module 
Mod  Ports  Module-Type                       Model               Status
---  -----  --------------------------------  ------------------  ------------
1    0      Virtual Supervisor Module         Nexus1000V          active *
2    0      Virtual Supervisor Module         Nexus1000V          ha-standby
3    332    Virtual Ethernet Module           NA                  ok
6    248    Virtual Ethernet Module           NA                  ok


Mod  Sw                  Hw      
---  ------------------  ------------------------------------------------  
1    5.2(1)SV3(1.2)  0.0                                              
2    5.2(1)SV3(1.2)  0.0                                              
3    5.2(1)SV3(1.2)      VMware ESXi 5.0.0 Releasebuild-843203 (3.0)      
6    5.2(1)SV3(1.2)      VMware ESXi 5.1.0 Releasebuild-843203 (3.0) 

    
Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    10.105.232.25    NA                                    NA
2    10.105.232.25    NA                                    NA
3    10.105.232.72    e6c1a563-bc9e-11e0-bd1d-30e4dbc2baba  10.105.232.72
6    10.105.232.70    ecebdf42-bc0e-11e0-bd1d-30e4dbc2b892  10.105.232.70

* this terminal session 
switch#

              Accepting the VEM Upgrade

              Before You Begin

              • The network and server administrators must coordinate the upgrade procedure with each other.

              • You have received a notification in the vCenter Server that a VEM software upgrade is available.

              Procedure
                Step 1   In the vCenter Server, choose Inventory > Networking.
                Step 2   Click the vSphere Client DVS Summary tab to check for the availability of a software upgrade.
                Figure 3. vSphere Client DVS Summary Tab



                Step 3   Click Apply upgrade.

                The network administrator is notified that you are ready to apply the upgrade to the VEMs.

                Upgrading the VEM Software Using the vCLI

                You can upgrade the VEM software by using the vCLI.

                Before You Begin

                • If you are using vCLI, do the following:

                  • You have downloaded and installed the VMware vCLI. For information about installing the vCLI, see the VMware vCLI documentation.

                  • You are logged in to the remote host where the vCLI is installed.


                    Note

                    The vSphere command-line interface (vCLI) command set allows you to enter common system administration commands against ESXi systems from any machine with network access to those systems. You can also enter most vCLI commands against a vCenter Server system and target any ESXi system that the vCenter Server system manages. vCLI commands are especially useful for ESXi hosts because ESXi does not include a service console.

                • Check Cisco Nexus 1000V and VMware Compatibility Information for compatible versions.

                • You have already copied the VEM software installation file to the /tmp directory. Do not copy the files to the root (/) folder.

                • You know the name of the VEM software file to be installed.

                Procedure
                  Step 1   [root@serialport -]# cd tmp

                  Go to the directory where the new VEM software was copied.

                  Step 2   Determine the upgrade method that you want to use and enter the appropriate command.
                  • vihostupdate

                    Installs the ESXi and VEM software simultaneously if you are using the vCLI.

                  Step 3   For ESXi 5.5 or later hosts, enter the appropriate commands as they apply to you.
                  1. ~ # esxcli software vib install -d /absolute-path/VEM_bundle
                  2. ~ # esxcli software vib install -v /absolute-path/vib_file
                  Note   

                  You must specify the absolute path to the VEM_bundle and vib_file files. The absolute path is the path that starts at the root of the file system such as /tmp/vib_file.

                  Step 4   Display values with which to compare to Cisco Nexus 1000V and VMware Compatibility Information by typing the following commands.
                  1. [root@serialport tmp]# vmware -v
                  2. root@serialport tmp]# # esxupdate query
                  3. [root@host212 ~]# . ~ # vem status -v
                  4. [root@host212 ~]# vemcmd show version
                  Step 5   switch# show module

                  Display that the VEMs were upgraded by entering the command on the VSM.

                  If the upgrade was successful, the installation procedure is complete.

                  The following example shows how to upgrade the VEM software using the vCLI.

                  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. 

                  [root@serialport -]# cd tmp
[root@serialport tmp]# 
esxupdate -b [VMware offline update bundle] update
~ # esxcli software vib install -d /tmp/VEM500-201401164100-BG-zip
Installation Result
   Message: Operation finished successfully.
   Reboot Required: false
   VIBs Installed: cross_cisco-vem-v170-5.2.1.3.1.2.0-3.0.1
   VIBs Removed: 
   VIBs Skipped: 
~ #

~ # esxcli software vib install -v /tmp/cross_cisco-vem-v170-5.2.1.3.1.2.0-3.0.1.vib
Installation Result
   Message: Operation finished successfully.
   Reboot Required: false
   VIBs Installed: Cisco_bootbank_cisco-vem-v170-esx_5.2.1.3.1.2.0-3.0.1
   VIBs Removed: 
   VIBs Skipped: 
~ #
[root@serialport tmp]# vmware -v
VMware ESXi 5.0.0 build-843203
root@serialport tmp]# # esxupdate query
------Bulletin ID------- -----Installed----- --------------Summary---------------
VEM500-201401164100 2014-01-27T08:18:22 Cisco Nexus 1000V 5.2(1)SV3(1.2)


[root@host212 ~]# . ~ # vem status -v
Package vssnet-esxmn-release
Version 5.2.1.3.1.2.0-3.0.1
Build 1
Date Mon Jul 27 04:56:14 PDT 2014
 
VEM modules are loaded
Switch Name      Num Ports   Used Ports  Configured Ports  MTU     Uplinks   
vSwitch0         128         4           128               1500    vmnic4    
DVS Name         Num Ports   Used Ports  Configured Ports  MTU     Uplinks   
p-1              256         19          256               1500    vmnic7,vmnic6,vmnic3,vmnic2,vmnic1,vmnic0
VEM Agent (vemdpa) is running
~ #


[root@host212 ~]# vemcmd show version
Running esx version -1024429 x86_64
VEM Version: 5.2.1.3.1.2.0-3.0.1
VSM Version: 5.2(1)SV3(1.2)
System Version: VMware ESXi 5.0.0 Releasebuild-1024429
ESX Version Update Level: 2

~ #
switch# show module 
Mod  Ports  Module-Type                       Model               Status
---  -----  --------------------------------  ------------------  ------------
1    0      Virtual Supervisor Module         Nexus1000V          active *
2    0      Virtual Supervisor Module         Nexus1000V          ha-standby
3    332    Virtual Ethernet Module           NA                  ok
6    248    Virtual Ethernet Module           NA                  ok

Mod  Sw                  Hw      
---  ------------------  ------------------------------------------------  
1    5.2(1)SV3(1.2)  0.0                                              
2    5.2(1)SV3(1.2)  0.0                                              
3    5.2(1)SV3(1.2)      VMware ESXi 5.0.0 Releasebuild-843203 (3.0)      
6    5.2(1)SV3(1.2)      VMware ESXi 5.1.0 Releasebuild-843203 (3.0)     


Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    10.105.232.25    NA                                    NA
2    10.105.232.25    NA                                    NA
3    10.105.232.72    e6c1a563-bc9e-11e0-bd1d-30e4dbc2baba  10.105.232.72
6    10.105.232.70    ecebdf42-bc0e-11e0-bd1d-30e4dbc2b892  10.105.232.70

switch#

                  Note

                  The highlighted text in the previous command output confirms that the upgrade was successful.