If the command is not a Tcl or Cisco IOS command, two error messages are displayed. If a command is not a recognized Tcl command, it is sent to the Cisco IOS CLI parser. If the commands are recognized as valid Tcl commands, the commands are executed and the results are sent to the TTY device. After Tcl commands are entered, they are sent to a Tcl interpreter. A Tcl shell can be enabled, and Tcl commands can be entered line by line. Several methods have been developed for creating and running Tcl scripts within Cisco IOS software. These subsystems have their own proprietary commands and keyword options that are not available in the Tcl shell.
#CUSTOMNC IOS SOFTWARE#
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. The Cisco IOS Tcl shell was designed to allow customers to run Tcl commands directly from the Cisco IOS CLI prompt.
#CUSTOMNC IOS UPDATE#
Commands entered using the fileevent Tcl command will not run unless forced using the update command. When the CLI tclsh command is used, there is no event loop implemented unless Embedded Syslog Manager (ESM) is active on the same router. The optional -time keyword to set the file modification time is not supported in Cisco IOS software. The optional -time keyword to set the file access time is not supported in Cisco IOS software. Sleep mode (the after command) works only with the ms keyword. Commands entered using the after Tcl command will not run unless forced using the update command. Tcl Command Options That Behave Differently in Cisco IOS Software
The table below lists Tcl commands and library calls that do not behave within Cisco IOS software as documented in standard Tcl documents.The 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. 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.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.Restrictions for Cisco IOS Scripting with Tcl Access to privileged EXEC mode should be managed by restricting access using the enable command password. Tcl configuration mode is accessed from privileged EXEC mode. Tcl commands can be executed from the Tcl configuration mode using the Cisco IOS CLI.Familiarity with Tcl programming and Cisco IOS commands is required.Prerequisites for Cisco IOS Scripting with Tcl To access Cisco Feature Navigator, go to An account on is not required. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. 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 Table at the end of this document. For the latest feature information and caveats, see the release notes for your platform and software release. Your software release may not support all the features documented in this module. Feature Information for Cisco IOS Scripting with Tcl.Configuration Examples for Cisco IOS Scripting with Tcl.
#CUSTOMNC IOS HOW TO#
Information About Cisco IOS Scripting with Tcl.Restrictions for Cisco IOS Scripting with Tcl.Prerequisites for Cisco IOS Scripting with Tcl.The 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).
0 kommentar(er)
