This section covers the following topics: SE Data Plane Architecture and Packet Flow Change VRF Setting for NSX Advanced Load Balancer SE's Management Network VRF Support for Service Engine Deployment on Bare-Metal Servers 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 Avi Load Balancer Service Engine (SE). Source NAT for Application IdentificationThe source IP address used by Avi 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 Avi Load Balancer Service Engine (SE) and destination servers are translated using source NAT (SNAT). Avi Load Balancer uses SNAT to translate the source IP address of the connection from the client address into the IP address of the SE. SE Data Plane Architecture and Packet FlowThe Data Plane Development Kit (DPDK) comprises a set of libraries that boosts packet processing in data plane applications. Change VRF Context Setting for SE Management NetworkThe option to change the VRF context setting is available on the Avi Load Balancer UI. VRF Support for Service Engine Deployment on Bare-Metal ServersAvi Load Balancer Service Engine data interfaces can be assigned to multiple Virtual Routing and Forwarding Context (VRFs). Parent topic: Data Plane Networking
