
Working in the CLI
Cluster and Match Rule Commands
Each cluster has its own context and the settings available in the cluster’s context depends on the cluster’s proto
parameter -- this parameter must be specified first on the command line when creating a cluster. A Layer 7 cluster
may have one or more match rules associated with it, each with its own context. Cluster and match rule
commands are summarized in the tables below.
Using Cluster Commands in the Global Context
eqcli > cluster clname req_cmds : Create clname (req_cmds = * commands
below)
eqcli > cluster clname cmds ... : Modify clname (cmds = any commands
below)
eqcli > no cluster clname : Delete clname
eqcli > show cluster [clname] : Display all clusters or clname
eqcli > cluster clname : Change to the "cl-clname" context(see
below)
Using Cluster Commands in a Cluster Specific Context
For all Clusters:
eqcli cl-clname> *ip ip_addr : Cluster IP address
eqcli cl-clname> *proto
{http|https|tcp|udp}
: Protocol -- MUST SET proto FIRST
eqcli cl-clname> *port integer : Cluster port
eqcli cl-clname> show : Show the cluster configuration
eqcli cl-clname> stats : Display cluster statistics
For Layer 7Clusters:
eqcli cl-clname> age integer : Cookie age in seconds (0 [default]
to 31536000 -- one year)
eqcli cl-clname> clientto integer : Client connection timeout
eqcli cl-clname> compress_min integer : Minimum bytes to compress (0 to
1073741824 -- default 1024)
eqcli cl-clname> compress_types string : Mime types to compress
eqcli cl-clname> connto integer : Server connection timeout
eqcli cl-clname> custhdr string : Custom request header
eqcli cl-clname> domain string : Cookie domain
eqcli cl-clname> flags : Disable and enable flags
For Layer 7 Http Clusters:
{[!]always,[!]compress,
[!]disable,[!}allow_utf8
146
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
Comentários a estes Manuais