Bitbucketblog

I decided to run the 1000v, version 4.2(1) SV1(5.1), install in a vCenter 4.1.0 environment today.  The first component in setting up a Nexus 1000v deals with the Virtual Supervisor Module (VSM).  The VSM has the ability to control multiple Virtual Ethernet Modules (VEMs) as a singular modular switch.  Configuration changes can be made in the VSM that will be propagated out to the VEMs.

As I was going through the IMC, I had encountered several issues and opted to install manually using the steps below:

-Create 3 x port groups (i.e. control, management, and packet) in vCenter for the VSM

-Create a typical virtual machine: Other Linux (64-bit), 3 GB disk, 2GB memory, 3 x e1000 NICs

-Start VM with nexus-1000v-mx.4.2.1.SV1.5.1.iso and follow the setup prompts; example for Mgmt0: 10.1.1.10

-Install and register the plug-in: https://10.1.1.10, download the cisco_nexus_1000v_extension.xml file, and register the xml under vCenter Manage Plug-ins

-Configure VSM connectivity:

svs connection NK1V-TEST
vmware dvs datacenter-name NAMEOFVCENTER
protocol vmware-vim
remote ip address 10.1.1.123
connect

-Create system uplink profile in VSM:

port-profile type ethernet SYSTEM-UPLINK
switchport mode trunk
switchport trunk allowed vlan 111,222,333,444
system vlan 111,222,333
vmware port-group SYSTEM-UPLINK
no shutdown
state enabled

-Create port profile in VSM:

port-profile type vethernet PORTS
switchport mode access
switchport access vlan 110
vmware max-ports 1024
no shutdown
state enabled

All the steps above would have been handled automatically if IMC worked.  Now that the VSM is operational, the VEM module needs to be installed which I’ll cover in another post.

For more information regarding installing 1000v, you should refer to the guide: http://goo.gl/YceTo