Feedback
|
Table Of Contents
Prerequisites for Cisco IOS Scripting with Tcl
Restrictions for Cisco IOS Scripting with Tcl
Information About Cisco IOS Scripting with Tcl
Tcl Shell for Cisco IOS Software
Custom Extensions in the Tcl Shell
SNMP MIB Custom Extensions in the Tcl Shell
How to Configure Cisco IOS Scripting with Tcl
Enabling the Tcl Shell and Using the CLI to Enter Commands
Using the Tcl Shell to Access SNMP MIB Objects
Running Predefined Tcl Scripts
Configuration Examples for Cisco IOS Scripting with Tcl
Example: Tcl Script Using the show interfaces Command
Example: Tcl Script for SMTP Support
Example: Tcl Script for SNMP MIB Access
Feature Information for Cisco IOS Scripting with Tcl
Cisco IOS Scripting with Tcl
First Published: July 28, 2003Last Updated: September 10, 2010The Cisco IOS Scripting with Tcl feature provides the ability to run Tool Command Language (Tcl) version 8.3.4 commands from the Cisco IOS command-line interface (CLI).
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Cisco IOS Scripting with Tcl" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Cisco IOS Scripting with Tcl
•
Restrictions for Cisco IOS Scripting with Tcl
•
Information About Cisco IOS Scripting with Tcl
•
How to Configure Cisco IOS Scripting with Tcl
•
Configuration Examples for Cisco IOS Scripting with Tcl
•
Feature Information for Cisco IOS Scripting with Tcl
Prerequisites for Cisco IOS Scripting with Tcl
•
Familiarity with Tcl programming and Cisco IOS commands is required.
•
Tcl commands can be executed from the Tcl configuration mode using the Cisco IOS CLI. Tcl configuration mode is accessed from privileged EXEC mode. Access to privileged EXEC mode should be managed by restricting access using the enable command password.
Restrictions for Cisco IOS Scripting with Tcl
•
If Cisco IOS configuration commands are used within the Tcl scripts, submode commands must be entered as quoted arguments on the same line as the configuration command.
•
Error messages are provided, but you must check that the Tcl script will run successfully because errors may cause the Tcl shell to run in an infinite loop.
CautionThe use of Tcl server sockets to listen to telnet and FTP ports (23 and 21 respectively) will preempt the normal handling of these ports in Cisco IOS software.
•
Table 1 lists Tcl commands and library calls that do not behave within Cisco IOS software as documented in standard Tcl documents.
Information About Cisco IOS Scripting with Tcl
To create and use Tcl scripts within Cisco IOS software, you should understand the following concepts:
•
Tcl Shell for Cisco IOS Software
Tcl Shell for Cisco IOS Software
The Cisco IOS Tcl shell was designed to allow customers to run Tcl commands directly from the Cisco IOS CLI prompt. Cisco IOS software does contain some subsystems such as Embedded Syslog Manager (ESM) and Interactive Voice Response (IVR) that use Tcl interpreters as part of their implementation. These subsystems have their own proprietary commands and keyword options that are not available in the Tcl shell.
Several methods have been developed for creating and running Tcl scripts within Cisco IOS software. A Tcl shell can be enabled, and Tcl commands can be entered line by line. After Tcl commands are entered, they are sent to a Tcl interpreter. If the commands are recognized as valid Tcl commands, the commands are executed and the results are sent to the TTY device. If a command is not a recognized Tcl command, it is sent to the Cisco IOS CLI parser. If the command is not a Tcl or Cisco IOS command, two error messages are displayed. A predefined Tcl script can be created outside of Cisco IOS software, transferred to flash or disk memory, and run within Cisco IOS software. It is also possible to create a Tcl script and precompile the code before running it under Cisco IOS software.
Multiple users on the same router can be in Tcl configuration mode at the same time without interference because each Tcl shell session launches a separate interpreter and Tcl server process. The TTY interface number served by each Tcl process is represented in the server process name and can be displayed using the show process CLI command.
The Tcl shell can be used to run Cisco IOS CLI EXEC commands within a Tcl script. Using the Tcl shell to run CLI commands allows customers to build menus to guide novice users through tasks, to automate repetitive tasks, and to create custom output for show commands.
Tcl Precompiler
The Cisco IOS Tcl implementation offers support for loading scripts that have been precompiled by the TclPro precompiler. Precompiled scripts allow a measure of security and consistency because they are obfuscated.
SNMP MIB Object Access
Designed to make access to Simple Network Management Protocol (SNMP) MIB objects easier, a set of UNIX-like SNMP commands has been created. The Tcl shell is enabled either manually or by using a Tcl script, and the new commands can be entered to allow you to perform specified get and set actions on MIB objects. To increase usability, the new commands have names similar to those used for UNIX SNMP access. To access the SNMP commands go to, "Using the Tcl Shell to Access SNMP MIB Objects" section.
Custom Extensions in the Tcl Shell
The Cisco IOS implementation of the Tcl shell contains some custom command extensions. These extensions operate only under Tcl configuration mode. Table 2 displays these command extensions.
SNMP MIB Custom Extensions in the Tcl Shell
The Cisco IOS implementation of the Tcl shell contains some custom command extensions for SNMP MIB object access. These extensions operate only under Tcl configuration mode. Table 3 displays these command extensions.
How to Configure Cisco IOS Scripting with Tcl
This section contains the following tasks:
•
Enabling the Tcl Shell and Using the CLI to Enter Commands (required)
•
Using the Tcl Shell to Access SNMP MIB Objects (optional)
•
Running Predefined Tcl Scripts (optional)
Enabling the Tcl Shell and Using the CLI to Enter Commands
Perform this task to enable the interactive Tcl shell and to enter Tcl commands line by line through the Cisco IOS CLI prompt. Optional steps include specifying a default location for encoding files and specifying an initialization script.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
scripting tcl encdir location-url
4.
scripting tcl init init-url
5.
scripting tcl low-memory bytes
6.
exit
7.
tclsh
8.
Enter the required Tcl command language syntax.
9.
ios_config "cmd" "cmd-option"
10.
socket -myaddr addr -myport port -myvrf vrf-table-name host port
11.
socket -server -myaddr addr -myvrf vrf-table-name port
12.
fconfigure channelname -remote [host port] -broadcast boolean vrf [vrf_table_name]
13.
udp_open -ipv6 port
14.
udp_peek sock buffersize
15.
exec "exec-cmd"
16.
exit
DETAILED STEPS
Command or Action PurposeStep 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
(Optional) Enters global configuration mode.
•
Perform Step 2 through Step 6 if you are using encoding files, an initialization script, or both.
Step 3
scripting tcl encdir location-url
Example:Router(config)# scripting tcl encdir tftp://10.18.117.23/enctcl/
(Optional) Specifies the default location of external encoding files used by the Tcl encoding command.
Step 4
scripting tcl init init-url
Example:Router(config)# scripting tcl init ftp://user:password@172.17.40.3/tclscript/initf iles3.tcl
(Optional) Specifies an initialization script to run when the Tcl shell is enabled.
Step 5
scripting tcl low-memory bytes
Example:Router(config)# scripting tcl low-memory 33117513
(Optional) Specifies a low water memory mark for free memory for Tcl-based applications. The memory threshold can be set anywhere between 0-4294967295 bytes.
Note
If minimum free RAM drops below this threshold, TCL aborts the current script. This prevents the Tcl interpreter from allocating too much RAM and crashing the router.
Step 6
exit
Example:Router(config)# exit
(Optional) Exits global configuration mode and returns to privileged EXEC mode.
Step 7
tclsh
Example:Router# tclsh
Enables the interactive Tcl shell and enters Tcl configuration mode.
Step 8
Enter the required Tcl command language syntax.
Example:Router(tcl)# proc get_bri {}
Commands entered in Tcl configuration mode are sent first to the interactive Tcl interpreter. If the command is not a valid Tcl command, it is then sent to the CLI parser.
Step 9
ios_config "cmd" "cmd-option"
Example:Router(tcl)# ios_config "interface Ethernet 2/0" "no keepalive"
(Optional) Modifies the router configuration using a Tcl script by specifying the Tcl command ios_config with CLI commands and options. All arguments and submode commands must be entered on the same line as the CLI configuration command.
•
In this example, the first argument in quotes configures an Ethernet interface and enters interface configuration mode. The second argument in quotes sets the keepalive option. If these two CLI statements were entered on separate Tcl command lines, the configuration would not work.
Step 10
socket -myaddr addr -myport port -myvrf vrf-table-name host port
Example:Router(tcl)# socket -myaddr 10.4.9.34 -myport 12345 -myvrf testvrf 12346
Specifies the client socket and allows a TCL interpreter to connect via TCP over IPv4/IPv6 and opens a TCP network connection. You can specify a port and host to connect to; there must be a server to accept connections on this port.
•
-myaddr addr—domain name or numerical IP address of the client-side network interface required for the connection. Use this option especially if the client machine has multiple network interfaces.
•
-myport port— port number that is required for the client's connection.
•
-myvrf [vrf_table_name]—specifies the vrf table name. If the vrf table is not configured, then the command will return a TCL_ERROR.
Step 11
socket -server -myaddr addr -myvrf vrf-table-name port
Example:Router(tcl)# socket -server test -myvrf testvrf 12348
Specifies the server socket and allows a TCL interpreter to connect via TCP over IPv4/IPv6 and opens a TCP network connection. If the port is zero, Cisco IOS will allocate a free port to the server socket by using fconfigure command to read the -sock0 argument.
•
-myaddr addr—domain name or numerical IP address of the client-side network interface required for the connection. Use this option especially if the client machine has multiple network interfaces.
•
-myvrf vrf—specifies the vrf table name. If the vrf table is not configured, then the command will return a TCL_ERROR and append "Cannot obtain VRF Table ID for VRF_table_name" to the interpreter result.
Step 12
fconfigure channelname -remote [host port] -broadcast boolean -vrf [vrf_table_name]
Example:Router(tcl)# fconfigure sock1 -vrf vrf1 -remote [list 10.4.9.37 56009] -broadcast 1
Specifies the options in a channel.
•
In case of UDP sockets that are created using the udp_open, the UDP socket can be mapped to a VRF using the fconfigure command.
•
This command can also be used to display the properties of the channel.
•
-broadcast—enables or disables the broadcasting.
Step 13
udp_open -ipv6 port
Example:Router(tcl)# udp_open -ipv6 56005
Opens a UDP socket.
•
If a port is specified the UDP socket will be opened on that port. Otherwise the system will choose a port and you can use the fconfigure command to obtain the port number, if required. If -ipv6 argument is specified, the socket will be opened specifying the AF_INET6 protocol family.
Step 14
udp_peek sock -buffersize buffer-size
Example:Router(tcl)# udp_peek sock0 -buffersize 100
Enables peeking into a UDP socket.
•
-buffersize buffer-size—specifies the buffersize.
Step 15
exec "exec-cmd"
Example:Router(tcl)# exec "show interfaces"
(Optional) Executes Cisco IOS CLI EXEC mode commands from a Tcl script by specifying the Tcl command exec with the CLI commands.
•
In this example, interface information for the router is displayed.
Step 16
exit
Example:Router(tcl)# exit
Exits Tcl configuration mode and returns to privileged EXEC mode.
Examples
The following sample (partial) output shows information about Ethernet interface 0 on the router. The show interfaces command has been executed from Tcl configuration mode.
Router# tclshRouter(tcl)# exec "show interfaces"Ethernet 0 is up, line protocol is upHardware is MCI Ethernet, address is 0000.0c00.750c (bia 0000.0c00.750c)Internet address is 10.108.28.8, subnet mask is 255.255.255.0MTU 1500 bytes, BW 10000 Kbit, DLY 100000 usec, rely 255/255, load 1/255Encapsulation ARPA, loopback not set, keepalive set (10 sec)ARP type: ARPA, ARP Timeout 4:00:00Last input 0:00:00, output 0:00:00, output hang neverLast clearing of "show interface" counters 0:00:00Output queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 2000 bits/sec, 4 packets/sec1127576 packets input, 447251251 bytes, 0 no bufferReceived 354125 broadcasts, 0 runts, 0 giants, 57186* throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort5332142 packets output, 496316039 bytes, 0 underruns0 output errors, 432 collisions, 0 interface resets, 0 restarts...Troubleshooting Tips
Use the Tcl puts command in a Tcl script to trace command execution.
Using the Tcl Shell to Access SNMP MIB Objects
Perform this task to enable the interactive Tcl shell and enter Tcl commands to perform actions on MIB objects.
Prerequisites
The SNMP community configuration must exist in the running configuration of the router.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
scripting tcl encdir location-url
4.
scripting tcl init init-url
5.
exit
6.
tclsh
7.
Enter any required Tcl command language syntax.
8.
snmp_getbulk community-string non-repeaters max-repetitions oid [oid2 oid3...]
9.
snmp_getid community-string
10.
snmp_getnext community-string oid [oid2 oid3...]
11.
snmp_getone community-string oid [oid2 oid3...]
12.
snmp_setany community-string oid type val [oid2 type2 val2...]
13.
exit
DETAILED STEPS
Command or Action PurposeStep 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Step 2
configure terminal
Example:Router# configure terminal
(Optional) Enters global configuration mode.
•
Perform Step 2 through Step 5 Perform Step 2 through Step 5 if you are using encoding files, an initialization script, or both.
Step 3
scripting tcl encdir location-url
Example:Router(config)# scripting tcl encdir tftp://10.18.117.23/enctcl/
(Optional) Specifies the default location of external encoding files used by the Tcl encoding command.
Step 4
scripting tcl init init-url
Example:Router(config)# scripting tcl init ftp://user:password@172.17.40.3/tclscript/initf iles3.tcl
(Optional) Specifies an initialization script to run when the Tcl shell is enabled.
Step 5
exit
Example:Router(config)# exit
(Optional) Exits global configuration mode and returns to privileged EXEC mode.
Step 6
tclsh
Example:Router# tclsh
Enables the interactive Tcl shell and enters Tcl configuration mode.
Step 7
Enter the required Tcl command language syntax.
Example:Router(tcl)# proc get_bri {}
Commands entered in Tcl configuration mode are sent first to the interactive Tcl interpreter. If the command is not a valid Tcl command, it is sent to the CLI parser.
Step 8
snmp_getbulk community-string non-repeaters max-repetitions oid [oid2 oid3...]
Example:Router(tcl)# snmp_getbulk public 1 3 1.3.6.1.2.1.1.1 1.3.6.1.2.1.10.18.8.1.1
(Optional) Retrieves a large section of a MIB table.
•
Use the community-string argument to specify the SNMP community from which the objects will be retrieved.
•
Use the non-repeaters argument to specify the number of objects that can be retrieved with a get-next operation.
•
Use the max-repetitions argument to specify the maximum number of get-next operations to attempt while trying to retrieve the remaining objects.
•
Use the oid argument to specify the object ID(s) to retrieve.
Step 9
snmp_getid community-string
Example:Router(tcl)# snmp_getid private
(Optional) Retrieves the following variables from the SNMP entity on the router: sysDesrc.0, sysObjectID.0, sysUpTime.0, sysContact.0, sysName.0, and sysLocation.0.
•
Use the community-string argument to specify the SNMP community from which the objects will be retrieved.
Step 10
snmp_getnext community-string oid [oid2 oid3...]
Example:Router(tcl)# snmp_getnext public 1.3.6.1.2.1.1.1.0 1.3.6.1.2.1.1.2.0
(Optional) Retrieves a set of individual variables from a MIB table.
•
Use the community-string argument to specify the SNMP community from which the objects will be retrieved.
•
Use the oid argument to specify the object ID(s) to retrieve.
Step 11
snmp_getone community-string oid [oid2 oid3...]
Example:Router(tcl)# snmp_getone public 1.3.6.1.2.1.1.1.0 1.3.6.1.2.1.1.2.0
(Optional) Retrieves a set of individual variables from a MIB table.
•
Use the community-string argument to specify the SNMP community from which the objects will be retrieved.
•
Use the oid argument to specify the object ID(s) to retrieve.
Step 12
snmp_setany community-string oid type val [oid2 type2 val2...]
Example:Router(tcl)# snmp_setany private 1.3.6.1.2.1.1.5.0 -d TCL-SNMP_TEST
(Optional) Retrieves current values of specified variables from a MIB table and then performs a set request on the variables.
•
Use the community-string argument to specify the SNMP community from which the values of objects will be retrieved and then set.
•
Use the oid argument to specify the object ID(s) to retrieve and set.
•
Use the type argument to specify the type of object to retrieve and set.
•
Use the val argument to specify the value of the object to be retrieved and then set.
Step 13
exit
Example:Router(tcl)# exit
Exits Tcl configuration mode and returns to privileged EXEC mode.
Troubleshooting Tips
Use the Tcl puts command in a Tcl script to trace command execution.
Running Predefined Tcl Scripts
Perform this optional task to run a predefined Tcl script in Cisco IOS software.
Prerequisites
Before performing this task, you must create a Tcl script that can run on Cisco IOS software. The Tcl script may be transferred to internal flash memory using any file system that the Cisco IOS file system (IFS) supports, including TFTP, FTP, and rcp. The Tcl script may also be sourced from a remote location.
SUMMARY STEPS
1.
enable
2.
tclsh
3.
Enter the Tcl source command with the filename and path.
4.
exit
DETAILED STEPS
Configuration Examples for Cisco IOS Scripting with Tcl
This section provides the following configuration examples:
•
Example: Tcl Script Using the show interfaces Command
•
Example: Tcl Script for SMTP Support
•
Example: Tcl Script for SNMP MIB Access
Example: Tcl Script Using the show interfaces Command
Using the Tcl regular expression engine, scripts can filter specific information from show commands and present it in a custom format. The following is an example of filtering the show interfaces command output and creating a comma-separated list of BRI interfaces on the router:
tclshproc get_bri {} {set check ""set int_out [exec "show interfaces"]foreach int [regexp -all -line -inline "(^BRI\[0-9]/\[0-9])" $int_out] {if {![string equal $check $int]} {if {[info exists bri_out]} {append bri_out "," $int} else {set bri_out $int}set check $int}}return $bri_out}Example: Tcl Script for SMTP Support
The following Tcl script is useful for sending e-mail messages from a router.
#### Place required comments here!!!##package provide sendmail 2.0# Sendmail procedure for Supportnamespace eval ::sendmail {namespace export initialize configure sendmessage sendfilearray set ::sendmail::sendmail {smtphost mailhubfrom ""friendly ""}proc configure {} {}proc initialize {smtphost from friendly} {variable sendmailif {[string length $smtphost]} then {set sendmail(smtphost) $smtphost}if {[string length $from]} then {set sendmail(from) $from}if {[string length $friendly]} then {set sendmail(friendly) $friendly}}proc sendmessage {toList subject body {tcl_trace 0}} {variable sendmailset smtphost $sendmail(smtphost)set from $sendmail(from)set friendly $sendmail(friendly)if {$trace} then {puts stdout "Connecting to $smtphost:25"}set sockid [socket $smtphost 25]## DEBUGset status [catch {puts $sockid "HELO $smtphost"flush $sockidset result [gets $sockid]if {$trace} then {puts stdout "HELO $smtphost\n\t$result"}puts $sockid "MAIL From:<$from>"flush $sockidset result [gets $sockid]if {$trace} then {puts stdout "MAIL From:<$from>\n\t$result"}foreach to $toList {puts $sockid "RCPT To:<$to>"flush $sockid}set result [gets $sockid]if {$trace} then {puts stdout "RCPT To:<$to>\n\t$result"}puts $sockid "DATA "flush $sockidset result [gets $sockid]if {$trace} then {puts stdout "DATA \n\t$result"}puts $sockid "From: $friendly <$from>"foreach to $toList {puts $sockid "To:<$to>"}puts $sockid "Subject: $subject"puts $sockid "\n"foreach line [split $body "\n"] {puts $sockid " $line"}puts $sockid "."puts $sockid "QUIT"flush $sockidset result [gets $sockid]if {$trace} then {puts stdout "QUIT\n\t$result"}} result]catch {close $sockid }if {$status} then {return -code error $result}return}proc sendfile {toList filename subject {tcl_trace 0}} {set fd [open $filename r]sendmessage $toList $subject [read $fd] $tracereturn}}Example: Tcl Script for SNMP MIB Access
Using the Tcl shell, Tcl commands can perform actions on MIBs. The following example shows how to set up the community access strings to permit access to SNMP. Public access is read-only, but private access is read-write. The following example shows how to retrieve a large section of a table at once using the snmp_getbulk Tcl command extension.
Two arguments, non-repeaters and max-repetitions, must be set when an snmp_getbulk command is issued. The non-repeaters argument specifies that the first N objects are to be retrieved with a simple snmp_getnext operation. The max-repetitions argument specifies that up to M snmp_getnext operations are to be attempted to retrieve the remaining objects.
In this example, three bindings—sysUpTime (1.3.6.1.2.1.1.2.0), ifDescr (1.3.6.1.2.1.2.2.1.2), and ifType (1.3.6.1.2.1.2.2.1.3)—are used. The total number of variable bindings requested is given by the formula N + (M * R), where N is the number of non-repeaters (in this example 1), M is the max-repetitions (in this example 5), and R is the number of request objects (in this case 2, ifDescr and ifType). Using the formula, 1 + (5 * 2) equals 11; and this is the total number of variable bindings that can be retrieved by this snmp_getbulk request command.
Sample results for the individual variables include a retrieved value of sysUpTime.0 being 1336090, where the unit is in milliseconds. The retrieved value of ifDescr.1 (the first interface description) is FastEthernet0/0, and the retrieved value of ifType.1 (the first interface type) is 6, which corresponds to the ethernetCsmacd type.
snmp-server community public ROsnmp-server community private RWtclshsnmp_getbulk public 1 5 1.3.6.1.2.1.1.2.0 1.3.6.1.2.1.2.2.1.2 1.3.6.1.2.1.2.2.1.3{<obj oid='sysUpTime.0' val='1336090'/>}{<obj oid='ifDescr.1' val='FastEthernet0/0'/>}{<obj oid='ifType.1' val='6'/>}{<obj oid='ifDescr.2' val='FastEthernet1/0'/>}{<obj oid='ifType.2' val='6'/>}{<obj oid='ifDescr.3' val='Ethernet2/0'/>}{<obj oid='ifType.3' val='6'/>}{<obj oid='ifDescr.4' val='Ethernet2/1'/>}{<obj oid='ifType.4' val='6'/>}{<obj oid='ifDescr.5' val='Ethernet2/2'/>}{<obj oid='ifType.5' val='6'/>}The following example shows how to retrieve the sysDescr.0, sysObjectID.0, sysUpTime.0, sysContact.0, sysName.0, and sysLocation.0 variables—in this example shown as system.1.0, system.2.0, system.3.0, system.4.0, system.5.0, and system.6.0—from the SNMP entity on the router using the snmp_getid Tcl command extension.
tclshsnmp_getid public{<obj oid='system.1.0' val='Cisco Internetwork Operating System SoftwareCisco IOS(tm) 7200 Software (C7200-IK9S-M), Experimental Version 12.3(20030507:225511)[geotpi2itd1 124]Copyright (c) 1986-2003 by Cisco Systems, Inc.Compiled Wed 21-May-03 16:16 by engineer'/>}{<obj oid='system.2.0' val='products.223'/>}{<obj oid='sysUpTime.0' val='6664317'/>}{<obj oid='system.4.0' val='1-800-553-2447 - phone the TAC'/>}{<obj oid='system.5.0' val='c7200.myCompany.com'/>}{<obj oid='system.6.0' val='Bldg 24, San Jose, CA'/>}The following example shows how to retrieve a set of individual variables from the SNMP entity on the router using the snmp_getnext Tcl command extension:
snmp_getnext public 1.3.6.1.2.1.1.1.0 1.3.6.1.2.1.1.2.0{<obj oid='system.2.0' val='products.223'/>}{<obj oid='sysUpTime.0' val='6683320'/>}The following example shows how to retrieve a set of individual variables from the SNMP entity on the router using the snmp_getone Tcl command extension:
snmp_getone public 1.3.6.1.2.1.1.1.0 1.3.6.1.2.1.1.2.0{<obj oid='system.1.0' val='Cisco Internetwork Operating System SoftwareCisco IOS(tm) 7200 Software (C7200-IK9S-M), Experimental Version 12.3(20030507:225511) [geotpi2itd1 124]Copyright (c) 1986-2003 by Cisco Systems, Inc.Compiled Wed 21-May-03 16:16 by engineer'/>}{<obj oid='system.2.0' val='products.223'/>}The following example shows how to change something in the configuration of the router using the snmp_setany Tcl command extension. In this example, the hostname of the router is changed to TCLSNMP-HOST.
tclshsnmp_setany private 1.3.6.1.2.1.1.5.0 -d TCLSNMP-HOST{<obj oid='system.5.0' val='TCLSNMP-HOST'/>}Additional References
The following sections provide references related to the Cisco IOS Scripting with Tcl feature.
Related Documents
Related Topic Document TitleEmbedded Syslog Manager
Embedded Syslog Manager module
Network Management commands (including Tcl and logging commands): complete command syntax, defaults, command mode, command history, usage guidelines, and examples
Standards
Standards TitleNo new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
RFCs
RFCs TitleNo new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
Feature Information for Cisco IOS Scripting with Tcl
Table 4 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 4 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
Glossary
ESM—Embedded Syslog Manager.
IVR—Interactive Voice Response.
MIB—Management Information Base.
SNMP—Simple Network Management Protocol.
Tcl—Tool Command Language.
Note
See Internetworking Terms and Acronyms for terms not included in this glossary.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2003-2010 Cisco Systems, Inc. All rights reserved.
Feedback
