Cisco Nexus 1000V Installation and Upgrade Guide, Release 4.2(1)SV2(1.1)
Installing the Cisco Nexus 1000V
Downloads: This chapterpdf (PDF - 7.25MB) The complete bookPDF (PDF - 11.32MB) | The complete bookePub (ePub - 6.15MB) | Feedback

Installing the Cisco Nexus 1000V

Contents

Installing the Cisco Nexus 1000V

This chapter contains the following sections:

Information About Installing the Cisco Nexus 1000V

VSM Software

You can obtain the Cisco Nexus 1000V software from the Cisco Nexus 1000V Series Switches web page:

Cisco Nexus 1000V Download Software page

The file name is Nexus1000v.4.2.1.SV2.1.1.zip.

VEM Software

You can obtain the Virtual Ethernet Module (VEM) software from the sources listed in the following table:

Table 1 VEM Software Sources

Source

Description

VSM

After the VSM has been installed as a Virtual Machine (VM), copy the file that contains the VEM software from the Virtual Supervisor Module (VSM) home page located at the following URL:

http://VSM_IP_Address/

Cisco

Download the VEM software from the Cisco Nexus 1000V Download Software page.

Information About the Cisco Nexus 1000V Installer App

The Cisco Nexus 1000V Installer App is the graphical user interface (GUI) for installing 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 does the following:

  • Creates port profiles for the control, management, and packet port groups.
  • Creates uplink port profiles.
  • Creates port profiles for VMware kernel NICs.
  • Specifies a VLAN to be used for system login and configuration, and control and packet traffic.

    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.


  • Enables Telnet and Secure Shell (SSH) and configures an SSH connection.
  • Creates a Cisco Nexus 1000V plug-in and registers it on the vCenter Server.
  • Migrates each VMware port group or kernel NIC to the correct port profile.
  • Migrates each physical network interface card (PNIC) from the VMware vSwitch to the correct uplink on the DVS.
  • Adds the host to the DVS.
  • The Cisco Nexus 1000V Installer App provides a quick method for a user to deploy VSMs and VEMs with minimal or custom inputs on a single screen and expect a fully functional Cisco Nexus 1000V setup. See the following link for best practice recommendations in the deployment of Cisco Nexus 1000V: http:/​/​www.cisco.com/​en/​US/​prod/​collateral/​switches/​ps9441/​ps9902/​guide_​c07-556626.html.

Prerequisites for Installing the Cisco Nexus 1000V

Cisco Nexus 1000V Installer App Prerequisites


Note


The Installation Management Center 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 host must have one or more physical NICs on each VMware vSwitch in use.
  • The VMware vSwitch must not have any active VMs. To prevent a disruption in connectivity during migration, any VMs that share a VMware vSwitch with port groups used by the VSM must be powered off.
  • You must also configure the VSM connection to the vCenter server datacenter where the host resides.
  • Host should have only one VMware vSwitch.
  • Make sure no VEMs were previously installed on the host where the VSM resides.
  • You must have administrative credentials for the vCenter Server.
  • The java.exe file must be located within the search path defined in your system.

Host Prerequisites

The ESX or ESXi hosts to be used for the Cisco Nexus 1000V have the following prerequisites:

  • You have already installed and prepared the vCenter Server for host management using the instructions from VMware.
  • You should have the VMware vSphere Client installed.
  • You have already installed the VMware Enterprise Plus license on the hosts.
  • All VEM hosts must be running ESX/ESXi 4.1 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 inter-switch trunk links carry all relevant VLANs, including control and packet VLANs. The uplink should be a trunk port that carries all VLANs configured on the host.
  • The control and management VLANs must already be configured 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.


The following table lists the minimum requirements for hosting a VSM.

Table 2 Minimum Requirements for a VM Hosting a VSM

VSM VM Component

Minimum Requirement

Platform

64-bit

Type

Other 64-bit Linux (recommended)

Processor

1

RAM (configured and reserved)

2 GB1

NIC

3

SCSI Hard Disk

3 GB with LSI Logic Parallel adapter

CPU speed

1500 MHz2

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 RAM and set the memory size.

Upstream Switch Prerequisites

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

  • If you are using a set of switches, make sure that the inter-switch 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 switch upstream from the Cisco Nexus 1000V on the ports connected to the VEM.
    • On upstream switches, the following configuration is mandatory: On your Catalyst series switches with Cisco IOS software, enter the following command: (config-if) spanning-tree portfast trunk or (config-if) spanning-tree portfast edge trunk On your Cisco Nexus 5000 series switches with Cisco NX-OS software, enter the following command: (config-if) spanning-tree port type edge trunk
    • On upstream switches we highly recommend that you enable the following globally: Global BPDU Filtering Global BPDU Guard
    • On upstream switches where you cannot globally enable BPDU Filtering and BPDU Guard, we highly recommend that you enter the following commands: (config-if) spanning-tree bpdu filter (config-if) spanning-tree bpdu guard
    For more information about spanning tree and its supporting commands, see the documentation for your upstream switch.
  • Run 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
    

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.
  • You have already identified the HA role for this VSM from the list in the following table.
Table 3 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 Layer 3 Topology.

VEM Prerequisites

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


Note


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


  • 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 cannot install the hosts in the cluster.
  • If the hosts are in ESXi stateless mode, then enable the Pxe Booted ESXi host settings available 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 ESX/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 the vCenter Server.

Guidelines and Limitations

Guidelines and Limitations of the Cisco Nexus 1000V Installer App

Configuring the software using the Cisco Nexus 1000V Installer App has the following guidelines and limitations:

  • For a complete list of port profile guidelines and limitations, see the Cisco Nexus 1000V Port Profile Configuration Guide.

    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.


  • If you are installing a Cisco Nexus 1000V in an environment where the upstream switch does not support static port channels, such as the Cisco Unified Computing System (UCS), you must use the channel-group auto mode on the mac-pinning command instead of the channel-group auto mode command.
  • We recommend that you install redundant VSMs on the Cisco Nexus 1000V. For information about high availability and redundancy, see the Cisco Nexus 1000V High Availability and Redundancy Configuration Guide.
  • For a user using the VC Connection installer, once the SVS connection is completed, the user must check the VSM using the show svs connection command to view an accurate status.
  • Layer 3 mode of deployment is supported by the Cisco Nexus 1000V Installer App with ESXi host only.
  • VEM installation and migration are supported for a maximum of four vmknics in a single subnet per host to deploy 64 VEMs. No more than four vmknics can be present on a single host during VEM installations.
  • The Cisco Nexus 1000V Installer App can support 14 different subnets during module additions when reusing port profiles.
  • The Cisco Nexus 1000V Installer App will always deploy with VSM HA pairs.
  • If the Installer App fails, check the vCenter Server event status. If an event shows failure due to a timeout, then it could be because of a vCenter Server overload. Please consult the VMware website to address a vCenter Server overload event.

Guidelines and Limitations for Installing the Cisco Nexus 1000V

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

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

Installing a VSM HA Pair with L3 Mode Behind a VEM Using the Cisco Nexus 1000V Installer App

Installing VSM Software Using the Cisco Nexus 1000V Installer App

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.

Installing Cisco Nexus 1000V in Standard Mode

Before You Begin
  • You have the following information:

    Note


    The VSM IP address must be in the same management VLAN as the host.


    • Management VLAN ID
    • Domain ID
    • Management IP address
    • Subnet mask
    • Gateway IP address
  • You have the JDK version 1.6 or later installed on the host running the Cisco Nexus 1000V Installer App.
  • The VSM will be deployed with the following credentials:
    • username: admin
    • password: admin
  • If the user selects the migration to DVS option as yes, then the migration of hosts that have VSMs will migrate all the interfaces under the vSwitch that have the ESXi management interface (say vmk0 ).
Procedure
    Step 1   Double-click on the installation file 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
    Figure 1. Command Line Interface



    Step 2   Click the Cisco Nexus 1000V Complete Installation radio button.
    Figure 2. Standard Cisco Nexus 1000V Complete Installation Screen



    Step 3   Click the Standard radio button.
    Figure 3. Standard Option Screen



    Step 4   After reading the Prerequisites, click Next.
    Step 5   In the vCenter Server Credentials screen, do the following:
    1. Enter the following vCenter credentials:
      • IP Address
      • Port (https only)
        Note   

        This field is prepopulated but can be modified.

      • User ID
      • Password
    2. Click Next.
    Figure 4. vCenter Server Credentials Screen



    Step 6   In the Standard Configuration Data screen, click the Browse button for the Host 1 IP address.
    Figure 5. Standard Configuration Data Screen



    Step 7   In the vCenter Inventory screen, do the following:
    1. Choose the host for the primary VSM.
    2. Click Select Host.

    The IP Address / Name and Data Store for Host 1 populate.

    Step 8   In the Standard Configuration Data screen, click the Browse button for the Host 2 IP address.
    Figure 6. Standard Configuration Data Screen



    Step 9   In the vCenter Inventory screen, do the following:
    1. Choose the host for the secondary VSM.
    2. Click Select Host.
    Step 10   In the Standard Configuration Data screen, enter the Virtual Machine Name.
    Figure 7. Standard Configuration Data Screen



    Step 11   In the Standard Configuration Data screen, do the following:
    1. Click the Browse button for the OVA Image Location field.
    2. Browse to the OVA file.
    3. Choose the OVA file.
    4. Click Open.
    Figure 8. Standard Configuration Data Screen



    Step 12   In the Standard Configuration Data screen, do the following:
    1. Enter the remaining configuration data:
      • VSM IP Address
      • Subnet Mask
      • Gateway IP Address
      • Domain ID
      • Management VLAN
    2. Click Yes or No to migrate the hosts to the DVS.
    3. Optional: Click Save Configuration.
      Note   

      The save configuration option allows you to create an XML configuration file for later use. This allows you to import and pre-populate common values in the template for later use.

    4. Click Next.
    Figure 9. Standard Configuration Data Screen



    Step 13   After reviewing the values in the Standard Configuration Review screen, choose one of the following:
    • Click Next to continue.
    • Click Prev to return to the previous screens and modify the entries.
    Figure 10. Standard Configuration Review Screen



    The Standard Installation Progress screen opens.

    Figure 11. Standard Installation Progress Screen



    When the installation process completes, the Confirmation screen is displayed. A typical installation of the VSM takes about 6-8 minutes.

    Step 14   In the Confirmation screen, do one of the following:
    • Click Yes if you want to add more modules and continue to the next step.
      Figure 12. Confirmation Screen



    • Click No if you do not want to add more modules and continue with Step 18.
      Figure 13. Not Adding Modules Screen



    Step 15   In the Adding Modules screen, do the following:
    1. Do one of the following:
      • Click Install VIB to install VIBs on this host.
      • Click Install VIB and add module to Nexus 1000V to install VIBs on this host and move them to the Nexus 1000V.
    2. Enter a VLAN ID in the Management VLAN field.
    Figure 14. Adding Modules Screen



    Step 16   In the Hosts Selection screen, do the following:
    1. Choose the hosts you want to add.
    2. Click Next.
    Figure 15. Hosts Selection Screen



    Step 17   In the Host Review screen, do the following:
    • Review the entries.
    • Click Finish.
    Figure 16. Host Review Screen

    Step 18   Click Close.
    Figure 17. Summary Screen




    Installing the Cisco Nexus 1000V in Custom Mode

    Before You Begin
    • You have the following information:
      • Control VLAN ID
      • Packet VLAN ID
      • Management VLAN ID
      • Domain ID
      • Management IP address
      • Subnet mask
      • Gateway IP address
      • SVS datacenter name
      • Control, packet, and management port groups
      • Management VLAN ID of ESXi hosts
    • You have the JDK version 1.6 or later installed on the host running the Cisco Nexus 1000V Installer App.
    Procedure
      Step 1   Double-click on the 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
      Figure 18. Command Line Interface



      Step 2   Click the Cisco Nexus 1000V Complete Installation radio button.
      Figure 19. Cisco Nexus 1000V Complete Installation Screen



      Step 3   Click the Custom radio button.
      Figure 20. Custom Installation



      Step 4   After reading the Prerequisites, click Next.
      Step 5   In the vCenter Server Credentials screen, do the following:
      1. Enter the following vCenter credentials:
        • IP Address
        • Port (https only)
          Note   

          This field is prepopulated but can be modified.

        • User ID
        • Password
      2. Click Next.
      Figure 21. vCenter Server Credentials Screen



      Step 6   In the Custom Configuration Data screen, click the Browse button for the Host 1 IP Address / Name field.
      Figure 22. Custom Configuration Data Screen



      Step 7   In the Host 1 Selection vCenter Inventory screen, do the following:
      1. Choose the host for the primary VSM.
      2. Click Select Host.

      The Host 1 IP Address / Name and Data Store fields are populated.

      Step 8   In the Host 1 vSwitch Custom Configuration Data screen, click the Browse button for the Host 1 vSwitch field.
      Figure 23. Host 1 vSwitch Custom Configuration Data Screen



      Step 9   In the Host 1 vSwitch Selection screen, do the following:
      • Choose a vSwitch.
      • Click Select.

      The Host 1 vSwitch field is populated.

      Step 10   In the Host 2 IP Address Custom Configuration Data screen, click the Browse button for the Host 2 IP Address / Name field.
      Figure 24. Host 2 IP Address Custom Configuration Data Screen



      Step 11   In the Host 2 Selection vCenter Inventory Screen screen, do the following:
      • Choose the host for the secondary VSM.
      • Click Select Host.
      Step 12   In the Host 2 vSwitch Custom Configuration Data screen, click the Browse button for the Host 2 vSwitch field.
      Figure 25. Host 2 vSwitch Custom Configuration Data Screen



      Step 13   In the Host 2 vSwitch Make a Selection screen, do the following:
      • Choose a vSwitch.
      • Click Select.
      Step 14   In the Switch Name Custom Configuration screen, do the following:
      1. Enter the Switch Name.
      2. Enter the Admin User Name.
      3. Enter the Admin Password.
      4. Enter the Confirm the Admin Password.
      5. Enter the Virtual Machine Name.
      Figure 26. Switch Name Custom Configuration Screen



      Step 15   In the OVA Image Custom Configuration Data screen, click the Browse button for the OVA Image Location field.
      Figure 27. OVA Image Custom Configuration Data Screen



      Step 16   In the OVA File Location screen, do the following:
      1. Browse to the OVA file.
      2. Choose the OVA file.
      3. Click Open.
      Figure 28. OVA File Location Screen



      Step 17   In the VSM IP Address Custom Configuration Data screen, do the following:
      1. Click the Layer L2 or Layer L3 radio button.

        The Layer 3 mode is selected by default.

      2. Enter the remaining configuration data.
        • VSM IP Address
        • Subnet Mask
        • Gateway IP Address
        • Domain ID
      3. Check the Enable Telnet check box if you want to enable Telnet.

        By default, only SSH is enabled.

      Figure 29. VSM IP Address Custom Configuration Data Screen



      Step 18   Click the Browse button for the Data Center Name.
      Figure 30. Data Center Name Screen



      Step 19   In the Choose a Data Center screen, do the following:
      1. Choose a data center.
      2. Click Select.
      Step 20   Click the Browse button for the Control Port Group Port Group Name field.
      Step 21   In the Choose Control Port Group - Port Group VLAN ID screen, do the following:
      • Choose a VLAN ID.
      • Click Select.
      Figure 31. Choose Control Port Group - Port Group VLAN ID Screen



      Step 22   In the Management Port Group - Port Group Name screen, do the following to create a new Management Port Group:
      1. Choose the Create New radio button
      2. Enter the Port Group Name.
      3. Enter the VLAN ID.
      Figure 32. Management Port Group - Port Group Name Screen



      Step 23   In the Management VLAN screen, do the following:
      Note   

      The Installer App assumes the use of dot1q trunking and requires you to specify the management VLAN.

      1. Enter a VLAN ID in the Management VLAN ID field.
      2. Click Yes or No to migrate the hosts to the DVS.
      3. Click the Save Configuration button if you want to save the settings to a configuration file.
      4. Click Next.
      Figure 33. Management VLAN Screen



      Step 24   In the Custom Configuration Review screen, do the following:
      • Validate the input.
      • Click Next.
      Figure 34. Custom Configuration Review Screen



      The Custom Configuration Review Installation Progress screen is displayed.

      Figure 35. Custom Configuration Review Installation Progress Screen



      When the installation completes, the Confirmation screen opens.

      Step 25   In the Custom Confirmation screen, do one of the following:
      • Click Yes if you want to add more modules and continue to the next step.
        Figure 36. Custom Confirmation Screen



      • Click No if you do not want to add more modules and continue with Step 29 .
        Figure 37. Not Adding Modules Screen



      Step 26   In the Confirmation screen, do the following:
      1. Do one of the following:
        • Click Install VIB to install VIBs on this host.
        • Click Install VIB and add module to Nexus 1000V to install VIBS on this host and move them to the Cisco Nexus 1000V.
      2. Enter a VLAN ID in the Management VLAN field.
        Note   

        In the Management VLAN field, add the same VLAN that is assigned to your vmkernel interface.

      Figure 38. Confirmation Screen



      Step 27   In the Hosts Selection screen, do the following:
      1. Choose the hosts you want to add.
      2. Click Next.
      Figure 39. Hosts Selection Screen



      Step 28   In the Host Review screen, do the following:
      • Review the entries.
      • Click Finish.
      Figure 40. Host Review Screen



      Step 29   In the Custom Summary screen, click Close.
      Figure 41. Custom Summary Screen




      Information About Layer 2 Connectivity


      Note


      Layer 3 connectivity is the preferred method for communications between the VSM and the VEMs.


      The following 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 for Layer 2 connectivity.

      Figure 42. Cisco Nexus 1000V Installation Diagram for Layer 2



      Layer 2 on the Same Host

      The following figure shows a VSM and VEM running on the same host in Layer 2 mode.

      Figure 43. VSM and VEM on the Same Host in Layer 2 Mode



      Configuring Layer 2 Connectivity


      Note


      Layer 3 connectivity is the preferred method.


      Procedure
        Step 1   To configure a different VMware vSwitch port group for each VSM network adapter, in the Configure Networking screen click L2: Configure port groups for L2.
        Step 2   In the Configure Networking screen, do the following:
        • From the Port Group drop-down lists, choose your port groups.
        • (Optional) In the VLAN ID field, enter the VLAN ID.
          Note   

          Only needed if you choose to create a new port group.

        • Click Next.
        Figure 44. Configure Networking Screen



        Step 3   Return to Step 17 in the Layer 2 configuration procedure.

        Installing the VEM Software Using the Cisco Nexus 1000V Installer App

        • When the Cisco Nexus 1000V Installer App installs VEMs, it migrates all VEM kernels and their corresponding vmnics across vSwitches to the Nexus 1000V VEMs
        • If a particular VEM is capable of hosting VSMs, the network administrator must manually allow control VLAN in the uplink port profile of VEMs in Layer 3 deployment mode for VSM HA communication.
        Before You Begin
        • You have the following information:
          • vCenter IP address
          • vCenter User ID
          • vCenter Password
          • VSM IP Address
          • VSM Password

        Note


        The hosts that will be installed as VEMs should not have any Cisco Nexus 1000V VIB files. Uninstall any Cisco Nexus 1000V VIBs before starting the Cisco Nexus 1000V Installer App.


        Procedure
          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 Installer App. java -jar Nexus1000V-install_CNX.jar
          Step 2   Click the Virtual Ethernet Module Installation radio button.
          Figure 45. Cisco Nexus 1000V Installer App Screen



          Step 3   After reading the Prerequisites, click Next.
          Step 4   In the VEM Enter vCenter Credentials screen, do the following:
          1. Enter the following vCenter Credentials:
            • IP address
            • Port (https only)
              Note   

              This field is prepopulated but can be modified.

            • User ID (for a vCenter user with administrator-level privileges)
            • Password (for a vCenter user with administrator-level privileges)
          2. Click Next.
          Figure 46. VEM Enter vCenter Credentials Screen



          Step 5   In the VEM Enter VSM IP & Credentials screen, do the following:
          1. Enter the following credentials:
            • VSM IP address
            • VSM Password
          2. Click Next.
          Figure 47. VEM Enter VSM IP & Credentials Screen



          Step 6   In the Confirmation screen, do one of the following:
          • Click Yes if you want to add more modules and continue to the next step.
            Figure 48. Confirmation Screen



          • Click No if you do not want to add more modules and continue with Step 10.
            Figure 49. Not Adding Modules Screen



          Step 7   In the Adding Modules screen, do the following:
          1. Do one of the following:
            • Click Install VIB to install VIBs on this host.
            • Click Install VIB and add module to Nexus 1000V to install VIBs on this host and move them to the Nexus 1000V.
          2. Enter a VLAN ID in the Management VLAN field.
          Figure 50. Adding Modules Screen



          Step 8   In the VEM Hosts Selection screen, do the following:
          1. Choose the hosts you want to add.
          2. Click Next.
          Figure 51. VEM Hosts Selection Screen



          Step 9   In the VEM Host Review screen, do the following:
          • Review the entries.
          • Click Finish.
          Figure 52. VEM Host Review Screen



          Step 10   In the VEM Summary screen, click Close.
          Figure 53. VEM Summary Screen



          Note   
          • If the VEM software fails to install on a host, the following message appears: "Install status: Failure".
          • Once the Cisco Nexus 1000V Installer App completes the VEM installation, verify the current status of modules from the VSM using the show module command.

          For more information about troubleshooting VSMs and VEMs, see the Cisco Nexus 1000V Troubleshooting Guide.


          Adding VEM Hosts to the 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.
            Figure 54. vSphere Client WIndow



            Step 2   In the vSphere Client Hosts window, choose the DVS and click the Hosts tab.
            Figure 55. 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.
            Figure 56. 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, click Next.
            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.

            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.

            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.
              Figure 57. vSphere Client Window



              Step 2   In the Configuration pane, choose Virtual Machine Startup/Shutdown.
              Figure 58. Configuration Pane



              Step 3   In the Virtual Machine Startup and Shutdown pane, click the Properties link.
              Figure 59. Virtual Machine Startup and Shutdown Pane



              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 a number of seconds in the Default Startup Delay seconds field.
                • Enter a number of seconds in the Default Shutdown Delay seconds field.
              3. In the Startup Order pane, do the following:
                • Choose the virtual machine.
                • Click the Move Up button until the virtual machine is under Automatic Startup.
              4. Click OK.
              5. Repeat Step 2 through Step 4 for the other virtual machine.
              Figure 60. System Settings Dialog Box




              Startup and shutdown settings are 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 VEM Software Locally on a VMware 4.1 Host by Using the CLI

              Before You Begin
              • 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 VEM software installation file to the /tmp directory.
              • You know the name of the VEM software file to be installed.
              Procedure
                Step 1   From the ESX host /tmp directory, begin the VEM update procedure.
                • If the offline bundle is used, enter the following command: esxupdate --bundle VMware_offline_update_bundle update


                Example:
                /tmp # esxupdate --bundle VEM410-201201401.zip update 
                Unpacking cross_cisco-vem-v14.. ######################################## [100%] 
                
                Installing packages :cross_ci.. ######################################## [100%] 
                
                Running [/usr/sbin/vmkmod-install.sh]... 
                ok.
                • If the VIB file is used, enter the following command: esxupdate -b VIB_file update


                Example:
                /tmp # esxupdate -b cross_cisco-vem-v140-4.2.1.2.1.1.0-2.0.1.vib update 
                
                Unpacking cross_cisco-vem-v140-esx.. ################################################# [100%] 
                
                Installing packages :cross_cisco-v.. ################################################# [100%] 
                
                Running [/usr/sbin/vmkmod-install.sh]... 
                ok.

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

                Step 2   Verify that the VEM software is installed on the host.
                /tmp # esxupdate --vib-view query | grep cisco 
                cross_cisco-vem-v140-4.2.1.2.1.1.0-2.0.1.vib                                installed     2012-02-02T12:29:18.728890+00:00 
                Step 3   Verify that the installation was successful by checking for the “VEM Agent (vemdpa) is running” statement in the output of the vem status command.
                /tmp # vem status -v 
                Package vssnet-esx5.5.0-00000-release
                Version 4.2.1.2.1.1.0-2.0.2
                Build 2
                Date Tue Jan 31 05:01:37 PST 2012
                 
                Number of PassThru NICs are 0
                VEM modules are loaded
                 
                Switch Name      Num Ports   Used Ports  Configured Ports  MTU     Uplinks   
                vSwitch0         128         3           128               1500    vmnic0    
                 
                Number of PassThru NICs are 0
                VEM Agent (vemdpa) is running 
                Step 4   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.

                Installing the VEM Software Remotely on a VMware 4.1 Host by Using the CLI

                Before You Begin
                • If you are using the vSphere command-line interface (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 machine where the vCLI is installed.

                Note


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


                Procedure
                  Step 1   Go to the directory where the new VEM software was copied.
                  [root@serialport -]# cd tmp 
                  [root@serialport tmp]# 
                  Step 2   Install the VEM software. [root@serialport tmp]# vihostupdate -i -b ./Cisco_updated_VEM_offline_bundle --server vsphere_host

                  Example:
                  [root@serialport tmp]# vihostupdate -i -b ./VEM410-201201401.zip --server 192.0.2.0 
                  Enter username: root
                  Enter password:
                  Please wait patch installation is in progress ...
                  Host updated successfully.
                  Step 3   Verify that the VEM software is installed on the host. vihostupdate.pl -q --server host_ip_address

                  Example:
                  [root@serialport tmp]# vihostupdate.pl -q --server 192.0.2.1 
                  Enter username: root 
                  Enter password: 

                  Look for the following:

                  ---------Bulletin ID--------- -----Installed----- ----------------Summary-------
                  ----------
                  VEM410-201201401-BG           2012-02-02T00:54:14 Cisco Nexus 1000V 4.2(1)SV2(1.1)
                  Step 4   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.

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

                  Procedure
                    Step 1   Copy the VEM software to the /tmp directory.
                    Step 2   Begin the VEM installation procedure. esxcli software vib install -v /tmp/VIB_FILE

                    Example:
                    ~ # esxcli software vib install -v /tmp/cross_cisco-vem-v140-4.2.1.2.1.1.0-3.0.1.vib 
                    Installation Result
                       Message: Operation finished successfully.
                       Reboot Required: false
                       VIBs Installed: Cisco_bootbank_cisco-vem-v140-esx_4.2.1.2.1.1.0-3.0.1
                       VIBs Removed: 
                       VIBs Skipped:
                    Step 3   Verify that the VEM software is installed on the host.
                    ~ # esxcli software vib list | grep cisco 
                    cisco-vem-v140-esx 4.2.1.2.1.1.0-3.0.1 Cisco PartnerSupported
                    2012-02-02
                    Step 4   Verify that the installation was successful by checking for the “VEM Agent (vemdpa) is running” statement in the output of the vem status command.

                    Example:
                    ~ # vem status -v 
                    Package vssnet-esxmn-ga-release 
                    Version 4.2.1.2.1.1.0-3.0.1 
                    Build 1 
                    Date Mon Jan 30 18:38:49 PST 2012 
                    
                    Number of PassThru NICs are 0 
                    VEM modules are loaded 
                    
                    Switch Name    Num Ports   Used Ports  Configured Ports MTU   Uplinks 
                    vSwitch0       128         3           128              1500  vmnic0 
                    Number of PassThru NICs are 0 
                    VEM Agent (vemdpa) is running 
                    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.

                    Installing VEM Software Remotely on a VMware 5.0 Host by Using the CLI

                    Procedure
                      Step 1   Copy the VEM software to the NFS storage which is mounted on the ESXi 5.0 host.
                      Step 2   Enter the following command from the remote machine where the vCLI is installed. esxcli --server=[server ip] software vib install --depot=Path_to_the_NFS_storage_mounted_ _on_ESXi_5.0 host

                      Example:
                      vi-admin@localhost:~> esxcli --server=192.0.2.2 software vib install --depot=/vmfs/volumes/newnfs/MN-patch01/CN-FCS/VEM500-201201140102-BG-release.zip
                      Enter username: root
                      Enter password:
                      Installation Result
                         Message: Operation finished successfully.
                         Reboot Required: false
                         VIBs Installed: Cisco_bootbank_cisco-vem-v140-esx_4.2.1.2.1.1.0-3.0.1
                         VIBs Removed:
                         VIBs Skipped:

                      where 192.0.2.2 is the target ESXi 5.0 host IP address and newnfs is the NFS storage mounted on the ESXi 5.0 host.

                      Note   

                      You should refer to the official VMware documentation for further information on the esxcli command.

                      Step 3   Verify that the VEM software is installed on the host. esxcli --server=host_ip_address software vib list

                      Example:
                      vi-admin@localhost:~> esxcli --server=192.0.2.1 software vib list 
                      Enter username: root
                      Enter password:
                      
                      
                      

                      Look for the following:

                      Name                  Version                             Vendor  Acceptance Lev
                      el  Install Date
                      --------------------  ----------------------------------  ------  --------------
                      --  ------------
                      cisco-vem-v140-esx    4.2.1.2.1.1.0-3.0.1                 Cisco   PartnerSupport
                      ed  2012-04-06
                      Step 4   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.

                      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:
                        Step 3   See the procedure for Configuring Layer 2 Connectivity.

                        Stateless ESXi Host


                        Note


                        For Stateless ESXi, the VLAN used for 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 and the image profile includes base VIBs from VMware and additional VIBs from partners.

                        On a stateless host, VEM software can be installed or upgraded using either the VUM or CLI.

                        In addition, you should bundle the new or modified VEM module in the image profile from which the stateless host boots. If it is not bundled in the image profile, the VEM module 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 module 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.

                        Note


                        In the following procedure, the image profile bundle is available as C:\ESXi-5.0.0-depot.zip and the VEM bundle is available as C:\VEM500-20110822140-BG.zip.


                        Procedure
                          Step 1   Start the vSphere PowerCLI application.
                          Step 2   Connect to the vCenter Server.
                          [vSphere PowerCLI] > Connect-VIServer 192.0.2.1 –User Administrator –Password XXXXX 
                          Step 3   Load the image profile offline bundle.
                          Note   

                          Each image profile bundle can include multiple image profiles.

                          [vSphere PowerCLI] > Add-ESXSoftwareDepot c:\vmware-ESXi-5.0.0-depot.zip 
                          Step 4   List the image profiles.
                          [vSphere PowerCLI] > Get-EsxImageProfile 
                          
                          Name                             Vendor          Last Modified
                          ----                             ------          -------------
                          ESXi-5.0.0-standard              VMware, Inc.    2/25/2011 9:42:21 PM
                          ESXi-5.0.0-no-tools              VMware, Inc.    2/25/2011 9:42:21 PM
                          Step 5   Choose the image profile into which the VEM is to be bundled from the output of the Get-EsxImageProfile command.
                          Note   

                          The image profiles will be in read-only format. You need to clone the image profile before adding the VEM into it.

                          [vSphere PowerCLI] > New-EsxImageProfile -CloneProfile ESXi-5.0.0-standard -Name n1kv-Image 
                          Note   

                          The n1kv-Image is the cloned image profile of the ESXi-5.0.0-standard.

                          Step 6   Load the Cisco Nexus 1000V VEM offline bundle.
                          Note   

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

                          [vSphere PowerCLI] > Add-EsxSoftwareDepot C:\VEM500-20110822140-BG.zip 
                          Step 7   Confirm that the n1kv-vib package is loaded.
                          [vSphere PowerCLI] > Get-EsxSoftwarePackage -Name cisco* 
                          
                          Name                           Version              Vendor          Release
                          ----                           -------              ------          -----------
                          cisco-vem-v131-esx             4.2.1.1.3.24.0-3.0.8 Cisco           8/22/2011.
                          Step 8   Bundle the n1kv-package into the cloned image profile.
                          [vSphere PowerCLI] > Add-EsxSoftwarePackage -ImageProfile n1kv-Image -SoftwarePackage cisco-vem-v131-esx 
                          Step 9   List all the VIBs in the cloned image profile.
                          [vSphere PowerCLI]> $img = Get-EsxImageProfile n1kv-Image 
                          [vSphere PowerCLI]> $img.vibList 
                          
                          Name                     Version                        Vendor     Release Date
                          ----                     -------                        ------     ------------
                          scsi-bnx2i               1.9.1d.v50.1-3vmw.500.0.0.4... VMware     6/22/2011...
                          net-s2io                 2.1.4.13427-3vmw.500.0.0.43... VMware     6/22/2011...
                          net-nx-nic               4.0.557-3vmw.500.0.0.434219    VMware     6/22/2011...
                          scsi-aic79xx             3.1-5vmw.500.0.0.434219        VMware     6/22/2011...
                          sata-ata-piix            2.12-4vmw.500.0.0.434219       VMware     6/22/2011...
                          net-e1000e               1.1.2-3vmw.500.0.0.434219      VMware     6/22/2011...
                          net-forcedeth            0.61-2vmw.500.0.0.434219       VMware     6/22/2011...
                          tools-light              5.0.0-0.0.434219               VMware     6/22/2011...
                          ipmi-ipmi-msghandler     39.1-4vmw.500.0.0.434219       VMware     6/22/2011...
                          scsi-aacraid             1.1.5.1-9vmw.500.0.0.434219    VMware     6/22/2011...
                          net-be2net               4.0.88.0-1vmw.500.0.0.434219   VMware     6/22/2011...
                          sata-ahci                3.0-6vmw.500.0.0.434219        VMware     6/22/2011...
                          ima-qla4xxx              2.01.07-1vmw.500.0.0.434219    VMware     6/22/2011...
                          ata-pata-sil680          0.4.8-3vmw.500.0.0.434219      VMware     6/22/2011...
                          scsi-ips                 7.12.05-4vmw.500.0.0.434219    VMware     6/22/2011...
                          scsi-megaraid-sas        4.32-1vmw.500.0.0.434219       VMware     6/22/2011...
                          scsi-mpt2sas             06.00.00.00-5vmw.500.0.0.43... VMware     6/22/2011...
                          net-cnic                 1.10.2j.v50.7-2vmw.500.0.0.... VMware     6/22/2011...
                          ipmi-ipmi-si-drv         39.1-4vmw.500.0.0.434219       VMware     6/22/2011...
                          esx-base                 5.0.0-0.0.434219               VMware     6/22/2011...
                          ata-pata-serverworks     0.4.3-3vmw.500.0.0.434219      VMware     6/22/2011...
                          scsi-mptspi              4.23.01.00-5vmw.500.0.0.434219 VMware     6/22/2011...
                          net-bnx2x                1.61.15.v50.1-1vmw.500.0.0.... VMware     6/22/2011...
                          ata-pata-hpt3x2n         0.3.4-3vmw.500.0.0.434219      VMware     6/22/2011...
                          sata-sata-sil            2.3-3vmw.500.0.0.434219        VMware     6/22/2011...
                          scsi-hpsa                5.0.0-17vmw.500.0.0.434219     VMware     6/22/2011...
                          block-cciss              3.6.14-10vmw.500.0.0.434219    VMware     6/22/2011...
                          net-tg3                  3.110h.v50.4-4vmw.500.0.0.4... VMware     6/22/2011...
                          net-igb                  2.1.11.1-3vmw.500.0.0.434219   VMware     6/22/2011...
                          ata-pata-amd             0.3.10-3vmw.500.0.0.434219     VMware     6/22/2011...
                          ata-pata-via             0.3.3-2vmw.500.0.0.434219      VMware     6/22/2011...
                          net-e1000                8.0.3.1-2vmw.500.0.0.434219    VMware     6/22/2011...
                          scsi-adp94xx             1.0.8.12-6vmw.500.0.0.434219   VMware     6/22/2011...
                          scsi-lpfc820             8.2.2.1-18vmw.500.0.0.434219   VMware     6/22/2011...
                          scsi-mptsas              4.23.01.00-5vmw.500.0.0.434219 VMware     6/22/2011...
                          ata-pata-cmd64x          0.2.5-3vmw.500.0.0.434219      VMware     6/22/2011...
                          sata-sata-svw            2.3-3vmw.500.0.0.434219        VMware     6/22/2011...
                          misc-cnic-register       1.1-1vmw.500.0.0.434219        VMware     6/22/2011...
                          ipmi-ipmi-devintf        39.1-4vmw.500.0.0.434219       VMware     6/22/2011...
                          sata-sata-promise        2.12-3vmw.500.0.0.434219       VMware     6/22/2011...
                          sata-sata-nv             3.5-3vmw.500.0.0.434219        VMware     6/22/2011...
                          cisco-vem-v131-esx       4.2.1.1.3.24.0-3.0.8           Cisco      6/30/2011...
                          Step 10   Export the image profile to a depot file for future use.
                          [vSphere PowerCLI] > Export-EsxImageProfile –ImageProfile n1kv-Image –FilePath C:\n1kv-Image.zip –ExportToBundle. 
                          Step 11   Set up the rule for the host to boot with this image profile.
                          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.

                          [vSphere PowerCLI] > New-deployrule -item $img -name rule-test –Pattern “mac=00:50:56:b6:03:c1” 
                          [vSphere PowerCLI] > Add-DeployRule -DeployRule rule-test 
                          Step 12   Display the configured rule to make sure that the correct image profile is associated with the host.
                          [vSphere PowerCLI] > Get-DeployRuleSet 
                          
                          Name        : rule-test
                          PatternList : {mac=00:50:56:b6:03:c1}
                          ItemList    : {n1kv-Image}
                          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.


                          Installing the VEM Software on a Stateless ESXi Host Using esxcli

                          Before You Begin
                          • When entering 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.
                            ~ # vmware -v 
                            VMware ESXi 5.0.0 build-441354
                            ~ #
                            ~ # vmware -l 
                            VMware ESXi 5.0.0 GA
                            Step 2   Log in to the ESXi stateless host.
                            Step 3   Copy the offline bundle to the host.
                            ~ # esxcli software vib install -d /vmfs/volumes/newnfs/MN-VEM/VEM500-20110728153-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-v150-esx_4.2.1.2.1.0-3.0.1
                               VIBs Removed:
                               VIBs Skipped:
                            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.
                            ~ # esxcli software vib list | grep cisco 
                            cisco-vem-v150-esx    4.2.1.2.1.0-3.0.1    Cisco   PartnerSupported  2012-10-09
                            Step 5   Check that the VEM agent is running.
                            ~ # vem status -v 
                            Package vssnet-esxmn-ga-release
                            Version 4.2.1.2.1.0-3.0.1
                            Build 5
                            Date Thu Jul 28 01:37:10 PDT 2011
                            Number of PassThru NICs are 0
                            VEM modules are loaded
                            Switch Name      Num Ports   Used Ports  Configured Ports  MTU     Uplinks
                            vSwitch0         128         4           128               1500    vmnic4
                            Number of PassThru NICs are 0
                            VEM Agent (vemdpa) is running
                            Step 6   Display the VEM version, VSM version, and ESXi version.
                            ~ # vemcmd show version 
                            VEM Version: 4.2.1.2.1.0-3.0.1
                            VSM Version:
                            System Version: VMware ESXi 5.0.0 Releasebuild-441354
                            Step 7   Display the ESXi version and details about pass-through NICs.
                            ~ # vem version -v 
                            Number of PassThru NICs are 0
                            Running esx version -441354 x86_64
                            VEM Version: 4.2.1.2.1.0-3.0.1
                            VSM Version:
                            System Version: VMware ESXi 5.0.0 Releasebuild-441354
                            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.
                            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    248    Virtual Ethernet Module          NA                             ok
                            
                            Mod  Sw                Hw
                            ---  ----------------  ------------------------------------------------
                            1    4.2(1)SV1(4a)     0.0
                            2    4.2(1)SV1(4a)     0.0
                            3    4.2(1)SV1(4a)     VMware ESXi 5.0.0 Releasebuild-441354 (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
                            
                            Mod  Server-IP        Server-UUID                           Server-Name
                            ---  ---------------  ------------------------------------  --------------------
                            1    10.104.62.227    NA                                    NA
                            2    10.104.62.227    NA                                    NA
                            3    10.104.62.216    3fa746d4-de2f-11de-bd5d-c47d4f7ca460  sans2-216.cisco.com

                            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 the vCenter Server, choose Home > Update Manager > Configuration > ESX host/Cluster settings.
                              Step 2   Check the PXE Booted ESXi Host Settings check box.
                              Figure 61. ESX Host/Cluster Settings Window



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

                              Installing a VSM on the Cisco Nexus 1010

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


                              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.


                              Before You Begin

                              Copy the ISO file to the bootflash:repository/ of the virtual service blade.

                              Procedure
                                Step 1   Create a virtual service blade by entering the following commands.
                                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.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.4.2.1.SV2.1.1.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 Cisco Nexus 1000V.
                                Note   

                                The configuration in the highlighted code is optional to change svs mode from Layer 2 to Layer 3.

                                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)#
                                
                                Note: Control VLAN and Packet VLAN are not used in L3 mode.

                                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

                                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.