Specifications

Working with Virtual Clusters
Equalizer Installation and Administration Guide 69
The port defined for a server in the cluster for which a port range is defined indicates the port
on the server that starts the range of ports to be opened. See Step 6 on page 89, under “Adding a
Server to a Cluster”
7. For all cluster protocols, choose the appropriate load-balancing policy to be used by this
cluster. Choose from round robin (default), static weight, adaptive, fastest response, least
connections, or server agent. For more information, refer to “Configuring a Cluster’s Load-
Balancing Options” on page 74.
8. Enter values for:
• responsiveness sets the load-balancing response setting for this cluster. For more
information, refer to “Configuring a Cluster’s Load-Balancing Options” on page 74.
• ACV probe is the active content verification probe string. For more information, refer to
“Using Active Content Verification (ACV)” on page 83.
• ACV response is the active content verification response string. For more information,
refer to “Using Active Content Verification (ACV)” on page 83.
• server agent port is the port used to contact server agents. The default port is 1510. See
Appendix A, ”Using Server Agents” for more information.
9. Set the flags:
• disable causes the cluster to be unavailable. Use this flag when you are experimenting
with a cluster’s settings and you do not want the cluster to listen for requests.
• server agent has Equalizer use server agents gather performance statistics from the
servers in the cluster. If you enable this option, you must run Server Agent daemons on
each server in the cluster and must specify a value in server agent port (default is port
1510). See Appendix A, ”Using Server Agents” for more information about configuring
server agents.
• ignore case causes all of the cluster’s match rules to use case insensitive comparisons
when this box is checked. You can override this setting by changing ignore case for a
specific match rule.
10. For HTTP and HTTPS clusters, choose from the following options:
• spoof causes Equalizer to spoof the client IP address when Equalizer routes a request to a
server in a virtual cluster; that is, the IP address of the client is sent to the server, not the
IP address of the Equalizer. This option is on by default. If you disable this option, the
server receiving the request will see the Equalizer’s address as the client address because
the TCP connection to the client is terminated when the request is routed. When spoof is
enabled, the servers in the cluster must use the Equalizer as the default gateway for
routing.
• persist instructs Equalizer to use cookies to maintain a persistent session between a client
and a particular server. This option is on by default. Equalizer “stuffs” a cookie into the
server’s response header on its way back to the client. This cookie uniquely identifies the
server to which the client was just connected. With persist
enabled, Equalizer routes only
the first request from
a client
using load balancing criteria; subsequent client requests are
Note – Old configuration files will still work—the port section for clusters will be interpreted
as having a port range of start port being the same as end port. The port section will remain
the same in the configuration file until the cluster is changed, at which point start_port and
end_port will be written to the file.