Loading Scripts - Cisco catalyst 6500 series Configuration Note

Configuring TCL Scripts

Loading Scripts

Scripts are loaded onto the CSM through script files. A script file may contain zero, one, or more scripts.
Each script requires 128 KB of stack space. Because there can be a maximum of 50 health scripts, the
maximum stack space for script probes is 6.4 MB. Standalone scripts may also be running, which would
consume more stack space.
Scripts can be loaded from a TFTP server, bootflash, slot0, and other storage devices using the script
file [file-url] command.
This example shows how to load a script:
Router(config)# module csm 4
Router(config-module-csm)# script file tftp://192.168.1.1/httpProbe.test
The script name is either the filename of the script or a special name encoded within the script file. Each
script file may contain a number scripts in the same file. To run the script or create a health probe using
that script, you must refer to the script name, not the script file from which the script was loaded.
In order to identify each relevant script, each script must start with a line:
#!name = script_name
This example shows a master script file in which the scripts are bundled:
#!name = SCRIPT1
puts "this is script1"
!name = SCRIPT2
puts "this is script2"
This example shows how to find the scripts available in a master script file:
Router(config)# configure terminal
Router(config-t)# module csm 4
Router(config-module-csm)# script file tftp://192.168.1.1/script.master
Router(config-module-csm)# end
This example shows three scripts available from the script.master file:
Router(config)# show module csm 4 file tftp://192.168.1.1/script.master
RECURSIVE_TCL, file tftp://192.168.1.1/script.master
size = 304, load time = 03:49:36 UTC 03/26/93
ECHO_TCL, file tftp://192.168.1.1/script.master
size = 228, load time = 03:49:36 UTC 03/26/93
HTTP_PROBE, file tftp://192.168.1.1/script.master
size = 920, load time = 03:49:36 UTC 03/26/93
To show the contents of a loaded script file, use this command:
Router(config)# show module csm slot script full_file_URL code
One major difference between a script task and a script probe is that the execution of a health script is
scheduled by the health monitoring CSM module. These conditions apply:
•
•
•
Catalyst 6500 Series Content Switching Module Configuration Note
10-2
A script can be modified while a script probe is active. The changes are applied automatically in the
next script execution, and for command line arguments.
During probe configuration, a particular script is attached to the probe. If the script is unavailable at
that time, the probe executes with a null script. If this situation occurs, a warning flag is generated.
However, when the script is loaded again, the binding between the probe object and the script does
not run automatically. You must use the no script and script commands again to do the binding.
After a script is loaded it remains in the system and cannot be removed. You can modify a script by
changing a script, and then by entering the no script file and script file commands again.
Chapter 10 Configuring CSM Scripts
OL-4612-01