Fortinet 5.0 Patch 6 - page 70

Fortinet 70 FortiWeb 5.0 Patch 6 Administration Guide
Figure 14:Example network topology: transparent proxy mode with configuration
synchronization and external HA via FortiADC
Unlike with FortiWeb HA, with external HA, that HA device must itself detect when a FortiWeb
has failed in order to redirect the traffic stream. (FortiWeb has no way of actively notifying the
external HA device.) To monitor the live paths through your FortiWebs, you could configure your
HA device to poll either:
• a back-end web server, or
• an IP on each FortiWeb bridge (V-zone)
See also
•Fail-to-wire for power loss/reboots
•Topology for reverse proxy mode
•Topology for either of the transparent modes
•Configuring a high availability (HA) FortiWeb cluster
•HA heartbeat & synchronization
•Replicating the configuration without FortiWeb HA (external HA)
If you need to replicate the FortiWeb configuration without HA (i.e. no load balancing and no
failover), you can achieve this by using configuration synchronization. This has no special
topology requirement, except that synchronized FortiWebs should be placed in identical
topologies. For more information, see “Replicating the configuration without FortiWeb HA
(external HA)” on page 107.