Configuring Scripts For Health Monitoring Probes - Cisco catalyst 6500 series Configuration Note

Configuring Scripts for Health Monitoring Probes

•
•
If you decide to modify the script or the command line arguments while a script task command is
Note
running, you must stop the task using the no script task command and then rerun the task.
Configuring Scripts for Health Monitoring Probes
The CSM supports several specific types of health probes, such as HTTP health probes, TCP health
probes, and ICMP health probes when you need to use a diverse set of applications and health probes to
administer your network. The basic health probe types supported in the current CSM software release
often do not support the specific probing behavior that your network requires. To support a more flexible
health-probing functionality, the CSM now allows you to upload and execute TCL scripts on the CSM.
(See the
You can create a script probe that the CSM periodically executes for each real server in any server farm
associated with a probe. Depending upon the exit code of such a script, the real server is considered
healthy, suspect, or failed. Probe scripts test the health of a real server by creating a network connection
to the server, sending data to the server, and checking the response. The flexibility of this TCL scripting
environment makes the available probing functions possible.
Catalyst 6500 Series Content Switching Module Configuration Note
10-10
Use a different task ID.
Run the no script task id command first, and then retype the command for that script.
"Configuring TCL Scripts" section on page
Chapter 10
10-1.)
Configuring CSM Scripts
OL-4612-01