This section covers the topics related to routing. What to read next Static Route Support for VIP and SNAT IP ReachabilityA static route is required on the next-hop router through which back end servers are connected to their NSX Advanced Load Balancer Service Engine (SE). Outbound NAT Configuration on NSX Advanced Load Balancer Service EngineThis section explains the NAT feature on NSX Advanced Load Balancer Service Engine. Source NAT for Application IdentificationThe source IP address used by NSX Advanced Load Balancer SEs for server back end connections can be overridden through an explicit user-specified address (Source NAT (SNAT) IP address). SNAT Source Port ExhaustionThe connections between an NSX Advanced Load Balancer Service Engine (SE) and destination servers are translated using source NAT (SNAT). NSX Advanced Load Balancer uses SNAT to translate the source IP address of the connection from the client address into the IP address of the SE. TCP Transparent Proxy SupportTransparent TCP proxy can also be called routed mode or default gateway mode. In this mode, servers point to the Service Engine’s IP address as their default gateway, mitigating the requirement for the Service Engine to Source NAT (SNAT) traffic sent to the destination servers. Proxy Protocol SupportThis section explains the Proxy protocol support for the NSX Advanced Load Balancer. Autoscale Service EnginesNSX Advanced Load Balancer SEs can run into CPU, memory, or PPS resource exhaustion while performing application delivery tasks. To increase the capacity of a load-balanced virtual service, NSX Advanced Load Balancer needs to increase the resources dedicated to the virtual service. Enable a Virtual Service VIP on All InterfacesThis section describes how to enable a virtual service VIP. Parent topic: Data Plane Networking
