06-28-2013 02:24 PM
I've added a host and one VM to the Nexus 1000V and I can't get the VM to ping to save my life. Here is my running config:
!Command: show running-config
!Time: Fri Jun 28 21:14:30 2013
version 4.2(1)SV2(1.1a)
svs switch edition essential
feature telnet
username admin password 5 $1$M2bnKdBW$GlztCYnlZ1CubhAa97c42/ role network-admin
banner motd #Nexus 1000v Switch#
ssh key rsa 2048
ip domain-lookup
ip host DOM-Nexus1000v 10.13.10.5
hostname DOM-Nexus1000v
errdisable recovery cause failed-port-state
snmp-server user admin network-admin auth md5 0xdf8ae522bcafaed22c21154ee750a0af priv 0xdf8ae522bcafaed22c21154ee750a0af localizedkey
vrf context management
ip route 0.0.0.0/0 10.13.10.1
vlan 1,110,114
vlan 110
name Prod_Servers_110
vlan 114
name Prod_Servers_114
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-Uplink
vmware port-group
switchport mode trunk
switchport trunk allowed vlan 110,114
channel-group auto mode active
no shutdown
system vlan 110,114
state enabled
port-profile type vethernet Prod_Servers_110
vmware port-group
switchport mode access
switchport access vlan 110
no shutdown
max-ports 1024
state enabled
port-profile type vethernet Prod_Servers_114
vmware port-group
switchport mode access
switchport access vlan 114
no shutdown
max-ports 1024
state enabled
vdc DOM-Nexus1000v 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 1 maximum 1
limit-resource u6route-mem minimum 1 maximum 1
interface mgmt0
ip address 10.13.10.5/24
interface Vethernet1
inherit port-profile Prod_Servers_110
no shutdown
vmware dvport 100
interface control0
line console
boot kickstart bootflash:/nexus-1000v-kickstart.4.2.1.SV2.1.1a.bin sup-1
boot system bootflash:/nexus-1000v.4.2.1.SV2.1.1a.bin sup-1
boot kickstart bootflash:/nexus-1000v-kickstart.4.2.1.SV2.1.1a.bin sup-2
boot system bootflash:/nexus-1000v.4.2.1.SV2.1.1a.bin sup-2
svs-domain
domain id 10
control vlan 1
packet vlan 1
svs mode L3 interface mgmt0
svs connection vcenter
protocol vmware-vim
remote ip address 10.13.10.126 port 80
vmware dvs uuid "7b 86 25 50 34 c7 35 72-fb 30 e6 58 d9 98 61 c2" datacenter-name DOM_Datacenter
admin user n1kUser
max-ports 8192
connect
vservice global type vsg
tcp state-checks invalid-ack
tcp state-checks seq-past-window
no tcp state-checks window-variation
no bypass asa-traffic
vnm-policy-agent
registration-ip 0.0.0.0
shared-secret **********
log-level
Here's a sh vlan output:
VLAN Name Status Ports
---- -------------------------------- --------- -------------------------------
1 default active
110 Prod_Servers_110 active Veth1
114 Prod_Servers_114 active
VLAN Type
---- -----
1 enet
110 enet
114 enet
Remote SPAN VLANs
-------------------------------------------------------------------------------
Primary Secondary Type Ports
------- --------- --------------- -------------------------------------------
Here's a sh int status output:
DOM-Nexus1000v(config-if)# sh int status
--------------------------------------------------------------------------------
Port Name Status Vlan Duplex Speed Type
--------------------------------------------------------------------------------
mgmt0 -- up routed full 1000 --
Veth1 -- down 110 auto auto --
control0 -- up routed full 1000 --
I've tried over and over the get the port 100 not to be in VLAN 1 in vCenter. What am I doing wrong here? I have the vm settings right also. Any suggestions?
07-01-2013 04:18 AM
Can we see
"show svs connection"
"show module"
One thing I don't see is a vmk interface assigned to the VEM. You are doing L3 control mode which requires that you assign a vmk interface to the VEM. You will need to create a new veth port-profile with "capability l3control" and assign the vmk interface to that port-profile.
louis
07-01-2013 05:36 AM
DOM-Nexus1000v# show svs connection
connection vcenter:
ip address: 10.13.10.126
remote port: 80
protocol: vmware-vim https
certificate: default
datacenter name: DOM_Datacenter
admin: n1kUser(user)
max-ports: 8192
DVS uuid: 7b 86 25 50 34 c7 35 72-fb 30 e6 58 d9 98 61 c2
config status: Enabled
operational status: Connected
sync status: Complete
version: VMware vCenter Server 5.1.0 build-880146
vc-uuid: 94B14170-27B9-4C5B-8399-894A433C994D
DOM-Nexus1000v# 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)SV2(1.1a) 0.0
2 4.2(1)SV2(1.1a) 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 10.13.10.5 NA NA
2 10.13.10.5 NA NA
* this terminal session
07-01-2013 09:50 AM
Yeah.There is no module showing up. You need to see a module #3 which would be the ESXi host to show up with "show module"
You need to add a vmknic to the VEM module for everything to work in L3 mode. You can create a new vmk interface or migrate the mgmt vmk interface.
Create a new port-profile like
port-profile type veth vmk-l3
switchport mode access
switchport access vlan #
no shut
vmware port-group
system vlan #
capability l3 control
state enabled
Then assign a vmk interface to that port-profile the module should show up and everything will work.
My recommendation would be to migrate the mgmt vmk interface. If you don't want to do that just be aware of two potential issues.
1. Don't create another vmk interface on the same subnet as your mgmt vmk.
2. You might have to add a static route to the ESXi host so that the new vmk interface can access the mgmt interface of the VSM.
louis
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