Visitors

HOW TO: Upgrade Cisco Nexus 1000V VSM and VEM

  1. Download Cisco Nexus 1000V upgrade code from Cisco web site:
    These instructions will be for Cisco Nexus 1000V Release 4.2(1)SV1(5.2b).

  2. Extract the following files from Nexus1000v.4.2.1.SV1.5.2b.zip:
    • VSM – Nexus1000v.4.2.1.SV1.5.2b.zipVSMUpgrade:
      • nexus-1000v.4.2.1.SV1.5.2b.bin – system software image;
      • nexus-1000v-kickstart.4.2.1.SV1.5.2b.bin – kickstart software image
    • VEM – Nexus1000v.4.2.1.SV1.5.2b.zipVEM:
      • VMware vSphere ESX 4.1 – VEM410-20121212147401.zip
      • VMware vSphere ESX 5.0 – VEM500-201212147102-BG-release.zip
      • VMware vSphere ESX 5.1 – VEM510-201212147105-BG-release.zip
  3. Cisco Nexus 1000V VEM upgrade:
    1. Open vCenter Update Manager, Admin View, Patch Repository, Import Patches
    2. Browse for VEM upgrade offline bundle that we extracted from the archive in Step 2, click Next
      Upgrade Cisco Nexus 1000V VEM - 1
    3. Confirm the upgrade version and click Finish.
      Upgrade Cisco Nexus 1000V VEM - 2
      The patch has been added to the Patch Repository.
    4. Click on Baselines and Groups tab and in the Baselines area click on Create…
    5. Provide a name for the new baseline, select Host Extension, click Next
      Upgrade Cisco Nexus 1000V VEM - 3
    6. Select Cisco 1000V VEM and add it to the Baseline, click Next
      Upgrade Cisco Nexus 1000V VEM - 4
    7. Confirm Host Extension version and click Finish.
      Upgrade Cisco Nexus 1000V VEM - 5
    8. Assign newly created Baseline to host/cluster/Data Center and install VEM upgrade following standard host remediation procedure.
    9. Alternatively, add this Baseline to Baseline Group, similar to this:
      Upgrade Cisco Nexus 1000V VEM - 6
  4. Cisco Nexus 1000V VSM upgrade:
    1. Login to the active VSM;
    2. Save the running configuration to the startup configuration.
       1000V-01# copy running-config startup-config
    3. Ensure that there is enough space for the image file(s);
      1000V-01# dir bootflash:
      
      <The list of files in bootflash>
      
      Usage for bootflash://sup-local
      672698368 bytes used
      922177536 bytes free
      1594875904 bytes total
      1000V-01# dir bootflash://sup-standby/
      
      <The list of files in bootflash>
      
      Usage for bootflash://sup-standby
      500957184 bytes used
      1093918720 bytes free
      1594875904 bytes total
    4. Copy the Cisco Nexus 1000V kickstart and system images to the active VSM. You can use ftp:, tftp:, scp:, or sftp:.
      1000V-01# copy scp://user@server/folder/nexus-1000v-kickstart.4.2.1.SV1.5.2b.bin bootflash: nexus-1000v-kickstart.4.2.1.SV1.5.2b.bin
      1000V-01# copy scp://user@server/folder/nexus-1000v.4.2.1.SV1.5.2b.bin bootflash: nexus-1000v.4.2.1.SV1.5.2b.bin
    5. Run “show install all impact” command to check for any compatibility issues;
      1000V-01# show install all impact kickstart bootflash:nexus-1000v-kickstart.4.2.1.SV1.5.2b.bin system bootflash:nexus-1000v.4.2.1.SV1.5.2b.bin
      
      Verifying image bootflash:/nexus-1000v-kickstart.4.2.1.SV1.5.2b.bin for boot variable "kickstart".
      [####################] 100% -- SUCCESS
      
      Verifying image bootflash:/nexus-1000v.4.2.1.SV1.5.2b.bin for boot variable "system".
      [####################] 100% -- SUCCESS
      
      Verifying image type.
      [###########         ]  50%
      [####################] 100% -- SUCCESS
      
      Extracting "system" version from image bootflash:/nexus-1000v.4.2.1.SV1.5.2b.bin.
      [####################] 100% -- SUCCESS
      
      Extracting "kickstart" version from image bootflash:/nexus-1000v-kickstart.4.2.1.SV1.5.2b.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          4.2(1)SV1(5.1a)         4.2(1)SV1(5.2b)           yes
      1   kickstart          4.2(1)SV1(5.1a)         4.2(1)SV1(5.2b)           yes
      2      system          4.2(1)SV1(5.1a)         4.2(1)SV1(5.2b)           yes
      2   kickstart          4.2(1)SV1(5.1a)         4.2(1)SV1(5.2b)           yes
      
      Module     Running-Version         ESX Version                                           VSM Compatibility       ESX Compatibility
      ------  ----------------------  ----------------------------------------------------  ----------------------  ----------------------
      17         4.2(1)SV1(5.1a)         VMware ESXi 5.0.0 Releasebuild-768111 (3.0)              COMPATIBLE              COMPATIBLE
      18         4.2(1)SV1(5.1a)         VMware ESXi 5.0.0 Releasebuild-768111 (3.0)              COMPATIBLE              COMPATIBLE
      <skipped>

      Make sure the impact of VSM module upgrade is ‘non-disruptive’ and upgraded VSM is compatible with VEM and ESX version.

    6. Perform the upgrade on the active VSM using the kickstart and system images;
      1000V-01# install all kickstart bootflash:nexus-1000v-kickstart.4.2.1.SV1.5.2b.bin system bootflash:nexus-1000v.4.2.1.SV1.5.2b.bin
      
      Verifying image bootflash:/nexus-1000v-kickstart.4.2.1.SV1.5.2b.bin for boot variable "kickstart".
      [####################] 100% -- SUCCESS
      
      Verifying image bootflash:/nexus-1000v.4.2.1.SV1.5.2b.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.2b.bin.
      [####################] 100% -- SUCCESS
      
      Extracting "kickstart" version from image bootflash:/nexus-1000v-kickstart.4.2.1.SV1.5.2b.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         4.2(1)SV1(5.1a)         4.2(1)SV1(5.2b)           yes
      1   kickstart         4.2(1)SV1(5.1a)         4.2(1)SV1(5.2b)           yes
      2      system         4.2(1)SV1(5.1a)         4.2(1)SV1(5.2b)           yes
      2   kickstart         4.2(1)SV1(5.1a)         4.2(1)SV1(5.2b)           yes
      
      Module     Running-Version         ESX Version                                           VSM Compatibility       ESX Compatibility
      ------  ----------------------  ----------------------------------------------------  ----------------------  ----------------------
      17         4.2(1)SV1(5.1a)         VMware ESXi 5.0.0 Releasebuild-821926 (3.0)              COMPATIBLE              COMPATIBLE
      18         4.2(1)SV1(5.1a)         VMware ESXi 5.0.0 Releasebuild-821926 (3.0)              COMPATIBLE              COMPATIBLE
      <skipped>
      Do you want to continue with the installation (y/n)?  [n]

      Continue with the installation by pressing Y, if you press N, the installation will be aborted.

      Install is in progress, please wait.
      
      Syncing image bootflash:/nexus-1000v-kickstart.4.2.1.SV1.5.2b.bin to standby.
      [####################] 100% -- SUCCESS
      
      Syncing image bootflash:/nexus-1000v.4.2.1.SV1.5.2b.bin to standby.
      [####################] 100% -- SUCCESS
      
      Setting boot variables.
      [####################] 100% -- SUCCESS
      
      Performing configuration copy.
      [####################] 100% -- SUCCESS
      
      Module 2: Waiting for module online.
      -- SUCCESS
      
      Notifying services about the switchover.
      [####################] 100% -- SUCCESS
      
      "Switching over onto standby".
      
      Install has been successful.

      As part of the upgrade process, the standby VSM is reloaded with new software images. Once it becomes the HA standby again, the upgrade process initiates a switchover

    7. After upgrade completed, log in and verify that the switch is running the required software version.
      1000V-01# show version
      <skipped>
      Software
      loader:    version unavailable [last: loader version not available]
      kickstart: version 4.2(1)SV1(5.2b)
      system:    version 4.2(1)SV1(5.2b)

6 comments to HOW TO: Upgrade Cisco Nexus 1000V VSM and VEM

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>