06-21-2010 01:48 PM
Newly deployed Nexus 1000v, running two VSMs (HA) and VEMs on two ESXi 4.0 hosts. VSM-VEM communication appears to be okay (we're not running the VSMs on the VEMs), and license status seems to be okay... but the vethernet port used by the first VM in the environment is going into an inactive state. How to troubleshoot?
n1kv# show license usage
Feature Ins Lic Status Expiry Date Comments
Count
--------------------------------------------------------------------------------
NEXUS1000V_LAN_SERVICES_PKG No 16 In use 16 Aug 2010 -
--------------------------------------------------------------------------------
n1kv# show modules vem internal license-info
License Sync Initiator : VEM 3
License Sync Stages : Complete
Num of Def Licenses in Use : 0
Num of Sync participants : 2
License Host-ID : 2846680221267926279
Default Eval time left : 0 days
Installed lic count : 16
Install time : 1267926279(07 Mar 2010)
Current time : 1277152209(21 Jun 2010)
---------------------VEM License Info -----------------------
Vem Current License Operation License Status License Flags
--- ------------------------- -------------- -------------
3 None licensed None
4 None licensed None
------------------VEM Socket License Info -------------------
Vem Sync License Usage Sockets License Version
--- ---- ------------- ------- ---------------
3 Yes 2 2 1.0
4 Yes 2 2 1.0
n1kv# show interface virtual port-mapping
-------------------------------------------------------------------------------
Port Hypervisor Port Status Reason
-------------------------------------------------------------------------------
Veth1 DVPort100 down inactive
From the VSM log: %VIM-5-IF_DOWN_INACTIVE: Interface Vethernet1 is down (Inactive)
n1kv# show port-profile
port-profile Server_Vlan115
description:
type: vethernet
status: enabled
capability l3control: no
pinning control-vlan: -
pinning packet-vlan: -
system vlans: none
port-group: Server_Vlan115
max ports: 128
inherit:
config attributes:
switchport mode access
switchport access vlan 115
no shutdown
evaluated config attributes:
switchport mode access
switchport access vlan 115
no shutdown
assigned interfaces:
Vethernet1
Any ideas what to investigate here?
06-21-2010 09:12 PM
Hi Rudd,
The interface might be down inactive due to the vlan (115) not being defined on the VSM. Can you define vlan 115 on the VSM and check for the interface status.
This is all you need to do:
n1k# configure t
n1k(config)# vlan 115
nk(config-vlan)#
./Abhinav
06-22-2010 08:36 AM
Ugh! I can't believe I missed that... this was the seventh site out of eight, and I had working n1kv's in every other location... just forgot to define the VLAN!
Thanks much for the suggestion... dead on.
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