This topic gives details related to SE data plane, VRFs, routing, and so on. What to read next VRFsThis section covers the following topics: IP RoutingThis section covers the topics related to routing. BGPBGP (Border Gateway Protocol) is primarily used in Avi Load Balancer to advertise VIP to routers in private clouds. It can also be configured to support dynamic routing through learning and advertising routes to peers. Configuring Networks for SEs and Virtual IPsThis section describes the IP address allocation and the steps to configure IP address pools. Sizing Service EnginesAvi Load Balancer publishes minimum and recommended resource requirements for Avi Load Balancer SEs. This section provides details on sizing. You can consult your Avi Load Balancer sales engineer for recommendations that are tailored to the exact requirements. Checking Service Engine Operation ModeThe following topic explains the CLI commands to check the operation mode for Service Engines. Per-App SE ModeThis section describes about per-app Service Engine (SE) mode. Connecting SE to Controllers in Isolated NetworkThis topic explains how SE-Controller communication can be established from Service Engines instantiated on a network isolated from the network of the Controller nodes. SE Memory ConsumptionThis section discusses calculation of memory utilization within a Service Engine (SE) to estimate the number of concurrent connections or the amount of memory that can be allocated to features such as HTTP caching. Connection Refusals to Incoming Requests Observed on Avi Load Balancer Service EnginesThis section describes the resolution to the intermittent connection refusals observed on Service Engines, which correlate to higher traffic volume. X-Forwarded-For Header InsertionAvi Load Balancer Service Engines (SEs) source-NAT (SNAT) traffic is destined to servers, by default. Due to SNAT, logs on the application servers will show the layer 4 IP address of the SE rather than the original client’s IP address. Resetting PCAP TX Ring for Non-DPDK DeploymentThis section discusses the steps to enable and deactivate the PCAP tx_ring using Avi Load Balancer shell prompt. Configuring TSO, LRO, GRO, and RSSThis section explains the TSO, LRO, GRO, and RSS configuration process. Certificate Management Integration for Trust AnchorThis section explains the certificate management integration for trust anchor. Preserve Client IPThis section discusses the configuration and scope of preserve client IP address. Support for Jumbo Frames in Avi Load BalancerThis section explains the support for jumbo frames in Avi Load Balancer. Network ReachabilityFor a virtual service to be placed on an Avi Load Balancer Service Engine, the Avi Load Balancer Controller first looks for SEs with available capacity and network reachability to make a virtual service placement decision. Reachability means the Service Engine has access to the networks required per the configuration of the virtual service and its pool members. Migration of Service Engine PropertiesThis section lists some of the updates done to the CLI and API structure. Adding IP Address to Data NIC for Service EngineDuring a cloud deployment with Avi Load Balancer, once a Service Engine’s (SE) virtual machine (VM) is up and a data NIC is associated with the VM, an IP address is assigned to the data NIC. Run the following steps to assign an IP address to the data NIC of the Avi Load Balancer SE. Multiple Queues per DispatcherThis feature is introduced in SE DP DPDK mode to achieve higher PPS in environments where the size of the NIC queue is limited. Upper Limit for ARP Rate SettingThere is no upper limit for ARP (Address Resolution Protocol) rate setting on Avi Load Balancer Controller and Avi Load Balancer Service Engines. Rate limit for ARP setting controls the maximum number of ARP packets processed by Avi Load Balancer Controller and Service Engines. DSRThis section explains about direct server return on Avi Load Balancer.
