- Tier-1 is in Active/Standby setup (Edge cluster is associated with this Tier-1) with stateful services being used
- Same Edges are also used in the Active/Active configuration on the Tier-0
- You are seeing uneven traffic between both uplinks of the ESXi host where Edge VM is present
- Two TEP interfaces for Edges and Hosts, multiple tunnels are formed between Host TEPs and Edge TEPs
VMware NSX
- On a distributed network using Edge Transport Nodes, traffic for stateful services is not load balanced across all uplinks for a given flow because it must be processed by a single, active Edge TEP (Tunnel Endpoint) to maintain the session state.
- Uneven uplink usage on ESXi hosts supporting NSX Edge VMs with multiple TEPs and Active/Standby Tier-1 Gateways is a common scenario, especially with stateful services.
- In a multi-TEP configuration, the Edge maps traffic for overlay segment to individual TEPs
- For stateful services like a firewall, NAT, or load balancer, every packet belonging to the same flow must be sent through the same logical service instance
- This unevenness arises due to how traffic is handled in an Active/Standby configuration of Tier-1 Gateway and the nature of stateful services.
- Load balancing at the physical uplink level typically uses stateless policies, such as hashing based on source/destination IP and port. For stateful services, this approach is not suitable because it cannot guarantee that all packets from a single session will arrive at the correct active Edge Node.
- While TEP traffic can be load balanced for stateless services, stateful services specifically require session persistence, which is maintained by ensuring that all packets belonging to a flow are processed by the same active Edge TEP instance.