The Virtual Server

The virtual server functions as a public face to the client for the services the client wishes to access. The client accesses a service by directing service requests to the Virtual IP (VIP) address configured on the virtual server.

Before enabling a virtual server you must name it, associate it with a server farm, configure the VIP, and configure the source NAT pool. The source address is natted to a source NAT pool entry before egressing the router. Optionally, you can restrict access to the virtual server to specified clients, by specifying the sticky type.

You must configure a virtual server with a VIP. The same IP address can be used for the VIP on multiple virtual servers provided a different port is specified for each VIP.

In cases where there is only one load balancing decision made for this client to virtual server for all TCP/UDP connections, the “match source-port any” binding mode allows Server Load Balancing (SLB) connections through the virtual server to create a single binding that will match any source port the client uses destined to the same virtual server VIP address and UDP/TCP port. Match source port any is only supported in an IPv4 context. Configure the “match source-port any” binding mode using the binding match source-port command.