VEM not showing as module on VSM

rshughes80 · ‎11-04-2009

I have a couple of questions on the VSM - is this deployed on a per-cluster basis or per-datacenter within vSphere? Currently I have a cluster of rack mounts within vSphere that are currently on the Cisco 1000v distributed switch. We created a new cluster on a set of blade servers because these have different CPU/chipsets and we can't VMotion across. With that being said, can I leverage the VSM on one cluster with related VEM's and have VEM's in this new cluster within the same DataCenter in vSphere register back into that VSM? vem status on the ESX hosts show them registered to the distributed switch and the distributed switch on the Virtual Console has registered them as hosts however, from the CLI ( show module ) I don't see them VEM's registered.

Robert Burns · ‎11-04-2009

VSM is deployed per Datacenter.

You can have multple VEM hosts in different clusters registered on the same VSM.

On the VSM, if they don't show up when you listing show module, that usually means there is a mis-configuration in with the VLANs (specifically the Control VLAN). Can you confirm that all phsyical NICs in the new cluster are setup identical to the other clusters with the hosts properly showing up? Since the new cluster are blade servers, ensure your blade switch is allowing your Control & Packet VLANs to each hosts.

What type of blade servers & blade switch are you using? Any config/details from the blade switch you can provide would be useful.

Robert

rshughes80 · ‎11-04-2009

The new cluster is a UCS blade enclosure. I have 2 B200's dedicated and I've ensure all of the appropriate layer2 adjacencies are in place and forwarding. What is curious is I did a reload of the VSM and then one of the 2 blades was able to register ( VEM mod 5). The last one still holding is registered but offline; see below:

N1000V# sh modu vem map

Mod Status UUID License Status

--- ----------- ------------------------------------ --------------

3 powered-up 34353939-3539-4d58-5138-32374135485a licensed

4 powered-up 34353939-3630-4d58-5138-353141324230 licensed

5 powered-up 20090908-0000-0001-0000-00000000000d licensed

6 absent 20090908-0000-0001-0000-00000000000e n/a

[root@ucs-esx4-2 ~]# vem status !! problematic VEM

VEM modules are loaded

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch0 32 4 32 1500 vmnic0

vSwitch1 64 1 64 1500

DVS Name Num Ports Used Ports Configured Ports Uplinks

N1000V 256 11 256 vmnic1

VEM Agent (vemdpa) is running

Robert Burns · ‎11-04-2009

Are you using 1 or 2 uplinks for these UCS VEM hosts to the DVS?

Please paste your uplink port profile(s) here.

If you're using two, you'll need to ensure you create a Port Channel on the 1000v and/or manually assign the sub-group IDs as UCS currently does not pass CDP info for vPC-HM.

What you can try is to remove the host from the DVS in vCenter-Networking view, and then on the VSM issue a "no vem 6" to clear the place holder for this blade, and then re-add it.

When you re-add if you're still having an issue can you paste the output of the following command issue from the VSM:

"module vem 6 execute vemcmd show card"

Thanks,

Robert

rshughes80 · ‎11-04-2009

Thanks!

I had to first disassociate all of the VM's attached to the DVS for that ESX host and then was able to disassociate it from the DVS. Once I re-added it, everything came up fine. Thanks for the command help.

N1000V# sho module vem map

Mod Status UUID License Status

--- ----------- ------------------------------------ --------------

3 powered-up 34353939-3539-4d58-5138-32374135485a licensed

4 powered-up 34353939-3630-4d58-5138-353141324230 licensed

5 powered-up 20090908-0000-0001-0000-00000000000d licensed

6 powered-up 20090908-0000-0001-0000-00000000000e licensed

N1000V#