12-28-2011 06:14 AM
Hi all,
We discover some problems with installing Nexus 1000v in our lab.
I read almost all threads in this comunity and in vmware and can't understand how to figure where is the exact problem
Here is some info for our setup (for all software we use 60 days trial license):
ESXi side (we have 3 ESXi hosts 192.168.44.21, 22 & 26)
~ # vmware -v
VMware ESXi 5.0.0 build-515841
~ # esxcli software vib list |grep cisco
cisco-vem-v131-esx 4.2.1.1.4.1.0-3.0.4 Cisco PartnerSupported 2011-12-22
~ # vem version -v
Number of PassThru NICs are 0
Running esx version -515841 x86_64
VEM Version: 4.2.1.1.4.1.0-3.0.4
VSM Version: 4.2(1)SV1(4a)
System Version: VMware ESXi 5.0.0 Releasebuild-515841
~ # vemcmd show card info
Card UUID type 2: info
Card name: esx22
Switch name: switch
Switch alias: DvsPortset-0
Switch uuid: 51 4a 17 50 be 8d ec 8a-6e 2f 4b a2 19 f2 76 01
Card domain: 44
Card slot: 1
VEM Tunnel Mode: L2 Mode
VEM Control (AIPC) MAC: 00:02:3d:10:2c:00
VEM Packet (Inband) MAC: 00:02:3d:20:2c:00
VEM Control Agent (DPA) MAC: 00:02:3d:40:2c:00
VEM SPAN MAC: 00:02:3d:30:2c:00
Primary VSM MAC : 00:50:56:97:5e:53
Primary VSM PKT MAC : 00:50:56:97:5e:55
Primary VSM MGMT MAC : 00:50:56:97:5e:54
Standby VSM CTRL MAC : 00:50:56:97:5e:56
Management IPv4 address: 192.168.44.22
Management IPv6 address: 0000:0000:0000:0000:0000:0000:0000:0000
Secondary VSM MAC : 00:00:00:00:00:00
Secondary L3 Control IPv4 address: 0.0.0.0
Upgrade : Default
Max physical ports: 32
Max virtual ports: 216
Card control VLAN: 50
Card packet VLAN: 51
Card Headless Mode : Yes
Processors: 24
Processor Cores: 12
Processor Sockets: 2
Kernel Memory: 100652780
Port link-up delay: 5s
Global UUFB: DISABLED
Heartbeat Set: False
PC LB Algo: source-mac
Datapath portset event in progress : no
~ # vem status -v
Package vssnet-esxmn-ga-release
Version 4.2.1.1.4.1.0-3.0.4
Build 4
Date Wed Jul 27 20:31:30 PDT 2011
Number of PassThru NICs are 0
VEM modules are loaded
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vSwitch0 128 7 128 1500 vmnic1
DVS Name Num Ports Used Ports Configured Ports MTU Uplinks
switch 256 15 256 1500 vmnic4,vmnic5,vmnic0
Number of PassThru NICs are 0
VEM Agent (vemdpa) is running
Virtual Center 5.0.0 build-455964
From vmware website available download is for version 456004, but files comes with names:
VMware-vCenter-Server-Appliance-5.0.0.3324-472350.
Actualy the build version when service is started is 455964
In this document : Cisco Nexus 1000v Compatibility Information
In Table 1 on first line is our ESXi Version ( ESXi 5.0.0 P02 ) with this patch ESXi500-201112001.zip and compatible under Cisco release version - 4.2(1)SV1(4a)
But in Table 3 again on first line are our version except for Linux vCenter Server Appliance, for minimum version they need 456004. The same version that we download from vmware site, but this version after instalation appear as 455964! Here is the only difference that I can figure.
Nexus 1000v:
switch# sh run
!Command: show running-config
!Time: Wed Dec 28 13:34:56 2011
version 4.2(1)SV1(4a)
no feature telnet
username admin password 5 $1$iZsCRxDi$ZsxFO0gxt2of5RxkuyejT0 role network-admin
banner motd #Nexus 1000v Switch#
ssh key rsa 2048
ip domain-lookup
ip domain-lookup
vem 3
snmp-server user admin network-admin auth md5 0xe6e1706b86ab72487c80011d953f0183 priv 0xe6e1706b86ab72487c80011d953f0183 localizedkey
vrf context management
ip route 0.0.0.0/0 192.168.44.1
vlan 1
vlan 14
name Managment
vlan 50
name Control
vlan 51
name Packets
port-channel load-balance ethernet source-mac
port-profile default max-ports 32
port-profile type ethernet Unused_Or_Quarantine_Uplink
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type vethernet Unused_Or_Quarantine_Veth
vmware port-group
shutdown
description Port-group created for Nexus1000V internal usage. Do not use.
state enabled
port-profile type ethernet System-Uplinks
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 14,50-51
no shutdown
system vlan 14,50-51
description System-Uplinks
state enabled
port-profile type vethernet VM-Access
vmware port-group
switchport mode access
switchport access vlan 14
no shutdown
system vlan 14
state enabled
port-profile type ethernet UpLink-PortChannel
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 1-3967,4048-4093
channel-group auto mode on sub-group cdp
no shutdown
system vlan 14,50-51
state enabled
vdc switch id 1
limit-resource vlan minimum 16 maximum 2049
limit-resource monitor-session minimum 0 maximum 2
limit-resource vrf minimum 16 maximum 8192
limit-resource port-channel minimum 0 maximum 768
limit-resource u4route-mem minimum 32 maximum 32
limit-resource u6route-mem minimum 16 maximum 16
limit-resource m4route-mem minimum 58 maximum 58
limit-resource m6route-mem minimum 8 maximum 8
interface mgmt0
ip address 192.168.44.3/24
interface control0
line console
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.2.1.SV1.4a.bin sup-1
boot system bootflash:/nexus-1000v-mz.4.2.1.SV1.4a.bin sup-1
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.2.1.SV1.4a.bin sup-2
boot system bootflash:/nexus-1000v-mz.4.2.1.SV1.4a.bin sup-2
svs-domain
domain id 44
control vlan 50
packet vlan 51
svs mode L2
svs connection vc
protocol vmware-vim
remote ip address 192.168.44.2 port 80
vmware dvs uuid "51 4a 17 50 be 8d ec 8a-6e 2f 4b a2 19 f2 76 01" datacenter-name Dev
max-ports 8192
connect
vsn type vsg global
tcp state-checks
vnm-policy-agent
registration-ip 0.0.0.0
shared-secret **********
log-level
switch# show svs connections
connection vc:
ip address: 192.168.44.2
remote port: 80
protocol: vmware-vim https
certificate: default
datacenter name: Dev
admin:
max-ports: 8192
DVS uuid: 51 4a 17 50 be 8d ec 8a-6e 2f 4b a2 19 f2 76 01
config status: Enabled
operational status: Connected
sync status: Complete
version: VMware vCenter Server 5.0.0 build-455964
switch# show module
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)SV1(4a) 0.0
2 4.2(1)SV1(4a) 0.0
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
2 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA
Mod Server-IP Server-UUID Server-Name
--- --------------- ------------------------------------ --------------------
1 192.168.44.3 NA NA
2 192.168.44.3 NA NA
* this terminal session
switch# show module vem missing
Server-IP Server-UUID Server-Name
--------------- ------------------------------------ --------------------
192.168.44.22 46b7b651-c2dc-0343-a10a-1c4dff7441bb NA
192.168.44.26 9fda2605-f011-7f45-8ef8-7a0aaaffd212 NA
192.168.44.21 c29470a0-40cb-3642-ac8a-3344b48bfd95 NA
switch# show license usage
Feature Ins Lic Status Expiry Date Comments
Count
--------------------------------------------------------------------------------
NEXUS_VSG_SERVICES_PKG No 16 Unused 25 Feb 2012 -
NEXUS1000V_LAN_SERVICES_PKG No 16 Unused 25 Feb 2012 -
--------------------------------------------------------------------------------
I tested all Vlans and ports in our switches, and there is no problem on L2 and L3 in VLAN 14,50,51.
This test enviroment is in HP Blace C7000 with 3 Blade Server Proliant BL460G7, Virtual Connect v3.30 and VC FLex-10 ethernet modules on blade chasi. The switch is Nexus 5000.
I can provide more information, on request, because all Troubleshooting guides didn't help me to resolve that problem
P.S. I want to excuse me, because I start new thread with issue that was commented before, but I didn't find my answers
Thanks in advance
Solved! Go to Solution.
12-30-2011 02:57 AM
Kalin,
Is VSM behind VEM or vswitch ?
Are VSM NICs connected and associated with corresponding port group ?
Let us pick up one host / VEM module. Are necessary VLANs configured and allowed along the path ?
Padma
12-30-2011 02:57 AM
Kalin,
Is VSM behind VEM or vswitch ?
Are VSM NICs connected and associated with corresponding port group ?
Let us pick up one host / VEM module. Are necessary VLANs configured and allowed along the path ?
Padma
01-05-2012 06:45 AM
Hi Padma,
and
Happy New Year. Best Whishes
I found some missconfiguration in my port profile, and when associate correct NIC with coreect port profiles everything work nice
Thank you.
01-05-2012 09:01 AM
Hello Kalin,
Wish you happy new year
Padma
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: