-
Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3 T
-
Introduction
-
CFR Commands: absolute through clock timezone
-
CFR Commands: clock update-calendar through escape-character
-
CFR Commands: event application through ip ftp passive
-
CFR Commands: major rising through periodic
-
CFR Commands: ping through service sequence-numbers
-
CFR Commands: service slave-log through show
tee -
CFR Commands: show context through show ip sla monitor total-statistics
-
CFR Commands [12.3T]: 'show kron schedule' through 'show rtr collection-statistics'
-
CFR Commands: show rtr configuration through snmp-server enable informs
-
CFR Commands: snmp-server enable traps through statistics-distribution-interval
-
CFR Commands: stopbits through ttl ip
-
CFR Commands: type dhcp through xsm vdm
-
Appendix: ASCII Character Set and Hex Values (12.3T CF CR)
-
Table Of Contents
terminal special-character-bits
terminal telnet refuse-negotiations
terminal-queue entry-retry-interval
stopbits
To set the number of the stop bits transmitted per byte, use the stopbits command in line configuration mode. To restore the default value, use the no form of this command.
stopbits {1 | 1.5 | 2}
no stopbits
Syntax Description
Defaults
2 stop bits per byte
Command Modes
Line configuration
Command History
Usage Guidelines
Communication protocols provided by devices such as terminals and modems often require a specific stop-bit setting.
Examples
In the following example, the stop bits transmitted per byte are changed from the default of two stop bits to one stop bit as a performance enhancement for line 4:
Router(config)# line 4Router(config-line)# stopbits 1Related Commands
terminal stopbits
Changes the number of stop bits sent per byte by the current terminal line during an active session.
system (ERM policy)
To configure system level resource owners, use the system command in ERM policy configuration mode.
system
Syntax Description
This command has no arguments or keywords.
Command Default
Disabled
Command Modes
ERM policy configuration
Command History
Usage Guidelines
You can configure system level resources in ERM policy configuration mode.
Examples
The following example shows how to configure system level ROs:
Router(config-erm-policy)# systemRelated Commands
tag
To create a user-specified identifier for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the tag command in the appropriate submode of IP SLA monitor configuration or RTR configuration mode. To remove a tag from an operation, use the no form of this command.
tag text
no tag
Syntax Description
Defaults
No tag identifier is specified.
Command Modes
IP SLA Monitor Configuration
DHCP configuration (config-sla-monitor-dhcp)
DLSw configuration (config-sla-monitor-dlsw)
DNS configuration (config-sla-monitor-dns)
Frame Relay configuration (config-sla-monitor-frameRelay)
FTP configuration (config-sla-monitor-ftp)
HTTP configuration (config-sla-monitor-http)
ICMP echo configuration (config-sla-monitor-echo)
ICMP path echo configuration (config-sla-monitor-pathEcho)
ICMP path jitter configuration (config-sla-monitor-pathJitter)
TCP connect configuration (config-sla-monitor-tcp)
UDP echo configuration (config-sla-monitor-udp)
UDP jitter configuration (config-sla-monitor-jitter)
VoIP configuration (config-sla-monitor-voip)RTR Configuration
DHCP configuration (config-rtr-dhcp)
DLSw configuration (config-rtr-dlsw)
DNS configuration (config-rtr-dns)
Frame Relay configuration (config-rtr-frameRelay)
FTP configuration (config-rtr-ftp)
HTTP configuration (config-rtr-http)
ICMP echo configuration (config-rtr-echo)
ICMP path echo configuration (config-rtr-pathEcho)
ICMP path jitter configuration (config-rtr-pathJitter)
TCP connect configuration (config-rtr-tcp)
UDP echo configuration (config-rtr-udp)
UDP jitter configuration (config-rtr-jitter)
Note
The configuration mode varies depending on the Cisco IOS release you are running and the operation type configured. See the "Usage Guidelines" section for more information.
Command History
Usage Guidelines
An operation tag is normally used to logically link operations in a group.
Tags can be used to support automation (for example, by using the same tag for two different operations on two different routers echoing the same target).
IP SLAs Operation Configuration Dependence on Cisco IOS Release
The Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 181). You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation.
The configuration mode for the tag command varies depending on the Cisco IOS release you are running (see Table 181) and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the ICMP echo operation type is configured, you would enter the tag command in ICMP echo configuration mode (config-sla-monitor-echo) within IP SLA monitor configuration mode.
Examples
In the following examples, IP SLAs ICMP echo operation 1 is tagged with the label testoperation. Note that the Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 181).
IP SLA Monitor Configuration
ip sla monitor 1type echo protocol ipIcmpEcho 172.16.1.176tag testoperation!ip sla monitor schedule 1 life forever start-time nowRTR Configuration
rtr 1type echo protocol ipIcmpEcho 172.16.1.176tag testoperation!rtr schedule 1 life forever start-time nowRelated Commands
tclsh
To enable the interactive Tool Command Language (Tcl) shell, use the tclsh command in privileged EXEC mode.
tclsh
Syntax Description
This command has no arguments or keywords.
Defaults
The Tcl shell is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the tclsh command when you want to run Tcl commands from the Cisco IOS command-line interface (CLI). When the interactive Tcl shell is enabled and Tcl configuration mode is entered, Tcl commands can be entered line by line or a predefined Tcl script can be run. After Tcl commands are entered they are sent to a Tcl interpreter. If the commands are recognized as valid Tcl commands, the command is executed and the result is sent to the tty. 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 will be 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.
Use the Cisco IOS CLI exit or the Tcl tclquit command to disable the use of the Tcl shell and return to privileged EXEC mode.
Examples
The following example shows how to enable the Tcl interactive shell:
Router# tclshRouter(tcl)#Related Commands
scripting tcl encdir
Specifies the default location of external encoding files used by the Tcl shell.
scripting tcl init
Specifies an initialization script for the Tcl shell.
template (cns)
To specify a list of Cisco Networking Services (CNS) connect templates within a CNS connect profile to be applied to a router's configuration, use the template command in CNS connect configuration mode. To disable this CNS connect template, use the no form of this command.
template name [...name]
no template name [...name]
Syntax Description
Defaults
No CNS connect templates are specified.
Command Modes
CNS connect configuration
Command History
12.3(2)XF
This command was introduced.
12.3(8)T
This command was integrated into Cisco IOS Release 12.3(8)T.
12.3(9)
This command was integrated into Cisco IOS Release 12.3(9).
Usage Guidelines
First use the cns connect command to enter CNS connect configuration mode and define the parameters of a CNS connect profile for connecting to the CNS configuration engine. Then use the following CNS connect commands to create a CNS connect profile:
•
•
A CNS connect profile specifies the discover commands and associated template commands that are to be applied to a router's configuration. The template command specifies the list of CNS connect templates that is to be applied to a router's configuration. The templates in the list are applied one at a time. That is, when the template command is processed, the first template in the list is applied to the router's configuration. The router then tries to ping the CNS configuration engine. If the ping fails, then the first template in the list is removed from the router's configuration and the second template in the list is applied and so on.
The configuration mode in which the CNS connect templates are applied is specified by the immediately preceding discover command. (If there are no preceding discover commands, the templates are applied in global configuration mode.) When multiple discover and template commands are configured in a CNS connect profile, they are processed in the order in which they are entered.
Examples
The following example shows how to create a CNS connect profile named profile-1:
Router (config)# cns connect profile-1Router (config-cns-conn)# discover interface SerialRouter (config-cns-conn)# template temp-A1 temp-A2Router (config-cns-conn)# template temp-B1 temp-B2Router (config-cns-conn)# exitRouter (config)#In this example, the following sequence of events occur for all serial interfaces when the cns connect profile-1 command is processed. Assume all ping attempts to the CNS configuration engine are unsuccessful.
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
Related Commands
terminal databits
To change the number of data bits per character for the current terminal line for this session, use the terminal databits command in EXEC mode.
terminal databits {5 | 6 | 7 | 8}
Syntax Description
5
Five data bits per character.
6
Six data bits per character.
7
Seven data bits per character.
8
Eight data bits per character. This is the default.
Defaults
8 data bits per character
Command Modes
EXEC
Command History
Usage Guidelines
Communication protocols provided by devices such as terminals and modems often require a specific data bit setting. The terminal databits command can be used to mask the high bit on input from devices that generate 7 data bits with parity. If parity is being generated, specify 7 data bits per character. If no parity generation is in effect, specify 8 data bits per character. The other keywords (5 and 6) are supplied for compatibility with older devices and are generally not used.
Examples
In the following example, the databits per character is changed to seven for the current session:
Router# terminal databits 7Related Commands
terminal data-character-bits
To set the number of data bits per character that are interpreted and generated by the Cisco IOS software for the current line and session, use the terminal data-character-bits command in EXEC mode.
terminal data-character-bits {7 | 8}
Syntax Description
Defaults
8 data bits per character
Command Modes
EXEC
Command History
Usage Guidelines
This command is used primarily to strip parity from X.25 connections on routers with the protocol translation software option. The terminal data-character-bits command does not work on hard-wired lines.
Examples
The following example sets the data bits per character to seven on the current line:
Router# terminal data-character-bits 7Related Commands
data-character-bits
Sets the number of data bits per character that are interpreted and generated by the Cisco IOS software.
terminal dispatch-character
To define a character that causes a packet to be sent for the current session, use the terminal dispatch-character command in EXEC mode.
terminal dispatch-character ascii-number [ascii-number2 . . . ascii-number]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
At times, you might want to queue up a string of characters until they fill a complete packet and then transmit the packet to a remote host. This can make more efficient use of a line, because the access server or router normally dispatches each character as it is entered.
Examples
The following example defines the characters Ctrl-D (ASCII decimal character 4) and Ctrl-Y (ASCII decimal character 25) as the dispatch characters:
Router# terminal dispatch-character 4 25Related Commands
terminal dispatch-timeout
To set the character dispatch timer for the current terminal line for the current session, use the terminal dispatch-timeout command in EXEC mode.
terminal dispatch-timeout milliseconds
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Use this command to increase the processing efficiency of the remote host.
The dispatch-timeout line configuration command causes the software to buffer characters into packets for transmission to the remote host. The Cisco IOS software sends a packet a specified amount of time after the first character is put into the buffer. You can use the terminal dispatch-timeout and terminal dispatch-character line configuration commands together. In this case, the software dispatches a packet each time the dispatch character is entered, or after the specified dispatch timeout interval, depending on which condition is met first.
Note
Examples
In the following example, the dispatch timeout timer is set to 80 milliseconds:
Router# terminal dispatch-timeout 80Related Commands
dispatch-timeout
Sets the character dispatch timer for a specified line or group of lines.
terminal download
To temporarily set the ability of a line to act as a transparent pipe for file transfers for the current session, use the terminal download command in EXEC mode.
terminal download
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
EXEC
Command History
Usage Guidelines
You can use this feature to run a program such as KERMIT, XMODEM, or CrossTalk that downloads a file across an access server or router line. This command configures the terminal line to send data and is equivalent to entering all the following commands:
•
•
•
•
•
•
•
Examples
The following example configures a line to act as a transparent pipe:
Router# terminal downloadterminal editing
To reenable the enhanced editing mode for only the current terminal session, use the terminal editing command in EXEC mode. To disable the enhanced editing mode on the current line, use the no form of this command.
terminal editing
terminal no editing
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
EXEC
Command History
Usage Guidelines
This command is identical to the editing EXEC mode command, except that it controls (enables or disables) enhanced editing for only the terminal session you are using. For a description of the available editing keys, see the description of the editing command in this document.
Examples
In the following example, enhanced editing mode is reenabled for only the current terminal session:
Router> terminal editingRelated Commands
terminal escape-character
To set the escape character for the current terminal line for the current session, use the terminal escape-character command in EXEC mode.
terminal escape-character ascii-number
Syntax Description
ascii-number
ASCII decimal representation of the escape character or control sequence (for example, Ctrl-P ).
Defaults
Ctrl-^ (Ctrl-Shift-6)
Command Modes
EXEC
Command History
Usage Guidelines
See the "ASCII Character Set and Hexidecimal Values" appendix for a list of ASCII characters and their numerical representation.
This command is useful, for example, if you have the default escape character defined for a different purpose in your keyboard file. Entering the escape character followed by the X key returns you to EXEC mode when you are connected to another computer.
Note
Examples
In the following example, the escape character to Ctrl-P (ASCII decimal character 16) for the current session:
Router# terminal escape-character 16Related Commands
terminal exec-character-bits
To locally change the ASCII character set used in EXEC and configuration command characters for the current session, use the terminal exec-character-bits command in EXEC mode.
terminal exec-character-bits {7 | 8}
Syntax Description
7
Selects the 7-bit ASCII character set. This is the default.
8
Selects the full 8-bit character set.
Defaults
7-bit ASCII character set (unless set otherwise in global configuration mode)
Command Modes
EXEC
Command History
Usage Guidelines
This EXEC command overrides the default-value exec-character-bits global configuration command. Configuring the EXEC character width to 8 bits enables you to view special graphical and international characters in banners, prompts, and so on.
When the user exits the session, the character width is reset to the default value established by the exec-character-bits global configuration command. However, setting the EXEC character width to 8 bits can also cause failures. For example, if a user on a terminal that is sending parity enters the help command, an "unrecognized command" message appears because the system is reading all 8 bits, and the eighth bit is not needed for the help command.
Examples
The following example temporarily configures the system to use a full 8-bit user interface for system banners and prompts, allowing the use of additional graphical and international characters:
Router# terminal exec-character-bits 8Related Commands
exec-character-bits
Configures the character widths of EXEC and configuration command characters.
terminal flowcontrol
To set flow control for the current terminal line for the current session, use the terminal flowcontrol command in EXEC mode.
terminal flowcontrol {none | software [in | out] | hardware}
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
Flow control enables you to regulate the rate at which data can be transmitted from one point so that it is equal to the rate at which it can be received at another point. Flow control protects against loss of data because the terminal is not capable of receiving data at the rate it is being sent. You can set up data flow control for the current terminal line in one of two ways: software flow control, which you do with control key sequences, and hardware flow control, which you do at the device level.
For software flow control, the default stop and start characters are Ctrl-S and Ctrl-Q (XOFF and XON). You can change them with the terminal stop-character and terminal start-character EXEC commands.
Examples
In the following example, incoming software flow control is set for the current session:
Router# terminal flowcontrol software inRelated Commands
flowcontrol
Sets the method of data flow control between the terminal or other serial device and the router.
terminal full-help
To get help for the full set of user-level commands, use the terminal full-help command in EXEC mode.
terminal full-help
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
EXEC
Command History
Usage Guidelines
The terminal full-help command enables a user to see all of the help messages available from the terminal. It is used with the show ? command.
Examples
In the following example, the difference between the output of the show ? command before and after using the terminal full-help command is shown:
Router> show ?bootflash Boot Flash informationcalendar Display the hardware calendarclock Display the system clockcontext Show context informationdialer Dialer parameters and statisticshistory Display the session command historyhosts IP domain-name, lookup style, nameservers, and host tableisdn ISDN informationkerberos Show Kerberos Valuesmodemcap Show Modem Capabilities databaseppp PPP parameters and statisticsrmon rmon statisticssessions Information about Telnet connectionssnmp snmp statisticsterminal Display terminal configuration parametersusers Display information about terminal linesversion System hardware and software statusRouter> terminal full-helpRouter> show ?access-expression List access expressionaccess-lists List access listsaliases Display alias commandsapollo Apollo network informationappletalk AppleTalk informationarp ARP tableasync Information on terminal lines used as router interfacesbootflash Boot Flash informationbridge Bridge Forwarding/Filtering Database [verbose]bsc BSC interface informationbstun BSTUN interface informationbuffers Buffer pool statisticscalendar Display the hardware calendarcdp CDP informationclns CLNS network informationclock Display the system clockcls DLC user informationcmns Connection-Mode networking services (CMNS) informationcompress Show compression statistics....x25 X.25 informationxns XNS informationxremote XRemote statisticsRelated Commands
full-help
Gets help for the full set of user-level commands.
help
Displays a brief description of the help system.
terminal history
To enable the command history function with 10 lines for the current terminal session, use the terminal history command in user EXEC or privileged EXEC mode. To disable the command history function, use the no form of this command.
terminal history
terminal no history
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled, history buffer of 10 lines
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The history function provides a record of commands you have entered. This function is particularly useful for recalling long or complex commands or entries for the purposes of modifying them slightly and reexecuting them.
The terminal history command enables the command history function with the default buffer size or the last buffer size specified using the terminal history size command.
Table 182 lists the keys and functions you can use to recall commands from the history buffer.
Table 182 History Keys
Ctrl-P or Up Arrow1
Recalls commands in the history buffer in a backward sequence, beginning with the most recent command. Repeat the key sequence to recall successively older commands.
Ctrl-N or Down Arrow1
Returns to more recent commands in the history buffer after recalling commands with Ctrl-P or the Up Arrow. Repeat the key sequence to recall successively more recent commands.
1 The arrow keys function only with ANSI-compatible terminals.
Examples
In the following example, the command history feature is disabled for the current terminal session:
Router> terminal no historyRelated Commands
terminal history size
To change the size of the command history buffer for the current terminal session, use the terminal history size command in EXEC mode. To reset the command history buffer to its default size of 10 lines, use the no form of this command.
terminal history size number-of-lines
terminal no history size
Syntax Description
number-of-lines
Number of command lines that the system will record in its history buffer. The range is from 0 to 256. The default is 10.
Defaults
10 lines of command history
Command Modes
EXEC
Command History
Usage Guidelines
The history feature provides a record of commands you have entered. This feature is particularly useful for recalling long or complex commands or entries for the purposes of modifying them slightly and reissuing them.
The terminal history size command enables the command history feature and sets the command history buffer size. The terminal no history size command resets the buffer size to the default of 10 command lines.
Table 183 lists the keys and functions you can use to recall commands from the history buffer. When you use these keys, the commands recalled will be from EXEC mode if you are in EXEC mode, or from all configuration modes if you are in any configuration mode.
Table 183 History Keys
Ctrl-P or Up Arrow1
Recalls commands in the history buffer in a backward sequence, beginning with the most recent command. Repeat the key sequence to recall successively older commands.
Ctrl-N or Down Arrow1
Returns to more recent commands in the history buffer after recalling commands with Ctrl-P or the Up Arrow. Repeat the key sequence to recall successively more recent commands.
1 The arrow keys function only with ANSI-compatible terminals.
In EXEC mode, you can also use the show history command to show the contents of the command history buffer.
To check the current settings for the command history feature on your line, use the show line command.
Examples
In the following example, the number of command lines recorded is set to 15 for the current terminal session. The user then checks to see what line he/she is connected to using the show users command. The user uses this line information to issue the show line command. (In this example, the user uses the show begin option in the show line command to start the output at the "Editing is enabled/disabled" line.)
Router# terminal history size 15Router# show usersLine User Host(s) Idle Location* 50 vty 0 admin idle 00:00:00! the * symbol indicates the active terminal session for the user (line 50)Router# show line 50 | begin EditingEditing is enabled.! the following line shows the history settings for the lineHistory is enabled, history size is 15.DNS resolution in show commands is enabledFull user help is disabledAllowed transports are telnet. Preferred is none.No output characters are paddedNo special data dispatching charactersRelated Commands
terminal hold-character
To define the hold character for the current session, use the terminal hold-character command in EXEC mode. To return the hold character definition to the default, use the no form of this command.
terminal hold-character ascii-number
terminal no hold-character
Syntax Description
Defaults
The default hold character is defined by the hold-character global configuration command.
Command Modes
EXEC
Command History
Usage Guidelines
You can define a local hold character that temporarily suspends the flow of output on the terminal. When information is scrolling too quickly, you can enter the hold character to pause the screen output, then enter any other character to resume the flow of output.
You cannot suspend output on the console terminal. To send the hold character to the host, precede it with the escape character.
Examples
In the following example, the hold character for the current (local) session is set to Ctrl-P. The show terminal output is included to show the verification of the setting (the value for the hold character is shown in the "Special Characters" listing).
Router# terminal hold-character 16"^P" is the local hold characterRouter# show terminalLine 50, Location: "", Type: "VT220"Length: 24 lines, Width: 80 columnsBaud rate (TX/RX) is 9600/9600Status: PSI Enabled, Ready, Active, No Exit Banner, Automore OnCapabilities: noneModem state: ReadyGroup codes: 0Special Chars: Escape Hold Stop Start Disconnect Activation^^x ^P - - noneTimeouts: Idle EXEC Idle Session Modem Answer Session Dispatch00:10:00 never none not setIdle Session Disconnect WarningneverLogin-sequence User Response00:00:30Autoselect Initial Waitnot setModem type is unknown.Session limit is not set.Time since activation: 00:04:13Editing is enabled.History is enabled, history size is 10....Related Commands
hold-character
Defines the local hold character used to pause output to the terminal screen.
show terminal
Displays settings for terminal operating characteristics.
terminal international
If you are using Telnet to access a Cisco IOS platform and you want to display 8-bit and multibyte international characters (for example, Kanji) and print the Escape character as a single character instead of as the caret and bracket symbols (^[) for a current Telnet session, use the terminal international command in user EXEC or priviledged mode. To display characters in 7-bit format for a current Telnet session, use the no form of this command.
terminal international
no terminal international
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
If you are configuring a Cisco IOS platform using the Cisco web browser UI, this feature is enabled automatically when you enable the Cisco web browser UI using the ip http server global configuration command.
Examples
The following example enables a Cisco IOS platform to display 8-bit and multibyte characters and print the Escape character as a single character instead of as the caret and bracket symbols (^[) when you are using Telnet to access the platform for the current Telnet session:
Router# terminal internationalRelated Commands
terminal keymap-type
To specify the current keyboard type for the current session, use the terminal keymap-type command in EXEC mode.
terminal keymap-type keymap-name
Syntax Description
Defaults
VT100
Command Modes
EXEC
Command History
Usage Guidelines
You must use this command when you are using a keyboard other than the default of VT100.
Examples
The following example specifies a VT220 keyboard as the current keyboard type:
Router# terminal keymap-type vt220Related Commands
terminal length
To set the number of lines on the current terminal screen for the current session, use the terminal length command in EXEC mode.
terminal length screen-length
Syntax Description
screen-length
Number of lines on the screen. A value of zero disables pausing between screens of output.
Defaults
24 lines
Command Modes
EXEC
Command History
Usage Guidelines
The system uses the length value to determine when to pause during multiple-screen output. A value of zero prevents the router from pausing between screens of output.
Some types of terminal sessions do not require you to specify the screen length because the screen length specified can be learned by some remote hosts. For example, the rlogin protocol uses the screen length to set up terminal parameters on a remote UNIX host.
Examples
In the following example, the system is configured to prevent output from pausing if it exceeds the length of the screen:
Router# terminal length 0Related Commands
terminal monitor
To display debug command output and system error messages for the current terminal and session, use the terminal monitor command in EXEC mode.
terminal monitor
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
EXEC
Command History
Usage Guidelines
Remember that all terminal parameter-setting commands are set locally and do not remain in effect after a session is ended.
Examples
In the following example, the system is configured to display debug command output and error messages during the current terminal session:
Router# terminal monitorterminal notify
To enable terminal notification about pending output from other Telnet connections for the current session, use the terminal notify command in EXEC mode. To disable notifications for the current session, use the no form of this command.
terminal notify
terminal no notify
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
Enabling notifications may be useful if, for example, you want to know when another connection receives mail, or when a process has been completed.
This command enables or disables notifications for only the current session. To globally set these notifications, use the notify line configuration command.
Examples
In the following example, notifications will be displayed to inform the user when output is pending on another connection:
Router# terminal notifyRelated Commands
notify
Enables terminal notification about pending output from other Telnet connections.
terminal padding
To change the character padding on a specific output character for the current session, use the terminal padding command in EXEC mode.
terminal padding ascii-number count
Syntax Description
ascii-number
ASCII decimal representation of the character.
count
Number of NULL bytes sent after the specified character, up to 255 padding characters in length.
Defaults
No padding
Command Modes
EXEC
Command History
Usage Guidelines
Character padding adds a number of null bytes to the end of the string and can be used to make a string an expected length for conformity.
Use this command when the attached device is an old terminal that requires padding after certain characters (such as ones that scrolled or moved the carriage). See the"ASCII Character Set and Hexidecimal Values" appendix for a list of ASCII characters.
Examples
The following example pads Ctrl-D (ASCII decimal character 4) with 164 NULL bytes:
Router# terminal padding 4 164Related Commands
terminal parity
To define the generation of the parity bit for the current terminal line and session, use the terminal parity command in EXEC mode.
terminal parity {none | even | odd | space | mark}
Syntax Description
none
No parity. This is the default.
even
Even parity.
odd
Odd parity.
space
Space parity.
mark
Mark parity.
Defaults
No parity.
Command Modes
EXEC
Command History
Usage Guidelines
Communication protocols provided by devices such as terminals and modems will sometimes require a specific parity bit setting. Refer to the documentation for your device to determine required parity settings.
Examples
In the following example, odd parity checking is enabled for the current session:
Router# terminal parity oddRelated Commands
parity
Defines generation of a parity bit for connections on a specified line or lines.
terminal rxspeed
To set the terminal receive speed (how fast information is sent to the terminal) for the current line and session, use the terminal rxspeed command in EXEC mode.
terminal rxspeed bps
Syntax Description
Defaults
9600 bps
Command Modes
EXEC
Command History
Usage Guidelines
Set the speed to match the baud rate of whatever device you have connected to the port. Some baud rates available on devices connected to the port might not be supported on the system. The system will indicate if the speed you select is not supported.
Examples
The following example sets the current auxiliary line receive speed to 115200 bps:
Router# terminal rxspeed 115200Related Commands
terminal special-character-bits
To change the ASCII character widths to accept special characters for the current terminal line and session, use the terminal special-character-bits command in EXEC mode.
terminal special-character-bits {7 | 8}
Syntax Description
7
Selects the 7-bit ASCII character set. This is the default.
8
Selects the full 8-bit ASCII character set.
Defaults
7-bit ASCII character set
Command Modes
EXEC
Command History
Usage Guidelines
Configuring the width to 8 bits enables you to use twice as many special characters as with the 7-bit setting. This selection enables you to add special graphical and international characters in banners, prompts, and so on.
This command is useful, for example, if you want the router to provide temporary support for international character sets. It overrides the default-value special-character-bits global configuration command and is used to compare character sets typed by the user with the special character available during a data connection, which includes software flow control and escape characters.
When you exit the session, character width is reset to the width established by the default-value exec-character-bits global configuration command.
Note that setting the EXEC character width to eight bits can cause failures. For example, if a user on a terminal that is sending parity enters the help command, an "unrecognized command" message appears because the Cisco IOS software is reading all eight bits, and the eighth bit is not needed for the help command.
Examples
The following example temporarily configures a router to use a full 8-bit user interface for system banners and prompts.
Router# terminal special-character-bits 8Related Commands
terminal speed
To set the transmit and receive speeds of the current terminal line for the current session, use the terminal speed command in EXEC mode.
terminal speed bps
Syntax Description
Defaults
9600 bps
Command Modes
EXEC
Command History
Usage Guidelines
Set the speed to match the transmission rate of whatever device you have connected to the port. Some baud rates available on devices connected to the port might not be supported on the router. The router indicates whether the speed you selected is not supported.
Examples
The following example restores the transmit and receive speed on the current line to 9600 bps:
Router# terminal speed 9600Related Commands
terminal start-character
To change the flow control start character for the current session, use the terminal start-character command in EXEC mode.
terminal start-character ascii-number
Syntax Description
Defaults
Ctrl-Q (ASCII decimal character 17)
Command Modes
EXEC
Command History
Usage Guidelines
The flow control start character signals the start of data transmission when software flow control is in effect.
Examples
The following example changes the start character to Ctrl-O (ASCII decimal character 15):
Router# terminal start-character 15Related Commands
terminal stopbits
To change the number of stop bits sent per byte by the current terminal line during an active session, use the terminal stopbits command in EXEC mode.
terminal stopbits {1 | 1.5 | 2}
Syntax Description
Defaults
2 stop bits
Command Modes
EXEC
Command History
Usage Guidelines
Communication protocols provided by devices such as terminals and modems often require a specific stop-bit setting.
Examples
In the following example, the setting for stop bits is changed to one for the current session:
Router# terminal stopbits 1Related Commands
terminal stop-character
To change the flow control stop character for the current session, use the terminal stop-character command in EXEC mode.
terminal stop-character ascii-number
Syntax Description
Defaults
Ctrl-S (ASCII character decimal 19)
Command Modes
EXEC
Command History
Usage Guidelines
The flow control stop character signals the end of data transmission when software flow control is in effect.
See the "ASCII Character Set and Hexidecimal Values" appendix for a list of ASCII characters.
Examples
In the following example, the stop character is configured as Ctrl-E (ASCII character decimal 5) for the current session:
Router# terminal stop-character 5Related Commands
terminal telnet break-on-ip
To cause an access server to generate a hardware Break signal when an interrupt-process (ip) command is received, use the terminal telnet break-on-ip command in EXEC mode.
terminal telnet break-on-ip
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
EXEC
Command History
Usage Guidelines
The hardware Break signal occurs when a Telnet interrupt-process (ip) command is received on that connection. The terminal telnet break-on-ip command can be used to control the translation of Telnet interrupt-process commands into X.25 Break indications.
Note
This command is also a useful workaround in the following situations:
•
•
Some EIA/TIA-232 hardware devices use a hardware Break signal for various purposes. A hardware Break signal is generated when a Telnet Break command is received.
You can verify if this command is enabled with the show terminal EXEC command. If enabled the following line will appear in the output: Capabilities: Send BREAK on IP.
Examples
In the following example, a Break signal is generated for the current connection when an interrupt-process command is issued:
Router# terminal telnet break-on-ipRelated Commands
terminal telnet ip-on-break
Configures the system to send an interrupt-process (ip) signal when the Break command is issued.
terminal telnet refuse-negotiations
To configure the current session to refuse to negotiate full-duplex, remote echo options on incoming connections, use the terminal telnet refuse-negotiations command in EXEC mode.
terminal telnet refuse-negotiations
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
EXEC
Command History
Usage Guidelines
You can set the line to allow access server to refuse full-duplex, remote echo connection requests from the other end. This command suppresses negotiation of the Telnet Remote Echo and Suppress Go Ahead options.
Examples
In the following example, the current session is configured to refuse full-duplex, remote echo requests:
Router# terminal telnet refuse-negotiationsterminal telnet speed
To allow an access server to negotiate transmission speed for the current terminal line and session, use the terminal telnet speed command in EXEC mode.
terminal telnet speed default-speed maximum-speed
Syntax Description
Defaults
9600 bps (unless otherwise set using the speed, txspeed or rxspeed line configuration commands)
Command Modes
EXEC
Command History
Usage Guidelines
You can match line speeds on remote systems in reverse Telnet, on host machines connected to an access server to access the network, or on a group of console lines connected to the access server when disparate line speeds are in use at the local and remote ends of the connections listed above. Line speed negotiation adheres to the Remote Flow Control option, defined in RFC 1080.
Note
Examples
The following example enables the access server to negotiate a bit rate on the line using the Telnet option. If no speed is negotiated, the line will run at 2400 bps. If the remote host requests a speed greater than 9600 bps, then 9600 bps will be used.
Router# terminal telnet speed 2400 9600terminal telnet sync-on-break
To cause the access server to send a Telnet Synchronize signal when it receives a Telnet Break signal on the current line and session, use the terminal telnet sync-on-break command in EXEC mode.
terminal telnet sync-on-break
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
EXEC
Command History
Usage Guidelines
You can configure the session to cause a reverse Telnet line to send a Telnet Synchronize signal when it receives a Telnet Break signal. The TCP Synchronize signal clears the data path, but still interprets incoming commands.
Note
Examples
The following example sets an asynchronous line to cause the access server to send a Telnet Synchronize signal:
Router# terminal telnet sync-on-breakterminal telnet transparent
To cause the current terminal line to send a Return character (CR) as a CR followed by a NULL instead of a CR followed by a Line Feed (LF) for the current session, use the terminal telnet transparent command in EXEC mode.
terminal telnet transparent
Syntax Description
This command has no arguments or keywords.
Defaults
CR followed by an LF
Command Modes
EXEC
Command History
Usage Guidelines
The end of each line typed at the terminal is ended with a Return (CR). This command permits interoperability with different interpretations of end-of-line demarcation in the Telnet protocol specification.
Note
Examples
In the following example, the session is configured to send a CR signal as a CR followed by a NULL:
Router# terminal telnet transparentterminal terminal-type
To specify the type of terminal connected to the current line for the current session, use the terminal terminal-type command in EXEC mode.
terminal terminal-type terminal-type
Syntax Description
terminal-type
Defines the terminal name and type, and permits terminal negotiation by hosts that provide that type of service. The default is VT100.
Defaults
VT100
Command Modes
EXEC
Command History
Usage Guidelines
Indicate the terminal type if it is different from the default of VT100.
The terminal type name is used by TN3270s for display management and by Telnet and rlogin to inform the remote host of the terminal type.
Examples
In the following example, the terminal type is defined as VT220 for the current session:
Router# terminal terminal-type VT220Related Commands
terminal keymap-type
Specifies the current keyboard type for the current session.
terminal-type
Specifies the type of terminal connected to a line.
terminal txspeed
To set the terminal transmit speed (how fast the terminal can send information) for the current line and session, use the terminal txspeed command in EXEC mode.
terminal txspeed bps
Syntax Description
Defaults
9600 bps
Command Modes
EXEC
Command History
Examples
In the following example, the line transmit speed is set to 2400 bps for the current session:
Router# terminal txspeed 2400Related Commands
terminal width
To set the number of character columns on the terminal screen for the current line for a session, use the terminal width command in EXEC mode.
terminal width characters
Syntax Description
Defaults
80 characters
Command Modes
EXEC
Command History
Usage Guidelines
By default, the route provides a screen display width of 80 characters. You can reset this value for the current session if it does not meet the needs of your terminal.
The rlogin protocol uses the value of the characters argument to set up terminal parameters on a remote host.
Examples
The following example sets the terminal character columns to 132:
Router# terminal width 132Related Commands
width
Sets the terminal screen width (the number of character columns displayed on the attached terminal).
terminal-queue entry-retry-interval
To change the retry interval for a terminal port queue, use the terminal-queue entry-rety-interval command in global configuration mode. To restore the default terminal port queue interval, use the no form of this command.
terminal-queue entry-retry-interval seconds
no terminal-queue entry-retry-interval
Syntax Description
Defaults
60 seconds
Command Modes
Global configuration
Command History
Usage Guidelines
If a remote device (such as a printer) is busy, the connection attempt is placed in a terminal port queue. If you want to decrease the waiting period between subsequent connection attempts, decrease the default of 60 to an interval of 10 seconds. Decrease the time between subsequent connection attempts when, for example, a printer queue stalls for long periods.
Examples
The following example changes the terminal port queue retry interval from the default of 60 seconds to 10 seconds:
Router# terminal-queue entry-retry-interval 10terminal-type
To specify the type of terminal connected to a line, use the terminal-type command in line configuration mode. To remove any information about the type of terminal and reset the line to the default terminal emulation, use the no form of this command.
terminal-type {terminal-name | terminal-type}
no terminal-type
Syntax Description
Defaults
VT100
Command Modes
Line configuration
Command History
Usage Guidelines
This command records the type of terminal connected to the line. The terminal-name argument provides a record of the terminal type and allows terminal negotiation of display management by hosts that provide that type of service.
For TN3270 applications, this command must follow the corresponding ttycap entry in the configuration file.
Examples
The following example defines the terminal on line 7 as a VT220:
Router(config)# line 7Router(config-line)# terminal-type VT220test flash
To test Flash memory on MCI and envm Flash EPROM interfaces, use the test flash command in EXEC mode.
test flash
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
In the following example, the Flash memory is tested:
test flashRelated Commands
test interfaces
Tests the system interfaces on the modular router.
test memory
Performs a test of Multibus memory (including nonvolatile memory) on the modular router.
test interfaces
To test the system interfaces on the modular router, use the test interfaces command in EXEC mode.
test interfaces
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
The test interfaces EXEC command is intended for the factory checkout of network interfaces. It is not intended for diagnosing problems with an operational router. The test interfaces output does not report correct results if the router is attached to a "live" network. For each network interface that has an IP address that can be tested in loopback (MCI and ciscoBus Ethernet and all serial interfaces), the test interfaces command sends a series of ICMP echoes. Error counters are examined to determine the operational status of the interface.
Examples
In the following example, the system interfaces are tested:
test interfacesRelated Commands
test flash
Tests Flash memory on MCI and envm Flash EPROM interfaces.
test memory
Performs a test of Multibus memory (including nonvolatile memory) on the modular router.
test memory
To perform a test of Multibus memory (including nonvolatile memory) on the modular router, use the test memory command in EXEC mode. The memory test overwrites memory.
test memory
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
The memory test overwrites memory. If you use the test memory command, you will need to rewrite nonvolatile memory. For example, if you test Multibus memory, which is the memory used by the CSC-R 4-Mbps Token Ring interfaces, you will need to reload the system before the network interfaces will operate properly. The test memory command is intended primarily for use by Cisco personnel.
Examples
In the following example, the memory is tested:
test memoryRelated Commands
test flash
Tests Flash memory on MCI and envm Flash EPROM interfaces.
test interfaces
Tests the system interfaces on the modular router.
tftp-server
To configure a router or a Flash memory device on the router as a TFTP server, use one of the following tftp-server commands in global configuration mode. This command replaces the tftp-server system command. To remove a previously defined filename, use the no form of this command with the appropriate filename.
tftp-server flash [partition-number:]filename1 [alias filename2] [access-list-number]
tftp-server rom alias filename1 [access-list-number]
no tftp-server {flash [partition-number:]filename1 | rom alias filename2}
Cisco 1600 Series and Cisco 3600 Series Routers
tftp-server flash [device:][partition-number:]filename
no tftp-server flash [device:][partition-number:]filename
Cisco 7000 Family Routers
tftp-server flash device:filename
no tftp-server flash device:filename
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
You can specify multiple filenames by repeating the tftp-server command. The system sends a copy of the system image contained in ROM or one of the system images contained in Flash memory to any client that issues a TFTP Read Request with this filename.
If the specified filename1 or filename2 argument exists in Flash memory, a copy of the Flash image is sent. On systems that contain a complete image in ROM, the system sends the ROM image if the specified filename1 or filename2 argument is not found in Flash memory.
Images that run from ROM cannot be loaded over the network. Therefore, it does not make sense to use TFTP to offer the ROMs on these images.
On the Cisco 7000 family routers, the system sends a copy of the file contained on one of the Flash memory devices to any client that issues a TFTP Read Request with its filename.
Examples
In the following example, the system uses TFTP to send a copy of the version-10.3 file located in Flash memory in response to a TFTP Read Request for that file. The requesting host is checked against access list 22.
tftp-server flash version-10.3 22In the following example, the system uses TFTP to send a copy of the ROM image gs3-k.101 in response to a TFTP Read Request for the gs3-k.101 file:
tftp-server rom alias gs3-k.101In the following example, the system uses TFTP to send a copy of the version-11.0 file in response to a TFTP Read Request for that file. The file is located on the Flash memory card inserted in slot 0.
tftp-server flash slot0:version-11.0The following example enables a Cisco 3600 series router to operate as a TFTP server. The source file c3640-i-mz is in the second partition of internal Flash memory.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.router(config)# tftp-server flash flash:2:dirt/gate/c3640-i-mzIn the following example, the source file is in the second partition of the Flash memory PC card in slot 0 on a Cisco 3600 series:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# tftp-server flash slot0:2:dirt/gate/c3640-j-mzThe following example enables a Cisco 1600 series router to operate as a TFTP server. The source file c1600-i-mz is in the second partition of Flash memory:
router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.router(config)# tftp-server flash flash:2:dirt/gate/c1600-i-mzRelated Commands
tftp-server system
The tftp-server system command has been replaced by the tftp-server command. See the description of the tftp-server command in this chapter for more information.
threshold
To set the rising threshold (hysteresis) that generates a reaction event and stores history information for a Cisco IOS IP Service Level Agreements (SLAs) operation, use the threshold command in the appropriate submode of IP SLA monitor configuration or RTR configuration mode. To return to the default value, use the no form of this command.
threshold milliseconds
no threshold
Syntax Description
milliseconds
Number of milliseconds required for a rising threshold to be declared. The default value is 5000 ms.
Defaults
5000 ms
Command Modes
IP SLA Monitor Configuration
DHCP configuration (config-sla-monitor-dhcp)
DLSw configuration (config-sla-monitor-dlsw)
DNS configuration (config-sla-monitor-dns)
Frame Relay configuration (config-sla-monitor-frameRelay)
FTP configuration (config-sla-monitor-ftp)
HTTP configuration (config-sla-monitor-http)
ICMP echo configuration (config-sla-monitor-echo)
ICMP path echo configuration (config-sla-monitor-pathEcho)
ICMP path jitter configuration (config-sla-monitor-pathJitter)
TCP connect configuration (config-sla-monitor-tcp)
UDP echo configuration (config-sla-monitor-udp)
UDP jitter configuration (config-sla-monitor-jitter)
VoIP configuration (config-sla-monitor-voip)RTR Configuration
DHCP configuration (config-rtr-dhcp)
DLSw configuration (config-rtr-dlsw)
DNS configuration (config-rtr-dns)
Frame Relay configuration (config-rtr-frameRelay)
FTP configuration (config-rtr-ftp)
HTTP configuration (config-rtr-http)
ICMP echo configuration (config-rtr-echo)
ICMP path echo configuration (config-rtr-pathEcho)
ICMP path jitter configuration (config-rtr-pathJitter)
TCP connect configuration (config-rtr-tcp)
UDP echo configuration (config-rtr-udp)
UDP jitter configuration (config-rtr-jitter)
Note
Command History
11.2
This command was introduced.
12.3(7)T
The same functionality of this command was made available using the ip sla monitor reaction-configuration command.
Usage Guidelines
The value specified for the threshold command must not exceed the value specified for the timeout command.
IP SLAs Operation Configuration Dependence on Cisco IOS Release
The Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 184). You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation.
The configuration mode for the threshold command varies depending on the Cisco IOS release you are running (see Table 184) and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the ICMP echo operation type is configured, you would enter the threshold command in ICMP echo configuration mode (config-sla-monitor-echo) within IP SLA monitor configuration mode.
Examples
In the following examples, the threshold of IP SLAs ICMP echo operation 1 is set to 2500 ms. Note that the Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 184).
IP SLA Monitor Configuration
ip sla monitor 1type echo protocol ipIcmpEcho 172.16.1.176threshold 2500!ip sla monitor schedule 1 start-time nowRTR Configuration
rtr 1type echo protocol ipIcmpEcho 172.16.1.176threshold 2500!rtr schedule 1 start-time nowRelated Commands
timeout
To set the amount of time a Cisco IOS IP Service Level Agreements (SLAs) operation waits for a response from its request packet, use the timeout command in the appropriate submode of IP SLA monitor configuration or RTR configuration mode. To return to the default value, use the no form of this command.
timeout milliseconds
no timeout
Syntax Description
milliseconds
Number of milliseconds (ms) the operation waits to receive a response from its request packet.
Defaults
The default timeout value will vary depending on the type of IP SLAs operation you are configuring.
Command Modes
IP SLA Monitor Configuration
DHCP configuration (config-sla-monitor-dhcp)
DLSw configuration (config-sla-monitor-dlsw)
DNS configuration (config-sla-monitor-dns)
Frame Relay configuration (config-sla-monitor-frameRelay)
FTP configuration (config-sla-monitor-ftp)
HTTP configuration (config-sla-monitor-http)
ICMP echo configuration (config-sla-monitor-echo)
ICMP path echo configuration (config-sla-monitor-pathEcho)
ICMP path jitter configuration (config-sla-monitor-pathJitter)
TCP connect configuration (config-sla-monitor-tcp)
UDP echo configuration (config-sla-monitor-udp)
UDP jitter configuration (config-sla-monitor-jitter)
VoIP configuration (config-sla-monitor-voip)RTR Configuration
DHCP configuration (config-rtr-dhcp)
DLSw configuration (config-rtr-dlsw)
DNS configuration (config-rtr-dns)
Frame Relay configuration (config-rtr-frameRelay)
FTP configuration (config-rtr-ftp)
HTTP configuration (config-rtr-http)
ICMP echo configuration (config-rtr-echo)
ICMP path echo configuration (config-rtr-pathEcho)
ICMP path jitter configuration (config-rtr-pathJitter)
TCP connect configuration (config-rtr-tcp)
UDP echo configuration (config-rtr-udp)
UDP jitter configuration (config-rtr-jitter)
Note
Command History
Usage Guidelines
Use the timeout command to set how long the operation waits to receive a response from its request packet, and use the frequency command to set the rate at which the IP SLAs operation restarts. The value specified for the timeout command cannot be greater than the value specified for the frequency command.
IP SLAs Operation Configuration Dependence on Cisco IOS Release
The Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 185). You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation.
The configuration mode for the timeout command varies depending on the Cisco IOS release you are running (see Table 185) and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the ICMP echo operation type is configured, you would enter the timeout command in ICMP echo configuration mode (config-sla-monitor-echo) within IP SLA monitor configuration mode.
Examples
In the following examples, the timeout value for IP SLAs ICMP echo operation 1 is set for 2500 ms. Note that the Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 185).
IP SLA Monitor Configuration
ip sla monitor 1type echo protocol ipIcmpEcho 172.16.1.176timeout 2500!ip sla monitor schedule 1 start-time nowRTR Configuration
rtr 1type echo protocol ipIcmpEcho 172.16.1.176timeout 2500!rtr schedule 1 start-time nowRelated Commands
time-period
To set the time increment for automatically saving an archive file of the current running configuration in the Cisco IOS configuration archive, use the time-period command in archive configuration mode. To disable this function, use the no form of this command.
time-period minutes
no time-period minutes
Syntax Description
minutes
Specifies how often, in minutes, to automatically save an archive file of the current running configuration in the Cisco IOS configuration archive.
Defaults
By default, no time increment is set.
Command Modes
Archive configuration
Command History
12.3(7)T
This command was introduced.
12.2(25)S
This command was integrated into Cisco IOS Release 12.2(25)S.
Usage Guidelines
Note
If this command is configured, an archive file of the current running configuration is automatically saved after the given time specified by the minutes argument. Archive files will continue to be automatically saved at this given time increment until this function is disabled. Use the maximum command to set the maximum number of archive files of the running configuration to be saved.
Note
Examples
In the following example, a value of 20 minutes is set as the time increment for which to automatically save an archive file of the current running configuration in the Cisco IOS configuration archive:
Router(config)# archiveRouter(config-archive)# path disk0:myconfigRouter(config-archive)# time-period 20Related Commands
time-range
To enable time-range configuration mode and define time ranges for functions (such as extended access lists), use the time-range command in global configuration mode. To remove the time limitation, use the no form of this command.
time-range time-range-name
no time-range time-range-name
Syntax Description
time-range-name
Desired name for the time range. The name cannot contain a space or quotation mark, and must begin with a letter.
Defaults
None
Command Modes
Global configuration
Command History
Usage Guidelines
The time-range entries are identified by a name, which is referred to by one or more other configuration commands. Multiple time ranges can occur in a single access list or other feature.After the time-range command, use the periodic time-range configuration command, the absolute time-range configuration command, or some combination of them to define when the feature is in effect. Multiple periodic commands are allowed in a time range; only one absolute command is allowed.
Tip
Examples
The following example denies HTTP traffic on Monday through Friday from 8:00 a.m. to 6:00 p.m. The example allows UDP traffic on Saturday and Sunday from noon to midnight only.
time-range no-httpperiodic weekdays 8:00 to 18:00!time-range udp-yesperiodic weekend 12:00 to 24:00!ip access-list extended strictdeny tcp any any eq http time-range no-httppermit udp any any time-range udp-yes!interface ethernet 0ip access-group strict inRelated Commands
tos
To define a type of service (ToS) byte in the IP header of a Cisco IOS IP Service Level Agreements (SLAs) operation, use the tos command in the appropriate submode of IP SLA monitor configuration or RTR configuration mode. To return to the default value, use the no form of this command.
tos number
no tos
Syntax Description
Defaults
The default type-of-service value is 0.
Command Modes
IP SLA Monitor Configuration
HTTP configuration (config-sla-monitor-http)
ICMP echo configuration (config-sla-monitor-echo)
ICMP path echo configuration (config-sla-monitor-pathEcho)
ICMP path jitter configuration (config-sla-monitor-pathJitter)
TCP connect configuration (config-sla-monitor-tcp)
UDP echo configuration (config-sla-monitor-udp)
UDP jitter configuration (config-sla-monitor-jitter)RTR Configuration
HTTP configuration (config-rtr-http)
ICMP echo configuration (config-rtr-echo)
ICMP path echo configuration (config-rtr-pathEcho)
ICMP path jitter configuration (config-rtr-pathJitter)
TCP connect configuration (config-rtr-tcp)
UDP echo configuration (config-rtr-udp)
UDP jitter configuration (config-rtr-jitter)
Note
Command History
Usage Guidelines
The ToS value is an 8-bit field in IP headers. This field contains information such as precedence and ToS. This information is useful for policy routing and for features like Committed Access Rate (CAR), where routers examine ToS values.
When the type of service is defined for an operation, the IP SLAs Responder will reflect the ToS value it receives.
IP SLAs Operation Configuration Dependence on Cisco IOS Release
The Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 186). You must configure the type of IP SLAs operation (such as User Datagram Protocol [UDP] jitter or Internet Control Message Protocol [ICMP] echo) before you can configure any of the other parameters of the operation.
The configuration mode for the tos command varies depending on the Cisco IOS release you are running (see Table 186) and the operation type configured. For example, if you are running Cisco IOS Release 12.4 and the ICMP echo operation type is configured, you would enter the tos command in ICMP echo configuration mode (config-sla-monitor-echo) within IP SLA monitor configuration mode.
Examples
In the following examples, IP SLAs operation 1 is configured as an ICMP echo operation with destination IP address 172.16.1.176. The ToS value is set to 0x80. Note that the Cisco IOS command used to begin configuration for an IP SLAs operation varies depending on the Cisco IOS release you are running (see Table 186).
IP SLA Monitor Configuration
ip sla monitor 1type echo protocol ipIcmpEcho 172.16.1.176tos 0x80!ip sla monitor schedule 1 start-time nowRTR Configuration
rtr 1type echo protocol ipIcmpEcho 172.16.1.176tos 0x80!rtr schedule 1 start-time nowRelated Commands
traceroute
To discover the routes that packets will actually take when traveling to their destination address, use the traceroute command in user EXEC or privileged EXEC mode.
traceroute [vrf vrf-name] [protocol] destination
Syntax Description
Defaults
When not specified, the protocol argument is determined by the software examining the format of the destination argument. For example, if the software finds a destination argument in IP format, the protocol value defaults to IP.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The traceroute command works by taking advantage of the error messages generated by routers when a datagram exceeds its hop limit value.
The traceroute command starts by sending probe datagrams with a hop limit of 1. Including a hop limit of 1 with a probe datagram causes the neighboring routers to discard the probe datagram and send back an error message. The traceroute command sends several probes with increasing hop limits and displays the round-trip time for each.
The traceroute command sends out one probe at a time. Each outgoing packet might result in one or more error messages. A time-exceeded error message indicates that an intermediate router has seen and discarded the probe. A destination unreachable error message indicates that the destination node has received and discarded the probe because the hop limit of the packet reached a value of 0. If the timer goes off before a response comes in, the traceroute command prints an asterisk (*).
The traceroute command terminates when the destination responds, when the hop limit is exceeded, or when the user interrupts the trace with the escape sequence. By default, to invoke the escape sequence, type Ctrl-^ X—by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing the X key.
To use nondefault parameters and invoke an extended traceroute test, enter the command without a protocol or destination argument in privileged EXEC mode. You are stepped through a dialog to select the desired parameters. Extended traceroute tests are not supported in user EXEC mode. The user-level traceroute feature provides a basic trace facility for users who do not have system privileges. The destination argument is required in user EXEC mode.
If the system cannot map an address for a host name, it returns a "%No valid source address for destination" message.
Resolving the AS with Interactive VRF Traceroute
In the noninteractive mode, the traceroute vrf command always resolves the AS in the global routing table. A destination address is required when you use the noninteractive command. Here, for example, the address is 10.0.0.3.
Router# traceroute vrf green 10.0.0.3In the interactive mode, a line in the traceroute vrf command allows you to select the global routing table or VRF table to resolve the AS number of a host address or to choose not to resolve the AS:
Resolve AS number in (G)lobal table, (V)RF or(N)one [G]:If you do not select one of these options to resolve the AS, the AS is resolved in the global routing table (default behavior).
The following example shows you the line where you select the routing table option that best represents the configuration of your network:
Router# traceroute vrf greenProtocol [ip]:Target IP address: 10.0.0.3Source address:Numeric display [n]:Resolve AS number in (G)lobal table, (V)RF or(N)one [G]:VRFTimeout in seconds [3]:. . .
Note
If you select N(one), the AS is not resolved, and the AS is not indicated in the output of the command. For example:
Tracing the route to 10.0.0.31 10.1.1.9 [MPLS: Labels 25/45 Exp 0] 4 msec 0 msec 0 msec2 10.1.1.1 [MPLS: Labels 26/45 Exp 0] 0 msec 4 msec 0 msec3 10.12.1.101 [MPLS: Labels 23/45 Exp 0] 0 msec 0 msec 0 msec4 10.12.1.6 [MPLS: Labels 19/45 Exp 0] 4 msec 0 msec 0 msec5 10.12.1.41 [MPLS: Label 45 Exp 0] 0 msec 4 msec 0 msec6 10.12.1.42 0 msec 0 msec 0 msec7 10.0.0.3 4 msec * 0 msecIf you select (V)RF, the AS is resolved in the VRF table, and the AS is indicated in the output of the command. For example:
Tracing the route to 10.0.0.31 10.1.1.9 [AS 100] [MPLS: Labels 25/45 Exp 0] 0 msec 4 msec 0 msec2 10.1.1.1 [AS 100] [MPLS: Labels 26/45 Exp 0] 0 msec 0 msec 0 msec3 10.12.1.101 [AS 100] [MPLS: Labels 23/45 Exp 0] 4 msec 0 msec 0 msec4 10.12.1.6 [AS 100] [MPLS: Labels 19/45 Exp 0] 0 msec 4 msec 0 msec5 10.12.1.41 [AS 100] [MPLS: Label 45 Exp 0] 0 msec 0 msec 4 msec6 10.12.1.42 [AS 100] 0 msec 0 msec 0 msec7 10.0.0.3 [AS 100] 0 msec * 0 msecThe path from a provider edge (PE)1 router to a PE2 router might contain routes from the global routing table and a VRF table. If that happens, you need to enter two interactive traceroute vrf commands at the PE1 router to trace the route to a customer edge (CE)2 router: one selecting the global routing table, and the other selecting a VRF table. You can then determine the valid and invalid AS numbers based on your knowledge of the network topology. In an interautonomous system (Inter-AS) network, however, you might not know the whole topology.
Common Traceroute Problems
Due to bugs in the IP implementation of various hosts and routers, the IP traceroute command might behave in an unexpected manner.
Not all destinations respond correctly to a probe message by sending back an "ICMP port unreachable" message. A long sequence of asterisks, terminating only when the maximum hop limit has been reached, might indicate this problem.
There is a known problem with the way some hosts handle an "ICMP TTL exceeded" message. Some hosts generate an "ICMP" message, but they reuse the Time to Live (TTL) of the incoming packet. Because the TTL of the incoming packet is 0, the Internet Control Message Protocol (ICMP) packets do not make it back. When you trace the path to such a host, you might see a set of TTL values with asterisks (*). Eventually the hop limit gets high enough that the "ICMP" message can get back. For example, if the host is six hops away, traceroute times out on responses 6 through 11.
Note
Examples
The following user EXEC example shows the IPv4 traceroute output that results when a destination host name has been specified:
Router> traceroute host77-name.domainZZ-name.comType escape sequence to abort.Tracing the route to host77-name.domainZZ-name.com (10.0.0.73)1 host1-name.domain1-name.com (192.168.1.6) 1000 msec 8 msec 4 msec2 host33-name.serviceprovider8-name.com (192.168.16.2) 8 msec 8 msec 8 msec3 host2-name.college2-name.edu (192.168.110.225) 8 msec 4 msec 4 msec4 host44-name.domain2-name.NET (192.168.254.6) 8 msec 8 msec 8 msec5 host22-name.serviceprovider99-name.com (192.168.3.8) 12 msec 12 msec 8 msec6 host-name5.domain5-name.com (192.168.195.1) 216 msec 120 msec 132 msec7 host77-name.domainZZ-name.com (10.0.0.73) 412 msec 628 msec 664 msecTable 187 describes the significant fields shown in the display.
The following user EXEC example shows the IPv6 traceroute output that results when a destination host name has been specified:
Router> traceroute host8-name.domainBB-name.noType escape sequence to abort.Tracing the route to host8-name.domainBB-name.no (3FFE:2A00:100:7FF9::2)1 3FFE:C:00:E:13::2 28 msec 24 msec *2 3FFE:2A00:100:7FF8::2 208 msec 204 msec3 host32-name.domainHH-name.net (3FFE:2A00:100:7FF8::1) 276 msec * 276 msec4 host8-name.domainBB-name.no (3FFE:2A00:100:7FF9::2) 292 msec 292 msec 296 msec
Note
Table 188 describes the significant fields shown in the display.
The following privileged EXEC example shows the extended dialog of the traceroute command when IPv4 is used:
Router# tracerouteProtocol [ip]:Target IP address: host77-name.domainZZ-name.comSource address:Numeric display [n]:Timeout in seconds [3]:Probe count [3]:Minimum Time to Live [1]:Maximum Time to Live [30]:Port Number [33434]:Loose, Strict, Record, Timestamp, Verbose[none]:Type escape sequence to abort.Tracing the route to host77-name.domainZZ-name.com (10.0.0.73)1 host1-name.domain1-name.com (192.168.1.6) 1000 msec 8 msec 4 msec2 host33-name.serviceprovider8-name.com (192.168.16.2) 8 msec 8 msec 8 msec3 host2-name.college2-name.edu (192.168.110.225) 8 msec 4 msec 4 msec4 host44-name.domain2-name.NET (192.168.254.6) 8 msec 8 msec 8 msec5 host22-name.serviceprovider99-name.com (192.168.3.8) 12 msec 12 msec 8 msec6 host-name5.domain5-name.com (192.168.195.1) 216 msec 120 msec 132 msec7 host77-name.domainZZ-name.com (10.0.0.73) 412 msec 628 msec 664 msecIf an unknown host name is used in the Target IP address field, the software queries a Domain Name System (DNS) server to resolve the unknown host name to its IP address. In the following example, a DNS server (IP address 192.168.7.93) is queried for the unknown host name college9-name.edu:
Router# tracerouteProtocol [ip]:Target IP address: college9-name.eduTranslating "college9-name.edu"...domain server (192.168.7.93) [OK]Table 189 describes the fields that are unique to the extended traceroute sequence that is shown in the display.
The following privileged EXEC example shows the extended dialog of the traceroute command when IPv6 is used:
Router# tracerouteProtocol [ip]: ipv6Target IP address: host8-name.domainBB-name.noSource IPv6 address:Numeric display [no]:Timeout in seconds [3]:Probe count [3]:Minimum Time to Live [1]:Maximum Time to Live [30]:Priority [0]:Port Number [33434]:Type escape sequence to abort.Tracing the route to host8-name.domainBB-name.no (3FFE:2A00:100:7FF9::2)1 3FFE:C:00:E:13::2 28 msec 24 msec *2 3FFE:2A00:100:7FF8::2 208 msec 204 msec3 host32-name.domainHH-name.net (3FFE:2A00:100:7FF8::1) 276 msec * 276 msec4 host8-name.domainBB-name.no (3FFE:2A00:100:7FF9::2) 292 msec 292 msec 296 msecIf an unknown host name is used in the Target IP address field, software queries a DNS server to resolve the unknown host name to an IP address. In the following example, a DNS server (IP address 192.168.7.93) is queried for the unknown host name host8-name.domainBB-name.no:
Router# tracerouteProtocol [ip]: ipv6Target IP address: host8-name.domainBB-name.noTranslating "host8-name.domainBB-name.no"...domain server (192.168.7.93) [OK]Table 190 describes the fields that are unique to the extended traceroute sequence shown in the display.
Table 191 describes the characters that can appear in traceroute command output when IPv4 is used.
Table 192 describes the characters that can appear in the traceroute command output when IPv6 is used.
transfer-interval
To configure how long bulk statistics should be collected before a bulk statistics transfer is initiated, use the transfer-interval command in Bulk Statistics Transfer configuration mode. To remove a previously configured interval from a bulk statistics configuration, use the no form of this command.
transfer-interval minutes
no transfer-interval minutes
Syntax Description
minutes
Length of time, in minutes, that the system should collect MIB data before attempting the transfer operation. The valid range is from 1 to 2147483647. The default is 30 minutes.
Defaults
Bulk statistics file transfer operations start 30 minutes after the enable (bulkstat) command is used.
Command Modes
Bulk Statistics Transfer configuration (config-bulk-tr)
Command History
Usage Guidelines
Because bulk statistics data is collected into a new file once a transfer attempt begins, this command also configures the collection interval.
If the maximum buffer size for a bulk statistics file is reached before the transfer interval time expires, the transfer operation will still be initiated, and bulk statistics MIB data will be collected into a new file in the system buffer.
Examples
The following example configures the transfer interval for the bulk statistics configuration bulkstat1 to 20 minutes:
Router(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# transfer-interval 20Related Commands
snmp mib bulkstat transfer
Names a bulk statistics transfer configuration and enters Bulk Statistics Transfer configuration mode.
transport event
To specify that inventory events are sent out by the CNS inventory agent, use the transport event command in CNS inventory configuration mode. To disable the transport of inventory events, use the no form of this command.
transport event
no transport event
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
CNS inventory configuration
Command History
Usage Guidelines
Use this command to send out inventory requests with each CNS inventory agent message. When configured, the routing device will respond to queries from the CNS Event Bus. Online insertion and removal (OIR) events on the routing device will be reported to the CNS Event Bus.
Examples
The following example shows how to enable the CNS inventory agent and configure it to send out inventory events:
Router(config)# cns inventoryRouter(cns_inv)# transport eventRelated Commands
cns inventory
Enables the CNS inventory agent and enters CNS inventory configuration mode.
ttl dns
To configure the number of seconds for which an answer received from the boomerang client will be cached by the Domain Name System (DNS) client, use the ttl dns command in boomerang configuration mode. To remove this command from the configuration file and restore the system to its default condition with respect to this command, use the no form of this command.
ttl dns seconds
no ttl dns seconds
Syntax Description
seconds
Number of seconds for which an answer received from the boomerang client will be cached by the DNS client. Range is from 10 to 2147483647.
Defaults
No default behavior or values.
Command Modes
Boomerang configuration
Command History
Usage Guidelines
The ttl dns command can be used only on a Director Response Protocol (DRP) agent. The boomerang client is the DRP agent.
The ttl dns command configures the number of seconds for which the DNS client can cache a boomerang reply from a boomerang client.
Examples
In the following example, the number of seconds for which the DNS client can cache a boomerang reply from a boomerang client is configured as 10:
Router(config)# ip drp domain www.boom1.comRouter(config-boomerang)# ttl dns 10Router# show running-config...ip drp domain www.boom1.comdns-ttl 10Related Commands
ttl ip
To configure the IP time-to-live (TTL) value for the boomerang response packets sent from the boomerang client to the DNS client, use the ttl ip command in boomerang configuration mode. To remove this command from the configuration file and restore the system to its default condition with respect to this command, use the no form of this command.
ttl ip hops
no ttl ip hops
Syntax Description
hops
Number of hops that occur between the boomerang client and the DNS client before the boomerang response packet fails. Range is from 1 to 255.
Defaults
No default behavior or values.
Command Modes
Boomerang configuration
Command History
Usage Guidelines
The ttl ip command can be used only on a Director Response Protocol (DRP) agent. The boomerang client is the DRP agent.
The ttl ip command configures the maximum number of hops allowed between the boomerang client and the DNS client, after which the boomerang response packet fails. If the user wants to restrict the contending proxies only to nearby ones, the value of the ttl ip command can be set to a specific number within the allowed range. Any proxy outside of this range will be automatically disqualified in the boomerang race because its replies will never reach the DNS client. Because the ttl ip command specifies the number of hops for which a response from a client will live, it allows faraway proxies to avoid wasting bandwidth.
Examples
In the following example, the number of hops that occur between the boomerang client and the DNS client before the boomerang response packet fails is configured as 2:
Router(config)# ip drp domain www.boom1.comRouter(config-boomerang)# ttl ip 2Router# show running-config...ip drp domain www.boom1.comip-ttl 2Related Commands
