Table of Contents
Cisco IOS Dial Services Commands: TR Through VIR
This chapter explains the function and syntax of the Cisco IOS dial services commands from TR through VIR. For more information about defaults and usage guidelines, see the corresponding chapter of the Cisco IOS Dial Services Command Reference, Release 12.1.
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
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 17 lists all outgoing options and their corresponding interface configuration commands.
translate lat incoming-service-name [unadvertised] virtual-template number [global-options]
Syntax Description
Table 17: Mapping Outgoing translate lat Command Options to Interface Commands
| Translate Command Options
| Corresponding Interface Configuration Command
|
ip-pool
| peer default ip address {ip-address | dhcp | pool [poolname]}
|
header-compression
| ip tcp header compression [on | off | passive]
|
routing
| ip routing or ipx routing
|
mtu
| mtu
|
keepalive
| keepalive
|
authentication {chap | pap}
| ppp authentication {chap | pap}
|
ppp use-tacacs
| ppp use-tacacs
|
ipx loopback
| ipx ppp-client loopback number
|
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
incoming-address
| TCP/IP Telnet and a standard IP address or host name. The argument ip-address is a standard, four-part dotted decimal IP address or the name of an IP host that can be resolved by the Domain Name System (DNS) or explicit specification in an ip host command.
|
in-options
| (Optional) Incoming connection request options. These arguments can have the following values:
Telnet TCP translation options:
|
protocol outgoing-address
| Name of a protocol followed by a service name, IP address, or host name. The host name is translated to an IP address during configuration.
These arguments can have the following values:
- lat service-name---LAT and a LAT service name. You must learn the service name, through LAT service advertisements, before you can use it.
- x25 X.121-address---X.25 and an X.121 address. The X.121 address must conform to specifications provided in the CCITT 1984 Red Book. This number generally consists of a portion that is administered by the PDN and a portion that is locally assigned. You must be sure that the numbers that you assign agree with the addresses assigned to you by the X.25 service provider. The X.121 addresses will generally be subaddresses of the X.121 address for the X.25 network interface.
- slip ip-address---The argument ip-address is a standard, four-part dotted decimal IP address or the name of an IP host that can be resolved by the Domain Name System (DNS). The slip argument applies only to outgoing connections; SLIP is not supported on incoming protocol translation connections.
- ppp ip-address---The argument ip-address is a standard, four-part dotted decimal IP address or the name of an IP host that can be resolved by the Domain Name System (DNS). The ppp argument applies only to outgoing connections; PPP is not supported for incoming protocol translation connections.
- autocommand---Enables you to specify a string for an outgoing connection. The string executes upon connection to a host. If you want to enable ARA on an outgoing connection, you need to specify autocommand arap.
The autocommand option is necessary for ARA, because ARA does not use addressing, and autocommand permits you to invoke the arap string.
If the string following autocommand has one or more spaces as part of the string, you must place quotation marks (" ") around the string. For example, if you specify autocommand tn3270 abracadabra, you must enclose tn3270 abracadabra in quotes.
The autocommand option applies only to outgoing connections.
You can issue any EXEC command and any switch or host name as an argument to the autocommand option.
|
out-options
| (Optional) Outgoing connection request options. These arguments can have the following values:
LAT translation options:
- node node-name---Connects to the specified node (node-name) that offers a service. By default, the connection is made to the highest-rated node that offers the service.
- port port-name---Destination LAT port name (port-name) in the format of the remote system. This parameter is usually ignored in most timesharing systems, but is used by terminal servers that offer reverse-LAT services.
|
|
|
| X.25 translation options:
- cud c-u-data---Sends the specified Call User Data (CUD) text (c-u-data) as part of an outgoing call request after the protocol identification bytes.
- no-reverse---Specifies that outgoing calls are not to use reverse charging, when the interface default is that all outgoing calls are reverse charged.
- profile profile---Sets the X.3 PAD parameters as defined in the profile created by the x29 profile command.
- reverse---Provides reverse charging for X.25 on a per-call rather than a per-interface basis. Requests reverse charges on a specified X.121 address, even if the serial interface is not configured to request reverse charge calls. This is an outgoing option only.
SLIP and PPP translation options:
- ip-pool---Obtain an IP address from a DHCP proxy client or a local pool. If the scope-name option is not specified, the address is obtained from a DHCP proxy client. If the scope-name option is specified, the IP address is obtained from the specified local pool.
- scope-name---Specific local scope name from which to obtain an IP address. Can specify a range of IP addresses.
- header-compression [passive]---Implements header compression on IP packets only. The option passive for SLIP connections permits compression on outgoing packets only if incoming TCP packets on the same virtual asynchronous interface are compressed. The default (without the passive option) permits compression on all traffic.
- routing---Permits routing updates between connections. This option is required if the destination device is not on a subnet connected to one of the interfaces on the router.
- mtu bytes---Permits you to change the maximum transmission unit (MTU) of packets that the virtual asynchronous interface supports. The default MTU is 1500 bytes on a virtual asynchronous interface. The acceptable range is 64 through 1,000,000 bytes.
|
| More PPP translation options:
|
global-options
| (Optional) Translation options that can be used by any connection type. It can be one or more of the following:
- access-class number---Allows the incoming call to be used by source hosts that match the access list parameters. The argument number is the number (integer) previously assigned to an access list. The standard access list is 1-99.
- max-users number---Limits the number of simultaneous users of the translation to number (an integer you specify).
- local---Allows Telnet protocol negotiations to not be translated.
- rotor---Specifies a rotary among host-name addresses.
- login---Requires that the user log in before the outgoing connection is made. This type of login is specified on the VTY lines with the login command.
- quiet---Suppresses printing of user-information messages.
|
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
incoming-address
| TCP/IP Telnet and a standard IP address or host name. The argument ip-address is a standard, four-part dotted decimal IP address or the name of an IP host that can be resolved by the Domain Name System (DNS) or explicit specification in an ip host command.
|
in-options
| (Optional) Incoming connection request options. These arguments can have the following values:
|
virtual-template number
| Applies the virtual interface template specified by number in place of outgoing options.
|
global-options
| (Optional) Translation options that can be used by any connection type. It can be one or more of the following:
- access-class number---Allows the incoming call to be used by source hosts that match the access list parameters. The argument number is an integer value previously assigned to an access list. The standard access list range is from 1 to 99.
|
| - local---Allows Telnet protocol negotiations to not be translated.
- login---Requires that the user log in before the outgoing connection is made. This type of login is specified on the virtual terminal lines with the login command.
- max-users number---Maximum number of simultaneous users of the translation.
- quiet---Suppresses printing of user-information messages.
- rotor---Specifies a rotary among host-name addresses.
|
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
incoming-address
| X.25 and an X.121 address. The X.121 address must conform to specifications provided in the CCITT 1984 Red Book. This number generally consists of a portion that is administered by the PDN and a portion that is locally assigned. You must be sure that the numbers that you assign agree with the addresses assigned to you by the X.25 service provider. The X.121 addresses will generally be subaddresses of the X.121 address for the X.25 network interface. Typically, the interface address will be a 12-digit number. Any additional digits are interpreted as a subaddress. The PDN still routes these calls to the interface, and the Cisco IOS software itself is responsible for dealing with the extra digits appropriately. Do not use the same address on the interface and for translation.
|
in-options
| (Optional) Incoming connection request options. These arguments can have the following values:
- accept-reverse---Accepts reverse charged calls on an X.121 address even if the serial interface is not configured to accept reverse charged calls. This is an incoming option only.
- cud c-u-data---Sends the specified Call User Data (CUD) text (c-u-data) as part of an outgoing call request after the protocol identification bytes.
- idle minutes---Specifies the number of minutes the VC is idle. This option enables the protocol translation function to clear a switched virtual circuit (SVC) after a set period of inactivity, where minutes is the number of minutes in the period. Calls either originated or terminated are cleared. The maximum value of minutes is 255. The default value of minutes is zero.
- printer---Supports LAT and TCP printing over an X.25 network among multiple sites. Provides an "interlock mechanism" between the acceptance of an incoming X.25 connection and the opening of an outgoing LAT or TCP connection. The option causes the Cisco IOS software to delay the call confirmation of an incoming X.25 call request until the outgoing protocol connection (to TCP or LAT) has been successfully established. An unsuccessful outgoing connection attempt to the router results in the incoming X.25 connection being refused, rather than being confirmed and then cleared, which is the default behavior. Note that using this option will force the global option quiet to be applied to the translation.
- profile profile---Sets the X.3 PAD parameters as defined in the profile created by the x29 profile command.
|
protocol outgoing-address
| Name of a protocol followed by a service name, IP address, or host name. The host name is translated to an IP address during configuration, unless you use the TCP host-name option, which allows load balancing by dynamically resolving an IP address from a host name. These arguments can have the following values:
- lat service-name---LAT and a LAT service name. You must learn the service name, through LAT service advertisements, before you can use it.
- tcp ip-address---TCP/IP Telnet and a standard IP address or host name. The argument ip-address is a standard, four-part dotted decimal IP address or the name of an IP host that can be resolved by the Domain Name System (DNS) or explicit specification in an ip host command.
- slip ip-address---The argument ip-address is a standard, four-part dotted decimal IP address or the name of an IP host that can be resolved by the Domain Name System (DNS). The slip argument applies only to outgoing connections; SLIP is not supported on incoming protocol translation connections.
- ppp ip-address---The argument ip-address is a standard, four-part dotted decimal IP address or the name of an IP host that can be resolved by the Domain Name System (DNS). The ppp argument applies only to outgoing connections; PPP is not supported for incoming protocol translation connections.
- autocommand---Enables you to specify a string for an outgoing connection. The string executes upon connection to a host. If you want to enable ARA on an outgoing connection, you need to specify the autocommand arap string.
The autocommand option is necessary for ARA, because ARA does not use addressing, and autocommand permits you to invoke the arap string.
If the string following autocommand has one or more spaces as part of the string, you must place quotation marks (" ") around the string. For example, if you specify autocommand tn3270 abracadabra, you must enclose the tn3270 abracadabra string in quotes.
The autocommand option applies only to outgoing connections.
You can issue any EXEC command and any switch or host name as an argument to the autocommand option.
|
out-options
| (Optional) Outgoing connection request options. These arguments can have the following values:
- use-map---Applies x25 map pad command entry options (such as CUD and idle) and facilities (such as packet in, packet out, win in, and win out) to the outgoing protocol translation call. This application occurs when the protocol translation function searches the X.25 map PAD entries and finds a matching X.121 destination address. The X.25 map facilities applied to the outgoing translation can be viewed with the show translation command throughout the duration of the translation session.
LAT translation options:
- node node-name---Connects to the specified node (node-name) that offers a service. By default, the connection is made to the highest-rated node that offers the service.
- port port-name---Destination LAT port name (port-name) in the format of the remote system. This parameter is usually ignored in most timesharing systems but is used by terminal servers that offer reverse-LAT services.
Telnet TCP translation options:
- port number---For incoming connections, number of the port to match. The default is port 23 (any port). For outgoing connections, number of the port to use. The default is port 23 (Telnet).
SLIP and PPP translation options:
- ip-pool---Obtain an IP address from a DHCP proxy client or a local pool. If the scope-name option is not specified, the address is obtained from a DHCP proxy client. If the scope-name option is specified, the IP address is obtained from the specified local pool.
- scope-name---Specific local scope name from which to obtain an IP aheader-compression [passive]---Implements header compression on IP packets only. The option passive for SLIP connections permits compression on outgoing packets only if incoming TCP packets on the same virtual asynchronous interface are compressed. The default (without the passive option) permits compression on all traffic.
- ddress. This option can specify a range of IP addresses.
- routing---Permits routing updates between connections. This option is required if the destination device is not on a subnet connected to one of the interfaces on the router.
- mtu bytes---Permits you to change the maximum transmission unit (MTU) of packets that the virtual asynchronous interface supports. The default MTU is 1500 bytes on a virtual asynchronous interface. The acceptable range is 64 to 1,000,000 bytes.
|
| PPP translation options:
|
global-options
| (Optional) Translation options that can be used by any connection type. It can be one or more of the following:
- access-class number---Allows the incoming call to be used by source hosts that match the access list parameters. The argument number is the number (integer) previously assigned to an access list. The standard access list is 1 to 99.
- max-users number---Limits the number of simultaneous users of the translation to number (an integer you specify).
- local---Prevents Telnet protocol negotiations to from being translated.
- login---Requires that the user log in before the outgoing connection is made. This type of login is specified on the virtual terminal lines with the login command.
- rotor---Specifies a rotary among host-name addresses.
- quiet---Suppresses printing of user-information messages.
|
|
|
| - pvc number {[interface serial number] [packetsize in-size out-size] [windowsize in-size out-size]}---Specifies that the incoming or outgoing connection is actually a permanent virtual circuit (PVC). Only one session is allowed per PVC, where:
number---Specifies the virtual-circuit channel number of the incoming connection, which must be less than the virtual circuits assigned to the switched virtual circuits (SVC).
interface serial number---Specifies a PVC interface on which to set up the PVC connection.
packetsize in-size out-size---Specifies the input packet size (in-size) and output packet size (out-size) for the PVC. Following are valid packet size values:
16, 32, 64, 128, 256, 512 1024, 2048, or 4096
windowsize in-size out-size---Specifies the packet count for input windows (in-size) and output windows (out-size) for the outgoing translation. Values of in-size and out-size range 1 to 127 and must not be greater than the value set for the x25 modulo command. You must specify the same value for in-size and out-size.
|
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 18 lists all outgoing options and their corresponding interface configuration commands.
x25 incoming-address [in-options] virtual-template number [global-options]
Syntax Description
Table 18: Mapping Outgoing translate x25 Command Options to Interface Commands
| Translate Command Options
| Corresponding Interface Configuration Command
|
ip-pool
| peer default ip address {ip-address | dhcp | pool [poolname]}
|
header-compression
| ip tcp header compression [on | off | passive]
|
routing
| ip routing or ipx routing
|
mtu
| mtu
|
keepalive
| keepalive
|
authentication {chap | pap}
| ppp authentication {chap | pap}
|
ppp use-tacacs
| ppp use-tacacs
|
ipx loopback
| ipx ppp-client loopback number
|
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.
|
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.
|
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.
|
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
no ttycap ttycap-name
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.
|
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.
|
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).
|
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 aaa
no virtual-profile aaa
Syntax Description
This command has no arguments or keywords.
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-needed
no virtual-profile if-needed
Syntax Description
This command has no arguments or keywords.
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.
|
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
no virtual-template
Syntax Description
template-number
| Number of the virtual template that will be used to clone virtual-access interfaces.
|







Posted: Wed Jul 26 12:01:47 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.