1000v with vCenter on same ESX host

[Zachary McGibbon]

In my lab I have only one ESX server.  On this server I am running VSM and vCenter (appliance).

I am trying to get 1000v working however everytime I try to migrate my ports I get the following error:

Network configuration change disconnected the host '192.168.0.10' from vCenter server and has been rolled back.

fault.NetworkDisruptedAndConfigRolledBack.summary

It seems that it doesn't like the fact that vCenter lives on the same ESX host as I'm trying to migrate.

Anyone have any ideas how I could get this to work?

I've tried both L2 and L3 mode but have failed with both.  I have tried using techniques from the Cisco Cloud Lab L3 tutorial as well as some videos I found on Youtube:

http://www.youtube.com/user/sysadmintutorials/videos?view=0

... But I keep getting stuck in the same place...

My port profile config:

port-profile type ethernet vmware-uplinks

  vmware port-group

  switchport mode trunk

  mtu 9000

  switchport trunk allowed vlan 1-3967,4048-4093

  no shutdown

  system vlan 62

  state enabled

port-profile type vethernet Management

  vmware port-group

  switchport mode access

  switchport access vlan 62

  no shutdown

  state enabled

port-profile type vethernet VLAN_62

  vmware port-group

  switchport mode access

  switchport access vlan 62

  no shutdown

  state enabled

!

svs-domain

  domain id 1

  control vlan 62

  packet vlan 62

  svs mode L2 

!

Also, I can never get the VEM to show up in my VSM when I do a 'show mod'...

Any ideas?

[Phillip Wilson]

Ok so before you can migrate anything onto the Nexus 1000v (VSM) you have to make sure it has connectivity to the VEM (Host) with the control vlan.  When you do a "show mod" it will show module 1 and 2 as the primary and secondary (if you have an HA) VSM.  When you add a host to the VSM they will fill in below that as module 3, 4 and so on.  Looks like you have it setup to do L2 in your config.  And you say when you do a show mod it doesn't show the current VEM for the host.  From what I have read and setup in live environments is you want seperate vlans for control, packet, and management. and seperate vlans for vm servers. I would create different port profiles for vmtraffic and one for your system traffic (management, control, packet).  If your VSM cannot talk to the VEM installed on the host across the system uplink they VEM will not be added as a module on your VSM.  I don't know how many nics you have on your ESX host, but make one assigned to vmware-uplinks port profile and then assign a seperate one to system-uplinks.  This should work I believe if i have typed this in correctly.  If you have followed the install sheet for the n1k on cisco's site you might need to confirm that the correct VIB is installed on your ESX host as well that is compatibale with the version of Nexus 1000v you have running.  You can download the VIB from your VSM if it's managment is working correctly (on the standard switch) at http://vsm-management-ip.  I hope this helps you out.

Example below.

vlan 50

     name Servers

vlan 61

     name Management

vlan 62

     name Control

vlan 63

     name Packet

port-profile type ethernet vmware-uplinks

  vmware port-group

  switchport mode trunk

  mtu 9000

  switchport trunk allowed vlan 50

  no shutdown

  state enabled

port-profile type ethernet system-uplinks

  vmware port-group

  switchport mode trun

  switchport trunk allowed vlan 61,62,63

  system vlans 61,62,63

  no shutdown

  state enabled

port-profile type vethernet Management

  vmware port-group

  switchport mode access

  switchport access vlan 61

  no shutdown

  system vlan 61

  state enabled

port-profile type vethernet Control

  vmware port-group

  switchport mode access

  switchport access vlan 62

  system vlan 62

  no shutdown

  state enabled

port-profile type vethernet Packet

  vmware port-group

  switchport mode access

  switchport access vlan 63

  system vlan 63

  no shutdown

  state enabled

port-profile type vethernet Servers

  vmware port-group

  switchport mode access

  switchport access vlan 50

  no shutdown

  state enabled

!

svs-domain

  domain id 1

  control vlan 62

  packet vlan 63

  svs mode L2