Operational Defect Database
BugZero updated this defect 51 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 97120
Addressing Common NSX Underlying Infrastructure Connectivity Issues
Last update date:
3/29/2024
Affected products:
NSX-T
Affected releases:
4.x2.53.x
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Inconsistent configurations in the underlying network infrastructure can cause connectivity issues. The goal of this document is to provide a checklist to easily identify and fix these configuration issues.
Resolution
Checklist VLAN config should match on segment/Edge logical uplinks, DVS uplinks, TOR Check VLAN config on the TOR connected to the physical NIC of the DVS uplink which provides connectivity to the Tier0 uplinkCheck DVS uplink config: Configure VLAN Tagging on a Distributed Port Group or Distributed Port Usually the DVS port group corresponding to Tier0 uplinks has a trunk range as multiple uplinks with different VLANs are often pinned to the same edge nic.Check NSX Edge Tier0 uplink VLAN: Create a Tier-0 Uplink Segment Consistent MTUs setting on LRPs (logical router ports), VDS, TOR Check MTU setting on the TOR interface connected to the physical NIC of the DVS uplink which provides connectivity to the Tier0 uplinkVDS MTU setting: Enable Jumbo Frames on a vSphere Distributed SwitchNSX MTU guidance: Guidance to Set Maximum Transmission Unit RPF setting on NSX Edge uplinks Ideally, asymmetric routing/forwarding is not recommended and therefore RPF is set to Strict mode on Tier0 uplinks.For symmetric routing configuration, please ensure that the configuration between Tier 0 and northbound routers is such that the same set of prefixes are advertised from each edge node within a Tier0 Gateway on a given site. Also, the same set of prefixes must be learned from TORs on all Edge nodes of a Tier0 Gateway on a given site.Asymmetric routing can happen when different BGP filters are applied on different nodes towards northbound neighbors in either direction leading to different routes getting advertised from different Edge nodes or if Edge nodes of a Tier0 Gateway have different BGP neighbors and learn/advertise different prefixes. Please check the BGP route maps to ensure that this is not the case. For Federation environments with Primary/Secondary site design, advertise longer AS paths for BGP advertisements on secondary site BGP neighbors to resolve asymmetric forwarding.After evaluating the above mentioned, if you still need asymmetric forwarding in your environment, please change the Tier0 uplink RPF setting to None. TEP VLAN mismatch Ensure that the VLAN configured on TOR matches the VLAN configured on the NSX side for overlay traffic. Federation RTEP VLAN mismatch Ensure consistent VLAN setting for RTEP and the VLAN ID on the underlay router connected to this RTEP: Configure Edge Nodes for Stretched Networking Edge connectivity issues after vmotion Set DRS rules as described in the following KB article: NSX-T Edge vMotion best practices (88034)Ensure VLAN/MTU config on TORs where the Edge may be vMotioned is consistent. Define the DRS vm/host rules such that the underlying hosts are on the same L2 domain and that the BGP/OSPF neighbors or static route next hops defined on Tier0 are reachable from all the hosts where the Edge may be vmotioned.
