|
|
This chapter describes how to set operating characteristics for remote terminal service connections. It includes the following main sections:
For a complete description of the terminal characteristic commands in this chapter, see the Cisco IOS Dial Services Command Reference publication. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
In line configuration mode, you can set terminal operating characteristics that will be in operation for that line until the next time you change the line parameters. Alternatively, you can change the line setting locally (temporarily) with terminal EXEC commands. Both tasks are described in this chapter.
Your first task is to select a preferred connection protocol, then configure the appropriate communication parameters. The preferred transport type is your preferred connection protocol. This section describes how to configure the router to support specific protocols for the following:
Use the transport preferred command to specify which transport protocol is used on connections. Use the transport input and transport output commands to explicitly specify the protocols allowed on individual lines for both incoming and outgoing connections.
 |
Note Cisco routers do not accept incoming network connections to asynchronous ports (TTY lines) by default. You must specify an incoming transport protocol, or specify transport input all before the line will accept incoming connections. For example, if you are using your router as a terminal server to make console-port connections to routers or other devices, you will not be able to use Telnet to connect to these devices. You will receive the message "Connection Refused." |
For routers that support LAT, the default protocol for outgoing connections is LAT. For those that do not support LAT, the default protocol for outgoing connections is Telnet. For incoming connections, all the supported network protocols are accepted (the default protocol is all).
To specify transport protocols, use one or more of the following commands in line configuration mode:
| Command | Purpose |
|---|---|
transport input {all | lat | mop | nasi | none | pad | rlogin | telnet | v120} | Defines which protocols can be used to connect to a specific line. |
transport output {all | lat | mop | nasi | none | pad | rlogin | telnet | v120} | Determines the protocols that can be used for outgoing connections from a line. |
transport preferred {all | lat | mop | nasi | pad | rlogin | telnet | v120} | Specifies the protocol for the router to use if the user did not specify a protocol. |
transport preferred none | Prevents errant connection attempts. |
The router accepts a host name entry at the EXEC system prompt as a Telnet command. If you enter the host name incorrectly, the router interprets the entry as an incorrect Telnet command and provides an error message indicating that the host does not exist. The transport preferred none command disables this option so that if you enter a command incorrectly at the EXEC prompt, the router does not attempt to make a Telnet connection to a host that it cannot find.
The transport preferred setting specifies a search order when attempting to resolve names that might be valid for multiple protocols. If the address or service does not match the preferred protocol, all other valid output protocols are searched to find a valid match.
You can configure the Cisco IOS software to save local parameters between sessions. These local parameters are set with the terminal EXEC commands.
To specify the preferred protocol to use for the current session when a command does not specify one, use the following command in EXEC mode:
| Command | Purpose |
|---|---|
terminal transport preferred {all | lat | mop | nasi | none | pad | rlogin | telnet | v120} | Specifies the protocol for the Cisco IOS software to use for the current session if the user did not specify a protocol. |
The preferred transport type is your preferred connection protocol. This setting specifies a protocol search order that the Cisco IOS software uses when it attempts to resolve a device name that you enter, but you do not specify a connection protocol. For example, if you want to connect to a TCP/IP host named host1 and want to use Telnet, you enter telnet host1. However, if your preferred connection protocol is set to Telnet, you could enter host1 and be connected to the device. A host name might be valid for multiple protocols. If the address or service does not match the preferred protocol, all other valid connection protocols are searched to find a valid match for the name.
For router software images that support LAT, the default protocol for outgoing connections is LAT. For router software images that do not support LAT, the default protocol for outgoing connections is Telnet. For incoming connections, all the supported network protocols are accepted (the default protocol is all).
The Cisco IOS software accepts a host name entry at the EXEC prompt as a Telnet command. If you enter the host name incorrectly, the Cisco IOS software interprets the entry as an incorrect Telnet command and provides an error message indicating that the host does not exist. The transport preferred none command disables this option so that if you enter a command incorrectly at the EXEC prompt, the Cisco IOS software does not attempt to make a Telnet connection.
The following sections describe how to configure communication parameters:
The Cisco IOS software supplies the following default serial communication parameters for terminal and other serial device operation:
To change the default parameters as necessary to meet the requirements of the terminal or host to which you are connected, use any of the following commands in line configuration mode:
| Command | Purpose |
|---|---|
speed bps | Sets the line speed. Choose from line speed, transmit speed, or receive speed. |
databits {5 | 6 | 7 | 8} | Sets the data bits. |
stopbits {1 | 1.5 | 2} | Sets the stop bits. |
parity {none | even | odd | space | mark} |
To change these parameters as necessary to meet the requirements of the terminal or host to which you are attached, use one or more of the following commands in EXEC mode:
| Command | Purpose |
|---|---|
terminal speed bps | Sets the line speed for the current session. Choose from line speed, transmit speed, or receive speed. |
terminal databits {5 | 6 | 7 | 8} | Sets the data bits for the current session. |
terminal stopbits {1 | 1.5 | 2} | Sets the stop bits for the current session. |
terminal parity {none | even | odd | space | mark} |
To change the default privilege level for a given line or a group of lines, use the following command in line configuration mode:
| Command | Purpose |
|---|---|
privilege level level | Specifies a default privilege level for a line. |
You can enable password checking on a particular line so that the user is prompted to enter a password at the system login screen. You must then also specify a password. To do so, use the following commands in line configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | login | Enables password checking on a per-line basis using the password specified with the password command. |
Step2 | password password | Assigns a password to a particular line. |
You can enable password checking on a per-user basis, in which case authentication is based on the username specified with the username global configuration command. To enable password checking on a per-user basis, use the following commands in line configuration mode:
| Command | Purpose | |
|---|---|---|
Step1 | login local | Enables password checking on a per-user basis using the username and password specified with the username global configuration command. |
Step2 | login tacacs | Selects the Terminal Access Controller Access Control System (TACACS) style user ID and password-checking mechanism. |
Use the login tacacs command with TACACS and extended TACACS. Use the login authentication command with AAA/TACACS+.
By default, virtual terminals require passwords. If you do not set a password for a virtual terminal, the router displays an error message and closes the attempted connection. Use the no login command to disable this function and allow connections without a password.
For other access control tasks and password restrictions, including the enable password global configuration command that restricts access to privileged mode, see the Cisco IOS Security Configuration Guide.
You might need to control terminal sessions in high-traffic areas to provide resources for all users. You can define the following limitations for terminal sessions:
To establish terminal session limits, use the following commands in line configuration mode:
| Command | Purpose |
|---|---|
session-limit session-number | Sets the maximum number of simultaneous sessions.1 |
session-timeout minutes [output] | Sets the idle session timeout interval. |
logout-warning [seconds] | Warns users of impending timeouts set with the absolute-timeout command. |
| 1There is no inherent upper limit to the number of sessions you can create. |
|
NoteThe absolute-timeout command overrides any timeouts set through the AppleTalk Remote Access (ARA) protocol. |
You can display the host name, line number, and location of the host each time an EXEC session is started or an incoming connection is made. The line number banner appears immediately after the EXEC banner or incoming banner. This feature is useful for tracking problems with modems because it lists the host and line for the modem connection. Modem type information is also included if applicable.
To provide line information after the login prompt, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
service linenumber | Provides service line-number information after the EXEC banner or incoming banner. |
Posted: Tue Jul 18 13:32:59 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.