Specifications

Clusters
persistence method and the “fallback” persistence method by dragging and dropping as well. As indicated
previously, with “fallback persistence” Equalizer provides a secondary option where if, for example, a cookie
response is not received, a secondary, or “fallback” option such as Source IP can be used.
The cookie scheme specifies the format of the cookie to be used for the cluster as an integer between 0 and 2
(default is 2).
Cookie 0:Cluster IP/Port, Server IP/Port
Constructs a cookie which will be named in such a way
that so as long as the cluster maintains the same IP
address, servers can be added to and removed from
the cluster without invalidating all of the existing
cookies. This cookie stores the cluster IP and
port, and the server IP and port.
Cookie 1:Cluster IP, Server IP /Port
Constructs a cookie which will be valid across all
clusters with the same IP address (not port specific). A
requirement for this to be useful is that all clusters on
that IP address share the same set of servers. This
cookie stores the Cluster IP, and Server IP and
port.
Cookie 2:Cluster IP, Server IP
Constructs a cookie which will be valid across all
clusters with the same IP address (using any port),
and the same server within those clusters (with the
server using any port). A requirement for this to be
useful is that all clusters on that IP address share the
same set of servers. This cookie encodes the
Cluster IP and Server IP.
Source IP
The Source IP address of the server will be embedded
in the response header back to the client.
Cookie Parameters
The Cookie Parameters pane will expand if a cookie scheme is enabled.
Cookie age
The Cookie age sets the time, in seconds, over which the client browser
maintains the cookie (“0” means the cookie never expires). After the
specified number of seconds have elapsed, the browser deletes the cookie
and any subsequent client requests will be handled by Equalizer’s load-
balancing algorithms
Cookie path
If a Cookie Path is specified, Equalizer honors cookies in a client
requests only when the path component of the request URI has the same
prefix as that of the specified Cookie Path. For example, if the cookie
path is /store/, Equalizer presents the cookie to the server only if the
request URI includes a path such as /store/ mypage.html.
Cookie Domain -
If a cookie domain is specified, then Equalizer will honor cookies in client
requests only if the server’s host name is within the specified domain. For
example, if the cookie domain is coyotepoint.com, then Equalizer will only
present the cookie to servers in the coyotepoint.com domain (for example,
www.coyotepoint.com or my.coyotepoint.com). Wildcards are not
supported in the cookie domain.
Cookie Generation -
A value added to cookies when the cookie scheme is 2. In order for cookies
to be valid, the specified Cookie Generation must match the equivalent
292
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.