Hi Tenaro, Please find my answers inline: - ESXi hosts connected and control0 used as L3 control interface but basic "ping a.b.c.d" (vmk interface on esxi) from VSM doesn't work; however, "ping a.b.c.d vrf default" works! Is that expected behavior? All IPs in the same subnet. [Shankar] In the Nexus 1000v, a regular ping would use the management vrf (and hence the mgmt0 interface). To ping from the control0 interface (default vrf), we need to specify the vrf explicitly like what you've stated. This is expected. - Is there a way to change system vlan that is already used in existing port-profiles (either for ethernet or vethernet)? If yes, please let us know how? [Shankar] You can add System VLANs when the port-profile is in use. But you cannot delete a system VLAN when the port-profile is in use: http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus1000/sw/5_x/port_profile_config/b_Cisco_N1KV_VMware_Port_Profile_Config_5x/b_Cisco_N1KV_VMware_Port_Profile_Config_5x_chapter_0100.html#concept_61CEFBDEF93C4163B1C2706120DF69E3 - Can you explain what is actually happening behind when host is connected to N1kv? Is control0 interface on VSM side and vmk on ESXi side mandatory prerequisite if "svs mode L3 interface control0" is specified or there is some alternative way for those two to communicate? [Shankar] In the L3 mode, the VSM can use the mgmt0 or the control0 interface to talk to the VEMs. On the VEM, we use a vmkernel interface that is attached to a port-profile with 'capability l3control'. So the two end points (mgmt0 or control0 on the VSM and vmkernel on the VEM) talk to each other and they are mandatory. In the L2 mode, the control0 interface needs L2 connectivity to the VEM (no L3 stuff here). So if you have the same VLAN extended from the VSM's control0 interface to at least one of the VEM's uplink ports, this will work.   - Do you agree with following statements: if control0 is used as l3control interface then only first of three vmnics on VSM VM is used; if mgmt0 is used as l3control interface then only second of three vmnics on VSM VM is used; third vmnic is not utilized when l3control mode is used but interface must be present on VSM VM? [Shankar] mgmt0 interface is used for VSM's management and also for talking to the vCenter. So there will always be a use for this interface. If you choose control0 for the l3 control, then the 1st interface (control0 interface), will be used to talk to the VEMs. mgmt0 will be used to talk to the vCenter and for VSM management. If you choose mgmt0 for the l3 control, then the 2nd interface (mgmt0 interface), will talk to the VEMs apart from talking to the vCenter etc. So the 3rd interface is never used in the L3 mode, but is necessary for the VSM to function correctly Thanks, Shankar ... View more

Please get these from the VSM: - show module - show int eth3/8 - show run int eth3/8 For some reason, VLAN 5 is missing from your uplink interface (Eth3/8): ~ # vemcmd show port vlans                           Native  VLAN   Allowed   LTL   VSM Port  Mode    VLAN    State* Vlans    24     Eth3/8   T          1   FWD    1   <<<<<    49      Veth1   A          1   FWD    1    50      Veth2   A          1   FWD    1    51      Veth3   A          5   FWD    5 Also, get 'vemcmd show port vsm' from the ESX host Thanks, Shankar ... View more

Hi Yoed, If the configuration is correct, the problem could be due to CSCuf65032. Please get the following: - esxcfg-vmknic -l - esxcfg-nics -l Indicate which vmk and vmnics are being used for the vSwitch in question. Thanks, Shankar ... View more