Load balancing : Load balancing among local servers : Distributing new sessions among your servers
 
Distributing new sessions among your servers
From the perspective of clients, it will appear as if they are connecting to a single server. This destination address, however, will actually be a virtual server on your FortiADC appliance.Once the appliance receives traffic at the virtual server’s IP address, it must apply changes such as decryption and content rewriting (if required) before using the virtual server’s selected session persistence and load balancing methods to distribute the packets to your pool of servers.
 
Unlike virtual IPs on FortiGate or virtual servers on FortiWeb, virtual servers on FortiADC are activated as soon as you configure them. You do not apply them by selecting them in a policy.
You do not specify an IP address for a layer 2 load balance virtual server. Instead of routing data for a specific destination, this type of server routes data from the specified network interface and port. The L2 Load Balance virtual server only routes client requests arriving at the specified interface and port.
 
If your L2 Load Balance virtual server is assigned a network interface that uses port 80 or 443, ensure that the HTTPS and HTTP administrative access options are not enabled for the interface.
For more information on these options, see “Configuring the physical network interfaces”
To configure a virtual server, first configure all profiles that it will use, then go to Server Load Balance > Virtual Servers.
 
See also
Virtual Server Summary widget
Virtual Server Network Throughput widget
Virtual Server Sessions widget