
Working in the CLI
Cluster and Match Rule Command Notes
l When creating a cluster, the list of available parameters depends on the protocol selected for the cluster.
As a result, the proto parameter must be specified
before
any other cluster parameters on the command
line.
l Layer 7 clusters can have one or more match rules that override the options set on the cluster when the
expression specified in the match rule matches an incoming client request. (Layer 4 clusters do
not
support
match rules.)
l The cluster flags supported for a particular cluster depend on the setting of the cluster proto parameter, as
shown in the table below.
Cluster Flags
A flag may be turned off by prefixing with "!".
Cluster 'proto' Flag Description
tcp and udp
dsr
Enables“direct server return" -- servers respond directly to clients
rather than through Equalizer.
ics
Enables“inter-cluster sticky” -- Layer 4 persistence is preserved
across clusters and server ports.
spoof
Disables Source NAT (SNAT) -- the client IP addressis used as
the source IP in packets sent to servers.
http and https
abort_server
Close server connections without waiting.
always
Always insert a cookie into server responses.
client_ip
Include the client IP address in headers.
compress
Compressserver responses. (E650GX Only)
ignore_case
Do not consider case when evaluating a match rule.
no_header_rewrite
Do not rewrite Location headersin server responses.
once_only
Evaluate the first set of headers in a client connection only.
persist
Insert a cookie in server responses if the server did not.
spoof
Use the client IP as source IP in packets sent to servers.
tcp_mux
EnablesTCP multiplexing for a cluster. TCP multiplexing must also
be enabled on at least one server instance in the server pool
assigned to the cluster (or one of its match rules). See the section.
150
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
Comentarios a estos manuales