Automatic Cluster Responders
The most common use of a responder is to change the default match rule behavior when no server
pools are available in a cluster. By default, every HTTP and HTTPS cluster is created with a
Default
match rule that does not specify a Responder -- thus, if all the server pools in the
Default
match
rule are down, Equalizer drops the client connection to the cluster.
In order to change the default behavior and supply a “sorry page” or redirect for a cluster, you
need to add a new match rule that:
l
matches any incoming request
l
selects the server pool specified
l
has a
Sorry Server
Responder selected
For example, let’s say you have two Responders defined and there is an existing cluster that you would like to redirect to
when no server pools in the cluster are available. To accomplish this, we need to create a new Responder
and then add a match rule to the cluster:
1. Verify that you are logged into the GUI. If not, log in as described in
2. Select the
Load Balance
configuration tab if it is not already selected.
3. Right click on
Responder
on the left navigational pane and select
AddResponder
. The
Add New
Responder
dialog appears.
4. Type
Sorry_Example
into the
Name
field and select
Sorry Server
.
5. Type the HTML content for the page to display into the text box that appears, as shown in
the following example.:
6. Click
Commit
to save the new Responder.
7. Right-click on the name of the cluster for which you want to display the sorry page in the
left frame and select
Add Match Rule
.
8. Refer to
on page 404 to configure the match rule. Leave the match
rule
expression
set to the default [any()] -- the rule will match all incoming requests.
Note
- The Responder will only be used if none of the server instances in the server pool is available.
486
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
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: ......