Edge Segments Fail to Pin to Uplinks Using Named Teaming Policies
Article ID: 439912
Updated On:
Products
Issue/Introduction
In VMware NSX-T, when configuring Edge Transport Node segments to use specific uplinks via Named Teaming Policies, the logical switch traffic fails to pin to the assigned datapath interface (e.g., fp-eth1). Instead, traffic from multiple isolated segments silently falls back to the default uplink interface (e.g., fp-eth0).
Environment
4.x
Cause
The Named Teaming Policy string is mismatched or not uniformly defined across the Segment, Transport Zone, and Edge Uplink Profile. If the Edge Transport Node cannot locally resolve the exact policy name requested by the segment within its assigned Transport Zone and Uplink Profile, the NSX datapath silently falls back to the Uplink Profile's Default Teaming Policy to prevent a complete traffic drop.
Resolution
To enforce deterministic uplink pinning, the Named Teaming Policy string must match exactly across all three architectural layers and is case sensitive.
Navigate to System > Fabric > Profiles > Uplink Profiles.
Edit the Uplink Profile assigned to the Edge Transport Node.
Under the Teamings section, ensure the Named Teaming Policy is explicitly defined (e.g., Policy-Uplink2) and mapped to the desired physical Active Uplink.
Navigate to System > Fabric > Transport Zones.
Edit the VLAN Transport Zone associated with the affected segments.
In the Named Teaming Policy Names (or Uplink Teaming Policy Names) field, type the exact case sensitive string used in step 3 (e.g., Policy-Uplink2) and press Enter to add the tag. Save the configuration.
Navigate to Networking > Segments.
Edit the affected segment(s).
Expand the Advanced Configuration or Uplink Teaming Policy section.
Set the Uplink Teaming Policy strictly to the established string (e.g., Policy-Uplink2).
Authenticate to the Edge Transport Node CLI and run get logical-switches to verify the segment MAC tables are now correctly mapped to the intended fp-eth interface.
Note: Edge VMs must also have contiguous virtual network adapter mappings in vCenter, starting from Network Adapter 2 for fp-eth0, to ensure correct PCI-to-DPDK interface enumeration.)
Additional Information
Feedback
