Some VLANs not showing in NSX-T bridge summary

Products

• VMware NSX Networking

Issue/Introduction

Symptoms:

• You have an NSX-T version < 3.2.2
• Traffic is being dropped on some vlans on an edge bridge.
• Checking the edge /var/log/syslog.log, you can see messages similar to the below indicating that two bridge endpoints with duplicate vlan ids are being pushed to the edge node:

<edge-name> NSX 9748 SWITCHING [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="lswitch" tname="dp-ipc31" level="WARN"] lswitch <uuid> is also using VLAN 3265 on device bond-EDGEBMS-MGMT-PIAAS-NVDS
<edge-name> NSX 9748 FABRIC [nsx@6876 comp="nsx-edge" subcomp="datapathd" s2comp="dpc-pb" tname="dp-ipc31" level="ERROR" errorCode="EDG0400171"] dpc_create_vlan_lswitch failed to create lswitch <uuid>

Environment

VMware NSX-T Data Center

Cause

When 2 bridge endpoints associated with 2 separate overlay segments tries to get associated with the same bridge/edge nodes (they may use same bridge-profile or may use different bridge profiles but both of them are associated with the same edge cluster) using the same VLAN ID, and when such configuration is pushed to an edge node, the edge node cannot process any subsequent configuration changes in the edge bridge profile.

Resolution

To prevent such configuration to be pushed and realized on the edge nodes, a validation workflow has been introduced from 3.2.2 onwards which will throw an error on that specific segment and the segment will be in 'Failed' state on the NSX-T Manager UI when such configuration are made to a segment.
Example error would be: 'There already exists a BridgeEndpoint on same edgeNodes [TransportNode/cd82cf10-9485-4aef-a46b-aef24ad18f09] with same vlan-transportzone PolicyTransportZone/f4a35306-d9fd-43e7-a729-748492aec0c2 and vlanId 3265'

This will prevent such configuration to be pushed and get realized on the edge nodes.

The is resolved in NSX-T 3.2.2 and 4.0.0 available at VMware Downloads.

Workaround:
Create a bridge profile and move all segments (except those with duplicate VLANs) from the existing bridge profile to the new bridge profile.