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
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.
Testing ACV Using the CLI
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:
eqcli sp-
spname
>
test acv
12020289: There are no server instances in the server pool to test.
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
All Rights Reserved.
445
Equalizer Administration Guide
Summary of Contents for Equalizer GX Series
Page 18: ......
Page 32: ...Overview 32 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 42: ......
Page 52: ......
Page 64: ......
Page 72: ......
Page 76: ......
Page 228: ......
Page 238: ......
Page 476: ......
Page 492: ......
Page 530: ......
Page 614: ......
Page 626: ......
Page 638: ......
Page 678: ......
Page 732: ...Using SNMP Traps 732 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 754: ......
Page 790: ......
Page 804: ......
Page 842: ......
Page 866: ......