VEM not showing in VSM

[jayepate]

Hi All,

I am very new to Nexus1000v. I am trying to install it on Blade server. I have three servers, one with vCenter in vlan 100, other two with ESXi 4.0 have two pNICs. i have installed the VSM in one esx server whose service console in vlan 100 has uplink vmnic0 and VSM has uplink vmnic1. Other esx server has service console conected to vmnic0 in vlan 100  and installed VEM with uplink vmnic1.  I have added the host into DVS. VEM version in ESx server shows the VSM version. but sh module in N1000v not showing up the VEM module. system-uplink profiles has been configured. I have attached the sh-run of the VSM.

COnfige of blade switch where the blade servers are connected.

!
interface GigabitEthernet0/6 ------------port connected  ESXi server where VSM is configured.
switchport mode trunk
speed 1000
!
!
interface GigabitEthernet0/7-------------- Port connected to ESXi server where VEM in installed.
switchport mode trunk
speed 1000
spanning-tree portfast
!

Please help me to solve this issue.

I have attached screen shot from VSM for sh module, VSM VM property, VEM status and version from esxi server.

[Robert Burns]

reason why your VEM modules are not showing up on the VSM are due a connectivity issue with your Control VLAN between the two devices.

Have you:

- Created your Control & Packet VLANs on all upstream switches in between the VSM & VEM hosts?

- Allowed the Control & Packet VLANs on all trunks?

You may want to run through the troubleshooting guide which should help you narrow down the issue:

http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_3/troubleshooting/configuration/guide/n1000v_trouble.html

In particular this section:

http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_3/troubleshooting/configuration/guide/n1000v_trouble_5modules.html#wp1192946

You can verify if the VEM can see the VSM by finding the VSM's Control MAC address (look in the vNIC properties of the first adapter of your VSM VM in vCenter) and the from the ESX host CLI enter:

vem-health check [VSM Control MAC address]

Ex.

[root@sv-vsphere01 ~]# vem-health check 00:50:56:bc:10:27
VSM Control MAC address: 00:50:56:bc:10:27
Control VLAN: 3001
DPA MAC: 00:02:3d:40:07:03

The VEM-VSM connectivity seems to be fine.

If you're still having issues post your running config of your VSM and the Switchport configuration of the upstream switch interface your host is connected to.

Regards,

Robert

[jayepate]

Thanks robert for your reply..

I have attached the running config of VSM and physical switch switchport configuration. VSM and VEM are connected to the two blade switch ( CBS 3040)  which is again connected to nexus 5k. I have configured the control and packet VLANs on both CBS and nexus5k switches. also those vlans are allowed on trunk.

!
interface GigabitEthernet0/6
switchport mode trunk
speed 1000
!
interface GigabitEthernet0/7
switchport mode trunk

speed 1000

please provide further trubleshooting steps.

[jayepate]

HI Robert,

While issuing the command vem-health chek <VSM control mac add> as per ur suggestion I am getting below output.

vem-health check 00:50:56:80:71:7e

Control VLAN: 200
DPA MAC: 00:02:3d:40:98:00

VSM heartbeats are not reaching the VEM.
Your uplink configuration is correct.
Recommanded action:
Check if the VEM's upstream switch has learned the VSM's Control MAC.

Could you please let me know what is the DPA MAC address? Where can i find it?

How to check in upstream switch for VSM's Control MAC Address?

Thanks,

Jayesh

[Robert Burns]

The DPA (Data Path Agent) is your VEM's MAC Address.  You can find this by issuing "vemcmd show card" from the CLI of your host.

Couple of issues regarding your config:

1. If you're going to use two differnet uplinks (one for system, one for VM Data), you have to separate VLANs on your uplinks.  Currently your System-uplink has all VLANs allowed which will cause issue as you also allow some VLANs on your VM-Data uplink.  Limit EACH uplink port profile to allowing ONLY the VLANs required.  Remember - a VLAN can only be allowed on ONE uplink port profile.

2. You're using VLAN 100 in your VM Uplink, but you haven't created VLAN 100 on your VSM.  Before any VLAN can be put into use, it must be created.  Allowing it on the uplink alone doesn't create it.  Ensure its also created on all upstream switches. "vlan 100" will create this on your VSM.

3.  I assume by your config you're only assigning a single interface from each host into each uplink port profile.  If you plan on adding multiple physical uplinks from each host to each uplink port profile, you'll need to create a port channel.  Keep this in mind if you decide to use redundant links for each uplinks port profile.

To troubleshoot futher you have to verify that you can see your VEM & VSM MAC address in VLAN 200 on each intermediate switch.

From each device you should be able to do something similar to:

show mac address-table vlan [Control VLAN] | include [VEM/VSM MAC address]

Ex.

Cat6509-E#show mac address-table vlan 200 | include 0050.56bc.36e1   << VEM/DPA MAC

Cat6509-E#show mac  address-table vlan 200 | include 0050.56bc.36ff   << VSM Control MAC

Trace this on each and every switch in between your VSM and VEM.  Somewhere along the line you'll find that either your VSM or VEM Control MAC address  is not appearing together.  That will isolate where to look for config errors next.

Robert

[jayepate]

Thanks Robert.

It has sovled my problem. Vlan was blocking in one of the upstrem link between blade switch and nexus5k.

Now i am able to view VEM on VSM.

Thanks once again for your valueable inputs.