|
|
This chapter describes how to configure lines, modems, and terminal settings to access the ATM switch for management purposes. The Cisco DSLAM has two types of terminal lines:
Most line setup is the same for all types of lines, but certain commands, such as those having to do with modem control, apply to the auxiliary port only.
This chapter includes these sections:
Configuring terminal lines is a two-step process:
Step 2 Configure the parameters for each line.
The tasks involved in these steps are described in these sections:
Use line configuration mode to enter line configuration commands that affect a specified console, auxiliary, or virtual terminal line. To enter line configuration mode, use this command in global configuration mode:
Command | Task |
|---|---|
|
|
The terminal from which you locally configure the system is attached to the console port. This example specifies the console port and begins line configuration mode:
DSLAM(config)# line con 0 DSLAM(config-line)#
The auxiliary port supports modem connections. See the section "Setting Up Modem Control on the Auxiliary Port", to set up modem support on the auxiliary port.
Configuring the console port or virtual terminal lines allows you to specify communication parameters and autobaud connections, and configure terminal operating parameters for the terminal you are using. These tasks are described in the section "Defining Terminal Operation Characteristics".
You can also use the line command to create virtual terminal lines. This example shows how to create and configure the maximum 4 virtual terminal lines with the "no login" feature:
DSLAM(config)# line vty 0 4 DSLAM(config-line)# no login
You can change the default parameters for terminal communications to meet the requirements of the terminal or host to which you are attached. To do so, use one or more of these commands in line configuration mode:
Command | Task |
|---|---|
| |
| |
| |
This example shows how to configure the auxiliary line with a speed of 19,200 bits per second (bps):
DSLAM(config)# line aux 0 DSLAM(config-line)# speed 19200
You can configure a terminal to automatically detect the baud rate over an asynchronous serial line. This configuration applies to the auxiliary port only. To set up automatic baud detection, use this command in line configuration mode:
Command | Task |
|---|---|
|
To start communications using automatic baud detection, press Return multiple times at the terminal:
To change the default privilege level for a given line or group of lines, use this command in line configuration mode:
Command | Task |
|---|---|
|
|
On the auxiliary port, you can set both hardware and software flow control between the DSLAM and the devices attached to it.
To configure flow control between the DSLAM and attached device, use one or more of this commands in line configuration mode:
Command | Task |
|---|---|
| |
| |
|
Both software and hardware flow control are bidirectional. If you do not specify a direction, the DSLAM enables software flow control in both directions. For information about setting up hardware flow control on the EIA/TIA-232 line, see the hardware installation and maintenance manual for your product.
You can define a command that automatically executes upon connection to another host. Any appropriate EXEC command and any switch or host name that occurs with the EXEC command is allowed. To do so, use this command in line configuration mode:
Command | Task |
|---|---|
|
You can specify the protocols for individual lines by setting the protocol for incoming and outgoing connections and changing the default (preferred) protocol for a line. The default transport protocol is Telnet.
To specify transport protocols, use one or more of these commands in line configuration mode:
Command | Task |
|---|---|
|
|
|
|
|
|
|
The system accepts a host name entry at the EXEC system prompt as a Telnet command. If you incorrectly type the host name, the system interprets the entry as an incorrect Telnet command and displays an error message indicating that the host does not exist. The transport preferred none command disables this option if you incorrectly type a command at the EXEC prompt, and the system does not attempt to make a Telnet connection.
You can set a time limit on a terminal session and specify a warning to the user when a session is about to time out. To limit terminal sessions, use one or more of these commands in line configuration mode:
Command | Task |
|---|---|
| |
|
|
|
|
This section describes modem control and how to configure it on the modem port. These subsections are included:
Figure 2-1 illustrates how modem control works on the DSLAM auxiliary port.

These figures show two processes:
In the figures, the current signal state and the signal line are listed inside each box. The state of the line is listed next to the box. (You can display the current state of a line with the show line command.) Events that change that state appear in italics along the event path, with the software actions described within the ovals.
EXEC and Daemon Creation on a Line with No Modem Control illustrates line behavior when no modem control is set. The DTR output is always high, and CTS and RING are ignored. The DSLAM creates an EXEC when the activation character is typed. Incoming Transmission Control Protocol (TCP) connections occur instantly if the line is not in use and can be closed only by the remote host.
With the dialup capability, you can set a modem to automatically dial the phone number of a remote DSLAM. This feature offers cost savings because phone line connections are made as needed. You pay for using the phone line only when there is data to be received or sent. To configure a line for automatic dialing, use this command in line configuration mode:
Command | Task |
|---|---|
|
You can configure a line to automatically answer a modem. You also configure the modem to do this:
![]() |
Note Configuring the modem is a modem-dependent process. |
Wire the modem's CD signal (generally pin 8) to the RING input (pin 22) of the DSLAM, then use this command in line configuration mode:
Command | Task |
|---|---|
|
You can turn on the modem's hardware flow control independently to act on the status of the DSLAM's CTS input. Wire CTS to the signal the modem uses for hardware flow control. If the modem is set to control hardware flow in both directions, you may also need to wire the modem's flow control input to a signal that the DSLAM always sets to high (such as DTR).
Figure 2-2 illustrates the modem dialin process. When the DSLAM detects a signal on the RING input of an idle line, it starts an EXEC or autobaud process on that line. If the RING signal disappears on an active line, the DSLAM closes any open network connections and terminates the EXEC. If the user exits the EXEC or the DSLAM terminates it because of no user input, the line hangs up the modem by lowering the DTR signal for 5 seconds. After 5 seconds, the modem is ready to accept another call.

To configure a line for both incoming and outgoing calls, use this command in line configuration mode:
Command | Task |
|---|---|
|
Figure 2-3 illustrates the modem in-out process.
If the line is activated by:
![]() |
Note If your system uses dial-out modems, consider using access lists to prevent unauthorized use. |
You can change the interval that the DSLAM waits for CTS after raising DTR in response to RING from the default of 15 seconds. To do so, use this command in line configuration mode:
Command | Task |
|---|---|
|
You can configure a line to close all connections from a user's terminal when the terminal is turned off, and prevent inbound connections to devices that are out of service. To do so, use this command in line configuration mode:
Command | Task |
|---|---|
|
Figure 2-4 illustrates the modem printer process requirement for a high CTS throughout the use of the line.

If CTS is not high, the user's typed input is ignored and incoming connections are refused (or stepped to the next line in a rotary group).
A DSLAM can reliably detect a CTS signal change if the signal remains in the new state for at least one full second.
The DSLAM supports dial-in modems that use DTR to control the off-hook status of the telephone line. To do this, use this command while in line configuration mode:
Command | Task |
|---|---|
|
Figure 2-5 illustrates the modem call in process.

When a modem dialing line is idle, the DTR is in a low state and waits for a transition to occur on the RING input. This transition causes the line to raise DTR and start watching the CTS signal from the modem. After the modem raises CTS, the DSLAM creates an EXEC on the line. If the timeout interval (set with the modem answer-timeout command) expires before the modem raises CTS, the line lowers DTR and returns to the idle state
![]() |
Note The modem callin and modem printer line configuration commands ensure that when the line is hung up or CTS drops, the line reverts from SLIP mode to normal interactive mode. These commands do not work if you use the async dedicated command to put the line in network mode permanently. |
Although you can use the modem callin line configuration command with newer modems, the modem dialin line configuration command described earlier in this section is more appropriate. The modem dialin command frees up CTS for hardware flow control. Modern modems do not require the DTR to take a phone line off-hook.
You can make connections to the next free line in a group of lines, also called a rotary or hunt group. A line can be in only one rotary group. A rotary group can consist of a single line or several contiguous lines. The console line (line 0) cannot be in a rotary group.
If you want to assign the rotary as the single auxiliary port line because the auxiliary port is not necessarily the same line number on all hardware. By assigning the line to a rotary group, you do not have to track the actual line number. Another reason to use a rotary group is that if the device supports local area transport (LAT), an inbound service can only be bound to a rotary group. It cannot be bound to a port number.
To configure a rotary group, use this command in line configuration mode:
Command | Task |
|---|---|
|
|
Modems that operate over normal dial-up telephone lines at speeds of 9600 bits per second (bps) and higher do not guarantee a specific throughput; instead, they operate at a speed that depends on the quality of the line, the effectiveness of data compression algorithms on the data being transmitted, and other variables. These modems use hardware flow control to stop the data from reaching the host by toggling an EIA/TIA-232 signal when they cannot accept any more data.
In addition to hardware flow control, dial-up modems require special software handling. You must configure the modems to:
The DSLAM supports hardware flow control on its CTS input, which is also used by the normal modem handshake. To configure and use a high-speed modem, perform these tasks, beginning in line configuration mode:
Step | Command | Task |
|---|---|---|
1 |
| |
2 |
|
|
3 |
| |
4 |
|
The DSLAM can receive incoming connections on the auxiliary port. This capability allows you to attach serial printers, modems, and other shared peripherals to the DSLAM and drive them remotely from other systems. The DSLAM supports reverse TCP connections.
The specific TCP port or socket to which you attach the peripheral device determines the type of service the DSLAM provides on that line. When you attach the serial lines of a computer system or a data terminal switch to the auxiliary port of the DSLAM, the DSLAM acts as a network front end for a host that does not support the TCP/IP protocols. This arrangement is sometimes called front-ending or reverse connection mode.
To connect the auxiliary port, the remote host or terminal must specify a particular TCP port on the DSLAM. If Telnet protocols are required, that port is 2000 (decimal) plus the decimal value of the line number.
If a raw TCP stream is required, the port is 4000 (decimal) plus the decimal line number. The raw TCP stream is usually the required mode for sending data to a printer.
The Telnet protocol requires that carriage return characters be translated into carriage return and line feed character pairs. You can turn this translation off by specifying the Telnet binary mode option. To specify this option, connect to port 6000 (decimal) plus the decimal line number.
In line configuration mode, you can set terminal operation characteristics for that line until you change the line parameters.
You can temporarily change the line settings using the terminal EXEC commands described in the "Cisco DSLAM User Interface."
Define the terminal operation characteristics by performing the tasks in these sections:
You can specify the type of terminal connected to a line. This feature has two benefits: it records the type of terminal attached to a line, and it can inform the remote host of the terminal type for display management. To specify the terminal type, use this command in line configuration mode:
Command | Task |
|---|---|
|
|
By default, the DSLAM provides a screen display of 24 lines by 80 characters. You can reconfigure these values if they do not meet the needs of your terminal by performing these tasks in line configuration mode:
Step | Command | Task |
|---|---|---|
1 |
|
|
2 |
|
|
The values set can be learned by some host systems that use this type of information in terminal negotiation. Set a value of 0 for the screen length to disable pausing between windows of output.
You can define or modify the default key sequences to execute functions for system escape, terminal activation, disconnect, and terminal pause. To define or change the default sequence, use one or more of these commands in line configuration mode:
Command | Task |
|---|---|
|
|
|
|
|
|
|
|
![]() |
Note If you are using the autoselect command, do not change the activation character from the default value of Return. If you change this default, autoselect may not function immediately. |
You can use a 7-bit character set (such as ASCII) or you can enable a full 8-bit international character set (such as ISO 8859) to allow special graphical and international characters for use in banners and prompts, and to add special characters such as software flow control. You can configure these settings globally by interface or locally at the user level. Use these criteria for determining the configuration mode to use when setting up this feature:
![]() |
Note Setting the EXEC character width to 8 bits can cause failures. If a user on a terminal that is sending parity enters the help command, an unrecognized command message appears because the system is reading all 8 bits, although the eighth bit is not needed for the help command. |
To specify a character set on a global basis, use one or both of these commands in global configuration mode:
Command | Task |
|---|---|
| |
|
To specify a character set based on hardware or software, or on a per-line basis, use the appropriate command in line configuration mode:
Command | Task |
|---|---|
|
|
|
|
|
|
|
|
![]() |
Note If you are using the autoselect function, let the activation character default to Return, and exec-character-bits default to 7. If you change these defaults, the application does not recognize the activation request. |
You can change the character padding on a specific output character. Character padding adds a number of null bytes to the end of the string and can make a string conform to an expected length. To set character padding, use this command in line configuration mode:
Command | Task |
|---|---|
|
|
To disable enhanced editing mode and revert to the editing mode of earlier software releases, use this command in line configuration mode:
Command | Task |
|---|---|
|
|
You can disable enhanced editing if you have prebuilt scripts that do not interact well when enhanced editing is enabled. You can reenable enhanced editing mode using the editing command.
You can provide the host name, line number, and location each time an EXEC is started or an incoming connection is made. The line number banner appears immediately after the EXEC banner or incoming banner. It is useful for tracking problems with modems because it lists the host and line for the modem connection. Modem information is also included if applicable.
To provide service line number information, use this command in global configuration mode:
Command | Task |
|---|---|
|
|
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, perform these tasks in line configuration mode:
Step | Command | Task |
|---|---|---|
1 |
| |
2 |
|
|
You can enable password checking on a per-user basis so that authentication is based on the user name specified with the username global configuration command. To enable this type of password checking, use one of these commands in line configuration mode:
Command | Task |
|---|---|
| |
|
|
Use the login tacacs command with Terminal Access Controller Access Control System (TACACS) and extended TACACS Plus. Use the login authentication command with authentication, authorization, and accounting (AAA)/TACACS+.
By default, virtual terminals require passwords. 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. Use the no login command to disable this behavior and allow connections without a password.
This example shows password checking enabled for a virtual terminal line 1:
DSLAM(config)# line vty 1 DSLAM(config-line)# login DSLAM(config-line)# password letmein
This example shows password checking enabled on a per-user basis:
DSLAM(config)# username jksmith password 0 letmein DSLAM(config)# username lmjones password 0 littlerock DSLAM(config)# line vty 1 DSLAM(config-line)# login local
These sections explain how to configure terminal messages:
You can configure a message-of-the-day (MOTD) banner to display on all connected terminals. This message is displayed at login and is useful for sending messages that affect all network users, such as impending system shutdowns. To do so, use this command in global configuration mode:
Command | Task |
|---|---|
|
You can configure a line activation message to display when an EXEC process such as line activation or an incoming connection to a virtual terminal is created. To do so, use this command in global configuration mode:
Command | Task |
|---|---|
|
You can configure a message to display on terminals connected to reverse Telnet lines. This message is useful for providing instructions to users of these types of connections. Reverse Telnet connections are described in more detail in the section "Supporting Reverse TCP Connections".
To configure the message that will be sent on incoming connections, use this command in global configuration mode:
Command | Task |
|---|---|
|
|
You can configure messages to display on a console or terminal that is not in use. Also called a vacant message, this message is different from the banner message displayed when an EXEC process is activated. To configure an idle terminal message, use this command in line configuration mode:
Command | Task |
|---|---|
|
|
You can control display of the MOTD and line activation banners. By default, these banners display on all lines. To suppress or resume these messages, use one of these commands in line configuration mode:
Command | Task |
|---|---|
|
|
|
This example shows how to use the banner global configuration command and
no exec-banner line configuration command to notify your users that the server will be reloaded with new software:
DSLAM(config)# banner exec / Enter TEXT message. End with the character '/'. Unauthorized access prohibited./ DSLAM(config)# banner incoming / You are connected to a Hayes-compatible modem. Enter the appropriate AT commands. Remember to reset anything to change before disconnecting. / DSLAM(config)# banner motd / The switch will go down at 6pm for a software upgrade. / DSLAM(config)# line vty 0 4 DSLAM(config-line)# no exec-banner DSLAM(config-line)#
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Tue Sep 19 10:55:55 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.