Fortinet FortiWAN - Virtual Server & Server Load Balancing

Virtual Server & Server Load Balancing Load Balancing & Fault Tolerance
Auto Routing Settings
Policies
Label Algorithm Parameter
WAN5 Fixed Tick the check box "5"
Default Policy By Downstream Traffic Tick the check boxes "1", "2", "3", "4" ...
Filters
Source Destination Service Routing Policy Fail-Over
Any Address WAN Any WAN5 Tunnel:
Branch2-HQ
Any Address WAN Any Default Policy No-Action
See also
Tunnel Routing
How the Tunnel Routing Works
Tunnel Routing - Setting
How to set up routing rules for Tunnel Routing
Tunnel Routing - Benchmark
Virtual Server & Server Load Balancing
Virtual Server is a method for single gateway machine to act as multiple servers while the real servers sit inside
corporate network to process requests passed in from the gateway machine. Inbound traffic does not have to know
where the real servers are, or whether there are just one or many servers. This method prevents direct access by users
and therefore increases security and flexibility.
FortiWAN has built in virtual server and is capable of supporting various virtual server mapping methods. For example,
different public IP addresses can be mapped to various real servers in LAN or DMZ. Or ports can be mapped to public
IP address on different servers.
Virtual server are configured by designating and adjusting virtual server rules. Each rule specifies a mapping condition.
It maps WAN IP address and a service (port or ports) to an internal server IP. The order of virtual server rules is like any
other rule tables in FortiWAN as it also uses the “first match scheme”, viz. the first rule of request matched is the rule
to take effect.
FortiWAN Handbook
Fortinet Technologies Inc.
163