|
|
This chapter describes how to locally change the terminal and line settings. The local settings temporarily override those made by the system administrator, remaining in effect only until you exit the system.
You can make the following local changes to the terminal and line settings.
You can perform all but the last task at the user-level EXEC prompt. Display system debugging messages at the privileged-level EXEC prompt. Each task is described in the following sections.
To see an online list of the supported terminal parameter-setting commands, use the terminal ? command:
terminal ?To specify the type of terminal connected to the current line, use the terminal terminal-type command. Indicate the terminal type if it is different from the default of VT100. This name is used by TN3270 for display management, and by Telnet and rlogin to inform the remote host of the terminal type. This command has the following syntax:
terminal terminal-type terminal-type| terminal-type | Defines the terminal name and type and allows terminal negotiation by hosts that provide that type of service. The default is VT100. |
The following example defines the terminal on line 7 as a VT220:
cs> terminal terminal-type VT220
You can set the number of lines on the current terminal screen using the terminal length screen-length command. Enter a bigger value for a larger number of lines on the screen. The screen length specified can be learned by remote hosts. For example, the rlogin protocol uses the screen length to set up terminal parameters on a remote UNIX host. The command has the following syntax:
terminal length screen-lengthSyntax Description
| screen-length | The desired number of lines on the screen. The server uses this value to determine when to pause during multiple-screen output. The default length is 24 lines. A value of zero prevents the server from pausing between screens of output. That is, if there is too much screen output to fit on the screen, the output scrolls past. |
The following example prevents the server from pausing between multiple screens of output:
pt> terminal length 0
You can set the escape character for the current terminal line using the terminal escape-character command. This is useful, for example, if you have the default escape character defined for a different purpose in your keyboard file. Entering the escape character followed by the X key returns you to EXEC mode when you are connected to another computer. The default escape characters are Ctrl-^. The command has the following syntax:
terminal escape-character ASCII-number| ASCII-number | Either the ASCII decimal representation of the desired escape character or a control sequence (Ctrl-P, for example). The default is Ctrl-^. Typing the escape character followed by the X key returns you to the EXEC when you are connected to another computer. See Appendix A, "ASCII Character Set," for a list of ASCII characters. |
The following example sets the escape character to Ctrl-P (ASCII decimal 16):
cs> terminal escape-character 17
You can specify the current keyboard type using the terminal keymap-type command. This is necessary when the keyboard you are using is other than the default of VT100. The system administrator can define other keyboard types and provide you with their names. This command has the following syntax:
terminal keymap-type keymap-name| keymap-name | The name defining the current keyboard type. The default is VT100. |
The following example specifies a VT220 keyboard as the current keyboard type:
cs> terminal keymap-type vt220
A hold character helps control display of information on a terminal screen when information is scrolling by too fast by using the terminal hold-character command. Typing the hold character temporarily halts the output at the terminal. To continue the output, type any other character. You can set, change, or remove the hold character. You cannot suspend output on the console terminal. Typing the hold character temporarily halts the output at the terminal. To continue the output, type any other character. To send the hold character to the host, precede it with the escape character. This command has the following syntax:
terminal hold-character ASCII-number| ASCII-number | Either the ASCII decimal representation of the hold character or a control sequence (for example, Ctrl-P). By default, no local hold character is set. The Break character is represented by zero; NULL cannot be represented. |
The following example removes the previously set hold character:
cs> terminal no hold-character
You can define the generation of the parity bit for the current terminal line using the terminal parity command. Communication protocols provided by devices such as terminals and modems often require a specific parity bit setting. The default is no parity. This command has the following syntax:
terminal parity {none | even | odd | space | mark}| none | No parity. This is the default. |
| even | Even parity. |
| odd | Odd parity. |
| space | Space. |
| mark | Mark. |
The following example shows how to set the parity bit to odd:
cs> terminal parity odd
You can set the transmit and receive speeds of the current terminal line using the terminal speed command. The default speed is 9600 bits per second (bps). This command has the following syntax:
terminal speed bps| bps | The baud rate in bits per second (bps). The default is 9600 bits per second. |
The following example sets the current auxiliary line transmit and receive speed to 2400 bps.
pt> terminal speed 2400
You can change the number of data bits per character for the current terminal line using the terminal databits command. Communication protocols provided by devices such as terminals and modems often require a specific data bit setting. The default is 8 data bits per character. You can change to 5, 6, or 7 (or back to 8). Enter the following command at the EXEC prompt:
terminal databits {5 | 6 | 7 | 8}| 5 | Five databits per character. |
| 6 | Six databits per character. |
| 7 | 7 databits per character. |
| 8 | 8 databits per character. This is the default. |
The terminal databits command can be used to mask the high bit on input from devices that generate 7 data bits with parity. If parity is being generated, specify 7 data bits per character. If no parity generation is in effect, specify 8 data bits per character. The other keywords are supplied for compatibility with older devices and generally are not used.
The following example shows how to change the databits per character to seven:
pt> terminal databits 7
You can change the number of stop bits transmitted per byte by the current terminal line using the terminal stopbits command. Communication protocols provided by devices such as terminals and modems often require a specific stopbit setting. This command has the following syntax:
terminal stopbits {1 | 1.5 | 2}| 1 | One stop bit. |
| 1.5 | One and a half stop bits. |
| 2 | 2 stop bits. This is the default. |
The following example illustrates how to change the stop bits to one:
cs> terminal stopbits 1
Flow control allows you to protect against overwhelming a device with too much data. You can set up data flow control for the current terminal line in one of two ways: software flow control, which is done with control key sequences, and hardware flow control, which is done at the device level. By default, no flow control method is set for a line. You can set flow control for the current terminal line using the terminal flowcontrol command. This command has the following syntax:
terminal flowcontrol {none | software [in | out] | hardware}| none | Prevents flow control. |
| software | Sets software flow control. |
| [in | out] | (Optional.) Specifies the direction: in causes the server to listen to flow control from the attached device, and out causes the server to send flow control information to the attached device. If you do not specify a direction, both directions are assumed. |
| hardware | Sets hardware flow control. For information about setting up the RS-232 line, see the hardware manual for your product. |
By default, no flow control method is set. This default is returned with the none keyword. For software flow control, the default stop and start characters are Ctrl-S and Ctrl-Q (XOFF and XON). You can change them with the terminal stop-character and terminal start-character commands.
The following example sets incoming software flow control:
pt> terminal flowcontrol software in
This character signals the start of data transmission when software flow control is in effect. You can change the flow control start character with the terminal start-character command. This command has the following syntax:
terminal start-character ASCII-number| ASCII-number | The ASCII decimal representation of the start character. The default is Ctrl-Q (ASCII decimal character 17) |
The following example changes the start character to Ctrl-O (ASCII decimal character 15):
pt> terminal start-character 15
This character signals the end of data transmission when software flow control is in effect. You can change the flow control stop character using the terminal stop-character command. This command has the following syntax:
terminal stop-character ASCII-number| ASCII-number | The ASCII decimal representation of the stop character. The default is Ctrl-S (ASCII character 19). |
The following example changes the stop character to Ctrl-E, which is ASCII character 5.
pt> terminal stop-character 5
Character padding adds a number of null bytes to the end of the string and can be used to make a string an expected length for conformity. You can change the character padding on a specific output character using the terminal padding command. This command has the following syntax:
terminal padding ASCII-number count| ASCII-number | The ASCII decimal representation of the character. |
| count | The number of NULL bytes sent after that character, up to 255 padding characters in length. |
The following example pads Ctrl-D (ASCII decimal character 4) with 164 NULL bytes:
pt> terminal padding 4 164
The end of each line typed at the terminal is ended with a RETURN (CR). You can cause the current terminal line to send a CR as a CR followed by a NULL instead of a CR followed by a LINE FEED (LF). This scheme permits interoperability with different interpretations of end-of-line handling in the Telnet protocol specification. Use the terminal telnet-transparent command, which has the following syntax:
terminal telnet-transparentThis command has no arguments or keywords.
At times, you might want to queue up a string of characters until they fill a complete packet and then transmit the packet to a remote host. This can make more efficient use of a line because the server normally dispatches each character as it is typed. You can define a character that causes a packet to be sent with the terminal dispatch-character command. This command has the following syntax:
terminal dispatch-character ASCII-number1 [ASCII-number2 . . . ASCII-number]| ASCII-number | The ASCII decimal representation of the character, such as Return (ASCII character 13) for line-at-a-time transmissions. The command can take multiple arguments, so you can define any number of characters as the dispatch character. |
The following examples defines the characters Ctrl-D (ASCII decimal character 4) and Ctrl-Y (ASCII decimal character 19) as the dispatch characters:
cs> terminal dispatch-character 4 25
You can set a line up to inform a user who has multiple, concurrent Telnet connections when output is pending on a connection other than the current one. You might want to know, for example, when another connection receives mail or a message. Use the terminal notify command, which has the following syntax:
terminal notifyThis command has no arguments or keywords.
You can temporarily set the ability of a line to act as a transparent pipe for file transfers using the terminal download command. You can use this feature to run a program such as KERMIT, XMODEM, or CrossTalk that downloads a file across a communication server or protocol translator line. This command has the following syntax:
terminal downloadThis command has no arguments or keywords.
You can use the terminal transport preferred command to specify the preferred protocol to use when a command does not specify one. For servers that support LAT, the default protocol is LAT. For those that do not support LAT, the default is Telnet. Other options include the UNIX rlogin and X.29 PAD protocols. This command has the following syntax:
terminal transport preferred {telnet | pad | lat | rlogin | none}| telnet | Specifies the TCP/IP Telnet protocol. |
| pad | Specifies X.3 PAD, which is used most often to connect a server to X.25 hosts. |
| lat | Specifies the LAT protocol. |
| rlogin | Specifies UNIX rlogin. |
| none | Prevents any protocol selection on the line. The system normally assumes that any unrecognized command is a host name. If the protocol is set to none, the system no longer makes that assumption. No connection will be attempted if the command is not recognized. |
The following example illustrates how to configure the console to not connect when an unrecognized command is entered:
cs> terminal transport preferred none
To set the number of data bits per character that are interpreted and generated by software for the current line, use the terminal data-character-bits EXEC command. This command is used primarily to strip parity from X.25 connections on IGS or Cisco 3000 routers with the protocol translation software option. The terminal data-character-bits command does not work on hardwired lines. This command has the following syntax:
terminal data-character-bits {7 | 8}| 7 | Seven data character bits. |
| 8 | Eight data character bits. This is the default. |
The following example sets the data bits per character on the current line to 7:
cs> terminal data-character-bits 7
To set the character dispatch timer for the current terminal line, use the terminal dispatch-timeout command. Use this command to increase the processing efficiency of the remote host. This command has the following syntax:
terminal dispatch-timeout milliseconds| milliseconds | An integer that specifies the number of milliseconds the server waits after putting the first character into a packet buffer before sending the packet. During this interval, more characters can be added to the packet, which increases processing efficiency on the remote host. |
The following example sets the dispatch timer to 80 milliseconds:
cs> terminal dispatch-timeout 80
To change the ASCII character widths to accept special characters for the current terminal line, use the terminal special-character-bits EXEC command. This is useful, for example, if you want the server to temporarily support international character sets. It overrides the default-value special-character-bits global configuration command and is used to compare character sets typed by the user with the special character available during a data connection, which includes software flow control and escape characters. When you exits the system, the command is reset to the default value established by the global configuration command. This command has the following syntax:
terminal special-character-bits {7 | 8} When you exit the system, the character width is reset to the default value established by the global configuration command. However, setting the EXEC character width to eight bits can also cause failures. If a user on a terminal that is sending parity enters the command help, an "unrecognized command" message appears because the system is reading all eight bits, although the eighth bit is not needed for the help command.
The following example temporarily configures a server to use a full 8-bit user interface for system banners and prompts. When you exit the system, character width will be reset to the width established by the default-value exec-character-bits global configuration command.
cs> terminal special-character-bits 8
To set the terminal receive (from terminal) speed for the current terminal line, use the terminal rxspeed command. This command has the following syntax:
terminal rxspeed bps| bps | The baud rate in bits per second (bps). The default is 9600 bps. Table 6-1 lists line speeds for communication servers, protocol translators, and other devices that run protocol translation. |
Use Table 6-1 as a guide for setting the line speeds.
| Server Model | Baud Rates |
|---|---|
| 500-CS | Any speed between 50 and 38400. |
| ASM-CS | The standard speeds include 75, 110, 134, 150, 300, 600, 1200, 2000, 2400, 4800, 1800, 9600, and 19200.
Nonstandard speeds include 11520, 12800, 14400, 16457, 23040, 28800, 38400, and 57600. |
| Cisco 7000, AGS, CGS, MGS | 50, 75, 110, 134, 150, 200, 300, 600, 1050, 1200, 2000, 2400, 4800, 9600, 19200, and 38400. |
| IGS, Cisco 2000, Cisco 3000, Cisco 4000 | 75, 110, 134, 150, 300, 600, 1200, 2000, 2400, 4800, 1800, 9600, 19200, and 38400. |
The following example sets the current auxiliary line receive speed to 2400 bps:
cs> terminal rxspeed 2400
To set the terminal transmit (to terminal) on the current terminal line, use the terminal txspeed command. This command has the following syntax:
terminal txspeed bps| bps | The baud rate in bits per second (bps). The default is 9600 bps. Table 6-1 lists line speeds for communication servers, protocol translators, and other devices that run protocol translation. |
Use Table 6-1 as a guide for setting the line speeds.
The following example sets the current auxiliary line transmit speed to 2400 bps:
pt> terminal txspeed 2400
The EXEC provides the ability to display debug command output and system error messages on the current terminal using the terminal monitor command. Remember that all terminal parameter-setting commands are set locally and do not remain in effect after a session is ended. You will need to perform this task at the privileged-level EXEC prompt at each session to see the debugging messages. This command has the following syntax:
terminal monitorThis command has no arguments or keywords.
|
|