Cisco Nexus 1000V VEM Software Installation and Upgrade Guide, Release 4.0(4) SV1(3a)

Table Of Contents

Cisco Nexus 1000V VEM Software Installation and Upgrade Guide, Release 4.0(4) SV1(3a)

Audience

Information About the Virtual Ethernet Module

Introduction to Cisco Nexus 1000V and the Virtual Ethernet Module

Obtaining the VEM Software

VMware Patch Releases

Prerequisites for Installing VEM Software

Choosing a VEM Software Installation or Upgrade Procedure

Installing or Upgrading the VEM Software Using the CLI

Upgrading the ESX/ESXi Host with VEM Software Installed Using CLI

Uninstalling the VEM Software

Available Documents

Obtaining Documentation and Submitting a Service Request

Cisco Nexus 1000V VEM Software Installation and Upgrade Guide, Release 4.0(4) SV1(3a)

---

Revised: March 7, 2011

OL-23101-01

This document describes how to install and upgrade the Cisco Nexus 1000V Virtual Ethernet Module (VEM) software on a VMware ESX/ESXi 4.0 server or ESX/ESXi 4.1 server.

This document includes the following topics:

•Audience

•Information About the Virtual Ethernet Module

•Prerequisites for Installing VEM Software

•Choosing a VEM Software Installation or Upgrade Procedure

•Installing or Upgrading the VEM Software Using the CLI

•Upgrading the ESX/ESXi Host with VEM Software Installed Using CLI

•Uninstalling the VEM Software

•Available Documents

•Obtaining Documentation and Submitting a Service Request, page 15

Audience

This document is intended for use by experienced server administrators who configure and maintain server software. Table 1 compares the roles of the network administrator and server administrator.

Table 1 Administrator Roles  

Network Administrator	Server Administrator
•Creates, configures, and manages vswitches. •Creates, configures, and manages port profiles, including the following: –Security –Port channels –QoS policies	•Assigns the following to port groups: –Virtual network interface cards (VNICs) –vmkernel interfaces –Service console interfaces •Assigns physical NICs (PNICs) to vswitches on each host.

This document includes instructions for installing new VEM software as a fresh install or after upgrading the VSM software to a new version.

To install the Virtual Supervisor Module (VSM), see the following document:

Cisco Nexus 1000V Virtual Supervisor Module Software Installation Guide, Release 4.0(4)SV1(3a)

For detailed information about upgrading the software on the VSM and VEM, see the following document:

Cisco Nexus 1000V Software Upgrade Guide, Release 4.0(4)SV1(3a)

Information About the Virtual Ethernet Module

This section provides information about the Virtual Ethernet Module and includes the following topics:

•Introduction to Cisco Nexus 1000V and the Virtual Ethernet Module

•Obtaining the VEM Software

•VMware Patch Releases

Introduction to Cisco Nexus 1000V and the Virtual Ethernet Module

The Cisco Nexus 1000V is compatible with any upstream physical access layer switch that is Ethernet standard compliant, including the Catalyst 6500 series switch, Cisco Nexus switches, and switches from other network vendors. The Cisco Nexus 1000V is compatible with any server hardware listed in the VMware Hardware Compatibility List (HCL).

Cisco and VMware jointly designed APIs that produced the Cisco Nexus 1000V. The Cisco Nexus 1000V is a distributed virtual switch solution that is fully integrated within the VMware virtual infrastructure, including VMware vCenter for the virtualization administrator. This solution off-loads the configuration of the virtual switch and port groups to the network administrator to enforce a consistent data center network policy.

The Cisco Nexus 1000V has the following components that can virtually emulate a 66-slot modular Ethernet switch with redundant supervisor functions:

•Virtual Ethernet module (VEM) data plane—Each hypervisor is embedded with one VEM, a lightweight software component that replaces the virtual switch by performing the following functions:

–Advanced networking and security

–Switching between directly attached virtual machines

–Uplinking to the rest of the network

---

Note There can be one and only one version of VEM installed on an ESX host at any given time.

---

•Virtual supervisor module (VSM) control plane—The VSM is a standalone, external, physical or virtual appliance that performs the following functions for the Cisco Nexus 1000V system (that is, the combination of the VSM itself and all VEMs it controls):

–Configuration

–Management

A single VSM can manage up to 64 VEMs.

–Monitoring

–Diagnostics

–Integration with VMware vCenter

Active-standby VSMs increase high availability

In the Cisco Nexus 1000V, traffic is switched between virtual machines locally at each VEM instance. Each VEM also interconnects the local virtual machine with the rest of the network through the upstream access-layer network switch (blade, top-of-rack, end-of-row, and so forth). The VSM runs the control plane protocols and configures the state of each VEM accordingly, but it never forwards packets.

In the Cisco Nexus 1000V, the module slots are primary module 1 and secondary module 2. Either module could act as active or standby. The first server or host is automatically assigned to Module 3. NIC ports are 3/1 and 3/2 (vmnic0 and vmnic1 on ESX host). The ports to which the virtual NIC interfaces connect are virtual ports on the Cisco Nexus 1000V where they are assigned a global number.

Figure 1 shows an example of the Cisco Nexus 1000V distributed architecture.

Figure 1 Cisco Nexus 1000V Distributed Switching Architecture

Obtaining the VEM Software

You can obtain the VEM software from the sources listed in Table 2.

Table 2 Obtaining VEM Software  

Source	Description
VUM	If you are using the VMware vCenter Update Manager (VUM), then VUM obtains the VEM software from the VSM or from the VMware online portal.1
VSM	After the VSM has been installed as a VM, copy the file containing the VEM software from the VSM homepage located at the following url: http://VSM_IP_Address/
VMware	Download the VEM software from the VMware website. Click Download Vmware vSphere 4 Enterprise Plus > Download Download the VMware patches if you are utilizing VMware releases with patches.
Cisco	Download the VEM software from the Cisco website.

1 VMware vCenter Update Manager 4.0 does not list Cisco Nexus 1000V patches or updates, but you can add a Cisco Nexus 1000V patch source using the VMware knowledge base procedure located at the following url: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013134 VMware vCenter Update Manager 4.0 Update 1 and later versions do not have this limitation.

VMware Patch Releases

The Cisco Nexus 1000V VEM software is updated to support VMware patch releases and is available on both the VMware and Cisco software download web sites. The Cisco Nexus 1000V software posted on these websites can be used for both installation and upgrade of the VEM for both the VMware Classic and VMware Embedded platforms.

For information about installing software on an ESX or ESXi, see your VMware documentation.

For information about VEM software packages and compatibility, see the following document:

Cisco Nexus 1000V Compatibility Information, Release 4.0(4)SV1(3a).

Prerequisites for Installing VEM Software

Before installing the Cisco Nexus 1000V VEM software, you must know or do the following:

---

Note When performing any VUM operation on hosts which are a part of a cluster, ensure that VMWare High Availability (HA), VMware Fault Tolerance (FT), and VMware Distributed Power Management (DPM) features are disabled for the entire cluster. Otherwise, VUM will fail to upgrade the hosts in the cluster.

---

---

Note Any ESX patches or updates after ESX400/ESXi400-201006201-UG will be backward compatible with the Cisco Nexus 1000V U2 VEM vib (cross_cisco-vem_v121-4.0.4.1.3.1.0-1.20.2.vib).

---

•You have a copy of your VMware documentation available for installing software on a host.

•You have already obtained a copy of the VEM software file from one of the sources listed in Table 2.

•If you are installing the VEM software for the first time, you can install it before the Virtual Supervisor Module (VSM) is installed; however, verification and configuration of the VEM can only be done after installing the VSM.

•You have already downloaded the correct VEM software based on the current ESX host patch level. For more information, see the Cisco Nexus 1000V Compatibility Information, Release 4.0(4)SV1(3a).

•If you install the VEM software on an ESXi host before adding the host to a vSphere Server, you need to reboot the host. The alternative is to add the host to vSphere Server first, and then install the VEM software.

•If using VUM for a first-time installation, no action is required by the server administrator.
VUM automatically installs the VEM software.

•If you use a proxy server to connect VUM to the Internet, you may need to disable the proxy before starting a VUM upgrade. In VMware versions before VUM Update 1, the proxy prevents VUM from communicating locally with the VSM. For this reason, automatic VEM upgrades may fail if the proxy is not disabled first.

•On upstream switches the following configuration is mandatory:

–cat6k IOS:
(config-if) portfast trunk
or
(config-if) portfast edge trunk

–n5k: (config-if) spanning-tree port type edge trunk

•On upstream switches it is highly recommended that you globally enable the following:

–Global BPDU Filtering

–Global BPDU Guard

•On upstream switches where you cannot globally enable BPDU Filtering and BPDU Guard, it is highly recommended that you configure the following:

–(config-if) spanning-tree bpdu filter

–(config-if) spanning-tree bpdu guard

•For more information about configuring spanning-tree, BPDU, or portfast, see the documentation for your upstream switch.

Choosing a VEM Software Installation or Upgrade Procedure

There are two possible procedures for upgrading the VEM software:

•Installing or Upgrading the VEM Software

–If you are using VUM, then the Cisco Nexus 1000V VEM software will be installed automatically when the host is added to the Cisco Nexus 1000V DVS. When VEM upgrades are triggered from the VSM, the VEM software will be automatically upgraded on the host.

---

Note If your host is ESX/ESXi400-201006201-UG or higher, VUM will install the corresponding Cisco Nexus 1000V Update 2 VEM vib (cross_cisco-vem_v121-4.0.4.1.3.1.0-1.20.2.vib).

---

–If you are using the CLI, use the vihostupdate command or the esxupdate command. See the "Installing or Upgrading the VEM Software Using the CLI" section.

•Upgrading the ESX/ESXi Host with VEM Software Installed

–If you are using VUM to upgrade the host, you will have to create a host patch baseline and include the appropriate VMware patch or update bulletins and the corresponding Cisco Nexus 1000V VEM bulletin in the baseline. You can then upgrade the host by applying the baseline to the host and remediating.

---

Note If you are upgrading your ESX/ESXi host from ESX/ESXi400-201006201-UG, then you do not need to include any VEM Bulletin in the baseline.

---

–If you are using the CLI, use the vihostupdate command or the esxupdate command. See the "Upgrading the ESX/ESXi Host with VEM Software Installed Using CLI" section.

Installing or Upgrading the VEM Software Using the CLI

You can use this procedure to install the Cisco Nexus 1000V VEM software on an ESX or ESXi host.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

•If you are using vCLI:

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

–You are logged in to the remote host when vCLI is installed.

---

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

---

•If you are using the esxupdate command:

–You are logged in to the ESX host.

•Check the Cisco Nexus 1000V Compatibility Information, Release 4.0(4)SV1(3a) for compatible versions.

•You have already copied the VEM software installation file to the /tmp directory.

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

PROCEDURE

---

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

[root@serialport -]# cd tmp

[root@serialport tmp]# 

Step 2 Determine which upgrade method you want to use and run the appropriate command:

•If you are using vCLI, run the vihostupdate command and install the ESX/ ESXi and VEM software simultaneously.

vihostupdate --install -- bundle "[path to VMware Update offline bundle]","[path to 
Cisco updated VEM offline bundle]" --server [vsphere host IP address]

---

Note Put the host is maintenance mode prior to running the following command.

---

Example:

[root@serialport tmp]# vihostupdate -i -b /ESXi400-201002001.zip, 
cisco-vem-v121-4.0.4.1.3.1.0-1.11.2.zip --server 192.0.2.0

Enter username: root

Enter password:

Please wait installation in progress ...

The update completed successfully, but the system needs to be rebooted for the changes 
to be effective.

[root@serialport tmp]#

•If you are using the esxupdate command, from the ESX host /tmp directory, install the VEM software as shown in the following example:

---

Note When using the esxupdate command, you must log in to each host and run the command.

---

esxupdate --bundle [Updated 1000V VEM offline bundle] --bundle [VMware offline update 
bundle] update

Example: 

[root@cos1-]# esxupdate -b ./cross_cisco-vem-v100-4.0.4.1.3.nn-0.4.nn-release.vib 
update 
cross_cisco-vem-v100-4.0.4.1.1.nn-0.4.nn..   ################################### 
[100%]

Unpacking cross_cisco-vem-v100-esx_4..        ################################### 
[100%]

Installing cisco-vem-v100-esx                 ################################### 
[100%]

Running [/usr/sbin/vmkmod-install.sh]...

ok.

[root@cos1-]#

This command loads the software manually onto the host, loads the kernel modules, and starts the VEM Agent on the running system.

Step 3 Run the following commands and compare the output with the Cisco Nexus 1000V Compatibility Information, Release 4.0(4)SV1(3a).

[root@serialport tmp]# vmware -v

VMware ESXi 4.0.0 build-208167

[root@serialport tmp]# esxupdate --vib-view query | grep cisco

cisco-vem-v121-4.0.4.1.3.1.0-1.9.2 installed     2010-07-18T16:56:00.787147+00:00

The highlighted text shows the upgraded Cisco VEM.

root@serialport tmp]# esxupdate query

-----Bulletin ID----- -----Installed----- ----------Summary----------

ESXi400-Update01    2010-07-18T14:30:58    VMware ESXi 4.0 Update 1 

VEM400-201004265419109-BG 2010-07-18T16:56:00 Cisco Nexus 1000V 4.0(4)SV1(3a)

root@serialport tmp]# vem status -v

Package vssnet-esx4.1.0-00000-release

Version 4.0.4.1.3.0.0-1.9.2

Build 2

Date Mon Apr 26 21:47:24 PDT 2010

Number of PassThru NICs are 0

VEM modules are loaded

Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks

vSwitch0       64          3           64                1500    vmnic0

DVS Name       Num Ports   Used Ports  Configured Ports  Uplinks

nexus          256         50          256               vmnic3

Number of PassThru NICs are 0

VEM Agent (vemdpa) is running

Step 4 Run the following command from the VSM.

switch# show mod

Mod  Ports  Module-Type                      Model              Status

---  -----  -------------------------------- ------------------ ------------

1    0      Virtual Supervisor Module        Nexus1000V         active *

4    248    Virtual Ethernet Module          NA                 ok

Mod  Sw               Hw

---  ---------------  ------

1    4.0(4)SV1(3a)     0.0 

4    4.0(4)SV1(3a)     1.9 

Mod  MAC-Address(es)                         Serial-Num

---  --------------------------------------  ----------

1    00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8  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.62.220    NA                                    NA

4    10.104.62.217    3fa746d4-de2f-11de-bd5d-c47d4f7ca460  visor

---

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

---

Step 5 Do one of the following:

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

•If not, see the Recreating the Cisco Nexus 1000V Installation section in Cisco Nexus 1000V Troubleshooting Guide, Release 4.0(4)SV1(3a).

You have completed this procedure.

---

Upgrading the ESX/ESXi Host with VEM Software Installed Using CLI

You can use this procedure to upgrade an ESX or ESXi host by installing a VMware patch or update along with the compatible Cisco Nexus 1000V VEM software.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

•If you are using vCLI:

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

–You are logged in to the remote host when vCLI is installed.

---

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

---

•If you are using the esxupdate command:

–You are logged in to the ESX host.

•Check the Cisco Nexus 1000V Compatibility Information, Release 4.0(4)SV1(3a) for compatible versions.

•You have already copied the ESX or ESXi host software and VEM software installation file to the /tmp directory.

•You know the name of the ESX or ESXi and VEM software file to be installed.

DETAILED STEPS

---

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

[root@serialport -]# cd tmp

[root@serialport tmp]# 

Step 2 Determine which upgrade method you want to use and run the appropriate command:

---

Note If you are upgrading your ESX/ESXi host from ESX/ESXi400-201006201-UG, then you do not need to include any VEM bundle.

vihostupdate --install -- bundle "[path to VMware Update offline bundle]" --server [ESX host IP address]

---

•If you are using vCLI, run the vihostupdate command and install the ESX/ ESXi and VEM software simultaneously.

vihostupdate --install -- bundle "[path to VMware Update offline bundle]","[path to 
Cisco updated VEM offline bundle]" --server [ESX host IP address]

---

Note Put the host is maintenance mode prior to running the following command.

---

Example:

[root@serialport tmp]# vihostupdate -i -b /ESXi400-201002001.zip, 
cisco-vem-v121-4.0.4.1.3.1.0-1.11.2.zip --server 192.0.2.0

Enter username: root

Enter password:

Please wait installation in progress  ...

The update completed successfully, but the system needs to be rebooted for the changes 
to be effective.

[root@serialport tmp]#

•If you are using the esxupdate command, from the ESX host /tmp directory, install the VEM software as shown in the following example:

---

Note When using the esxupdate command, you must log in to each host and run the command.

---

esxupdate --bundle [Updated 1000V VEM offline bundle] --bundle [VMware offline update 
bundle] update

Example: 

~ # esxupdate --bundle /vmfs/volumes/datastore1/upgrade-from-esxi4.0-4.0_update02.zip 
--bundle /vmfs/volumes/datastore1/VEM400-201006021.zip update 

Unpacking cross_cisco-vem-v120-esx_4.0.4.1.3.0.0-1.20.21               
############################################################################### [100%]

Unpacking deb_vmware-esx-firmware_4.0.0-2.17.261974                    
############################################################################### [100%]

Unpacking deb_vmware-esx-viclient_4.0.0-2.17.261974                    
############################################################################### [100%]

Unpacking deb_vmware-esx-tools-light_4.0.0-2.17.261974                 
############################################################################### [100%]

Removing packages :vmware-esx-tools-light vmware-esx-viclient          
############################################################################### [100%]

Installing packages :deb_vmware-esx-firmware_4.0.0-2.17.261974         
############################################################################### [100%]

Installing packages :cross_cisco-vem-v120-esx_4.0.4.1.3.0.0-1.20.21    
############################################################################### [100%]

Installing packages :deb_vmware-esx-viclient_4.0.0-2.17.261974, deb_.. 
############################################################################### [100%]

Running [/usr/sbin/vmkmod-install.sh]...

ok.

The update completed successfully, but the system needs to be rebooted for the

changes to be effective.

~ #

This command loads the software manually onto the host, loads the kernel modules, and starts the VEM Agent on the running system.

Step 3 Reboot the host.

Step 4 Verify that the installation was successful.

[root@serialport tmp]# vmware -v

VMware ESXi 4.0.0 build-236512

root@serialport tmp]# esxupdate --vib-view query | grep cisco

cross_cisco-vem-v120-esx_4.0.4.1.3.0.0-1.9.2 retired       
2010-07-18T16:56:00.787147+00:00

cross_cisco-vem-v120-esx_4.0.4.1.3.0.0-1.11.2 installed     
2010-07-18T17:06:53.675403+00:00

[root@serialport tmp]# esxupdate query

-----Bulletin ID----- -----Installed----- ----------Summary----------

ESXi400-200911203-UG      2010-07-18T14:30:58 VI Client update for 4.0 U1 release

ESXi400-Update01          2010-07-18T14:30:58 VMware ESXi 4.0 Update 1

ESXi400-201002401-BG      2010-07-18T17:07:14 Updates Firmware

ESXi400-201002402-BG      2010-07-18T17:07:14 Updates VMware Tools

VEM400-201004265454109-BG 2010-07-18T17:07:14 Cisco Nexus 1000V 4.0(4)SV1(3a)

[root@serialport tmp]# vem status -v

Package vssnet-esx4.1.2-00000-release

Version 4.0.4.1.3.0.0-1.11.2

Build 2

Date Mon Apr 26 21:47:24 PDT 2010

Number of PassThru NICs are 0

VEM modules are loaded

Switch Name    Num Ports   Used Ports  Configured Ports  MTU     Uplinks

vSwitch0       64          3           64                1500    vmnic0

DVS Name       Num Ports   Used Ports  Configured Ports  Uplinks

nexus          256         50          256               vmnic3

Number of PassThru NICs are 0

VEM Agent (vemdpa) is running 

---

Note If the VEM Agent is not running, see the Cisco Nexus 1000V Troubleshooting Guide, Release 4.0(4)SV1(3a).

---

Step 5 Run the following command from the VSM.

switch# sh mod

Mod  Ports  Module-Type                      Model              Status

---  -----  -------------------------------- ------------------ ------------

1    0      Virtual Supervisor Module        Nexus1000V         active *

4    248    Virtual Ethernet Module          NA                          ok

Mod  Sw               Hw

---  ---------------  ------

1    4.0(4)SV1(3a)     0.0 

4    4.0(4)SV1(3a)     1.11 

Mod  MAC-Address(es)                         Serial-Num

---  --------------------------------------  ----------

1    00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8  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.62.220    NA                                    NA

4    10.104.62.217    3fa746d4-de2f-11de-bd5d-c47d4f7ca460  10.104.62.217

---

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

---

Step 6 Do one of the following:

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

•If not, see the Recreating the Cisco Nexus 1000V Installation section in Cisco Nexus 1000V Troubleshooting Guide, Release 4.0(4)SV1(3a).

You have completed this procedure.

---

Uninstalling the VEM Software

You can use this procedure to uninstall the Cisco Nexus 1000V software from a VEM.

BEFORE YOU BEGIN

Before beginning this procedure, you must know or do the following:

•Make sure the host is not currently a part of any DV switch by removing all of the following active ports from the DV switch:

–VMware kernel NICs

–Virtual switch interfaces

–Virtual NICs

•You are logged in to the ESX/ESXi host remotely using SSH.

DETAILED STEPS

---

Step 1 Uninstall the VEM software using the vem-remove -d command.

This command removes the software from the host, removes the kernel modules, and stops the VEM Agent on the running system.

---

Note The following example is being run on ESX.

---

[root@fcs-cos2 ~]# vem-remove -d

Watchdog-vemdpa: Terminating watchdog with PID 6651

Removing CIsco VEM VIB from COS system

Removing VIB cross_cisco-vem-v100-esx_4.0.4.1.2.3.0-1.11.2

Removing cisco-vem-v100-esx ############################### [100%]

Running [/usr/sbin/vmkmod-install.sh]...

Ok.

root@fcs-cos2 ~]#

---

Note The following example is being run on ESXi.

---

~ # vem-remove -d

watchdog-vemdpa: Terminating watchdog with PID 8815

Removing Cisco VEM VIB from visor system

Removing VIB cross_cisco-vem-v100-esx_4.0.4.1.2.3.0-1.11.2

Removing packages :cisco-vem-v100-esx ########################### [100%]

Running [/usr/sbin/vmkmod-install.sh]...

ok.

Cleaning up running visor system

~ #

Step 2 Verify that the software was successfully removed by checking for the output of the esxupdate --vib-view query command:

[root@fcs-cos2 -]# esxupdate --vib-view query

------------------VIB ID------------------ Package State -----------Timestamp------------ 

cross_cisco-vem-v100-esx_4.0.4.1.3.27-0.4.3 retired       2009-07-02T15:26:45.994264-05:00 

root@fcs-cos2 -]#

[root@fcs-cos2 -]# esxupdate --vib-view query

------------------VIB ID------------------ Package State -----------Timestamp------------ 

cross_cisco-vem-v100-esx_4.0.4.1.3.27-0.4.3 retired       2009-07-02T05:20:47.860404+00:00 

~ # 

Step 3 Do one of the following:

•If the removal was successful, your uninstallation is complete.

•If not, see the Recreating the Cisco Nexus 1000V Installation section in Cisco Nexus 1000V Troubleshooting Guide, Release 4.0(4)SV1(3a).

You have completed this procedure.

---

Available Documents

The following documents are used with the Cisco Nexus 1000 and are available on Cisco.com at the following url:

http://www.cisco.com/en/US/products/ps9902/tsd_products_support_series_home.html

General Information

Cisco Nexus 1000V Documentation Roadmap, Release 4.0(4)SV1(3a)

Cisco Nexus 1000V Release Notes, Release 4.0(4)SV1(3a)

Cisco Nexus 1000V Compatibility Information, Release 4.0(4)SV1(3a)

Cisco Nexus 1010 Management Software Release Notes, Release 4.0(4)SP1(1)

Install and Upgrade

Cisco Nexus 1000V Virtual Supervisor Module Software Installation Guide, Release 4.0(4)SV1(3a)

Cisco Nexus 1000V Software Upgrade Guide, Release 4.0(4)SV1(3a)

Cisco Nexus 1000V VEM Software Installation and Upgrade Guide, Release 4.0(4)SV1(3a)

Cisco Nexus 1010 Virtual Services Appliance Installation Guide

Configuration Guides

Cisco Nexus 1000V License Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Getting Started Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V High Availability and Redundancy Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Interface Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Layer 2 Switching Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Port Profile Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Quality of Service Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V Security Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1000V System Management Configuration Guide, Release 4.0(4)SV1(3)

Cisco Nexus 1010 Software Configuration Guide, Release 4.0(4)SP1(1)

Programming Guide

Cisco Nexus 1000V XML API User Guide, Release 4.0(4)SV1(3)

Reference Guides

Cisco Nexus 1000V Command Reference, Release 4.0(4)SV1(3)

Cisco Nexus 1000V MIB Quick Reference

Cisco Nexus 1010 Command Reference, Release 4.0(4)SP1(1)

Troubleshooting and Alerts

Cisco Nexus 1000V Troubleshooting Guide, Release 4.0(4)SV1(3a)

Cisco Nexus 1000V Password Recovery Guide

Cisco NX-OS System Messages Reference

Network Analysis Module Documentation

Cisco Network Analysis Module Software Documentation Guide, 4.2

Cisco Nexus 1000V NAM Virtual Service Blade Installation and Configuration Guide

Network Analysis Module Command Reference Guide, 4.2

User Guide for the Cisco Network Analysis Module Virtual Service Blades, 4.2

Cisco Network Analysis Module Software Release Notes, 4.2

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.

---

This document is to be used in conjunction with the documents listed in the Available Documents section.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Internet Protocol (IP) addresses used in this document are for illustration only. Examples, command display output, and figures are for illustration only. If an actual IP address appears in this document, it is coincidental.

© 2010-2011 Cisco Systems, Inc. All rights reserved.