On the Advanced page, configure the following settings: Pool: Select the server pool that you created previously.Load balanced applications are accessed by accessing the VIP address. FQDN or IPv4 Address: IP Address of the VIP for the virtual server.This example shows the System-HTTP type for a web application. Application Profile: Use the application profile pull-down menu to select how the virtual service will listen for client requests.Existing concurrent connections will be terminated, and the virtual service will be unassociated from all Service Engines. When disabled (red icon), the virtual service will not accept any new connections.When enabled (green icon), the virtual service will accept and process traffic normally.Enabled: The toggle icon enables (green) and disables (red) the virtual service.To create a new Virtual Service, navigate to Applications > Virtual Services > Create Virtual Service > Advanced Setup and configure the following settings: A virtual service advertises an IP address and ports to the external world and listens for client traffic. Virtual services are the core of the NSX load balancing and proxy functionality. Port number if any custom port/service port is being used.Add the workload/servers that will be part of this pool.Add Active Monitor and add the health monitor that created previously.Persistence: Select the persistence profile that you created previously.To create a new server pool, navigate to Applications > Pools and click CREATE POOL. To learn more about the supported configuration parameters in a health monitor profile, see the Avi Networks documentation.Ī Server Pool has a list of servers that must be load balanced. To create a new health monitor profile, navigate to Templates > Profiles > Health Monitors and click Create.
NSX ALB health monitor is explained in greater detail in the NSX ALB documentation. If a back-end server has gone bad, the load balancer doesn’t forward any traffic to that server and ensures that client computers always get connected to healthy servers. Health monitors are used by load balancers to check if the back-end servers in the server pool are healthy or not. To learn more about this, see the Avi documentation on HTTP Cookie Persistence Note: Cookie-based persistence is the most commonly used mechanism when dealing with web applications. Before configuring the timeout value, consult your application owner to understand the ideal timeout value for client connections. A value of ‘0’ disables persistence and allows new connections to be load balanced to a new server immediately. To learn more about persistence profile type, see the NSX ALB Documentation.Įnter the number of minutes to preserve the client’s IP address in the Persistence Timeout field. Supported types are Client IP Address, HTTP Cookie, App Cookie, HTTP Custom Header, and TLS. To create a new persistence profile, log in to the Avi Controller UI and navigate to Templates > Profiles > Persistence, and click Create. To know more about persistence profiles in NSX ALB, refer to the Avi documentation. Enabling a persistence profile ensures the client will reconnect to the same server every time, or at least for a desired duration of time. Service Engines are shared among Virtual Services, CPU/Memory reservations can be configured on the service engine VMs for guaranteed performance.Ī persistence profile controls the settings that dictate how long a client will stay connected to one of the servers from a pool of load-balanced servers. To know more about the charges, see VMware Cloud on AWS Pricing Guide. Public IPs are chargeable in VMware Cloud. Public IPs are needed per DNS virtual service VIP. To learn more about NSX ALB high availability, refer to the Avi Networks documentation.
Service Engines must be deployed in N+M mode for high availability.