Table Of Contents
terminal lat remote-modification
skip (ruleset)
To identify a connection to ignore by the translation ruleset, use the skip command in translate ruleset configuration mode. To remove the test operation, use one of the two no forms of this command.
skip [line-number] incoming-connection-parameter regular-expression [line-number incoming-connection-parameter regular-expression [...]]
no skip incoming-connection-parameter regular-expression [incoming-connection-parameter regular-expression [...]]
no skip line-number
Syntax Description
line-number
(Optional) The line in the translation ruleset to test for a skip operation.
incoming-connection-parameter
Incoming protocol parameter to test for; up to six skip tests can be written on one command line. Parameters are available for packet assembler/disassembler (PAD) and Telnet connections, and are listed in Table 39 and Table 40.
regular-expression
Pattern with regular expression to test for ignoring.
Defaults
No default behavior or values
Command Modes
Translate ruleset configuration
Command History
Usage Guidelines
Up to six skip tests can be written on one command line. The ellipses in the format shown above means multiple skip tests can be written in a translation ruleset statement.
For incoming connection attempts, a template is configured, and within the template a connection can be identified by tests written using Cisco regular expressions and a pattern that is ignored (skipped).
The translation ruleset templates have line numbers that can be displayed using the show translate ruleset EXEC command.
Cisco regular expressions are described in Appendix A, "Regular Expressions," in the Cisco IOS Terminal Services Configuration Guide.
Table 39 and Table 40 list the protocol parameter keywords and arguments that can be specified in the skip statements for incoming PAD and Telnet connections.
Examples
The following example shows how to write match and skip tests to skip connection attempts from any subnetwork address starting with 10 or 11 and match only those with a specific IP address and destination port number:
translate ruleset customer-case-1 from telnet to pad! Ignore an incoming Telnet attempt from any subnetwork address starting with 10skip source-addr ^10\.*! Match an incoming Telnet attempt destined for an IP addresses starting! with 172.18., and a 5-digit port starting with 10 or 11match dest-addr ^172\.18\..* dest-port ^1[0-1]...$! Or match an incoming Telnet attempt destined an IP addresses starting! with 172.18., and a 5-digit port starting with 120 through 127match dest-addr ^172\.18\..* dest-port ^12[0-7]..$The following example shows how to write match and skip tests to skip connection attempts from destination 55554 and to match only those with destination addresses from 55550 to 55553 and from 55556 to 55559:
translate ruleset A from pad to telnetskip dest-addr ^55554$match dest-addr ^5555.$Related Commands
slip
To start a serial connection to a remote host by using Serial Line Internet Protocol (SLIP), use the slip command in EXEC mode.
slip [/default] {remote-ip-address | remote-name} [@tacacs-server] [/routing]} [/compressed]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
When you connect from a remote node computer to the EXEC facility on a router and want to connect from the router to a device on the network, issue the slip command.
If you specify an address for the TACACS server by using /default or tacacs-server arguments, the address must be the first parameter in the command after you enter slip. If you do not specify an address or enter /default, you are prompted for an IP address or host name. You can enter the /default keyword at this point.
If you do not use the tacacs-server argument to specify a TACACS server for SLIP address authentication, the TACACS server specified at login (if any) is used for the SLIP address query.
To optimize bandwidth on a line, SLIP enables compression of the SLIP packets using Van Jacobson TCP header compression as defined in RFC 1144.
Your system administrator must configure the system with the ip tcp header-compression passive command for the /compressed command option to be valid in EXEC mode. The ip tcp header-compression command forces header compression on or off. The default is to not compress the packets. The configuration file must have header compression on and the slip /compressed EXEC command must be entered for header compression to occur.
To terminate a session initiated with the slip command, disconnect from the device on the network using the command specific to that device. Then, exit from EXEC mode by using the exit command.
Examples
The following example makes a connection when a default IP address is assigned. Once a correct password is entered, you are placed in SLIP mode, and the IP address is displayed.
Router> slipPassword:Entering SLIP mode.Your IP address is 192.168.7.28, MTU is 1524 bytesThe following example illustrates the prompts displayed and the response required when you use dynamic addressing to assign the SLIP address:
Router> slipIP address or hostname? 192.168.6.15Password:Entering SLIP modeYour IP address is 192.168.6.15, MTU is 1524 bytesIn the preceding example, the address 172.31.6.15 has been assigned as the default. Password verification is still required before SLIP mode can be enabled.
Router> slip /defaultPassword:Entering SLIP modeYour IP address is 192.168.6.15, MTU is 1524 bytesThe following example illustrates the implementation of header compression on the interface with the IP address 172.24.2.1:
Router> slip 172.24.2.1 /compressedPassword:Entering SLIP mode.Interface IP address is 172.24.2.1, MTU is 1500 bytes.Header compression will match your system.In the preceding example, the interface is configured for the ip tcp header-compression passive command, which permits the user to enter the /compressed keyword at the EXEC mode prompt. The message "Header compression will match your system" indicates that the user specified compression. If the line was configured for the ip tcp header-compression on command, this line would read "Header compression is On."
The following example specifies a TACACS server named server1 for address authentication:
Router> slip 10.0.0.1@server1Password:Entering SLIP mode.Interface IP address is 10.0.0.1, MTU is 1500 bytesHeader compression will match your system.Related Commands
substitute (ruleset)
To match an available protocol and substitute another in a translation ruleset, use the substitute command in translate ruleset configuration mode. To change or remove the substitution statement, use one of the no forms of this command.
substitute [line-number] {pad | telnet} variable-parameter reg-exp-match into {pad | telnet} variable-parameter [reg-exp-write]
no substitute {pad | telnet} variable-parameter reg-exp-match into {pad | telnet} variable-parameter [reg-exp-write]
no substitute line-number ...
Syntax Description
line-number
(Optional) The line in the translation ruleset to test for substitution.
{pad | telnet}
Identifies the incoming or outgoing protocol and controls which parameters are available in the next element of this command.
variable-parameter
A parameter that varies depending upon the protocol selected, either pad or telnet, and its role, either incoming or outgoing. Protocol parameters that modify the incoming or outgoing connection behavior during protocol translation session setup are indicated in Table 41 with an X.
reg-exp-match
A standard Cisco regular expression match specification.
into
Makes the substitution into an available protocol parameter.
reg-exp-write
(Optional) A standard Cisco regular expression write specification that uses information from a match specification.
Defaults
No default behavior or values
Command Modes
Translate ruleset configuration
Command History
Usage Guidelines
Up to six substitute specifications can be entered on one command line. The ellipses in the format shown above means multiple substitute statements can be specified in a translation ruleset statement.
When you use the first no form of this command, specify the full set of parameters and expressions in the command to be removed. The second no form must specify the correct substitute command and line number within the translation ruleset template.
This command is used to substitute between protocol parameters using regular expressions to match elements with a test string, and to substitute parameters into another string that can take elements from the matched string.
A substitute ... into statement will perform a regular expression match on any available protocol parameter and, if matched, substitute into any available protocol parameter. The regular expression write specification is optional. If the specification is omitted, the current value of the parameter will be taken as the regular expression write specification. This latter provision is a way of using multiple parameter values to set another parameter value. As an example, two successive substitute statements from a Telnet destination address and destination port into a packet assembler/disassembler (PAD) destination address could be specified using the following statements:
substitute telnet dest-addr ^10\.0\.0\.(.)$ into pad dest-addr 111100\1\\1
substitute telnet dest-addr ^10\.0\.0\.(..)$ into pad dest-addr 111100\1\\1
substitute telnet dest-port ^10(...)$ into pad dest-addr
If these successive substitutions were performed using an incoming Telnet connection from IP address 10.0.0.9/10234, the PAD destination address after the first substitution would be 111009\1, and after the second substitution would be 1111009234.
The following statements construct a switched virtual circuit (SVC) source address from the Telnet source information, starting with the source IP address in the form 172.18.#.##, which allows for a subsequent substitution of one field (notice the use of the backslash to concatenate the substitute and into statements):
substitute telnet source-addr ^172\.18\.(.)\.(..) \
into pad source-addr 98\1\2\\1
You can add in elements extracted from the Telnet destination port, where the rewrite pattern is taken from the current value of PAD source address, as follows:
substitute telnet dest-port ^.(...). into pad source-addr
Table 41 lists the PAD and Telnet parameters that can be set, as indicated by an X.
Examples
The following example shows how to build a translation ruleset template by starting with a match connection test, specifying protocol translation options, and setting specific parameters for incoming Telnet connections. The translation ruleset goes on to test and set appropriate parameters for incoming PAD connections, and to construct an SVC source address from Telnet information starting with the source IP address expressed using regular expression characters that allow for subsequent substitution in its last two fields. The translation ruleset is completed by adding in elements extracted from the Telnet destination port; the rewrite pattern is taken from the current value of PAD source address. Note use of the backslash character to construct the test ... set and substitute ... into statements.
translate ruleset customer-case-1 from telnet to pad! Match an incoming Telnet attempt destined for IP addresses starting! with 172.18., and a 5-digit port starting with the numbers 120 through 127.match dest-addr ^172\.18\..* dest-port ^12[0-7]..$! Once the correct network is matched, specify that this ruleset is limited! to ten concurrent users and requires a login exchange.options max-users 10 login! Set Telnet options:set telnet printer Y telnet binary Y! Set PAD options:set pad profile cust-profile-one! Test conditional parameters and make appropriate settings:test telnet dest-addr ^172\.18\.0\.* telnet dest-port ^10.00 \set pad pvc 1 telnet binary T! Construct an SVC source address from the Telnet source information;! start with the source IP address in the form 172.18.#.##, allowing! for substitutions in the last two fields:substitute telnet source-addr ^172\.18\.(.)\.(..) \into pad source-addr 98\1\2\\1! Now add in an extract from the Telnet destination port,! where the rewrite pattern is taken from the current value of the PAD! source address:substitute telnet dest-port ^.(...). into pad source-addrRelated Commands
telnet
To log in to a host that supports Telnet, use the telnet command in EXEC mode.
telnet host [port] [keyword]
Syntax Description
host
A host name or an IP address.
port
(Optional) A decimal TCP port number; the default is the Telnet router port (decimal 23) on the host.
keyword
(Optional) One of the keywords listed in Table 42.
Command Modes
EXEC
Command History
Usage Guidelines
Table 42 lists the optional telnet command keywords.
With the Cisco IOS implementation of TCP/IP, you are not required to enter the connect or telnet commands to establish a terminal connection. You can enter only the learned host name—as long as the following conditions are met:
•
The host name is different from a command word for the router.
•
To display a list of the available hosts, use the show hosts command. To display the status of all TCP connections, use the show tcp command.
The Cisco IOS software assigns a logical name to each connection, and several commands use these names to identify connections. The logical name is the same as the host name, unless that name is already in use, or you change the connection name with the name-connection EXEC command. If the name is already in use, the Cisco IOS software assigns a null name to the connection.
The Telnet software supports special Telnet commands in the form of Telnet sequences that map generic terminal control functions to operating system-specific functions. To issue a special Telnet command, enter the escape sequence and then a command character. The default escape sequence is Ctrl-^ (press and hold the Ctrl-Shift-6). You can enter the command character as you hold down Ctrl or with Ctrl released; you can use either uppercase or lowercase letters. Table 43 lists the special Telnet escape sequences.
Table 43 Special Telnet Escape Sequences
Ctrl-^ b
Break
Ctrl-^ c
Interrupt Process (IP)
Ctrl-^ h
Erase Character (EC)
Ctrl-^ o
Abort Output (AO)
Ctrl-^ t
Are You There? (AYT)
Ctrl-^ u
Erase Line (EL)
1 The caret (^) symbol refers to Shift-6 on your keyboard.
At any time during an active Telnet session, you can list the Telnet commands by pressing the escape sequence keys followed by a question mark at the system prompt:
Ctrl-^ ?A sample of this list follows.
In this sample output, the first caret (^) symbol represents the Ctrl key, and the second caret represents Shift-6 on your keyboard:
Router> ^^?[Special telnet escape help]^^B sends telnet BREAK^^C sends telnet IP^^H sends telnet EC^^O sends telnet AO^^T sends telnet AYT^^U sends telnet ELYou can have several concurrent Telnet sessions open and switch between them. To open a subsequent session, first suspend the current connection by pressing the escape sequence (Ctrl-Shift-6 then x [Ctrl^x] by default) to return to the system command prompt. Then open a new connection with the telnet command.
To terminate an active Telnet session, enter any of the following commands at the prompt of the device to which you are connecting:
•
•
•
•
•
Examples
The following example establishes an encrypted Telnet session from a router to a remote host named host1:
Router> telnet host1 /encrypt kerberosThe following example routes packets from the source system host1 to kl.sri.com, then to 10.1.0.11, and finally back to host1:
Router> telnet host1 /route:kl.sri.com 10.1.0.11 host1The following example connects to a host with logical name host1:
Router> host1The following example suppresses all onscreen messages from the Cisco IOS software during login and logout:
Router> telnet host2 /quietThe following example shows the limited number of messages displayed when connection is done using the optional /quiet keyword:
login:User2Password:Welcome to OpenVMS VAX version V6.1 on node CRAWLast interactive login on Tuesday, 15-DEC-1998 11:01Last non-interactive login on Sunday, 3-JAN-1999 22:32Server3)logoutUser2 logged out at 16-FEB-2000 09:38:27.85Related Commands
telnet break-on-ip
To cause the system to generate a hardware BREAK signal on the EIA/TIA-232 line that is associated with a reverse Telnet connection when a Telnet Interrupt-Process command is received on that connection, use the telnet break-on-ip command in line configuration mode.
telnet break-on-ip
Syntax Description
This command has no arguments or keywords.
Defaults
No hardware BREAK signal is generated when an Interrupt-Process command is received.
Command Modes
Line configuration
Command History
Usage Guidelines
This command causes the system to generate a hardware BREAK signal on the EIA/TIA-232 line that is associated with a reverse Telnet connection. It is useful when a Telnet Interrupt-Process command is received on that connection because it can control the translation of Telnet Interrupt-Process commands into X.25 BREAK indications. It is also a useful workaround in the following situations:
•
•
•
A hardware BREAK signal is generated when a Telnet BREAK command is received.
Examples
In the following example, line 5 is configured with the telnet break-on-ip command. The location text notes that this line is the location of the high-speed modem. The telnet transparent command sets end-of-line handling.
line 5location high-speed modemtelnet transparenttelnet break-on-ipRelated Commands
telnet refuse-negotiations
To set a line using Telnet to refuse to negotiate full-duplex, remote echo requests on incoming connections, use the telnet refuse-negotiations command in line configuration mode. To disable this function, use the no form of this command.
telnet refuse-negotiations
no telnet refuse-negotiations
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Line configuration
Command History
Usage Guidelines
Use this command on reverse Telnet connections to allow the Cisco IOS software to refuse full-duplex, remote echo option connection requests from the other end. This command suppresses negotiation of the Telnet Remote Echo and Suppress Go Ahead options.
This command does not apply to protocol translation configurations. It is intended for applications in which the router is functioning as a terminal server to allow terminal connections to remote devices through the asynchronous terminal ports of the router. Terminal server connections are those where the user types a command similar to the following to access network resources:
telnet access-server 2005
where access-server is the host name of the Cisco router functioning as a terminal server, and 2005 is the port number on the router to which the remote terminal is connected.
Examples
The following example shows how to set line 5 to refuse full-duplex, remote echo requests:
line 5telnet refuse-negotiationsRelated Commands
telnet speed
To allow negotiation of the transmission speed of the line to a connected device, use the telnet speed command in line configuration mode. To disable this function, use the no form of this command.
telnet speed default-speed maximum-speed
no telnet speed
Syntax Description
Defaults
No default behavior or values.
Command Modes
Line configuration
Command History
Usage Guidelines
Negotiates speeds on reverse Telnet lines. You can match line speeds on remote systems in reverse Telnet, on host machines hooked up to a router used to access the network, or on a group of console lines hooked up to the router, when disparate line speeds are in use at the local and remote ends of the connection. Line speed negotiation adheres to the Remote Flow Control option defined in RFC 1080.
Examples
The following example allows a router to negotiate a bit rate on the line using the Telnet option. If no speed is negotiated, the line will run at 2400 bits per second (bps). If the remote host requests a speed of greater than 9600 bps, then 9600 will be used.
line 5telnet speed 2400 9600Related Commands
telnet sync-on-break
To configure the Cisco IOS software to cause an incoming connection to send a Telnet Synchronize signal when it receives a Telnet BREAK signal, use the telnet sync-on-break command in line configuration mode. To disable this function, use the no form of this command.
telnet sync-on-break
no telnet sync-on-break
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Line configuration
Command History
Usage Guidelines
This command causes a reverse Telnet line to send a Telnet Synchronize signal when it receives a Telnet BREAK signal. This option is used very rarely to ensure the ordering of BREAK reception with respect to data characters sent after the BREAK.
Examples
The following example configures the AUX line with the telnet sync-on-break command:
line aux 0telnet sync-on-breakRelated Commands
telnet transparent
To configure the Cisco IOS software to send a CARRIAGE RETURN (CR) as a CR followed by a NULL instead of a CR followed by a LINE FEED (LF), use the telnet transparent command in line configuration mode. To return to the default setting, use the no form of this command.
telnet transparent
no telnet transparent
Syntax Description
This command has no arguments or keywords.
Defaults
CARRIAGE RETURN followed by a LINE FEED.
Command Modes
Line configuration
Command History
Usage Guidelines
This command is useful for coping with different interpretations of end-of-line handling in the Telnet protocol specification.
Examples
The following example causes the Cisco IOS software, when sending a CR, to send a CR followed by a NULL character:
line 7telnet transparentRelated Commands
terminal lat out-group
To temporarily define the list of services to which you or another user can connect, use the terminal lat out-group command in EXEC mode.
terminal lat out-group group-number [start-end] {disabled | enabled}
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
To temporarily define the list of services to which you or another user can connect, you define the group code lists used for connections from specific lines. You limit the connection choices for an individual line by defining the group code lists for an outgoing connection. When a user initiates a connection with a local-area transport (LAT) host, the line must share a common group number with the remote LAT host before a connection can be made.
The group code range entered in this command must fall within the group code range already configured for the line.
Examples
The following example defines a group code list for the outgoing group 4:
terminal lat out-group 4, 6-189Related Commands
connect
Logs in to a host that supports Telnet, rlogin, or LAT.
l2f ignore-mid-sequence
Specifies a connection to a particular LAT node that offers LAT services.
terminal lat remote-modification
To set a line running local-area transport (LAT) to be remotely modifiable, use the terminal lat remote-modification command in EXEC mode.
terminal lat remote-modification
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following example sets line 6 to be remotely modifiable:
terminal lat remote-modification 6Related Commands
connect
Logs in to a host that supports Telnet, rlogin, or LAT.
l2f ignore-mid-sequence
Specifies a connection to a particular LAT node that offers LAT services.
terminal transport preferred
To specify the preferred protocol to use for the current session when a command does not specify one, use the terminal transport preferred command in EXEC mode.
terminal transport preferred {all | lat | mop | nasi | none | pad | rlogin | telnet | v120}
Syntax Description
Defaults
lat (if LAT is not supported, telnet)
Command Modes
EXEC
Command History
10.0
This command first appeared in a release prior to Cisco IOS Release 10.0.
11.2
The following keywords were added:
•
•
•
•
•
•
•
•
Examples
The following example configures the console so that it does not connect when an unrecognized command is entered:
terminal transport preferred noneRelated Commands
transport preferred
Specifies the transport protocol that the Cisco IOS software uses if the user does not specify one when initiating a connection.
test (ruleset)
To test parameter values in a translation ruleset using regular expressions, use the test command in translate ruleset configuration mode. To change or remove the specification, use one of the two no forms of this command.
test [line-number] {pad | telnet} variable-parameter reg-exp-match [{pad | telnet} variable-parameter reg-exp-match [...]] set {pad | telnet} variable-parameter
no test {pad | telnet} variable-parameter reg-exp-match [{pad | telnet} variable-parameter reg-exp-match [...]] set {pad | telnet} variable-parameter
no test line-number ...
Syntax Description
line-number
(Optional) The line in the translation ruleset to test for substitution.
{pad | telnet}
Identifies the incoming or outgoing protocol and controls which parameters are available in the next element of this command.
variable-parameter
A parameter that varies depending upon the protocol selected, either pad or telnet, and its role, either incoming or outgoing. Protocol parameters are available to modify the incoming or outgoing connection behavior during protocol translation session setup. Up to six parameters can be entered on one command line. Table 44 indicates supported incoming and outgoing PAD and Telnet connection parameter keywords for the test command with an X.
reg-exp-match
A standard Cisco regular expression match specification.
set
Conditionally sets the specified protocol parameters to a fixed value.
Defaults
No default behavior or values
Command Modes
Translate ruleset configuration
Command History
Usage Guidelines
Up to six test statements can be entered on one command line. The ellipses in the format shown above means multiple test statements can be specified in a translation ruleset template.
The test command is useful for working with conditional parameters.
A test ... set ... statement conditionally sets one or more connection parameters to a given value, but only after a successful comparison of one or more connection parameters against a regular expression.
When you use the first no form of this command, specify the full set of parameters and expressions in the command to be removed. The second no form must specify the correct test command and line number within the translation ruleset template.
Examples
The following example shows how to integrate a test into a translation ruleset template. The translation ruleset begins with the required match connection test, specifies protocol translation options, and sets specific parameters for incoming Telnet connections. The translation ruleset goes on to test and set appropriate parameters for incoming PAD connections, and to construct an SVC source address from Telnet information, starting with the source IP address. The translation ruleset is completed by adding in elements extracted from the Telnet destination port; the rewrite pattern is taken from the current value of PAD source address. The backslash character is used to construct the test ... set and substitute ... into statements.
translate ruleset customer-case-1 from telnet to pad! Match an incoming Telnet attempt destined for IP addresses starting! with 172.18., and a 5-digit port starting with the numbers 120 through 127.match dest-addr ^172\.18\..* dest-port ^12[0-7]..$! Once the correct network is matched, specify that this ruleset is limited! to ten concurrent users and requires a login exchange.options max-users 10 login! Set Telnet options:set telnet printer Y telnet binary Y! Set PAD options:set pad profile cust-profile-one! Test conditional parameters and make appropriate settings:test telnet dest-addr ^172\.18\.0\.* telnet dest-port ^10.00 \set pad pvc 1 telnet binary T! Construct an SVC source address from the Telnet source information;! start with the source IP address in the form 172.18.#.##, allowing! for a following substitute of one field:substitute telnet source-addr ^172\.18\.(.)\.(..) \into pad source-addr 98\1\2\\1! Now add in an extract from the Telnet destination port,! where the rewrite pattern is taken from the current value of the PAD! source address:substitute telnet dest-port ^.(...). into pad source-addrRelated Commands
test translate
To display a trace of protocol translation behavior for a connection attempt, use the test translate command in user or privileged EXEC mode.
test translate {pad | telnet | parameter parameter} [detail]
Syntax Description
Defaults
No default behavior or values
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command will traverse the set of protocol translation configurations in the order they are listed in the translation ruleset, and report all events that take place. The detail keyword shows each line being evaluated and detailed translation test information.
The translation ruleset operations to test, set, and substitute protocol parameter values use strings, and the ruleset generates the set of protocol parameter values as a set of strings. When entered with the optional parameter keyword and parameter type, the test translate command becomes interactive and queries for incoming connection parameter values. For a given protocol parameter there may be additional validation tests that apply. If the application of a translation ruleset results in an invalid value for a parameter (whether a violation of the basic type rule or the more specific validation tests for the parameter), the protocol translation operation will fail with an informative message.
Configuration errors are not detected when translation ruleset commands are entered. They are tested when the connection is attempted or when you use the test (ruleset) command. In the following example, the set translation ruleset command unconditionally sets the PAD's profile name to a profile that does not exist in the configuration:
set pad profile Bldg-1-5ess
This command would be accepted at the command-line interpreter, but not tested until a connection attempt or with the test translate EXEC command. When the error is detected, the following messages display:
*%PT-3-PARAMRESULTERR: PT ruleset test protocol pad parameter profile parse error: Bldg-1-5ess.
-Process= "PAD InCall", ipl= 3, pid= 94
*PAD: ruleset translation not generated Cause: 9 Diag: 0
Examples
The following example shows a sample of the self-explanatory report from the test translate command:
Router# test translate paddest-addr (X.121 address): 55555Ruleset A match/skip line 1 compared: matchRuleset A; pad parameter read:pad/dest-addr: 55555Parameters set:telnet/dest-addr: 10.2.2.1Translate From: PAD 55555To: Telnet 10.2.2.1 Port 23Ruleset A0/1 users activeThe following is a sample of a detailed report:
Router# test translate pad detailPAD translate command 1 PVC match not requireddest-addr (X.121 address): 55555Normalized PAD dest-addr: 55555PAD translate command 1 skipped, destination address 55555 doesn't match 12345PAD translate command 2 PVC match not requiredPAD translate command 2 skipped, destination address 55555 doesn't match 55551No PAD translate command matched(Testing translate command A ...)Ruleset A match/skip line 1 compared: match(processing set/test/substitute line 1)(set/test/subst line 1, item 1, parameter dest-addr set to 10.2.2.1)(parsed telnet parameter dest-addr: 10.2.2.1)Ruleset A; pad parameter read:pad/dest-addr: 55555Parameters set:telnet/dest-addr: 10.2.2.1(translation requires 0 bytes variable-sized memory)Translate From: PAD 55555To: Telnet 10.2.2.1 Port 23Ruleset A0/1 users activeThe following example tests the boolean translate ruleset parameter in interactive mode:
Router# test translate parameter booleanEnter parameter value (boolean): YEnter encode buffer size (integer): 10Encoded into YRouter#Related Commands
tn3270
To begin a TN3270 session, use the tn3270 command in EXEC mode.
tn3270 host
Syntax Description
host
Name or IP address of a specific host on a network that can be reached by the router. The default terminal emulation mode allows access using a VT100 emulation.
Command Modes
EXEC
Command History
Usage Guidelines
Unlike Telnet and local-area transport (LAT) connections, you must enter the tn3270 command to make a connection to an IBM TN3278 host.
To terminate an active TN3270 session, enter the escape sequence (Ctrl-Shift-6 then x [Ctrl^x] by default) and enter the disconnect command at the EXEC prompt. Or log off the remote system by issuing the command specific to that system (such as exit, logout, quit, close, or disconnect).
Examples
The following example establishes a terminal session with an IBM TN3270 host named finance:
tn3270 financetn3270 8bit display
To configure the Cisco IOS software to use the mask set by the data-character-bits {7 | 8} command in line configuration mode or the terminal data-character bits {7 | 8} EXEC command, use the tn3270 8bit display command in line configuration mode. To restore the default 7-bit mask used for TN3270 connections, use the no form of this command.
tn3270 8bit display
no tn3270 8bit display
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Line configuration
Command History
Usage Guidelines
Use the tn3270-character-map command to map between extended EBCDIC or extended ASCII characters.
Examples
The following example configures the Cisco IOS software to use the mask set by the data-character-bits line configuration and EXEC commands on line 5:
line 5tn3270 8bit displayRelated Commands
tn3270 8bit transparent-mode
To configure the Cisco IOS software to use the mask set by the data-character-bits {7 | 8} command in line configuration mode or the terminal data-character bits {7 | 8} EXEC command, use the tn3270 8bit transparent-mode command in line configuration mode. To restore the default 7-bit mask used for TN3270 connections, use the no form of this command.
tn3270 8bit transparent-mode
no tn3270 8bit transparent-mode
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Line configuration
Command History
Usage Guidelines
This command is needed if you are using a file transfer protocol such as Kermit in 8-bit mode or you are using 8-bit graphics, both of which rely on transparent mode.
Examples
The following example configures the software to use the mask set by the data-character-bits line configuration and EXEC commands on line 5:
line 5tn3270 8bit transparent-modeRelated Commands
tn3270 character-map
To convert incoming EBCDIC characters into ASCII characters, use the tn3270 character-map command in global configuration mode. To restore default character mappings, use the no form of this command.
tn3270 character-map ebcdic-in-hex ascii-in-hex
no tn3270 character-map {all | ebcdic-in-hex} [ascii-in-hex]
Syntax Description
ebcdic-in-hex
Hexadecimal value of an EBCDIC character.
ascii-in-hex
Hexadecimal value of an ASCII character.
all
Indicates all character mappings.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to print international characters that are EBCDIC characters not normally printed, including umlauts (ยจ) and tildes (~). The command first restores default mapping for both EBCDIC and ASCII characters. In the no form of the command, the all keyword resets all character mappings to Cisco defaults.
Table 45 shows the default character mappings between ASCII and EBCDIC in decimal and hexadecimal format.
To convert outgoing ASCII characters into EBCDIC characters, use the keymap command to modify the keymap structure with the tag ebcdic_xx=string, where xx is a hexadecimal value and string is the sequence of characters that send the EBCDIC character.
Examples
The following example creates a two-way binding between an EBCDIC character and an ASCII character:
tn3270 character-map 0x81 0x78Related Commands
show tn3270 ascii-hexval
Displays ASCII-hexadecimal character mappings.
show tn3270 character-map
Displays character mappings between ASCII and EBCDIC.
tn3270 datastream
To enable the TN3270 extended datastream, use the tn3270 datastream command in global configuration mode. To return to the normal TN3270 datastream, use the no form of this command.
tn3270 datastream {extended | normal}
no tn3270 datastream
Syntax Description
Defaults
Normal datastream
Command Modes
Global configuration
Command History
Usage Guidelines
This command causes an "-E" to be appended to the terminal type string sent to the IBM host, which allows you to use the extended TN3270 features.
Examples
The following example shows the supported TN3270 datastream options:
tn3270 datastream ?extended Use extended TN3270 datastreamnormal Use normal TN3270 datastreamtn3270 null-processing
To specify how NULL signals are handled, use the tn3270 null-processing command in global configuration mode. To return to 7171 NULL processing, use the no form of this command.
tn3270 null-processing [3270 | 7171]
no tn3270 null-processing [3270 | 7171]
Syntax Description
3270
(Optional) NULLs are compressed out of the string, as on a 3278-x terminal.
7171
(Optional) NULLs are converted to spaces, as on a 7171 controller.
Defaults
7171 NULL processing
Command Modes
Global configuration
Command History
Usage Guidelines
If a user enters data, uses an arrow key to move the cursor to the right on the screen, and then enters more data, the intervening spaces are filled with NULLs. To specify how NULLs are handled, enter the tn3270 null-processing command either with the 3270 argument, where NULLs are compressed out of the string (as on a real 3278-x terminal) or the 7171 argument, where NULLs are converted to spaces as on a 7171 controller. Enter this command in global configuration.
Examples
The following example shows the two available null processing methods:
tn3270 null-processing ?3270 Use 3270-style null processing7171 Use 7171-style null processingtn3270 optimize-cursor-move
To increase performance between a remote user and a TN3270 host by limiting cursor movement information that is sent to user terminals, use the tn3270 optimize-cursor-move command in global configuration mode. To ensure that all cursor movement information is sent between the terminal and the TN3270 host, use the no form of this command.
tn3270 optimize-cursor-move
no tn3270 optimize-cursor-move
Syntax Description
This command has no arguments or keywords.
Defaults
Cursor movement escape strings are sent to the terminal.
Command Modes
Global configuration
Command History
Usage Guidelines
Issuing this command increases the speed of information transfer between users and TN3270 hosts through an access server.
If you do not issue this command, virtually every byte of information between the terminal and the TN3270 host is prepended and trailed by cursor-movement strings.
Examples
The following example disables status messages to users connected to 3278 terminals:
tn3270 optimize-cursor-moveRelated Commands
tn3270 status-message
Reenables the display of status messages after they have been disabled.
tn3270 reset-required
To lock a terminal after input error until the user resets the terminal, use the tn3270 reset-required command in global configuration mode. To return to the default of no reset required, use the no form of this command.
tn3270 reset-required
no tn3270 reset-required
Syntax Description
This command has no arguments or keywords.
Defaults
No reset is required.
Command Modes
Global configuration
Command History
Usage Guidelines
On a 3278-x terminal, the keyboard is locked and further input is not permitted after input error (due to field overflow, invalid entry, and so on) until the user presses the RESET key. Most TN3270 implementations leave the keyboard unlocked and remove any error message on the next key input after the error. Use this command to lock the keyboard until the user performs a reset.
Examples
The following example enables keyboard locking after an input error:
tn3270 reset-requiredtn3270 status-message
To reenable the display of status messages after they have been disabled, use the tn3270 status-message command in global configuration mode. To save bandwidth on asynchronous lines by not displaying status messages, use the no form of this command.
tn3270 status-message
no tn3270 status-message
Syntax Description
This command has no arguments or keywords.
Defaults
Status messages appear.
Command Modes
Global configuration
Command History
Usage Guidelines
Status messages appear on the console by default. These messages include "System Locked," "Field error," and "System UnLocked" messages. These messages are sent back to the terminal via the TTY line on the access server.
Disabling status messages saves bandwidth on asynchronous lines, which have very low bandwidth.
Examples
The following example disables status messages to users connected to 3270 terminals:
no tn3270 status-messageRelated Commands
tn3270 optimize-cursor-move
Increases performance between a remote user and a TN3270 host by limiting cursor movement information that is sent to user terminals.
tn3270 typeahead
To buffer keyboard data when a 3278 server is in locked mode, use the tn3270 typeahead command in global configuration mode. To disable the typeahead function, use the no form of this command.
tn3270 typeahead
no tn3270 typeahead
Syntax Description
This command has no arguments or keywords.
Defaults
Typeahead is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
When typeahead is enabled, the TN3270 client implementation in the Cisco IOS software permits you to continue typing while the system is trying to obtain a response from the TN3270 server. Information you type while a "System Locked" message appears on the terminal is stored in a buffer. After the "System Locked" message disappears, the information is then used as though it were just typed.
Examples
The following example saves user information when "System Locked" messages appear on the screen:
tn3270 typeaheadRelated Commands
tn3270 reset-required
Locks a terminal after input error until the user resets the terminal.