This section covers the following topics: Static Route Support for VIP and SNAT IP Reachability NAT Configuration on NSX Advanced Load Balancer Service Engine Source NAT for Application Identification SNAT Source Port Exhaustion TCP Transparent Proxy Support Autoscale Service Engines 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). NAT Configuration on NSX Advanced Load Balancer Service EngineWhen new application servers are deployed, the servers need external connectivity for manageability. 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 ExhaustionTypically, 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. Autoscale Service EnginesNSX Advanced Load Balancer Service Engines 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. Parent topic: SE Advanced Networking
