The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains the following sections:
Installing the Cisco Nexus 1000V Software using the Installer Application
The Cisco Nexus 1000V Installer App is the graphical user interface (GUI) that you use to install the VSMs in high availability (HA) mode and the VEMs on ESX/ESXi hosts.
To prevent a disruption in connectivity, all port profiles are created with a system VLAN. You can change this after migration if needed.
The host and adapter migration process moves all physical network interface cards (PNICs) used by the VSM from the VMware vSwitch to the Cisco Nexus 1000V Distributed Virtual Switch (DVS).
The migration process supports Layer 2 and Layer 3 topologies.
The installer app does the following:
![]() Note | You can use the same VLAN for control, packet, and management port groups, but you can also use separate VLANs for flexibility. If you use the same VLAN, make sure that the network segment where the VLAN resides has adequate bandwidth and latency. |
![]() Note | The Installation Application requires you to satisfy all the prerequisites. |
If you migrate the host and adapters from the VMware vSwitch to the Cisco Nexus 1000V DVS:
The ESX or ESXi hosts to be used for the Cisco Nexus 1000V have the following prerequisites:
The upstream switch from the Cisco Nexus 1000V has the following prerequisites:
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
The Cisco Nexus 1000V Installer app has the following configuration guidelines and limitations:
![]() Caution | Host management connectivity might be interrupted if the management vmknic or vswif are migrated and the uplink’s native VLAN is not correctly specified in the setup process. |
To improve redundancy, install primary and secondary VSM VMs on separate hosts that are connected to different upstream switches.
Installing the Cisco Nexus 1000V Software using the Installer Application
There are two procedures for installing the Cisco Nexus 1000V VSMs. The standard procedure is for the novice administrator. The custom procedure is for the more experienced administrator. The custom procedure has more configuration inputs to be used by administrators already familiar with the installation process and requiring more installation options.
![]() Note | The VSM IP address must be in the same management VLAN as the host. |
![]() Note | The hosts that will be installed as VEMs should not have any Cisco Nexus 1000V vSphere Installation Bundle (VIB) files. Uninstall any Cisco Nexus 1000V VIBs before starting the Cisco Nexus 1000V Installer App. |
Step 1 | Double-click the installation application icon or at the command-line interface, enter the following command to start the Cisco Nexus 1000V Installer App. java -jar Nexus1000V-install_CNX.jar | ||
Step 2 | In the Cisco Nexus 1000V Installer App screen, click the Virtual Ethernet Module Installation radio button. | ||
Step 3 | After reading the prerequisites, click Next. | ||
Step 4 | In the VEM Enter vCenter Credentials screen, do the following: | ||
Step 5 | In the Enter VSM IP & Credentials screen, do the following: | ||
Step 6 | In the Confirmation screen, do one of the following: | ||
Step 7 | In the Adding Modules screen, do the following: | ||
Step 8 | In the VEM Hosts Selection screen, do the following: | ||
Step 9 | In the VEM Host Review screen, do the following: | ||
Step 10 | In the VEM Summary screen, click Close.
For more information about troubleshooting VSMs and VEMs, see the Cisco Nexus 1000V Troubleshooting Guide. |
To establish connection between the VSM and the vCenter Server, perform the following steps:
Step 1 | Double-click on the installation application icon. Or, at the command-line interface, enter the following command to start the Cisco Nexus 1000V. java -jar Nexus1000V-install_CNX.jar |
Step 2 | In the Cisco Nexus 1000V Installer App screen, click the VC Connection radio button. |
Step 3 | After reading the Prerequisites, click Next. |
Step 4 | In the Enter vCenter Credentials screen, do the following: |
Step 5 | In the Enter VSM IP & Credentials screen, do the following: |
Installing the Cisco Nexus 1000V Software Manually
ESX or ESXi hosts have the following prerequisites:
![]() 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.
VSM VM Component |
Minimum Requirement |
---|---|
Platform |
64 bit |
Type |
Other 64-bit Linux (recommended) |
Processor |
1 |
RAM (configured and reserved) |
3 GB1 |
NIC |
3 |
SCSI Hard Disk |
3 GB with LSI Logic Parallel adapter |
CPU speed |
2048 MHz2 |
The Cisco Nexus 1000V VSM software has the following are prerequisites:
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. |
The upstream switch from the Cisco Nexus 1000V has the following prerequisites:
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
The Cisco Nexus 1000V VEM software has the following prerequisites:
![]() Note | 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 will fail. You should manually VMotion the vCenter Server VM to another host before you perform an upgrade. |
The Cisco Nexus 1000V software installation has the following configuration guidelines and limitations:
![]() Note | We recommend you to monitor and install all the relevant patch applications from VMware ESX host server. |
Installing the Cisco Nexus 1000V Software Using ISO or OVA Files
Installing the VSM Software
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 3 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 2048 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. | ||||
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.
| ||||
Step 13 | Enter the domain ID. Enter the domain id<1-4095>: 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: | ||||
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 4.2(1)SV2(2.2), Do you want to reconfigure? (yes/no) [n] yes Current vem feature level is set to 4.2(1)SV2(2.2) 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 no control vlan no packet vlan svs mode L3 interface mgmt0 | ||||
Step 32 | Do one of the following: Would you like to edit the configuration? (yes/no) [n]:no | ||||
Step 33 | Enter
yes to use and save this configuration, answer
yes.
Use this configuration and save it? (yes/no) [y]: yes [########################################] 100% The new configuration is saved into nonvolatile storage.
| ||||
Step 34 | Create the SVS connection manually or go to Establishing the SVS Connection. |
Before beginning this procedure, you must know or do the following:
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.
| ||||||||||||||
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:
| ||||||||||||||
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: | ||||||||||||||
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:
Would you like to edit the configuration? (yes/no) [n]:no | ||||||||||||||
Step 42 | Enter yes to use and save this configuration.
Use this configuration and save it? (yes/no) [y]: yes [########################################] 100% The new configuration is saved into nonvolatile storage.
| ||||||||||||||
Step 43 | Create the SVS connection manually or go to Establishing the SVS Connection. |
Step 1 | Open the vSphere Client. |
Step 2 | Choose the
primary VSM.
![]() |
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.
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: |
Startup and shutdown settings are complete.
Step 1 |
In the vSphere Client window, choose Hosts and Clusters > Networking.
![]() | ||
Step 2 | In the vSphere Client Hosts window, choose the DVS and click the Hosts tab. ![]() | ||
Step 3 | In the Add Hosts to DVS window, right-click the DVS and from the drop-down list, choose Add Host. ![]() | ||
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:
| ||
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.
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. |
Based on the version of VMware ESX/ESXi software that is running on the server, there are different installation paths.
![]() Note | This procedure applies for VMware 5.0 host and later ESXi versions. |
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: |
~ # esxcli software vib install -v /Cisco_bootbank_cisco-vem-v164-esx_4.2.1.2.2.2.0-3.0.1.vib Installation Result Message: Operation finished successfully. Reboot Required: false VIBs Installed: Cisco_bootbank_cisco-vem-v164-esx_4.2.1.2.2.2.0-3.0.1.vib VIBs Removed: Cisco_bootbank_cisco-vem-v144-esx_4.2.1.1.5.2.0-3.0.1 VIBs Skipped ~ # vem status -v Package vssnet-esxmn-release Version 4.2.1.2.2.2.0-3.0.1 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 256 19 256 1500 vmnic7,vmnic6,vmnic3,vmnic2,vmnic1,vmnic0 VEM Agent (vemdpa) is running ~ # esxcli software vib list | grep cisco cisco-vem-v164-esx 4.2.1.2.2.2.0-3.0.1 Cisco PartnerSupported 2014-01-25 ~ # ~ # vemcmd show version VEM Version: 4.2.1.2.2.2.0-3.0.1 VSM Version: 4.2(1)SV2(2.2) [build 4.2(1)SV2(2.2)] System Version: VMware ESXi 5.0.0 Releasebuild-843203
![]() Note | This procedure applies for VMware 5.0 host and later ESXi versions. |
Step 1 | Copy the VEM software to the NFS storage which is mounted on the ESXi 5.0 host. | ||
Step 2 | esxcli --server=[server ip] software vib install --depot=Path_to_NFS_storage_mounted _on_ESXi_5.0 host
| ||
Step 3 | esxcli --server=host_ip_address software vib list Verify that the VEM software is installed on the host. Look for the installation summary and bulletin ID. | ||
Step 4 | Do one of the following: |
This example shows how to install VEM software remotely on a VMware 5.0 host using the CLI.
vi-admin@localhost:~> esxcli --server=192.0.2.2 software vib install--depot=/vmfs/volumes/newnfs/MN-patch01/ CY-FCS/VEM500-201401164100-BG-release.zip Enter username: root Enter password: Installation Result Message: Operation finished successfully. Reboot Required: false VIBs Installed: Cisco_bootbank_cisco-vem-v164-esx_4.2.1.2.2.2.0-3.0.1 VIBs Removed: VIBs Skipped: vi-admin@localhost:~> esxcli --server=192.0.2.1 software vib list Enter username:
The following list outlines the VEM installation process on a stateless ESXi host.
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: |
Step 3 | See the procedure for Configuring Layer 2 Connectivity. |
![]() 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.
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:
| ||
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
| ||
Step 6 | change to Load the Cisco Nexus 1000V offline bundle by entering the following command: Add-EsxSoftwareDepot VEM_bundle
| ||
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: | ||
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
| ||
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\cisco-vem-v1 64-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 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.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}
Step 1 | Display the VMware version and build number by entering the following commands: | ||
Step 2 | Log in to the ESXi stateless host. | ||
Step 3 | Copy the offline bundle to the host by entering the the following command:
| ||
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 |
~ # 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-201401164100-BG-release.zip Installation Result Message: WARNING: Only live system was updated, the change is not persistent. Reboot Required: false VIBs Installed: Cisco_bootbank_cisco-vem-v164-esx_4.2.1.2.2.2.0-3.0.1 VIBs Removed: VIBs Skipped: ~ # esxcli software vib list | grep cisco cisco-vem-v164-esx 4.2.1.2.2.2.0-3.0.1 Cisco PartnerSupported 2014-01-24 ~ # vem status -v Package vssnet-esxmn-release Version 4.2.1.2.2.2.0-3.0.1 Build 1 Date Sat Jan 24 04:56:14 PDT 2014 VEM modules are loaded Switch Name Num Ports Used Ports Configured Ports MTU Uplinks vSwitch0 128 4 128 1500 vmnic4 DVS Name Num Ports Used Ports Configured Ports MTU Uplinks p-1 256 19 256 1500 vmnic7,vmnic6,vmnic3,vmnic2,vmnic1,vmnic0 VEM Agent (vemdpa) is running ~ # vemcmd show version vemcmd show version VEM Version: 4.2.1.2.2.2.0-3.0.1 VSM Version: 4.2(1)SV2(2.2) [build 4.2(1)SV2(2.2)] System Version: VMware ESXi 5.0.0 Releasebuild-843203 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 332 Virtual Ethernet Module NA ok 6 248 Virtual Ethernet Module NA ok Mod Sw Hw --- ------------------ ------------------------------------------------ 4.2(1) SV2(2.2) 0.0 4.2(1) SV2(2.2) 0.0 3 4.2(1)SV2(2.2) VMware ESXi 5.0.0 Releasebuild-843203 (3.0) 6 4.2(1)SV2(2.2) VMware ESXi 5.1.0 Releasebuild-843203 (3.0) Mod Server-IP Server-UUID Server-Name --- --------------- ------------------------------------ -------------------- 1 10.105.232.25 NA NA 2 10.105.232.25 NA NA 3 10.105.232.72 e6c1a563-bc9e-11e0-bd1d-30e4dbc2baba 10.105.232.72 6 10.105.232.70 ecebdf42-bc0e-11e0-bd1d-30e4dbc2b892 10.105.232.70
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. ![]() |
Step 3 | Add the host to the DVS by using vCenter Server. |
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. |
Copy the ISO file to the bootflash:repository/ of the Cisco Nexus Cloud Services Platform.
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-1000v.4.2.1.SV2.2.2.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.4.2.1.SV2.2.2.iso] Enter domain id[1-4095]: 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.
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)# |
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. |