04-27-2011 06:19 AM
I have a N1k version 4.0.4.SV13a that has 15 hosts connected to it and working.
I added a new host yesterday and the VEM install went smoothly (VUM) and everything looks good in vCenter.
However when I look in the VSM the module doesn't show up. When I do a show mod vem map it shows up as absent.
On the ESXi host (4.1)everything looks good.
vem status shows the DVS with the ports
vemcmd show card info - This seems to show that I am connected to the VSM
vemcmd show trunk - This shows all the correct vlans with CBL 4
vemcmd show port - This shows the interface with the Control vlan as Down. Also the trunk interfaces are set to CBL 0
Any idea on how to fix this? It is almost like there isn't a network path, but this blade has the exact same service profile template (UCS) as all the other blades.
04-27-2011 06:47 PM
Hi Kris,
Please provide the output of the following:
ESX# vem-health check
ESX# vemcmd show card
ESX# vemcmd show port
ESX# vemcmd show trunk
ESX# vemcmd show bd
After obtaining the above data, perform a 'vem restart' on the affected ESX server. Let me know if that clears the issue.
On a side note, please note that 'vemcmd show card' displays the opaque data, which is pushed from vCenter to the VEM. So it indicates that the communication between vCenter and VEM is okay.
Regards,
Michael
04-28-2011 07:06 AM
Here are all the commands. I have only removed the IP addresses....
I tried the vem restart and that didn't change anything.....
-----------------------------------------------------------------------------------------------------------------------------------------------------------
/sbin # /usr/lib/ext/cisco/nexus/vem-v121/sbin/vem-health check 00:50:56:98:00:03
VSM Control MAC address: 00:50:56:98:00:03
Control VLAN: 998
DPA MAC: 00:02:3d:40:0a:02
The VEM-VSM connectivity seems to be fine.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
/sbin # vemcmd show card
Card UUID type 2: 997040e0-a49a-11df-0000-00000000005d
Card name: bwi40-esxi-43
Switch name: hcs1-vzb-n1kv-1
Switch alias: DvsPortset-0
Switch uuid: 6e e1 18 50 12 9c fe e2-42 8e a7 e7 9f 25 47 39
Card domain: 10
Card slot: 3
VEM Tunnel Mode: L2 Mode
VEM Control (AIPC) MAC: 00:02:3d:10:0a:02
VEM Packet (Inband) MAC: 00:02:3d:20:0a:02
VEM Control Agent (DPA) MAC: 00:02:3d:40:0a:02
VEM SPAN MAC: 00:02:3d:30:0a:02
Management IPv4 address: XX.XX.XX.XX
Management IPv6 address: 0000:0000:0000:0000:0000:0000:0000:0000
Max physical ports: 32
Max virtual ports: 216
Card control VLAN: 998
Card packet VLAN: 997
Processors: 24
Processor Cores: 12
Processor Sockets: 2
Kernel Memory: 50265192
Port link-up delay: 5s
Heartbeat Set: False
-------------------------------------------------------------------------------------------------------------------------------------------
/sbin # vemcmd show port
LTL IfIndex Vlan Bndl SG_ID Pinned_SGID Type Admin State CBL Mode Name
8 0 3969 0 32 32 VIRT UP DOWN 4 Access
9 0 3969 0 32 32 VIRT UP DOWN 4 Access
10 0 998 0 32 32 VIRT UP DOWN 4 Access
11 0 3968 0 32 32 VIRT UP DOWN 4 Access
12 0 997 0 32 32 VIRT UP DOWN 4 Access
13 0 1 0 32 32 VIRT UP DOWN 0 Access
14 0 3967 0 32 32 VIRT UP DOWN 4 Access
15 0 3967 0 32 32 VIRT UP DOWN 4 Access
16 0 1 T 0 32 32 PHYS UP UP 0 Trunk vmnic0
17 0 1 T 0 32 32 PHYS UP UP 0 Trunk vmnic1
48 0 994 0 32 32 VIRT UP UP 4 Access vmk0
49 0 996 0 32 32 VIRT UP UP 4 Access vmk1
-------------------------------------------------------------------------------------------------------------------------------------------
/sbin # vemcmd show trunk
Trunk port 16 native_vlan 1 CBL 0
vlan(994) cbl 4, vlan(996) cbl 4, vlan(997) cbl 4, vlan(998) cbl 4, vlan(999) cbl 4,
Trunk port 17 native_vlan 1 CBL 0
vlan(994) cbl 4, vlan(996) cbl 4, vlan(997) cbl 4, vlan(998) cbl 4, vlan(999) cbl 4,
---------------------------------------------------------------------------------------------------------------------------------------------
/sbin # vemcmd show bd 998
BD 998, vdc 1, vlan 998, 3 ports
Portlist:
10
16 vmnic0
17 vmnic1
---------------------------------------------------------------------------------------------------------------------------------------------------------
hcs1-vzb-n1kv-1# show mod vem mapping
Mod Status UUID License Status
--- ----------- ------------------------------------ --------------
3 absent 997040e0-a49a-11df-0000-00000000005d licensed
05-06-2011 12:45 AM
Hi Kris,
Thanks for getting that data. From it, when I review the control vlan BD data, with 'vemcmd show bd 998', I do NOT see the LTL index for the port-channel interface.I can see that there is actually no port-channel interface created, when it should have been, from the output of 'vemcmd show port'. There were a couple of bugs with this type of symptom.
This is why the VEM is not visible on the VSM, within the VSM 'show module'. If you execute the command 'show module vem counters' a few times, and analyze the column "InHBeats", for Mod 3, you will probably find that this is NOT incrementing due to the lack of communication.
If you provide the output of the following commands, I should be able to narrow it down specifically which one it is. Depending on which Bug it is, the workaround is either to restart the ESX server or restart the VSM. However, ultimately the resolution will be an upgrade.
VSM:
- show vlan
- show system internal l2fm info detail
VEM:
- vemlog show all (warning output is long. You can send me a private message with this output, or attach to the thread)
Thanks,
Michael
05-09-2011 10:43 AM
Show vlan is attached
vemlog show all is attached
show system internal l2fm info detail
Distribution: TRUE, MACDB Recovery: Done
Issu state: Flag not set, Issu slot num: 0, ISSU SVI gwmac flag: False
Global BPDU Recpt Enable: TRUE
Default Aging Time: 300 seconds, Number of VLANs: 11, Reason: TMR_DEFAULT
Gateway Mac: 0200.0c00.003c
VLAN(0) Age: 300 sec, Reason: TMR_DEFAULT bd = 0
Num Static Macs: 0
Num Dynamic Macs: 0
VLAN(1) Age: 300 sec, Reason: TMR_DEFAULT bd = 1
Num Static Macs: 0
Num Dynamic Macs: 59
VLAN(66) Age: 300 sec, Reason: TMR_DEFAULT bd = 11
Num Static Macs: 0
Num Dynamic Macs: 0
VLAN(100) Age: 300 sec, Reason: TMR_DEFAULT bd = 2
Num Static Macs: 0
Num Dynamic Macs: 116
VLAN(101) Age: 300 sec, Reason: TMR_DEFAULT bd = 3
Num Static Macs: 0
Num Dynamic Macs: 0
VLAN(102) Age: 300 sec, Reason: TMR_DEFAULT bd = 4
Num Static Macs: 0
Num Dynamic Macs: 69
VLAN(994) Age: 300 sec, Reason: TMR_DEFAULT bd = 5
Num Static Macs: 0
Num Dynamic Macs: 317
VLAN(996) Age: 300 sec, Reason: TMR_DEFAULT bd = 6
Num Static Macs: 0
Num Dynamic Macs: 12
VLAN(997) Age: 300 sec, Reason: TMR_DEFAULT bd = 7
Num Static Macs: 0
Num Dynamic Macs: 160
VLAN(998) Age: 300 sec, Reason: TMR_DEFAULT bd = 8
Num Static Macs: 0
Num Dynamic Macs: 191
VLAN(999) Age: 300 sec, Reason: TMR_DEFAULT bd = 9
Num Static Macs: 0
Num Dynamic Macs: 132
05-09-2011 10:45 AM
Do you know the bug ids for the similar issues?
If it is a bug is there a release that it is fixed in that we should upgrade to?
08-19-2014 01:23 PM
Version 4.2(1)SV2(2.2)
2 ESXi release 1892794
vCenter release 1750787
Fiat# sh mod
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
1 0 Virtual Supervisor Module Nexus1000V active *
2 0 Virtual Supervisor Module Nexus1000V ha-standby
Mod Sw Hw
--- ------------------ ------------------------------------------------
1 4.2(1)SV2(2.2) 0.0
2 4.2(1)SV2(2.2) 0.0
Mod Server-IP Server-UUID Server-Name
--- --------------- ------------------------------------ --------------------
1 10.17.249.14 NA NA
2 10.17.249.14 NA NA
* this terminal session
Fiat# sh run (partial)
version 4.2(1)SV2(2.2)
svs switch edition essential
vem 3
host id 4c4c4544-004e-4310-8035-b3c04f333032
vem 4
host id 4c4c4544-0034-4710-8033-b4c04f333032
interface port-channel1
inherit port-profile Uplink
vem 3
interface port-channel2
inherit port-profile Uplink
vem 4
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: