08-20-2009 12:31 AM
Hi all,
have a little problem. I want to test the nexus 1000v and have installed the VSM and it works fine.
I`ve createt three virtual machine port groups in the vcenter (Control Vlan 51, Packet Vlan 52 and Mgmt Vlan 1) . The default Network on the vswitch ist the Vm Network with Vlan 1.
I`ve added a host to the VSM with two nics (system-uplink and data-uplink) and at this moment a new VEM should be created or i`m wrong?
Maybe i forgot something???
If i look on the ESX4 server console and perform a "vem status" i see this:
VEM modules are loaded
Switch Name Num Ports Used Ports Configured Ports MTU Uplinks
vSwitch0 32 18 32 1500 vmnic5,vmnic4,vmnic3,vmnic2,vmnic1,vmnic0
DVS Name Num Ports Used Ports Configured Ports Uplinks
NEXUS-VSM 256 10 256 vmnic7,vmnic6
VEM Agent (vemdpa) is running
I think this is ok ?!
If i look on the nexus-vsm and perform a "show module" i see this:
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.0(4)SV1(1) 0.0
2 4.0(4)SV1(1) 0.0
Mod MAC-Address(es) Serial-Num
--- -------------------------------------- ----------
1 00-19-07-6c-5a-a8 to 00-19-05-6d-63-a2 NA
2 00-19-07-6c-5a-a8 to 00-19-05-6d-63-a2 NA
Mod Server-IP Server-UUID Server-Name
--- --------------- ------------------------------------ --------------------
1 10.0.10.10 NA NA
2 10.0.10.10 NA NA
* this terminal session
I think this looks good too.
A "show license usage" shows this:
NEXUS-VSM-Primary# show license usage
Feature Ins Lic Status Expiry Date Comments
Count
--------------------------------------------------------------------------------
NEXUS1000V_LAN_SERVICES_PKG Yes 16 Unused 13 Oct 2009 -
--------------------------------------------------------------------------------
Why the status is "unused" because there is no VEM active ?
The nexus plugin is also installed. Hope someone could help me. I strongly want to test the nexus 1000v
Thanks and regards
Thorsten
08-20-2009 12:41 AM
Thorsten,
Your config looks good, but you appear to have a problem on your upstream switch with vlans. Though the VEM DPA is running successfully, if the ESX host can't communicate back to the VSM over the Control VLAN the module will never show up on your VSM.
Ensure the following:
1. On your upstream switches, ensure you haven't set a "Native vlan" on the trunks that connect to your ESX VEM host.
2. On your Virtual Center port groups, ensure you're set the VLAN tag for your Control and Packet Portgroups to be 51 and 52 respectfully.
This issue is 99.999999% related to a vlan issue. If the above doesn't fix your problem please provide:
- The "show run" of the switch your ESX VEM host is connected to, and indicate which port you're using.
- Provide a "show run" of your VSM.
Cheers,
Robert
08-20-2009 12:57 AM
Robert,
thanks for your quick answer.
Here is a "sh run" of one interface of the uplink switch:
interface GigabitEthernet1/0/2
description "ESX01 TRUNK"
switchport trunk encapsulation dot1q
switchport trunk native vlan 99
switchport trunk allowed vlan 1,10,51,52,99,101-200
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpduguard enable
Do you think the native vlan is the Problem? Why this not work?
If i remove the native vlan for the ports which connected to the DVS the VEM come up automaticaly or have i re-add the host to the DVS ?
08-20-2009 01:03 AM
Which port is this connected to? Your System uplink or Data-Uplink?
In our experience and a best practice with VMware is to do all your tagging on the host. We've seen many issues with this.
What traffic is on vlan 99? If this is something you can change I'd remove the native vlan on the switch, and just tag the Port Group for vlan 99 on your vSwitch/DVS
Can you provide the show run of your VSM please?
As soon as your VSM can communicate with your VEM host it will show up. No need to re-add it.
Robert
08-20-2009 01:19 AM
vmnic6 is connected to the system-uplink port-groupe
vmnic7 is connected to the data-uplink port-group
i have to go to the datacenter and have to check which ports are connected to these vmnics.
if i perform a "sh mac address-table" on the uplink switch i can`t see the MACs of these two vmnics....any suggestions?
On VLAN 99 the ESX traffic is on because of transfering the vlans from esx to the upstream switch..... with vlan1 this still not work on a catalyst switch... this is how we make it the last years with ESX servers and it works fine.
Here is the sh run of the VSM:
NEXUS-VSM-Primary# sh run
version 4.0(4)SV1(1)
username admin password 5 $1$5l.LussdSdjfhdsdjgs$dsdqal28/l.0vhhQgghT77r5dssdMUKdsdfma. role network-admin
ip domain-lookup
ip host NEXUS-VSM-Primary 172.16.110.90
kernel core target 0.0.0.0
kernel core limit 1
system default switchport
snmp-server user admin network-admin auth md5 0x1cb044ef41dsfdsa334c9455f950d7a0dsfsce564 priv 0xsdfsd1cb044esdfsdff41a334c9455f950d7a0ce564 local
izedkey
snmp-server enable traps license
vrf context management
ip route 0.0.0.0/0 172.16.110.1
switchname NEXUS-VSM-Primary
vlan 1,51-52
vlan 53
name VM-Data
vdc NEXUS-VSM-Primary id 1
limit-resource vlan minimum 16 maximum 513
limit-resource monitor-session minimum 0 maximum 64
limit-resource vrf minimum 16 maximum 8192
limit-resource port-channel minimum 0 maximum 256
limit-resource u4route-mem minimum 32 maximum 80
limit-resource u6route-mem minimum 16 maximum 48
port-profile Unused_Or_Quarantine_Uplink
description "Port-group created for Nexus1000V internal usage. Do not use."
capability uplink
vmware port-group
shutdown
state enabled
port-profile Unused_Or_Quarantine_Veth
description "Port-group created for Nexus1000V internal usage. Do not use."
vmware port-group
shutdown
state enabled
port-profile system-uplink
capability uplink
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 51-52
channel-group auto mode on sub-group cdp
no shutdown
system vlan 51-52
state enabled
port-profile data-uplink
capability uplink
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 53
channel-group auto mode on sub-group cdp
no shutdown
state enabled
port-profile Test-VM
vmware port-group
switchport mode access
switchport access vlan 110
no shutdown
state enabled
interface mgmt0
ip address 172.168.110.90/24
interface control0
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.0.4.SV1.1.bin sup-1
boot system bootflash:/nexus-1000v-mz.4.0.4.SV1.1.bin sup-1
boot kickstart bootflash:/nexus-1000v-kickstart-mz.4.0.4.SV1.1.bin sup-2
boot system bootflash:/nexus-1000v-mz.4.0.4.SV1.1.bin sup-2
svs-domain
domain id 1
control vlan 51
packet vlan 52
svs mode L2
svs connection vc
protocol vmware-vim
remote ip address 172.16.110.100
vmware dvs uuid "8b 03 1c 30 d6 0f a7 25-34 ff c4 07 56 10 86 76" datacenter-name ESXCenter
connect
08-20-2009 01:44 AM
You can use CDP (assuming you have it enabled) to find out which Ports on the switch each VMNIC is actually connected to.
In vCenter, click on a host, then go to Configuration Tab, Select Networking on the right, click the Distributed Virtual Switch Tab.
Expand your "System-Uplinks" Portgroup on the right, click the plus sign near the adapter and click the "i" (info) icon. This will show you CDP info and tell you what port your vmnic is connected to. See the attached screen shot.
Then let me know what port you're vmnic6 is connected to. If you didn't send the switch config for that port, include it in your response.
I still don't follow what vlan 99 is. Is that your Service Consle/MAnagement VLAN?
Robert
08-20-2009 02:11 AM
I`ve removed the native vlan from the interfaces and now i`m able to see information on the "i" (info) icon. But only for a short time, now the information is gone and everything is empty, why? CDP is enabled....
Tthe VEM module is not shown on the VSM.
Here are the config for VMNIC7 - data-uplink
!
interface GigabitEthernet2/0/3
description "NEXUS 1000v TEST"
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,10,51,52,99,101-200
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpduguard enable
Here are the config for VMNIC6 - system-uplink
!
interface GigabitEthernet2/0/4
description "NEXUS 1000v TEST"
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,10,51,52,99,101-200
switchport mode trunk
spanning-tree portfast trunk
spanning-tree bpduguard enable
!
Vlan99 are the TRUNK ports from the ESX host to the uplink switch. We have different VlANs on the ESX host and these VLANs have to transferred over the switch.
08-20-2009 02:32 AM
Problem resolved. Control & Packet VLANs were not created on upstream phsyical switch.
Cheers,
Robert
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide