Cisco Explorer 4700 Installation Guide Page 243

  • Download
  • Add to my manuals
  • Print
  • Page
    / 648
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 242
6-41
Device Manager Guide, Cisco ACE 4700 Series Application Control Engine Appliance
OL-26645-02
Chapter 6 Configuring Real Servers and Server Farms
Configuring Health Monitoring
HTTP_PROBE_SCRIPT
HTTPCONTENT_PROBE
HTTPHEADER_PROBE
HTTPPROXY_PROBE
IMAP_PROBE
LDAP_PROBE
MAIL_PROBE
POP3_PROBE
PROBENOTICE_PROBE
RTSP_PROBE
SSL_PROBE_SCRIPT
These scripts are located in the probe: directory and are accessible in both the Admin and user contexts.
Note that the script files in the probe: directory are read-only, so you cannot copy or modify them.
However, you can copy files from the probe: directory. For more information, see the Administration
Guide, Cisco ACE Application Control Engine.
To load a script into memory on the ACE appliance and enable it for use, use the script file command.
For detailed information on uploading and executing Toolkit Command Language (TCL) scripts on the
ACE appliance, refer to the Server Load-Balancing Guide, Cisco ACE Application Control Engine.
Configuring Health Monitoring for Real Servers
To check the health and availability of a real server, the ACE appliance periodically sends a probe to the
real server. Depending on the server response, the ACE appliance determines whether to include the
server in its load-balancing decision.
Note You can configure the inband health monitoring feature and health probes to monitor the health of the
real servers in a server farm. When you do, both are required to keep a real server in service within a
server farm. If either feature detects a server is out of service, the ACE does not select the server for load
balancing. For more information on inband health monitoring, see the “Configuring Server Farms”
section on page 6-18.
Use this procedure to establish monitoring of real servers to determine their viability in load-balancing
decisions.
Procedure
Step 1 Choose Config > Virtual Contexts > context > Load Balancing > Health Monitoring. The Health
Monitoring table appears.
Step 2 Click Add to add a new health monitoring probe, or select an existing entry, and then click Edit to
modify it. The Health Monitoring screen appears.
Step 3 In the Name field, enter a name that identifies the probe and that associates the probe with the real server.
Valid entries are unquoted text strings with no spaces and a maximum of 64 characters.
Step 4 In the Type field, select the type of probe you want to use. The probe type determines what the probe
sends to the real server. See Table 6-9 for the types of probes and their descriptions.
Page view 242
1 ... 242 243 244 ... 648

Comments to this Manuals

No comments