
Servers
Server Configuration Constraints
When configuring servers on Equalizer, you must observe the following constraints:
l In general, there must be no Layer 3 devices (e.g., such as a router) between a server and Equalizer in order
for health check probes to work correctly.
l Equalizer operation depends on reliable communication between Equalizer and the servers behind it. The
latency introduced by Layer 3 devices such as routers can, for example, result in connection time-outs even
when the server is available.
l If you require remote servers in your clusters, you must be very careful to configure network routes that
allow Equalizer and the server to communicate. It may also be necessary to reconfigure probe time-outs in
order to account for network latency.
An example of a configuration with both directly connected servers and remotely accessible servers is illustrated
in the diagram below.
The configuration shown above is an example of a single VLAN configuration, where Equalizer communicates with
all servers and clients via the same subnet. The example cluster shown above contains three servers, two on the
local 10.0.0.0 subnet, and one on another subnet.
In this example, a static route would be needed on Equalizer to forward all packets for the 172.16.0.0 network to
the gateway at 10.0.0.172. Similarly, the server at 172.16.0.33 would need a static route that forwards all traffic for
the 10.0.0.0 network through 172.16.0.10, the gateway address for the 10.0.0.0 network.
244
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
Kommentare zu diesen Handbüchern