
Server Pools and Server Instances
The CLI is now in the aggregate server instance context “sv01,sv02,sv03” -- only the first three characters of
which are displayed in the command line. To see the entire context name, use the context command:
eqcli sp-sp01-si-sv0*> context
The context is “sv01,sv02,sv03”.
eqcli sp-sp01-si-sv0*>
In an aggregate server instance context, the show command will display the configuration of all the server
instances in the context.
Testing ACV on a Server Instance
A test function is available where you can test the functionality of an ACV probe. It is performed on a server pool
that must have server instances configured in the pool. All the uncommitted CLI parameters are used when
running the test, including the ACV query strings, response strings, timeouts, etc. The idea is to test the proposed
configuration before it is committed.
You have the option of specifying a server instance to test or you can test all of the server instances in a server
pool. A response is received indicating whether probing is successful or if it fails.
In the example below, a server instance is being tested. Enter the following:
eqcli sp-spname> test acv si name
[si name] ACV probe successful!
If you do not specify a server instance in a server pool, all of the server instances will be tested. For example:
eqcli sp-spname> test acv
[si name] ACV probe successful
[si name] ACV probe failed.
[si name] ACV probe successful
If no server instances are attached to the server pool you will receive a message:
240
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
Comentarios a estos manuales