|
|
When receiving a local-area transport (LAT) connection request to a service name, to set up the Cisco router to automatically translate the request to another outgoing protocol connection type, use the translate lat command in global configuration mode.
translate lat incoming-service-name [in-option] protocol outgoing-address [out-options] [global-options]
Syntax Description
Defaults
No default translation parameters
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
Table 129 provides a visual aid for the translate lat command. You define protocol translation connections by supplying a protocol keyword and the address, host name, or service name, followed by optional features. Global options apply to most connection types, but there are exceptions.
| Incoming Address | Incoming Options | Outgoing Protocol | Outgoing Options | Global Options |
|---|---|---|---|---|
incoming-address | [in-options] | protocol outgoing-address | [out-options] | [global-options] |
lat service-name | unadvertised | x25 x.121-address | cud c-u-data | access-class number |
|
| no-reverse | max-users number | |
profile profile | local | |||
reverse | login | |||
tcp ip-address | port number | quiet | ||
| host-name name |
| ||
multibyte-IAC | ||||
slip ip-address | ip-pool [scope-name name] | |||
| headercompression [passive] | |||
routing | ||||
keepalive number-of-seconds | ||||
mtu bytes | ||||
ppp ip-address | ip-pool [scope-name name] | |||
| headercompression [passive] | |||
routing | ||||
keepalive number-of-seconds | ||||
mtu bytes | ||||
authentication {pap | chap} | ||||
ppp use-tacacs | ||||
ipx loopback number | ||||
autocommand [arap | exec-string] | ||||
Examples
The following example illustrates incoming LAT to outgoing TCP translations. The unadvertised keyword prevents broadcast of service advertisements to other servers. Outgoing translated packets are transmitted to IP host rubble, TCP port 4005.
translatelat pt-printer1unadvertisedtcp rubble port 4005incoming option outgoing option
The following example translates LAT on an incoming line to SLIP on an outgoing line. It uses header compression only if incoming TCP packets on the same interface are compressed.
translate lat rudolph slip 10.0.0.4 header-compression
incoming outgoing option
The following example first shows the command to disable keepalive packets on a PPP line, then shows sample output from the show translate command when keepalive packets have been turned off on the line.
translate lat ramble ppp 172.21.2.2 keepalive 0
.
.
router# show translate
Translate From: LAT ramble
To: PPP 172.21.2.2 keepalive 0
0/0 users active, 0 peak, 0 total, 0 failures
Related Commands
Displays configured translation sessions. Translates a TCP connection request automatically to another outgoing protocol connection Translates an X.25 connection request automatically to another outgoing protocol connection x29 access-list Limits access to the access server from certain X.25 hosts. x29 profile Creates a PAD profile script for use by the translate command.
Command
Description
When receiving a local-area transport (LAT) connection request to a service name, to set up the Cisco router to automatically translate the request to another outgoing protocol connection type, use the translate lat command in global configuration mode.
The command syntax that follows shows how to apply a virtual interface template in place of outgoing translate options. If you are using virtual templates for protocol translation, all outgoing options are defined in the virtual interface template. Table 130 lists all outgoing options and their corresponding interface configuration commands.
translate lat incoming-service-name [unadvertised] virtual-template number [global-options]
Syntax Description
Defaults
No default translation parameters
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
You define the protocol translation connections by choosing a protocol keyword and supplying the appropriate address, host name, or service name. The protocol connection information is followed by optional features for that connection, as appropriate. For example, the binary option is only appropriate with TCP/IP connections. The global options, in general, apply to all the connection types, but there are exceptions.
Rather than specifying outgoing translation options in the translate command, configure these options as interface configuration commands under the virtual interface template, then apply the virtual interface template to the translate command. Table 130 maps outgoing translate command options to interface commands you can configure in the virtual interface template.
| Translate Command Options | Corresponding Interface Configuration Command |
|---|---|
peer default ip address {ip-address | dhcp | pool [poolname]} | |
ip tcp header compression [on | off | passive] | |
ip routing or ipx routing | |
mtu | |
keepalive | |
ppp authentication {chap | pap} | |
ppp use-tacacs | |
ipx ppp-client loopback number |
Examples
The following example configures PPP tunneling from a PC across a LAT network. The remote PC is given the IP address 10.12.118.12 when it dials in. The unadvertised keyword prevents broadcast of service advertisements to other servers.
interface Virtual-Template1 ip unnumbered Ethernet0 peer default ip address 10.12.118.12 ppp authentication chap !translatelat pt-printer1unadvertisedvirtual-template 1incoming option outgoing
Related Commands
Displays configured translation sessions. Translates a TCP connection request automatically to another outgoing protocol connection. Translates an X.25 connection request automatically to another outgoing protocol connection. x29 access-list Limits access to the access server from certain X.25 hosts. x29 profile Creates a PAD profile script for use by the translate command.
Command
Description
When receiving a TCP connection request to a particular destination address or host name, the Cisco router can automatically translate the request to another outgoing protocol connection type. To set this up, use the translate tcp command in global configuration mode.
translate tcp incoming-address [in-options] protocol outgoing-address [out-options] [global-options]
Syntax Description
Defaults
No default translation parameters
Command Modes
Global configuration
Command History
11.2 This command was introduced.
Release
Modification
Usage Guidelines
Table 131 provides a visual aid for understanding how to use the translate tcp command. As the table illustrates, you define the protocol translation connections by choosing a protocol keyword and supplying the appropriate address, host name, or service name. The protocol connection information is followed by optional features for that connection, as appropriate. For example, the binary option is only appropriate with TCP/IP connections. The global options, in general, apply to all the connection types, but there are exceptions.
| Incoming Protocol | Incoming Options | Outgoing Protocol | Outgoing Options | Global Options |
|---|---|---|---|---|
protocol incoming-address | [in-options] | protocol outgoing-address | [out-options] | [global-options] |
tcp ip-address | host_name | port number | lat service-name | node node-name | access-class number |
| binary |
| port port-name | max-users number |
| stream | x25 x.121-address | cud c-u-data | local |
| printer |
| no-reverse | login |
|
| profile profile | quiet | |
| reverse |
| ||
| slip ip-address | ip-pool [scope-name name] | ||
|
| headercompression [passive] | ||
| routing | |||
| keepalive number-of-seconds | |||
| mtu bytes | |||
| ppp ip-address | ip-pool | ||
|
| headercompression [passive] | ||
| routing | |||
| keepalive number-of-seconds | |||
| mtu bytes | |||
| authentication {pap | chap} | |||
| ppp use-tacacs | |||
| ipx loopback number | |||
| autocommand [arap | exec-string] |
| ||
Examples
The following example illustrates the use of the TCP incoming protocol option printer for an incoming TCP connection:
translatetcp 172.19.32.250printerx25 5678incomingoption outgoing
The following example permits clients running IPX/PPP to connect through the device's VTY lines to a server running PPP:
interface loopback0 no ip address ipx network 544 ipx sap-interval 2000 ! translate tcp 172.21.14.67 port 1234 ppp 10.0.0.2 ipx loopback0 ! incoming outgoing option
Related Commands
Displays configured translation sessions. Translates a TCP connection request automatically to another outgoing protocol connection. Translates an X.25 connection request automatically to another outgoing protocol connection. x29 access-list Limits access to the access server from certain X.25 hosts. x29 profile Creates a PAD profile script for use by the translate command.
Command
Description
When receiving a TCP connection request to a particular destination address or host name, to set up the Cisco router to automatically translate the request to another outgoing protocol connection type, use the translate tcp command in global configuration mode.
The command syntax that follows shows how to apply a virtual interface template in place of outgoing translate options. If you are using virtual templates for protocol translation, all outgoing options are defined in the virtual interface template.
translate tcp incoming-address [in-options] virtual-template number [global-options]
Syntax Description
Defaults
No default translation parameters
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
You define the protocol translation connections by choosing a protocol keyword and supplying the appropriate address, host name, or service name. The protocol connection information is followed by optional features for that connection, as appropriate. For example, the binary option is only appropriate with TCP/IP connections. The global options, in general, apply to all the connection types, but there are exceptions.
Examples
The following example illustrates the use of the TCP incoming option printer for an incoming TCP connection:
interface Virtual-Template1 ip unnumbered Ethernet0 peer default ip address 10.12.108.1 ppp authentication chaptranslatetcp 172.19.32.250printerVirtual-Template1incoming option outgoing
Related Commands
Displays configured translation sessions. Translates a TCP connection request automatically to another outgoing protocol connection. Translates an X.25 connection request automatically to another outgoing protocol connection. x29 access-list Limits access to the access server from certain X.25 hosts. x29 profile Creates a PAD profile script for use by the translate command.
Command
Description
When receiving an X.25 connection request to a particular destination address, or set up the Cisco router to automatically translate the request to another outgoing protocol connection type, use the translate command in global configuration mode.
translate x25 incoming-address [in-options] protocol outgoing-address [out-options] [global-options]
Syntax Description
Defaults
No default translation parameters
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
Table 132 provides a visual aid for understanding how the command syntax flows for the translate x25 command. In the table, follow the steps horizontally (from left to right). As you travel from step to step, you can choose from a vertical list of options at each step. As the table illustrates, you define the protocol translation connections by choosing a protocol keyword and supplying the appropriate address or service name. The protocol connection information is followed by optional features for that connection, as appropriate. The global options, in general, apply to all the connection types, but there are exceptions. The swap keyword, for example, is for X.25 to TCP translations only. See the examples for more explanations on how to enter this command.
To use virtual templates with incoming X.25 translation, see the translate x25 (virtual access interfaces) command.
| Incoming
Address
| Incoming Options
| Protocol Outgoing Address
| Outgoing
Options
|
Global Options
| |
|---|---|---|---|---|---|
translate x25 | x.21 address | idle minutes | lat service-name | use-map | access-class number |
| cud c-u-data | tcp ip-address | node node-name | max-users number | |
profile profile | slip ip-address | port port-name | local | ||
accept-reverse | ppp ip-address | port number | login | ||
printer | autocommand [arap | exec-string] | host-name name | quiet | ||
idle minutes |
| multibyte-iac | swap | ||
| ip-pool [scope-name name] | pvc [number | interface serial-number] packetsize in-size out-size windowsize in-size out-size | |||
headercompression [passive] |
| ||||
routing |
| ||||
keepalive number-of-seconds |
| ||||
mtu bytes |
| ||||
ip-pool |
| ||||
headercompression [passive] |
| ||||
routing |
| ||||
keepalive number-of-seconds |
| ||||
mtu bytes |
| ||||
authentication |
| ||||
ppp use-tacacs |
| ||||
ipx loopback number |
| ||||
|
| ||||
|
| ||||
Examples
The following example illustrates a simple X.25-to-TCP translate x25 command. Packets coming in X.25 address 652365123 arrive via PVC 1 and are translated to TCP packets and sent out IP address 172.16.1.1.
translatex25 652365123pvc 1tcp 172.16.1.1!incomingoption outgoing
The following example illustrates a more complex configuration that calls an X.29 profile and swaps the default PAD operation of the router to that of an X.25 host. The name of the profile is fullpackets.
x29 profile fullpackets 2:0 3:0 4:100 7:21translatex25 217536124profile fullpacketstcp rubbleport 4006swap!incoming option outgoing option global
The following example illustrates the use of the X.25 incoming protocol option printer for an incoming X.25 connection:
translatex25 55555printertcp 172.16.1.1!incomingoption outgoing
The following example translates X.25 packets to PPP. It enables routing updates between the two connections:
translate x25 12345678 ppp 10.0.0.2 routing ! incoming outgoing option
The following example permits clients running ARA to connect through the devices' virtual terminal lines to an AppleTalk network:
appletalk routing translate x25 12345678 autocommand arap ! incoming outgoing arap enable arap dedicated arap timelimit 45 arap warningtime 5 arap noguest arap require-manual-password arap net-access-list 614
The following example specifies IP pooling from a DHCP server named ludicrous. It then specifies that incoming TCP traffic be translated to SLIP. The DHCP server will dynamically assign IP addresses on the outgoing sessions.
ip address-pool dhcp-proxy-client ip dhcp-server ludicrous translate x25 5467835 ppp ip-pool scope-name ludicrous
The following example specifies a local IP pool named scandal with IP addresses ranging from 172.18.10.10 to 172.18.10.110. It then specifies that incoming X.25 traffic be translated to PPP. The local IP pool scandal will be used to dynamically assign IP addresses on the outgoing sessions.
ip-pool scandal 172.18.10.10 172.18.10.110 translate x25 1234567 ppp ip-pool scope-name scandal
X.25 calls are cleared if they are idle for the configured time, as shown in the following example:
translate x25 1234 idle 2 lat shazam
Related Commands
Displays configured translation sessions. When a LAT connection request to a service name is received, the Cisco router can automatically translate the request to another outgoing protocol connection type. When a TCP connection request to a particular destination address or host name is received, the Cisco router can automatically translate the request to another outgoing protocol connection type. x29 access-list Limits access to the access server from certain X.25 hosts. x29 profile Creates a PAD profile script for use by the translate command.
Command
Description
When receiving a X.25 connection request to a particular destination address, to set up the Cisco router to automatically translate the request to another outgoing protocol connection type, use the translate x25 command in global configuration mode.
The command syntax that follows shows how to apply a virtual interface template in place of outgoing translate x25 options. If you are using virtual templates for protocol translation, all outgoing options are defined in the virtual interface template. Table 133 lists all outgoing options and their corresponding interface configuration commands.
x25 incoming-address [in-options] virtual-template number [global-options]
Syntax Description
incoming-address in-options (Optional) Incoming connection request options. These arguments can have the following values: virtual-template number Apply the virtual interface template specified by number in place of outgoing options. (Optional) Translation options that can be used by any connection type. It can be one or more of the following:
Defaults
No default translation parameters.
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
You define the protocol translation connections by choosing a protocol keyword and supplying the appropriate address or service name. The protocol connection information is followed by optional features for that connection, as appropriate. The global options, in general, apply to all the connection types, but there are exceptions. The swap keyword, for example, is for X.25 to TCP translations only. See the example for more explanations on how to enter this command.
Rather than specifying outgoing translation options in the translate command, configure these options as interface configuration commands under the virtual interface template, then apply the virtual interface template to the translate command. Table 133 maps outgoing translate command options to interface commands you can configure in the virtual interface template.
| Translate Command Options | Corresponding Interface Configuration Command |
|---|---|
peer default ip address {ip-address | dhcp | pool [poolname]} | |
ip tcp header compression [on | off | passive] | |
ip routing or ipx routing | |
mtu | |
keepalive | |
ppp authentication {chap | pap} | |
ppp use-tacacs | |
ipx ppp-client loopback number |
Examples
The following example shows a virtual template with PPP encapsulation specified by default (not explicit). It also specifies CHAP authentication and an X.29 access list.
x29 access-list 1 permit ^5555 ! interface Virtual-Template1 ip unnumbered Ethernet0 peer default ip address 172.16.2.129 ppp authentication chap ! translate x25 5555667 virtual-template 1 access-class 1
Related Commands
Creates a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces. Displays configured translation sessions. When a LAT connection request to a service name is received, the Cisco router can automatically translate the request to another outgoing protocol connection type. When a TCP connection request to a particular destination address or host name is received, the Cisco router can automatically translate the request to another outgoing protocol connection type. x29 access-list Limits access to the access server from certain X.25 hosts. x29 profile Creates a PAD profile script for use by the translate command.
Command
Description
To define which protocols to use to connect to a specific line of the router, use the transport input command in line configuration mode.
transport input {all | lat | mop | nasi | none | pad | rlogin | telnet | v120}
Syntax Description
all Selects all protocols. Restores the default configuration. lat Selects the Digital LAT protocol and specifies both incoming reverse LAT and host-initiated connections. mop Selects Maintenance Operation Protocol (MOP). nasi Select NetWare Access Servers Interface (NASI) as the input transport protocol. none Prevents any protocol selection on the line. This makes the port unusable by incoming connections. pad Selects X.3 PAD incoming connections. rlogin Selects the UNIX rlogin protocol. telnet Specifies all types of incoming TCP/IP connections. v120 Select the V.120 protocol for incoming async over ISDN connections.
Defaults
No protocols allowed on the line (none).
Command Modes
Line configuration
Command History
10.0 This command was introduced. 11.1 The none keyword was added and became the default. Before Cisco IOS Release 11.1, the default keyword was all.
Release
Modification
Usage Guidelines
Cisco routers do not accept incoming network connections to asynchronous ports (TTY lines) by default. You have to specify an incoming transport protocol, or specify the transport input all command 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." This behavior is new as of Cisco IOS Software Release 11.1. Previous to release 11.1, the default was the transport input all command. If you are upgrading to Cisco IOS software version 11.1(1) or later from Cisco IOS software Release 11.0 or earlier, you must add the transport input {protocol | all} command, or you will be locked out of your router.
You can specify one protocol, multiple protocols, all protocols, or no protocols. To specify multiple protocols, enter the keyword for each protocol, separated by a space.
This command can be useful in distributing resources among different types of users, or making certain that only specific hosts can access a particular port. When using two-step protocol translation, the transport input command is useful in controlling exactly which protocols can be translated to other protocols.
Access lists for each individual protocol can be defined in addition to the allowances created by the transport input command. Any settings made with the transport input command override settings made with the transport preferred command.
Examples
The following example sets the incoming protocol to Telnet for vtys 0 to 32:
line vty 0 32 transport input telnet
Related Commands
Determines the protocols that can be used for outgoing connections from a line. Specifies the transport protocol that the Cisco IOS software uses if the user does not specify one when initiating a connection.
Command
Description
To determine the protocols that can be used for outgoing connections from a line, use the transport output command in line configuration mode.
transport output {all | lat | mop | nasi | none | pad | rlogin | telnet | v120}
Syntax Description
all Selects all protocols. lat Selects the Digital LAT protocol, which is the protocol used most often to connect routers to Digital hosts. mop Selects Maintenance Operation Protocol (MOP). nasi Select NetWare Access Server Interface (NASI) as the output transport protocol. 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. pad Selects X.3 PAD, used most often to connect routers to X.25 hosts. rlogin Selects the UNIX rlogin protocol for TCP connections. The rlogin setting is a special case of Telnet. If an rlogin attempt to a particular host has failed, the failure will be tracked, and subsequent connection attempts will use Telnet instead. telnet Selects the TCP/IP Telnet protocol. It allows a user at one site to establish a TCP connection to a login server at another site. v120 Select the V.120 protocol for outgoing asynchronous over ISDN connections.
Defaults
Telnet
Command Modes
Line configuration
Command History
10.0 This command was introduced. 11.1 The following keywords were added:
Release
Modification
Usage Guidelines
You can specify one protocol, multiple protocols, all protocols, or no protocols. To specify multiple protocols, enter the keyword for each protocol, separated by a space.
Any settings made with the transport output command override settings made with the transport preferred command.
Examples
The following example prevents any protocol selection:
transport output none
Related Commands
Defines which protocols to use to connect to a specific line of the router. Specifies the transport protocol that the Cisco IOS software uses if the user does not specify one when initiating a connection.
Command
Description
To specify the transport protocol that the Cisco IOS software uses if the user does not specify one when initiating a connection, use the transport preferred command in line configuration mode.
transport preferred {all | lat | mop | nasi | none | pad | rlogin | telnet | v120}
Syntax Description
all Specifies all recognized protocols. lat Selects the Digital LAT protocol, which is the protocol used most often to connect routers to Digital hosts. mop Specifies the Maintenance Operation Protocol (MOP). nasi Specifies the NetWare Access Server Interface (NASI) protocol. 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 is attempted if the command is not recognized. pad Selects X.3 PAD, used most often to connect routers to X.25 hosts. rlogin Selects the UNIX rlogin protocol for TCP connections. The rlogin setting is part of the Telnet protocol. If an rlogin attempt to a particular host fails, the failure is tracked, and subsequent connection attempts will use Telnet instead. telnet Selects the TCP/IP Telnet protocol. It allows a user at one site to establish a TCP connection to a login server at another site. v120 Specifies asynchronous protocols over ISDN.
Defaults
Telnet
Command Modes
Line configuration
Command History
10.0 This command was introduced. 11.1 The following keywords were added:
Release
Modification
Usage Guidelines
Specify the transport preferred none command to prevent errant connection attempts.
Any settings made with the transport input or transport output commands override settings made with the transport preferred command.
Examples
The following example sets the preferred protocol to Telnet on physical terminal line 1:
line tty 1 transport preferred telnet
Related Commands
Specifies the preferred protocol to use for the current session when a command does not specify one. Defines which protocols to use to connect to a specific line of the router. Determines the protocols that can be used for outgoing connections from a line.
Command
Description
To define characteristics of a terminal emulation file, use the ttycap command in global configuration mode. Use the no form of this command to delete any named ttycap entry from the configuration file.
ttycap ttycap-name termcap-entry
Syntax Description
ttycap-name Name of a file. It can be up to 32 characters long and must be unique. termcap-entry Commands that define the ttycap. Consists of two parts (see the "Usage Guidelines" section for details).
Defaults
VT100 terminal emulation
Command Modes
Global configuration
Command History
10.3 This command was introduced.
Release
Modification
Usage Guidelines
Use the show ttycap EXEC command to test for the availability of a ttycap.
![]() |
Note Do not type a ttycap entry filename "default" or the Cisco IOS software will adopt the newly defined entry as the default. |
The termcap-entry argument consists of two parts: a name portion and a capabilities portion:
The name portion is a series of names that can be used to refer to a specific terminal type. Generally, these names should represent commonly recognized terminal names (such as VT100 and VT200). Multiple names can be used. Each name is separated by a vertical bar symbol (|). The series is terminated by a colon symbol (:).
d0|vt100|vt100-am|vt100am|dec vt100:
The capabilities portion of the termcap-entry consists of a sequence of termcap capabilities. These capabilities can include boolean flags, string sequences, or numeric sequences. Each individual capability is terminated using a colon symbol (:).
The following is an example of a backspace Boolean flag:
bs:
A string sequence is a two-character capability name followed by an equal sign (=) and the character sequence.
The following example illustrates the capability for homing the cursor:
ho=\E[H:
The sequence \E represents the ESC character.
Control characters can be represented in string sequences by entering a two-character sequence starting with a caret symbol (^), followed by the character to be used as a control character.
The following example illustrates the definition of a control character.
bc=^h:
In this example, the backspace is entered into the termcap-entry as the string sequence as the characters "^h."
A numeric sequence is a two-character capability name followed by a number symbol (#) and the number.
The following example represents the number of columns on a screen.
co#80:
Use the backslash symbol ( \ ) to extend the definition to multiple lines. The end of the ttycap termcap-entry is specified by a colon terminating a line followed by an end-of-line character and no backslash.
For the definitions of supported Boolean-flag ttycap capabilities, see Table 134. For the definitions of supported string-sequence ttycap capabilities, see Table 135. For the definitions of supported number-sequence ttycap capabilities, see Table 136. For the definitions of supported color-sequence ttycap capabilities, see Table 137.
| Boolean Flag | Description |
|---|---|
am | Automatic margin |
bs | Terminal can backspace with bs |
ms | Safe to move in standout modes |
nc | No currently working carriage return |
xn | NEWLINE ignored after 80 columns (Concept) |
xs | Standout not erased by overwriting (Hewlett-Packard) |
| String Sequence | Description |
|---|---|
AL | Add line below with cursor sequence |
bc | Backspace if not ^h |
bt | Backtab sequence |
ce | Clear to end of line |
cl | Clear screen, cursor to upper left |
cm | Move cursor to row # and col # |
cr | Carriage return sequence |
cs | Change scrolling region |
DL | Delete the line the cursor is on |
ei | End insert mode |
ho | Home, move cursor to upper left |
ic | Character insert |
im | Begin insert mode |
is | Initialization string (typically tab stop initialization) |
ll | Move cursor to lower left corner |
md | Turn on bold (extra bright) character attribute |
me | Turn off all character attributes |
nd | Nondestructive space |
nl | Newline sequence |
pc | Pad character if not NULL |
rc | Restore cursor position |
rs | Resets terminal to known starting state |
sc | Save cursor position |
se | End standout mode (highlight) |
so | Start standout mode (highlight) |
ta | Tab |
te | End programs that use cursor motion |
ti | Initialization for programs that use cursor motion |
uc | Underline character at cursor |
ue | End underline mode |
up | Move cursor up |
us | Begin underline mode |
vb | Visual bell |
vs | Visual cursor |
ve | Normal cursor |
| Number Sequence | Description |
|---|---|
li | Lines on the screen |
co | Columns on the screen |
sg | Standout glitch, number of spaces printed when entering or leaving standout display mode |
ug | Underline glitch, number of spaces printed when entering or leaving underline mode |
| Color Sequence | Description |
|---|---|
x0 | Black |
x1 | Blue |
x2 | Red or orange |
x3 | Pink or purple |
x4 | Green, which is the default color. |
x5 | Turquoise |
x6 | Yellow |
x7 | Gray or white |
The ttycap database uses these color sequences to translate IBM directives into screen drawing commands. These color sequences control only foreground terminal colors. They do not control background color, which is configured to black by default.
Examples
The following is an example of a ttycap file. Refer to the chapter "Configuring Dial-In Terminal Services" in the Cisco IOS Dial Services Configuration Guide: Terminal Services and the tn3270.examples file in the Cisco ftp@cisco.com directory for more examples.
ttycap ttycap1\ d0|vt100|vt100-am|vt100am|dec vt100:do=^J:co#80:li#24:\ cl=50^[[;H^[[2J:bs:am:cm=5^[[%i%d;%dH:nd=2^[[C:up=2^[[A:\ ce=3^[[K:so=2^[[7m:se=2^[[m:us=2^[[4m:ue=2^[[m:md=2^[[1m:\ me=2^[[m:ho=^[[H:xn:sc=^[7:rc=^[8:cs=^[[%i%d;%dr:
Related Commands
Specifies the keyboard map for a terminal connected to the line. terminal-type Specifies the type of terminal connected to a line.
Command
Description
To set up a network layer connection to a router, use the tunnel user EXEC command.
tunnel host
Syntax Description
host Name or IP address of a specific host on a network that can be reached by the router.
Command Modes
User EXEC
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
If you are a mobile user, it is often impractical to dial in to your "home" router from a remote site. The asynchronous mobility feature allows you to dial in to different routers elsewhere on the internetwork while experiencing the same server environment that you would if you were connecting directly to your home router.
This asynchronous host mobility is accomplished by packet tunneling, a technique by which raw data from the dial-in user is encapsulated and transported directly to the host site where your home router performs the actual protocol processing.
You enable asynchronous mobility by entering the tunnel command to set up a network layer connection to a specified host. From a router other than a Cisco router, however, you need to use the Telnet protocol.
After a connection is established, you receive an authentication dialog or prompt from your home router and can proceed as if you are connected directly to it. When communications are complete, the network connection can be closed and terminated from either end of the connection.
Examples
The following example establishes a network layer connection with an IBM host named mktg:
router> tunnel mktg
To set the terminal transmit speed (how fast the terminal sends information to the modem), use the txspeed command in line configuration mode.
txspeed bps
Syntax Description
bps Baud rate in bits per second (bps).
Defaults
9600 bps
Command Modes
Line configuration
Command History
10.0 This command was introduced.
Release
Modification
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 router. The Cisco IOS software will indicate if the speed you select is not supported.
Examples
The following example sets the transmit speed for line 5 to 2400 bps:
line 5 txspeed 2400
Related Commands
Sets the terminal receive speed (how fast the terminal receives information from the modem). Sets the flow control start character. terminal txspeed Sets the terminal transmit speed (how fast the terminal can send information) on the current line and session.
Command
Description
To enable virtual profiles by authentication, authorization, and accounting (AAA) configuration, use the virtual-profile aaa command in global configuration mode. Use the no form of this command to disable virtual profiles.
virtual-profile aaaSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
11.2F This command was introduced. 12.0(7)T This command was enhanced to allow virtual profiles to be downloaded from an AAA server using the HDLC, LAPB-TA, X.25, and Frame Relay encapsulations, in addition to the originally supported PPP encapsulation.
Release
Modification
Usage Guidelines
Effect of this command for any specific user depends on the router being configured for AAA and the AAA server being configured for that user's specific configuration information.
Examples
The following example configures virtual profiles by AAA configuration only:
virtual-profile aaa
Related Commands
aaa authentication Enables AAA authentication to determine if a user can access the privileged command level. Enables virtual profiles by virtual interface template.
Command
Description
To specify that a virtual profile be used to create a virtual access interface only if the inbound connection requires a virtual access interface, use the virtual-profile if-needed command in global configuration mode. Use the no form of this command to create virtual access interfaces for every inbound connection.
virtual-profile if-neededSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
12.0(5)T This command was introduced.
Release
Modification
Usage Guidelines
This command is intended to prevent the creating of virtual-access interfaces for inbound calls on physical interfaces that do not require virtual-access interfaces.
This command is compatible with local, RADIUS, and TACACS+ AAA.
Examples
The following example enables selective virtual-access interface creation:
virtual-profile if-needed
Related Commands
interface virtual-template Creates a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces. virtual-profile virtual-template Enables virtual profiles by virtual interface template. virtual-profile aaa Enables virtual profiles by AAA configuration.
Command
Description
To enable virtual profiles by virtual interface template, use the virtual-profile virtual-template command in global configuration mode.
virtual-profile virtual-template number
Syntax Description
number Number of the virtual template to apply, in the range 1 to 30.
Defaults
Disabled. No virtual template is defined, and no default virtual template number is used.
Command Modes
Global configuration
Command History
11.2F This command was introduced.
Release
Modification
Usage Guidelines
When virtual profiles are configured by virtual templates only, any interface-specific configuration information that is downloaded from the AAA server is ignored in configuring the virtual access interface for a user.
The interface virtual-template command defines a virtual template to be used for virtual profiles. Because several virtual templates might be defined for different purposes on the router (such as MLP, PPP over ATM, and virtual profiles), it is important to be clear about the virtual template number to use in each case.
Examples
The following example configures virtual profiles by virtual templates only. The number 2 was chosen because virtual template 1 was previously defined for use by Multilink PPP.
virtual-profile virtual-template 2
Related Commands
Creates a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces.
Command
Description
To specify which virtual template will be used to clone virtual access interfaces, use the virtual-template command in accept-dialin configuration mode. To remove the virtual template from an accept-dialin Virtual Private Dialup Network (VPDN) subgroup, use the no form of this command.
virtual-template template-number
Syntax Description
template-number Number of the virtual template that will be used to clone virtual-access interfaces.
Defaults
Disabled
Command Modes
Accept-dialin configuration
Command History
12.0(5)T This command was introduced.
Release
Modification
Usage Guidelines
Each accept-dialin group can only clone virtual-access interfaces using one virtual template. If you enter a second virtual-template command on an accept-dialin subgroup, it will replace the first virtual-template command.
You must first enable a tunneling protocol on the accept-dialin VPDN subgroup (using the protocol command) before you can enable the virtual-template command. Removing or modifying the protocol command will remove virtual-template command from the request-dialin subgroup.
Examples
The following example enables the LNS to accept an L2TP tunnel from a LAC named mugsy. A virtual-access interface will be cloned from virtual template 1:
vpdn-group 1 accept dialin protocol l2tp virtual-template 1 terminate-from hostname mugsy
Related Commands
Specifies the LNS to use for authenticating, and the virtual template to use for cloning, new virtual access interfaces when an incoming L2TP tunnel connection is requested from a specific peer.
Command
Description
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Fri Mar 17 16:06:59 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.