- absolute-timeout
- access-class (LAT)
- arap dedicated
- arap enable
- arap net-access-list
- arap network
- arap require-manual-password
- arap timelimit
- arap warningtime
- arap zonelist
- async default ip address
- authentication-retries
- autocommand
- banner (transport map)
- busy-message
- clear entry
- connect
- connection wait
- description (ruleset)
- flu sh-at-acti vation
- ip alias
- ipx nasi-server enable
- keymap
- keymap-type
- lat
- lat access-list
- lat enabled
- lat group-list
- lat host-buffers
- lat ka-timer
- lat node
- lat out-group
- lat remote-modification
- lat retransmit-limit
- lat server-buffers
- lat service enabled
- lat service-host
- lat service ident
- lat service password
- lat service rating
- lat service rotary
- lat service-announcements
- lat service-group
- lat service-responder
- lat service-timer
- lat vc-sessions
- lat vc-timer
- line
- login (EXEC)
- login (line)
- login-string
- match (ruleset)
- monitor traffic line
- options (ruleset)
- pad
- resume (setting X.3 PAD parameters)
- resume (switching sessions)
- rlogin
- rlogin trusted-localuser-source
- rlogin trusted-remoteuser-source local
- rsa keypair-name
- rxspeed
Terminal Services Commands
absolute-timeout
To set the interval for closing the connection, use the absolute-timeout command in line configuration mode. To restore the default, use the no form of this command.
Syntax Description
Number of minutes after which the user session will be terminated. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Use the absolute-timeout command line configuration command to configure the EXEC to terminate when the configured number of minutes occurs on the virtual terminal (vty) line. The absolute-timeout command terminates the connection after the specified time period has elapsed, regardless of whether the connection is being used at the time of termination. You can specify an absolute-timeout value for each port. The user is given 20 seconds notice before the session is terminated. You can use this command along with the logout-warning command to notify users of an impending logout.
Cisco IOS software also provides the session-timeout and exec-timeout line configuration commands for releasing lines when they have been idle for too long.
You can set the absolute-timeout command and an AppleTalk Remote Access Protocol (ARAP) timeout for the same line; however, this command supersedes any timeouts set in ARAP. Additionally, ARAP users will receive no notice of any impending termination if you use this command.
Examples
The following example sets an interval of 60 minutes on line 5:
Related Commands
access-class (LAT)
To define restrictions on incoming and outgoing connections, use the access-class command in line configuration mode. To remove the access list number, use the no form of this command.
access-class access-list-number { in [ vrf-also ] | out }
no access-class access-list-number { in | out }
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
This command defines access list numbers that will then be used with the lat access-list command to specify the access conditions.
The value supplied for the access-list-number argument is used for all protocols supported by the Cisco IOS software. If you are already using an IP access list, you must define LAT and possibly X.25 access lists permitting connections to all devices, to emulate the behavior of previous software versions.
When both IP and LAT connections are allowed from a terminal line and an IP access list is applied to that line with the access-class line configuration command, you must also create a LAT access list with the same number if you want to allow any LAT connections from that terminal. You can specify only one incoming and one outgoing access list number for each terminal line.When checking LAT access lists, if the specified list does not exist, the system denies all LAT connections.
If you do not specify the vrf-also keyword, incoming Telnet connections from interfaces that are part of a VRF are rejected.
Examples
The following example configures an incoming access class on vty line 4:
Related Commands
|
|
|
|---|---|
arap dedicated
To configure a line to be used only as an AppleTalk Remote Access (ARA) connection, use the arap dedicated command in line configuration mode. To return the line to interactive mode, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following example configures line 3 to be used only for ARA connections:
arap enable
To enable AppleTalk Remote Access (ARA) for a line, use the arap enable command in line configuration mode. To disable ARA, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following example enables ARA on line 3:
Related Commands
|
|
|
|---|---|
arap net-access-list
To control Apple Macintosh access to networks, use the arap net-access-list command in line configuration mode. To return to the default setting, use the no form of this command.
arap net-access-list net-access-list-number
no arap net-access-list net-access-list-number
Syntax Description
One of the list values configured using the AppleTalk access-list cable-range , access-list include s , access-list network , access-list other-access , or access-list within commands. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
You can use the arap net-access-list command to apply access lists defined by the access-list cable-range , access-list includes , access-list network , access-list other-access, or access-list within commands.
You cannot use the arap net-access-list command to apply access lists defined by the access-list zone or access-list additional-zones commands.
Examples
In the following example, ARA is enabled on line 3 and the Macintosh will have access to the AppleTalk access list numbered 650:
Related Commands
arap network
To create a new network or zone and cause it to be advertised, use the arap network command in global configuration mode. To prevent a new network or zone from being advertised, use the no form of this command.
arap network [ network-number ] [ zone-name ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
This is a required command. ARAP does not run without it in Cisco IOS Release 10.2 and later.
Examples
The following example creates a new zone named test zone:
arap require-manual-password
To require users to enter their password manually at the time they log in, use the arap require-manual-password command in line configuration mode. To disable the manual password-entry requirement, use the no form of this command.
no arap require-manual-password
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
This command only works for AppleTalk Remote Access Protocol (ARAP) 2.0 connections.
Examples
The following example forces users to enter their passwords manually at the time they log in, rather than use a saved password:
Related Commands
arap timelimit
To set the maximum length of an AppleTalk Remote Access (ARA) session for a line, use the arap timelimit command in line configuration mode. To return to the default of unlimited session length, use the no form of this command.
Syntax Description
(Optional) Maximum length of time, in minutes, for a session. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
After the specified length of time, the session will be terminated.
Examples
The following example specifies a maximum length of 20 minutes for ARA sessions:
Related Commands
|
|
|
|---|---|
arap warningtime
To set when a disconnect warning message is displayed, use the arap warningtime command in line configuration mode. To disable this function, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
This command can only be used if a session time limit has been configured on the line.
Examples
The following example shows a line configured for 20-minute AppleTalk Remote Access (ARA) sessions, with a warning 17 minutes after the session is started:
Related Commands
|
|
|
|---|---|
arap zonelist
To control which zones the Apple Macintosh client sees, use the arap zonelist command in line configuration mode. To disable the default setting, use the no form of this command.
arap zonelist zone-access-list-number
no arap zonelist zone-access-list-number
Syntax Description
One of the list values configured using the AppleTalk access-list zone or access-list additional-zones command. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
You can use the arap zonelist command to apply access lists defined by the access-list zone and access-list additional-zones commands.
You cannot use the arap zonelist command to apply access lists defined by the access-list network command.
Hiding a zone from users is not the same as preventing them from sending and receiving packets from the networks that make up that zone. For true security, an arap net-access-list command must be issued to prevent traffic to and from those networks.
Examples
The following example enables AppleTalk Remote Access (ARA) on line 3; the Macintosh will see only zones permitted by access list 650.
Related Commands
|
|
|
|---|---|
Defines the default action to take for access checks that apply to zones. |
|
async default ip address
The async default ip address command is replaced by the peer default ip address command. See the peer default ip address command for more information.
authentication-retries
To specify the number of authentication retries before dropping the connection for a persistent Secure Shell (SSH) connection attempt, use the authentication-retries transport map configuration mode command. To restore the default setting of three retries, use the no form of the command.
authentication-retries number-of-retries
Syntax Description
Specifies the number of retries before the connection attempt is dropped. |
Command Default
Command Modes
Transport map configuration (config-tmap)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Routers. |
Usage Guidelines
This command configures the number of authentication retries for users using SSH to connect to a Management Ethernet interface with an applied transport map.
Examples
In the following example, a transport map is configured that will apply the following settings to any users attempting to access the Management Ethernet port via SSH:
- Users using SSH wait for the IOS process to become active, but enter diagnostic mode if the attempt to access IOS is interrupted.
- The RSA keypair name is “sshkeys”.
- The connection allows one authentication retry.
- The banner “--Welcome to Diagnostic Mode--” appears if diagnostic mode is entered as a result of SSH handling through this transport map.
- The banner “--Waiting for IOS Process--” appears if the connection is waiting for the IOS process to be come active.
The transport map is then applied to the interface when the transport type persistent ssh input command is entered to enable persistent SSH.
Router(config-tmap)# authentication-retries 1
Router(config-tmap)# banner diagnostic X
Enter TEXT message. End with the character 'X'.
--Welcome to Diagnostic Mode--
Related Commands
autocommand
To configure the system to automatically execute a specific EXEC command when it connects to a port, use the autocommand command in line configuration mode. To disable the automatic execution, use the no form of this command.
autocommand [ no-suppress-linenumber ] command-text
Syntax Description
Defaults
Command Modes
Line configuration (config-line)
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
The line number message enables users to track the port that is currently connected. The line numbers for these messages are provided by the service linenumber command. The autocommand command generally suppresses the line number message. However, when autocommand is used with the no-suppress-linenumber keyword, the line number messages are not suppressed.
Examples
The following example shows how to force an automatic connection to host21:
Related Commands
|
|
|
|---|---|
Configures Cisco IOS software to display line number information after the EXEC or incoming banner. |
banner (transport map)
To create a banner message that will be seen by users entering diagnostic mode or waiting for the IOS process as a result of a transport map configuration configured on a console port or for users using Telnet or Secure Shell (SSH), use the banner command in transport map configuration mode. To restore the default setting of no diagnostic or no wait banner, use the no form of the command.
banner [ diagnostic | wait ] banner-message
Syntax Description
Command Default
There are no banners configured for transport maps by default.
Command Modes
Transport map configuration (config-tmap)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Routers. |
Usage Guidelines
Configuring the diagnostic and wait banners is optional but recommended. The banners are especially useful as indicators to users of the status of their Telnet, SSH, or console port connection attempts.
When defining the banner-message, it is advisable to press Enter before entering the final delimiting character. Pressing Enter moves the cursor down a line and ensures the prompt on the router does not appear on the same line as the banner when the banner posts during a Telnet or SSH session.
The currently applied banner messages can be checked using the show platform software configuration access policy command.
Examples
In the following example, a transport map that will make all Telnet connections wait for the IOS process to become active before connecting to the router, while also allowing the user to interrupt the process and enter diagnostic mode, is configured and applied to the Management Ethernet interface (interface gigabitethernet 0).
A diagnostic and a wait banner are also configured.
The transport map is then applied to the interface when the transport type persistent telnet input command is entered to enable persistent Telnet.
In the following example, a transport map to set console port access policies is created and attached to console port 0. The transport map configuration includes both a diagnostic and a wait banner.
Related Commands
busy-message
To create a “host failed” message that displays when a connection fails, use the busy-message command in global configuration mode. To disable the “host failed” message from displaying on the specified host, use the no form of this command.
busy-message host-name d message d
Syntax Description
Delimiting character of your choice—a pound sign (#), for example. You cannot use the delimiting character in the message. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
This command applies only to Telnet connections.
Follow the busy-message command with one or more blank spaces and a delimiting character of your choice. Then enter one or more lines of text, terminating the message with the second occurrence of the delimiting character.
Defining a “host failed” message for a host prevents all Cisco IOS software-initiated user messages, including the initial message that indicates the connection is “Trying....” The busy-message command can be used in the autocommand command to suppress these messages.
Examples
The following example sets a message that will be displayed on the terminal whenever an attempt to connect to the host named router1 fails. The pound sign (#) is used as a delimiting character.
busy-message router1 #
Cannot connect to host. Contact the computer center.
#
Related Commands
|
|
|
|---|---|
Automatically execute a command when a user connects to a particular line. |
clear entry
To delete an entry from the list of queued host-initiated connections, use the clear entry command in EXEC mode.
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following example deletes pending entry number 3 from the queue:
Related Commands
|
|
|
|---|---|
Displays the list of queued host-initiated connections to a router. |
connect
To log in to a host that supports Telnet, rlogin, or local-area transport (LAT), use the connect command in EXEC mode.
connect host [ port ] [ keyword ]
Syntax Description
(Optional) A decimal TCP port number; the default is the Telnet router port (decimal 23) on the host. |
|
(Optional) One of the keywords listed in Table 1 . |
Command Modes
Command History
Usage Guidelines
Table 1 lists the optional connect command keywords.
With the Cisco IOS software implementation of TCP/IP, you are not required to enter the connect, telnet, lat, or rlogin commands to establish a terminal connection. You can enter only the learned host name—as long as the host name is different from a command word in the Cisco IOS software. The Cisco IOS software assigns a logical name to each connection, and several commands use these names to identify connections. The logical name is the same as the host name, unless that name is already in use, or you change the connection name with the name-connection EXEC command. If the name is already in use, the Cisco IOS software assigns a null name to the connection. To display a list of the available hosts, use the show hosts command. To display the status of all TCP connections, use the show tcp command.
Examples
The following example establishes an encrypted Telnet session from a router to a remote host named host1:
Router> connect host1 /encrypt kerberos
The following example routes packets from the source system named host1 to router1.cisco.com, then to 10.1.0.11, and finally back to host1:
Router> connect host1 /route:router1.cisco.com 10.1.0.11 host1
The following example connects to a host with logical name host1:
Router> host1
The following example suppresses all onscreen messages from the Cisco IOS software during login and logout:
Router> connect host2 /quiet
The following example shows the limited messages displayed when connection is done using the optional /quiet keyword:
Related Commands
connection wait
To specify how users accessing a router using Telnet, Secure Shell (SSH), or the console port will be connected, use the connection wait command in transport map configuration mode. To restore the default setting of waiting for an IOS vty line to become available while also allowing the user to enter diagnostic mode if the connection that is waiting for the IOS vty line is interrupted, use the no or default form of the command.
connection wait [ allow [ interruptable ]| none [ disconnect ]]
no connection wait [ allow [ interruptable ]| none [ disconnect ]]
Syntax Description
Command Default
Command Modes
Transport map configuration (config-tmap)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Routers. |
Usage Guidelines
When connection wait allow interruptable is configured, users enter diagnostic mode by sending a break signal while waiting to connect to the IOS process. The Ctrl-C or Ctrl-Shift-6 sequences are used to send a break signal.
For a persistent Telnet connection to access IOS on the Cisco ASR 1000 Series Routers, local login authentication must be configured for the vty line (the login command in line configuration mode). If local login authentication is not configured, users will not be able to access IOS using a Telnet connection into the Management Ethernet interface with an applied transport map. Diagnostic mode will still be accessible in this scenario.
Examples
In the following example, a transport map that makes all Telnet connections wait for the IOS vty line to become active before connecting to the router, while also allowing the user to interrupt the process and enter diagnostic mode, is configured and applied to the Management Ethernet interface (interface gigabitethernet 0).
A diagnostic and a wait banner are also configured.
The transport map is then applied to the interface when the transport type persistent telnet input command is entered to enable persistent Telnet.
In the following example, a transport map to set console port access policies is created and attached to console port 0.
Related Commands
description (ruleset)
To add a description about a translation ruleset, use the description command in translate ruleset configuration mode. To remove the description, use the no form of this command.
Syntax Description
Defaults
Command Modes
Translate ruleset configuration
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Only one description line is accepted. If you reenter this command, the new description replaces the existing description.
Examples
The following example shows how to add a description to a ruleset:
Related Commands
flush-at-activation
To discard any data or noise characters that are sitting in the input buffer of the asynchronous line before the line is activated, use the flush-at-activation command in line configuration mode. To keep any data or noise characters that are sitting in the input buffer of the asynchronous line before the line is activated, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
For an incoming call on a line configured with modem control (using the modem inout and modem dialin commands), the line will be activated when the data set ready (DSR) signal goes high and will be dropped when the DSR signal goes low. While the line is idle, its input buffer may receive characters; for example, modem result codes such as “NO CARRIER” or “RING” or line noise. Such characters are not useful to the line application. Flushing the line input buffer when the DSR goes high using the flush-at-activation command is the preferred behavior.
Note
To know whether the DSR signal is going high or low, use the debug modem command or the show line command. Output of these commands displays the status of DSR signal.
On most Cisco IOS platforms, there may be up to a one-second delay between when the DSR signal goes high and Cisco IOS activates the line. Therefore, some valid data received from the line may be discarded when you issue the flush-at-activation command. If it is important to process this valid data rather than discarding it and the application is tolerant of receiving bad data, configure the no flush-at-activation command.
The application that is used determines whether the system can differentiate the valid data from the bad data or the system is tolerant of receiving any data. For example, consider that the application used is TCP over IP over PPP. PPP uses a Frame Check Sequence (FCS) in a data frame format to verify the integrity of the received data. If an invalid data pattern is delivered to a PPP receiver, PPP will discard it as a framing or FCS error. So the bad data will not be delivered to the higher layers. Even if some data is delivered up to IP and TCP, TCP has its own FCS which will reject bad data. Therefore, the application is tolerant of receiving the bad data that the line delivers.
Consider another application where incoming character data received from the line is delivered as TCP payload to a server running a pager application. Unless the pager application has implemented its own protocol to verify data integrity, this bad data may cause the pager not to be delivered, or to deliver bad data within the message payload to the receiving pager. So the bad data should not be delivered as payload to the line.
Where an upper-layer framed protocol such as PPP or Serial Line Internet Protocol (SLIP) is always used (asynchronous mode dedicated), the framed protocol may reach link status more quickly when you issue the no flush-at-activation command. Since the framed protocol discards any erroneous data received, you do not have to use the flush-at-activation command.
If the line application is not tolerant of receiving bad data; for example, when you are using character-mode username/password authentication, always use the flush-at-activation command. Otherwise, the bad data may trigger an application failure.
Note Prior to Cisco IOS Release 12.2, the no flush-at-activation command was the default on AS5000 platforms with modem ISDN channel aggregation (MICA) and NextPort modems. However, from Cisco IOS Release 12.3 and later, there is no longer any significant delay between when the modem link reaches steady state (DSR high) and when the line is activated so you do not need to use the no flush-at-activation command.
The modem state STEADY_STATE is mapped to DSR high and TERMINATING is mapped to DSR low when asynchronous lines are the internal digital modem ports.
Examples
The following example shows how to configure lines 1/0 through 1/59 to flush any data in their input buffers when the lines are activated:
Related Commands
|
|
|
|---|---|
Defines the character entered at a vacant terminal to begin a terminal session. |
|
Configures a line to enable a modem attached to the router to accept incoming calls only. |
|
ip alias
To assign an IP address to the service provided on a TCP port, use the ip alias command in interface configuration mode. To remove the specified address for the router, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
A user attempting to establish a connection is connected to the first free line in a rotary group using the Telnet protocol.
The IP address must be on the same network or subnet as the main address of the terminal server, and must not be used by another host on that network or subnet. Connecting to the IP address has the same effect as connecting to the main address of the router, using the argument tcp-port as the TCP port.
You can use the ip alias command to assign multiple IP addresses to the router. For example, in addition to the primary alias address, you can specify addresses that correspond to lines or rotary groups. Using the ip alias command in this way makes connection to a specific rotary group transparent to the user.
When asynchronous mode is implemented, the Cisco IOS software creates the appropriate IP aliases, which map the asynchronous addresses for the lines to which they are connected. This process is automatic and does not require configuration.
Examples
The following example configures connections to IP address 172.30.42.42 to act identically to connections made to the primary IP address of the server on TCP port 3001. In other words, a user is connected to the first free line on port 1 of the rotary group that uses the Telnet protocol.
172.30.42.42 3001
ipx nasi-server enable
To enable NetWare Asynchronous Services Interface (NASI) clients to connect to asynchronous devices attached to your router, use the ipx nasi-server enable command in global configuration mode. To prevent NASI clients from connecting to asynchronous devices through a router, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
When you enter this command, NASI clients can connect to any port on the router, other than the console port, to access network resources. When the user on the NASI client uses the Windows or DOS application to connect to the router, a list of available tty and vty lines appear, beginning with tty1. The user can select the desired outgoing tty or vty port.
To to enable a username and password prompt for authentication, authorization, and accounting purposes, you can configure TACACS+ security on the router, after the user on the NASI client selects a tty or vty port.
Examples
The following example shows a minimum configuration to enable NASI clients dial-in access with TACACS+ authentication:
Related Commands
keymap
To define specific characteristics of keyboard mappings, use the keymap command in global configuration mode. To remove the named keymap from the current image of the configuration file, use the no form of this command.
keymap keymap-name keymap-entry
Syntax Description
Name of the file containing the keyboard mappings. The name can be up to 32 characters long and must be unique. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
The keymap command maps individual keys on a non-TN3270 keyboard to perform the function defined for the TN3270 keyboard. Use the show keymap EXEC command to test for the availability of a keymap.
Do not use the name “default” for a ttycap entry filename or the Cisco IOS software will adopt the newly defined entry as the default.
The guidelines for creating a keymap follow.
A keymap is a keyboard map file. A keymap consists of an entry for a keyboard. The first part of a keymap lists the names of the keyboards that use that entry. These names will often be the same as in the ttycaps (terminal emulation) file, and often the terminals from various ttycap entries will use the same keymap entry. For example, both 925 and 925vb (for 925 with visual bells) terminals would probably use the same keymap entry. There are other circumstances in which it is necessary to specify a keyboard name as the name of the entry (for example, if a user requires a custom key layout).
After the names, which are separated by vertical bars (|), comes an open brace ({), the text that forms the definitions, the a close brace (}), as follows:
Each definition consists of a reserved keyword, which identifies the TN3270 function, followed by an equal sign (=), followed by the various ways to generate this particular function, followed by a semicolon (;), as follows:
Each alternative way to generate the function is a sequence of ASCII characters enclosed inside single quotes (''); the alternatives are separated by vertical bars (|), as follows:
Inside the single quotes, a few characters are special. A caret (^) specifies that the next character is a control (Ctrl) character. The two-character string caret-a (^a) represents Ctrl-a. The caret-A sequence (^A) generates the same code as caret-a (^a). To generate Delete (or DEL), enter the caret-question mark (^?) sequence.
Note The Ctrl-caret combination (Ctrl-^), used to generate a hexadecimal 1E, is represented as two caret symbols in sequence (^^)—not as a caret-backslash-caret combination (^\^).
In addition to the caret, a letter can be preceded by a backslash (\). Because this sequence has little effect for most characters, its use is usually not recommended. In the case of a single quote ( '), the backslash prevents that single quote from terminating the string. In the case of a caret (^), the backslash prevents the caret from having its special meaning. To include the backslash in the string, place two backslashes (\\) in the keymap. Table 2 lists other supported special characters.
|
|
|
|---|---|
Each character in a string needs not be enclosed within single quotes. For example, \E\E\E means three escape characters.
To enter a keymap, provide a unique name for it and explicitly define all special keys you intend to include in it within open and close braces. Also, except for the last line, each line must be terminated with a backslash symbol (\). The last line ends with the closing bracket (}) symbol and an end-of-line character.
When IBM-style TN3270 terminals are emulated, a mapping must be performed between sequences of keys pressed at an ASCII keyboard and the keys available on a TN3270 keyboard. For example, a TN3270 keyboard has a key labeled EEOF that erases the contents of the current field from the location of the cursor to the end. To accomplish this function, the terminal user and a program emulating a TN3270 keyboard must agree on which keys will be typed to invoke the function. The requirements for these sequences follow:
- The first character of the sequence must be outside of the standard ASCII printable characters.
- No sequence can be a complete subset of another sequence (although sequences can share partial elements).
Following are examples of acceptable keymap entries:
Following are examples of unacceptable keymap entries:
In the acceptable example, the keymap entry for pfk1 is not completely included in the keymap entry for pfk2. By contrast, in the unacceptable, or conflicting keymap pair, the sequence used to represent pfk1 is a complete subset of the sequence used to represent pfk11. See the keymap entry provided later in the Examples section of how various keys can be represented to avoid this kind of conflict.
Table 3 lists TN3270 key names that are supported in this keymap. Note that some of the keys do not exist on a TN3270 keyboard. An unsupported function will cause the Cisco IOS software to send a (possibly visual) bell sequence to the terminal.
|
|
|
|---|---|
Please hold output1 |
|
Tab to last nonblank of current or next unprotected (writable) field 1 |
|
|
|
Table 4 lists the proper keys used to emulate each TN3270 function when default key mappings are used.
|
|
|
|
|---|---|---|
| ESC-Space2 |
||
|
|
Examples
The following example is the default entry used by the TN3270 emulation software when it is unable to locate a valid keymap in the active configuration image. Table 3 lists the key names supported by the default Cisco TN3270 keymap.
The following keymap statement maps the “|” character to send EBCDIC 0x6A:
Related Commands
|
|
|
|---|---|
Specifies the keyboard map for a terminal connected to the line. |
|
Tests the availability of a keymap after a connection on a router takes place. |
|
keymap-type
To specify the keyboard map for a terminal connected to the line, use the keymap-type command in line configuration mode. To reset the keyboard type for the line to the default, use the no form of this command.
Syntax Description
Name of a keymap defined within the configuration file of the router. The TN3270 terminal-type negotiations use the specified keymap type when setting up a connection with the remote host. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
This command must follow the corresponding keymap global configuration entry in the configuration file. The TN3270 terminal-type negotiations use the specified keymap type when setting up a connection with the remote host.
Setting the keyboard to a different keymap requires that a keymap be defined with the Cisco IOS software configuration either by obtaining a configuration file over the network that includes the keymap definition or by defining the keyboard mapping using the keymap global configuration command.
Use the command show keymap EXEC command to test for the availability of a keymap.
Examples
The following example sets the keyboard mapping to a keymap named vt100map:
Related Commands
|
|
|
|---|---|
Tests the availability of a keymap after a connection on a router takes place. |
|
lat
To connect to a local-area transport (LAT) host, use the lat command in EXEC mode.
lat name [ node nodename | port portname | /debug ]
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
After entering the lat command, you can quit the connection by pressing Ctrl-C, or complete the connection by entering the password for a given service.
You can have several concurrent LAT sessions open and switch between them. To open a subsequent session, first enter the escape sequence ( Ctrl-Shift-6 then x [ Ctrl^x ] by default) to suspend the current session. Then open a new session.
To list the available LAT services, use the show lat services EXEC command.
You can temporarily define the list of services to which you or another user can connect. To do so, use the terminal lat out-group command to define the group code lists used for connections from specific lines.
To exit a session, simply log off the remote system. Then terminate an active LAT session by entering the exit command.
If your preferred transport is set to lat, you can use the connect command in place of the lat command. Refer to the chapter “Configuring Terminal Operating Characteristics for Dial-In Sessions” in the Cisco IOS Terminal Services Configuration Guide for more information about configuring a preferred transport type. When your preferred transport is set to none or to another protocol, you must use the lat command to connect to a LAT host.
Examples
The following sample command and output shows a LAT connection from the router named Router_A to host eng2:
Router_A> lat eng2
The system informs you of its progress by displaying the messages “Trying <system>...” and then “Open.” If the connection attempt is not successful, you receive a failure message.
The following sample command establishes a LAT connection from the router named Router_B to a device named our-modems and specifies port 24, which is a special modem:
The following sample command establishes a LAT connection from the router named Router_C to a device named our-modems and specifies a node named eng:
The following sample command and output shows the LAT session debugging capability:
A variety of LAT events are reported, including all requests by the remote system to set local line parameters. The messages within brackets ([ ]) are the messages produced by the remote system setting line characteristics to operating system defaults.
Related Commands
lat access-list
To specify access conditions to nodes on the local-area transport (LAT) network, use the lat access-list command in global configuration mode. To remove a specified access list number, use the no form of this command.
lat access-list number { permit | deny } nodename
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Regular expressions are case sensitive. Because LAT node names are always in all uppercase letters, make sure you use only all uppercase regular expressions.
Table 5 and Table 6 list pattern and character matching symbols and their use. A more complete description of the pattern matching characters is found in the “Regular Expressions” appendix in the Cisco IOS Terminal Services Configuration Guide.
|
|
|
|---|---|
Replaces the strings that match the first through ninth parenthesized part of X.121 address. |
|
|
|
|
|---|---|
Matches the null string at the beginning of the input string. |
|
Examples
The following example permits all packets destined for any LAT node named WHEEL:
The following example denies all packets destined for any LAT node name beginning with the BLDG1- prefix:
Related Commands
|
|
|
|---|---|
Defines access list restrictions on incoming and outgoing connections. |
lat enabled
To enable local-area transport (LAT), use the lat enabled command in interface configuration mode. To disable LAT, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Examples
The following example enables LAT on Ethernet interface 0:
The following example disables LAT on Ethernet interface 0:
lat group-list
To allow a name to be assigned to the group list, use the lat group-list command in global configuration mode. To remove the specified group list, use the no form of this command.
lat group-list groupname { number | range | all } [ enabled | disabled ]
no lat group-list groupname { number | range | all } [ enabled | disabled ]
Syntax Description
Defaults
None. A group list is any combination of group names, numbers, or ranges. No group names are assigned to the list by default.
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Specifying a name for a group list simplifies the task of entering individual group codes. In other words, a name makes it easier to refer to a long list of group code numbers. The group list must already exist. Use the show lat groups EXEC command to see a list of existing groups.
Examples
The following example creates the new group named stockroom and defines it to include the group numbers 71 and 99:
The following example adds group code 101 to the group named stockroom:
The following example deletes the group named Bldg-2:
Related Commands
lat host-buffers
To set the number of receive buffers that will be negotiated when the router is acting as a local-area transport (LAT) host, use the lat host-buffers command in global configuration mode. To return to the default of one receive buffer, use the no form of this command.
lat host-buffers receive-buffers
no lat host-buffers receive-buffers
Syntax Description
Specifies the number of receive buffers that will be negotiated. Valid values range from 1 to 128. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Before LAT Version 5.2, LAT allowed only one outstanding message at a time on a virtual circuit. This restriction could limit the performance of large routers. For example, only one Ethernet packet of data could be in transit at a time. With LAT Version 5.2, nodes can indicate that they are willing to receive more than one message at a time. During virtual circuit startup, each side communicates to the other how many outstanding messages it is willing to accept.
Examples
The following example enables LAT and configures the LAT host to negotiate 100 receive buffers:
Related Commands
|
|
|
|---|---|
Sets the number of receive buffers that will be negotiated when the router is acting as a LAT server. |
lat ka-timer
To set the rate of the keepalive timer, use the lat ka-timer command in global configuration mode. To restore the default, use the no form of this command.
Syntax Description
Timer rate, in seconds. Valid values for the timer rate range from 10 to 255 seconds. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
The keepalive timer sets the rate that messages are sent in the absence of actual traffic between the router and the remote node. The server uses keepalive messages to detect when communication with a remote node is disrupted or when the remote node has crashed.
Examples
The following example sets the keepalive timer rate to 5 seconds:
lat node
To change the local-area transport (LAT) node name without changing the system host name, use the lat node command in global configuration mode.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
This command allows you to give the server a node name that is different from the host name. Use the show entry EXEC command to determine which LAT hosts have queue entries for printers on the servers. Use the clear entry EXEC command to delete entries from the queue.
Examples
The following example specifies the LAT node name as DEC2:
Related Commands
|
|
|
|---|---|
Deletes an entry from the list of queued host-initiated connections. |
|
Displays the list of queued host-initiated connections to a router. |
lat out-group
To define a group list for outgoing user-initiated connections on a line, use the lat out-group command in line configuration mode. To return to the default value, use the lat out-group 0 command.
lat out-group { group-name number | range | all }
Syntax Description
Group code number. You can also enter both a group code name and group code numbers. |
|
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
You can have values for one, two, or all three arguments. If the all keyword is specified, no arguments can be used. You can enter the group-name, number, and range values in any order.
Use the show lat groups EXEC command to display group numbers. If the host node and router do not share a common group number, the host services will not be displayed.
Examples
The following example defines the services for lines 1 through 7, 10 through 17, and 20 through 24. Access to systems on the first set of lines is limited to groups 12 and 18 through 23; the second set is limited to group 12; the third set is limited to group codes 12, 18 through 23, and 44. All other lines use the default of group 0.
Related Commands
lat remote-modification
To enable remote local-area transport (LAT) modification of line characteristics (for example, baud rate), use the lat remote-modification command in line configuration mode. To disable remote LAT modification of line characteristics, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Enabling the line for remote modification allows the remote LAT node to change line characteristics (for example, baud rate, parity, and so on).
Examples
The following example enables remote LAT modification on line 4:
lat retransmit-limit
To set the number of times that local-area transport (LAT) resends a message before declaring the remote system unreachable, use the lat retransmit-limit command in global configuration mode. To restore the default retry value, use the no form of this command.
Syntax Description
Number of retries. Valid values range from 4 to 255 retries. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Assigning larger values to the number of tries increases the robustness of the LAT service at the cost of longer delays when communications are disrupted. Because LAT generally resends messages once per second, the value is approximately the number of seconds that LAT connections will survive connection disruption.
If you bridge LAT, the retransmission limit should be set to at least 20 tries for LAT sessions to survive a worst-case spanning-tree reconfiguration, because the time for bridging spanning-tree reconfiguration to be completed can be up to 15 seconds.
Examples
The following example sets the retransmission limit to 30 tries, enough time to sustain the downtime incurred when the system must reconfigure a spanning-tree topology:
lat server-buffers
To set the number of receive buffers that will be negotiated when the router is acting as a local-area transport (LAT) server, use the lat server-buffers command in global configuration mode. To return to the default of one receive buffer, use the no form of this command.
lat server-buffers receive-buffers
no lat server-buffers receive-buffers
Syntax Description
Specifies the number of receive buffers that will be negotiated. Valid values range from 1 to 128 receive buffers. The default value is 1 receive buffer. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Before LAT Version 5.2, LAT allowed only one outstanding message on a virtual circuit at a time. This restriction could limit the performance of large routers because only one Ethernet packet of data could be in transit at a time. With LAT Version 5.2, nodes can indicate that they are willing to receive more than one message at a time. During virtual circuit startup, each side communicates to the other how many outstanding messages it is willing to accept.
Examples
The following example enables LAT and configures the server to negotiate 25 receive buffers:
Related Commands
|
|
|
|---|---|
Sets the number of receive buffers that will be negotiated when the router is acting as a LAT host. |
lat service enabled
To enable inbound connections to the specified service and enable the advertisement of this service to routers on the network, use the lat service enabled command in global configuration mode. To delete the named service, use the no form of this command.
lat service service-name enabled
no lat service service-name enabled
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
In the simplest form, this command creates a service that gives connecting users access to a vty port on the server.
Use the lat service enabled command after commands that define a service so that users do not connect to a service before all the parameters are set.
Deleting a service does not disconnect existing connections.
Examples
The following example enables inbound connections to the service named WHEEL:
lat service-host
To statically define local-area transport (LAT) services, use the lat service-host command in interface configuration mode. To remove the statically defined LAT services, use the no form of this command.
lat service-host node-name service-name MACaddress
Syntax Description
MAC address entered as three hexadecimal numbers of four digits separated by a period MAC address of the remote node. |
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Usage Guidelines
Use the show running-config command to verify if the LAT services have been configured.
Examples
The following example shows how to statically define LAT services:
Related Commands
|
|
|
|---|---|
lat service ident
To set the local-area transport (LAT) service identification for a specified service, use the lat service ident command in global configuration mode. To remove the identification, use the no form of this command.
lat service service-name ident identification
no lat service service-name ident
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
The identification is advertised to other servers on the network and is displayed along with the list of name services on the LAN.
Examples
The following example specifies the identification “Welcome to Gateway-A” on the service named host1:
lat service password
To set up a local-area transport (LAT) password for a service, use the lat service password command in global configuration mode. To remove the password, use the no form of this command.
lat service service-name password password
no lat service service-name password
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
The connecting user will be required to enter the password to complete the connection. The password is obtained through the LAT password mechanism.
Examples
The following example specifies a service named host1 and the password secret:
lat service rating
To set a static service rating for the specified service, use the lat service rating command in global configuration mode. To remove the service rating, use the no form of this command.
lat service service-name rating static-rating
no lat service service-name rating
Syntax Description
Static service rating. The rating must be in the range from 1 to 255. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
If this command is not entered, the Cisco IOS software calculates a dynamic rating based on the number of free ports that can handle connections to the service. Setting a static rating overrides this calculation and causes the specified value to be used.
Examples
The following example specifies a service rating of 84 on the service named WHEEL:
lat service rotary
To associate a rotary group with a service, use the lat service rotary command in global configuration mode. To remove the association, use the no form of this command.
lat service service-name rotary group-number
no lat service service-name rotary
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Establish rotary groups using the rotary line configuration command.
When an inbound connection is received for this service, the router establishes a reverse local-area transport (LAT) connection to a terminal in that rotary group.
If the rotary option is not set, the connection will be to a virtual terminal session on the router.
Examples
The following example creates a service named MODEM to establish a rotary group:
Related Commands
|
|
|
|---|---|
lat service-announcements
To reenable local-area transport (LAT) broadcast service announcements, use the lat service-announcements command in global configuration mode. To disable the sending of LAT service announcements, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
If this command is enabled, the LAT code will periodically broadcast service advertisements. If the command is disabled, the LAT code will not send service announcements, so solicit information messages must be used to look up node information.
Note You should only disable service announcements if all of the nodes on the LAN support the service responder feature.
Examples
The following example reenables the sending of broadcast service announcements:
Related Commands
|
|
|
|---|---|
Configures a node to act as proxy for other nodes when a solicit-information multicast message is received. |
lat service-group
To specify a group code mask to use when advertising all services for this node and to control incoming services, use the lat service-group command in global configuration mode. To remove the group code mask specified, use the no form of this command.
lat service-group {[ groupname ] [ number ] [ min - max ] | all } [ enabled | disabled ]
no lat service-group {[ groupname ] [ number ] [ min - max ] | all } [ enabled | disabled ]
Syntax Description
Defaults
If no service group is specified, the Cisco IOS software defaults to advertising to group 0.
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
When this command is written to NVRAM (using the write memory EXEC command), the system looks for an exact match on a group code name. If it finds one, it uses that name in the command. Otherwise, it writes out a list of numbers, using the range syntax whenever possible.
Examples
The following example specifies groups 100 through 103, then defines engineering as the group code list to advertise:
The following example specifies the groups 1, 5, 20 through 36, and 52:
Related Commands
|
|
|
|---|---|
Allows a name to be assigned to the group list, which is any combination of group names, numbers, or ranges. |
lat service-responder
To configure a node to act as proxy for other nodes when a solicit-information multicast message is received, use the lat service-responder command in global configuration mode. To remove any proxy definition set up using the lat service-responder command, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
The Cisco IOS software can be configured to support the service responder feature that is part of the latest LAT Version 5.2 specification.
Specifically, the DECserver90L+, which has less memory than other Digital Equipment Corporation servers, does not maintain a cache of learned services. Instead, the DECserver90L+ solicits information about services as they are needed.
LAT Version 5.2 nodes can respond for themselves; however LAT Version 5.1 nodes, for example, VMS Version 5.4 or earlier nodes, cannot respond for themselves. Instead, a LAT Version 5.2 node configured as a service responder must respond in proxy for the LAT Version 5.1 nodes.
The Cisco IOS software can be configured as a LAT service responder. If all your nodes are LAT Version 5.2 nodes, you need not enable the service responder features.
Examples
The following example configures a node to act as a proxy for a node when a solicit-information multicast message is received. The node configured with this command will respond to solicit messages.
Related Commands
|
|
|
|---|---|
lat service-timer
To adjust the time between local-area transport (LAT) service advertisements, use the lat service-timer command in global configuration mode. To return to the default setting, use the no form of this command.
Syntax Description
Number of seconds between service announcements. Note that the granularity offered by this command is 10-second intervals, and the seconds value is rounded up. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
This command adjusts the time, in seconds, between LAT service announcements for services offered by the router. This function is useful in large networks with many LAT services and limited bandwidth.
Examples
The following example sets the interval between LAT service advertisements to 11, and it illustrates the rough granularity of the lat service-timer command:
lat vc-sessions
To set the maximum number of sessions to be multiplexed onto a single local-area transport (LAT) virtual circuit, use the lat vc-sessions command in global configuration mode. To remove the definition of a prior session, use the no form of this command.
lat vc-sessions maximum-number
no lat vc-sessions maximum-number
Syntax Description
Specifies the number of sessions that will be multiplexed onto a single LAT virtual circuit. This number cannot be greater than 255. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Setting the number of sessions to a lower number can increase throughput if many sessions are running on one host, especially with routers with many physical ports. It can also increase overhead if the same host has little traffic but a large number of sessions.
Examples
The following example sets the maximum number of sessions to be multiplexed onto a single LAT virtual circuit at 100:
lat vc-timer
To set the interval of time local-area transport (LAT) waits before sending any traffic, use the lat vc-timer command in global configuration mode. To remove a timer definition, use the no form of this command.
Syntax Description
Specifies the amount of time LAT will wait before sending traffic. Acceptable values range from 10 to 1000 milliseconds. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Smaller timer values increase the overhead on both the router and the host. However, you can use smaller values to correct buffer overflows, which happen when the router receives more data than it can buffer during a virtual circuit timer interval.
Larger values increase the need for buffering and can cause noticeable echoing delay. However, increased values can reduce traffic. In environments with slow bridging, retransmissions can be reduced if you increase the value to at least three times the worst-case, round-trip interval.
Examples
The following example sets the time between sending messages to 500 milliseconds:
line
To identify a specific line for configuration and enter line configuration collection mode, use the line command in global configuration mode.
line [ aux | console | tty | vty ] line-number [ ending-line-number ]
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
You can address a single line or a consecutive range of lines with the line command. A line number is necessary, though, and you will receive an error message if you forget to include it.
Entering the line command with the optional line type ( aux, console, tty, or vty) designates the line number as a relative line number. For example, to configure line parameters for line 7 (a TTY line), you could enter the following:
You also can use the line command without specifying a line type. In this case, the line number is treated as an absolute line number. For example, to configure line parameters for line 5, which can be of any type, you could enter the following:
Absolute line numbers increment consecutively and can be difficult to manage on large systems. Relative line numbers are a shorthand notation used in configuration. Internally, the Cisco IOS software uses absolute line numbers. You cannot use relative line numbers everywhere, but you can use absolute line numbers everywhere.
The absolute line number of the auxiliary port is 1. The relative line number of the auxiliary port is 0. See the modem line configuration command to set up modem support on the auxiliary port.
The software keeps a table of absolute and relative line numbers that you can display with the show users all EXEC command. A sample display follows:
0 con 0 con2 console
1 tty 1 Engineering printer
2 tty 2
3 tty 3 HOST1 1:07 Employee1 x1111
4 tty 4 Console E3-D
5 tty 5 Mkt. demo area
6 tty 6
7 tty 7 HOST1 14 Employee2 x1112
10 tty 10
136 tty 136
137 tty 137 rp4-printer
140 tty 140 Braille printer
141 aux 0
142 vty 0 User1 idle ROUTER-MAC.CISCO.COM
143 vty 1 User2 idle 0 HOST1.CISCO.COM
144 vty 2
145 vty 3
146 vty 4
147 vty 5
The absolute line numbers are listed at the far left, followed by the line type, and then the relative line number. Relative line numbers always begin numbering at zero and define the type of line. Addressing the second virtual terminal line as line VTY 1, for example, is easier than remembering it as line 143—its absolute line number.
The line types are ranked as follows in the line table:
2. Standard asynchronous line (TTY)
4. Virtual terminal line (VTY)
The terminal from which you locally configure the router is attached to the console port. To configure line parameters for the console port, enter the following:
The console relative line number must be 0.
Virtual terminal lines are used to allow remote access to the router. A virtual terminal line is not associated with either the auxiliary or console port. The router has five virtual terminal lines by default. However, you can create additional virtual terminal lines as described in the chapter “Configuring Protocol Translation and Virtual Asynchronous Devices” in the Cisco IOS Terminal Services Configuration Guide.
Configuring the console port or virtual terminal lines allows you to perform such tasks as setting communication parameters, specifying autobaud connections, and configuring terminal operating parameters for the terminal you are using.
Examples
The following example starts configuration for virtual terminal lines 0 to 4:
In the following example, the user creates and configures the maximum 100 virtual terminal lines with the no login command:
In the following example, the user eliminates virtual terminal line number 5 and all higher-numbered virtual terminal lines. Only virtual terminal lines 0 to 4 will remain.
In the following example, the user configures console line 0, auxiliary line 0, and virtual terminal lines 0 to 4:
Related Commands
|
|
|
|---|---|
login (EXEC)
To change a login username, use the login command in EXEC mode.
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
You can change a login username if you must match outgoing access list requirements or other login prompt requirements.
When you enter this command, the Cisco IOS software prompts you for a username and password. Enter the new username and the original password. If the username does not match, but the password does, the Cisco IOS software updates the session to the new username with which the login command attempt was made.
If no username and password prompts appear when you enter this command, the network administrator did not specify that a username and password be required at login time. If both the username and password are entered correctly, the session becomes associated with the specified username.
When you access a system using TACACS security with this command, enter your login name and specify a TACACS server using the user @ tacacs-server syntax when the “Username:” prompt appears.
The TACACS server must be one of those defined in a Cisco IOS software configuration file. For more information, refer to the sections about specifying a TACACS host in the Cisco IOS Security Configuration Guide, or refer to the tacacs-server host command in the Cisco IOS Security Command Reference.
If you do not specify a host, the Cisco IOS software tries each of the TACACS servers in the list until it receives a response.
If you do specify a host that does not respond, no other TACACS server is queried. The Cisco IOS software will deny access or function according to the action specified by the tacacs-server last-resort command, if one is configured.
If you specified a TACACS server host with the user @ tacacs-server command, the TACACS server specified will be used for all subsequent authentication or notification queries, with the possible exception of Serial Line Internet Protocol (SLIP) address queries.
Examples
The following example shows how login usernames and passwords can be changed. In this example, a user currently logged in under the username user1 attempts to change that login name to user2. After entering the login command, the user enters the new username, but enters an incorrect password. Because the password does not match the original password, the system rejects the attempt to change the username.
Next, the user attempts the login change again, with the username user2, but enters the correct (original) password. This time the password matches the current login information, the login username is changed to user2, and the user is allowed access to the EXEC at the user level.
Related Commands
|
|
|
|---|---|
login (line)
To enable password checking at login, use the login command in line configuration mode. To disable password checking and allow connections without a password, use the no form of this command.
Syntax Description
Defaults
Virtual terminals require a password. If you do not set a password for a virtual terminal, it responds to attempted connections by displaying an error message and closing the connection.
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
If you specify the login command without the local or tacacs option, authentication is based on the password specified with the password line configuration command.
Note This command cannot be used with AAA/TACACS+. Cisco recommends that you use the login authentication command instead of the login (line) configuration command. Refer to the Cisco IOS Security Command Reference for a description of the login authentication command.
Examples
The following example sets the password letmein on vty 4:
The following example enables the TACACS-style user ID and password-checking mechanism:
Related Commands
login-string
To define a string of characters that is sent to a host after a successful Telnet connection, use the login-string command in global configuration mode. To remove the login string, use the no form of this command.
login-string host-name d message [ % sec p ] [ % sec w ] [ % b ] [ % m ] d
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Follow this command with one or more blank spaces and a delimiting character of your choice. Then enter one or more lines of text, terminating the message with the second occurrence of the delimiting character. To use a percent sign in the login string, precede it with another percent sign; that is, type the characters “%%.” The options can be used anywhere within the message string.
Examples
In the following example, the value % 5 p causes a 5-second pause:
match (ruleset)
To identify a connection for processing by a protocol translation ruleset, use the match command in translate ruleset configuration mode. To remove the match statement, use one of the two no forms of this command.
match [ # line-number ] incoming-connection-parameter regular-expression [ # line-number incoming-connection-parameter regular-expression [...]]
no match incoming-connection-parameter regular-expression [ incoming-connection-parameter regular-expression [...]]
Syntax Description
(Optional) The line in the ruleset to test for a match operation. The # character must be entered. |
|
An incoming protocol parameter to test for; parameters are available for packet assembler/disassembler (PAD) and Telnet connections and are listed in Table 7 and Table 8 . |
|
(Optional) Specifies that multiple entries can be made as follows: |
Defaults
Command Modes
Translate ruleset configuration
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Up to six match tests can be written on one command line. The ellipses in the format shown above means multiple match test statements can be specified.
The match command is specific to the identified ruleset. A connection can be identified for processing by the ruleset match operation where tests written using keywords from Table 7 and Table 8 , such as dest-addr and dest-port , match a regular expression.
Each protocol translation ruleset must have at least one match statement. If an incoming connection does not match any tests written in this template, it is not selected for processing by the ruleset.
The ordered set of commands in the template have line numbers that can be displayed using the show translate EXEC command.
Cisco regular expressions are described in Appendix A, “Regular Expressions,” in the Cisco IOS Terminal Services Configuration Guide.
Table 7 and Table 8 lists the protocol parameter keywords that can be specified in the match test statements for incoming PAD and Telnet connections.
Examples
The following example shows how to write match and skip tests to ignore connection attempts from any subnetwork address starting with 10 and match only those with a specific IP address and destination port number:
The following example shows how to write match and skip tests to skip connection attempts from destination 55554 and to match only those with destination addresses from 55550 to 55553 and from 55556 to 55559:
Related Commands
monitor traffic line
To monitor inbound or outbound asynchronous character mode traffic on another terminal line, use the monitor traffic line command in privileged EXEC mode.
monitor traffic line [ aux | tty ] line-number [ in | out ] [ control-char ] [ interactive ]
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
The monitor traffic line command allows for the monitoring of only tty and auxiliary lines. The monitoring of console or vty lines is not permitted.
You can monitor only a single line with the monitor traffic line command. A line number is necessary, though, and you will receive an error message if you forget to include it.
To disable asynchronous line monitoring, enter the escape sequence (Ctrl-Shift-6, then x [ Ctrl ^ x ] by default).
Entering the monitor traffic line command with the optional line type ( aux or tty) designates the line number as a relative number. For example, to configure line monitoring for line 7 (a tty line), you could enter the following:
You can also use the monitor traffic line command without specifying a line type. In this case, the line number is treated as an absolute line number. For example, to configure line traffic monitoring for line 5, which can be of aux or tty type, you could enter the following:
The monitor traffic line command starts displaying the asynchronous characters traversing the line that is being monitored. To stop monitoring traffic, enter the escape sequence (Ctrl-Shift-6, then x [ Ctrl ^ x ] by default).
You can issue the control-char keyword with the monitor traffic line command to configure the display of control characters along with the asynchronous character traffic on the line that is being monitored.
Note The monitor traffic line command inserts a linefeed (LF) character in the character stream immediately after a carriage return (CR) character if the CR character is not immediately followed by an LF character in the original character stream.
In releases prior to Cisco IOS Release 12.3(8)T, when the monitor traffic line command is running and the asynchronous characters are being displayed (the user has not yet entered the escape sequence to stop traffic monitoring), the Asynchronous Line Monitoring feature allows the user of the remote monitoring station to enter more commands on this line. The output of the additional commands are displayed not only to the user of the remote monitoring station but also to the user of the terminal line that is being monitored. To prevent this display of command output on the terminal line that is being monitored, the user of the remote monitoring station must be careful not to enter more commands while the monitor traffic line command is still running.
In Release 12.3(8)T, the default behavior of the monitor traffic line command was changed so that commands entered by the user on the remote monitoring station are not displayed to the user on the terminal line being monitored (the keyboard lock is on). The interactive keyword turns off the keyboard lock, enabling the display of commands entered on the remote monitoring station to the user of the terminal line being monitored.
Examples
The following example allows the user to monitor inbound asynchronous character mode traffic on tty line 10:
The following example allows the user to monitor inbound asynchronous character mode traffic, including control characters, on tty line 10:
The following example allows the user to monitor inbound asynchronous character mode traffic on line 5. The interactive keyword turns off the keyboard lock, specifying that commands entered at the remote monitoring station will be displayed to the user of the line being monitored.
options (ruleset)
To specify protocol translation options in a translation ruleset, use the options command in translate ruleset configuration mode. To remove or change the option, use the no form of this command.
options rule-option [ rule-option […]]
Syntax Description
One of the protocol translation option keywords listed in Table 9 followed, for some keywords, by a value for the option. More than one option can be listed on a command line. |
Defaults
Command Modes
Translate ruleset configuration
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Use this command to set the supported options listed in Table 9 . The ellipses in the format shown above means multiple options statements can be specified. The ruleset-defined options are overwritten each time the options command is entered. A connection that matches a ruleset, but fails the ruleset’s configured option test, will be rejected.
Examples
The following example limits the number of simultaneous ruleset users to 10 and requires that the user log in before the outgoing connection is made:
Related Commands
pad
To log in to a packet assembler/disassembler (PAD), use the pad command in EXEC mode.
pa d { x121-address | host-name } [ /cud text ] [ /debug ] [ /profile name ] [ /quiet message ] [ /reverse ] [ /use-map ]
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
The pad command supports one-word connections. You need not enter the pad command; entering the address is enough to start the connection. A PAD can also be accessed and X.3 parameters configured with the x28 EXEC command, which uses the standard X.28 user interface.
You can have several PAD connections open at the same time and switch between them. You also can exit a connection and return to the user EXEC prompt at any point. To open a new connection, first exit the current connection by entering the escape sequence ( Ctrl-Shift-6 then x [ Ctrl^x ] by default) to return to the EXEC prompt, then open the new connection. If the /use-map option is selected on the outgoing pad command, the x25 map pad command entries are searched for a matching X.121 destination address. If a match is found, the x25 map pad command entry options (such as CUD and idle) and facilities (such as packet in, packet out, win in, and win out) are applied to the outgoing PAD call.
To display information about packet transmission and X.3 PAD parameter settings, use the show x25 pad command. To exit a session, simply log out of the remote system. Then, terminate the active session by entering the exit command.
Examples
Use the ? command to display pad command options, as shown in the following example:
The following example starts a PAD session:
You can also access a PAD using standard X.28 commands. The following example enters X.28 mode with the x28 EXEC command and configures a PAD with the set X.3 parameter command. The set command sets the idle time delay to 40 seconds.
The following example uses the /use-map option to configure a larger window and packet size than the default specified on the interface, and it sets the virtual circuit idle time to 2 seconds. Notice that the map values are used rather than the interface default values.
Related Commands
resume (setting X.3 PAD parameters)
To set X.3 parameters, use the resume command in EXEC mode.
resume [ connection ] [ /set parameter : value ]
Syntax Description
(Optional) The name or number of the connection; the default is the most recent connection. |
|
(Optional) Sets the X.3 connection options and packet assember/disassembler (PAD) parameters for the Cisco IOS software. See Table 10 in the Usage Guidelines for the PAD parameter numbers. Refer to the chapter “Configuring the Cisco PAD Facility for X.25 Connections” of the Cisco IOS Terminal Services Configuration Guide for a list of these connection options. |
Defaults
For outgoing connections, the X.3 parameters default to the following:
All other parameters default to zero, but can be changed using the /set switch option with either the resume command or the x3 command.
For incoming PAD connections, the software sends an X.29 SET PARAMETER packet to set only the following parameters:
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Table 10 summarizes the X.3 PAD Parameters supported on Cisco devices. Refer to the “X.3 PAD Parameters” appendix in the Cisco IOS Terminal Services Configuration Guide for more complete information about these parameters.
The /set switch sets the X.3 parameters defined by parameter number and value, separated by a colon. You set one or more X.3 PAD parameters, as follows:
Step 1 Escape out of the current session by pressing the escape sequence ( Ctrl-Shift-6 then x [ Ctrl^x ] by default) and return to the EXEC prompt.
Step 2 Issue the where command, to list the open sessions. All open sessions associated with the current terminal line are displayed.
Step 3 Enter the resume command, followed by the parameter, a colon, and then the value to be set.
Examples
The following example specifies that local echo mode be turned on for a connection to the device named Swift (which is session number 3). As shown in Table 7, “local echo on” uses the parameter 2 and the value 1 (represented as 2:1 in this example):
Related Commands
|
|
|
|---|---|
resume (switching sessions)
To switch to another open Telnet, rlogin, local-area transport (LAT), or packet assembler/disassembler (PAD) session, use the resume command in EXEC mode.
resume [ connection ] [ keyword ] [ /set parameter : value ]
Syntax Description
(Optional) The name or number of the connection; the default is the most recent connection. |
|
(Optional) Sets PAD parameters for the Cisco IOS software (see Table 7). |
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Table 11 lists Telnet and rlogin resume options.
|
|
|
|---|---|
Displays parameter changes and messages. In the Cisco IOS software, this option displays informational messages whenever the remote host changes an X.3 parameter, or sends an X.29 control packet. |
|
/noline3 |
Disables line mode and enables character-at-a-time mode, which is the default. |
Sets X.3 connection options. Refer to the chapter “Configuring the Cisco PAD Facility for X.25 Connections” of the Cisco IOS Terminal Services Configuration Guide for a list of these connection options. |
|
|
|
You can have several concurrent sessions open and switch between them. The number of sessions that can be open is defined by the session-limit command.
You can switch between sessions by escaping one session and resuming a previously opened session, as follows:
Step 1 Escape out of the current session by pressing the escape sequence ( Ctrl-Shift-6 then x [ Ctrl^x ] by default) and return to the EXEC prompt.
Step 2 Enter the where command, to list the open sessions. All open sessions associated with the current terminal line are displayed.
Step 3 Enter the resume command and the session number to make the connection.
You also can resume the previous session by pressing the Return key.
The Ctrl^x, where, and resume commands are available with all supported connection protocols.
Examples
The following example shows how to escape out of a connection and to resume connection 2:
You can omit the command name and simply enter the connection number to resume that connection. The following example illustrates how to resume connection 3:
Related Commands
|
|
|
|---|---|
Lists open sessions associated with the current terminal line. |
rlogin
To log in to a UNIX host using rlogin, use the rlogin command in EXEC mode.
rlogin host [ - l username ] [ /user username ] [ /quiet ] [ debug ]
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
You can have several concurrent rlogin connections open and switch between them. To open a new connection, first suspend the current connection by pressing the escape sequence ( Ctrl-Shift-6 then x [Ctrl^x ] by default) to return to the EXEC prompt. Then open a new connection. A user cannot automatically log in to a UNIX system from the router, but must provide a user ID and a password for each connection.
If your preferred transport is set to rlogin, you can use the connect command in place of the rlogin command. Refer to the chapter “Configuring Terminal Operating Characteristics for Dial-In Sessions” in the Cisco IOS Terminal Services Configuration Guide for more information about configuring a preferred transport type. When your preferred transport is set to none or to another protocol, you must use the rlogin command to connect to a host.
To terminate an active rlogin session, enter one of the following commands at the UNIX prompt of the device to which you are connecting:
Examples
The following example illustrates how a user with the login name jsmith can use the rlogin ? help command and the debug command mode to establish and troubleshoot a remote connection to the host named Alviso:
The following example illustrates debug return on the host named router1 by the user named user1:
The following example makes an rlogin connection to a host at address 10.30.21.2 for a user named user2 and enables the message mode for debugging:
The following example makes an rlogin connection to a host named headquarters for the user named admin:
The following example suppresses all onscreen messages from the Cisco IOS software during login and logout:
Router> rlogin host2 /quiet
Related Commands
|
|
|
|---|---|
rlogin trusted-localuser-source
To choose an authentication method for determining the local username to send to the remote rlogin server, use the rlogin trusted-localuser-source command in global configuration mode. To restore the default rlogin behavior, use the no form of this command.
rlogin trusted-localuser-source [ local | radius | tacacs ]
no rlogin trusted-localuser-source [ local | radius | tacacs ]
Syntax Description
(Optional) Uses local username from any authentication method. |
|
Defaults
The user must enter an rlogin username and password when connecting to the rlogin server.
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
Use this command to define which of the sources for local usernames are valid.
The rlogin protocol passes three types of information: the remote username, the local username, and the local host name of the router. The rlogin trusted-localuser-source command allows you to configure one of three behaviors for making connections to the rlogin server, as follows:
- The user must enter a login username and password to connect (default).
- The Cisco IOS-authenticated username can be passed to the rlogin server so the user need only enter a password to connect.
- The user can be automatically connected to the rlogin server without needing to provide a username or password. This configuration is made by using both the rlogin trusted-localuser-source and rlogin trusted-remoteuser-source local commands where both the Cisco IOS authenticated username and the rlogin server username are the same.
Examples
The following example uses the local username from RADIUS authentication:
Related Commands
rlogin trusted-remoteuser-source local
To determine the remote username to send to the remote rlogin server, use the rlogin trusted-remoteuser-source local command in global configuration mode. To restore the default rlogin behavior, which is to prompt the user for the remote username, use the no form of this command.
rlogin trusted-remoteuser-source local
no rlogin trusted-remoteuser-source local
Syntax Description
Defaults
The user must enter an rlogin username and password when connecting to the rlogin server.
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
Usage Guidelines
The current username is used only if the rlogin host /user username command is not enabled. If the current username is not known, rlogin falls back to providing the “login:” prompt to discover a remote username.
After you issue the rlogin trusted-remoteuser-source local command, you will not be prompted for a username. The first response you see is the password prompt from the remote system. For example, when this command is not enabled, you must enter your username twice (once at initial system login and once for the rlogin command).
Configuring the remote host to consider the Cisco router a “trusted” host should be considered a security hole.
Examples
The following sample output shows the two prompts a user must reply to when the rlogin trusted-remoteuser-source local command is not set:
The following example shows that after you issue the rlogin trusted-remoteuser-source local command, you no longer need to specify the username after the rlogin command. The username is automatically copied from the user ID of the router:
The following example uses the /user root keyword option as an override:
Related Commands
rsa keypair-name
To name the Rivest, Shamir, and Adelman (RSA) ke ypair to be used for a persistent Secure Shell (SSH) connection, use the rsa keypair-name command in transport map configuration mode command. To restore the default setting of no configured RSA keypair name, use the no form of the command.
rsa keypair-name rsa-keypair-name
Syntax Description
The name of the RSA keypair to be used for a persistent SSH connection. |
Command Default
No RSA keypair names for persistent SSH are specified by default.
Command Modes
Transport map configuration (config-tmap)
Command History
|
|
|
|---|---|
This command was introduced on the Cisco ASR 1000 Series Routers. |
Usage Guidelines
For persistent SSH connections, the RSA keypair name must be defined using this command in transport map configuration mode. The RSA keypair definitions defined elsewhere on the router, such as through the use of the ip ssh rsa keypair-name command, do not apply to persistent SSH connections.
The generation of an RSA keypair, by default, starts the IOS internal SSH server. If you do not want to generate an SSH keypair using IOS, configure the ip ssh rsa keypair-name as a value that would never generate a connection (such as ip ssh rsa keypair-name none , ip ssh rsa keypair-name never, or any other name that will never generate a connection)
Examples
In the following example, a transport map that will make all SSH connections wait for the IOS process to become active before connecting to the router is configured and applied to the Management Ethernet interface (interface gigabitethernet 0). The RSA keypair is named “sshkeys”.
This example only uses the commands required to configure persistent SSH.
In the following example, a transport map is configured that applies the following settings to any users attempting to access the Management Ethernet port via SSH:
- Users using SSH wait for the IOS process to become active, but enter diagnostic mode if the attempt to access IOS is interrupted.
- The RSA keypair name is “sshkeys”
- The connection allows one authentication retry.
- The banner “--Welcome to Diagnostic Mode--” appears if diagnostic mode is entered as a result of SSH handling through this transport map.
- The banner “--Waiting for IOS Process--” appears if the connection is waiting for the IOS process to be come active.
The transport map is then applied to the interface when the transport type persistent ssh input command is entered to enable persistent SSH.
Router(config-tmap)# authentication-retries 1
Router(config-tmap)# banner diagnostic X
Enter TEXT message. End with the character 'X'.
--Welcome to Diagnostic Mode--
Related Commands
rxspeed
To set the terminal receive speed (how fast the terminal receives information from the modem), use the rxspeed command in line configuration mode. To reset the default value, use the no form of this command.
Syntax Description
Baud rate in bits per second (bps). The default value is 9600 bps. |
Defaults
Command Modes
Command History
|
|
|
|---|---|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware. |
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.
Note If the line was previously configured for automatic baud rate detection (autobaud), disable autobaud by entering the no autobaud command before entering the rxspeed command to fix the speed of the port.
Examples
The following example sets the line 5 receive rate to 2400 bps:
Feedback