Maximum Connections Limits, Responders, and Hot Spares
When a maximum connections limit is set on all the servers in a cluster, it is often desirable to
define either a responder or a hot spare server for the cluster, so that any attempted connections
to the cluster that occur after the
Maximum Reused Connections
limit has been reached are
directed to the responder or hot spare instead of being refused or sent to the server anyway
because of a persistent connection.
In general, a Responder is easier to configure than setting up a separate server as a hot spare,
since the responder runs on Equalizer. However, while Responders are capable of returning only a
single HTML page, a hot spare can be configured to return multiple HTML pages and images. See
on page 480for information on configuring a responder.
To use a hot spare, you would usually configure it on Equalizer as follows:
1. Set
Maximum Reused Connections
to zero (0), so that all connection requests sent to the
hot spare are accepted.
2. Enable the
Hot Spare
flag. This specifies that any requests refused by all the other server
instances in a server pool because they reached their
Maximum Reused Connections
limit
(or are down) will be forwarded to the hot spare server.
3. Enable the
Dont Persist
flag so that connections made to the hot spare don’t persist. Each
connection to the cluster must first be load balanced amongst the other servers in the
cluster and only go to the hot spare if all the other servers have reached their
Maximum
Reused Connections
limit.
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
All Rights Reserved.
465
Equalizer Administration Guide
Summary of Contents for Equalizer GX Series
Page 18: ......
Page 32: ...Overview 32 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 42: ......
Page 52: ......
Page 64: ......
Page 72: ......
Page 76: ......
Page 228: ......
Page 238: ......
Page 476: ......
Page 492: ......
Page 530: ......
Page 614: ......
Page 626: ......
Page 638: ......
Page 678: ......
Page 732: ...Using SNMP Traps 732 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 754: ......
Page 790: ......
Page 804: ......
Page 842: ......
Page 866: ......