7-31
Cisco 4700 Series Application Control Engine Appliance Administration Guide
OL-11157-01
Chapter 7 Configuring Redundant ACE Appliances
Configuring Tracking and Failure Detection
Configuring a Probe on the Active Member for Host Tracking
Configure one or more probes on the active FT group member to track the health
of the gateway or host. For details about creating probes, see the
Cisco 4700
Series Application Control Engine Appliance Server Load-Balancing
Configuration Guide
. To associate an existing probe with a gateway or host for
tracking by the active member, use the
probe
command in FT track host
configuration mode. The syntax of this command is:
probe
name
priority
number
The keyword and arguments are:
•
name
—Identifier of an existing probe that you want to associate with a
gateway or host for tracking.
•
priority
number
—Specifies the priority of the probe sent by the active
member. Enter an integer from 0 to 255. The default is 0. Higher values
indicate higher priorities. Assign a priority value based on the relative
importance of the gateway or host that the probe is tracking. If the probe goes
down, the ACE decrements the priority of the FT group on the active member
by the value of the
number
argument. If the resulting priority of the FT group
on the active member is less than the priority of the FT group on the standby
member, a switchover occurs.
Note
If you remove a probe from the active FT group member configuration and you
have not configured a tracking priority for the FT group (see the
“Configuring a
Priority on the Active Member for Multiple Probes”
section), the ACE increments
the net FT group priority by the priority value of the deleted probe. You cannot
delete a probe from the running-configuration file if the ACE is using the probe
for tracking.
For example, enter:
host1/Admin(config-ft-track-host)#
probe TCP_PROBE1 priority 50
To remove the tracking probe from the active member, enter:
host1/Admin(config-ft-track-host)#
no probe TCP_PROBE1
