Part I. Introduction

Chapter 1. Overview

Information About Cisco Nexus 1000V

Virtual Supervisor Module

Virtual Ethernet Module

Information About VSM-to-VEM Communication

Layer 3 Control Mode

Layer 2 Control Mode

System Port Profiles

System VLANs

Installing the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Installing the Cisco Nexus 1000V Manually

Topology for Layer 3 Control Mode

Topology for Layer 2 Control Mode

Control and Management VLAN Topology Options

Part II. Installation Procedures

Chapter 2. Installing Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Steps to Install Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Process Flowchart for Installing the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Supported Servers

Supported Software

Guidelines and Limitations for Installing Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Prerequisites for Installing the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Information Required for Installation

Installing the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Information About Migrating Hosts to the Cisco Nexus 1000V Switch Using Cisco Virtual Switch Update Manager

Guidelines and Limitations for Migrating Hosts to the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Prerequisites for Migrating Hosts to the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Migrating Hosts to the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Chapter 3. Installing the Cisco Nexus 1000V Software Manually

Steps to Install Cisco Nexus 1000V Manually

Process Flowchart for Installing the Cisco Nexus 1000V Manually

Supported VMware vSphere ESXi Hypervisor Versions

ESXi Host Prerequisites

VSM Prerequisites

VEM Prerequisites

Upstream Switch Prerequisites

Guidelines and Limitations for Installing the Cisco Nexus 1000V

Information Required for Installation

Verifying the Authenticity of the Cisco-Signed Image (Optional)

Installing the Software from the ISO Image

Installing the Software from an OVA Image

Establishing the SVS Connection

Setting Virtual Machine Startup and Shutdown Parameters

Adding VEM Hosts to the Cisco Nexus 1000V Distributed Virtual Switch

Installing the VEM Software Using VUM

Installing the VEM Software Using the CLI

Installing the VEM Software Locally on a VMware Host Using the CLI

Installing the VEM Software on a Stateless ESXi Host

Stateless ESXi Host

Adding the Cisco Nexus 1000V to an ESXi Image Profile

Installing the VEM Software on a Stateless ESXi Host Using esxcli

Installing the VEM Software on a Stateless ESXi Host Using VUM

Installing a VSM on the Cisco Nexus Cloud Services Platform

Feature History for Installing the Cisco Nexus 1000V

Part III. Upgrade Procedures

Chapter 4. Upgrading the Cisco Nexus 1000V

Upgrade Software Sources

Information about NetFlow Upgrade

Before You Begin

Prerequisites for Upgrading VSMs

Prerequisites for Upgrading VEMs

Prerequisite to Upgrading a VSM to a 3-GB Hard Disk Drive

Upgrading Hard Disk Drive Space from 2 GB to 3 GB on a VSM as a VM

Upgrading Hard Disk Drive Space from 2 GB to 3 GB on a VSM on a VSB

Verifying that the VSM has 3-GB of Hard Disk Drive Storage

Guidelines and Limitations for Upgrading the Cisco Nexus 1000V

Upgrade Procedures

Upgrade Types

Upgrading the Cisco Nexus 1000V Only

Combined Upgrade of vSphere and Cisco Nexus 1000V

Reserving the Memory and CPU on the Virtual Supervisor Module Virtual Machine

Reserving the Memory and CPU for the Virtual Supervisor Module in VSB on the Cloud Services Platform

Reserving the Memory and CPU for the Virtual Supervisor Module in VSB on the Cloud Services Platform Using the CLI

Software Images

In-Service Software Upgrades on Systems with Dual VSMs

ISSU Process for the Cisco Nexus 1000V

ISSU VSM Switchover

ISSU Command Attributes

VEM Upgrade Procedures

Creating an Upgrade ISO with a VMware ESX Image and a Cisco Nexus 1000V VEM Image

Upgrading the vCenter Server

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

Accepting the VEM Upgrade

Required Task After Upgradeâ€”Changing the VEM Feature Level

Information About Upgrading the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Guidelines and Limitations for Upgrading the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Prerequisites for Upgrading Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Upgrading the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Upgrading the VEM Software Using the vCLI

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

Simplified Upgrade Process

Upgrading from Releases 4.2(1)SV1(4x), 4.2(1)SV1(5.1x), or 4.2(1)SV1(5.2x) to the Current Release

Layer 3 Advantages

About VSM-VEM Layer 2 to 3 Conversion Tool

Prerequisites for Using VSM-VEM Layer 2 to 3 Conversion Tool

Using VSM-VEM Layer 2 to 3 Conversion Tool

Using Extract Mode

Using Convert Mode

Interface Comparisons Between mgmt0 and control0

Configuring the Layer 3 Interface

Creating a Port Profile with Layer 3 Control Capability

Creating a VMKernel on the Host

Configuring the SVS Domain in the VSM

Feature History for Upgrading the Cisco Nexus 1000V

Chapter 5. Upgrading a Standalone VSM

Upgrading a Standalone VSM

Part IV. VMware Procedures

Chapter 6. Installing and Upgrading VMware

Upgrading from VMware Releases 4.0, 4.1, 5.0, 5.1 to VMware Release 5.5

Installing the vCenter Single Sign On

Installing the vCenter Inventory Service

Upgrading the vCenter Server

Upgrading the vCenter Update Manager to Release 5.5

Augmenting the Customized ISO for VMware Release 5.1 and Later

Upgrading the ESXi Hosts to Release 5.x

Creating the Host Patch Baseline for 5.1 Update 1

Upgrading the ESXi Hosts to Release 5.1 Update 1 using VMware Update Manager

Upgrading the ESXi Hosts to Release 5.1 Update 1 using the CLI

Verifying the Build Number and Upgrade

Upgrading a VMware ESXi 5.0 Stateful Host to VMware ESXi 5.0 Patch 01

Installing ESXi 5.1 Host Software Using the CLI

Creating an Upgrade ISO with a VMware ESX Image and a Cisco Nexus 1000V VEM Image

Copyright Page

Part I. Introduction

- Overview

Chapter 1. Overview

This chapter contains the following sections:

- Information About Cisco Nexus 1000V

Information About 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 offloads 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 is compatible with any upstream physical access layer switch that is compliant with Ethernet standard, 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 that is listed in the VMware Hardware Compatibility List (HCL).

Note

We recommend that you monitor and install the patch files for the VMware ESX host software.

The Cisco Nexus 1000Vhas the following components:

- Virtual Supervisor Module (VSM)—The control plane of the switch and a VM that runs Cisco NX-OS.

- Virtual Ethernet Module (VEM)—A virtual line card that is embedded in each VMware vSphere (ESXi) host. The VEM is partly inside the kernel of the hypervisor and partly in a user-world process, called the VEM Agent.

See Glossary for a comprehensive list of terms that are used with the Cisco Nexus 1000V.

- Virtual Supervisor Module

- Virtual Ethernet Module

- Information About VSM-to-VEM Communication

Virtual Supervisor Module

You can install the VSM in either a standalone or active/standby high-availability (HA) pair. We recommend that you install two VSMs in an active-standby configuration for high availability.

The VSM, along with the VEMs that it controls, performs the following functions for the Cisco Nexus 1000V system:

- Configuration

- Management

- Monitoring

- Diagnostics

- Integration with VMware vCenter Server

The VSM uses an external network fabric to communicate with the VEMs. The VSM runs the control plane protocols and configures the state of each VEM, but it never actually forwards packets. The physical NICs on the VEM server are the uplinks to the external fabric. VEMs switch traffic between the local virtual Ethernet ports that are connected to the VM vNICs but do not switch the traffic to other VEMs. Instead, a source VEM switches packets to the uplinks that the external fabric delivers to the target VEM.

A single Cisco Nexus 1000V instance, including dual-redundant VSMs and managed VEMs, forms a switch domain. Each Cisco Nexus 1000V domain within a VMware vCenter Server must be distinguished by a unique integer called the domain identifier.

A single VSM can control up to 256 VEMs. Assuming that you have the 256 VEMs and the redundant VSMs, the Cisco Nexus 1000V can be viewed as a 66-slot modular switch.

See the Cisco Nexus 1000V Resource Availability Reference for more information about scale limits.

The Cisco Nexus 1000V architecture is shown in this figure.

Cisco Nexus 1000V Architecture

Virtual Ethernet Module

Each hypervisor is embedded with one VEM which replaces the virtual switch by performing the following functions:

- Advanced networking and security

- Switching between directly attached VMs

- Uplinking to the rest of the network

Note

Only one version of the VEM can be installed on an ESXi host at any given time.

In the Cisco Nexus 1000V, the traffic is switched between VMs locally at each VEM instance. Each VEM also interconnects the local VM 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 for the primary module 1 and secondary module 2. Either module can act as active or standby. The first server or host is automatically assigned to module 3. The network interface card (NIC) ports are 3/1 and 3/2 (vmnic0 and vmnic1 on the ESXi host). The ports to which the virtual NIC interfaces connect are virtual ports on the Cisco Nexus 1000V where they are assigned with a global number.

Information About VSM-to-VEM Communication

The VSM and the VEM can communicate over a Layer 2 network or a Layer 3 network. These configurations are referred to as Layer 2 or Layer 3 control modes.

- Layer 3 Control Mode

- Layer 2 Control Mode

Layer 3 Control Mode

Layer 3 control mode is the preferred method of communication between the VSM and the VEMs. In Layer 3 control mode, the VEMs can be in a different subnet than the VSM and from each other. Active and standby VSM control ports should be Layer 2 adjacent. These ports are used to communicate the HA protocol between the active and standby VSMs.

Each VEM needs a designated VMkernel NIC interface that is attached to the VEM that communicates with the VSM. This interface, which is called the Layer 3 Control vmknic, must have a system port profile applied to it (see System Port Profiles and System VLANs), so the VEM can enable it before contacting the VSM.

For a sample topology diagram, see Topology for Layer 3 Control Mode.

For more information about Layer 3 control mode, see the “Configuring the Domain” chapter in the Cisco Nexus 1000V System Management Configuration Guide.

Layer 2 Control Mode

In Layer 2 control mode, the VSM and VEMs are in the same subnet. You can install the VSM and VEMs on different ESXi hosts or on the same ESXi host. This figure shows a VSM and VEM that are running on the same host in Layer 2 control mode.

For a sample topology diagram showing Layer 2 control mode, see Topology for Layer 2 Control Mode.

VSM and VEM on the Same Host in Layer 2 Control Mode

System Port Profiles

System port profiles can establish and protect ports and VLANs that need to be configured before the VEM contacts the VSM.

When a server administrator adds a host to a DVS, its VEM must be able to contact the VSM. Because the ports and VLANs used for this communication are not yet in place, the VSM sends a minimal configuration, including the system port profiles and system VLANs, to vCenter Server, which then propagates it to the VEM.

When configuring a system port profile, you assign VLANs and designate them as system VLANs. The port profile becomes a system port profile and is included in the Cisco Nexus 1000V opaque data. Interfaces that use the system port profile, which are members of one of the defined system VLANs, are automatically enabled and forward traffic when the VMware ESX starts even if the VEM does not have communication with the VSM. The critical host functions are enabled even if the VMware ESX host starts and cannot communicate with the VSM.

Caution

VMkernel connectivity can be lost if you do not configure the relevant VLANs as system VLANs.

System VLANs

You must define a system VLAN in both the Ethernet and vEthernet port profiles to automatically enable a specific virtual interface to forward traffic outside the ESX host. If the system VLAN is configured only on the port profile for the virtual interface, the traffic is not forwarded outside the host. Conversely, if the system VLAN is configured only on the Ethernet port profile, the VMware VMkernel interface that needs that VLAN is not enabled by default and does not forward traffic.

The following ports must use system VLANs:

- Control and packet VLANs in the uplinks that communicate with the VSM.

- The Management VLAN in the uplinks and port profiles (that is, the Ethernet and vEthernet ports) and VMware kernel NICs used for VMware vCenter Server connectivity, Secure Shell (SSH), or Telnet connections.

- The VLAN that is used for remote storage access (iSCSI or NFS).

Caution

You must use system VLANs sparingly and only as described in this section. Only 32 system port profiles are supported.

After a system port profile has been applied to one or more ports, you can add more system VLANs, but you can only delete a system VLAN after you remove the port profile from service. This action prevents you from accidentally deleting a critical VLAN, such as a host management VLAN or a VSM storage VLAN.

Note

One VLAN can be a system VLAN on one port and a regular VLAN on another port in the same ESX host.

To delete a system VLAN, see the Cisco Nexus 1000V Port Profile Configuration Guide.

Installing the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Cisco Virtual Switch Update Manager is the graphical user interface (GUI) that you use to install the VSMs in high availability (HA) or standalone mode and the VEMs on ESXi hosts. The Cisco Virtual Switch Update Manager graphical user interface (GUI) is an integral part of VMware vSphere Web Client and it can only be accessed by logging into VMware vSphere Web Client.

Installing the Cisco Nexus 1000V Manually

When you install the Cisco Nexus 1000V manually, you download and install all of the necessary software. This installation method gives you the option of deploying Layer 2 or Layer 3 connectivity between the VSM and VEMs. Layer 3 connectivity is the preferred method. For an example of the Layer 3 installation topology, see Topology for Layer 3 Control Mode. If you want to use Layer 2 connectivity, see Topology for Layer 2 Control Mode.

Topology for Layer 3 Control Mode

Layer 3 control mode is the preferred method of communication between the VSM and VEMs. This figure shows an example of a Layer 3 control mode topology where redundant VSM VMs are installed. The software for the primary VSM is installed on ESXi 1, and the software for the secondary VSM is installed on ESXi 2.

Layer 3 Control Mode Topology Diagram

Topology for Layer 2 Control Mode

Note

Layer 3 control mode is the preferred method for communications between the VSM and the VEMs. For a topology diagram, see Topology for Layer 3 Control Mode.

In Layer 2 control mode, the VSM and VEMs are in the same subnet. This figure shows an example of redundant VSM VMs, where the software for the primary VSM is installed on ESXi 1, and the software for the secondary VSM is installed on ESXi 2.

Layer 2 Control Mode Topology Diagram

Control and Management VLAN Topology Options

You can deploy the control and management interfaces on separate VLANs or on the same VLAN.

Part II. Installation Procedures

- Installing Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

- Installing the Cisco Nexus 1000V Software Manually

Chapter 2. Installing Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

This chapter contains the following sections:

Steps to Install Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

You can install the Cisco Nexus 1000V using Cisco Virtual Switch Update Manager. Use these high-level steps and the workflow diagram in the Process Flowchart for Installing the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager to guide you through the installation process.

Procedure

Step 1

Make sure that all of the Cisco Virtual Switch Update Manager requirements have been met before you install Cisco Virtual Switch Update Manager.
For details, see the Cisco Nexus 1000V Manager Getting Started Guide.

Step 2

Make sure that all of the VMware software requirements have been met.
For details, see System Requirements.

Step 3

Gather the required information for the installation.
For details, see Preparing for Installation.

Step 4

Install the VSM.
For details, see Installing Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager.

Step 5

Add hosts to the Cisco Nexus 1000V distributed virtual switch (DVS), which installs the Virtual Ethernet Modules (VEMs) and migrates the hosts to the Cisco Nexus 1000V.
For details, see Migrating Hosts to Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager.

Process Flowchart for Installing the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

You can install the Cisco Nexus 1000V for VMware using Cisco Virtual Switch Update Manager, or you can install it manually. We recommend that you use Cisco Virtual Switch Update Manager as the primary method.

Supported Servers

The servers that run the Cisco Nexus 1000V VSM and VEM must be in the VMware Hardware Compatibility List (HCL).

Supported Software

The Cisco Nexus 1000V supports the following VMware vSphere ESXi Hypervisor versions (including patches and updates):

- 5.5

- 5.1

- 5.0

Note

Release 5.2(1)SV3(1.1) does not support any earlier versions of the VMware components than those listed above.

Guidelines and Limitations for Installing Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

The Cisco Nexus 1000V installation using Cisco Virtual Switch Update Manager has the following guidelines and limitations:

- We recommend that you install the VSMs in a high availability mode on the Cisco Nexus 1000V. For information about high availability and redundancy, see the Cisco Nexus 1000V High Availability and Redundancy Configuration Guide. Cisco Virtual Switch Update Manager supports standalone mode, but we do not recommend that you use this mode in a production environment.

- Cisco Virtual Switch Update Manager always deploys with VSM HA pairs by default. We recommend that you install primary and secondary VSM VMs on separate hosts.

- Only Layer 3 mode of deployment is supported by the Cisco Virtual Switch Update Manager with ESXi host only.

- The Cisco Nexus 1000V VSM always uses the following two network interfaces in the same order as follows:

1. Control Interface

2. Management Interface

- The VM hardware version has no dependencies; so the VM hardware version can be upgraded if required.

- Do not deploy vCenter server and VSM in different data centers. It is not supported.

- We recommend that you monitor and install all the relevant patch applications from the VMware ESX host server.

Prerequisites for Installing the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

The Cisco Nexus 1000V installation using Cisco Virtual Switch Update Manager has the following prerequisites:

- You have installed Cisco Virtual Switch Update Manager.

- You have installed and prepared vCenter Server for host management using the instructions from VMware.

- You have installed VMware vSphere Web Client.

- You have installed the VMware Enterprise Plus license on the hosts.

- You are familiar with the Cisco Nexus 1000V topology diagram.

- You must create port groups for the Control and Management VLANs on the Cisco Nexus 1000V.

- You must have the Distributed Switch—Create, Extension-Register, Update privilege permissions enabled on the vCenter Server.

Information Required for Installation

Cisco Virtual Switch Update Manager requires information about your Cisco Nexus 1000V for VMware deployment. Cisco Virtual Switch Update Manager uses this information to configure the VSMs and VEMs during the installation and deployment

The following information is required:

- Name of the datacenter in which the switch will be installed

- Switch deployment type (whether you are installing the switch as a high availability pair or a single standalone switch)

- Switch VSM version (the Cisco Nexus 1000V version to be installed)

- VM port group for the switch's control traffic

- VM port group for the switch's management traffic

- Host IP address

- SVS domain ID (a unique ID for the switch)

- IP address, subnet mask, and gateway IP address for switch connectivity

- IP address, subnet mask, and gateway IP address for management

- Switch name and password

Installing the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

You can install Cisco Nexus 1000V using Cisco Virtual Switch Update Manager.

Before You Begin

Know the following about the switch:

- VM port group for the control traffic of the switch

- VM port group for the management traffic of the switch

- IP address for management

- Subnet mask

- Gateway IP address

- Datacenter in which the switch will be installed

- Domain ID (a unique ID for the switch)

- Password

Procedure

Step 1

Log in to VMware vSphere Web Client.

Step 2

In the vSphere Client, choose Cisco Virtual Switch Update Manager > Install Cisco Nexus 1000V Distributed Switch > Datacenter. The Cisco Nexus 1000V Installer pane appears.
Cisco Nexus 1000V Installer Pane

Step 3

(Optional)You can also access the Cisco Nexus 1000V Installer in vSphere Client by choosing vCenter > Datacenter.

Step 4

Choose Manage > Cisco Nexus 1000V Installer.

Step 5

In the Cisco Nexus 1000V Switch Deployment Type area, complete the following fields:

Name

Description

HIgh Availability Pair radio button

Installs the switch as a HA pair. By default, the High Availability Pair is selected.

Standalone radio button

Installs the switch in a standalone mode.

Note:
We recommend that you install the Cisco Nexus 1000V in an HA pair.

VSM Version drop-down list

Select the Cisco Nexus 1000V version to be installed. By default, the latest version is selected.

Control VLAN drop-down list

Choose the control port group for the switch.

The control port group is used for the control traffic.

Management VLAN drop-down list

Choose the management port group for the switch.

Note:
The Cisco Nexus 1000V VSM uses the management network to communicate with vCenter server and ESXi.

Step 6

Click Suggest. This will automatically select two hosts based on the details provided in the Cisco Nexus 1000V Switch deployment type area.

Step 7

In the Host Selection area, complete the following fields:

Name

Description

IP Address field

The IP address of the hosts on which the switch will be deployed.

The primary switch is deployed on Host 1 and the secondary switch is deployed on Host 2.

You can override system choices by dragging and dropping hosts. Click Pick a host to drag and drop hosts.

Datastore drop-down list

Choose the system-selected datastore that you want to override. Choose a datastore for each host.

Resource Pool drop-down list

Choose the resource pool for each host.

Note:
If you do not choose a resource pool and the host is a cluster, the resource pool for the switch is the root resource pool of the cluster.

If you do not choose a resource pool and the host is in a standalone mode, then the resource pool for the switch will be the root resource pool of the host.

Folder Name drop-down list

Choose the folder name for each host.

Note:
If the folder name is not displayed in the drop-down list, the switch VM is created in the root VM folder of the datacenter.

Step 8

In the Switch Configuration area, complete the following fields:

Name

Description

Domain ID field

The domain ID for the switch.

The domain ID is common for both the primary and secondary switches and it should be unique for every new switch. The range for the domain is from 1 to 1023.

Deployment Type radio button

Configures the deployment type.

By default, Management IP Address is selected.

Note:

- If you select the Management IP address, then this IP address is used for both, the VSM management operations as well as the VSM to VEM communications.

- If you select the Control IP address, then this IP address is used only for the VSM to VEM communications.

Control:IP/Name field

The IP address for switch connectivity.

Control: Mask field

The sub net mask.

Control: Gateway IP/Name field

The gateway IP address.

Default Port Profile checkbox

If checked, the default port profile is enabled and this creates sample port profiles for the different features in the VSM, and pushes it to the VSM.

The sample port profiles are created as user references and includes default and mandatory commands that are required to configure this feature. You can modify the port profiles based on the network configuration.

Step 9

In the VIrtual Supervisor Module (VSM) configuration area, complete the following fields:

Name

Description

Switch Name field

The name of the switch. The name must: have the following:

- Start with a letter (A-Z, a-z).

- Contain up to 32 case-sensitive letters (A-Z, a-z), numbers (0-9), or hyphens (-).

- Not contain any other special characters or spaces.

When a switch VM is created in the vCenter, the same name is used for the primary and the secondary switch.

For a standalone deployment, the VSM VM is the switch name.

For a HA deployment, the primary VSM VM is the switch name_primary and the secondary switch is the switch name_secondary.

IP Address field

The IP address of the switch. The IP address is used for the management of the Cisco Nexus 1000V switch.

Subnet Mask field

The subnet mask for the above entered IP address.

Gateway Address field

The gateway IP address for the above entered IP address.

Username field

By default, the user name is admin. This field is not editable.

Password field

The admin user password.

This password is used to log in to the switch for administration.

Confirm Password field

The admin user password that you reenter for confirmation.

Step 10

Click Finish to install the Cisco Nexus 1000V switch.

Step 11

In the vSphere Web Client, choose Home > vCenter > Datacenters > Select Datacenter > Monitor > Tasks to view the status of the Cisco Nexus 1000V switch installation.
A typical installation of the switch takes about four minutes. In the vCenter Web Client, you can view the tasks by the task object, user, or the task status.

What to Do Next

Install VEM as described in the procedure Migrating Hosts to the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager.

Information About Migrating Hosts to the Cisco Nexus 1000V Switch Using Cisco Virtual Switch Update Manager

You can use the Cisco Virtual Switch Update Manager GUI to migrate hosts from the VMware vSwitch and VMware distributed virtual switch (DVS) to the Cisco Nexus 1000V switch.

Cisco Virtual Switch Update Manager enables you to do the following:

- Add hosts and/or Migrate multiple hosts.

- Migrate each VMware port group or kernel NIC to the correct port profile.

- Migrate each physical NIC from the VMware vSwitch or VMware DVS to the correct uplink on the Cisco Nexus 1000V.

- Migrate VM NICs from the VMware vSwitch or VMware DVS to the corresponding uplink on the Cisco Nexus 1000V.

See the Cisco Nexus 1000V and VMware Compatibility Information for more information on the compatibility information for Cisco Nexus 1000V.

Guidelines and Limitations for Migrating Hosts to the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

When you move the ESXi host that runs the Virtual Supervisor module (VSM) from the VMware vSwitch or VMware DVS to the Cisco Nexus 1000V, the connectivity between the active and standby VSM might get temporarily lost. In that situation, both active and standby VSMs assume the active role.

The reboot of the VSM is based on the following conditions:

1. The number of modules attached to the VSM

- If a VSM has more modules attached than the other VSMs, and there is no virtual channel (VC) connectivity on either VSM, the VSM that has fewer modules is rebooted.

- If modules are attached to both VSMs and one VSM has VC connectivity, the VSM without connectivity is rebooted.

2. VC connectivity

Note

This option is invoked when the previous condition is not met.

- If both VSMs have the same number of modules or no modules, the software makes a selection that is based on the VC connectivity status.

3. Last configuration change

Note

This condition is invoked when the previous two conditions are not met.

- If both VSMs have the same number of modules and no VC connectivity, the VSM with the latest configuration remains active and the other VSM is rebooted.

4. Last active VSM

- If the previous three conditions are not met, the VSM that became active most recently is rebooted.

Prerequisites for Migrating Hosts to the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

The migration of hosts to the Cisco Nexus 1000V using Cisco Virtual Switch Update Manager has the following prerequisites:

- The host must have one or more physical NICs on each VMware vSwitch/VMware DVS in use.

- You must have administrative privileges for vCenter Server.

- You must have the Distributed Switch—Create and Modify privilege permission enabled on the vCentre.

Migrating Hosts to the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

You can install a Cisco Nexus 1000V Virtual Ethernet module (VEM) using Cisco Virtual Switch Update Manager. When the Cisco Virtual Switch Update Manager installs VEMs, it migrates all VM kernels and their corresponding VM NICs across vSwitches to the Cisco Nexus 1000V VEMs.

Before You Begin

Know the following information about the switch:

- vCenter IP address

- vCenter user ID

- vCenter password

- Cisco Nexus 1000V switch username

- Cisco Nexus 1000V switch password

Procedure

Step 1

Log in to the VMware vSphere Web Client.

Step 2

In the vSphere Client, choose Cisco Virtual Switch Update Manager > Configure and Manage Nexus 1000V and Application Virtual Switch > Datacenter > Distributed Virtual Switch > Manage.
Note:
If the switch is not managed by Cisco Virtual Switch Update Manager, you are prompted to enter the switch credentials in the Make Managed window.

Step 3

In the switch pane, click Add Host.

Step 4

(Optional)In case of multiple vCenter Servers, choose Home > Cisco Virtual Switch Update Manager > vCenter Server > Configure and Manage Nexus 1000V and Application Virtual Switch .

Step 5

(Optional)You can also access the Cisco Virtual Switch Update Manager in the vSphere Client by navigating to vCenter > Distributed Switches.

Step 6

(Optional) In the switch pane, click Manage > Cisco Nexus 1000V > Add Host
Cisco Virtual Switch Update Manager—Migrating Hosts

Step 7

In the Host Selection area, review the following fields.

Name

Description

Clustered hosts drop-down list

Choose the hosts to be migrated. The clustered hosts list displays all the hosts that are in HA pair.

Standalone hosts drop-down list

Choose the hosts to be migrated.

Supported Hosts check box

If checked, displays the lists of hosts that can be migrated to the current version of the Cisco Nexus 1000V.

Unsupported Hosts check box

If checked, displays the list of hosts that cannot be migrated to the current version of the Cisco Nexus 1000V.

Unreachable Hosts check box

If checked, displays the list of hosts that are in a unreachable state.

Already in DVS check box

If checked, displays the list of hosts that are already migrated to the Cisco Nexus 1000V.

Step 8

Click Suggest. Cisco Virtual Switch Update Manager displays the list of existing and proposed port profiles and suggests appropriate port profiles for each VMKNIC, VM NIC, and physical NICs.

Step 9

Review the port profile populated in the Port Profile Editor area. You can edit the fields based on your requirements. To edit the fields, you must use the Port Profile Editor.
The port profiles that are already available on the VSM are not editable. You can edit only those port profiles that are suggested by the Cisco Virtual Switch Update Manager. Click the Duplicate button to create a new port profile from an existing or from a suggested port profile.

Step 10

In the Port Profile Editor area, complete the following fields.

Name

Description

Port Profile Editor drop-down list

The list of existing port profiles or new port profiles to be created are displayed. Choose the port profile.

- In Use—Displays true, when the port profile is in use on the current Add Host screen. Displays False when the port profile is not in use on the current Add Host screen.

- Valid—Displays true when all the port profile fields are completed. Displays false when one or more of the port profile fields is incomplete.

- Editable—Displays true if the port profile is editable. Displays false if the port profile is not editable.

- Profile Name—Displays the name of the port profile.

Uplink check box

If checked, displays the uplink associated with the port profile.

Trunk check box

If checked, displays the trunk associated with the port profile.

L3 Capable check box

If checked, the L3 capability is associated with the port profile.

ISCSI Multipath check box

If checked, the ISCSI Multipath is associated with the port profile.

Neither L3 nor ISCSI check box

If checked, then neither the L3 or the ISCSI is associated with the port profile.

Channel-group auto mode check box

If checked, the channel group auto mode is associated with the port profile.

Mac-pinning check box

If checked, the channel group auto mode on mac-pining is associated with the port profile.

Name field

The name of the port profile.

VLANs field

Choose the VLAN.

Native VLAN field

The native VLAN associated with the port profile.

Duplicate button

Clones an existing port profile configuration to create a new port profile .

Step 11

Scroll down to view the host profile populated in the Physical NIC Migration area.

Step 12

In the Physical NIC Migration area, review the following fields.

Name

Description

Physical NIC check box

Review the physical NIC that has been automatically selected by the Cisco Virtual Switch Update Manager. Check/uncheck to select/deselect the VMNIcs for the migration. You must ensure that at least one physical NIC is selected for the migration.

Profile drop-down list

Review the port profile associated with the physical NICs.

Alternatively, you can choose the required port profile from the profile drop-down list, to associate it with the physical NIC. You must ensure that all the necessary VLANs are allowed in the selected port profile.

Source column

The vSwitch or VDS port group that the PNIC is currently assigned to.

Select All button

Migrates all the physical NICs associated with the host.

Select None button

Deselects all the selected values for the physical NICs associated with the host.

Step 13

Scroll down to view the host profile populated in the VM Kernel NIC Setup area.

Step 14

In the VM Kernel NIC Setup area, complete the following fields.

Name

Description

VM Kernel NIC check box

If checked, displays the port profile configuration that will be created on Cisco Nexus 1000V and associated with the VMkernel NIC.

Review the selected VMkernel NICs. You can also uncheck the VMkernel NIC check boxes if you do not want the VMKs to be migrated to the Cisco Nexus 1000V.

You must ensure that at least one VMkernel NIC is selected to migrate to the Cisco Nexus 1000V which will carry the L3 traffic.
Note:
Do not uncheck any of the VMkernel NIC checkboxes, unless and until the required VMkernel NIC is associated with the Layer3 port profile.

L3 Capable column

Displays whether the VMkernel NIC is Layer 3 capable. Only one VMkernel NIC is Layer3 capable. By default, the VMK0 is selected as the Layer3 control.

Note:
To change the VMkernel to Layer3 port profile, do the following:

- From the Port Profile drop-down list, choose the non Layer3 port profile for VMk0. In absence of non Layer3 veth profile, you can create non Layer3 port profiles as follows:

- Select the Layer3 port profile and click Duplicate.

- Check the Neither L3 nor ISCSI radio button and click OK. You can edit the list of the supported VLANs.

- Select the L3 enabled PP for any one VMkernel NICs, which you want to use for the L3 control traffic.

Profile drop-down list

Choose the port profile associated with the VMkernel NIC.

Source Profile column

Displays the vSwitch or VDS port group that the VMkernel NIC is currently assigned to.

Select None button

Deselects all the selected VMkernel NICs associated with the host.

New button

Adds a new VMkernel NIC for Layer 3 control. Enter the IP address and net mask for the new VMkernel NIC and click OK.

After the VMKernel NIC is created, select the appropriate port profile for the VMKernel NIC from the port profile drop-down list.
Note:   Ensure that the host is selected before you create the new VMkernel NIC.

Edit button

Edits the IP address and subnet mask for a newly created VMkernel NIC.

Step 15

Scroll down to view the host profile populated in the VM Migration area.

Step 16

In the VM Migration area, review the following fields.

Area

Action

Virtual Machine NICs check box

If checked, displays the VSMs and the network adapters associated with the VM.

Profile drop-down list

Choose the port profile associated with the Virtual NIC.

Source Profile column

The source associated with the port profile.

Select None button

Deselects all the VMs associated with the host.

Step 17

Click Finish to migrate the host from the VMware vSwitch to the Cisco Nexus 1000V switch.

Step 18

In the vSphere Client, choose vCenter > Datacenter > Switch > Monitor > Tasks to view the status of the migration. You can also view the tasks in the vSphere Web client by navigating to Cisco Virtual Switch Update Manager > Select vCenter Host > Manage DVS > Select Datacenter > Select Switch > Monitor > Tasks.
A typical migration of the host takes about 2 minutes. In the vCenter Client, you can view the tasks by the task object, user, or task status.

Chapter 3. Installing the Cisco Nexus 1000V Software Manually

This chapter contains the following sections:

- Supported VMware vSphere ESXi Hypervisor Versions

- Guidelines and Limitations for Installing the Cisco Nexus 1000V

- Information Required for Installation

- Verifying the Authenticity of the Cisco-Signed Image (Optional)

Steps to Install Cisco Nexus 1000V Manually

You can install Cisco Nexus 1000V manually. Use these high-level steps and the workflow diagram in the section to guide you through the installation process.

Procedure

Step 1

Make sure that all of the VMware prerequisites have been met.
For details, see the following sections:

- Supported VMware vSphere ESXi Hypervisor Versions

- ESXi Host Prerequisites

Step 2

Make sure that all of the Cisco Nexus 1000V prerequisites have been met.
For details, see the following sections:.

- VSM Prerequisites

- VEM Prerequisites

- Upstream Switch Prerequisites

Step 3

Read and follow the guidelines and limitations for the Cisco Nexus 1000V.
For details, see Guidelines and Limitations for Installing the Cisco Nexus 1000V.

Step 4

Make topology decisions and gather any necessary information.
For details, see Information Required for Installation.

Step 5

Download the Cisco Nexus 1000V software.

Step 6

(Optional)Verify the authenticity of the Cisco Nexus 1000V image.
For details, see Verifying the Authenticity of the Cisco-Signed Image (Optional)

Step 7

Install the Virtual Supervisor Module (VSM) software from an ISO image, OVA image, or on a Cisco Nexus Cloud Services Platform.
For details, see one of the following sections:

- Installing the Software from the ISO Image

- Installing the Software from an OVA Image

- Installing a VSM on the Cisco Nexus Cloud Services Platform

Step 8

If you installed the VSM software on a CSP, proceed to the next step. If you installed the VSM software on a VM using an ISO or OVA image, you need to establish the SVS connection and configure the VM startup and shutdown parameters.
For details, see Establishing the SVS Connection and Setting Virtual Machine Startup and Shutdown Parameters.

Step 9

Add the VEM hosts to the Distributed Virtual Switch.
For details, see Adding VEM Hosts to the Cisco Nexus 1000V Distributed Virtual Switch.

Step 10

If you want to install the VEM software on a stateless ESXi host, proceed to the next step. Otherwise, install the VEM software using VUM, the Cisco Nexus 1000VCLI, or the VMware ESXi CLI.
For details, see one of the following sections:

- Installing the VEM Software Using VUM

- Installing the VEM Software Using the CLI

- Installing the VEM Software Locally on a VMware Host Using the CLI

Step 11

Install the VEM software on a stateless ESXi host.
For more details, see Installing the VEM Software on a Stateless ESXi Host.

Process Flowchart for Installing the Cisco Nexus 1000V Manually

Use the procedures in this chapter and the following workflow as a guide to install the Cisco Nexus 1000V for VMware manually.

Supported VMware vSphere ESXi Hypervisor Versions

Cisco Nexus 1000V supports the following VMware vSphere ESXi Hypervisor versions:

- 5.5

- 5.1

- 5.0

For information about installing or upgrading the VMware software, see Installing and Upgrading VMware.

See the following table for detailed compatibility information.

VMware vSphere ESXi Hypervisor Software Compatibility Versions

VMware

[1]

VIB

[2]

VEM Bundle

[3]

Windows VC Installer

Linux vCenter Server Appliance

VMware vSphere CLI

Power-Shell CLI

ESXi 5.5

cross_cisco-vem-

v170-5.2.1.3.1.1.0-3.2.1.vib

cisco-vem-

v170-5.2.1.3.1.1.0-3.2.1.zip

5.5

5.5

5.5

5.5

ESXi 5.1

cross_cisco-vem-

v170-5.2.1.3.1.1.0-3.1.1.vib

cisco-vem-

v170-5.2.1.3.1.1.0-3.1.1.zip

5.1

5.1

5.1

5.1

ESXi 5.0

cross_cisco-vem-

v170-5.2.1.3.1.1.0-3.0.1.vib

cisco-vem-

v170-5.2.1.3.1.1.0-3.0.1.zip

5.0

5.0

5.0

5.0

[1] Includes patches and updates.

[2] VIB files are available at http://www.vmware.com/patch/download.

[3] VMware bundled software updates require placing the host in maintenance mode.

ESXi Host Prerequisites

ESX or ESXi hosts have the following prerequisites:

- You have already installed and prepared vCenter Server for host management using the instructions from VMware.

- You should have VMware vSphere Client installed.

- You have already installed the VMware Enterprise Plus license on the hosts.

- All VEM hosts must be running ESXi 5.0 or later releases.

- You have two physical NICs on each host for redundancy. Deployment is also possible with one physical NIC.

- If you are using a set of switches, make sure that the interswitch trunk links carry all relevant VLANs, including control and packet VLANs. The uplink should be a trunk port that carries all VLANs that are configured on the host.

- You must configure control and management VLANs on the host to be used for the VSM VM.

- Make sure that the VM to be used for the VSM meets the minimum requirements listed in the following table.

- All the vmnics should have the same configuration upstream.

Caution

The VSM VM might fail to boot if RAM and CPU are not properly allocated. This document includes procedures for allocating RAM and setting the CPU speed.

This table lists the minimum requirements for hosting a VSM.

Minimum Requirements for a VM Hosting a VSM

VSM VM Component

Minimum Requirement

Platform

64 bit

Type

Other 64-bit Linux (recommended)

Processor

2

RAM (configured and reserved)

4 GB[1]

NIC

3

SCSI Hard Disk

3 GB with LSI Logic Parallel adapter

CPU speed

2048 MHz[2]

[1] If you are installing the VSM using an OVA file, the correct RAM setting is made automatically during the installation of this file. If you are using the CD ISO image, see Installing the Software from the ISO Image to reserve RAM and set the memory size.

[2] If you are installing the VSM using an OVA file, the correct CPU speed setting is made automatically during the installation. If you are using the CD ISO image, see Installing the Software from the ISO Image to reserve CPU and set the CPU reservation.

VSM Prerequisites

The Cisco Nexus 1000V VSM software has the following are prerequisites:

- You have the VSM IP address.

- You have installed the appropriate vCenter Server and VMware Update Manager (VUM) versions.

- If you are installing redundant VSMs, make sure that you first install and set up the software on the primary VSM before installing and setting up the software on the secondary VSM.

- If you are using the OVA file for installation, make sure that the CPU speed is 2048 MHz or greater. If the CPU speed is less than 2048 MHz, then use ISO image for installation.

- You have already identified the HA role for this VSM from the list in the following table.

HA Roles

HA Role

Single Supervisor System

Dual Supervisor System

Standalone (test environment only)

X

HA

X

Note

A standalone VSM is not supported in a production environment.

- You are familiar with the Cisco Nexus 1000V topology diagram that is shown in Topology for Layer 3 Control Mode.

VEM Prerequisites

The Cisco Nexus 1000V VEM software has the following prerequisites:

Note

If VMware vCenter Server is hosted on the same ESXi host as a Cisco Nexus 1000V VEM, a VUM-assisted upgrade on the host will fail. You should manually VMotion the vCenter Server VM to another host before you perform an upgrade.

- When you perform any VUM operation on hosts that are a part of a cluster, ensure that VMware fault tolerance (FT) and VMware distributed power management (DPM) features are disabled for the entire cluster. Otherwise, VUM cannot install the hosts in the cluster.

- If the hosts are in ESXi stateless mode, enable the PXE booted ESXi host settings under Home > Update Manager > Configuration > ESXi host/cluster.

- 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 VEM Software.

- You have already downloaded the correct VEM software based on the current ESXi host patch level. For more information, see the Cisco Nexus 1000V and VMware Compatibility Information.

- For a VUM-based installation, you must deploy VUM and make sure that the VSM is connected to vCenter Server.

Upstream Switch Prerequisites

The upstream switch from the Cisco Nexus 1000V has the following prerequisites:

- If you are using a set of switches, make sure that the interswitch trunk links carry all relevant VLANs, including the control and packet VLANs. The uplink must be a trunk port that carries all the VLANs that are configured on the host.

- The following spanning tree prerequisites apply to the upstream switch from the Cisco Nexus 1000V on the ports that are connected to the VEM.

- On upstream switches, the following configuration is mandatory:

On your Catalyst series switches with Cisco IOS software, enter the spanning-tree portfast trunk or spanning-tree portfast edge trunk command.

On your Cisco Nexus 5000 series switches with Cisco NX-OS software, enter the spanning-tree port type edge trunk command.

- On upstream switches we highly recommend that you enable Global BPDU Filtering and Global BPDU Guard globally.

- On upstream switches, where you cannot globally enable BPDU Filtering and BPDU Guard, we highly recommend that you enter the spanning-tree bpdu filter and spanning-tree bpdu guardcommands.

For more information about spanning tree and its supporting commands, see the documentation for your upstream switch.

- Enter the following commands on the upstream switch:

show running interface interface number
interface GigabitEthernet interface number
description description of interface
switchport
switchport trunk encapsulation dot1q
switchport trunk native VLAN native VLAN
switchport trunk allowed vlan list of VLANs
switchport mode trunk

end

Guidelines and Limitations for Installing the Cisco Nexus 1000V

The Cisco Nexus 1000V software installation has the following configuration guidelines and limitations:

- Virtual machine hardware version 11 is not supported.

- Do not enable VMware fault tolerance (FT) for the VSM VM because it is not supported. Instead, Cisco NX-OS HA provides high availability for the VSM.

- The VSM VM supports VMware HA. However, we strongly recommend that you deploy redundant VSMs and configure Cisco NX-OS HA between them. Use the VMware recommendations for the VMware HA.

- Do not enable VM monitoring for the VSM VM because it is not supported, even if you enable the VMware HA on the underlying host. Cisco NX-OS redundancy is the preferred method.

- When you move a VSM from the VMware vSwitch to the Cisco Nexus 1000V DVS, the connectivity between the active and standby VSM might get temporarily lost. In that situation, both active and standby VSMs assume the active role.

The reboot of the VSM is based on the following conditions:

1. The number of modules attached to the VSM

- If more modules are attached on one of the VSMs and there is no virtual channel (VC) connectivity on both VSMs, the VSM that has the smaller number of modules is rebooted.

- If modules are attached to both VSMs and one of the VSMs has VC connectivity, the VSM without connectivity is rebooted.

2. VC connectivity

Note

This option is invoked when the previous condition is not met.

- If both VSMs have the same number of modules, the software makes a selection that is based on the VC connectivity status.

For example, this action is taken if both VSMs have two modules attached or both VSMs have no modules attached.

3. Last configuration change

Note

This condition is invoked when the previous two conditions are not met.

- If both VSMs have the same number of modules and no VC connectivity, the VSM with the latest configuration remains active and the other VSM is rebooted.

4. Last active VSM

- If the previous three conditions are not met, the VSM that became active most recently is rebooted.

- If the VSM is moved from the VMware vSwitch to the Cisco Nexus 1000V DVS, we recommend that you configure port security on the VSM vEthernet interfaces to secure control/packet MAC addresses.

- To improve redundancy, install primary and secondary VSM VMs on separate hosts that are connected to different upstream switches.

- The Cisco Nexus 1000V VSM always uses the following three network interfaces in the same order as specified below:

1. Control Interface

2. Management Interface

3. Packet Interface

- There is no dependency on the VM hardware version, so the VM hardware version can be upgraded if required.

- We recommend that you deploy the VMware vCenter server and VSM in the same physical data center. If you choose to deploy the vCenter server and VSM in different physical data centers, be aware of the following guidelines and limitations:

- The VSM HA pair must be located in the same site as their storage and the active vCenter Server.

- Layer 3 control mode is preferred.

- If you are using Link Aggregation Control Protocol (LACP) on the VEM, use LACP offload.

- Quality of Service bandwidth guarantees for control traffic over the DCI link.

- Limit the number of physical data centers to two.

- A maximum latency of 10 ms is supported for VSM-VSM control traffic when deployed across datacenters.

- A maximum latency of 100 ms is supported for VSM-VEM control traffic for both L2 and L3 mode of deployments.

- Cisco Nexus 1000V Release 5.2(1)SV3(1.1) and later supports deployments where vCenter and VSM are in different data centers, provided the number of hosts does not exceed 35 and the link latency does not exceed 200 ms . In these types of deployments, we recommend that you do not edit port profiles when the VSM and the vCenter are disconnected.

- We recommend that you monitor and install all the relevant patch applications from VMware ESX host server.

Information Required for Installation

Before installing the software, make topology decisions and gather any necessary information, as follows:

- Decide whether to deploy the VSM as a VM on a vSphere host or cluster or on a CSP.

- Decide whether to deploy in Layer 2 or Layer 3 control mode (Layer 3 control mode is recommended).

- For Layer 2 control mode, determine the control or packet VLANs that will be used.

- For Layer 3 control mode, decide whether the management and Layer 3 control ports will be unified or separate. If they will be separate, determine the IP address of the Layer 3 control port for each ESXi host.

- Determine the domain ID.

- Determine the management, subnet, and gateway IP addresses for the VSM.

- Determine the administrative password for the VSM.

Verifying the Authenticity of the Cisco-Signed Image (Optional)

Before you install the Nexus1000v.5.2.1.SV3.1.1.zip image, you have the option to validate the authenticity of it. In the zip file, there is a signature.txt file that contains a SHA-512 signature and an executable script that can be used to verify the authenticity of the Nexus1000v.5.2.1.SV3.1.1.zip image.

Note

Verifying the authenticity of an image is optional. You can still install the image without validating its authenticity.

Before You Begin

You need to be running a Linux machine with the following utilities installed:

- openssl

- base64

Procedure

Step 1

Copy the following files to a directory on the Linux machine:

- Nexus1000v.5.2.1.SV3.1.1.zip image

- signature.txt file

- cisco_n1k_image_validation_v_1_1 script

Step 2

Ensure that the script is executable.
chmod 755 cisco_n1k_image_validation_v_1_1

Step 3

Run the script.
./cisco_n1k_image_validation_v_1_1 -s signature.txt Nexus1000v.5.2.1.SV3.1.1.zip

Step 4

Check the output. If the validation is successful, the following message displays:

Authenticity of Cisco-signed image Nexus1000v.5.2.1.SV3.1.1.zip has been successfully verified!

Installing the Software from the ISO Image

Before You Begin

- Know the location and image name of the ISO image you require for the installation.

- You have already read the Prerequisites for Installing the Cisco Nexus 1000V.

- You have already manually provisioned the VM to be used for the VSM. For more information, see the vSphere Virtual Machine Administration Guide.

- The VSM VM requires the following and this procedure includes steps for updating these properties:

- We recommend 4 Gigabit of RAM reserved and allocated.

- We recommend 2048 MHz of CPU speed.

Procedure

Step 1

Using your VMware documentation, attach the VSM ISO image to the virtual CD-ROM and copy the software to a virtual machine (VM).

Step 2

Make sure that the VSM VM is powered off.

Step 3

In the vSphere client Virtual Machine Properties window Hardware tab, choose Memory.

Step 4

In the Memory Size field, choose 4 GB.

Step 5

In the Resources tab, choose Memory.
The Resource Allocation settings display in the right-hand pane.

Step 6

In the Reservation field, choose 4096 MB.

Step 7

In the Resources tab, choose CPU.
The Resource Allocation settings display in the right-hand pane.

Step 8

In the Reservation field, choose 2048 MHz.

Note:   For optimum performance, we recommend minimum 2048 MHz of CPU speed. You may change the value as per availability.

Step 9

Click OK.
The VSM VM memory and CPU speed settings are saved in VMware vSphere Client.

Step 10

Right-click the VSM and choose Open Console.

Step 11

Choose Install Nexus1000V and bring up the new image entry and press Enter.

Step 12

Enter and confirm the Administrator password.
Note:
All alphanumeric characters and symbols on a standard US keyboard are allowed except for these three: $ \ ?

Step 13

Enter the domain ID. Enter the domain id<1-1023>: 152

Step 14

Enter the HA role.
If you do not specify a role, standalone is assigned by default.

This example shows the HA role as primary.

Enter HA role[standalone/primary/secondary]: primary

[#########################################] 100%

---- Basic System Configuration Dialog ----

This setup utility will guide you through the basic configuration of
the system. Setup configures only enough connectivity for management
of the system.

*Note: setup is mainly used for configuring the system initially,
when no configuration is present. So setup always assumes system
defaults and not the current system configuration values.

Press Enter at anytime to skip a dialog. Use ctrl-c at anytime
to skip the remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no):

This example shows the HA role as secondary.
Enter HA role[standalone/primary/secondary]: secondary

Setting HA role to secondary will cause a system reboot. Are you sure (yes/no) ? :

Step 15

Do one of the following:

- If you are setting up the primary/active VSM, go to Step 18.

- If you are setting up the secondary/standby VSM, then continue with the next step.

Step 16

If you have set up the VSM virtual machine (VM) to boot from the CD-ROM, and are installing the secondary VSM from the ISO image attached to your CD-ROM, remove the virtual CD-ROM now so that the VSM does not boot from the CD.
This step is necessary if you have set up the VSM VM to boot from the CD-ROM before the hard drive.

Step 17

If you are setting up the secondary/standby VSM, when prompted to reboot the VSM, answer yes.
The secondary VSM VM is rebooted and brought up in standby mode.

The password on the secondary VSM is synchronized with the password on the active/primary VSM.

Any configuration made on the active/primary VSM is now automatically synchronized with the standby.

This example show the system rebooting when the HA role is set to secondary.

Setting HA role to secondary will cause a system reboot. Are you sure (yes/no) ? :y

[########################################] 100%

HA mode set to secondary. Rebooting now...

You have completed this procedure for the secondary VSM.

Step 18

Enter yes to enter the basic configuration dialog.

Would you like to enter the basic configuration dialog (yes/no): yes

Step 19

Enter no to create another Login account.

Create another login account (yes/no) [n]: no

Step 20

Enter no to configure a read-only SNMP community string.

Configure read-only SNMP community string (yes/no) [n]: no

Step 21

Enter no to configure a read-write SNMP community string.

Configure read-write SNMP community string (yes/no) [n]: no

Step 22

Enter a name for the switch.

Enter the switch name: n1000v

Step 23

Enter yes to configure out-of-band management and then enter the mgmt0 IPv4 address and subnet mask.

Continue with Out-of-band (mgmt0) management configuration? [yes/no] [y]: yes
Mgmt0 IPv4 address: 172.28.15.152
Mgmt0 IPv4 netmask: 255.255.255.0

Step 24

Enter yes to configure the default gateway.

Configure the default-gateway: (yes/no) [y]: yes
IPv4 address of the default gateway : 172.23.233.1

Step 25

Enter no to configure advanced IP options.

Configure Advanced IP options (yes/no)? [n]: no

Step 26

Enter yes to enable the Telnet service.

Enable the telnet service? (yes/no) [y]: yes

Step 27

Enter yes to enable the SSH service and then enter the key type and number of key bits.

Enable the ssh service? (yes/no) [y]: yes
Type of ssh key you would like to generate (dsa/rsa) : rsa
Number of  key bits <768-2048> : 1024

For more information, see the document, Cisco Nexus 1000V Security Configuration Guide.

Step 28

Enter yes to enable the HTTP server.

Enable the http-server? (yes/no) [y]: yes

Step 29

Enter no to configure the NTP server.

Configure NTP server? (yes/no) [n]: no

Step 30

Enter yes to configure the SVS domain parameters and then enter the mode (L2 or L3), and the control and packet VLAN IDs.

Configure svs domain parameters? (yes/no) [y]: yes
Enter SVS Control mode (L2 / L3) [L3] : Press Return

Step 31

Enter yes to configure the VEM feature level and then enter 0 or 1.

Vem feature level will be set to 5.2(1)SV3(1.1),
Do you want to reconfigure? (yes/no) [n] yes
Current vem feature level is set to 5.2(1)SV3(1.1)
You can change the feature level to:
vem feature level is set to the highest value possible

Note:
The feature level is the least VEM release that the VSM can support. For example, if the feature level is set to the 5.2(1)SV3(1.1) release, any VEMs with an earlier release are not attached to the VSM.

The system now summarizes the complete configuration and asks if you want to edit it.

The following configuration will be applied:
Switchname n1000v
interface Mgmt0
ip address 172.28.15.152 255.255.255.0
no shutdown
no telnet server enable
ssh key rsa 1024 force
ssh server enable
feature http-server
svs-domain
no control vlan
no packet vlan
svs mode L3 interface mgmt0

Step 32

Do one of the following:

- If you do not want to edit the configuration enter no and continue with the next step.

- If you want to edit the configuration, enter yes and return to Step 19 to revisit each command.

Would you like to edit the configuration? (yes/no) [n]:no

Step 33

Enter yes to use and save this configuration, answer yes.
Caution:
If you do not save the configuration now, none of your changes will be part of the configuration the next time that the switch is rebooted. Enter yes to save the new configuration and to ensure that the kickstart and system images are also automatically configured.

Use this configuration and save it? (yes/no) [y]: yes
[########################################] 100%

The new configuration is saved into nonvolatile storage.

Note:
You can use the setup routine to update the configuration done in Step 18 through Step 33 at any time by entering the setup command in EXEC mode. Once setup begins, press Enter to skip a command. Press Ctrl-C to skip the remaining commands.

If you are installing redundant VSMs, make sure that you configure the software on the primary VSM before installing the software on the secondary VSM.

Step 34

Create the SVS connection manually or go to Establishing the SVS Connection.

Installing the Software from an OVA Image

Before You Begin

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

- Know the location and image name of the OVA image you require for the installation.

- You have already read the Prerequisites for Installing the Cisco Nexus 1000V.

- You have a copy of the following Cisco Nexus 1000V software image files on your local drive, depending on the installation type you are using:

- For detailed information about using the Deploy OVF Template wizard, see the vSphere Virtual Machine Administration Guide.

- You have the following information available for creating a VM for the VSM and mapping the required port groups:

- A name for the new VSM that is unique within the inventory folder and up to 80 characters.

- The name of the host where the VSM will be installed in the inventory folder.

- The name of the datastore in which the VM files will be stored.

- The names of the network port groups used for the VM.

- The Cisco Nexus 1000V VSM IP address.

- If you are using the OVA file for installation, make sure that you have the following information available for creating and saving an initial configuration file on the VSM:

- VSM domain ID

- Admin password

- Management IP address, subnet mask, and gateway

- The VSM VM requires the CPU speed to be 2048 MHz or greater. If the CPU speed is less than 2048 MHz, then do not proceed with this procedure. Instead perform Installing the Software from the ISO Image.

Procedure

Step 1

From the vSphere Client, choose File > Deploy OVF Template.

Step 2

In the Source screen, specify the location of the OVA file and click Next.
The OVF Template Details screen opens displaying product information, including the size of the file and the size of the VM disk.

Step 3

Click Next.

Step 4

Read the Cisco Nexus 1000V License Agreement.

Step 5

Click Accept and then click Next.

Step 6

In the Name: field, add the VSM name, choose the folder location within the inventory where it will reside, and click Next.
The name for the VSM must be unique within the inventory folder and less than 80 characters.

Step 7

From the Configuration drop-down list, choose Nexus 1000V Installer.
This choice configures the primary VSM using the GUI setup dialog.

Step 8

Click Next.

Step 9

Choose the data center or cluster on which to install the VSM.

Step 10

Click Next.

Step 11

Choose the datastore in which to store the file if one is available.
On this page, you choose from datastores already configured on the destination cluster or host. The virtual machine configuration file and virtual disk files are stored on the datastore. Choose a datastore large enough to accommodate the virtual machine and all of its virtual disk files.

Step 12

Click Next.

Step 13

Choose the Thick provisioned disk format for storing virtual machine virtual disks, and click Next.

Format

Description

Thin Provisioned

The storage is allocated on demand as data is written to the virtual disks.

Note:
This disk format is not supported for Cisco Nexus 1000V.

Thick Provisioned

All storage is immediately allocated.

Flat Provisioned

Note:
This format is only available with VMWare ESXi 5.0.

Flat Disk

All storage for the virtual disk is allocated in advance.

Step 14

In the Network Mapping screen, choose the networks (the control, management, and packet port groups) that are present in your inventory.

Step 15

Click Next

Step 16

Do one of the following:

- If you are installing software on a primary VSM, specify the following properties for your primary VSM:

- VSM domain ID

- Admin password

- Management IP address

- Management IP subnet mask

- Management IP gateway

- If you are installing software on a secondary VSM, specify only the following properties for your secondary VSM (all other properties are acquired on synchronization with the primary VSM), and then click Next:

- VSM domain ID (use the same domain ID entered for the primary).

- Admin password (use the same password entered for the primary).

Step 17

Click Next.

Step 18

In the Ready to Complete screen, if the configuration is correct, click Finish.
A status bar displays as the VM installation progresses.

Step 19

Click Close.
You have completed installing the Cisco Nexus 1000V software.

Step 20

Right-click the VSM and choose Open Console.

Step 21

Click the green arrow to power on the VSM.

Step 22

Enter the following commands at the VSM prompt.

switch# configure terminal
switch(config)# setup

Step 23

Enter the HA role.
If you do not specify a role, standalone is assigned by default.

This example shows the HA role as primary.

Enter HA role[standalone/primary/secondary]: primary

[#########################################] 100%

---- Basic System Configuration Dialog ----

This setup utility will guide you through the basic configuration of
the system. Setup configures only enough connectivity for management
of the system.

*Note: setup is mainly used for configuring the system initially,
when no configuration is present. So setup always assumes system
defaults and not the current system configuration values.

Press Enter at anytime to skip a dialog. Use ctrl-c at anytime
to skip the remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no):

This example shows the HA role as secondary.

Enter HA role[standalone/primary/secondary]: secondary

Setting HA role to secondary will cause a system reboot. Are you sure (yes/no) ? :

Step 24

Do one of the following:

- If you are setting up the primary/active VSM, go to Step 18.

- If you are setting up the secondary/standby VSM, then continue with the next step.

Step 25

If you have set up the VSM virtual machine (VM) to boot from the CD-ROM, and are installing the secondary VSM from the ISO image attached to your CD-ROM, remove the virtual CD-ROM now so that the VSM does not boot from the CD.
This step is necessary if you have set up the VSM VM to boot from the CD-ROM before the hard drive.

Step 26

If you are setting up the secondary/standby VSM, when prompted to reboot the VSM, answer yes.
The secondary VSM VM is rebooted and brought up in standby mode.

The password on the secondary VSM is synchronized with the password on the active/primary VSM.

Any configuration made on the active/primary VSM is now automatically synchronized with the standby.

This example shows the system rebooting when the HA role is set to secondary.

Setting HA role to secondary will cause a system reboot. Are you sure (yes/no) ? :y

[########################################] 100%

HA mode set to secondary. Rebooting now...

You have completed this procedure for the secondary VSM.

Step 27

Enter yes to enter the basic configuration dialog. Would you like to enter the basic configuration dialog (yes/no): yes

Step 28

Enter no to create another Login account.

Create another login account (yes/no) [n]: no

Step 29

Enter no to configure a read-only SNMP community string.

Configure read-only SNMP community string (yes/no) [n]: no

Step 30

Enter no to configure a read-write SNMP community string.

Configure read-write SNMP community string (yes/no) [n]: no

Step 31

Enter a name for the switch.

Enter the switch name: n1000v

Step 32

Enter yes to configure out-of-band management and then enter the mgmt0 IPv4 address and subnet mask.

Continue with Out-of-band (mgmt0) management configuration? [yes/no] [y]: yes
Mgmt0 IPv4 address: 172.28.15.152
Mgmt0 IPv4 netmask: 255.255.255.0

Step 33

Enter yes to configure the default gateway.

Configure the default-gateway: (yes/no) [y]: yes

IPv4 address of the default gateway : 172.23.233.1

Step 34

Enter no to configure advanced IP options.

Configure Advanced IP options (yes/no)? [n]: no

Step 35

Enter yes to enable the Telnet service.

Enable the telnet service? (yes/no) [y]: yes

Step 36

Enter yes to enable the SSH service and then enter the key type and number of key bits.

Enable the ssh service? (yes/no) [y]: yes
Type of ssh key you would like to generate (dsa/rsa) : rsa
Number of  key bits <768-2048> : 1024

For more information, see the document, Cisco Nexus 1000V Security Configuration Guide.

Step 37

Enter yes to enable the HTTP server.

Enable the http-server? (yes/no) [y]: yes

Step 38

Enter no to configure the NTP server.

Configure NTP server? (yes/no) [n]: no

Step 39

Enter yes to configure the SVS domain parameters and then enter the mode (L2 or L3), and the control and packet VLAN IDs.

Configure svs domain parameters? (yes/no) [y]: yes
Enter SVS Control mode (L2 / L3) : L2
Enter control vlan <1-3967, 4048-4093> : 100
Enter packet vlan <1-3967, 4048-4093> : 101

Step 40

Enter yes to configure the VEM feature level and then enter 0 or 1.

Vem feature level will be set to 4.2(1)SV2(1.1),
Do you want to reconfigure? (yes/no) [n] yes
Current vem feature level is set to 4.2(1)SV2(1.1)
You can change the feature level to:
vem feature level is set to the highest value possible

The system now summarizes the complete configuration and asks if you want to edit it.

The following configuration will be applied:
Switchname n1000v
interface Mgmt0
ip address 172.28.15.152 255.255.255.0
no shutdown
no telnet server enable
ssh key rsa 1024 force
ssh server enable
feature http-server
svs-domain
svs mode L2
control vlan 100
packet vlan 101
domain id 101
vlan 100
vlan 101

Step 41

Do one of the following:

- If you do not want to edit the configuration enter no and continue with the next step.

- If you want to edit the configuration, enter yes and return to Step 19 to revisit each command.

Would you like to edit the configuration? (yes/no) [n]:no

Step 42

Enter yes to use and save this configuration.
Caution:
If you do not save the configuration now, none of your changes will be part of the configuration the next time that the switch is rebooted. Enter yes to save the new configuration and to ensure that the kickstart and system images are also automatically configured.

Use this configuration and save it? (yes/no) [y]: yes
[########################################] 100%

The new configuration is saved into nonvolatile storage.

Note:
You can use the setup routine to update the configuration done in Step 18 through Step 33 at any time by entering the setup command in EXEC mode. Once setup begins, press Enter to skip a command. Press Ctrl-C to skip the remaining commands.

Note:
If you are installing redundant VSMs, make sure that you configure the software on the primary VSM before installing the software on the secondary VSM.

Step 43

Create the SVS connection manually or go to Establishing the SVS Connection.

Establishing the SVS Connection

Procedure

Step 1

Open the vSphere Client.

Step 2

Choose the primary VSM.
vSphere Client Window

Step 3

Choose the Console tab.

Step 4

Enter the show svs connections command to confirm that there is not an SVS connection.

Step 5

Open a command window.

Step 6

In the VSM Console, enter the following command:

svs connection < Name of the Connection >
protocol vmware-vim
remote ip address  <VC Ip address >  port  80
vmware dvs datacenter-name  <name>
max-ports 8192
Connect

Step 7

In the vSphere Console window, enter the show svs connections command.
The operational status is Connected.

You have completed establishing the SVS connection.

Setting Virtual Machine Startup and Shutdown Parameters

Before You Begin

- You have the following information:

- Number of seconds for the default startup delay

- Number of seconds for the default shutdown delay

Procedure

Step 1

In the vSphere Client window, choose a host and click the Configuration tab.

Step 2

In the Configuration pane, choose Virtual Machine Startup/Shutdown.

Step 3

In the Virtual Machine Startup and Shutdown pane, click the Properties link.

Step 4

In the System Settings dialog box, do the following:

1. Check the Allow virtual machines to start and stop automatically with the system check box.

2. In the System Settings pane, do the following:

- Enter the number of seconds in the Default Startup Delay seconds field.

- Enter the number of seconds in the Default Shutdown Delay seconds field.

3. In the Startup Order pane, do the following:

- Choose the VM.

- Click the Move Up button until the VM is under Automatic Startup.

4. Click OK.

5. Repeat Step 2 through Step 4 for the other VM.

Startup and shutdown settings are complete.

Adding VEM Hosts to the Cisco Nexus 1000V Distributed Virtual Switch

Before You Begin

- You have the following information:

- Physical adapters

- Uplink port groups

Procedure

Step 1

In the vSphere Client window, choose Hosts and Clusters > Networking.
vSphere Client WIndow

Step 2

In the vSphere Client Hosts window, choose the DVS and click the Hosts tab.
vSphere Client Hosts Window

Step 3

In the Add Hosts to DVS window, right-click the DVS and from the drop-down list, choose Add Host.
Add Hosts to DVS

Step 4

In the Select Hosts and Physical Adapters screen, choose the hosts and the uplink port groups, and click Next.

Step 5

In the Network Connectivity screen, do the following tasks:
Note:
For Layer 3 communication, you must migrate or create a new Layer 3 vmkernel interface. Migrate your management vmkernel interface into the Layer 3 capable port-profile. Do not use multiple vmkernel interfaces on the same subnet.

1. Highlight the vmkernel interface that you want to migrate, and choose the destination port group that you created for management traffic earlier.

2. Click Next.

Step 6

In the Virtual Machine Networking screen, click Next.

Step 7

In the Ready to Complete screen, click Finish.

Step 8

In the vSphere Client Hosts window, confirm that the hosts are in the Connected state.

The host connection process is complete.

Installing the VEM Software Using VUM

Before You Begin

VMware Update Manager (VUM) automatically selects the correct VEM software to be installed on the host when the host is added to the DVS.

Note

Make sure that you read the VEM Prerequisites to ensure that the VUM operation proceeds without failure.

Installing the VEM Software Using the CLI

Based on the version of VMware ESX/ESXi software that is running on the server, there are different installation paths.

Installing the VEM Software Locally on a VMware Host Using the CLI

Note

This procedure applies for VMware 5.0 host and later ESXi versions.

Procedure

Step 1

Copy the VEM software to the /tmp directory.

Step 2

~ # esxcli software vib install -v /tmp/VIB_FILE

Begin the VEM installation procedure.

Step 3

Verify that the VEM software is installed on the host.

Step 4

vem status -v

Verify that the installation was successful by checking for the “VEM Agent (vemdpa) is running” statement in the output of the vem status command.

Step 5

Do one of the following:

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

- If the installation was not successful, see the "Recreating the Cisco Nexus 1000V Installation" section in the Cisco Nexus 1000V Troubleshooting Guide.

The following example shows how to install VEM software locally on a VMware 5.0 host using the CLI.

~ # esxcli software vib install -v /Cisco_bootbank_cisco-vem-v170-esx_5.2.1.3.1.1.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.1.0-3.0.1.vib
VIBs Removed: Cisco_bootbank_cisco-vem-v164-esx_4.2.1.2.2.2.0-3.0.1.vib
VIBs Skipped

~ # vem status -v
Package vssnet-esxmn-release
Version 5.2.1.3.1.1.0-3.0.0
Build 1
Date Sat Jan 25 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              1024        19          1024              1500    vmnic7,vmnic6,vmnic3,vmnic2,vmnic1,vmnic0

VEM Agent (vemdpa) is running

~ # esxcli software vib list | grep cisco
cisco-vem-v170-esx               5.2.1.3.1.1.0-3.0.0                Cisco   PartnerSupported  2014-01-25
~ #

~ # vemcmd show version
VEM Version: 5.2.1.3.1.1.0-3.0.0
VSM Version: 5.2(1)SV3(1.1) [build 5.2(1)SV3(1.1)]
System Version: VMware ESXi 5.0.0 Releasebuild-914586

Installing the VEM Software on a Stateless ESXi Host

The following list outlines the VEM installation process on a stateless ESXi host.

Procedure

Step 1

See the procedure for Adding the Cisco Nexus 1000V to an ESXi Image Profile.

Step 2

Installing the VEM software using one of the two following procedures:

- Installing the VEM Software on a Stateless ESXi Host Using esxcli

- Installing the VEM Software on a Stateless ESXi Host Using VUM

Step 3

See the procedure for Configuring Layer 2 Connectivity.

- Stateless ESXi Host

- Adding the Cisco Nexus 1000V to an ESXi Image Profile

- Installing the VEM Software on a Stateless ESXi Host Using esxcli

- Installing the VEM Software on a Stateless ESXi Host Using VUM

Stateless ESXi Host

Note

For stateless ESXi, the VLAN that you use for the Preboot Execution Environment (gPXE) and Management must be a native VLAN in the Cisco Nexus 1000V management uplink. It must also be a system VLAN on the management VMkernel NIC and on the uplink.

VMware vSphere 5.0.0 introduces the VMware Auto Deploy, which provides the infrastructure for loading the ESXi image directly into the host’s memory. The software image of a stateless ESXi is loaded from the Auto Deploy Server after every boot. In this context, the image with which the host boots is identified as the image profile.

An image profile is a collection of vSphere Installation Bundles (VIBs) required for the host to operate. The image profile includes base VIBs from VMware and additional VIBs from partners.

On a stateless host, you can install or upgrade the VEM software using either the VUM or CLI.

In addition, you should bundle the new or modified VEM in the image profile from which the stateless host boots. If it is not bundled in the image profile, the VEM does not persist across reboots of the stateless host.

For more information about the VMware Auto Deploy Infrastructure and stateless boot process, see the “Installing ESXi using VMware Auto Deploy” chapter of the vSphere Installation and Setup, vSphere 5.0.0 document.

Adding the Cisco Nexus 1000V to an ESXi Image Profile

Before You Begin

- Install and set up the VMware Auto Deploy Server. See the vSphere Installation and Setup document.

- Install the VMware PowerCLI on a Windows platform. This step is required for bundling the VEM into the image profile. For more information, see the vSphere PowerCLI Installation Guide.

- On the same Windows platform where VMware PowerCLI is installed, do the following:

- Download the image profile offline bundle, which is a ZIP file, to a local file path.

- Download the VEM offline bundle, which is a ZIP file, to a local file path.

Procedure

Step 1

Start the vSphere PowerCLI application.

Step 2

Connect to vCenter Server by entering the following command:
Connect-VIServer IP_address –User Administrator –Password XXXXX.

Step 3

Load the image profile offline bundle by entering the following command:
Add-ESXSoftwareDepot image_profile_bundle
Note:
Each image profile bundle can include multiple image profiles.

Step 4

List the image profiles by entering the following command:
[vSphere PowerCLI] > Get-EsxImageProfile

Step 5

Choose the image profile into which the VEM is to be bundled by entering the following command:
New-EsxImageProfile -CloneProfile image_profile_name -Name n1kv-Image

Note:
The image profiles are in read-only format. You must clone the image profile before adding the VEM into it. The n1kv-Image is the cloned image profile of the ESXi-5.0.0-standard.

Step 6

change to Load the Cisco Nexus 1000V offline bundle by entering the following command:
Add-EsxSoftwareDepot VEM_bundle

Note:
The offline bundle is a zip file that includes the n1kv-vib file.

Step 7

Confirm that the n1kv-vib package is loaded by entering the following command:
Get-EsxSoftwarePackage -Name cisco*

Step 8

Bundle the n1kv-package into the cloned image profile by entering the following command:
Add-EsxSoftwarePackage -ImageProfile n1kv-Image -SoftwarePackage n1kv_package_name

Step 9

List all the VIBs into the cloned image profile by entering the following command:

1. $img = Get-EsxImageProfile n1kv-Image

2. $img.vibList

Step 10

Export the image profile to a depot file for future use by entering the following command:
Export-EsxImageProfile –ImageProfile n1kv-Image –FilePath C:\n1kv-Image.zip –ExportToBundle

Step 11

Set up the rule for the host to bott with the image profile by entering the following commands

Note:
Any of the host parameters, such as the MAC address, IPV4 IP address, or domain name, can be used to associate an image profile with the host.

1. New-deployrule -item $img -name rule-test –Pattern “mac=00:50:56:b6:03:c1”

2. Add-DeployRule -DeployRule rule-test

Step 12

Display the configured rule to make sure that the correct image profile is associated with the host by entering the following command:
Get-DeployRuleSet

Step 13

Reboot the host.
The host contacts the Auto-Deploy Server and presents the host boot parameters. The Auto Deploy server checks the rules to find the image profile associated with this host and loads the image to the host’s memory. The host boots from the image.

This example shows how to add the Cisco Nexus 1000V to an ESXi image profile:

vSphere PowerCLI> Set-ExecutionPolicy unrestricted

Execution Policy Change
The execution policy helps protect you from scripts that you do not trust.
Changing the execution policy might expose you to the security risks described
in the about_Execution_Policies help topic. Do you want to change the execution
policy?
[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): Y
vSphere PowerCLI>  Connect-VIServer 10.105.231.40 -User administrator -Password 'xxxxxxxx'

Working with multiple default servers?

Select [Y] if you want to work with more than one default servers. In this
case, every time when you connect to a different server using Connect-VIServer,
the new server connection is stored in an array variable together with the
previously connected servers. When you run a cmdlet and the target servers
cannot be determined from the specified parameters, the cmdlet runs against all
servers stored in the array variable.
Select [N] if you want to work with a single default server. In this case,
when you run a cmdlet and the target servers cannot be determined from the
specified parameters, the cmdlet runs against the last connected server.

WARNING: WORKING WITH MULTIPLE DEFAULT SERVERS WILL BE ENABLED BY DEFAULT
IN A FUTURE RELEASE. You can explicitly set your own preference at any time by
using the DefaultServerMode parameter of Set-PowerCLIConfiguration.

[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): Y

Name                           Port  User
----                           ----  ----
10.105.231.40                  443   administrator

vSphere PowerCLI> Add-EsxSoftwareDepot 'C:\Documents and Settings\Administrator\Desktop\upgrade\229\VMware-ESXi-
5.1.0-799733-depot.zip'

Depot Url
---------
zip:C:\Documents and Settings\Administrator\Desktop\upgrade\229\VMware-ESXi-...

vSphere PowerCLI>  Get-EsxImageProfile

Name                           Vendor          Last Modified   Acceptance Level
----                           ------          -------------   ----------------
ESXi-5.1.0-20121201001s-no-... VMware, Inc.    12/7/2012 7:... PartnerSupported
CN1-CY                         CISCO           4/22/2013 11... PartnerSupported
ESXi-5.1.0-20121204001-stan... VMware, Inc.    12/7/2012 7:... PartnerSupported
ESXi-5.1.0-20121201001s-sta... VMware, Inc.    12/7/2012 7:... PartnerSupported
ESXi-5.1.0-799733-no-tools     VMware, Inc.    8/2/2012 3:0... PartnerSupported
ESXi-5.1.0-20121204001-no-t... VMware, Inc.    12/7/2012 7:... PartnerSupported
ESXi-5.1.0-799733-standard     VMware, Inc.    8/2/2012 3:0... PartnerSupported

vSphere PowerCLI> New-EsxImageProfile -CloneProfile ESXi-5.1.0-799733-standard -Name FINAL

cmdlet New-EsxImageProfile at command pipeline position 1
Supply values for the following parameters:
(Type !? for Help.)
Vendor: CISCO

Name                           Vendor          Last Modified   Acceptance Level
----                           ------          -------------   ----------------
FINAL                          CISCO           8/2/2012 3:0... PartnerSupported

vSphere PowerCLI> Add-EsxSoftwareDepot 'C:\Documents and Settings\Administrator\Desktop\upgrade\229\VEM510-201408170106-BG-release.zip
Depot Url
---------
zip:C:\Documents and Settings\Administrator\Desktop\upgrade\229\cisco-vem-v1...

vSphere PowerCLI> Get-EsxSoftwarePackage cisco*

Name                     Version                        Vendor     Creation Date
----                     -------                        ------     ------------
Cisco-vem-v170-esx       5.2.1.3.1.1.0-3.1.1          Cisco      1/24/2014...

vSphere PowerCLI> Add-EsxSoftwarePackage -SoftwarePackage cisco-vem-v170-esx -ImageProfile FINAL

Name                           Vendor          Last Modified   Acceptance Level
----                           ------          -------------   ----------------
FINAL                          CISCO           1/24/2014 3:... PartnerSupported

vSphere PowerCLI> $img = Get-EsxImageProfile FINAL

Name                     Version                        Vendor     Creation Date
----                     -------                        ------     ------------
scsi-bnx2i               1.9.1d.v50.1-5vmw.510.0.0.7... VMware     8/2/2012 ...
sata-sata-promise        2.12-3vmw.510.0.0.799733       VMware     8/2/2012 ...
net-forcedeth            0.61-2vmw.510.0.0.799733       VMware     8/2/2012 ...
esx-xserver              5.1.0-0.0.799733               VMware     8/2/2012 ...
misc-cnic-register       1.1-1vmw.510.0.0.799733        VMware     8/2/2012 ...
net-tg3                  3.110h.v50.4-4vmw.510.0.0.7... VMware     8/2/2012 ...
scsi-megaraid-sas        5.34-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-megaraid-mbox       2.20.5.1-6vmw.510.0.0.799733   VMware     8/2/2012 ...
scsi-ips                 7.12.05-4vmw.510.0.0.799733    VMware     8/2/2012 ...
net-e1000e               1.1.2-3vmw.510.0.0.799733      VMware     8/2/2012 ...
sata-ahci                3.0-13vmw.510.0.0.799733       VMware     8/2/2012 ...
sata-sata-svw            2.3-3vmw.510.0.0.799733        VMware     8/2/2012 ...
net-cnic                 1.10.2j.v50.7-3vmw.510.0.0.... VMware     8/2/2012 ...
net-e1000                8.0.3.1-2vmw.510.0.0.799733    VMware     8/2/2012 ...
ata-pata-serverworks     0.4.3-3vmw.510.0.0.799733      VMware     8/2/2012 ...
scsi-mptspi              4.23.01.00-6vmw.510.0.0.799733 VMware     8/2/2012 ...
ata-pata-hpt3x2n         0.3.4-3vmw.510.0.0.799733      VMware     8/2/2012 ...
net-s2io                 2.1.4.13427-3vmw.510.0.0.79... VMware     8/2/2012 ...
esx-base                 5.1.0-0.0.799733               VMware     8/2/2012 ...
net-vmxnet3              1.1.3.0-3vmw.510.0.0.799733    VMware     8/2/2012 ...
net-bnx2                 2.0.15g.v50.11-7vmw.510.0.0... VMware     8/2/2012 ...
cisco-vem-v164-esx       4.2.1.2.2.2.0-3.1.1            Cisco      1/24/2014...
scsi-megaraid2           2.00.4-9vmw.510.0.0.799733     VMware     8/2/2012 ...
ata-pata-amd             0.3.10-3vmw.510.0.0.799733     VMware     8/2/2012 ...
ipmi-ipmi-si-drv         39.1-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-lpfc820             8.2.3.1-127vmw.510.0.0.799733  VMware     8/2/2012 ...
ata-pata-atiixp          0.4.6-4vmw.510.0.0.799733      VMware     8/2/2012 ...
esx-dvfilter-generic-... 5.1.0-0.0.799733               VMware     8/2/2012 ...
net-sky2                 1.20-2vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-qla2xxx             902.k1.1-9vmw.510.0.0.799733   VMware     8/2/2012 ...
net-r8169                6.011.00-2vmw.510.0.0.799733   VMware     8/2/2012 ...
sata-sata-sil            2.3-4vmw.510.0.0.799733        VMware     8/2/2012 ...
scsi-mpt2sas             10.00.00.00-5vmw.510.0.0.79... VMware     8/2/2012 ...
sata-ata-piix            2.12-6vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-hpsa                5.0.0-21vmw.510.0.0.799733     VMware     8/2/2012 ...
ata-pata-via             0.3.3-2vmw.510.0.0.799733      VMware     8/2/2012 ...
scsi-aacraid             1.1.5.1-9vmw.510.0.0.799733    VMware     8/2/2012 ...
scsi-rste                2.0.2.0088-1vmw.510.0.0.799733 VMware     8/2/2012 ...
ata-pata-cmd64x          0.2.5-3vmw.510.0.0.799733      VMware     8/2/2012 ...
ima-qla4xxx              2.01.31-1vmw.510.0.0.799733    VMware     8/2/2012 ...
net-igb                  2.1.11.1-3vmw.510.0.0.799733   VMware     8/2/2012 ...
scsi-qla4xxx             5.01.03.2-4vmw.510.0.0.799733  VMware     8/2/2012 ...
block-cciss              3.6.14-10vmw.510.0.0.799733    VMware     8/2/2012 ...
scsi-aic79xx             3.1-5vmw.510.0.0.799733        VMware     8/2/2012 ...
tools-light              5.1.0-0.0.799733               VMware     8/2/2012 ...
uhci-usb-uhci            1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
sata-sata-nv             3.5-4vmw.510.0.0.799733        VMware     8/2/2012 ...
sata-sata-sil24          1.1-1vmw.510.0.0.799733        VMware     8/2/2012 ...
net-ixgbe                3.7.13.6iov-10vmw.510.0.0.7... VMware     8/2/2012 ...
ipmi-ipmi-msghandler     39.1-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-adp94xx             1.0.8.12-6vmw.510.0.0.799733   VMware     8/2/2012 ...
scsi-fnic                1.5.0.3-1vmw.510.0.0.799733    VMware     8/2/2012 ...
ata-pata-pdc2027x        1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
misc-drivers             5.1.0-0.0.799733               VMware     8/2/2012 ...
net-enic                 1.4.2.15a-1vmw.510.0.0.799733  VMware     8/2/2012 ...
net-be2net               4.1.255.11-1vmw.510.0.0.799733 VMware     8/2/2012 ...
net-nx-nic               4.0.558-3vmw.510.0.0.799733    VMware     8/2/2012 ...
esx-xlibs                5.1.0-0.0.799733               VMware     8/2/2012 ...
net-bnx2x                1.61.15.v50.3-1vmw.510.0.0.... VMware     8/2/2012 ...
ehci-ehci-hcd            1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
ohci-usb-ohci            1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
net-r8168                8.013.00-3vmw.510.0.0.799733   VMware     8/2/2012 ...
esx-tboot                5.1.0-0.0.799733               VMware     8/2/2012 ...
ata-pata-sil680          0.4.8-3vmw.510.0.0.799733      VMware     8/2/2012 ...
ipmi-ipmi-devintf        39.1-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-mptsas              4.23.01.00-6vmw.510.0.0.799733 VMware     8/2/2012 ...

vSphere PowerCLI> Export-EsxImageProfile -ImageProfile FINAL -FilePath 'C:\Documents and Settings\Administrator\Desktop\FINAL.zip' -ExportToBundle
vSphere PowerCLI>  New-deployrule -item $img -name rule-test –Pattern “mac=00:50:16:26:13:c2”
vSphere PowerCLI] > Add-DeployRule -DeployRule rule-test
[vSphere PowerCLI] > Get-DeployRuleSet
Name : rule-test
PatternList : {mac=00:50:16:26:13:c2}
ItemList : {FINAL}

Installing the VEM Software on a Stateless ESXi Host Using esxcli

Before You Begin

- When you enter the esxcli software vib install command on an ESXi 5.0.0 host, note that the following message appears:

Message: WARNING: Only live system was updated, the change is not persistent.

Procedure

Step 1

Display the VMware version and build number by entering the following commands:

- vmware -v

- vmware -l

Step 2

Log in to the ESXi stateless host.

Step 3

Copy the offline bundle to the host by entering the the following command:
esxcli software vib install -d file_path/offline_bundle
Note:
If the host is an ESXi 5.0.0 stateful host, the “Message: Operation finished successfully” line appears.

Step 4

Verify that the VIB has installed by entering the following command:
esxcli software vib list | grep cisco

Step 5

Change to Check that the VEM agent is running by entering the following command:
vem status -v

Step 6

Display the VEM version, VSM version, and ESXi version by entering the following command:
vemcmd show version

Step 7

Display the ESXi version and details about passthrough NICs by entering the following command:
vem version -v

Step 8

Add the host to the DVS by using the vCenter Server.

Step 9

On the VSM, verify that the VEM software has been installed by entering the following command:
show module

This example shows how to install VEM software on a stateless host using esxcli.

~ # vmware -v
VMware ESXi 5.0.0 build-843203
~ #
~ # vmware -l
VMware ESXi 5.0.0 U2

~ # esxcli software vib install –d /vmfs/volumes/newnfs/MN-VEM/VEM500-201408170101-BG-release.zip
Installation Result
Message: WARNING: Only live system was updated, the change is not persistent.
Reboot Required: false
VIBs Installed: Cisco_bootbank_170-5.2.1.3.1.1.0-3.0.1
VIBs Removed:
VIBs Skipped:

~ # esxcli software vib list | grep cisco
cisco-vem-v170-esx     5.2.1.3.1.1.0-3.2.1                 Cisco   PartnerSupported  2014-08-18

~ # vem status -v
Package vssnet-esxmn-release
Version 5.2.1.3.1.1.0-3.0.1
Build 1
Date Thu Aug 14 23:59:55 PDT 2014

VEM modules are loaded

Switch Name      Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch0         128         6           128               1500    vmnic0
DVS Name         Num Ports   Used Ports  Configured Ports  MTU     Uplinks
dao-gold         1024        15          1024              1500    vmnic4

VEM Agent (vemdpa) is running
~ # vemcmd show version
vemcmd show version
VEM Version: 5.2.1.3.1.1.0-3.0.1
VSM Version: 5.2(1)SV3(1.1) [build 5.2(1)SV3(1.1)]
System Version: VMware ESXi 5.0.0 Releasebuild-1311175
ESX Version Update Level: 3

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

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

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

Installing the VEM Software on a Stateless ESXi Host Using VUM

Before You Begin

- Make sure that the VUM patch repository has the VEM software downloaded.

Procedure

Step 1

In vCenter Server, choose Home > Update Manager > Configuration > ESX host/Cluster settings.
The ESX Host/Cluster Settings window opens.

Step 2

Check the PXE Booted ESXi Host Settings check box.
ESX Host/Cluster Settings Window

Step 3

Add the host to the DVS by using vCenter Server.

Installing a VSM on the Cisco Nexus Cloud Services Platform

You can install the VSM on the Cisco Nexus Cloud Services Platform and move from Layer 2 to Layer 3 connectivity.

Note

VEMs do not register to the VSM before a vmkernel interface (vmk) is migrated to a Layer 3 control-capable port profile. You must migrate a vmk to the Layer 3 port profile after migrating host vmnics to Ethernet port profiles.

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.

Before You Begin

Copy the ISO file to the bootflash:repository/ of the Cisco Nexus Cloud Services Platform.

Procedure

Step 1

Create a virtual service blade.

switch(config)# show virtual-service-blade summary

---------------------------------------------------------------------------------
Name        HA-Role       HA-Status     Status               Location
---------------------------------------------------------------------------------
switch(config)# virtual-service-blade vsm-1
switch(config-vsb-config)# virtual-service-blade-type new nexus-n1000v-dk9.5.2.1.SV3.1.1.iso
switch(config-vsb-config)# show virtual-service-blade summary

--------------------------------------------------------------------------------------
Name        HA-Role       HA-Status     Status                   Location
--------------------------------------------------------------------------------------
vsm-1       PRIMARY       NONE          VSB NOT PRESENT          PRIMARY
vsm-1       SECONDARY     NONE          VSB NOT PRESENT          SECONDARY

switch(config-vsb-config)#

Step 2

Configure the control, packet, and management interface VLANs for static and flexible topologies.

switch(config-vsb-config)# interface management vlan 100
switch(config-vsb-config)# interface control vlan 101
switch(config-vsb-config)# interface packet vlan 101

Step 3

Configure the Cisco Nexus 1000V on the Cisco Nexus 1010.

switch(config-vsb-config)# enable
Enter vsb image: [nexus-1000v.5.2.1.SV3.1.1.iso]
Enter domain id[1-1023]: 127
Enter SVS Control mode (L2 / L3): [L3] L2
Management IP version [V4/V6]: [V4]
Enter Management IP address: 192.0.2.79
Enter Management subnet mask: 255.255.255.0
IPv4 address of the default gateway: 192.0.2.1
Enter HostName: n1000v
Enter the password for ‘admin’: ********
Note: VSB installation is in progress, please use show virtual-service-blade commands to check the installation status.
switch(config-vsb-config)#

Step 4

Display the primary and secondary VSM status.

switch(config-vsb-config)# show virtual-service-blade summary

--------------------------------------------------------------------------------------
Name        HA-Role       HA-Status     Status                   Location
--------------------------------------------------------------------------------------
vsm-1       PRIMARY       NONE          VSB POWER ON IN PROGRESS PRIMARY
vsm-1       SECONDARY     ACTIVE        VSB POWERED ON           SECONDARY

Step 5

Log in to the VSM.

switch(config)# virtual-service-blade vsm-1
switch(config-vsb-config)# login virtual-service-blade vsm-1
Telnet escape character is ‘^\’.
Trying 192.0.2.18...
Connected to 192.0.2.18.
Escape character is ‘^\’.

Nexus 1000v Switch
n1000v login: admin
Password:
Cisco Nexus operating System (NX-OS) Software
TAC support: http://www/cisco.com/tac
Copyright (c) 2002-2012, 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#

Step 6

Change svs mode from Layer 2 to Layer 3 in the Cisco Nexus 1000V.
Note:
The configuration in the highlighted code is optional.

switch(config)# svs-domain
switch(config-svs-domain)# no control vlan
Warning: Config saved but not pushed to vCenter Server due to inactive connection!
switch(config-svs-domain)# no packet vlan
Warning: Config saved but not pushed to vCenter Server due to inactive connection!
switch(config-svs-domain)# svs mode L3 interface mgmt0
Warning: Config saved but not pushed to vCenter Server due to inactive connection!
switch(config-svs-domain)# show svs domain
switch(config-svs-domain)# show svs domain
SVS domain config
Domain id: 101
Control vlan: NA
Packet vlan:  NA
L2/L3 Control mode: L3
L3 control interface: mgmt0
Status: Config push to VC successful.
switch(config-svs-domain)#

Feature History for Installing the Cisco Nexus 1000V

The following table lists the release history for installing the Cisco Nexus 1000V.

Feature Name

Releases

Feature Information

VEM Installation 5.1

4.2(1)SV2(2.1)

Installing VEM software remotely or locally on a VMware 5.1 host using the CLI is now supported.

Standard and Custom installation application

4.2(1)SV2(1.1)

Installation Application updated with a Standard and Custom version

Updated installation application

4.2(1)SV1(5.2)

Added screens to the Java application.

VSM and VEM Installation

4.2(1)SV1(5.1)

Java applications introduced for VSM and VEM installation.

Installing the Cisco Nexus 1000V

4.0(1)SV1(1)

Introduced in this release.

Part III. Upgrade Procedures

- Upgrading the Cisco Nexus 1000V

- Upgrading a Standalone VSM

Chapter 4. Upgrading the Cisco Nexus 1000V

This chapter contains the following sections:

- Prerequisite to Upgrading a VSM to a 3-GB Hard Disk Drive

- Guidelines and Limitations for Upgrading the Cisco Nexus 1000V

- Upgrade Procedures

- Upgrade Types

- Simplified Upgrade Process

- Upgrading from Releases 4.2(1)SV1(4x), 4.2(1)SV1(5.1x), or 4.2(1)SV1(5.2x) to the Current Release

- Feature History for Upgrading the Cisco Nexus 1000V

Upgrade Software Sources

Note

An interactive upgrade tool has been provided to assist you in determining the correct upgrade steps based on your current environment and the one to which you want to upgrade.

You can obtain your upgrade-related software from the following sources listed in this table:

Obtaining the Upgrade Software

Source

Description

Cisco

Download the current release of the Cisco Nexus 1000V software from Click Here .

VMware

Download the VMware software from the VMware website.

The current Cisco Nexus 1000V software release image for VMware Release 5.1 is at the VMware web site:

- Online portal for VMware Update Manager (VUM): Click Here

- Offline patch portal: Click Here

For information about your software and platform compatibility, see the Cisco Nexus 1000V and VMware Compatibility Information document.

Information about NetFlow Upgrade

With Distributed NetFlow, the switch sends NetFlow export packets directly from the VEMs to the collectors.

During the upgrade process, the switch migrates from the old centralized model to the new distributed model. As part of this migration, unsupported commands are removed and/or converted as part of the VSM upgrade. The new and changed commands are available as soon as all of the VEMs are upgraded and the feature level is updated. Additionally, the following new requirements are imposed on the network reachability:

- The collectors must be Layer 3 reachable from at least one vmknic on each VEM host.

- Strict Reverse Path Forwarding (RPF) might need to be disabled on the routers between the VEM hosts and the collectors.

These are the removed, converted, and new commands:

Command

Change

cache size

Removed.

The cache size is no longer user configurable.

timeout active

timeout inactive

Converted.

The configured timeout active and timeout inactive values are consolidated and converted to be the flow timeout active and flow timeout inactive values. The new consolidated timeouts are set to the maximum of the old individual timeouts.
Note:
After conversion, subsequent changes to the timeouts do not apply to the existing interface configurations on non-upgraded VEMs.

source mgmt

Converted.

The configured source mgmt values are converted to be the source lc-exp values. The NetFlow export packets are no longer sent from the VSM’s mgmt0 interface.

netflow layer2-switched input

New.

The netflow layer2-switched input command configures the Layer 2 default record.

match datalink

New.

The match datalink command configures the Layer 2 record fields.

Before You Begin

The Virtual Service Domain (VSD) feature is no longer supported and must be removed before upgrading to Release 5.2(1)SV3(1.1).

The Upgrade Application cannot be used for the direct upgrade of the Virtual Supervisor Module(VSMs) from Releases 4.2(1)SV1(4), 4.2(1)SV1(5.1), 4.2(1)SV1(5.2) to the current release.

A pair of VSMs in a high availability (HA) pair is required in order to support a nondisruptive upgrade.

A system with a single VSM can only be upgraded in a disruptive manner.

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

The upgrade process is irrevocable. After the software is upgraded, you can downgrade by removing the current installation and reinstalling the software. For more information, see the “Recreating the Installation” section of the Cisco Nexus 1000V Troubleshooting Guide.

A combined upgrade of ESX and the Virtual Ethernet Module (VEM) in a single maintenance mode is supported in this release. A combined upgrade requires at least vCenter 5.0 Update 1 whether you upgrade manually or are using the VMware Update Manager.

You can manually upgrade the ESX and VEM in one maintenance mode as follows:

1. Place the host in maintenance mode.

2. Upgrade ESX to 5.0 or 5.1 as needed.

3. Install the VEM vSphere Installation Bundle (VIB) while the host is still in maintenance mode.

4. Remove the host from maintenance mode.

The steps for the manual combined upgrade procedure do not apply for VMware Update Manager (VUM)-based upgrades.

You can abort the upgrade procedure by pressing Ctrl-C.

Prerequisites for Upgrading VSMs

Upgrading VSMs has the following prerequisites:

- Close any active configuration sessions before upgrading the Cisco Nexus 1000V software.

- Save all changes in the running configuration to the startup configuration.

- Save a backup copy of the running configuration in external storage.

- Perform a VSM backup. For more information, see the “Configuring VSM Backup and Recovery” chapter in the Cisco Nexus 1000V System Management Configuration Guide.

- Use the VSM management IP address to log into VSM and perform management tasks.

Important:
If you connect to a VSM using the VSA serial port or the connect host from the Cisco Integrated Management Control (CIMC), do not initiate commands that are CPU intensive, such as copying image from the TFTP server to bootflash or generating a lot of screen output or updates. Use the VSA serial connections, including CIMC, only for operations such as debugging or basic configuration of the VSA.

Prerequisites for Upgrading VEMs

Caution

If VMware vCenter Server is hosted on the same ESX/ESXi host as a Cisco Nexus 1000V VEM, a VUM-assisted upgrade on the host fails. You should manually VMotion the vCenter Server VM to another host before you perform an upgrade.

Note

When you perform any VUM operation on hosts that are a part of a cluster, ensure that VMware HA, VMware fault tolerance (FT), and VMware Distributed Power Management (DPM) features are disabled for the entire cluster. Otherwise, VUM will fail to install the hosts in the cluster.

- If you have VXLAN Gateway installed in your deployment, we recommend that you upgrade the VXLAN gateway service module after upgrading the VSM and before upgrading the VEM. This recommendation applies to upgrades to Release 5.2(1)SV3(1.1) only.

- You are logged in to the VSM command-line interface (CLI) in EXEC mode.

- 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 VEM Software. For more information, see the Cisco Nexus 1000V and VMware Compatibility Information document.

- If you need to migrate a vSphere host from ESX to ESXi, do it before the Cisco Nexus 1000V upgrade.

- You have placed the VEM software file in /tmp on the vSphere host. Placing it in the root (/) directory might interfere with the upgrade. Make sure that the root RAM disk has at least 12 MB of free space by entering the vdf command.

- On your upstream switches, you must have the following configuration.

- On Catalyst 6500 Series switches with the Cisco IOS software, enter the portfast trunk command or the portfast edge trunk command.

- On Cisco Nexus 5000 Series switches with the Cisco NX-OS software, enter the spanning-tree port type edge trunk command.

- On your upstream switches, we highly recommend that you globally enable the following:

- Global BPDU Filtering

- Global BPDU Guard

- On your upstream switches where you cannot globally enable BPDU Filtering and BPDU Guard, we highly recommend that you enter the following commands:

- spanning-tree bpdu filter

- spanning-tree bpdu guard

- The collectors must be L3 reachable from at least one vmknic on each VEM host.

- Strict Reverse Path Forwarding (RPF) may require disabling on the routers between the VEMs and the collectors.

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

Prerequisite to Upgrading a VSM to a 3-GB Hard Disk Drive

Cisco Nexus 1000V for VMware Release 5.2(1)SV3(1.1) and higher requires a minimum of 3-GB of hard disk drive (HDD) space. If you are upgrading from a previous release to Release 5.2(1)SV3(1.1) and you have a 2-GB HDD, you must upgrade to a 3-GB HDD.

- Upgrading Hard Disk Drive Space from 2 GB to 3 GB on a VSM as a VM

- Upgrading Hard Disk Drive Space from 2 GB to 3 GB on a VSM on a VSB

- Verifying that the VSM has 3-GB of Hard Disk Drive Storage

Upgrading Hard Disk Drive Space from 2 GB to 3 GB on a VSM as a VM

We recommend that you upgrade the hard disk drive (HDD) space from 2 GB to 3 GB on a VSM VM before upgrading VSM to Release 5.2(1)SV3(1.1) or later.

Before You Begin

Make sure that the Cisco Nexus 1000V VSMs are running Release 4.2(1)SV2(1.1) or 4.2(1)SV2(2.1).

Make sure that the existing Cisco Nexus 1000V VSMs are an HA pair with 2 GB HDD.

Procedure

Step 1

Remove the existing standby VSM.

1. Right-click on the VSM VM and power off the VM.

2. Remove it from the Virtual Center inventory.

Step 2

Bring up the new standby VSM VM (with 3-GB HDD) with the same release as the active VSM using ISO.
For example, if the active VSM is running Release 4.2(1)SV2(1.1), bring up the new standby VSM with Release 4.2(1)SV2(1.1).

1. Confirm that the same port profiles are used as the primary VSM for 3 network interfaces.

2. Provision a 3-GB HDD with a minimum of 2 GB of RAM reserved and allocated, and has a minimum CPU speed of 1600 MHz.

See Installing the Software from the ISO Image for more information.

Step 3

Power on the standby VSM.

1. Confirm the HA role is set as Secondary.

2. Configure the Domain ID is the same as the Primary VSM.

Step 4

After the HA pair is formed, perform a system switchover to make the standby VSM become the active VSM.

Step 5

Remove the current standby VSM.

1. Right-click on the VSM VM and power off the VM.

2. Remove it from the Virtual Center inventory.

Step 6

Change the Active VSM system redundancy role to Primary system by entering system redundancy role primary.

Step 7

Copy the config to start-up and perform a reload.

Step 8

Verify the current role by entering show system redundancy status. Role should be set as Primary.

Step 9

Bring up the new standby VSM VM (with 3-GB HDD) using ISO following Step 2 and Step 3.

Step 10

After the HA pair is formed, verify it by entering show system internal flash. It should reflect the VSM with 3-GB HDD.

What to Do Next

Perform an in-service software upgrade (ISSU) to Release 5.2(1)SV3(1.1) or later.

Upgrading Hard Disk Drive Space from 2 GB to 3 GB on a VSM on a VSB

We recommend that you upgrade the VSM that is deployed on a CSP from a 2-GB hard disk drive (HDD) to a 3-GB HDD.

Procedure

Step 1

Identify the standby VSM by entering the show virtual-service-blade summary command.

N1110# show virtual-service-blade summary

Name                    HA-Role     HA-Status     Status                Location
-------------------------------------------------------------------------------
switch                  PRIMARY     ACTIVE      VSB POWERED ON           PRIMARY
switch                  SECONDARY   STANDBY     VSB POWERED ON           SECONDARY

N1110#

The output shows that the standby VSM is running on the secondary Cisco Nexus 1010 Virtual Service Blade (VSB).

Step 2

Shut down and delete the standby VSM on the secondary VSB.

1. N1110# configure terminal

2. N1110#(config)virtual-service-blade name switch

3. N1110#(config-vsb-config)shutdown secondary

4. N1110#(config-vsb-config)no enable secondary

Step 3

Bring up the new secondary VSB with Release 4.2(1)SV2(1.1) using ISO. See the Cisco Nexus 1100 Series Virtual Services Appliances Deployment Guide White Paper for more information.

Step 4

Change the disk size to 3 GB or more.

N1110(config-vsb-config)# disksize 4

Step 5

Enable the standby VSM on the secondary VSB. See the Cisco Nexus 1100 Series Virtual Services Appliances Deployment Guide White Paper for more information.

N1110# sh virtual-service-blade summary

-------------------------------------------------------------------------------
Name                    HA-Role     HA-Status   Status                   Location
-------------------------------------------------------------------------------
switch                  PRIMARY     ACTIVE      VSB POWERED ON           PRIMARY
switch                  SECONDARY   NONE        VSB NOT PRESENT          SECONDARY
switch1                 PRIMARY     NONE        VSB NOT PRESENT          PRIMARY
switch1                 SECONDARY   STANDBY     VSB POWERED ON           SECONDARY

N1110#

Step 6

Perform a system switchover to make the active VSM on the primary VSB become the standby VSM. To do this, enter the system switchover command on the active VSM.

N1110# system switchover
N1110(config-vsb-config)# show virtual-service-blade summary

-------------------------------------------------------------------------------
Name                 HA-Role     HA-Status   Status                   Location
-------------------------------------------------------------------------------
switch                  PRIMARY     STANDBY     VSB POWERED ON           PRIMARY
switch                  SECONDARY   NONE        VSB NOT PRESENT          SECONDARY
switch1                 PRIMARY     NONE        VSB NOT PRESENT          PRIMARY
switch1                 SECONDARY   ACTIVE      VSB POWERED ON           SECONDARY

N1110(config-vsb-config#

Step 7

After the HA pair is formed, shutdown and delete the standby VSM on the primary VSB.

N1110(config)# virtual-service-blade switch
N1110(config-vsb-config)# shutdown primary
N1110(config-vsb-config)# no enable primary

N1110(config-vsb-config)# show virtual-service-blade summary

-------------------------------------------------------------------------------
Name                HA-Role     HA-Status   Status                   Location
-------------------------------------------------------------------------------
switch                  PRIMARY     NONE        VSB NOT PRESENT          PRIMARY
switch                  SECONDARY   NONE        VSB NOT PRESENT          SECONDARY
switch1                 PRIMARY     NONE        VSB NOT PRESENT          PRIMARY
switch1                 SECONDARY   ACTIVE      VSB POWERED ON           SECONDARY

N1110(config-vsb-config)#

Step 8

Bring up the new VSB with Release 4.2(2)SV2(1.1) using ISO. See the Cisco Nexus 1100 Series Virtual Services Appliances Deployment Guide White Paper for more information.

Step 9

Enable the primary VSM. See the Cisco Nexus 1100 Series Virtual Services Appliances Deployment Guide White Paper for more information.

N1110(config)# show virtual-service-blade summary

-------------------------------------------------------------------------------
Name                    HA-Role     HA-Status   Status                   Location
-------------------------------------------------------------------------------
switch                  PRIMARY     NONE        VSB NOT PRESENT          PRIMARY
switch                  SECONDARY   NONE        VSB NOT PRESENT          SECONDARY
switch1                 PRIMARY     STANDBY     VSB POWERED ON           PRIMARY
switch1                 SECONDARY   ACTIVE      VSB POWERED ON           SECONDARY

N1110(config-vsb-config)#

Step 10

Verify that the HDD size has changed. The following example shows that the HDD size is 4 GB.

N1110(config)# show system internal flash

Mount-on                  1K-blocks      Used   Available   Use%  Filesystem
/                            307200     87628      219572     29   /dev/root
/proc                             0         0           0      0   proc
/isan                        614400    243076      371324     40   none
/var/sysmgr                  512000     18896      493104      4   none
/var/sysmgr/ftp              204800        40      204760      1   none
/dev/shm                     358400     30268      328132      9   none
/volatile                     20480         0       20480      0   none
/debug                         2048         8        2040      1   none
/dev/mqueue                       0         0           0      0   none
/mnt/cfg/0                   326681      8360      301455      3   /dev/hda5
/mnt/cfg/1                   326681      8359      301456      3   /dev/hda6
/var/sysmgr/startup-cfg      409600      1168      408432      1   none
/dev/pts                          0         0           0      0   devpts
/mnt/pss                     326671      8625      301178      3   /dev/hda3
/bootflash                  3122988    151756     2812592      6   /dev/hda4
/bootflash_sup-remote       3122992    151760     2812592      6   127.1.1.1:/mnt/bootflash/

What to Do Next

Perform an in-service software upgrade (ISSU) to Release 5.2(1)SV3(1.1) or later.

Verifying that the VSM has 3-GB of Hard Disk Drive Storage

You can display the system internal flash to verify that you have a minimum of 3-GB of hard disk drive space.

Procedure

Step 1

Display the system internal flash.

switch# show system internal flash
Mount-on                  1K-blocks      Used   Available   Use%  Filesystem
/                            307200     77808      229392     26   /dev/root
/mnt/pss                     248895      8164      227879      4   /dev/sda3
/proc                             0         0           0      0   proc
/isan                        614400    372236      242164     61   none
/var/sysmgr                 1048576    488704      559872     47   none
/var/sysmgr/ftp              204800        52      204748      1   none
/nxos/tmp                     20480         0       20480      0   none
/dev/shm                     358400     89660      268740     26   none
/volatile                     20480         0       20480      0   none
/debug                         2048       128        1920      7   none
/dev/mqueue                       0         0           0      0   none
/mnt/cfg/0                   248895      4494      231551      2   /dev/sda5
/mnt/cfg/1                   241116      4493      224175      2   /dev/sda6
/var/sysmgr/startup-cfg      409600      5892      403708      2   none
/dev/pts                          0         0           0      0   devpts
/mnt/pss                     248895      8164      227879      4   /dev/sda3
/bootflash                  2332296   1918624      295196     87   /dev/sda4
/sys                              0         0           0      0   sysfs

Step 2

Make sure that the number of blocks allocated to the /mnt/cfg/0, /mnt/cfg/1, /mnt/pss, and /bootflash partitions equals at least 3 GB.

Guidelines and Limitations for Upgrading the Cisco Nexus 1000V

Before attempting to migrate to any software image version, follow these guidelines:

Caution

During the upgrade process, the Cisco Nexus 1000V does not support any new additions such as modules, virtual NICs (vNICs), or VM NICs and does not support any configuration changes. VM NIC and vNIC port-profile changes might render VM NICs and vNICs in an unusable state.

Note

We recommended that you use vSphere 5.0 Update 1 or later instead of vSphere 5.0.

- You are upgrading the Cisco Nexus 1000V software to the current release.

- Scheduling—Schedule the upgrade when your network is stable and steady. Ensure that everyone who has access to the switch or the network is not configuring the switch or the network during this time. You cannot configure a switch during an upgrade.

- Hardware—Avoid power interruptions to the hosts that run the VSM VMs during any installation procedure.

- Connectivity to remote servers — do the following:

- Copy the kickstart and system images from the remote server to the Cisco Nexus 1000V.

- Ensure that the switch has a route to the remote server. The switch and the remote server must be in the same subnetwork if you do not have a router to route traffic between subnets.

- Software images— Do the following:

- Make sure that the system and kickstart images are the same version.

- Retrieve the images in one of two ways:

- Locally—Images are locally available on the upgrade CD-ROM/ISO image.

- Remotely—Images are in a remote location and you specify the destination using the remote server parameters and the filename to be used locally.

- Commands to use—Do the following:

- Verify connectivity to the remote server by using the ping command.

- If you are using Layer 3 mode for VSM-to-VEM connectivity, verify the IP address on the Layer 3 control interface using the show interface {control0 | mgmt0} command. If the IP address is missing, re-apply the IP address configuration on the corresponding Layer 3 control interface.

- Use the install all command to upgrade your software. This command upgrades the VSMs.

- Do not enter another install all command while running the installation. You can run commands other than configuration commands.

- During the VSM upgrade, if you try to add a new VEM or any of the VEMs are detached due to uplink flaps, the VEM attachment is queued until the upgrade completes.

- If VEMs get removed after the VSM upgrade, use the system switchover command to perform a system switchover after the HA pair is established.

Note

If the ESX hosts are not compatible with the software image that you install on the VSM, a traffic disruption occurs in those modules, depending on your configuration. The install all command output identifies these scenarios. The hosts must be at the right version before the upgrade.

Before upgrading the VEMs, note these guidelines and limitations.

Note

It is your responsibility to monitor and install all the relevant patches on VMware ESX hosts.

- The VEM software can be upgraded manually using the CLI or upgraded automatically using VUM.

- During the VEM upgrade process, VEMs reattach to the VSM.

- Connectivity to the VSM can be lost during a VEM upgrade when the interfaces of a VSM VM connect to its own Distributed Virtual Switch (DVS).

- If you are upgrading a VEM using a Cisco Nexus 1000V bundle, follow the instructions in your VMware documentation. For more details about VMware bundled software, see the Cisco Nexus 1000V and VMware Compatibility Information document.

Caution

Do not enter the vemlog, vemcmd, or vempkt commands during the VEM upgrade process because these commands impact the upgrade.

Note

For ESXi 5.1 update 2 and later, the minimum versions are as follows:

- VMware vCenter Server 5.1, 799731

- VMware Update Manager 5.1, 782803

For ESXi 5.5 update 1 and later, the minimum versions are as follows:

- VMware vCenter Server 5.0.0, 455964

- VMware Update Manager 5.0.0 432001

If you plan to do a combined upgrade of ESX and VEM, the minimum vCenter Server/VUM version required is 623373/639867.

This procedure is different from the upgrade to Release 4.2(1)SV1(4). In this procedure, you upgrade the VSMs first by using the install all command and then you upgrade the VEMs.

- You can upgrade the hosts in the DVS a few at a time across multiple maintenance windows. The only exception is if you are upgrading the VEM alone using VUM with the ESX version unchanged.

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.

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)SV2(1.1) or later at the following URL: Click Here

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. Upgrading 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. Upgrading 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) with a vSphere release 5.0 GA, patches, or updates.

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

2. Upgrading VEMs from releases 4.2(1)SV1(4x) 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.

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

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

If you are running this configuration

Follow these steps

With vSphere 4.1 GA, patches, or updates.

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

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

3. Upgrading VEMs from releases 4.2(1)SV1(5.1x) 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.

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. Upgrading 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.

With ESX version upgrade.

Installing and Upgrading VMware

Upgrade Types

Upgrades can be one of three types:

- Upgrade of the Cisco Nexus 1000V version only, with vSphere version intact. See Upgrading the Cisco Nexus 1000V Only.

- Upgrade of both vSphere and Cisco Nexus 1000V versions together. See Combined Upgrade of vSphere and Cisco Nexus 1000V.

- Upgrade of vSphere version only, with the Cisco Nexus 1000V version intact. See the Installing and Upgrading VMware appendix.

- Upgrading the Cisco Nexus 1000V Only

- Combined Upgrade of vSphere and Cisco Nexus 1000V

- Reserving the Memory and CPU on the Virtual Supervisor Module Virtual Machine

- Reserving the Memory and CPU for the Virtual Supervisor Module in VSB on the Cloud Services Platform

- VEM Upgrade Procedures

Upgrading the Cisco Nexus 1000V Only

You must complete the following procedures to upgrade the Cisco Nexus 1000V only.

1. Upgrade the VSM. See VSM Upgrade Procedures.

2. Upgrade the VEM.

- For Stateless ESXi, see Installing the VEM Software on a Stateless ESXi Host.

- For a VUM-based upgrade of a Stateful ESX or ESXi, use a host upgrade baseline with the VEM depot. See Upgrading the ESXi Hosts to Release 5.x.

- For a stateful manual upgrade using the esxupdate or esxcli commands, see Installing ESXi 5.1 Host Software Using the CLI.

Combined Upgrade of vSphere and Cisco Nexus 1000V

You can perform a combined upgrade of vSphere and Cisco Nexus 1000V.

If any of the hosts are running ESX 4.0 when the VSM is upgraded, the installer command displays that some VEMs are incompatible. You can proceed if you are planning a combined upgrade of the Cisco Nexus 1000V 4.2(1)SV1(4), 4.2(1)SV1(4a), 4.2(1)SV2(2.1), and ESX 4.0/4.1 to current release with ESX 5.0/5.1/5.5.

Note

Starting with the 4.2(1)SV2(2.1) release, during an VSM upgrade, if you have incompatible hosts attached to the VSM you will be allowed to upgrade from the current release of Cisco Nexus 1000V software to the later releases. You will see a warning message on incompatible host when you upgrade. Ignore the warning message and continue with the upgrade and the VSM will be upgraded to the latest version. You can perform a combined upgrade on the incompatible hosts.

Note

A combined upgrade is supported only for vCenter Server 5.0 Update 1 or later.

The following procedures are necessary to perform a combined upgrade.

1. Upgrading the vCenter Server

2. Upgrading the vCenter Update Manager to Release 5.5

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

4. Creating an Upgrade ISO with a VMware ESX Image and a Cisco Nexus 1000V VEM Image

5. Upgrading the ESXi Hosts to Release 5.x

6. Verifying the Build Number and Upgrade

Reserving the Memory and CPU on the Virtual Supervisor Module Virtual Machine

From the current release of Cisco Nexus 1000V software, the VSM requires 4-GB RAM and two 2-GHz vCPUs reservation to accommodate the new scalability limits.

Note

When you install the Cisco Nexus 1000V software VSM through the OVA files for the first time, the RAM and CPU reservations are automatically reflected.

To upgrade to the current release of Cisco Nexus 1000V software and update the CPU and RAM reservations, use the following procedure:

Procedure

Step 1

Upgrade from the previous release of Cisco Nexus 1000V software to the current release of Cisco Nexus 1000V software.

Step 2

Once the upgrade is complete, power off the secondary VSM.

Step 3

Change the RAM size from 2 or 3 GB to 4 GB and change the RAM reservation from 2 or 3 GB to 4 GB.

Step 4

Under CPU settings, change the number of vCPUs to 2 and change the CPU reservation from 1.5 GHz to 2 GHz.

Step 5

Power on the secondary VSM.

Step 6

Perform a system switch over to get the secondary VSM as Active.

Step 7

Power off the primary VSM and repeat steps 3 to 6.

Step 8

After the primary and secondary VSM have the correct CPU and RAM reservations, the VSM is able to accommodate the scale numbers that are supported on Release 5.2(1)SV3(1.1).
Note:
You do not have to change the CPU and RAM reservations to continue to support for the scale numbers supported in releases before Release 5.2(1)SV3(1.1).

Reserving the Memory and CPU for the Virtual Supervisor Module in VSB on the Cloud Services Platform

To change the memory reservations in the VSM VSB, use the following procedure:

Before You Begin

From the current release of Cisco Nexus 1000V software, the VSM requires 4-GB RAM and two vCPUs to accommodate the new scalability limits.

Procedure

Step 1

Login to the Cloud Services Platform command prompt.

Step 2

Enter the VSM configuration mode.

Step 3

Change the RAM size to 4 GB and change the vCPU number to 2.

Note:
With Cisco Nexus Cloud Services Platform Release 4.2(1)SP1(6.1) and later, the virtual service blades can remain powered on when you change the RAM size. In Cisco Nexus Cloud Services Platform releases earlier than 4.2(1)SP1(6.1), the primary/secondary virtual service blades must be powered off before you can change the RAM size.

Step 4

Copy the running configuration to the startup configuration.

Step 5

Reboot the secondary VSM VSB by using the shut and no shut commands.

Step 6

Check if the secondary VSM has 4-GB RAM and two vCPUs.

Step 7

Perform a system switch over from the primary VSM to make the secondary VSM as active with 4-GB RAM and two vCPUs.
The primary VSM reboots and is in the standby state with 4-GB RAM and two vCPUs.

- Reserving the Memory and CPU for the Virtual Supervisor Module in VSB on the Cloud Services Platform Using the CLI

Reserving the Memory and CPU for the Virtual Supervisor Module in VSB on the Cloud Services Platform Using the CLI

To change the memory reservations in the VSM VSB using the CLI, use the following procedure:

Before You Begin

From the current release of Cisco Nexus 1000V software, VSM requires 3 GB RAM reservation to accommodate the new scalability limits.

Procedure

Command or Action

Purpose

Step 1

CSP configure terminal

Enters the global configuration mode.

Step 2

CSP(config)# virtual-service-blade VSM for the current release

Enters the VSM configuration mode.

Step 3

CSP(config-vsb-config)# ramsize 4096

Change the RAM size to 4 GB.

Note:
The virtual service blade is powered ON. Restart the VSB to reflect the change in RAM size. Perform a shutdown using the shutdown and no shutdown commands.

Step 4

CSP(config-vsb-config)# numcpu 2

Changing the number of CPUs to 2.

Step 5

CSP(config-vsb-config)# copy running-config startup-config

Copies the running configuration to the startup configuration.

Step 6

CSP(config-vsb-config)# shutdown secondary

Shuts down the secondary VSB.

Step 7

CSP(config-vsb-config)# no shutdown secondary

Applies the RAM and vCPU changes.

Step 8

VSM# system switchover

Performs a system switch over from primary VSM to make the secondary VSM as active with 4-GB RAM and two vCPUs.

Step 9

VSM(standby)# show system resources

Displays that the secondary VSM has 4-GB of RAM and two vCPUs.

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.

- ISO file—If a local ISO file is passed to the install all command, the kickstart and system images are extracted from the ISO file.

In-Service Software Upgrades on Systems with Dual VSMs

Note

Performing an In-service Upgrade (ISSU) from Cisco Nexus 1000V Release 4.2(1)SV1(4x), 4.2(1)SV1(5.1x), 4.2(1)SV1(5.2x) to the current release of Cisco Nexus 1000V is not supported.

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

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.

ISSU Process

ISSU VSM Switchover

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

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. Alternatively, if a local ISO file is passed to the install all command instead, the kickstart and system images are extracted from the file.

- 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.

VEM Upgrade Procedures

- VUM Upgrade Procedures

- Generate an upgrade ISO. See Creating an Upgrade ISO with a VMware ESX Image and a Cisco Nexus 1000V VEM Image.

- Set up VUM baselines. See Upgrading the ESXi Hosts to Release 5.x.

- Initiate an upgrade from VUM. See Upgrading the VEMs Using VMware Update Manager from Release 4.2(1)SV2(1.1x) and Later Releases to the Current Release.

- Upgrade VEM from VSM. See Upgrading the VEMs Using VMware Update Manager from Release 4.2(1)SV2(1.1x) and Later Releases to the Current Release.

- Manual upgrade procedures

- Upgrading VIB Manually from the CLI. See Upgrading the VEMs Manually from Release 4.2(1)SV2(1.1x) and Later Releases to the Current ReleaseUpgrading the VEMs Manually from Release 4.2(1)SV2(1.1x) and Later Releases to the Current Release

- Installing or upgrading stateless ESXi. See Installing the VEM Software on a Stateless ESXi Host.

VEM upgrades fall into three types:

- An upgrade of an ESX or 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. The upgrade is described in Installing the VEM Software on a Stateless ESXi Host.

- An upgrade that involves a migration from ESX to ESXi (of the same or different vSphere version).

An upgrade of an ESX or 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 ESX/ESXi version intact. The first figure shows this flow.

2. Upgrade the ESX/ESXi without a change of the Cisco Nexus 1000V version. This process is addressed in the Workflow 2 figure.

The following figure shows Workflow 1 where Cisco Nexus 1000V Release 4.2(1)SV1(4.x) or 4.2(1)SV1(5.x) is upgraded to the current release, without a change of ESX versions.

Workflow 1 with a Cisco Nexus 1000V Version 4.2(1)SV1(4), SV1(4a), SV1(4b), SV1(5.1), or SV1(5.2) Installed

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)SV2(1.1x) 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)SV2(1.1x) and Later Releases to the Current Release.

The following figure shows Workflow 2 where Cisco Nexus 1000VRelease 4.2(1)SV2(1.1) is installed and VMware 4.1 is upgraded to 5.0.

Workflow 2 with Cisco Nexus 1000V 4.2(1)SV2(1.1a) Installed and Upgrading ESX from 4.1 to 5.0

- 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 ESX host to a new update within a release, use a host upgrade baseline. For example, vSphere 5.0 GA to 5.0 U1.

- If you are upgrading the ESX host to a major release (for example, vSphere 5.0 U1), generate an upgrade ISO and set up a host upgrade baseline. The upgrade ISO must have the desired final images for both ESX and VEM. The procedure to generate an upgrade ISO is in Creating an Upgrade ISO with a VMware ESX Image and a Cisco Nexus 1000V VEM Image.

- You can upgrade the ESX 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.

Note

If you plan to perform Workflow 2 and manually update to vSphere 5.0 or later, you must boot the host from an upgrade ISO with both ESX and VEM images.

Creating an Upgrade ISO with a VMware ESX Image and a Cisco Nexus 1000V VEM Image

Before You Begin

- Install the VMware PowerCLI on a Windows platform. For more information, see the vSphere PowerCLI Installation Guide.

- On the same Windows platform, where the VMware PowerCLI is installed, do one of the following:

- Download the ESX depot, which is a .zip file, to a local file path.

- Download the VEM offline bundle, which is a .zip file, to a local file path.

Procedure

Step 1

Start the VMWare PowerCLI application.

Step 2

Connect to the vCenter Server by using the Connect-VIServer IP_address -User Administrator -Password password_name command.

Step 3

Load the ESX depot by using the Add-ESXSoftwareDepot path_name\file_name command.

Step 4

Display the image profiles by using the Get-EsxImageProfile command.

Step 5

Clone the ESX standard image profile by using the New-ESxImageProfile -CloneProfile ESXImageProfile_name -Name clone_profile command.
Note:
The image profiles are usually in READ-ONLY format. You must clone the image profile before adding the VEM image to it.

Step 6

Load the Cisco Nexus 1000V VEM offline bundle by using the Add-EsxSoftwareDepot VEM_offline_bundle command.

Step 7

Confirm that the n1kv-vib package is loaded by using the Get-EsxSoftwarePackage -Name package_name command.

Step 8

Bundle the n1kv-package into the cloned image profile by using the Add-EsxSoftwarePackage -ImageProfile n1kv-Image -SoftwarePackage cloned_image_profile command.

Step 9

Verify that the Cisco VIB is present by listing all the VIBs in the cloned image profile by entering the following commands.

1. $img = Get-EsxImageProfile n1kv-Image

2. $img.vibList

Verify that the Cisco VIB is present by listing all the VIBs in the cloned image profile.

Step 10

Export the image profile to an ISO file by using the Export-EsxImageProfile -ImageProfile n1kv-Image -FilePath iso_filepath command.

This example shows how to create an upgrade ISO with a VMware ESX image and a Cisco VEM image.

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.

vSphere PowerCLI> Connect-VIServer 10.105.231.40 -User administrator -Password 'XXXXXXXX'

Working with multiple default servers?

Select [Y] if you want to work with more than one default servers. In this
case, every time when you connect to a different server using Connect-VIServer,
the new server connection is stored in an array variable together with the
previously connected servers. When you run a cmdlet and the target servers
cannot be determined from the specified parameters, the cmdlet runs against all
servers stored in the array variable.
Select [N] if you want to work with a single default server. In this case,
when you run a cmdlet and the target servers cannot be determined from the
specified parameters, the cmdlet runs against the last connected server.

WARNING: WORKING WITH MULTIPLE DEFAULT SERVERS WILL BE ENABLED BY DEFAULT
IN A FUTURE RELEASE. You can explicitly set your own preference at any time by
using the DefaultServerMode parameter of Set-PowerCLIConfiguration.

[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): Y

Name                           Port  User
----                           ----  ----
10.105.231.40                  443   administrator

vSphere PowerCLI> Add-EsxSoftwareDepot 'C:\Documents and Settings\Administrator\Desktop\upgrade\229\VMware-ESXi-5.1.0-799733-depot.zip'

Depot Url
---------
zip:C:\Documents and Settings\Administrator\Desktop\upgrade\229\VMware-ESXi-...

vSphere PowerCLI> Get-EsxImageProfile

Name                           Vendor          Last Modified   Acceptance Level
----                           ------          -------------   ----------------
ESXi-5.1.0-20121201001s-no-... VMware, Inc.    12/7/2012 7:... PartnerSupported
CN1-CY                         CISCO           4/22/2013 11... PartnerSupported
ESXi-5.1.0-20121204001-stan... VMware, Inc.    12/7/2012 7:... PartnerSupported
ESXi-5.1.0-20121201001s-sta... VMware, Inc.    12/7/2012 7:... PartnerSupported
ESXi-5.1.0-799733-no-tools     VMware, Inc.    8/2/2012 3:0... PartnerSupported
ESXi-5.1.0-20121204001-no-t... VMware, Inc.    12/7/2012 7:... PartnerSupported
ESXi-5.1.0-799733-standard     VMware, Inc.    8/2/2012 3:0... PartnerSupported

vSphere PowerCLI> New-EsxImageProfile -CloneProfile ESXi-5.1.0-799733-standard -Name FINAL

cmdlet New-EsxImageProfile at command pipeline position 1
Supply values for the following parameters:
(Type !? for Help.)
Vendor: CISCO

Name                           Vendor          Last Modified   Acceptance Level
----                           ------          -------------   ----------------
FINAL                          CISCO           8/2/2012 3:0... PartnerSupported

vSphere PowerCLI> Add-EsxSoftwareDepot 'C:\Documents and Settings\Administrator\Desktop\upgrade\229
\VEM510-201408170106-BG-release.zip

Depot Url
---------
zip:C:\Documents and Settings\Administrator\Desktop\upgrade\229\cisco-vem-v1...

vSphere PowerCLI> Get-EsxSoftwarePackage cisco*

Name                     Version                        Vendor     Creation Dat
e
----                     -------                        ------     ------------
cisco-vem-v170-esx       5.2.1.3.1.1.0-3.1.1          Cisco      1/24/2014...

vSphere PowerCLI> Add-EsxSoftwarePackage -SoftwarePackage cisco-vem-v170-esx -ImageProfile FINAL

Name                           Vendor          Last Modified   Acceptance Level
----                           ------          -------------   ----------------
FINAL                          CISCO           1/24/2014 3:... PartnerSupported

vSphere PowerCLI> $img = Get-EsxImageProfile FINAL

vSphere PowerCLI> $img.vibList

Name                     Version                        Vendor     Creation Dat
e
----                     -------                        ------     ------------
scsi-bnx2i               1.9.1d.v50.1-5vmw.510.0.0.7... VMware     8/2/2012 ...
sata-sata-promise        2.12-3vmw.510.0.0.799733       VMware     8/2/2012 ...
net-forcedeth            0.61-2vmw.510.0.0.799733       VMware     8/2/2012 ...
esx-xserver              5.1.0-0.0.799733               VMware     8/2/2012 ...
misc-cnic-register       1.1-1vmw.510.0.0.799733        VMware     8/2/2012 ...
net-tg3                  3.110h.v50.4-4vmw.510.0.0.7... VMware     8/2/2012 ...
scsi-megaraid-sas        5.34-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-megaraid-mbox       2.20.5.1-6vmw.510.0.0.799733   VMware     8/2/2012 ...
scsi-ips                 7.12.05-4vmw.510.0.0.799733    VMware     8/2/2012 ...
net-e1000e               1.1.2-3vmw.510.0.0.799733      VMware     8/2/2012 ...
sata-ahci                3.0-13vmw.510.0.0.799733       VMware     8/2/2012 ...
sata-sata-svw            2.3-3vmw.510.0.0.799733        VMware     8/2/2012 ...
net-cnic                 1.10.2j.v50.7-3vmw.510.0.0.... VMware     8/2/2012 ...
net-e1000                8.0.3.1-2vmw.510.0.0.799733    VMware     8/2/2012 ...
ata-pata-serverworks     0.4.3-3vmw.510.0.0.799733      VMware     8/2/2012 ...
scsi-mptspi              4.23.01.00-6vmw.510.0.0.799733 VMware     8/2/2012 ...
ata-pata-hpt3x2n         0.3.4-3vmw.510.0.0.799733      VMware     8/2/2012 ...
net-s2io                 2.1.4.13427-3vmw.510.0.0.79... VMware     8/2/2012 ...
esx-base                 5.1.0-0.0.799733               VMware     8/2/2012 ...
net-vmxnet3              1.1.3.0-3vmw.510.0.0.799733    VMware     8/2/2012 ...
net-bnx2                 2.0.15g.v50.11-7vmw.510.0.0... VMware     8/2/2012 ...
cisco-vem-v164-esx       4.2.1.2.2.2.0-3.1.1            Cisco      1/24/2014...
scsi-megaraid2           2.00.4-9vmw.510.0.0.799733     VMware     8/2/2012 ...
ata-pata-amd             0.3.10-3vmw.510.0.0.799733     VMware     8/2/2012 ...
ipmi-ipmi-si-drv         39.1-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-lpfc820             8.2.3.1-127vmw.510.0.0.799733  VMware     8/2/2012 ...
ata-pata-atiixp          0.4.6-4vmw.510.0.0.799733      VMware     8/2/2012 ...
esx-dvfilter-generic-... 5.1.0-0.0.799733               VMware     8/2/2012 ...
net-sky2                 1.20-2vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-qla2xxx             902.k1.1-9vmw.510.0.0.799733   VMware     8/2/2012 ...
net-r8169                6.011.00-2vmw.510.0.0.799733   VMware     8/2/2012 ...
sata-sata-sil            2.3-4vmw.510.0.0.799733        VMware     8/2/2012 ...
scsi-mpt2sas             10.00.00.00-5vmw.510.0.0.79... VMware     8/2/2012 ...
sata-ata-piix            2.12-6vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-hpsa                5.0.0-21vmw.510.0.0.799733     VMware     8/2/2012 ...
ata-pata-via             0.3.3-2vmw.510.0.0.799733      VMware     8/2/2012 ...
scsi-aacraid             1.1.5.1-9vmw.510.0.0.799733    VMware     8/2/2012 ...
scsi-rste                2.0.2.0088-1vmw.510.0.0.799733 VMware     8/2/2012 ...
ata-pata-cmd64x          0.2.5-3vmw.510.0.0.799733      VMware     8/2/2012 ...
ima-qla4xxx              2.01.31-1vmw.510.0.0.799733    VMware     8/2/2012 ...
net-igb                  2.1.11.1-3vmw.510.0.0.799733   VMware     8/2/2012 ...
scsi-qla4xxx             5.01.03.2-4vmw.510.0.0.799733  VMware     8/2/2012 ...
block-cciss              3.6.14-10vmw.510.0.0.799733    VMware     8/2/2012 ...
scsi-aic79xx             3.1-5vmw.510.0.0.799733        VMware     8/2/2012 ...
tools-light              5.1.0-0.0.799733               VMware     8/2/2012 ...
uhci-usb-uhci            1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
sata-sata-nv             3.5-4vmw.510.0.0.799733        VMware     8/2/2012 ...
sata-sata-sil24          1.1-1vmw.510.0.0.799733        VMware     8/2/2012 ...
net-ixgbe                3.7.13.6iov-10vmw.510.0.0.7... VMware     8/2/2012 ...
ipmi-ipmi-msghandler     39.1-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-adp94xx             1.0.8.12-6vmw.510.0.0.799733   VMware     8/2/2012 ...
scsi-fnic                1.5.0.3-1vmw.510.0.0.799733    VMware     8/2/2012 ...
ata-pata-pdc2027x        1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
misc-drivers             5.1.0-0.0.799733               VMware     8/2/2012 ...
net-enic                 1.4.2.15a-1vmw.510.0.0.799733  VMware     8/2/2012 ...
net-be2net               4.1.255.11-1vmw.510.0.0.799733 VMware     8/2/2012 ...
net-nx-nic               4.0.558-3vmw.510.0.0.799733    VMware     8/2/2012 ...
esx-xlibs                5.1.0-0.0.799733               VMware     8/2/2012 ...
net-bnx2x                1.61.15.v50.3-1vmw.510.0.0.... VMware     8/2/2012 ...
ehci-ehci-hcd            1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
ohci-usb-ohci            1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
net-r8168                8.013.00-3vmw.510.0.0.799733   VMware     8/2/2012 ...
esx-tboot                5.1.0-0.0.799733               VMware     8/2/2012 ...
ata-pata-sil680          0.4.8-3vmw.510.0.0.799733      VMware     8/2/2012 ...
ipmi-ipmi-devintf        39.1-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-mptsas              4.23.01.00-6vmw.510.0.0.799733 VMware     8/2/2012 ...

vSphere PowerCLI> Export-EsxImageProfile -ImageProfile FINAL -FilePath 'C:\Documents and Settings\Administrator\Desktop\FINAL.iso' -ExportToIso

Upgrading the vCenter Server

Note

This upgrade procedure applies to vCenter Server 5.0, 5.0 Update 1 and later, 5.1, and 5.5 versions.

Before You Begin

- Download the upgrade ISO file that contains your desired ESXi image and the desired Cisco Nexus 1000V image.

- See the Cisco Nexus 1000V and VMware Compatibility Information document to determine the correct VIB Version, VEM Bundle, Host Build, vCenter Server, and Update Manager versions.

Procedure

Step 1

Navigate to the VMware vSphere installation file.
Note:
If you have the ISO image, you should mount it on the host.

Step 2

Double-click autorun.

Step 3

In the VMware vCenter Installer screen, click vCenter Server.

Step 4

Click Install.

Step 5

Choose a language and click OK.

Step 6

Click Next.

Step 7

In the Patent Agreement screen, click Next.

Step 8

In the License Agreement screen, click the I agree to the terms in the license agreement radio button.

Step 9

Click Next.

Step 10

In the Database Options screen, click Next.

Step 11

Click the Upgrade existing vCenter Server database radio button and check the I have taken a backup of the existing vCenter Server database and SSL certificates in the folder: C:\ProgramData\VMware\VMware VirtualCenter\SSL\. check box.

Step 12

From the Windows Start Menu, click Run.

Step 13

Enter the name of the folder that contains the vCenter Server database and click OK.

Step 14

Drag a copy of the parent folder (SSL) to the desktop as a backup.

Step 15

Return to the installer program.

Step 16

Click Next.

Step 17

In the vCenter Agent Upgrade screen, click the Automatic radio button.

Step 18

Click Next.

Step 19

In the vCenter Server Service screen, check the Use SYSTEM Account check box.

Step 20

Click Next.

Step 21

Review the port settings and click Next.

Step 22

In the vCenter Server JVM Memory screen based on the number of hosts, click the appropriate memory radio button.

Step 23

Click Next.

Step 24

Click Install.

Step 25

Click Finish.
This step completes the upgrade of the vCenter Server.

Step 26

Upgrade the VMware vSphere Client to your desired ESXi version.

Step 27

Open the VMware vSphere Client.

Step 28

From the Help menu, choose About VMware vSphere.

Step 29

Confirm that the vSphere Client and the VMware vCenter Server are both the same VMware versions.

Step 30

Click OK, and exit the VMware vSphere Client.

What to Do Next

Complete the steps in Upgrading the vCenter Update Manager to Release 5.5.

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

Caution

If removable media is still connected (for example, if you have installed the VSM using ISO and forgot to remove the media), host movement to maintenance mode fails and the VUM upgrade fails.

Before You Begin

When using VUM, the feature http-server enable command must be enabled.

Procedure

Step 1

switch# show vmware vem upgrade status
Display the current configuration.

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 host is using ESXi 5.0.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-201408170101-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 Jan 27 10:03:24 2014
Upgrade Status Time(vCenter):
Upgrade Start Time:
Upgrade End Time(vCenter):
Upgrade Error:
Upgrade Bundle ID:
VSM:  VEM500-201401170100-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 Jan 27 10:03:24 2014
Upgrade Status Time(vCenter): Tue Jan 27 02:06:53 2014
Upgrade Start Time:
Upgrade End Time(vCenter):
Upgrade Error:
Upgrade Bundle ID:
VSM: VEM500-201401170100-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 Jan 27 10:03:24 2014
Upgrade Status Time(vCenter) : Tue Jan 27 02:06:53 2014
Upgrade Start Time: : Tue Jan 27 10:09:08 2014
Upgrade End Time(vCenter):
Upgrade Error:
Upgrade Bundle ID:
VSM: VEM500-201401170100-BG
DVS: VEM500-201401170100-BG
switch#
switch# show vmware vem upgrade status

Upgrade VIBs: System VEM Image
Upgrade Status: Upgrade Complete in vCenter
Upgrade Notification Sent Time: : Tue Jan 27 10:03:24 2014
Upgrade Status Time(vCenter): : Tue Jan 27 02:06:53 2014
Upgrade Start Time: : Tue Jan 27 10:09:08 2013
Upgrade End Time(vCenter): : Tue Jan 27 10:09:08 2014
Upgrade Error:
Upgrade Bundle ID:
VSM: VEM500-201401170100-BG
DVS: VEM500-201401170100-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-201401170100-BG
DVS: VEM500-201401170100-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    1022   Virtual Ethernet Module           NA                  ok
4    1022   Virtual Ethernet Module           NA                  ok

Mod  Sw                  Hw
---  ------------------  ------------------------------------------------
1    5.2(1)SV3(1.1)      0.0
2    5.2(1)SV3(1.1)      0.0
3    5.2(1)SV3(1.1)      VMware ESXi 5.0.0 Releasebuild-469512 (3.0)
4    5.2(1)SV3(1.1)      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.

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.
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.

Required Task After Upgrade—Changing the VEM Feature Level

After upgrading to Release 5.2(1)SV3(1.1), you must update the VEM feature level to Release 5.2(1)SV3(1.1). After you perform this task, the new features in Release 5.2(1)SV3(1.1) are available on the Cisco Nexus 1000V and you have the option to increase the VLAN and port channel resource limits.

Before You Begin

- VSM and VEM have been upgraded to Release 5.2(1)SV3(1.1).

Procedure

Step 1

switch# configure terminal
Enters global configuration mode.

Step 2

switch(config)# show system vem feature level
Displays the current VEM feature level. The current feature level should be 5.2(1)SV3(1.1).

Step 3

switch(config)# vdc switch-name
Enters VDC configuration mode for the specified switch.

Step 4

switch(config-vdc)# limit-resource port-channel minimum value maximum value
Configures the port channel resource limit.

Step 5

switch(config-vdc)# limit-resource vlan minimum value maximum value
Configures the VLAN resource limit

Step 6

switch(config-vdc)# show resource
Displays the updated values.

Step 7

switch(config-vdc)# exit
Exists the current configuration mode.

Step 8

(Optional)switch(config)# copy running-config startup-config
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

This example shows how to update the VEM feature level after upgrading from Release 4.2(1)SV2(1.1) to Release 5.2(1)SV3(1.1).

switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
switch(config)# system update vem feature ?
level  Updating vem feature level

switch(config)# system update vem feature level ?
<CR>
<1-50>  Version number index from the list above

switch(config)# system update vem feature level
Feature      Version
Level        String
--------------------
1            4.2(1)SV2(2.1)
2            4.2(1)SV2(2.2)
3            4.2(1)SV2(2.3)
4            5.2(1)SV3(1.1)
switch(config)#
switch(config)#
switch(config)# system update vem feature level 4
switch(config)# copy running-config startup-config

Information About Upgrading the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Cisco Virtual Switch Update Manager is the graphical user interface (GUI) that you can use to upgrade the Virtual Supervisor modules (VSMs) and the VEMs on ESX/ESXi hosts.

An interactive upgrade tool has been provided to assist you in determining the correct upgrade steps based on your current environment and the one to which you want to upgrade.

See the Cisco Nexus 1000V and VMware Compatibility Information for more information on the compatibility information for Cisco Nexus 1000V.

You can obtain your upgrade-related software for the current release of the Cisco Nexus 1000V software from cisco.com.

With Cisco Virtual Switch Update Manager, you can upgrade Cisco Nexus 1000V version only with the vSphere version intact.

See the Cisco Nexus 1000V Installation and Upgrade Guide for information about how to upgrade both vSphere and Cisco Nexus 1000V versions together and how to upgrade the vSphere version only, with the Cisco Nexus 1000V version intact.

Supported Upgrade Paths: With Cisco Virtual Switch Update Manager, you can upgrade Cisco Nexus 1000V from Release 4.2(1)SV1(4b) and later releases.

Unsupported Upgrade Paths: Using Cisco Virtual Switch Update Manager, you cannot upgrade the following releases of Cisco Nexus 1000V to the current release, Release 5.2(1)SV3(1.1):

- Release 4.2(1)SV1(4)

- Release 4.2(1)SV1(4a)

- Release 4.2(1)SV1(3x) series

Note

Upgrades from Release 4.0(4)SV1(1), 4.0(4)SV1(2), and 4.0(4)SV1(3x) are no longer supported. VMware 4.0 and 4.1 are also not supported with this Cisco Nexus 1000V release.

Guidelines and Limitations for Upgrading the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Caution

During the upgrade process, the Cisco Nexus 1000V does not support any new additions such as modules, virtual NICs (vNICs), or VM NICs and does not support any configuration changes. VM NIC and vNIC port-profile changes might render VM NICs and vNICs in an unusable state.

Note

We recommend that you use vSphere 5.0 Update 1 or later instead of vSphere 5.0.

Upgrading the Cisco Nexus 1000V with Cisco Virtual Switch Update Manager has the following guidelines and limitations:

- You are upgrading the Cisco Nexus 1000V software to the current release.

- Schedule the upgrade when your network is stable and steady. Ensure that everyone who has access to the switch or the network is not configuring the switch or the network during this time. You cannot configure a switch during an upgrade.

- Avoid power interruptions to the hosts that run the VSM VMs during any installation procedure.

Before you upgrade the VEMs, note these guidelines and limitations:

- During the VEM upgrade process, VEMs reattach to the VSM.

- Connectivity to the VSM can be lost during a VEM upgrade when the interfaces of a VSM VM connect to its own distributed virtual switch (DVS).

Prerequisites for Upgrading Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

Upgrading the Cisco Nexus 1000V with Cisco Virtual Switch Update Manager has the following prerequisites:

- Close any active configuration sessions before upgrading the Cisco Nexus 1000V software.

- Save all changes in the running configuration to the startup configuration.

- Save a backup copy of the running configuration in the external storage.

- Perform a VSM backup. For more information, see the “Configuring VSM Backup and Recovery” chapter in the Cisco Nexus 1000V System Management Configuration Guide.

- Use the VSM management IP address to log into VSM and perform management tasks.

Important:
If you connect to a VSM using the VSA serial port or the connect host from the Cisco Integrated Management Control (CIMC), do not initiate commands that are CPU intensive, such as copying images from the TFTP server to bootflash or generating a lot of screen output or updates. Use the VSA serial connections, including CIMC, only for operations such as debugging or basic configuration of the VSA.

- If you need to migrate a vSphere host from ESX to ESXi, do it before the Cisco Nexus 1000V upgrade.

- You have placed the VEM software file in /tmp on the vSphere host. Placing it in the root (/) directory might interfere with the upgrade. Make sure that the root RAM disk has at least 12 MB of free space by entering the vdf command.

- On your upstream switches, you must have the following configuration.

- On Catalyst 6500 Series switches with the Cisco IOS software, enter the portfast trunk command or the portfast edge trunk command.

- On Cisco Nexus 5000 Series switches with the Cisco NX-OS software, enter the spanning-tree port type edge trunk command.

- On your upstream switches, we highly recommend that you globally enable the following:

- Global BPDU Filtering

- Global BPDU Guard

- On your upstream switches where you cannot globally enable BPDU Filtering and BPDU Guard, we highly recommend that you enter the following commands:

- spanning-tree bpdu filter

- spanning-tree bpdu guard

- You must have the Distributed Switch—Create and Modify privilege permission enabled on the vCentre.

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

Upgrading the Cisco Nexus 1000V Using Cisco Virtual Switch Update Manager

You can upgrade the Cisco Nexus 1000V using Cisco Virtual Switch Update Manager.

Procedure

Step 1

Log in to the VMware vSphere Web Client.

Step 2

In the vSphere Client, choose Cisco Virtual Switch Update Manager > Configure and Manage Nexus 1000V and Application Virtual Switch > Datacenter > Distributed Virtual Switch > Manage.
Note:
If the switch is not managed by Cisco Virtual Switch Update Manager, you are prompted to enter the switch credentials in the Make Managed window.

Step 3

In the switch pane, click Upgrade.

Step 4

(Optional)In case of multiple vCenter Servers, choose Home > Cisco Virtual Switch Update Manager > vCenter Server > Configure and Manage Nexus 1000V and Application Virtual Switch .

Step 5

(Optional)You can also access the Cisco Virtual Switch Update Manager in the vSphere Client by navigating to vCenter > Distributed Switches.

Step 6

(Optional) In the switch pane, click Manage > Cisco Nexus 1000V > Upgrade.
Note:
If the policy agent has been installed on the VSM, then do the following:

1. Enter the PNSC version number in the PNSC field.

2. Enter the VSG version number in the VSG field.

3. Click OK. The upgrade path displays the selected PNSC version and PA Compatible option as Yes.

4. From the Eligible Hosts drop-down list, choose the host and click Finish. This upgrades the VSMs along with the Policy Agent and the VEM.

Step 7

In the Switch Upgrade Path area, the Switch Upgrade Path for the selected switch displays the switch to be upgraded.
Cisco Virtual Switch Update Manager—Upgrading Cisco Nexus 1000V

Step 8

In the Versions area, the following information is pre configured.

Name

Description

Suggested Upgrade field

Displays if the upgrade is supported .

Version field

Displays the version number of the Cisco Nexus 1000V switch suggested for upgrade.

PA Compatble field

Displays if the Cisco PNSC version is compatible with the Cisco Nexus 1000V switch version suggested for upgrade.

Unsupported Hosts field

Displays if the ESX host has to be upgraded manually.

Step 9

In the Hosts area, the hosts that are associated with the Cisco Nexus 1000V version suggested for upgrade are displayed.
The hosts are represented in the following four categories

- Unknown Status Hosts—The status of the host is in nonresponding state.

- Unsupported Hosts—The ESX version of the host is not compatible with the ESX version of the host that is associated with the Cisco Nexus 1000V version suggested for upgrade. The unsupported hosts should be upgraded manually to the ESX versions supported by the Cisco Nexus 1000V. See the Cisco Nexus 1000V and VMware Compatibility Information for more information about supported ESX versions.

- No Upgrade Needed Hosts—The hosts already have the correct VEM version installed.

- Eligible Hosts—The ESX version of the host is compatible with the ESX version of the host that is associated with the Cisco Nexus 1000V version suggested for upgrade. During the upgrade process, Cisco Virtual Switch Update Manager upgrades the VEM version installed on the hosts to the specified version.

Step 10

Click Finish to upgrade the Cisco Nexus 1000V.

Step 11

In vSphere Web Client, choose vCenter > Datacenter > Switch > Monitor > Tasks to view the status of the upgrade. You can also view the tasks in the vSphere Web Client by choosing Cisco Virtual Switch Update Manager > Select vCenter Host > Mange DVS > Select Datacenter > Select Switch > Monitor > Tasks.
A typical upgrade of the host takes a few minutes. In vCenter Web Client, you can view the tasks by the task object, user, or task status.

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 ESX/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 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 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 ESX/ESXi and VEM software simultaneously if you are using the vCLI.

- esxupdate
Installs the VEM software from the ESX host /tmp directory.
Note:
You must log in to each host and enter this command. This command loads the software manually on the host, loads the kernel modules, and starts the VEM agent on the running system.

Step 3

For ESXi 5.0.0 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-201408170101-BG-release.zip
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: Cisco_bootbank_cisco-vem-v170-esx_5.2.1.3.1.1.0-3.0.1
VIBs Removed:
VIBs Skipped:
~ #

~ # esxcli software vib install -v /tmp/cross_cisco-vem-v170-5.2.1.3.1.1.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.1.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-201408170101 2014-01-27T08:18:22 Cisco Nexus 1000V 5.2(1)SV3(1.1)

~ # vem status -v
Package vssnet-esxmn-ga-release
Version 5.2.1.3.1.1.0-3.0.1
Build 1
Date Mon Aug 4 04:56:14 PDT 2014

VEM modules are loaded
Switch Name      Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch0         128         4           128               1500    vmnic0
DVS Name         Num Ports   Used Ports  Configured Ports  MTU     Uplinks
p-1              1024        13          1024              1500    vmnic7,vmnic6,vmnic3,vmnic2,vmnic1,vmnic0
VEM Agent (vemdpa) is running
~ #

~ # vemcmd show version
VEM Version: 5.2.1.3.1.1.0-3.0.1
VSM Version: 5.2(1)SV3(1.1)
System Version: VMware ESXi 5.0.0 Releasebuild-843203
ESX Version Update Level: 3

~ #
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    1022   Virtual Ethernet Module           NA                  ok
6    1022   Virtual Ethernet Module           NA                  ok

Mod  Sw                  Hw
---  ------------------  ------------------------------------------------
1     5.2(1)SV3(1.1)  0.0
2     5.2(1)SV3(1.1)  0.0
3     5.2(1)SV3(1.1)      VMware ESXi 5.0.0 Releasebuild-843203 (3.0)
6     5.2(1)SV3(1.1)      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.

Upgrading the VEMs Manually from Release 4.2(1)SV2(1.1x) 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.

Caution

If removable media is still connected, (for example, if you have installed the VSM using ISO and forgot to remove the media), host movement to maintenance mode fails and the VEM upgrade fails.

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-201408170101-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 Jan 28 10:03:24 2014
Upgrade Status Time(vCenter): Tue Jan 28 02:06:53 2014
Upgrade Start Time:
Upgrade End Time(vCenter):
Upgrade Error:
Upgrade Bundle ID:
VSM: VEM500-201408170101-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 Jan 28 10:03:24 2014
Upgrade Status Time(vCenter): Tue Jan 28 02:06:53 2014
Upgrade Start Time: Tue Jan 28 10:09:08 2014
Upgrade End Time(vCenter):
Upgrade Error:
Upgrade Bundle ID:
VSM: VEM500-201408170101-BG
DVS: VEM500-201408170101-BG

switch# show vmware vem upgrade status
Upgrade VIBs: System VEM Image
Upgrade Status: Upgrade Complete in vCenter
Upgrade Notification Sent Time: Tue Jan 28 10:03:24 2014
Upgrade Status Time(vCenter): Tue Jan 28 02:06:53 2014
Upgrade Start Time: Tue Jan 28 10:09:08 2014
Upgrade End Time(vCenter):
Upgrade Error
Upgrade Bundle ID:
VSM: VEM500-201408170101-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-201408170101-BG
DVS: VEM500-201408170101-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    1022   Virtual Ethernet Module           NA                  ok
6    1022   Virtual Ethernet Module           NA                  ok

Mod  Sw                  Hw
---  ------------------  ------------------------------------------------
1    5.2(1)SV3(1.1)  0.0
2    5.2(1)SV3(1.1)  0.0
3    5.2(1)SV3(1.1)      VMware ESXi 5.0.0 Releasebuild-843203 (3.0)
6    5.2(1)SV3(1.1)      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#

Simplified Upgrade Process

Combined Upgrade

You can upgrade the VEM and ESX version simultaneously. It requires vSphere version 5.0 Update1 and later versions. It is supported in Cisco Nexus 1000V Release 4.2(1)SV1(5.2) and later. This upgrade can be implemented manually or by using VUM.

Selective Upgrade

You can upgrade a selective set of VEMs and a few hosts or clusters at a time in a single maintenance window. This enables incremental upgrades during short maintenance windows. It is supported with combined upgrades of VEM and ESX, and also with manual upgrades of VEMs only. It is supported for VUM-based combined upgrades with select hosts or clusters using the GUI. It is not supported with VUM-based upgrades of VEMs alone. To upgrade manually using this procedure follow these general steps:

- Identify the cluster or set of hosts in a cluster

- Place the selected hosts in maintenance mode (to vacate the VMs)

- Upgrade the VEM image on the hosts using the manual command or scripts

- Take the hosts out of maintenance mode, allowing Distributed Resource Scheduler (DRS) to rebalance VMs

Allowed Infrastructure Operations Under Selective Upgrade

These operations are allowed under selective upgrades:

- vMotion of VMs with the following releases:

- pre-5.2(1)SV3(1.1) to 5.2(1)SV3(1.1)

- 5.2(1)SV3(1.1) to pre-5.2(1)SV3(1.1)

- 5.2(1)SV3(1.1) to 5.2(1)SV3(1.1)

- pre5.2(1)SV3(1.1) to pre-5.2(1)SV3(1.1)

- VEM restart

- Host Reboot

- Add modules in 5.2(1)SV3(1.1)

- Add or remove ports vEth ports

- Shut or no-shut on port

- Migrate ports to or from vSwitch

- Add or delete VLAN or VLAN ranges

Background Upgrade

You can upgrade VEMs without a maintenance window for VEMs. You use the manual procedure to upgrade VEMs during production. Place the host in maintenance mode, upgrade the VEM, and remove the host from the maintenance mode. You do not have to shut off HA Admission Control and such (as you would during VUM upgrades). You must ensure the spare capacity in the cluster and perform a health check before the upgrade. To upgrade using this procedure follow these general steps:

- Upgrade the VSM first as usual. This may be done in a maintenance window

- Place one host at a time in maintenance mode (to vacate the VMs)

- Upgrade the VEM image on that host using manual commands or scripts

- Take the host out of maintenance mode, allowing the DRS to rebalance the VMs.

- Repeat the same procedure for every host in the DVS.

Note

Make sure there is enough spare capacity for HA and that all required ports have system profiles (such as mgmt vmk). Check the host health before upgrading.

Extended Upgrade

You can modify configurations between the upgrade maintenance windows. VSM configuration changes are allowed where you can add or remove modules, port configurations, VLANs, and other similar changes. If a set of hosts are upgraded to the latest VEM version using the Selective Upgrade or the Background Upgrade, the remaining set of hosts will remain in older VEM versions. During that time, various Cisco Nexus 1000V configuration changes are allowed between maintenanance windows.

Note

Do not make configuration changes during a maintenance window when the VEMs are being upgraded.

The list of allowed configuration changes are as follows:

- Add or remove modules

- Add or remove ports (ETH and VETH)

- Shut or no-shut a port

- Migrate ports to or from a vswitch

- Change port modes (trunk or access) on ports

- Add or remove port profiles

- Modify port profiles to add or remove specific features such as VLANS, ACLs, QoS, or PortSec.

- Change port channel modes in uplink port profiles

- Add or delete VLANs and VLAN ranges

- Add or delete static MACs in VEMs

Note

Queuing configuration changes are not supported on QoS.

Upgrading from Releases 4.2(1)SV1(4x), 4.2(1)SV1(5.1x), or 4.2(1)SV1(5.2x) to the Current Release

Upgrading from Releases 4.2(1)SV1(4x), 4.2(1)SV1(5.1x), or 4.2(1)SV1(5.2x) to the current release is a two-step process.

Procedure

Step 1

See the Upgrading from Releases 4.2(1)SV1(4x), 4.2(1)SV1(5.1x), or 4.2(1)SV1(5.2x) to the Current Release section in the Cisco Nexus 1000V Software Upgrade Guide, Release 4.2(1)SV2(1.1).

Step 2

See Upgrade Procedures.

Layer 3 Advantages

The following lists the advantages of using a Layer 3 configuration over a Layer 2 configuration:

- The VSM can control the VEMs that are in a different subnets.

- The VEMs can be in different subnets.

- Because the VEMs can be in different subnets, there is no constraint on the physical location of the hosts.

- Minimal VLAN configurations are required for establishing the VSM-VEM connection when compared to Layer 2 control mode. The IP address of the VEM (Layer 3 capable vmknic’s IP address) and the VSM’s control0/mgmt0 interface are the only required information.

- In the VSM, either the mgmt0 or the control0 interface can be used as the Layer 3 control interface. If mgmt0 is used, there is no need for another IP address as the VSM’s management IP address is used for VSM-VEM Layer 3 connection.

- If the management VMKernel (vmk0) is used as the Layer 3 control interface in the VEM, there is no need for another IP address because the host’s management IP address is used for VSM-VEM Layer 3 connectivity.

Note

These advantages are applicable only for ESX-Visor hosts. On ESX-Cos hosts, a new VMKernel must be created.

About VSM-VEM Layer 2 to 3 Conversion Tool

Use the VSM-VEM Layer 2 to 3 Conversion Tool as an optional, simplified method to migrate from Layer 2 to Layer 3 mode. The tool enables you to do the following:

- Check whether the prerequisites are met for the migration from L2 to L3 mode.

- Migrate the VSM from Layer 2 to Layer 3 Mode, with user interaction.

In the process of migration, the tool creates a port profile. You can use port profiles to configure interfaces, which you can assign to other interfaces to give them the same configuration. The VSM-VEM Layer 2 to 3 Conversion Tool also gives you the option of retrieving the IP addresses from a local file (static).

Prerequisites for Using VSM-VEM Layer 2 to 3 Conversion Tool

The L2-L3_CT.zip file contains the applications required to run VSM-VEM Layer 2 to 3 Conversion Tool

Before you begin:

- Log in as administrator to use this conversion tool script.

- Download the L2-L3_CT.zip file from the CCO Download Center.

- Install Tool Conversion Language (TCL) version 8.4 or later on the workstation.

- Install VMware PowerShell API version 5.0 or later on both the vCenter and the workstation.

- Install OpenSSH on the workstation.

- In the workstation environment variables, add installation_directory_for_OpenSSH\bin directory to the end of the Windows path variable.

- Ensure that VLANs are allowed on the uplinks.

Note

You must install vCenter, VSM, and OpenSSH with admin privileges.

Using VSM-VEM Layer 2 to 3 Conversion Tool

Procedure

Step 1

On your workstation, unzip the L2-L3_CT.zip file to any folder.
When you unzip the file, a Pre-Migrate-Check-Logs folder is created that holds all the running logs. Debugging log files will be created in this folder.

Step 2

Inside the L2-L3_CT folder, run migration.bat as an administrator. This starts the VSM-VEM Layer 2 to 3 Conversion Tool.

Step 3

Enter the VSM IP address.

Step 4

Enter the VSM username.

Step 5

Enter the vCenter IP.

Step 6

Enter the vCenter username.

Step 7

Enter the VSM password.

Step 8

Enter the vCenter password.
The migration tool begins creating the .csv file for the user, and then checks for a port profile with layer 3 capability.

Step 9

If there is no layer 3-capable port profile, the tool will prompt for the creation of one. If you don't want to create a layer-3 capable port profile, skip to the next step.

1. Enter yes to confirm when asked to create 1 layer 3-capable port profile.

2. Enter a layer 3 port profile name.

3. Enter access VLAN ID

This creates a port profile with the required configuration. You can select this port profile when prompted by the tool. The migration tool checks for connectivity between VSM, vCenter, and VEM modules. Wait for the message to display that all connectivity is fine.

Step 10

Enter yes to continue when asked if you want to continue.
The migration tool proceeds to create an extract .csv file.

Step 11

Open the extract.csv file (in C:\Windows\Temp).

Step 12

Enter the vmknic IP details at the end of the text, delimited by semicolons, and save the file as convert.csv.

Step 13

Press any key to continue.

Step 14

Enter yes to confirm when asked if you are sure you completed the required steps.

Step 15

Enter the VSM password.

Step 16

Enter the vCenter password.
The migration tool connects to the vCenter and VSM of the user.

Step 17

Enter yes to confirm when asked if you want to continue.
The migration process continues.

Step 18

Enter the port profile name from the list of port profiles that appears at the prompt.
Once the port profile is selected, the max port value is automatically changed to 128.

Step 19

Enter yes to confirm when asked if you have updated convert.csv file as per the instructions.

Step 20

Enter yes to confirm, when asked if you want to continue.
The tool checks the connectivity between VSM, vCenter, and VEM modules. A message is displayed that the addition to vmknics are successful and all connectivity is fine. The VmkNicAddingToHost window will remain open until the configuration is complete.

Step 21

Enter yes to confirm that you would like to proceed with mode change from L2 to L3.

Step 22

Enter yes to confirm when asked if you wish to continue.
Wait for the SUCCESSFULLY COMPLETED MIGRATION message to display. The migration from layer 2 to layer 3 is now complete. The operating mode should now be listed as L3.

Using Extract Mode

You can use Extract Mode to extract the attached VEM states and save them to the Extract.csv file, which is located in C:\Windows\Temp.

Procedure

Command or Action

Purpose

Step 1

Choose extract mode when prompted by VSM-VEM Layer 2 to 3 Conversion Tool. You can now view the data in the Extract.csv file in the Windows temp folder of your workstation.

This mode will not migrate the VSM.

Using Convert Mode

You can use Convert Mode to migrate the VSM from Layer 2 to Layer 3.

Procedure

Command or Action

Purpose

Step 1

Rename the Extract.csv file to Convert.csv

The migration tool will retrieve the data from the Convert.csv file.

Step 2

Populate your Convert.csv file (in C:\Windows\Temp) with the vmknic IP address and netmask.

Step 3

Run migration.bat.

This will migrate the VSM mode from Layer 2 to Layer 3 .

Example

The following example shows how to use the VSM-VEM Layer 2 to 3 Conversion Tool.

Enter VSM IP:
enter VSM Username:
Enter VC IP:
enter VC Username:
Enter VSM password:
Enter VC password:
create the Csv File for User I/P: C:\windows\temp\extract.csv
#### VSM DETAILS STARTS ##########
.........
.............
#### VC DETAILS END ##########
.............
................
Operating Mode : L2
Operatoinal Mode is L2 Currently ......
###############################################################################
List of port profiles on VSM:
-----------------------------
###############################################################################
=========
CHECK 1: Checking for a port profile with capability l3control set and Enabled.
................
=========
There is not even One L3 Capable Port Profile

Do you want to Create One L3 Capable Port Profile
Please Give Option (Yes/No):Yes
Please Enter L3 PortProfile Name: L3-Control
Please Give Access Vlan Id :5
Creating L3 Port Profile : L3-Control with Access Vlan : 5
……………………………….
………………………………………………..
L3 capable port profiles: L3-Control
Modules Registered:[10.105.228.116]
=========
CHECK 3:  Checking for connectivity between VSM and VC, VSM and VEM Modules
=========
…………………..
……………………………………

## All connectivity is fine
###############################################################################
Please wait for a few minutes.
Do you want to Continue,Please Type ....(yes/no):yes
Migration Tool Proceeding ....
Creating csv file: C:\windows\temp\extract.csv
Modules : 10.105.228.116
#########################################################
Modules Registered:[3 10.105.228.116]
#########################################################

#########################################################
###########################################################################
Extraction of VEM connection status has been dumped in: C:\windows\temp\extract.
csv
Please rename this file before using Convert Mode
Update the VMKNic IP and NetMask for all disconnected entries
###########################################################################
!###############################################################################
########!
!Open c:\windows\temp\Extract.csv and save as Convert.csv (in the same directory
)
!Enter the VMKNic IP and netmask in the Convert.csv file as shown below
!VEM_Host_IP;PPConnectionStatus;Vem_Vmk_IP;NetMask!
!PPConnectionStatus Should not be changed!
!10.10.10.12;DisConnected;10.10.10.100;255.255.255.0!
!After Updating the IP and Netmask, save the file in the same directory
!###############################################################################
########!
Press any key to continue . . .
Are you sure you completed the above steps? (yes/no):yes

##############################################################################

##Tool expects this File have an IP/Netmask given for disconnected VEM in the co
rrect format : C:\windows\temp\Convert.csv

##10.10.10.12;DisConnected;10.10.10.100;255.255.255.0

###############################################################################
VSM password required 10.105.228.115:

VC password required 10.105.228.113:

create the Csv File for User I/P: C:\windows\temp\extract.csv
……………………..
…………………………….
## All connectivity is fine

###############################################################################
Please wait for a few minutes.
Do you want to Continue,Please Type ....(yes/no):yes
Migration Tool Proceeding ....
……………………………
……………………………………………….
#########################################################
Name the port profile you want to proceed with : [l3-pp]
Please type any port profile mentioned above       ||:l3-pp
You Selected : l3-pp
…………………..
……………………………….
###################################################################
## Have you created a Convert.csv file with a proper VMKNic IP and NetMask?
## In the C:\windows\temp\Convert.csv file for disconnected VEMs.
###################################################################
Have you Updated C:\windows\temp\Convert.csv as per the above instructions?(Yes)
:yes
Do you want to Continue,Please Type ....(yes/no):yes
Migration Tool Proceeding ....
………………………….
……………………………………………..

Addition to VmKNics are successful
## All connectivity is Fine
……………………………
…………………………………..
###############################################################################

Would You Like to Proceed with Mode Change from L2 to L3....(yes/no):yes
Do you want to Continue,Please Type ....(yes/no):yes
Migration Tool Proceeding ....
…………………..
……………………..
switch#
Operating Mode : L3
Operatoinal Mode is L3 Currently
Svs Connection Mode : L3
Vem IP : 10.10.10.108 Connected Back
………………
……………………
All VEMs are back: pass
==============SUCCESSFULLY COMPLETED MIGRATION===========================

Interface Comparisons Between mgmt0 and control0

The following describes the differences between using a mgmt0 interface or a control0 interface:

- On the VSM, there are two ways of connectivity via the mgmt0 or control0 interface.

- Setting mgmt0 as Layer 3 interface uses the mgmt0 interface on the VSM.

- The control0 interface is a special interface created for Layer 3 connectivity.

- The Layer 3 interface on the VEM is selected by designating the interface with the Layer 3 control capability.

- The egress control traffic route is decided by the VMware routing stack.

- On a VEM, the management vmknic (vmk0) can be used for Layer 3 control connectivity if it is managed by the Cisco Nexus 1000V and is designated with the Layer 3 control capability.

Configuring the Layer 3 Interface

Configure either the control0 (see Step 1) or mgmt0 interface (see Step 2).

Procedure

Step 1

Configuring the control0 interface.
Note:
When using control0 as the control interface on the VSM, the control0 interface must be assigned with an IP address.

1. Configure the IP address.

switch# configure terminal
switch(config)# interface control 0
switch(config-if)# ip address 5.5.5.2 255.255.255.0

2. Display the running configuration of the control0 interface.

switch# show running-config interface control 0
!Command: show running-config interface control0
!Time: Mon Dec 12 02:41:47 2011
version 4.2(1)SV1(5.1)
interface control0
ip address 5.5.5.2/24

Step 2

Configure the mgmt0 interface.
Note:
When using mgmt0 as the control interface, no configuration on the VSM is required as the mgmt0 interface is assigned with the host’s management IP address.

1. Display the running configuration of the mgmt0 interface.

switch# show running-config interface mgmt 0
!Command: show running-config interface mgmt0
!Time: Mon Dec 12 02:43:25 2011
version 4.2(1)SV1(5.1)
interface mgmt0
ip address 10.104.249.37/27

Creating a Port Profile with Layer 3 Control Capability

Before You Begin

- You are creating a port profile with Layer 3 control capability.

- Allow the VLAN that you use for VSM to VEM connectivity in this port profile.

- Configure the VLAN as a system VLAN.

Note

VEM modules will not register to the VSM before a vmkernel interface (vmk) is migrated to a Layer 3 control capable port profile. You must migrate a vmk to the Layer 3 port profile after migrating host vmnics to Ethernet port profiles. Migrate your management vmkernel interface into the Layer 3 capable port profile. Do not use multiple vmkernel interfaces on the same subnet.

Procedure

Step 1

Create a Layer 3 port profile.

VSM_1# configure terminal
VSM_1(config)# port-profile type vethernet l3_control
VSM_1(config-port-prof)# switchport mode access
VSM_1(config-port-prof)# switchport access vlan 3160
VSM_1(config-port-prof)# capability l3control
VSM_1(config-port-prof)# vmware port-group
VSM_1(config-port-prof)# state enabled
VSM_1(config-port-prof)# no shutdown

Step 2

Display the port profile.

VSM_1# show port-profile name l3_control
port-profile l3_control
type: Vethernet
description:
status: enabled
max-ports: 32
min-ports: 1
inherit:
config attributes:
switchport mode access
switchport access vlan 3160 (Allow the VLAN in access mode.)
no shutdown
evaluated config attributes:
switchport mode access
switchport access vlan 3160
no shutdown
assigned interfaces:
Vethernet1
port-group: l3_control
system vlans: 3160 (Configure the VLAN as a system VLAN.)
capability l3control: yes (Configure capability l3 control.)
capability iscsi-multipath: no
capability vxlan: no
capability l3-vn-service: no
port-profile role: none port-binding: static

Creating a VMKernel on the Host

Procedure

Step 1

Log in to the vCenter Server.

Step 2

Choose Home > Inventory > Hosts and Clusters.

Step 3

Choose the host.

Step 4

Click the Configuration tab.

Step 5

In the Hardware pane, choose Networking.

Step 6

Click the vSphere Distributed Switch button.

Step 7

Go to Manage Virtual Adapters.

Step 8

Add and create a new VMKernel.
Note:
The management vmkernel can also be used as a Layer 3 control interface. For ESX-Visor hosts only. Migrate your management vmkernel interface into the Layer 3 capable port profile. Do not use multiple vmkernel interfaes on the same subnet.

Step 9

Assign the VMkernel to the port profile created in Creating a Port Profile with Layer 3 Control Capability.

Step 10

Assign an IP address.

Configuring the SVS Domain in the VSM

Before You Begin

The control0 or mgmt0 interface can be assigned as the Layer 3 control interface.

Procedure

Step 1

Disconnect the VSM to vCenter Server connection.

switch# configure terminal
switch(config)# svs connection toVC
switch(config-svs-conn)# no connect
switch(config-svs-conn)# exit

Step 2

(Optional)Remove the control and the packet VLAN configuration.

switch(config)# svs-domain
switch(config-svs-domain)# no control vlan
switch(config-svs-domain)# no packet vlan

Step 3

Change the svs mode from Layer 2 to Layer 3 with the mgmt0 interface as the Layer 3 control interface.

switch(config-svs-domain)# svs mode l3 interface mgmt0
switch(config-svs-domain)# exit

Note:
If the control0 interface is being used as the Layer 3 control interface, enter the svs mode l3 interface control0 command:

Step 4

Restore the VSM to vCenter Server connection.

switch(config)# svs connection toVC
switch(config-svs-conn)# connect
switch(config-svs-conn)# end

Note:
After entering the svs connection toVC command, the module is detached and reattached in Layer 3 mode. If this delay is more than six seconds, a module flap occurs. This does not affect the data traffic.

Step 5

Display the SVS domain configuration.

switch# show svs domain
SVS domain config:
Domain id:    3185
Control vlan: NA
Packet vlan:  NA
L2/L3 Control mode: L3
L3 control interface: mgmt0
Status: Config push to VC successful.

Note: Control VLAN and Packet VLAN are not used in L3 mode.

Feature History for Upgrading the Cisco Nexus 1000V

The following table lists the release history for upgrading the Cisco Nexus 1000V.

Feature Name

Releases

Feature Information

Combined Upgrade

4.2(1)SV1(5.2)

The ability to perform a simultaneous upgrade of the VEM and ESXi host.

Upgrading the Cisco Nexus 1000V

4.0(4)SV1(2)

Introduced in this release.

Chapter 5. Upgrading a Standalone VSM

This chapter contains the following sections:

- Upgrading a Standalone VSM

Upgrading a Standalone VSM

Note

The example may contain Cisco Nexus 1000V versions and filenames that are not relevant to your release. Refer to the Cisco Nexus 1000V and VMware Compatibility Information for your specific versions and filenames.

Procedure

Step 1

Log in to the VSM on the console.

Step 2

Log in to Cisco.com to access the links provided in this document.
To log in, go to the URL Click Here 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: Click Here

Step 4

Navigate to the download site for your switch.
You see links to the download images for your switch.

Step 5

Select and download the Cisco Nexus 1000V zip file and extract the kickstart and system software files to a server.

Step 6

Ensure that the required space is available for the image files to be copied.

switch# dir bootflash:
.
.
.
Usage for bootflash://
485830656 bytes used
1109045248 bytes free
1594875904 bytes total

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

Delete unnecessary files to make space available if you need more space on the VSM bootflash,

Step 8

If you plan to install the images from the bootflash:, copy the Cisco Nexus 1000V kickstart and system images to the active VSM bootflash using a transfer protocol. You can use ftp:, tftp:, scp:, or sftp:. The examples in this procedure use scp:.
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.

switch# copy scp://user@scpserver.cisco.com//downloads/
nexus-1000v-kickstart.5.2.1.SV3.1.1.bin
switch# copy scp://user@scpserver.cisco.com//downloads/
nexus-1000v-kickstart.5.2.1.SV3.1.1.bin

Step 9

Read the release notes for the related image file. See the Cisco Nexus 1000V Release Notes.

Step 10

Determine the VSM status.

switch# show system redundancy status
Redundancy role
---------------
administrative:   standalone
operational:   standalone

Redundancy mode
---------------
administrative:   HA
operational:   None

This supervisor (sup-1)
-----------------------
Redundancy state:   Active
Supervisor state:   Active
Internal state:   Active with no standby

Other supervisor (sup-2)
------------------------
Redundancy state:   Not present

Step 11

Save the running configuration to the start configuration.

switch# copy running-config startup-config

Step 12

Update the boot variables and module images on the VSM.

switch# install all system bootflash:nexus-1000v.5.2.1.SV3.1.1.bin kickstart
bootflash: nexus-1000v-kickstart.5.2.1.SV3.1.1.bin

Verifying image bootflash:/nexus-1000v-kickstart-5.2.1.SV3.1.1.bin for boot variable "kickstart".
[####################] 100% -- SUCCESS

Verifying image bootflash:/nexus-1000v-5.2.1.SV3.1.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.1.1.bin.
[####################] 100% -- SUCCESS

Extracting "kickstart" version from image bootflash:/nexus-1000v-kickstart.5.2.1.SV3.1.1.bin.
[####################] 100% -- SUCCESS

Notifying services about system upgrade.
[####################] 100% -- SUCCESS

Compatibility check is done:
Module  bootable          Impact  Install-type  Reason
------  --------  --------------  ------------  ------
1       yes      disruptive         reset  Reset due to single supervisor

Images will be upgraded according to following table:
Module       Image         Running-Version             New-Version  Upg-Required
------  ----------  ----------------------  ----------------------  ------------
1      system           4.2(1)SV2(2.1)           5.2(1)SV3(1.1)           yes
1   kickstart           4.2(1)SV2(2.1)           5.2(1)SV3(1.1)           yes

Module  Running-Version     ESX Version                 VSM Compatibility  ESX Compatibility
------  ------------------  --------------------------- ------------------ ----------------------
3  4.2(1)SV2(2.1)      VMware ESXi 5.0.0            COMPATIBLE        COMPATIBLE
Releasebuild-1311175 (3.0)

Switch will be reloaded for disruptive upgrade.
Do you want to continue with the installation (y/n)?  [n]

Step 13

Continue with the installation by pressing Y.
Note:
If you press N, the installation exits gracefully.

Install is in progress, please wait.

Setting boot variables.
[####################] 100% -- SUCCESS

Performing configuration copy.
[####################] 100% -- SUCCESS

Finishing the upgrade, switch will reboot in 10 seconds.

Step 14

After the switch completes the reload operation, log in and verify that the switch is running the required software version.

Example:

switch# show version
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2014, 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(1.1)
system:    version 5.2(1)SV3(1.1)
kickstart image file is: bootflash:/nexus-1000v-kickstart-5.2.1.SV3.1.1.bin
kickstart compile time:  1/27/2014 14:00:00 [01/27/2011 22:26:45]
system image file is:    bootflash:/nexus-1000v-5.2.1.SV3.1.1.bin
system compile time:     1/27/2014 14:00:00 [01/28/2011 00:56:08]

Hardware
cisco Nexus 1000V Chassis ("Virtual Supervisor Module")
Intel(R) Xeon(R) CPU         with 2075740 kB of memory.
Processor Board ID T5056B050BB

Device name: BL1-VSM
bootflash:    3122988 kB

Kernel uptime is 0 day(s), 0 hour(s), 6 minute(s), 23 second(s)

plugin
Core Plugin, Ethernet Plugin, Virtualization Plugin
...

What to Do Next

Continue to Upgrading the VEMs Manually from Release 4.2(1)SV2(1.1x) and Later Releases to the Current Release.

Part IV. VMware Procedures

- Installing and Upgrading VMware

Chapter 6. Installing and Upgrading VMware

This chapter contains the following sections:

- Installing ESXi 5.1 Host Software Using the CLI

- Creating an Upgrade ISO with a VMware ESX Image and a Cisco Nexus 1000V VEM Image

Upgrading from VMware Releases 4.0, 4.1, 5.0, 5.1 to VMware Release 5.5

The steps to upgrade are as follows:

Note

From vCenter Server Release 5.1, you cannot directly upgrade an existing vCenter Server from an older version to Release 5.1. vSphere 5.1 introduces the vCenter Single Sign On service as part of the vCenter Server management infrastructure. This change affects vCenter Server installation, upgrading, and operation. When you upgrade to vCenter Server 5.1, the upgrade process installs vCenter Single Sign On first and then upgrades the vCenter Server.

Procedure

Step 1

Installing the vCenter Single Sign On

Step 2

Installing the vCenter Inventory Service

Step 3

Upgrading the vCenter Server

Step 4

Upgrading the vCenter Update Manager to Release 5.5

Step 5

Augmenting the Customized ISO for VMware Release 5.1 and Later

Step 6

Upgrading the ESXi Hosts to Release 5.x

Installing the vCenter Single Sign On

Before You Begin

- Download the upgrade ISO file that contains the ESXi image and the Cisco Nexus 1000V software image files.

- See the Cisco Nexus 1000V and VMware Compatibility Information document to determine the correct VIB Version, VEM Bundle, Host Build, vCenter Server, and Update Manager versions.

Procedure

Step 1

Navigate to the desired VMware vSphere installation file.
Note:
If you have the ISO image, you should mount it on the host.

Step 2

Double-click autorun.

Step 3

In the VMware vCenter Installer window, click vCenter Single Sign On.

Step 4

Click OK on the warning message and click Next.

Step 5

In the Patent Agreement window, click Next.

Step 6

In the License Agreement window, click the I agree to the terms in the license agreement radio button and Click Next.

Step 7

In the vCenter Single Sign On Deployment Type window, keep the default setting of installing vCenter Single SignOn with basic node and click Next.

Step 8

In the vCenter Single Sign On Type window, keep the default setting of Install basic vCenter Single Sign On and click Next.

Step 9

In the vCenter Single Sign On Information window, provide the single sign on server password and click Next.
Note:
Ensure your single sign on server password is different from the windows VM password.

Step 10

In the Database Options screen, click Next.

Step 11

In the Database User Information screen, provide the SSO password for RSA_DBA and RSA_USER.

Step 12

In the Local system information screen, provide the IP address of your local machine.

Step 13

Ignore the warning message and Click Ok.

Step 14

Click Next.

Step 15

Retain the default HTTPs port settings and Click Next.

Step 16

Click Install.

Step 17

Click Finish.

Installing the vCenter Inventory Service

Procedure

Step 1

In the VMware vCenter Installer window, click vCenter Inventory Service.

Step 2

Click Install.

Step 3

Choose the desired language and click OK.

Step 4

Click Next.

Step 5

In the Patent Agreement window, click Next.

Step 6

In the License Agreement window, click I agree to the terms in the license agreement radio button and click Next.

Step 7

In the Database Options screen, click Next .

Step 8

In the Local system information window, provide the IP address of your local machine.

Step 9

Ignore the warning message and Click Ok.

Step 10

Click Next.

Step 11

Retain the default configured port settings and Click Next.

Step 12

Retain the default Inventory size for vCenter Server deployment and Click Next .

Step 13

Enter the vCenter Single Sign On server credentials and Click Next .

Step 14

In the Certificate Installation for Secure Connection window, select Overwrite Certificates.

Step 15

Click Install.

Step 16

Click Finish.

Upgrading the vCenter Server

Note

This upgrade procedure applies to vCenter Server 5.0, 5.0 Update 1 and later, 5.1, and 5.5 versions.

Before You Begin

- Download the upgrade ISO file that contains your desired ESXi image and the desired Cisco Nexus 1000V image.

- See the Cisco Nexus 1000V and VMware Compatibility Information document to determine the correct VIB Version, VEM Bundle, Host Build, vCenter Server, and Update Manager versions.

Procedure

Step 1

Navigate to the VMware vSphere installation file.
Note:
If you have the ISO image, you should mount it on the host.

Step 2

Double-click autorun.

Step 3

In the VMware vCenter Installer screen, click vCenter Server.

Step 4

Click Install.

Step 5

Choose a language and click OK.

Step 6

Click Next.

Step 7

In the Patent Agreement screen, click Next.

Step 8

In the License Agreement screen, click the I agree to the terms in the license agreement radio button.

Step 9

Click Next.

Step 10

In the Database Options screen, click Next.

Step 11

Click the Upgrade existing vCenter Server database radio button and check the I have taken a backup of the existing vCenter Server database and SSL certificates in the folder: C:\ProgramData\VMware\VMware VirtualCenter\SSL\. check box.

Step 12

From the Windows Start Menu, click Run.

Step 13

Enter the name of the folder that contains the vCenter Server database and click OK.

Step 14

Drag a copy of the parent folder (SSL) to the desktop as a backup.

Step 15

Return to the installer program.

Step 16

Click Next.

Step 17

In the vCenter Agent Upgrade screen, click the Automatic radio button.

Step 18

Click Next.

Step 19

In the vCenter Server Service screen, check the Use SYSTEM Account check box.

Step 20

Click Next.

Step 21

Review the port settings and click Next.

Step 22

In the vCenter Server JVM Memory screen based on the number of hosts, click the appropriate memory radio button.

Step 23

Click Next.

Step 24

Click Install.

Step 25

Click Finish.
This step completes the upgrade of the vCenter Server.

Step 26

Upgrade the VMware vSphere Client to your desired ESXi version.

Step 27

Open the VMware vSphere Client.

Step 28

From the Help menu, choose About VMware vSphere.

Step 29

Confirm that the vSphere Client and the VMware vCenter Server are both the same VMware versions.

Step 30

Click OK, and exit the VMware vSphere Client.

What to Do Next

Complete the steps in Upgrading the vCenter Update Manager to Release 5.5.

Upgrading the vCenter Update Manager to Release 5.5

Note

This upgrade procedure also applies to vCenter Update Manager 5.0, 5.0 Update 1 and later, 5.1, and 5.5 versions.

Before You Begin

You have upgraded the vCenter Server to the desired VMware ESXi version.

Procedure

Step 1

On the local drive, double-click VMware-UpdateManager.

Step 2

Choose a language and click OK.
The Update Manager Installer opens.

Step 3

Click OK to upgrade.

Step 4

Click Next to begin.

Step 5

Click Next at the Patent Agreement.

Step 6

Click the I agree to the terms in the license agreement radio button.

Step 7

Click Next.

Step 8

In the VMware vCenter Server Information area, verify the IP address and username.

Step 9

In the Password field, enter your password.

Step 10

Click Next.

Step 11

Click Next.

Step 12

Click the Yes, I want to upgrade my Update Manager database radio button.

Step 13

Click Next.

Step 14

Verify the Update Manager port settings.

Step 15

Click Next.

Step 16

Verify the proxy settings.

Step 17

Click Next.

Step 18

Click Install to begin the upgrade.

Step 19

Click OK to acknowledge that a reboot will be required to complete the setup.
During the upgrade, the vSphere Client is disconnected.

Step 20

Click Cancel for the attempt to reconnect.

Step 21

Click OK in the Server Connection Invalid dialog box.

Step 22

Click Finish.

Step 23

Reboot the VUM/vCenter Server.

Step 24

In the Shut Down Windows dialog box from the Option drop-down list, choose Other (Planned), enter a value in the comment field, and click OK.

Step 25

After the system has rebooted, browse to the C:\ProgramData\VMware\VMware Update Manager\Logs\ folder.

Step 26

Open the vmware-vum-server-log4cpp file.

Step 27

From the VMware vCenter Server’s Plug-in menu, choose Manage Plug-ins.

Step 28

Under Available Plug-ins, click Download and Install for VMware vSphere Update Manager Extension.

What to Do Next

Complete the steps in Augmenting the Customized ISO for VMware Release 5.1 and Later.

Augmenting the Customized ISO for VMware Release 5.1 and Later

Before You Begin

If you are using a QLogic NIC, download the driver to include in the customized ISO for that specific NIC.

Procedure

If the ESXi host that is being upgraded needs any Async drivers that are not already in the VMware release, see the respective vendor documentation for the drivers and the procedure to update the customized ISO.

What to Do Next

Complete the steps in Upgrading the ESXi Hosts to Release 5.x.

Upgrading the ESXi Hosts to Release 5.x

Note

- This upgrade procedure also applies to ESXi hosts 5.0, 5.0 Update 1, 5.1 and 5.5 versions.

- If you have multiple vmkernel interfaces on the same subnet when upgrading you ESXi host, you must place your management vmkernel interface into the Layer 3 capable port profile.

Procedure

Step 1

In the vSphere Client, click Home.

Step 2

Click the Update Manager tab.

Step 3

Click the ESXi Image tab.

Step 4

Click the Import ESXi Image link in the ESXi Image window.

Step 5

Click the Browse button and navigate to the customized upgrade ISO image.

Step 6

Choose the upgrade file and click Open.

Step 7

To import the ISO file, click Next.

Step 8

When the upgrade ISO file is uploaded, click Next.

Step 9

In the Baseline Name and Description area, enter a name for the baseline and an optional description.

Step 10

Click Finish.

Step 11

In the vSphere Client, choose Home > Hosts and Clusters.

Step 12

In the left-hand pane, select the host or cluster to upgrade and click the Update Manager tab.

Step 13

Click Attach.

Step 14

In the Individual Baselines by Type area, check your upgrade baseline's check box.

Step 15

Click Attach.

Step 16

Click Scan.
After the scan, the baseline will display non-compliant.

Step 17

In the Confirm Scan dialog box, check the Upgrades check box and click Scan.

Step 18

In the Upgrade Details window, if the Compliance State has a value of Incompatible, reboot the host with the baseline attached.
After the reboot, the Compliance State will have a value of Non-Compliant.

Step 19

When you are finished viewing the upgrade details, click Close.

Step 20

Verify that all hosts are Non-Compliant.

Step 21

Click Remediate.

Step 22

Click Next

Step 23

In the End User License Agreement screen, check the I accept the terms and license agreement check box.

Step 24

Click Next

Step 25

In the ESXi 5.x Upgrade window, click Next.

Step 26

Click Next.

Step 27

In the Maintenance Mode Options area, check the Disable any removable media devices connected to the virtual machines on the host check box.

Step 28

Click Next.

Step 29

In the Cluster Remediation Options window, check all check boxes.

Step 30

Click Next.

Step 31

Click Finish to begin the remediation.

Step 32

To check the host versions, click each host in the left-hand pane and confirm that 5.1 appears in the top-left corner of the right-hand pane and that the version information matches the contents of the Cisco Nexus 1000V and VMware Compatibility Information.

Step 33

The upgrade can also be confirmed by running the show module command on the VSM and observing that the VEMs are on the correct build.

The upgrade is complete.

What to Do Next

Complete the steps in Verifying the Build Number and Upgrade.

Creating the Host Patch Baseline for 5.1 Update 1

Before You Begin

Ensure you configure the VMware Update Manager Download settings with proxy enabled and VMware production portal links for VMware ESX/ESXi in connected state and download those images into the VUM patch repository.

Procedure

Step 1

Under Home > Solutions and Applications > Update Manager, select Baselines and Groups tab.

Step 2

Under Baseline, click Create to create a baseline.

Step 3

In the Baseline Name and Type window, enter a name for the baseline, select the Host Patch radio button and click Next.

Step 4

In the Patch Options window, select the Fixed radio button and click Next.

Step 5

In the Patches window, select the required patch to upgrade to version 5.1 Update 1 and move the selected patch to Fixed patches to Add column and click Next.
Note:
To know the 5.1 update 1 patches, refer to Click Here .

Note:
In the combined upgrade scenario, add the required Cisco Nexus 1000V VEM patch that corresponds to 5.1 Update 1 release to the Fixed patches to Add column along with ESXi 5.1 Update 1 patches. You can get the required Cisco Nexus 1000V VEM patches into the VUM patch repository either from www.cisco.com, VMWare production portal links or through the VSM home page.

Upgrading the ESXi Hosts to Release 5.1 Update 1 using VMware Update Manager

Note

Follow the same procedure to upgrade ESXi hosts 5.0 to 5.0 Update 1 and later.

Procedure

Step 1

In the vSphere Client, choose Home > Hosts and Clusters .

Step 2

From the left navigation pane, select the host or cluster that needs to be upgraded and click Update Manager.

Step 3

Click Attach.

Step 4

In the Individual Baselines by Type area, select your Patch baseline's radio button check box.

Step 5

Click Attach.

Step 6

Click Scan.

Step 7

In the Confirm Scan dialog box, check the Patches and extensions box and click Scan.
Verify if all the hosts are non-compliant.

Step 8

Click Stage.

Step 9

In Baseline Selection window, keep the default selected baseline and click Next.

Step 10

In Patch and Extension exclusion window, keep the default selected baseline and click Next.

Step 11

Click Finish.

Step 12

Click Remediate and click Next.

Step 13

In Patch and Extension exclusion window, keep the default selected baseline and click Next.

Step 14

Click Next.

Step 15

In the Host Remediate Options window, under Maintenance Mode Options, select the Disable any removable media devices connected to the virtual machines on the host check box.
Note:
If you have stateless host in your setup, select Enable Patch Remediation on Powered on PXE booted ESXi hosts radio button.

Step 16

Click Next.

Step 17

In the Cluster Remediation Options window, select all the check boxes and click Next.

Step 18

Click Finish to begin the remediation.
To check the host versions, on the left-hand pane, click on each host to confirm if version 5.1 appears in the top-left corner of the right-hand pane and the version information matches the information provided under the Cisco Nexus 1000V and VMware Compatibility Information guide.

You can also confirm if the upgrade was successful by executing the show module command on the VSM and check if the VEMs are running the correct build.

Note:
Follow the same procedure for combined upgrade of 5.0 or 5.1 and the initial version of Cisco Nexus 1000V to 5.0 Update1 or 5.1 Update1 and the upgraded version of Cisco Nexus 1000V.

Upgrading the ESXi Hosts to Release 5.1 Update 1 using the CLI

You can upgrade an ESXi host by installing a VMware patch or update with the compatible Cisco Nexus 1000V VEM software.

Before You Begin

- 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 when the vCLI is installed.

Note

The vSphere Command-Line Interface (vSphere CLI) 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 vSphere CLI commands against a vCenter Server system and target any 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 into the ESX host.

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

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

- You know the name of the ESXi and VEM software file to be installed.

Procedure

Step 1

Download the VEM software and copy them to the local host.

Step 2

Determine the upgrade method that you want to use.
If you are using the vCLI, enter the esxcli command and install the ESXi and VEM software simultaneously.

esxcli software vib install -v full-path-to-vib
Note:
When using the esxcli software VIB install command, you must log in to each host and enter the command. ESXi 5.1 expects the VIB to be in the /var/log/vmware directory if the absolute path is not specified.

# esxcli software vib update -d /var/tmp/update-from-esxi5.1-5.1_update01.zip
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VMware_bootbank_esx-base_5.1.0-0.12.1065491, VMware_locker_tools-light_5.1.0-0.12.1065491
VIBs Removed: VMware_bootbank_esx-base_5.1.0-0.3.799733, VMware_locker_tools-light_5.0.0-0.0.799733
VIBs Skipped: VMware_bootbank_ata-pata-amd_0.3.10-3vmw.510.0. 3.799733, VMware_bootbank_ata-pata-atiixp_0.4.6-3vmw.510.0. 3.799733,
<============================================================================================================>
VMware_bootbank_scsi-qla4xxx_5.01.03.2-3vmw.510.0.3.799733., VMware_bootbank_uhci-usb-uhci_1.0-3vmw.510.0.3.799733

What to Do Next

Complete the steps under Verifying the Build Number and Upgrade

- Verifying the Build Number and Upgrade

Verifying the Build Number and Upgrade

Before You Begin

- You have upgraded the VSMs and VEMs to the current Cisco Nexus 1000V release.

Note

The VSM upgrade will not proceed if ESX/ESXi 4.0 or 4.1 is part of the DVS. You must either remove ESX 4.0 or 4.1 from the DVS and proceed with VSM upgrade or upgrade ESX 4.0 or 4.1 to 5.0 or later releases and proceed with the VSM upgrade.

- You have upgraded the vCenter Server to VMware Release 5.1 Update 1.

- You have upgraded the VMware Update Manager to VMware Release 5. 1 Update 1.

- You have upgraded your ESX/ESXi hosts to VMware Release 5. 1 Update 1.

Procedure

Step 1

Verify the build number on the ESXi host.

~ # vmware -v
VMware ESXi 5.1.0 build-1065491
VMware ESXi 5.1.0 Update 1

Step 2

Verify the upgrade on the Cisco Nexus 1000V.

switch# show module

N1KV-VSM# show mod
Mod  Ports  Module-Type                      Model              Status
---  -----  -------------------------------- ------------------ ------------
1    0      Virtual Supervisor Module        Nexus1000V         active *
2    0      Virtual Supervisor Module        Nexus1000V         ha-standby
3    1022   Virtual Ethernet Module          NA                 ok
Mod  Sw               Hw
---  ---------------  ------
1    5.2(1)SV3(1.1)    0.0
2    5.2(1)SV3(1.1)    0.0
3    5.2(1)SV3(1.1)    3.1
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-09-00 to 02-00-0c-00-09-80  NA
Mod  Server-IP        Server-UUID                           Server-Name
---  ---------------  ------------------------------------  --------------------
1    10.105.235.74   NA                                    NA
2    10.105.235.74   NA                                    NA
3    10.105.235.72   42064d20-4e52-62d1-e0ee-0b14be4388d6  mnn-update1-esxi-statefull

* this terminal session

Upgrading a VMware ESXi 5.0 Stateful Host to VMware ESXi 5.0 Patch 01

Procedure

Step 1

Copy the ESXi 5.0 Patch 01 bundle (ESXi500- 201301152108.zip) to the host.

Step 2

Upgrade the host to ESXi 5.0 Patch 01.

~ # esxcli software vib update -d /vmfs/volumes/newnfs/MN-patch01/ESXi500-201301152108.zip
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: VMware_bootbank_esx-base_5.0.0-0.3.474610, VMware_locker_tools-light_5.0.0-0.3.474610
VIBs Removed: VMware_bootbank_esx-base_5.0.0-0.0.469512, VMware_locker_tools-light_5.0.0-0.0.469512
VIBs Skipped: VMware_bootbank_ata-pata-amd_0.3.10-3vmw.500.0.0.469512, VMware_bootbank_ata-pata-atiixp_0.4.6-3vmw.500.0.0.469512,
<============================================================================================================>
VMware_bootbank_scsi-qla4xxx_5.01.03.2-3vmw.500.0.0.469512, VMware_bootbank_uhci-usb-uhci_1.0-3vmw.500.0.0.469512

Installing ESXi 5.1 Host Software Using the CLI

You can upgrade an ESXi host by installing a VMware patch or update with the compatible Cisco Nexus 1000V VEM software.

Before You Begin

- If you are using the 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 when the vCLI is installed.

Note

The vSphere Command-Line Interface (vSphere CLI) 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 vSphere CLI commands against a vCenter Server system and target any 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 into the ESX host.

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

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

- You know the name of the ESXi and VEM software file to be installed.

Procedure

Step 1

Download the VEM bits and copy them to the local host.

Step 2

Determine the upgrade method that you want and use the following steps.

1. ~ # esxcli software vib install -d full_path_to_VEM_bundle

2. ~ # esxcli software vib install –vfull_path_to_VIB

If you are using the vCLI, enter the esxcli command and install the ESXi and VEM software simultaneously.
Note:
When using the esxcli software vib install command, you must log in to each host and enter the command. ESXi 5.1 expects the VIB to be in the /var/log/vmware directory if the absolute path is not specified.

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

Step 3

Verify that the installation was successful by typing the following commands.
Note:
If the VEM Agent is not running, see the Cisco Nexus 1000V Troubleshooting Guide.

1. ~ # vmware -v -l

2. ~ # vemcmd show version

3. ~ # vem status -v

4. ~ # esxcli software vib list | grep name

5. ~ # vem version -v

Step 4

switch# show module

Verify that the VEM has been upgraded by entering the following command from the VSM.

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

Step 5

Do one of the following:

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

2. If not, see the Recreating the Cisco Nexus 1000V Installation section in the Cisco Nexus 1000V Troubleshooting Guide.

The following example shows how to install ESXi 5.1 software using the CLI.

~ # esxcli software vib install -d /var/log/vmware/VEM510-201408170106-BG-release.zip
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: Cisco_bootbank_cisco-vem-v170-esx_170-5.2.1.3.1.1.0-3.1.1
VIBs Removed:
VIBs Skipped:

~ # esxcli software vib install –v /var/log/vmware/cross_cisco-vem-v170-5.2.1.3.1.1.0-3.1.1.vib
Installation Result
Message: Operation finished successfully.
Reboot Required: false
VIBs Installed: Cisco_bootbank_cisco-vem-v170-esx_5.2.1.3.1.1.0-3.1.1
VIBs Removed:
VIBs Skipped:
~ #
~ # vmware -v -l
VMware ESXi 5.1.0 build-1029768
VMware ESXi 5.1.0 Update 1
~ #

~ # vemcmd show version
VEM Version: 5.2.1.3.1.1.0-3.1.1
VSM Version: 5.2(1)SV3(1.1) [build 5.2(1)SV3(1.1)]
System Version: VMware ESXi 5.1.0 Releasebuild-1029768

~ # vem status -v
Package vssnet-esxmn-next-release
Version 5.2.1.3.1.1.0-3.1.1
Build 1
Date Mon Aug 4 23:33:48 PDT 2014

VEM modules are loaded

Switch Name      Num Ports   Used Ports  Configured Ports  MTU     Uplinks
vSwitch0         128         6           128               1500    vmnic0

DVS Name         Num Ports   Used Ports  Configured Ports  MTU     Uplinks
p-1              1024        13          1024              1500    vmnic5

VEM Agent (vemdpa) is running

~ # esxcli software vib list | grep cisco
cisco-vem-v170-esx 5.2.1.3.1.1.0-3.1.1 Cisco PartnerSupported 2014-08-05
~ #

~ # vem version -v
Running esx version -1483097 x86_64
VEM Version: 5.2.1.3.1.1.0-3.1.1
VSM Version: 5.2(1)SV3(1.1)
System Version: VMware ESXi 5.1.0 Releasebuild-1029768

~ #
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    1022   Virtual Ethernet Module           NA                  ok
6    1022   Virtual Ethernet Module           NA                  ok

Mod  Sw                  Hw
---  ------------------  ------------------------------------------------
1    5.2(1)SV3(1.1)  0.0
2    5.2(1)SV3(1.1)  0.0
3    5.2(1)SV3(1.1)      VMware ESXi 5.1.0 Releasebuild-911593 (3.1)
6    5.2(1)SV3(1.1)      VMware ESXi 5.1.0 Releasebuild-1029768 (3.1)

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#

Creating an Upgrade ISO with a VMware ESX Image and a Cisco Nexus 1000V VEM Image

Before You Begin

- Install the VMware PowerCLI on a Windows platform. For more information, see the vSphere PowerCLI Installation Guide.

- On the same Windows platform, where the VMware PowerCLI is installed, do one of the following:

- Download the ESX depot, which is a .zip file, to a local file path.

- Download the VEM offline bundle, which is a .zip file, to a local file path.

Procedure

Step 1

Start the VMWare PowerCLI application.

Step 2

Connect to the vCenter Server by using the Connect-VIServer IP_address -User Administrator -Password password_name command.

Step 3

Load the ESX depot by using the Add-ESXSoftwareDepot path_name\file_name command.

Step 4

Display the image profiles by using the Get-EsxImageProfile command.

Step 5

Clone the ESX standard image profile by using the New-ESxImageProfile -CloneProfile ESXImageProfile_name -Name clone_profile command.
Note:
The image profiles are usually in READ-ONLY format. You must clone the image profile before adding the VEM image to it.

Step 6

Load the Cisco Nexus 1000V VEM offline bundle by using the Add-EsxSoftwareDepot VEM_offline_bundle command.

Step 7

Confirm that the n1kv-vib package is loaded by using the Get-EsxSoftwarePackage -Name package_name command.

Step 8

Bundle the n1kv-package into the cloned image profile by using the Add-EsxSoftwarePackage -ImageProfile n1kv-Image -SoftwarePackage cloned_image_profile command.

Step 9

Verify that the Cisco VIB is present by listing all the VIBs in the cloned image profile by entering the following commands.

1. $img = Get-EsxImageProfile n1kv-Image

2. $img.vibList

Verify that the Cisco VIB is present by listing all the VIBs in the cloned image profile.

Step 10

Export the image profile to an ISO file by using the Export-EsxImageProfile -ImageProfile n1kv-Image -FilePath iso_filepath command.

This example shows how to create an upgrade ISO with a VMware ESX image and a Cisco VEM image.

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.

vSphere PowerCLI> Connect-VIServer 10.105.231.40 -User administrator -Password 'XXXXXXXX'

Working with multiple default servers?

Select [Y] if you want to work with more than one default servers. In this
case, every time when you connect to a different server using Connect-VIServer,
the new server connection is stored in an array variable together with the
previously connected servers. When you run a cmdlet and the target servers
cannot be determined from the specified parameters, the cmdlet runs against all
servers stored in the array variable.
Select [N] if you want to work with a single default server. In this case,
when you run a cmdlet and the target servers cannot be determined from the
specified parameters, the cmdlet runs against the last connected server.

WARNING: WORKING WITH MULTIPLE DEFAULT SERVERS WILL BE ENABLED BY DEFAULT
IN A FUTURE RELEASE. You can explicitly set your own preference at any time by
using the DefaultServerMode parameter of Set-PowerCLIConfiguration.

[Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"): Y

Name                           Port  User
----                           ----  ----
10.105.231.40                  443   administrator

vSphere PowerCLI> Add-EsxSoftwareDepot 'C:\Documents and Settings\Administrator\Desktop\upgrade\229\VMware-ESXi-5.1.0-799733-depot.zip'

Depot Url
---------
zip:C:\Documents and Settings\Administrator\Desktop\upgrade\229\VMware-ESXi-...

vSphere PowerCLI> Get-EsxImageProfile

Name                           Vendor          Last Modified   Acceptance Level
----                           ------          -------------   ----------------
ESXi-5.1.0-20121201001s-no-... VMware, Inc.    12/7/2012 7:... PartnerSupported
CN1-CY                         CISCO           4/22/2013 11... PartnerSupported
ESXi-5.1.0-20121204001-stan... VMware, Inc.    12/7/2012 7:... PartnerSupported
ESXi-5.1.0-20121201001s-sta... VMware, Inc.    12/7/2012 7:... PartnerSupported
ESXi-5.1.0-799733-no-tools     VMware, Inc.    8/2/2012 3:0... PartnerSupported
ESXi-5.1.0-20121204001-no-t... VMware, Inc.    12/7/2012 7:... PartnerSupported
ESXi-5.1.0-799733-standard     VMware, Inc.    8/2/2012 3:0... PartnerSupported

vSphere PowerCLI> New-EsxImageProfile -CloneProfile ESXi-5.1.0-799733-standard -Name FINAL

cmdlet New-EsxImageProfile at command pipeline position 1
Supply values for the following parameters:
(Type !? for Help.)
Vendor: CISCO

Name                           Vendor          Last Modified   Acceptance Level
----                           ------          -------------   ----------------
FINAL                          CISCO           8/2/2012 3:0... PartnerSupported

vSphere PowerCLI> Add-EsxSoftwareDepot 'C:\Documents and Settings\Administrator\Desktop\upgrade\229
\cisco-vem-v164-4.2.1.2.2.2.0-3.1.1.zip'

Depot Url
---------
zip:C:\Documents and Settings\Administrator\Desktop\upgrade\229\cisco-vem-v1...

vSphere PowerCLI> Get-EsxSoftwarePackage cisco*

Name                     Version                        Vendor     Creation Dat
e
----                     -------                        ------     ------------
cisco-vem-v164-esx       4.2.1.2.2.2.0-3.1.1          Cisco      1/24/2014...

vSphere PowerCLI> Add-EsxSoftwarePackage -SoftwarePackage cisco-vem-v164-esx -ImageProfile FINAL

Name                           Vendor          Last Modified   Acceptance Level
----                           ------          -------------   ----------------
FINAL                          CISCO           1/24/2014 3:... PartnerSupported

vSphere PowerCLI> $img = Get-EsxImageProfile FINAL

vSphere PowerCLI> $img.vibList

Name                     Version                        Vendor     Creation Dat
e
----                     -------                        ------     ------------
scsi-bnx2i               1.9.1d.v50.1-5vmw.510.0.0.7... VMware     8/2/2012 ...
sata-sata-promise        2.12-3vmw.510.0.0.799733       VMware     8/2/2012 ...
net-forcedeth            0.61-2vmw.510.0.0.799733       VMware     8/2/2012 ...
esx-xserver              5.1.0-0.0.799733               VMware     8/2/2012 ...
misc-cnic-register       1.1-1vmw.510.0.0.799733        VMware     8/2/2012 ...
net-tg3                  3.110h.v50.4-4vmw.510.0.0.7... VMware     8/2/2012 ...
scsi-megaraid-sas        5.34-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-megaraid-mbox       2.20.5.1-6vmw.510.0.0.799733   VMware     8/2/2012 ...
scsi-ips                 7.12.05-4vmw.510.0.0.799733    VMware     8/2/2012 ...
net-e1000e               1.1.2-3vmw.510.0.0.799733      VMware     8/2/2012 ...
sata-ahci                3.0-13vmw.510.0.0.799733       VMware     8/2/2012 ...
sata-sata-svw            2.3-3vmw.510.0.0.799733        VMware     8/2/2012 ...
net-cnic                 1.10.2j.v50.7-3vmw.510.0.0.... VMware     8/2/2012 ...
net-e1000                8.0.3.1-2vmw.510.0.0.799733    VMware     8/2/2012 ...
ata-pata-serverworks     0.4.3-3vmw.510.0.0.799733      VMware     8/2/2012 ...
scsi-mptspi              4.23.01.00-6vmw.510.0.0.799733 VMware     8/2/2012 ...
ata-pata-hpt3x2n         0.3.4-3vmw.510.0.0.799733      VMware     8/2/2012 ...
net-s2io                 2.1.4.13427-3vmw.510.0.0.79... VMware     8/2/2012 ...
esx-base                 5.1.0-0.0.799733               VMware     8/2/2012 ...
net-vmxnet3              1.1.3.0-3vmw.510.0.0.799733    VMware     8/2/2012 ...
net-bnx2                 2.0.15g.v50.11-7vmw.510.0.0... VMware     8/2/2012 ...
cisco-vem-v164-esx       4.2.1.2.2.2.0-3.1.1            Cisco      1/24/2014...
scsi-megaraid2           2.00.4-9vmw.510.0.0.799733     VMware     8/2/2012 ...
ata-pata-amd             0.3.10-3vmw.510.0.0.799733     VMware     8/2/2012 ...
ipmi-ipmi-si-drv         39.1-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-lpfc820             8.2.3.1-127vmw.510.0.0.799733  VMware     8/2/2012 ...
ata-pata-atiixp          0.4.6-4vmw.510.0.0.799733      VMware     8/2/2012 ...
esx-dvfilter-generic-... 5.1.0-0.0.799733               VMware     8/2/2012 ...
net-sky2                 1.20-2vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-qla2xxx             902.k1.1-9vmw.510.0.0.799733   VMware     8/2/2012 ...
net-r8169                6.011.00-2vmw.510.0.0.799733   VMware     8/2/2012 ...
sata-sata-sil            2.3-4vmw.510.0.0.799733        VMware     8/2/2012 ...
scsi-mpt2sas             10.00.00.00-5vmw.510.0.0.79... VMware     8/2/2012 ...
sata-ata-piix            2.12-6vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-hpsa                5.0.0-21vmw.510.0.0.799733     VMware     8/2/2012 ...
ata-pata-via             0.3.3-2vmw.510.0.0.799733      VMware     8/2/2012 ...
scsi-aacraid             1.1.5.1-9vmw.510.0.0.799733    VMware     8/2/2012 ...
scsi-rste                2.0.2.0088-1vmw.510.0.0.799733 VMware     8/2/2012 ...
ata-pata-cmd64x          0.2.5-3vmw.510.0.0.799733      VMware     8/2/2012 ...
ima-qla4xxx              2.01.31-1vmw.510.0.0.799733    VMware     8/2/2012 ...
net-igb                  2.1.11.1-3vmw.510.0.0.799733   VMware     8/2/2012 ...
scsi-qla4xxx             5.01.03.2-4vmw.510.0.0.799733  VMware     8/2/2012 ...
block-cciss              3.6.14-10vmw.510.0.0.799733    VMware     8/2/2012 ...
scsi-aic79xx             3.1-5vmw.510.0.0.799733        VMware     8/2/2012 ...
tools-light              5.1.0-0.0.799733               VMware     8/2/2012 ...
uhci-usb-uhci            1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
sata-sata-nv             3.5-4vmw.510.0.0.799733        VMware     8/2/2012 ...
sata-sata-sil24          1.1-1vmw.510.0.0.799733        VMware     8/2/2012 ...
net-ixgbe                3.7.13.6iov-10vmw.510.0.0.7... VMware     8/2/2012 ...
ipmi-ipmi-msghandler     39.1-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-adp94xx             1.0.8.12-6vmw.510.0.0.799733   VMware     8/2/2012 ...
scsi-fnic                1.5.0.3-1vmw.510.0.0.799733    VMware     8/2/2012 ...
ata-pata-pdc2027x        1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
misc-drivers             5.1.0-0.0.799733               VMware     8/2/2012 ...
net-enic                 1.4.2.15a-1vmw.510.0.0.799733  VMware     8/2/2012 ...
net-be2net               4.1.255.11-1vmw.510.0.0.799733 VMware     8/2/2012 ...
net-nx-nic               4.0.558-3vmw.510.0.0.799733    VMware     8/2/2012 ...
esx-xlibs                5.1.0-0.0.799733               VMware     8/2/2012 ...
net-bnx2x                1.61.15.v50.3-1vmw.510.0.0.... VMware     8/2/2012 ...
ehci-ehci-hcd            1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
ohci-usb-ohci            1.0-3vmw.510.0.0.799733        VMware     8/2/2012 ...
net-r8168                8.013.00-3vmw.510.0.0.799733   VMware     8/2/2012 ...
esx-tboot                5.1.0-0.0.799733               VMware     8/2/2012 ...
ata-pata-sil680          0.4.8-3vmw.510.0.0.799733      VMware     8/2/2012 ...
ipmi-ipmi-devintf        39.1-4vmw.510.0.0.799733       VMware     8/2/2012 ...
scsi-mptsas              4.23.01.00-6vmw.510.0.0.799733 VMware     8/2/2012 ...

vSphere PowerCLI> Export-EsxImageProfile -ImageProfile FINAL -FilePath 'C:\Documents and Settings\Administrator\Desktop\FINAL.iso' -ExportToIso

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: Click Here . 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. (1110R)