get logical-router interfaces .interface : <UUID>ifuid : <NNN>VRF : <UUID>name : <gateway>Fwd-mode : IPV4_ONLYmode : lifport-type : serviceIP/Mask : <IP/Mask>MAC : <MAC address>VLAN : <VLAN ID>LS port : <UUID>urpf-mode : STRICT_MODEadmin : upop_state : upMTU : 1500arp_proxy :
interface : <UUID>ifuid : <NNN>VRF : <UUID>name : <gateway>Fwd-mode : IPV4_ONLYmode : lifport-type : serviceIP/Mask : <IP/Mask>MAC : <MAC address>VLAN : <VLAN ID>LS port : <UUID>urpf-mode : STRICT_MODEadmin : upop_state : upMTU : 1500arp_proxy :
get host-switch vlan-table .<VLAN ID>get host-switch vlan-table , the interface is not functioning.VMware NSX-T
VMware NSX
An Edge node can have only 1 VLAN uplink/service interface per VLAN ID and vNIC.
Since NSX-T 3.1 validation have been implemented to prevent multiple VLAN interfaces of the same VLAN.
However, it's been reported that the validation was somehow slipped through and multiple VLAN interfaces of the same VLAN could be configured on an Edge node.
In such a case, only one of the interfaces works fine.
Currently, there is no resolution.
If you find multiple VLAN interfaces of the same VLAN is configured on an Edge node, distribute the gateways to another Edge node.
After you make sure only 1 interfaces of the VLAN is configured on an Edge node, disable/enable the interface to make sure it is functioning.
To prevent such a configuration, if you plan to configure multiple interfaces of the same VLAN within an Edge cluster, first distribute gateways and make sure the gateways do not share the same Edge node, and then create VLAN interfaces.