Table Of Contents
secure-server
server (transport map)
service exec-callback
service old-slip-prompts
service pt-vty-logging
session-limit
session-timeout
set (ruleset)
show arap
show entry
show keymap
show lat advertised
show lat groups
show lat nodes
show lat services
show lat sessions
show lat traffic
show line
show line autodetect
show node
show platform software configuration access policy
show service
show terminal
show tn3270 ascii-hexval
show tn3270 character-map
show translate
show translate ruleset
show transport-map
show ttycap
show users
show x25 pad
skip (ruleset)
slip
substitute (ruleset)
telnet
telnet break-on-ip
telnet refuse-negotiations
telnet speed
telnet sync-on-break
telnet transparent
terminal lat out-group
terminal lat remote-modification
terminal transport preferred
test (ruleset)
test translate
time-out
tn3270
tn3270 8bit display
tn3270 8bit transparent-mode
tn3270 character-map
tn3270 datastream
tn3270 null-processing
tn3270 optimize-cursor-move
tn3270 reset-required
tn3270 status-message
tn3270 typeahead
translate lat
translate ruleset
translate lat (virtual access interfaces)
translate tcp
translate tcp (virtual access interfaces)
translate use telnet
translate x25
translate x25 (virtual access interfaces)
transport-map type console
transport-map type persistent
transport input
transport interface
transport output
transport preferred
transport type console
transport type persistent
ttycap
txspeed
where
x25 pvc translate ruleset
x25 subaddress
x28
x28 no-outgoing
x3
secure-server
To enable the secure HTTP (HTTPS) server for a web user interface transport map, use the secure-server command in transport map configuration mode. To disable the HTTPS secure server for a web user interface transport map, use the no form of this command.
secure-server
no secure-server
Syntax Description
This command has no arguments or keywords.
Command Default
No server is enabled in a web user interface transport map by default.
Command Modes
Transport map configuration (config-tmap)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.1
|
This command was introduced on the Cisco ASR 1000 Series Routers.
|
Usage Guidelines
This command is used to enable the secure HTTPS web server for web user interface traffic. The other choice is the server option, which configures HTTP as the web server. Both web servers can be configured at the same time.
When this command is entered, the router decides which port to use for HTTPS traffic based on the ip http secure-server or ip http secure-port configuration. Therefore, ip http secure-server, which configures the router to use the default port of 443 for HTTPS traffic, or ip http secure-port, which specifies a user-defined port for HTTPS traffic, must be configured when the secure-server command is used.
Examples
In the following example, the web user interface using the default HTTPS port is enabled:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# ip http secure-server
Router(config)# transport-map type persistent webui https-webui
Router(config-tmap)# secure-server
Router(config-tmap)# exit
Router(config)# transport type persistent webui input https-webui
*Apr 22 02:38:43.597: %UICFGEXP-6-SERVER_NOTIFIED_START: R0/0: psd: Server wui has been
notified to start
Related Commands
Command
|
Description
|
ip http secure-server
|
Enables the HTTPS server on a router using the default HTTPS port.
|
ip http secure-port
|
Enables the HTTPS server on a router using a user-specified port.
|
server (transport map)
|
Enables the HTTP server for a persistent web user interface transport map.
|
transport type persistent
|
Applies an already-configured persistent transport map to an interface.
|
transport-map type persistent
|
Creates and names a transport map and enters transport map configuration mode.
|
server (transport map)
To enable the HTTP server for a web user interface transport map, use the server command in transport map configuration mode. To disable the HTTP server for a web user interface transport map, use the no form of this command.
server
no server
Syntax Description
This command has no arguments or keywords.
Command Default
No server is enabled in a web user interface transport map by default.
Command Modes
Transport map configuration (config-tmap)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.1
|
This command was introduced on the Cisco ASR 1000 Series Routers.
|
Usage Guidelines
This command is used to enable the HTTP web server for web user interface traffic. The other choice is the secure-server option, which configures HTTPS as the web server. Both web servers can be configured at the same time.
When this command is entered, the router decides which port to use for HTTP traffic based on the ip http server or ip http port configuration. Therefore, ip http server, which configures the router to use the default port of 80 for HTTP traffic, or ip http port, which specifies a user-defined port for HTTP traffic, must be configured when the server command is used.
Examples
In the following example, the web user interface using the default HTTP port is enabled:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# ip http server
Router(config)# transport-map type persistent webui http-webui
Router(config-tmap)# server
Router(config-tmap)# exit
Router(config)# transport type persistent webui input http-webui
*Apr 22 02:43:55.798: %UICFGEXP-6-SERVER_NOTIFIED_START: R0/0: psd: Server wui has been
notified to start
Related Commands
Command
|
Description
|
ip http server
|
Enables the HTTP server on a router using the default HTTP port.
|
ip http port
|
Enables the HTTP server on a router using a user-specified port.
|
secure-server
|
Enables the secure HTTP (HTTPS) server for a persistent web user interface transport map.
|
transport type persistent
|
Applies an already-configured persistent transport map to an interface.
|
transport-map type persistent
|
Creates and names a transport map and enters transport map configuration mode.
|
service exec-callback
To enable call back to clients who request a callback from the EXEC level, use the service exec-callback command in global configuration mode.
service exec-callback
Syntax Description
This command has no arguments or keywords.
Defaults
Callback is not enabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
This command enables the Cisco IOS software to return a call to a device that dials in, connects to the EXEC, and requests callback.
Examples
The following example enables EXEC level callback:
Related Commands
Command
|
Description
|
arap callback
|
Enables an ARA client to request a callback from an ARA client.
|
debug callback
|
Displays callback events when the router is using a modem and a chat script to call back on a terminal line.
|
debug confmodem
|
Displays information associated with the discovery and configuration of the modem attached to the router.
|
ppp callback (PPP client)
|
Enables a dialer interface that is not a DTR interface to function either as a callback client that requests callback or as a callback server that accepts callback requests.
|
script arap-callback
|
Specifies that a chat script start on a line when an ARA client requests a callback.
|
username
|
Establishes a username-based authentication system, such as PPP CHAP and PAP.
|
service old-slip-prompts
To provide backward compatibility for client software scripts expecting Serial Line Internet Protocol (SLIP) and PPP dialogs to be formatted with Cisco IOS software Release 9.1 or earlier releases, use the service old-slip-prompts command in global configuration mode. To disable this function, use the no form of this command.
service old-slip-prompts
no service old-slip-prompts
Syntax Description
This command has no arguments or keywords.
Defaults
The prompts and information sent by SLIP and PPP are formatted with the current release of Cisco IOS software.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
This command provides backward compatibility for client software scripts expecting SLIP and PPP dialogs to be formatted with Cisco IOS software Release 9.1 or earlier releases.
Examples
The following example shows the output of a SLIP command after the service old-slip-prompts command is enabled:
Router# configure terminal
Router(config)# service old-slip-prompts
IP address or hostname: 10.2.2.2
Your IP address is 10.2.2.2. MTU is 1500 bytes
service pt-vty-logging
To log the X.121 calling address, Call User Data (CUD), and IP address assigned to a vty asynchronous connection, use the service pt-vty-logging command in global configuration mode. To disable this function, use the no form of this command.
service pt-vty-logging
no service pt-vty-logging
Syntax Description
This command has no arguments or keywords.
Defaults
This feature is disabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
This command permits you to log the X.121 calling address, CUD, and IP address assigned to a vty asynchronous connection and direct this information to the console, an internal buffer, or a UNIX syslog server, depending on the logging configuration command you use. This authentication information can be used to associate an incoming packet assembler/disassembler (PAD) vty-asynchronous connection with an IP address.
Note
By default, the Cisco IOS software displays all messages to the console terminal.
Examples
The following example enables you to log the X.121 calling address, CUD, and IP address assigned to a vty asynchronous connection and save this information to a syslog server:
The following is sample output from the service pt-vty-logging command:
01:24:31: PAD18: call from 00011890 on LCI 10 PID 1 0 0 0 CUD "xyz"
Table 12 describes the fields shown in the output.
Table 12 service pt-vty-logging Field Descriptions
Field
|
Description
|
01:24:31:
|
Time stamp.
|
PAD18:
|
Active vty line number using the PAD connection.
|
00011890
|
The source or calling address.
|
on LCI 10
|
Incoming call is initiated on Logical Channel 10.
|
PID 1 0 0 0
|
The PAD Protocol Identifier is "01000000."
|
CUD "xyz"
|
CUD "xyz." If no CUD is available, this field will appear as follows:
|
Related Commands
Command
|
Description
|
logging
|
Logs messages to a syslog server host.
|
logging buffered
|
Logs messages to an internal buffer.
|
session-limit
To set the maximum number of terminal sessions per line, use the session-limit command in line configuration mode. To remove any specified session limit, use the no form of this command.
session-limit session-number
no session-limit
Syntax Description
session-number
|
Specifies the maximum number of sessions.
|
Defaults
The default and set session limits are displayed with the start-character EXEC command.
Command Modes
Line configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following example limits the number of sessions to eight on a ten-line range:
Related Commands
Command
|
Description
|
line vty
|
Specifies a virtual terminal for remote console access.
|
start-character
|
Sets the flow control start character.
|
session-timeout
To set the interval for closing the connection when there is no input or output traffic, use the session-timeout command in line configuration mode. To remove the timeout definition, use the no form of this command.
session-timeout minutes [output]
no session-timeout
Syntax Description
minutes
|
Specifies the timeout interval in minutes.
|
output
|
(Optional) Specifies that when traffic is sent to an asynchronous line from the router (within the specified interval), the connection is retained.
|
Defaults
The default interval is zero, indicating that the router maintains the connection indefinitely.
Command Modes
Line configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
This command sets the interval that the Cisco IOS software waits for traffic before closing the connection to a remote computer and returning the terminal to an idle state.
If only the session timeout command is specified, the session timeout interval is based solely on detected input from the user.
If the session timeout command is specified with the output keyword, the interval is based on both input and output traffic. You can specify a session timeout on each port.
The session-timeout command behaves slightly differently on virtual (vty) terminals than on physical console, auxiliary (aux), and terminal (tty) lines. When a timeout occurs on a vty, the user session returns to the EXEC prompt. When a timeout occurs on physical lines, the user session is logged out and the line returned to the idle state.
You can use a combination of the exec-timeout and session-timeout line configuration commands, set to approximately the same values, to get the same behavior from virtual lines that the session-timeout command causes on physical lines.
Examples
The following example sets an interval of 20 minutes and specifies that the timeout is subject to traffic detected from the user (input only):
The following example sets an interval of 10 minutes, subject to traffic on the line in either direction:
session-timeout 10 output
Related Commands
Command
|
Description
|
absolute-timeout
|
Sets the interval for closing the connection on a virtual terminal line.
|
exec-timeout
|
Sets the interval that the EXEC command interpreter waits until user input is detected.
|
set (ruleset)
To unconditionally set one or more connection parameters to a fixed value for a translation ruleset, use the set command in translate ruleset configuration mode. To remove the ruleset, use one of the no forms of this command.
set [#line-number] {pad | telnet} variable-parameter [{pad | telnet} variable-parameter [...]]
no set {pad | telnet} variable-parameter [{pad | telnet} variable-parameter [...]]
no set #line-number [...]
Syntax Description
#line-number
|
(Optional) The line in the ruleset template the command should occupy. The # character must be entered.
|
{pad | telnet}
|
Specifies the incoming or outgoing protocol, which controls the parameters that 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 parameter values 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 13 indicates the supported Telnet and PAD incoming and outgoing connection parameter keywords with an X.
|
[...]
|
(Optional) Specifies that multiple entries can be made as follows:
• Up to six set specifications can be entered on one command line.
• Multiple line numbers can be specified using the second no form of this command.
|
Defaults
No default behavior or values
Command Modes
Translate ruleset configuration
Command History
Release
|
Modification
|
12.3(8)T
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
Up to six set specifications can be entered on one command line. The ellipses in the format shown above means multiple set statements can be specified.
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 set command and line number within the ruleset template.
Once an incoming connection has been matched for processing, the ruleset generates the protocol translation parameters using a template that unconditionally sets a value defined by a set statement. It is also possible that the incoming connection could conditionally set a value based on a test of parameter values using regular expressions. This is a test and set operation. The ruleset template could then substitute one parameter into another from a regular expression pattern match. These command combinations provide the network administrator with much flexibility in determining the protocol parameter values to use when establishing a protocol translation session.
As an example of set, test, and substitute command usage, an incoming TCP connection to an outgoing PAD connection might unconditionally set the PAD's profile identifier as follows:
set pad profile Bldg-1-5ess
The incoming connection might conditionally set the profile identifier from a test of the destination information, as follows:
test telnet dest-addr \.11$ telnet dest-port ^10000$ set pad profile ess
Finally, the command might substitute a portion of the TCP destination port into the profile identifier, as follows:
substitute telnet dest-port ^1000(.)$ pad profile Bldg-1-5ess-\1
To combine the test and set commands, use the backslash character (\) to concatenate the command lines. The following statements test conditional parameters and then set appropriate parameters:
test telnet dest-addr ^172\.18\.0\.* telnet dest-port ^10.00 \
set pad pvc 1 telnet binary T
The protocol parameters for the incoming connection attempt are available for match expressions in the test, set and substitute statements. The values of the incoming connection attempt cannot be modified, though. For example, an incoming PAD connection has source and destination addresses that can be tested and used to modify other parameters, but the incoming connection addresses themselves cannot be modified.
Configuration errors are not detected when translation ruleset commands are entered. They are tested when the connection is attempted and the test (ruleset) command is used. In the following example, the translation ruleset set 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, and validated only upon 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
Table 13 lists the PAD and Telnet parameters that can be set, as indicated by an X. PAD outgoing service routing information (interface, CMNS MAC address, X.25 over TCP or XOT parameters, for example) are available for both switched virtual circuit (SVC) and permanent virtual circuit (PVC) service, and will take precedence over the X.25 routing table. If no routing information is specified, the X.25 routing table will be used. Entering an incomplete specification of routing information or the Connection-Mode Network Service (CMNS) MAC address, or omitting an interface specification for an Annex G data-link connection identifier (DLCI), will result in an error.
Table 13 Set Connection Parameter Keywords
Parameter
|
Description
|
Incoming PAD
|
Outgoing Telnet
|
Outgoing PAD
|
Incoming Telnet
|
authorize-method ASCII-string
|
Connection authorization method to use that must match one of a fixed set of values.
|
X
|
—
|
—
|
X
|
authorize-tag ASCII-string
|
Connection authorization identity to supply, entered as an ASCII string.
|
X
|
—
|
—
|
X
|
binary flag
|
Flag that specifies whether 8-bit binary data is required, entered as one of the following characters to specify binary mode: Y, y, 1-9, T, t.
|
—
|
X
|
—
|
X
|
cud ASCII-string
|
Call user data (CUD) that occurs after the protocol identification (PID). For X.29 service, this is the optional, user-specified text included in the command to place a call.
|
—
|
—
|
X
|
—
|
dest-addr address
|
Destination IP (Telnet) or X.121 (PAD) address.
|
—
|
X
|
X
|
—
|
dest-addr-ext address
|
Network service access point (NSAP) destination address extension.
|
—
|
—
|
X
|
—
|
dest-port port
|
Destination port entered as a decimal number from one to five digits long.
|
—
|
X
|
—
|
|
dlci number
|
Frame Relay data-link connection identifier (DLCI) of an Annex G service entered as a number from one to seven digits in length, although a size of two to four digits is more likely, or the NULL string if not received on an Annex G service.
|
—
|
—
|
X
|
—
|
eor specification
|
A character set defining the End-of-Record (EOR) string for the protocol translation session, entered as an ASCII or hexadecimal specification from one to four bytes in length, aaa or 0x19, as examples.
|
—
|
X
|
—
|
X
|
eor-insert flag
|
Flag specifying that the EOR character set should be inserted for PAD data being forwarded to a Telnet session, and is entered as a single character. Use one of the following characters to specify EOR insertion: Y, y, 1-9, T, t.
|
—
|
X
|
—
|
X
|
hostname address
|
Destination host name for Domain Name System (DNS) resolution entered as an ASCII string.
|
—
|
X
|
—
|
—
|
idle seconds
|
Number of seconds the PAD connection can be idle before being cleared.
|
X
|
—
|
X
|
—
|
interface type number
|
Interface to be used for the circuit, entered using standard Cisco IOS interface designations; Serial1/0:1, for example.
|
—
|
—
|
X
|
—
|
keepalive-period seconds
|
Indicates the number of seconds between TCP keepalives for the X.25 over TCP (XOT) connection.
TCP keepalive information applies only when a ruleset is configured to match an XOT destination address. Example:
match dest-addr ^5555.$ xot-dest-addr 5.5.5.2
|
X
|
—
|
X
|
—
|
keepalive-tries number
|
Indicates the number of TCP keepalives to send before the XOT connection is declared dead.
TCP keepalive information applies only when a ruleset is configured to match an XOT destination address. Example:
match dest-addr ^5555.$ xot-dest-addr 5.5.5.2
|
X
|
—
|
X
|
—
|
local flag
|
Flag specifying that Telnet control sequences should be forwarded, not processed, and is entered as a single character. Use one of the following characters to specify local mode: Y, y, 1-9, T, t.
|
—
|
X
|
—
|
X
|
mac address
|
Connection-Mode Network Service (CMNS) service remote host MAC address entered as three hexadecimal numbers of four digits separated by a period, (0000.fc08.12ab, for example) or the NULL string if not received on a CMNS service.
|
—
|
—
|
X
|
—
|
no-reset
|
Suppress a PVC Reset packet at session startup.
|
X
|
—
|
X
|
—
|
packetsize size
|
X.25 maximum data packet sizes to request, entered as two numbers from the following choices: 16, 32, 64, 128, 256, 512, 1024, 2048, 4096.
|
—
|
—
|
X
|
—
|
pid byte-string
|
PID string specified in ASCII or hexadecimal. A hexadecimal PID must be prefixed by "0x." For example, 0x01000000 is the standard PAD PID. Although it is available for specifying a nonstandard Call PID, this parameter is not restricted to the common PID length and can be used to specify the entire user data field.
|
—
|
—
|
X
|
—
|
printer flag
|
Printer access mode. Flag specifying that the outgoing connection should be brought up before the incoming connection is confirmed. Use one of the following characters to specify printer mode: Y, y, 1-9, T, t.
An unsuccessful outgoing connection attempt results in the incoming connection to the ruleset being refused, rather than being accepted and then closed, which is the default behavior. Note that using this keyword will force the ruleset quiet keyword to be applied to the translation.
|
X
|
—
|
—
|
X
|
profile name
|
Named PAD profile to use.
|
X
|
—
|
X
|
—
|
pvc circuit-number
|
Permanent virtual circuit (PVC) entered as a number from 1 to 4095, or the null string if not a PVC.
|
—
|
—
|
X
|
—
|
reverse
|
Request reverse charging.
|
—
|
—
|
X
|
—
|
reversed flag
|
Flag to indicate whether a reverse charged Call is permitted. This flag applies to a switched virtual circuit (SVC) and is entered as a single character, Y or N, for yes or no.
|
—
|
—
|
—
|
—
|
rotor
|
Modifies the behavior of the host-name keyword by allowing one of the IP addresses defined by the ip host configuration command to be chosen randomly. If one address fails, another will be tried until a connection is made or all address choices are exhausted.
|
—
|
X
|
—
|
—
|
source-addr address
|
Source X.121 address.
|
—
|
—
|
X
|
—
|
source-addr-ext address
|
NSAP source address extension.
|
—
|
—
|
X
|
—
|
source-ifc type number
|
Interface from which to take the source IP address, entered using standard Cisco IOS interface designations, Loopback0, for example.
|
—
|
X
|
X
|
—
|
stream flag
|
Flag that specifies whether Telnet negotiation should be sent or accepted, entered as one of the following characters to specify stream mode: Y, y, 1-9, T, t.
|
—
|
X
|
—
|
X
|
swap flag
|
X.29 role reversal. Flag that indicates the PAD connection should not initiate X.29 commands when first connected. Use one of the following characters to swap behavior: Y, y, 1-9, T, t.
This parameter enables incoming and outgoing PAD connections to be swapped so that a protocol translation is treated like a PAD when it accepts a call. By default, the protocol translation functions like a PAD for calls that it initiates, and like an X.25 host for calls it accepts.
|
X
|
—
|
X
|
—
|
use-map map
|
Use the map defined for PAD service.
|
—
|
—
|
X
|
—
|
windowsize size
|
X.25 window sizes to request, entered as two numbers in a range from 1 to 127.
|
—
|
—
|
X
|
—
|
xot-dest-addr address
|
Destination IP address of an X.25 over TCP (XOT) service entered in standard IP address dotted decimal notation (10.0.0.127, for example) or the NULL string if not received on an XOT service.
|
—
|
—
|
X
|
—
|
xot-source-addr address
|
Source IP address of an XOT service entered in standard IP address dotted decimal notation (10.0.0.127, for example) or the NULL string if not received on an XOT service.
|
—
|
—
|
—
|
—
|
Examples
The following example shows how to build a ruleset by writing a match statement, specifying protocol translation options, setting parameters for incoming Telnet connections, then testing and setting appropriate parameters for incoming PAD connections. Note use of the backslash character to combine the test and set 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 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 printer Y telnet binary Y
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
Related Commands
Command
|
Description
|
description (ruleset)
|
Adds a description about a translation ruleset.
|
match (ruleset)
|
Identifies a connection for processing by the translation ruleset.
|
options (ruleset)
|
Specifies protocol translation options in a translation ruleset.
|
show translate ruleset
|
Displays a summary of a specific or of all configured translation rulesets, behavioral parameters, and usage statistic.
|
skip (ruleset)
|
Identifies a connection for omission by the translation ruleset.
|
substitute (ruleset)
|
Matches an available protocol and substitutes another in a translation ruleset.
|
test (ruleset)
|
Tests parameter values in a translation ruleset using regular expressions.
|
test translate
|
Displays a trace of protocol translation behavior for a connection attempt.
|
translate ruleset
|
Defines a unique name for a translation ruleset, specifies translated protocols, and enters translate ruleset configuration mode.
|
x25 pvc translate ruleset
|
Configures PVCs that are valid for protocol translation ruleset handling.
|
show arap
To display information about a running AppleTalk Remote Access Protocol (ARAP) connection, use the show arap command in EXEC mode.
show arap [line-number]
Syntax Description
line-number
|
(Optional) Number of the line on which an ARAP connection is established and active.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
Use the show arap command with no arguments to display a summary of the ARAP traffic since the router was last booted.
Examples
The following is sample output from the show arap command:
Statistics are cumulative since last reboot
Total ARAP connections: 2
Total Appletalk packets output: 157824
Total Appletalk packets input: 12465
These fields refer to the sum of all of the ARA connections since the box was last reloaded.
The following sample output results in a display of information about ARA activity on a specific line (line 3):
"Unlimited time left" or "22 minutes left"
"Doing smartbuffering" or "Smartbuffering disabled"
Appletalk packets output: 157824
Appletalk packets input: 12465
Appletalk packets overflowed: 1642
Appletalk packets dropped: 586
V42bis compression efficiency (incoming/outgoing): {percentage/percentage}
MNP4 packets received: 864
MNP4 garbled packets received: 4
MNP4 out of order packets received: 0
Table 14 describes the significant fields shown in the display.
Table 14 show arap Field Descriptions
Field
|
Description
|
Active for integer minutes
|
Number of minutes since ARAP started on the line.
|
Unlimited time left or integer minutes left
|
Remaining time limit on the line, if applicable on the line.
|
Doing smartbuffering or Smartbuffering disabled
|
Obsolete. Always says "Doing smartbuffering."
|
Appletalk packets output:
|
Number of AppleTalk packets that have been received from the Apple Macintosh and out to the network during this connection.
|
Appletalk packets input:
|
Number of AppleTalk packets that have been received from the network and sent to the Apple Macintosh during this connection.
|
Appletalk packets overflowed:
|
Number of packets from the network that have been dropped because the link to the Apple Macintosh was congested.
|
Appletalk packets dropped:
|
Number of packets from the network that have been dropped because it was unnecessary to pass them (frequently RTMP).
|
V42bis compression efficiency (incoming/outgoing):
|
Performance of the v42bis protocol underneath ARA, expressed as a percentage of incoming/percentage outgoing. If the efficiency is low, a network user is probably copying already compressed files across the link. Generally, low efficiency means slow performance.
|
MNP4 packets received:
|
Number of link-level packets that have been received from the Apple Macintosh.
|
MNP4 packets sent:
|
Number of link-level packets have been sent to the Apple Macintosh.
|
MNP4 garbled packets received:
|
Number of garbled packets that have been received from the Apple Macintosh.
|
MNP4 out of order packets received:
|
Number of out-of-order packets that have been received from the Apple Macintosh.
|
MNP4 packets resent:
|
Number of times packets have been re-sent.1
|
MNP4 nobuffers:
|
Number of times MNP4 has run out of buffers. This field should be zero.
|
show entry
To display the list of queued host-initiated connections to a router, use the show entry command in EXEC mode.
show entry
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
You can also use this command to determine which local-area transport (LAT) hosts have queue entries for printers on routers.
Examples
The following is sample output from the show entry command. The display shows that two LAT connections are waiting for access to port 5. The list is ordered so that the lower-numbered entry has been waiting longer, and will use the line next.
1 waiting 0:02:22 for port 5 from LAT node BLUE
2 waiting 0:00:32 for port 5 from LAT node STELLA
Table 15 describes the fields in the first line of output shown in the display.
Table 15 show entry Field Descriptions
Field
|
Description
|
1
|
Number assigned to the queued connection attempt.
|
waiting 0:02:22
|
Interval (hours:minutes:seconds) during which the connection attempt has been waiting.
|
for port 5
|
Port for which the connection attempt is waiting.
|
from LAT node BLUE
|
Name of the user (BLUE) attempting to make the connection.
|
show keymap
To test for the availability of a keymap after a connection on a router takes place, use the show keymap command in EXEC mode.
show keymap [keymap-name | all]
Syntax Description
keymap-name
|
(Optional) Name of the keymap.
|
all
|
(Optional) Lists the names of all defined keymaps. The name of the default keymap is not listed.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
The Cisco IOS software searches for the specified keymap in its active configuration image and lists the complete entry if found. If the keymap is not found, an appropriate "not found" message appears.
If you do not use any arguments with the show keymap command, then the keymap currently used for the terminal is displayed.
Examples
The following is sample output from the show keymap command:
ciscodefault { clear = '^z'; flinp = '^x'; enter = '^m';\
synch = '^r'; reshow = '^v'; eeof = '^e'; tab = '^i';\
btab = '^b'; nl = '^n'; left = '^h'; right = '^l';\
up = '^k'; down = '^j'; einp = '^w'; reset = '^t';\
xoff = '^s'; xon = '^q'; escape = '^c'; ferase = '^u';\
pa1 = '^p1'; pa2 = '^p2'; pa3 = '^p3';\
pfk1 = '\E1'; pfk2 = '\E2'; pfk3 = '\E3'; pfk4 = '\E4';\
pfk5 = '\E5'; pfk6 = '\E6'; pfk7 = '\E7'; pfk8 = '\E8';\
pfk9 = '\E9'; pfk10 = '\E0'; pfk11 = '\E-'; pfk12 = '\E=';\
pfk13 = '\E!'; pfk14 = '\E@'; pfk15 = '\E#'; pfk16 = '\E$';\
pfk17 = '\E%'; pfk18 = '\E\^'; pfk19 = '\E&'; pfk20 = '\E*';\
pfk21 = '\E('; pfk22 = '\E)'; pfk23 = '\E_'; pfk24 = '\E+';\
Refer to the keymap command for more information about keyboard mappings and keymap entry structures.
Related Commands
Command
|
Description
|
keymap
|
Defines specific characteristics of keyboard mappings.
|
show lat advertised
To display the local-area transport (LAT) services a router offers to other systems running LAT on the network, use the show lat advertised command in EXEC mode.
show lat advertised
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
Advertised services are created with the lat service commands. The display includes the service rating, rotary group if present, and whether the service is enabled for incoming connections.
Examples
The following is sample output from the show lat advertised command:
Router# show lat advertised
service Name Rating Rotary Flags
service1 4(Dynamic) None Enabled
Autocommand: telnet service1
Service2 0(Dynamic) 12 Enabled
Ident: service2 modem services
service3 4(Dynamic) None Enabled
The display shows output from a router named router1 that has three services defined: service1, service2, and service3.
Table 16 describes the fields shown in the display.
Table 16 show lat advertised Field Descriptions
Field
|
Description
|
Service Name
|
Lists the LAT service name.
|
Rating
|
Lists the static service rating set, if any.
|
Rotary
|
Lists the associated rotary service.
|
Flags
|
Lists whether a service is enabled.
|
Autocommand
|
Defines the autocommand associated with the service.
|
Ident
|
Lists the advertised identification for the service.
|
show lat groups
To display the groups that were defined in the Cisco IOS software with the lat group-list command, use the show lat groups command in EXEC mode.
show lat groups
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show lat groups command:
manufacturing 10 70 71 72
Table 17 describes the fields shown in the display.
Table 17 show lat groups Field Descriptions
Field
|
Description
|
Group Name
|
Assigned group name.
|
Len
|
Size of internal data structure used to contain the group code map.
|
Groups
|
Group codes associated with the learned group.
|
Related Commands
Command
|
Description
|
lat group-list
|
Allows a name to be assigned to the group list, which is any combination of group names, numbers, or ranges.
|
show lat nodes
To display information about all known local-area transport (LAT) nodes, use the show lat nodes command in EXEC mode.
show lat nodes
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show lat nodes command:
Node "service1", usage -1, Interface Ethernet0, Address 0000.0c01.0509
Timer 89, sequence 188, changes 131, flags 0x0, protocol 5.1
Facility 0, Product code 0, Product version 0
Recv 0/0/0, Xmit 0/0/0, 0 Dups, 0 ReXmit
Bad messages: 0, Bad slots: 0, Solicits accepted: 0
Solicits rejected: 0, Multiple nodes: 0
Node "service2", usage -1, Local
Timer 99, sequence 4, changes 151, flags 0x0, protocol 5.2
Facility 0, Product code 0, Product version 0
Recv 0/0/0, Xmit 0/0/0, 0 Dups, 0 ReXmit
Bad messages: 0, Bad slots: 0, Solicits accepted: 0
Solicits rejected: 0, Multiple nodes: 0
Node "service3", usage -1, Interface Ethernet0, Address 0000.0cff.c9ed
Timer 99, sequence 9, changes 159, flags 0x0, protocol 5.1
Facility 0, Product code 0, Product version 0
Recv 0/0/0, Xmit 0/0/0, 0 Dups, 0 ReXmit
Bad messages: 0, Bad slots: 0, Solicits accepted: 0
Solicits rejected: 0, Multiple nodes: 0
Node "service4", usage -1, Interface Ethernet0, Address 0000.0c02.c7c1
Timer -10351, sequence 1, changes 131, flags 0x40, protocol 5.2
Facility 0, Product code 0, Product version 0
Recv 0/0/0, Xmit 0/0/0, 0 Dups, 0 ReXmit
Bad messages: 0, Bad slots: 0, Solicits accepted: 0
Solicits rejected: 0, Multiple nodes: 0
Table 18 describes the significant fields shown in the display.
Table 18 show lat nodes Field Descriptions
Field
|
Description
|
Node
|
The node name as reported by the host computer.
|
usage
|
The number of virtual circuits currently active to this node.
|
Interface
|
Node interface type and number.
|
Address
|
The MAC address of the Ethernet interface for the node.
|
Timer
|
The number of seconds remaining until the service advertisement message for this node will time out; this value is set to three times the nodes multicast timer value whenever a new service advertisement message is received.
|
sequence
|
The sequence number received in the last service advertisement message received. Nodes increment their sequence number when the contents of the service advertisement change.
|
changes
|
The internal representation of what changed in the multicast message the last time the sequence number changed.
|
flags
|
The internal representation of various state information about the node.
|
protocol
|
The LAT protocol version used by the node.
|
Facility
|
The remote facility number.
|
Product code
|
The remote product code.
|
Product version
|
The remote product version.
|
Recv and Xmit
|
The number of messages, slots, and bytes received or sent to the node. The number of messages is the number of LAT virtual circuit messages. Each virtual circuit message contains some number of slots, which contain actual terminal data or control information. Bytes is the number of data bytes (input or output characters) exchanged.
|
Dups
|
The number of duplicate virtual circuit messages received.
|
ReXmit
|
The number of virtual circuit messages resent.
|
Bad messages
|
The number of bad messages received.
|
Bad slots
|
The number of bad slots received.
|
Solicits accepted
|
The number of solicit-information requests accepted.
|
Solicits rejected
|
The number of solicit-information requests rejected.
|
Multiple nodes
|
The total of multiple nodes seen.
|
Groups
|
The list of group codes advertised by the service-advertisement message of the node.
|
Service classes
|
The number of service classes.
|
show lat services
To display information about learned local-area transport (LAT) services in the Cisco IOS software, use the show lat services command in EXEC mode.
show lat services [service-name]
Syntax Description
service-name
|
(Optional) Name of a specific LAT service.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show lat services command:
Router# show lat services
Service Name Rating Interface Node (Address)
ABCDEFGHIJ 5 Ethernet0 SERVICE1(0000.0c00.391f)
GLAD 84 Ethernet0 SERVICE2 (aa00.0400.9205)
Ident: Welcome to Gateway
WHEEL 83 Ethernet0 SERVICE3 (aa00.0400.9005)
ZXYW 5 Ethernet0 SERVICE4 (0000.0c00.391f)
Table 19 describes the significant fields shown in the display.
Table 19 show lat services Field Descriptions
Field
|
Description
|
Service Name
|
LAT service name.
|
Rating
|
Rating of the service. If a single service is provided by more than one host, the Cisco IOS software connects to the one with the highest rating.
|
Interface
|
Interface type.
|
Node
|
Connection address.
|
(Address)
|
Advertised identification for the service.
|
Related Commands
Command
|
Description
|
show lat sessions
|
Displays active LAT sessions.
|
show resource-pool call
|
Displays specific LAT learned services.
|
show lat sessions
To display active local-area transport (LAT) sessions, use the show lat sessions command in EXEC mode.
show lat sessions [line-number]
Syntax Description
line-number
|
(Optional) Displays an active LAT session on a specific line.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show lat sessions command. In this example, information about all active LAT sessions is displayed. The output is divided into three sections for each session (in this case two sessions): TTY data, session data, and remote node data.
Router> show lat sessions
tty0, connection 1 to service TERM1
Name "0", Local usage 1/0, Remote usage disabled
Flags: Local Connects, Enabled
Config flags: -FlowOut, -FlowIn, Parameter Info
Flow control ^S/^Q in ^S/^Q out, Mode Normal, Parity None, databits 8
Name TERM1, Remote Id 1, Local Id 1
Remote credits 2, Local credits 0, Advertised Credits 2
Max Data Slot 255, Max Attn Slot 255, Stop Reason 0
Node "TERM1", Address 0000.0C00.291F, usage 1
Timer 59, sequence 5, changes 159, flags 0x0, protocol 5.1
Recv 56/22/83, Xmit 41/23/14, 0 Dups, 0 ReXmit
tty10, connection 1 to service ENG2
Name "10", Local usage 1/0, Remote usage disabled
Flags: Local Connects, Enabled
Config flags: -FlowOut, +FlowIn, Set Parameters, 0x40000000
Flow control ^S/^Q in ^S/^Q out, Mode Normal, Parity None, databits 8
Name ENG2, Remote Id 1, Local Id 1
Remote credits 1, Local credits 0, Advertised Credits 2
Max Data Slot 255, Max Attn Slot 255, Stop Reason 0
Node "ENG2", Address AA00.0400.34DC, usage 1
Timer 179, sequence 60, changes 255, flags 0x0, protocol 5.1
Recv 58/29/186, Xmit 50/36/21, 0 Dups, 0 ReXmit
The following sample output displays information about active LAT sessions on one line (line 10). The output is divided into three sections: TTY data, session data, and remote node data.
Router> show lat sessions 10
tty10, connection 1 to service ENG2
Name "10", Local usage 1/0, Remote usage disabled
Flags: Local Connects, Enabled
Config flags: -FlowOut, +FlowIn, Set Parameters, 0x40000000
Flow control ^S/^Q in ^S/^Q out, Mode Normal, Parity None, databits 8
Name ENG2, Remote Id 1, Local Id 1
Remote credits 1, Local credits 0, Advertised Credits 2
Max Data Slot 255, Max Attn Slot 255, Stop Reason 0
Node "ENG2", Address AA00.0400.34DC, usage 1
Timer 189, sequence 61, changes 247, flags 0x0, protocol 5.1
Recv 60/29/186, Xmit 52/36/21, 0 Dups, 0 ReXmit
Table 20 describes the fields shown in the displays.
Table 20 show lat sessions Field Descriptions
Field
|
Description
|
TTY data
|
Summary of the LAT-oriented terminal-line-specific data.
|
Name
|
Name used for this port as a port identification string. The name is reported to remote systems, which can display it in some operating-system dependent manner. This value is also used for targets of host-initiated connections. Currently, this value is hard-wired to be the line number of the associated terminal line.
|
Local/Remote usage
|
Current status of the terminal. The number is reported as current/maximum, where current is the current number of sessions of a given type, and maximum is the maximum number of sessions allowed (or zero if there is no maximum). If a terminal is being used for outgoing sessions, the local usage is equal to the number of current LAT sessions. If the terminal is being used for incoming sessions, local usage is disabled, and the remote count and maximum is one.
|
Flags
|
Current state of the line, and whether there are any queued host-initiated connections.
|
Type flags
|
Report flags not used in the current software release.
|
Config flags
|
Current port state as reflected by the most recent configuration message exchange.
|
Flow control
|
Lists set flow control characters.
|
Groups
|
Group code list currently in use for the line.
|
Session data
|
Reports various parameters about the connection.
|
Name
|
For the outbound connection, the name of the remote service to which it is connected. For inbound connections, this field is currently unused.
|
Remote/Local Id
|
Slot IDs being used to uniquely identify the session multiplexed over the underlying LAT virtual circuit.
|
Remote/Local/ Advertised Credits
|
Number of flow control credits that the Cisco IOS software will be sending to the host as soon as possible. The advertised credits are the number of credits that have already been sent.
|
Flags
|
Transient conditions in the LAT-state machine dealing with the current connection status.
|
Max Data Slot
|
Maximum number of characters that can be sent in a single data slot.
|
Max Attn Slot
|
Maximum amount of data that can be sent in an attention message. Current LAT implementations only send 1-byte attention messages (attention messages are used to flush buffered output). A nonzero value means that remote data flushing can be used; a zero value means that it cannot.
|
Stop Reason
|
Reason the session was stopped, if it was stopped but not deleted. This value is usually zero, indicating that the session has not yet been stopped. If a session persists for a long time with a nonzero stop reason, there is probably a problem in the local LAT software.
|
Remote Node data
|
Reports information about the remote node. The data includes the same fields as those from the show lat nodes output.
|
Node
|
Node name as reported by the host computer.
|
Address
|
MAC address of the Ethernet interface for the node.
|
usage
|
Number of virtual circuits currently active to the node.
|
Timer
|
Number of seconds remaining until the service advertisement message for the node will time out; this value is set to three times greater than the node multicast timer value whenever a new service-advertisement message is received.
|
sequence
|
Sequence number received in the last service-advertisement message. Nodes increment their sequence number when the contents of the service-advertisement change.
|
changes
|
Internal representation of what changed in the multicast message the last time the sequence number changed.
|
flags
|
Internal representation of various state information about the node.
|
protocol
|
LAT protocol version used by the node.
|
Recv and Xmit
|
Number of messages, slots, and bytes received or sent to the node. The number of messages is the number of LAT virtual circuit messages. Each virtual circuit message contains some number of slots, which contain actual terminal data or control information.
|
Dups
|
Number of duplicate virtual circuit messages received.
|
ReXmit
|
Number of virtual circuit messages resent.
|
Groups
|
Group codes advertised by the service-advertisement message of the node.
|
Related Commands
Command
|
Description
|
show lat services
|
Displays information about learned LAT services in the Cisco IOS software.
|
show resource-pool call
|
Displays specific LAT learned services.
|
show lat traffic
To display information about traffic and resource utilization statistics on all active lines, use the show lat traffic command in EXEC mode.
show lat traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show lat traffic command:
0/100 circuits, 0/500 sessions, 1/500 services
100 sessions/circuit, circuit timer 80, keep-alive timer 5
Recv: 335535 messages (2478 duplicates), 161722 slots, 1950146 bytes
0 bad circuit messages, 3458 service messages (52 used)
Xmit: 182376 messages (2761 retransmit), 146490 slots, 36085 bytes
Total: 23 circuits created, 38 sessions
Table 21 describes the significant fields shown in the display.
Table 21 show lat traffic Field Descriptions
Field
|
Description
|
Local host statistics
|
Information about the router.
|
circuits
|
Current number and maximum support number of virtual circuits.
|
sessions
|
Current and maximum number of sessions.
|
services
|
Current number of known remote services, and the maximum supported.
|
sessions/circuit
|
Number of sessions per virtual circuit supported by the software.
|
circuit timer
|
Value of the virtual circuit timer parameter defined by the lat vc-timer global configuration command.
|
keep-alive timer
|
Value defined by the lat ka-timer global configuration command.
|
Recv
|
Statistics about local node receive totals.
|
messages
|
Total count of virtual circuit messages received.
|
duplicates
|
Number of duplicate virtual circuit messages received.
|
slots
|
Number of slots received.
|
bytes
|
Number of data bytes received.
|
bad circuit messages
|
Count of invalid messages received.
|
service messages
|
Number of service advertisement multicast messages received.
|
used
|
Number of multicast messages that caused the local node information to be updated.
|
Xmit
|
Various transmission totals.
|
messages
|
Total number of virtual circuit messages sent.
|
retransmit
|
Number of virtual circuit messages resent due to the lack of an acknowledgment.
|
slots
|
Number of data and control slots sent.
|
bytes
|
Count of user data bytes sent.
|
circuit timeouts
|
Count of times that a virtual circuit timed out because the remote node stopped responding (due to a node failure or communications failure).
|
Total
|
Count of virtual circuits and sessions that have existed since the router booted or rebooted.
|
show line
To display parameters of a terminal line, use the show line command in user EXEC or privileged EXEC mode.
show line [line-number [upper-line-number] | [{aux | console | vty} line-number
[upper-line-number]] [summary]
Syntax Description
line-number
|
(Optional) Absolute line number of the line for which you want to list parameters.
|
upper-line-number
|
(Optional) Specifies the upper limit of a range.
|
aux
|
(Optional) Auxiliary line.
|
console
|
(Optional) Primary terminal line.
|
vty
|
(Optional) Virtual terminal line.
|
summary
|
(Optional) Line status summary.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
11.3(1)T
|
The summary keyword was added.
|
12.0
|
The vty keyword was added.
|
12.1
|
Output from this command was modified to show the transport method configured.
|
12.2(13)T
|
This command was modified to indicate when support for closed user group (CUG) security is enabled on the line.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
If Closed User Group (CUG) security is configured on a line, the show line command used with the line-number argument causes "CUG Security Enabled" to be displayed in the Capabilities field of the output.
The show line command used with the summary keyword provides line status summary details such as whether there were modem calls or character mode calls.
Examples
The following sample output from the show line vty4 command shows that virtual terminal line 4 has a send and receive rate of 9600 bits per second (bps). Also shown are the terminal screen width and length, modem state, preferred transport method, and other characteristics.
Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns
22 VTY - - - - - 0 0 0/0 -
Line 22, Location: "", Type: ""
Length: 24 lines, Width: 80 columns
Baud rate (TX/RX) is 9600/9600
Capabilities: CUG Security Enabled
Special Chars: Escape Hold Stop Start Disconnect Activation
Timeouts: Idle EXEC Idle Session Modem Answer Session
Idle Session Disconnect Warning
Login-sequence User Response
Session limit is not set.
Time since activation: never
History is enabled, history size is 10.
DNS resolution in show commands is enabled
Full user help is disabled
Allowed input transports are none.
Allowed output transports are pad v120 telnet rlogin udptn.
Preferred transport is telnet.
No output characters are padded
No special data dispatching characters
Table 22 describes the significant fields shown in the report displayed by the show line command (and may not match the previous example).
Table 22 show line Field Descriptions
Field
|
Description
|
Tty
|
Line number.
|
Typ
|
Type of line. In this case, a virtual terminal line, which is active, in asynchronous mode denoted by the preceding "A." All possible values follow:
• VTY—virtual terminal line
• CTY—console
• AUX—auxiliary port
• TTY—asynchronous terminal port
• lpt—parallel printer
|
Tx/Rx
|
Transmit rate/receive rate of the line.
|
A
|
Indicates whether autobaud has been configured for the line. A value of F indicates that autobaud has been configured; a hyphen indicates that it has not been configured.
|
Modem
|
Types of modem signals that have been configured for the line. Possible values follow:
• callin
• callout
• cts-req
• DTR-Act
• inout
• RIisCD
|
Roty
|
Rotary group configured for the line, if set.
|
AccO, AccI
|
Output or input access list number configured for the line.
|
Uses
|
Number of connections established to or from the line since the system was restarted.
|
Noise
|
Number of times noise has been detected on the line since the system restarted.
|
Overruns
|
Hardware Universal Asynchronous Receiver/Transmitter (UART) overruns or software buffer overflows, both defined as the number of overruns or overflows that have occurred on the specified line since the system was restarted. Hardware overruns are buffer overruns; the UART chip has received bits from the software faster than it can process them. A software overflow occurs when the software has received bits from the hardware faster than it can process them.
|
A (or I or *)
|
An A at the upper left of the display indicates that the user is running an asynchronous interface; an I indicates that the line has an asynchronous interface available; an asterisk (*) indicates that the line is otherwise active (in character mode).
|
Line
|
Definition of the specified protocol and address of the line.
|
Location
|
Location of the current line.
|
Type
|
Type of line, as specified by the line global configuration command.
|
Length
|
Length of the terminal or screen display, in rows.
|
Width
|
Width of the terminal or screen display, in columns.
|
Baud rate (TX/RX)
|
Transmit rate/receive rate of the line, in bps.
|
Status
|
State of the line: ready or not, connected or disconnected, active or inactive, exit banner or no exit banner, asynchronous interface active or inactive.
|
Capabilities
|
Current terminal capabilities.
|
Modem state
|
Modem control state. Although the sample output shows the modem state Idle, this field should always say READY.
|
Special Chars
|
Current settings of special characters that were input by the user (or taken by default) from the following global configuration commands:
• escape-character
• hold-character
• stop-character
• start-character
• disconnect-character
• activation-character
|
Timeouts
|
Current settings that were input by the user (or taken by default) from the following global configuration commands:
• exec-timeout
• session-timeout
• dispatch-timeout
• modem answer-timeout
• session-disconnect-warning
• timeout login response
• autoselect timeout
|
Session limit
|
Maximum number of sessions.
|
Time since activation
|
Last time start_process was run.
|
Editing
|
Whether command-line editing is enabled.
|
History
|
Current history list size, set by the user (or taken by default) from the history configuration command.
|
DNS resolution in show commands is
|
Whether Open Shortest Path First (OSPF) is configured to look up Domain Name System (DNS) names for use in show EXEC command displays.
|
Full user help
|
Whether full user help has been set by the user with the terminal full-help EXEC command or by the administrator with the full-help line configuration command.
|
Allowed input transports are
|
Current set transport method, set by the user (or taken by default) from the transport input line configuration command.
|
Allowed output transports are
|
Current set transport method, set by the user (or taken by default) from the transport output line configuration command.
|
Preferred transport is
|
Current set transport method, set by the user (or taken by default) from the transport preferred line configuration command.
|
...characters are padded
|
Current set padding, set by the user (or taken by default) from the padding line configuration command.
|
...data dispatching characters
|
Current dispatch character set by the user (or taken by default) from the dispatch-character line configuration command.
|
Modem type is unknown
|
No modemcap has been applied to this line, that means either modem autoconfigure has not been configured for the line, or modem autoconfigure discovery is configured. Autoconfigure is unable to discover the modem type.
|
Dispatch
|
Displays the current configured dispatch-timeout value.
|
The following sample output from the show line summary command shows line summary status for lines 1/3/36 through 1/3/102. Each row of output represents 36 lines, and the line status characters in groups of four for readability. For example, the first row represents information on rows 1/3/36 through 1/3/71, and the first line status character "U" corresponds to line 1/3/36.
Router# show line summary
1/3/36: U??? ---- ---- ---- ---- --u- ---- ???? ....
1/3/72: ---- ???? ---- ???? ???? MMMM MMMM MMMM MMMM
2 character mode users. (U)
31 lines used, but currently idle. (-)
4 lines do not exist. (.)
16 lines in use by modem management (M)
18 total lines in use, 1 not authenticated (lowercase)
Table 23 describes the possible line status characters that can be shown in output from the show line summary command.
Table 23 Line Status Character Descriptions
Line Status Character
|
Description
|
?
|
Line has never been used.
|
-
|
Lines has been used but is currently idle.
|
.
|
Line does not exist.
|
A
|
Line in use by a packet mode user such as asynchronous PPP, Serial Line Internet Protocol (SLIP), Appletalk Remote Access Protocol (ARAP), or Serial Tunneling (STUN).
|
D
|
Line in use by a digit mode user such as V.110 or V.120.
|
F
|
Line in use by a TCP fast-stream user.
|
M
|
Line in use by modem management.
|
U
|
Line in use by character mode user, such as an EXEC user making an outbound packet connection using Telnet, rlogin, local-area transport (LAT), packet assembler/disassembler (PAD), or normal (nonfast-stream) TCP clear.
|
V
|
Line in use by a voice mode user.
|
Related Commands
Command
|
Description
|
modem enable
|
Enables backup dial capability through the console port (changes the console port into an auxiliary port).
|
show line autodetect
To detect the type of device connected on the console line, use the show line autodetect command in user EXEC or privileged EXEC mode.
show line autodetect
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.2(13)ZG
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
Use this command to detect the type of device connected on the console line.
Examples
The following example shows the command used to configure console autodetect mode:
Router(config-line)# modem enable autodetect
Use the show line autodetect command to determine when a modem or a console has been detected:
Router# show line autodetect
Detection State: Feature not enabled
Router# show line autodetect
Detection State: Nothing Attached
Router# show line autodetect
Detection State: Init State
Router# show line autodetect
Detection State: Console Attached
Router# show line autodetect
Detection State: Modem Attached
Table 24 describes the significant fields shown in the display.
Table 24 show line autodetect Field Descriptions
Field
|
Description
|
Detection State: Feature not enabled
|
No device connection is detected.
|
Detection State: Nothing Attached
|
No cable is attached to the EIA/TIA-232 port on the router.
|
Detection State: Init State
|
Autodetection has been enabled, but no changes have been detected.
|
Detection State: Console Attached
|
A DTE console or terminal device is attached.
|
Detection State: Modem Attached
|
A DCE asynchronous modem device is attached.
|
Related Commands
Command
|
Description
|
modem enable
|
Enables backup dial capability through the console port (changes the console port into an auxiliary port).
|
show node
To display information about local-area transport (LAT) nodes, use the show node command in EXEC mode.
show node [all | node-name] [counters | status | summary]
Syntax Description
all
|
(Optional) Specifies all nodes.
|
node-name
|
(Optional) Indicates the name of the node for which status is required.
|
counters
|
(Optional) Specifies the various node counters.
|
status
|
(Optional) Specifies detailed node status. This is the default if a node name is specified.
|
summary
|
(Optional) Specifies a status summary for the node. This is the default if no node name is specified.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
Entering the show node command with no arguments is the same as entering the show node all summary command and shows a one-line summary of all known nodes.
You can enter the show node command with either a specific node name or the all keyword, but not both.
The show node command displays three different sets of information about a node: the node counters, the node status, or a one-line summary of the node status.
You can enter the show node command with only one of the counters, status, or summary keywords. If you enter show node and two of these keywords without specifying a node name, the first keyword is treated as a node name, causing an error. If you enter the show node node-name command and two of these keywords, the second keyword will be treated as ambiguous.
The show node command with a node-name argument but no counters, status, or summary keyword defaults to show node node-name status.
Examples
The following is sample output from the show node command with no further keywords (the same as the show node all summary command):
Node Name Status Identification
WHEEL Reachable Welcome to VAX/VMS V5.4-2
Table 25 describes the significant fields shown in the display.
Table 25 show node Field Descriptions
Field
|
Description
|
Node Name
|
Lists the names of the nodes.
|
Status
|
Indicates whether the node is reachable or not.
|
Identification
|
Identification string for the node.
|
The following is sample output from the show node output that defaults to show node chaos status. It results in a display of the detailed status of node chaos.
Node: CHAOS Address: 00-00-0C-01-05-09
LAT Protocol: V5.1 Data Link Frame Size: 1500
Service Name Status Rating Identification
Table 26 describes the significant fields shown in the display.
Table 26 show node status Field Descriptions
Field
|
Description
|
Node
|
Lists the node name as reported by the host computer.
|
Address
|
Identifies the MAC address of the node Ethernet interface.
|
LAT protocol
|
Lists the version of the LAT protocol used by the node.
|
Data Link Frame Size
|
Lists the size of the largest packet that can be sent to the LAT host.
|
Identification
|
Lists the identification string for the node.
|
Node Groups
|
Lists the group code list that is advertised by the remote node, which comes from the service advertisement of the remote node.
|
Service Name
|
Lists the LAT service name.
|
Status
|
Indicates whether the node is currently available on the network.
|
Rating
|
Indicates the rating of the service: an integer from 0 to 255, with the highest number being the preferred service. Used for load balancing.
|
The following sample output displays the counter information for a specific node:
Router> show node tarmac counters
Seconds Since Zeroed: 100 Multiple Node Addresses: 0
Messages Received: 0 Duplicates Received: 0
Messages Transmitted: 0 Messages Re-transmitted: 0
Slots Received: 0 Illegal Messages Received: 0
Slots Transmitted: 0 Illegal Slots Received: 0
Bytes Received: 0 Solicitations Accepted: 0
Bytes Transmitted: 0 Solicitations Rejected: 0
In the following sample command and output displays, the status keyword is treated as the node name:
Router> show node status counters
Local -710- Node STATUS not known
In the following example, the second keyword counters is treated as ambiguous:
Router> show node lager status counters
Local -702- Keyword "COUNTERS" not known or ambiguous
show platform software configuration access policy
To view the access policies and banners for users entering the router using Telnet, Secure Shell (SSH), or the console port, enter the show platform software configuration access policy command in priviliged EXEC and diagnostic mode.
show platform software configuration access policy
Syntax Description
This comand has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
Privileged EXEC (#)
Diagnostic (diag)
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.1
|
This command was introduced on the Cisco ASR 1000 Series Routers.
|
Usage Guidelines
Access policies for the console port, Telnet, and SSH are set through the use of transport maps. If no transport maps are applied for a particular access method, the router uses the default settings.
Transport maps are configured by entering the transport-map type command, then setting the configuration of the transport map in transport map configuration mode. Transport maps are then enabled using the transport type global configuration command.
Examples
In the following example, the connection policy and banners are set for a persistent Telnet transport map, and the transport map is enabled.
The show platform software configuration access policy output is given both before the new transport map is enabled and after the transport map is enabled so the changes to the Telnet configuration are illustrated in the output.
Router# show platform software configuration access policy
The current access-policies
Rule : wait with interrupt
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# transport-map type persistent telnet telnethandler
Router(config-tmap)# connection wait allow interruptable
Router(config-tmap)# banner diagnostic X
Enter TEXT message. End with the character 'X'.
Welcome to Diagnostic Mode
Router(config-tmap)# banner wait X
Enter TEXT message. End with the character 'X'.
Router(config-tmap)# transport interface gigabitethernet 0
Router(config-tmap)# exit
Router(config)# transport type persistent telnet input telnethandler
Router# show platform software configuration access policy
The current access-policies
Rule : wait with interrupt
Welcome to Diagnostic Mode
Rule : wait with interrupt
In the following example, the connection policy and banners are set for a persistent SSH transport map, and the transport map is enabled.
The show platform software configuration access policy output is given both before the new transport map is enabled and after the transport map is enabled so the changes to the SSH configuration are illustrated in the output.
Router# show platform software configuration access policy
The current access-policies
Rule : wait with interrupt
Welcome to Diagnostic Mode
Rule : wait with interrupt
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# transport-map type persistent ssh sshhandler
Router(config-tmap)# connection wait allow interruptable
Router(config-tmap)# banner diagnostic X
Enter TEXT message. End with the character 'X'.
Router(config-tmap)# banner wait X
Enter TEXT message. End with the character 'X'.
Router(config-tmap)# rsa keypair-name sshkeys
Router(config-tmap)# transport interface gigabitethernet 0
Router(config-tmap)# exit
Router(config)# transport type persistent ssh input sshhandler
Router# show platform software configuration access policy
The current access-policies
Rule : wait with interrupt
Welcome to Diagnostic Mode
Rule : wait with interrupt
Rule : wait with interrupt
Related Commands
Command
|
Description
|
banner (transport-map)
|
Creates a banner message that will be seen by users entering diagnostic mode or waiting for the IOS process as a result of the transport map configuration.
|
connection wait
|
Specifies how an incoming connection will be handled.
|
transport interface
|
Applies the transport map settings to the interface.
|
transport type persistent
|
Applies an already-configured persistent transport map to an interface.
|
transport-map type persistent
|
Creates and names a persistent transport map and enters transport map configuration mode.
|
show service
To display specific local-area transport (LAT) learned services, use the show service command in EXEC mode.
show service [service-name]
Syntax Description
service-name
|
(Optional) The name of a specific LAT service.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
The show service command without a service name displays a list of known LAT learned services. When entered with the service-name argument, it displays a more-detailed status of the named service. If no LAT learned service by the specified name is known, then a lookup is done for an IP host of that name.
Examples
The following is sample output from the show service command:
Service Name Status Identification
BLUE Available Welcome to VAX/VMS V5.4
STELLA-BLUE Available Welcome to VAX/VMS V5.4
The following is sample output of the show service command for a specific service:
Router> show service blue
Node Name Status Rating Identification
BLUE reachable 84 Welcome to VAX/VMS V5.4
Table 27 describes the significant fields shown in the two previous displays.
Table 27 show service Field Descriptions
Field
|
Description
|
Service
|
Name of the service.
|
Node Name
|
Name of the nodes advertising the service.
|
Status
|
Status of the service: Available or Unknown when a command is entered without a service name. Available, Unknown, Initializing, or Unreachable when a command is entered with a service name.
|
Rating
|
Rating of the service: An integer from 0 to 255, with the highest number being the preferred service. Used for load balancing.
|
Identification
|
Identification string.
|
show terminal
To obtain information about the terminal configuration parameter settings for the current terminal line, use the show terminal command in EXEC mode.
show terminal
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show terminal command:
Line 2, Location: "", Type: ""
Length: 24 lines, Width: 80 columns
Baud rate (TX/RX) is 9600/9600
Status: Ready, Active, No Exit Banner
Special Chars: Escape Hold Stop Start Disconnect Activation
Timeouts: Idle EXEC Idle Session Modem Answer Session Dispatch
never never 0:00:15 not imp not set
Session limit is not set.
Allowed transports are telnet rlogin. Preferred is telnet
No output characters are padded
Table 28 describes the fields in the first three lines of the show terminal output.
Table 28 show terminal Field Descriptions—First Three Lines of Output
Field
|
Description
|
Line 2
|
Current terminal line.
|
Location: ""
|
Location of the current terminal line, as specified using the location line configuration command.
|
Type: ""
|
Type of the current terminal line, as specified using the line global configuration command.
|
Length: 24 lines
|
Length of the terminal display.
|
Width: 80 columns
|
Width of the terminal display, in character columns.
|
Baud rate (TX/RX) is 9600/9600
|
Transmit rate/receive rate of the line.
|
The following line of output indicates the status of the line:
Status: Ready, Active, No Exit Banner
Table 29 describes possible values for the Status field.
Table 29 show terminal Field Descriptions—Status Field Values
Field
|
Description
|
Active
|
A process is actively using the line.
|
Autobauding
|
The line is running the autobaud process.
|
Carrier Dropped
|
Some sense of "carrier" has been dropped, so the line process should be killed.
|
Connected
|
The line has at least one active connection.
|
Dialing Out
|
A dial-on-demand routing (DDR) asynchronous interface is dialing a remote site on this line.
|
Echo Off
|
The line is not echoing what the user types in (for example, because a password must be entered).
|
Escape Started
|
The first character of the escape sequence has been typed.
|
Escape Typed
|
Both characters of the escape sequence have been typed.
|
Hanging Up
|
The line state is "hanging up."
|
Hardware XON/XOFF
|
The line uses a Universal Asynchronous Receiver/Transmitter (UART) that supports XON/XOFF flow control in hardware. (This does not mean that the line is currently using software flow control.)
|
Hold Typed
|
The user typed the "hold character" (and the line is paused).
|
Idle
|
The line modem state is "idle" (see modem state diagrams).
|
Idle Timeout
|
An idle timeout has occurred.
|
Input Stopped
|
The input has been turned off because of hardware flow control or overflow.
|
No Exit Banner
|
The normal exit banner will not be displayed on this line.
|
PSI Enabled
|
The line is paying attention to typed escape characters.
|
Rcvd BREAK
|
A BREAK sequence has been received on the line.
|
Rcvd Command
|
The line has received a special command sequence (for example, ^^B for send break).
|
Rcvd CR
|
The last character received was a carriage return.
|
Ready
|
The line state is "ready."
|
Ring Transition
|
A transition has occurred on the RING signal of the line.
|
Send Break Soon
|
Send a BREAK on the line soon.
|
Send XOFF Soon
|
Buffers are full and an XOFF should be sent soon.
|
Sending Break
|
A BREAK sequence is being sent on the line.
|
Sent XOFF
|
Buffers were full, so an XOFF was sent.
|
SLIP Mode
|
The line is running SLIP or PPP.
|
The following line of output indicates the status of the capabilities of the line. These capabilities correspond closely to configurable parameters that can be set using configuration commands.
Table 30 describes possible values for the Capabilities field.
Table 30 show terminal Field Descriptions—Capabilities Field Values
Field
|
Description
|
Autobaud Full Range
|
Corresponds to the autobaud command.
|
Character Padding
|
At least one pad c x configuration command has been used.
|
Enabled
|
The user has "enabled" successfully.
|
EXEC Suppressed
|
Corresponds to the no exec command.
|
Hangup on Last Close
|
Corresponds to the autohangup command.
|
Hardware Flowcontrol In
|
Corresponds to the flowcontrol hardware in command.
|
Hardware Flowcontrol Out
|
Corresponds to the flowcontrol hardware out command.
|
Insecure
|
Corresponds to the insecure command.
|
Lockable
|
Corresponds to the lockable command.
|
Modem Callin
|
Corresponds to the modem callin command.
|
Modem Callout
|
Corresponds to the modem callout command.
|
Modem CTS-Required
|
Corresponds to the modem cts-required command.
|
Modem DTR-Active
|
Corresponds to the modem dtr-active command.
|
Modem RI is CD
|
Corresponds to the modem ri-is-cd command.
|
No Login Banner
|
Corresponds to the no exec-banner command.
|
Notification Set
|
Corresponds to the notify command.
|
Output Non-Idle
|
Corresponds to the session-timeout command.
|
Permanent SLIP
|
Corresponds to the slip-dedicated command
|
Private Line
|
Corresponds to the private command.
|
Refuse Suppress-GA
|
Corresponds to the telnet refuse command.
|
Receives Logging Output
|
Corresponds to the monitor command.
|
Refuse Telnet Echo
|
Corresponds to the telnet refuse command.
|
Send BREAK on IP
|
Corresponds to the telnet break-on-ip command.
|
SLIP allowed
|
Corresponds to the slip address command.
|
Software Flowcontrol In
|
Corresponds to the flowcontrol software in command.
|
Software Flowcontrol Out
|
Corresponds to the flowcontrol software out command.
|
Telnet Transparent Mode
|
Corresponds to the telnet transparent command.
|
The following line of output indicates the modem state. Values include Autobauding, Carrier Dropped, Hanging Up, Idle, and Ready.
The following lines of output indicate the special characters that can be entered to activate various terminal operations. The none or hyphen (-) values imply that no special characters are set.
Special Chars: Escape Hold Stop Start Disconnect Activation
The following lines of output indicate the timeout values that have been configured for the line:
Timeouts: Idle EXEC Idle Session Modem Answer Session Dispatch
never never 0:00:15 not imp not set
Table 31 describes the fields in the preceding lines of output.
Table 31 show terminal Field Descriptions—Timeouts
Field
|
Description
|
Idle EXEC
|
Interval that the EXEC command interpreter waits for user input before resuming the current connection; or if no connections exist, returning the terminal to the idle state and disconnecting the incoming session. This interval is set using the exec-timeout command.
|
Idle Session
|
Interval that the Cisco IOS software waits for traffic before closing the connection to a remote computer and returning the terminal to an idle state. This interval is set using the session-timeout command.
|
Modem Answer
|
Interval during which the software raises DTR in response to RING and the modem response to CTS. This interval is set using the modem answer-timeout command.
|
Session
|
Not implemented in this release.
|
Dispatch
|
Number of milliseconds the software waits after putting the first character into a packet buffer before sending the packet. This interval is set using the dispatch-timeout command.
|
The following lines of output indicate how various options have been configured:
Session limit is not set.
Allowed transports are telnet rlogin. Preferred is telnet
No output characters are padded
show tn3270 ascii-hexval
To determine ASCII-hexadecimal character mappings, use the show tn3270 ascii-hexval command in EXEC mode.
show tn3270 ascii-hexval
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
Use the show tn3270 ascii-hexval command to display the hexadecimal value of a character on your keyboard. After you enter the show tn3270 ascii-hexval command, you will be prompted to press a key. The hexadecimal value of the ASCII character is displayed. This command is useful for users who do not know the ASCII codes associated with various keys or do not have manuals for their terminals.
Examples
The following is sample output from the show tn3270 ascii-hexval command:
Router> show tn3270 ascii-hexval
Press key> 7 - hexadecimal value is 0x37.
Router> show tn3270 ascii-hexval
Press key> f - hexadecimal value is 0x66.
Router> show tn3270 ascii-hexval
Press key> not printable - hexadecimal value is 0xD.
Related Commands
Command
|
Description
|
show tn3270 character-map
|
Displays character mappings between ASCII and EBCDIC.
|
tn3270 character-map
|
Converts incoming EBCDIC characters into ASCII characters for TN3270 connections.
|
show tn3270 character-map
To display character mappings between ASCII and EBCDIC, use the show tn3270 character-map command in EXEC mode.
show tn3270 character-map {all | ebcdic-in-hex}
Syntax Description
all
|
Displays all nonstandard character mappings.
|
ebcdic-in-hex
|
Displays the ASCII mapping for a specific EBCDIC character.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show tn3270 character-map command:
Router# show tn3270 character-map all
EBCDIC 0x81 <=> 0x78 ASCII
EBCDIC 0x82 <=> 0x79 ASCII
EBCDIC 0x83 <=> 0x7A ASCII
Refer to the tn3270 character-map command for more information about EBCDIC and ASCII character mappings.
Related Commands
Command
|
Description
|
show tn3270 ascii-hexval
|
Displays ASCII-hexadecimal character mappings.
|
tn3270 character-map
|
Converts incoming EBCDIC characters into ASCII characters for TN3270 connections.
|
show translate
To display translation sessions that have been configured, use the show translate command in privileged EXEC mode.
show translate
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
12.3(2)T
|
Output fields were added to display information about translation sessions configured to use an End-of-Record (EOR) marker.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
The display from this command shows each translation session set up on the router. It shows the incoming device and virtual terminal protocol, and the outgoing device and protocol.
Examples
The following show translate sample output is based on the following translate command configuration:
translate x25 3131415912345 ppp ip-pool scope-name router1 keepalive 0
If the previous translate command is enabled, the following output is created by the show translate command:
Translate From: x25 3131415912345
To: PPP ip-pool scope-name router1 keepalive 0
1/1 users active, 1 peak, 1 total, 0 failures
Table 32 describes the significant fields shown in the display.
Table 32 show translate Field Descriptions—X.25 to IP Translation
Field
|
Description
|
Translate From: x25 3131415912345
|
Protocol (X.25) and address (3131415912345) of the incoming device.
|
To: PPP
|
The virtual terminal protocol (PPP).
|
ip-pool
|
Obtain an IP address from a DHCP proxy client or a local pool.
|
scope-name router1
|
Specific local scope name (router1) from which to obtain an IP address.
|
keepalive 0
|
Indicates that keepalive updates have been disabled for the current translation session.
|
1/1 users active
|
Number of users active over the total number of users.
|
1 peak
|
Maximum number of translate sessions up at any given time.
|
1 total
|
Total number of translation sessions.
|
0 failures
|
Number of failed translation attempts resulting from this configuration.
|
The following show translate sample output is based on the following translate command configuration:
translate x25 31301234 PPP 192.168.14.23 ipx-client Loopback0
If the previous translate command is enabled, the following output is created by the show translate command:
Translate From: x25 31301234
To: PPP 192.168.14.23 ipx-client Loopback0
1/1 users active, 1 peak, 1 total, 0 failures
Table 33 describes the significant fields shown in the display.
Table 33 show translate Field Descriptions—X.25 to IPX Translation
Field
|
Description
|
Translate From: x25 31301234
|
Protocol (X.25) and address (31301234) of the incoming device.
|
To: PPP 192.168.14.23
|
The virtual terminal protocol (PPP) and IP address of the outgoing device.
|
ipx-client Loopback0
|
Indicates that loopback interface 0 has been configured in client mode.
|
1/1 users active
|
Number of users active over the total number of users.
|
1 peak
|
Maximum number of translate sessions up at any given time.
|
1 total
|
Total number of translation sessions.
|
0 failures
|
Number of failed translation attempts resulting from this configuration.
|
The following show translate sample output is based on the following translate command configuration:
translate tcp 10.60.155.63 x25 12345678 pvc 3 dynamic eor 0x19 insert
If the previous translate command is enabled, the following output is created by the show translate command:
Translate From: TCP 10.60.155.63 Port 23
To: X25 12345678 Pvc 3 dynamic
1/1 users active, 1 peak, 1 total, 0 failures
Table 34 describes the significant fields shown in the display.
Table 34 show translate Field Descriptions—TCP to X.25 Translation
Field
|
Description
|
Translate From: TCP 10.60.155.63 Port 23
|
Protocol (TCP) and address (10.60.155.63) of the incoming device.
|
To: X25 12345678
|
The virtual terminal protocol (X.25) and X.121 destination address of the outgoing device.
|
Pvc 3
|
The outgoing connection is using permanent virtual circuit (PVC) 3.
|
dynamic
|
Terminate the TCP-to-X.25 PVC session when the interface goes down.
|
EOR 0x19 Insert
|
Indicates that EOR functionality is configured and that the EOR marker (0x19) will be inserted into the TCP stream after each received X.25 packet that does not contain the More-bit set.
|
1/1 users active
|
Number of users active over the total number of users.
|
1 peak
|
Maximum number of translate sessions up at any given time.
|
1 total
|
Total number of translation sessions.
|
0 failures
|
Number of failed translation attempts resulting from this configuration.
|
show translate ruleset
To display a summary of a specific or of all configured translate rulesets, behavioral parameters, and usage statistics, use the show translate ruleset command in user or privileged EXEC mode.
show translate ruleset [name]
Syntax Description
name
|
(Optional) Ruleset name.
|
Defaults
Displays all one-line translate command and ruleset configuration and connection information.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(8)T
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
This command is useful for maintaining and updating ruleset statements. The output of this command identifies match, skip, set, test, and substitute statement lines and numbers them. The line number can be used to reconfigure or remove any of these statements.
When the optional name argument is used, the display includes only the configured ruleset and does not include information about the standard one-line translate commands.
Examples
Specific Ruleset Information
The following example shows specific information about the ruleset named A:
Router# show translate ruleset A
PT ruleset A, from pad to telnet.
administrative locks: 2 (2 readers, 0 writers).
translations: 0 created, 0 active, 0 failed, 0 created for test.
#1 match on 1 pad test: dest-addr ^5555(.)$.
#2 skip on 1 pad test: dest-addr ^5555[89]$.
options: limited to 10 active sessions.
set/test/substitute lines: 3.
#1 set 1 parameter: telnet/dest-addr 10.2.2.1.
#2 substitute from: pad/dest-addr ^5555(.)$ into telnet/dest-port 200\1.
#3 test 1 parameter: telnet/dest-port 2004; to set 1: telnet/dest-port 2010.
Information About All Rulesets
The following example shows information about all protocol translation rulesets configured on the device:
Router# show translate ruleset
Protocol translation rulesets: 27 created, 25 deleted, 25 freed, 0 failed.
in/out: telnet 1/1, pad 1/1, ppp -/0, autocommand -/0, virtual-template -/0.
PT ruleset A, from telnet to pad.
administrative locks: 2 (2 readers, 0 writers).
translations: 2 created, 0 active, 0 failed, 4 created for test.
#1 match on 1 telnet test: dest-addr 10.2.2.3.
options: none configured.
set/test/substitute lines: 4.
#1 test 1 parameter: telnet/dest-addr 10.2.2.3; to set 1: pad/dest-addr 4444.
#2 test 1 parameter: pad/dest-addr 4444; to set 1: pad/source-addr-ext 11.2222.2.
#3 substitute from: pad/source-addr-ext 11.2222.2 into pad/source-addr-ext 11.2222.3.
#4 test 1 parameter: pad/source-addr-ext ^11.2222.3$; to set 1: telnet/binary 1.
PT ruleset B, from pad to telnet.
administrative locks: 2 (2 readers, 0 writers).
translations: 0 created, 0 active, 0 failed, 0 created for test.
#1 match on 1 pad test: dest-addr ^5555(.)$.
#2 skip on 1 pad test: dest-addr ^55551$
set/test/substitute lines: 3.
#1 set 1 parameter: telnet/dest-addr 10.2.2.1.
#2 substitute from: pad/dest-addr ^5555(.) into telnet/dest-port 2000.
#3 test 1 parameter: pad/dest-addr ^5555[6-9]
Table 35 describes all significant fields seen that may be reported by this command.
Table 35 show translate ruleset Field Descriptions
Field
|
Description
|
Protocol translation rulesets:
|
Describes ruleset memory management statistics. In the sample output seen in the "Information About All Rulesets" section, there were 27 total translate rulesets created, 25 rulesets deleted from the configuration, 25 rulesets freed, and 0 ruleset creation failure.
|
active ruleset:
|
Total number of current configured ruleset (rulesets created - rulesets deleted).
|
in/out:
|
Ruleset translation protocol counts, by incoming and outgoing protocol.
|
PT ruleset
|
Shows the defined name of the ruleset. In the sample output seen in the "Information About All Rulesets" section, the ruleset named A is configured to translate from a Telnet connection to PAD a connection.
|
administrative locks:
|
Describes the total ruleset administrative locks.
|
readers:
|
Total count of administrative locks.
|
writers:
|
Total count of configuration editors (rulesets being edited).
Note Editing a ruleset changes the behavior of the set as a whole; an incoming connection will not be processed against a ruleset with an editor lock.
|
translations:
|
Describes ruleset memory management statistics for the dynamic one-line translate command, generated for and used by the protocol translation operation.
|
created:
|
Total number of translation sessions created by this ruleset.
|
test function translations:
|
Total number of translations created by the test (ruleset) command.
|
active:
|
Total number of active connections through this translation.
|
failed:
|
Total number of attempted translation connections that failed. Example of failures: number of maximum users limit has reached, a destination host not responding, an access failure, login failure, no resources, and so on.
|
(0 max-user):
|
Total number of connections refused due to reaching maximum users limit; (zero, in this example).
|
match/skip lines:
|
Total number of match and skip lines configured for the ruleset.
|
#1 match #2 skip
|
The line number within the block of match and skip commands.
|
options:
|
Options configured for ruleset processing.
|
set/test/substitute lines:
|
Total number of set, test, and substitute lines configured for the ruleset.
|
#1 set #2 substitute #3 test
|
Reports the line number within the block of set, substitute, and test commands and describes the commands configured for the ruleset.
|
#line number substitute from:
|
Reports the line number within the block of set, test, and substitute commands and describes the substitute command configured for the ruleset.
|
#line number [set/test] parameter:
|
Reports the line number within the block of set and test commands and describes the set and test parameters configured for the ruleset.
|
Related Commands
Command
|
Description
|
description (ruleset)
|
Adds a description about a translation ruleset.
|
match (ruleset)
|
Identifies a connection for processing by the translation ruleset.
|
options (ruleset)
|
Specifies protocol translation options in a translation ruleset.
|
set (ruleset)
|
Unconditionally sets one or more connection parameters to a fixed value for a translation ruleset.
|
skip (ruleset)
|
Identifies a connection for omission by the translation ruleset.
|
substitute (ruleset)
|
Matches an available protocol and substitutes another in a translation ruleset.
|
test (ruleset)
|
Tests parameter values in a translation ruleset using regular expressions.
|
test translate
|
Displays a trace of protocol translation behavior for a connection attempt.
|
translate ruleset
|
Defines a unique name for a translation ruleset, specifies translated protocols, and enters translate ruleset configuration mode.
|
x25 pvc translate ruleset
|
Configures PVCs that are valid for protocol translation ruleset handling.
|
show transport-map
To view the transport map configuration details on your router, enter the show transport-map EXEC or priviliged EXEC command.
show transport map [all | name transport-map-name | type [console | persistent [ssh | telnet |
webui]]]
Syntax Description
all
|
Specifies information on all transport maps.
|
name transport-map-name
|
Specifies information on a specific transport map, where transport-map-name is the name of the specific transport map.
|
type [console | persistent [ssh | telnet | webui]
|
Specifies information on all transport maps of a specific type on the router. Options include:
• console—specifies information on all console port transport maps.
• persistent ssh—specifies information on all persistent ssh transport maps.
• persistent telnet—specifies information on all persistent telnet transport maps.
• persistent webui—specifies information on all web user interface transport maps.
|
Command Modes
EXEC (>)
Privileged EXEC (#)
Command Default
No default behavior or values.
Command History
Release
|
Modification
|
Cisco IOS XE Release 2.1
|
This command was introduced on the Cisco ASR 1000 Series Routers.
|
Usage Guidelines
This command is used to view information about transport map configurations.
If you are unable to access the IOS CLI in diagnostic mode and want transport map configuration information, the show platform software configuration access policy command is available in diagnostic mode and provides some of the information displayed in this command output for console port, Telnet, and SSH connections.
Examples
In the following example, the router has a console port transport map named consolehandler, a persistent SSH transport map named sshhandler, and a persistent Telnet transport map named telnethandler. The show transport-map all, show transport-map type, and show transport-map name command are all used throughout the example to gather information on the transport maps.
Router#show transport-map all
Wait option: Wait Allow Interruptable
Welcome to Diagnostic Mode
Type: Persistent SSH Transport
Wait option: Wait Allow Interruptable
Welcome to Diagnostic Mode
Authentication retries: 5
Type: Persistent Telnet Transport
Wait option: Wait Allow Interruptable
Welcome to Diagnostic Mode
Type: Persistent Telnet Transport
Router#show transport-map type console
Wait option: Wait Allow Interruptable
Welcome to Diagnostic Mode
Router#show transport-map type persistent ssh
Type: Persistent SSH Transport
Wait option: Wait Allow Interruptable
Welcome to Diagnostic Mode
Authentication retries: 5
Router#show transport-map type persistent telnet
Type: Persistent Telnet Transport
Wait option: Wait Allow Interruptable
Welcome to Diagnostic Mode
Type: Persistent Telnet Transport
Router#show transport-map name telnethandler
Type: Persistent Telnet Transport
Wait option: Wait Allow Interruptable
Welcome to Diagnostic Mode
Router#show transport-map name telnethandler1
% No transport map telnethandler1
Router#show transport-map name consolehandler
Wait option: Wait Allow Interruptable
Welcome to Diagnostic Mode
Router#show transport-map name sshhandler
Type: Persistent SSH Transport
Wait option: Wait Allow Interruptable
Welcome to Diagnostic Mode
Authentication retries: 5
In the following example, a transport map that has enabled both the HTTP server and the secure HTTP server is viewed using this command.
Router# show transport-map type persistent webui
Type: Persistent Webui Transport
Table 36 show transport-map Field Descriptions
Field
|
Description
|
Name:
|
Specifies the name of the transport map. A transport-map is named when the transport-map type command is entered in global configuration mode to create a transport map.
|
Type:
|
Specifies the type of transport map. The possibilities include Console Transport for console port transport maps, Persistent SSH for Persistent SSH transport maps, and Persistent Telnet for persistent Telnet transport maps, Persistent WebUI Transport for web user interface transport maps.
|
Wait option:
|
Displayed the connection policy. The connection policy is defined using the connection wait transport map configuration command, and can include allow (wait for an IOS vty line, or exit router if send break signal is sent), allow interruptable (wait for an IOS vty line, and enter diagnostic mode if a send break signal is sent), none (immediately enter diagnostic mode if no IOS vty line is available, or none disconnect (immediately leave router if no IOS vty line is available).
|
Wait banner:
|
Specifies the banner seen when a user is waiting for an IOS vty line. The wait banner is defined using the banner wait transport map configuration mode command. If no text is seen, there is no wait banner.
|
Bshell banner:
|
Specifies the banner seen when a user is waiting for an diagnostic mode. The wait banner is defined using the banner diagnostic transport map configuration mode command. If no text is seen, there is no wait banner.
|
Interface:
|
Specifies the interface where the transport map will be applied if it is enabled or once it is enabled. The interface is defined using the transport interface transport map configuration mode command.
|
Timeout:
|
The login SSH timeout value, in seconds. The login timeout value can be set for SSH transport maps using the time-out transport map configuration command and has a default of 120 seconds.
|
Authentication-retries:
|
The number of authentication retries before dropping the connection for a persistent SSH connection attempt. This value can be set using the authentication-retries transport map configuration command.
|
RSA keypair:
|
The RSA keypair name, which is set using the rsa keypair-name transport map configuration command.
|
Server
|
The HTTP server. This value tells users if the HTTP server is enabled or disabled when a particular web user interface transport map is used.
|
Secure Server
|
The secure HTTP (HTTPS) server. This value tells users if the secure HTTP server is enabled or disabled when a particular web user interface transport map is used.
|
Related Commands
Command
|
Description
|
authentication-retries
|
Specifies the number of SSH authentication retries before dropping the connection when a persistent SSH transport map is applied to the receiving interface.
|
banner (transport map)
|
Creates a banner message that will be seen by users entering diagnostic mode or waiting for the IOS process as a result of the transport map configuration.
|
connection wait
|
Specifies how an incoming connection will be handled.
|
rsa keypair-name
|
Names the RSA keypair to be used for persistent SSH connections.
|
secure-server
|
Enables the secure HTTP (HTTPS) server for a persistent web user interface transport map.
|
server
|
Enables the HTTP server for a persistent web user interface transport map.
|
show platform software configuration access policy
|
Displays the access policy and banner settings for console, Telnet, and SSH connections.
|
time-out
|
Specifies the SSH timeout interval in seconds.
|
transport interface
|
Applies the transport map settings to the interface.
|
transport type persistent
|
Applies an already-configured persistent transport map to an interface.
|
transport-map type persistent
|
Creates and names a persistent transport map and enters transport map configuration mode.
|
show ttycap
To test for the availability of a ttycap after a connection on a router takes place, use the show ttycap command in EXEC mode.
show ttycap [ttycap-name | all]
Syntax Description
ttycap-name
|
(Optional) Name of a ttycap.
|
all
|
(Optional) Lists the names of all defined ttycaps. The name of the default ttycap is not listed.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
The Cisco IOS software searches for the specified ttycap in its active configuration image, and lists the complete entry if found. If it is not found, an appropriate "not found" message appears.
If you do not include any arguments with the show ttycap command, then the current keymap used for the terminal is displayed.
Examples
The following is sample output from the show ttycap command:
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:
ttycap3 d0|vt100|vt100-am|vt100am|dec vt100
ttycap2 dl|vt200|vt220|vt200-js|vt220-js|dec vt200 series with jump scroll
ttycap1 ku|h19-u|h19u|heathkit with underscore cursor
Router# show ttycap ttycap1
ttycap1 ku|h19-u|h19u|heathkit with underscore cursor:\:vs@:ve@:tc=h19-b:\
:al=1*\EL:am:le=^H:bs:cd=\EJ:ce=\EK:cl=\EE:cm=\EY%+ %+\
:co#80:dc=\EN:\:dl=1*\EM:do=\EB:ei=\EO:ho=\EH\
:im=\E@:li#24:mi:nd=\EC:as=\EF:ae=\EG:\
:ms:pt:sr=\EI:se=\Eq:so=\Ep:up=\EA:vs=\Ex4:ve=\Ey4:\
:kb=^h:ku=\EA:kd=\EB:kl=\ED:kr=\EC:kh=\EH:kn#8:ke=\E>:ks=\E=:\
:k1=\ES:k2=\ET:k3=\EU:k4=\EV:k5=\EW:\
:l6=blue:l7=red:l8=white:k6=\EP:k7=\EQ:k8=\ER:\
:es:hs:ts=\Ej\Ex5\Ex1\EY8%+ \Eo:fs=\Ek\Ey5:ds=\Ey1:
Refer to the ttycap command for more information about keyboard mappings and keymap entry structures.
Related Commands
Command
|
Description
|
keymap
|
Defines characteristics of a terminal emulation file.
|
show users
To display information about the active lines on the router, use the show users command in privileged EXEC mode.
show users [all] [lawful-intercept]
Syntax Description
all
|
(Optional) Specifies that all lines be displayed, regardless of whether anyone is using them.
|
lawful-intercept
|
(Optional) Displays lawful-intercept users.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.3(7)T
|
The lawful-intercept keyword was introduced.
|
12.2(33)SRB
|
The lawful-intercept keyword was integrated into Cisco IOS Release 12.2(33)SRB.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
This command displays the line number, connection name, idle time, hosts (including virtual access interfaces), and terminal location. An asterisk (*) indicates the current terminal session.
If the lawful-intercept keyword is issued, the names of all users who have access to a configured lawful intercept view will be displayed. To access the show users lawful-intercept command, you must be an authorized lawful-intercept-view user.
Examples
The following is sample output from the show users command:
Line User Host(s) Idle Location
* 2 vty 0 user1 idle 0 SERVICE1.CISCO.COM
The following is sample output identifying an active virtual access interface:
Line User Host(s) Idle Location
10 vty 0 Virtual-Access2 0 1212321
The following is sample output from the show users all command:
Line User Host(s) Idle Location
* 0 vty 0 user1 idle 0 SERVICE1.CISCO.COM
Table 37 describes the significant fields shown in the displays.
Table 37 show users Field Descriptions
Field
|
Description
|
Line
|
Contains three subfields:
• The first subfield (0 in the sample output) is the absolute line number.
• The second subfield (vty in the sample output) indicates the type of line. Possible values follow:
con—console
aux—auxiliary port
tty—asynchronous terminal port
vty—virtual terminal
• The third subfield (0 in the * sample output) indicates the relative line number within the type.
|
User
|
User using the line. If no user is listed in this field, no one is using the line.
|
Host(s)
|
Host to which the user is connected (outgoing connection). A value of idle means that there is no outgoing connection to a host.
|
Idle
|
Interval (in minutes) since the user has entered something.
|
Location
|
Either the hard-wired location for the line or, if there is an incoming connection, the host from which incoming connection came.
|
The following sample output from the show users lawful intercept command, shows three LI-View users on the system—li_admin, li-user1, and li-user2":
Router# show users lawful-intercept
Related Commands
Command
|
Description
|
line
|
Identifies a specific line for configuration and starts the line configuration command collection mode.
|
li-view
|
Creates a lawful intercept view.
|
show line
|
Displays the parameters of a terminal line.
|
username
|
Establishes a username-based authentication system.
|
show x25 pad
To display information about current open connections, including packet transmissions, X.3 parameter settings, and the current status of virtual circuits, use the show x25 pad command in EXEC mode.
show x25 pad
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Examples
The following is sample output from the show x25 pad command:
tty2, Incoming PAD connection
Total input: 61, control 6, bytes 129. Queued: 0 of 7 (0 bytes).
Total output: 65, control 6, bytes 696.
Flags: 1, State: 3, Last error: 1
ParamsIn: 1:1, 2:0, 3:2, 4:1, 5:1, 6:0, 7:21,
8:0, 9:0, 10:0, 11:14, 12:0, 13:0, 14:0, 15:1,
16:127, 17:21, 18:18, 19:0, 20:0, 21:0, 22:0,
ParamsOut: 1:1, 2:1, 3:2, 4:1, 5:0, 6:0, 7:4,
8:0, 9:0, 10:0, 11:14, 12:0, 13:0, 14:0, 15:0,
16:127, 17:21, 18:18, 19:0, 20:0, 21:0, 22:0,
LCI: 1, State: D1, Interface: Serial0
Started 0:11:10, last input 0:00:16, output 0:00:16
Connected to 313700540651
Window size input: 7, output: 7
Packet size input: 512, output: 512
PS: 1 PR: 5 ACK: 5 Remote PR: 1 RCNT: 0 RNR: FALSE
Retransmits: 0 Timer (secs): 0 Reassembly (bytes): 0
Held Fragments/Packets: 0/0
Bytes 696/129 Packets 65/61 Resets 0/0 RNRs 0/0 REJs 0/0 INTs 0/0
Table 38 describes the fields shown in the display.
Table 38 show x25 pad Field Descriptions
Field
|
Description
|
Total input/output
|
Number of packets received or sent for the connection.
|
control
|
Number of packets with Qbit set (X.29 control packets).
|
bytes
|
Number of bytes in each direction.
|
Queued
|
Number of unread packets waiting for the connection.
|
Waiting to send
|
Local data packet bit not sent (part of a line).
|
Flags, State, Last error
|
Displays data for detecting errors and tracing initialization status. Only useful to your Cisco-certified technical support personnel.
|
ParamsIn
|
Parameters read from the PAD at the start of the connection.
|
ParamsOut
|
Active X.3 parameters.
|
LCI, State, Interface
|
Status of the X.25 virtual circuit associated with the PAD connection. This is the same display that the show x25 vc command shows.
|
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. The # character must be entered.
|
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.
|
[...]
|
(Optional) Specifies that multiple entries can be made as follows:
• Up to six skip tests can be written on one command line.
• Multiple line numbers can be specified using the second no form of this command.
|
Defaults
No default behavior or values
Command Modes
Translate ruleset configuration
Command History
Release
|
Modification
|
12.3(8)T
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
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.
Table 39 Skip Keywords for Incoming PAD Connections
Keyword
|
Description
|
cud ASCII-string
|
Call user data (CUD) that occurs after the protocol identification (PID). For outgoing PAD connections, this is the optional, user-specified text included in the outgoing call request packet after the protocol identification bytes. The CUD is entered as an ASCII string.
|
dest-addr address
|
Destination X.121 address entered as a number from 0 to 15 digits long.
|
dest-addr-ext address
|
Network service access point (NSAP) destination address extension.
|
dlci number
|
Frame Relay data-link connection identifier (DLCI) of an Annex G service entered as a number from one to seven digits, although a size of two to four digits is more likely, or the NULL string if not received on an Annex G service.
|
interface type number
|
Interface to be used for the circuit, entered using standard Cisco IOS interface designations: Serial1/0:1, for example.
|
mac address
|
Connection-Mode Network Service (CMNS) service remote host MAC address entered as three hexadecimal numbers of four digits separated by a period, 0000.fc08.12ab, for example, or the NULL string if not received on a CMNS service.
|
packetsize size
|
X.25 maximum data packet sizes to request, entered as two numbers from the following choices: 16, 32, 64, 128, 256, 512, 1024, 2048, 4096.
|
pid byte-string
|
PID string specified in ASCII or hexadecimal. A hexadecimal PID must be prefixed by "0x." For example, 0x01000000 is the standard PAD PID. Although it is available for specifying a nonstandard Call PID, this parameter is not restricted to the common PID length and can be used to specify the entire user data field.
|
reversed flag
|
Flag to indicate whether a reverse charged Call is permitted. This flag applies to a switched virtual circuit (SVC) and is entered as a single character, Y or N, for yes or no.
|
source-addr address
|
Source X.121 address.
|
source-addr-ext address
|
NSAP source address extension.
|
windowsize size
|
X.25 window sizes to request, entered as two numbers in a range from 1 to 127.
|
xot-dest-addr address
|
Destination IP address of an X.25 over TCP (XOT) service entered in standard IP address dotted decimal notation (10.0.0.127, for example) or the NULL string if not received on an XOT service.
|
xot-source-addr address
|
Source IP address of an XOT service entered in standard IP address dotted decimal notation (10.0.0.127, for example) or the NULL string if not received on an XOT service.
|
Table 40 Skip Keywords for Incoming Telnet Connections
Keyword
|
Description
|
dest-addr address
|
Destination IP address entered in standard IP address dotted decimal notation: 10.0.0.127, for example.
|
dest-port port
|
Destination port entered as a decimal number from one to five digits long.
|
source-addr address
|
Source IP address entered in standard IP address dotted decimal notation: 10.0.0.127, for example.
|
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 10
! Match an incoming Telnet attempt destined for an IP addresses starting
! with 172.18., and a 5-digit port starting with 10 or 11
match 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 127
match 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 telnet
Related Commands
Command
|
Description
|
description (ruleset)
|
Adds a description about a translation ruleset.
|
match (ruleset)
|
Identifies a connection for processing by the translation ruleset.
|
options (ruleset)
|
Specifies protocol translation options in a translation ruleset.
|
set (ruleset)
|
Unconditionally sets one or more connection parameters to a fixed value for a translation ruleset.
|
show translate ruleset
|
Displays a summary of a specific or of all configured translation rulesets, behavioral parameters, and usage statistic.
|
substitute (ruleset)
|
Matches an available protocol and substitutes another in a translation ruleset.
|
test (ruleset)
|
Tests parameter values in a translation ruleset using regular expressions.
|
test translate
|
Displays a trace of protocol translation behavior for a connection attempt.
|
translate ruleset
|
Defines a unique name for a translation ruleset, specifies translated protocols, and enters translate ruleset configuration mode.
|
x25 pvc translate ruleset
|
Configures PVCs that are valid for protocol translation ruleset handling.
|
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
/default
|
(Optional) Makes a SLIP connection when a default address has been configured.
|
remote-ip-address
|
IP address of the client workstation or PC.
|
remote-name
|
Name of the client workstation or PC.
|
@tacacs-server
|
(Optional) IP address or IP host name of the TACACS server to which your TACACS authentication request is sent.
|
/routing
|
(Optional) Indicates that the remote system is a router. Line must be configured for asynchronous routing using SLIP encapsulation.
|
/compressed
|
(Optional) Indicates that IP header compression should be negotiated.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced in a release prior to Cisco IOS Release 10.0.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
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.
Your IP address is 192.168.7.28, MTU is 1524 bytes
The following example illustrates the prompts displayed and the response required when you use dynamic addressing to assign the SLIP address:
IP address or hostname? 192.168.6.15
Your IP address is 192.168.6.15, MTU is 1524 bytes
In 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.
Your IP address is 192.168.6.15, MTU is 1524 bytes
The 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 /compressed
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@server1
Interface IP address is 10.0.0.1, MTU is 1500 bytes
Header compression will match your system.
Related Commands
Command
|
Description
|
ip tcp header-compression
|
Enables TCP header compression.
|
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 [#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. The # character must be entered.
|
{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.
|
[...]
|
(Optional) Specifies that multiple entries can be made as follows:
• Up to six substitute statements can be written on one command line.
• Multiple line numbers can be specified using the second no form of this command.
|
Defaults
No default behavior or values
Command Modes
Translate ruleset configuration
Command History
Release
|
Modification
|
12.3(8)T
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
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.
Cisco regular expressions are described in Appendix A, "Regular Expressions," in the Cisco IOS Terminal Services Configuration Guide.
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.
Table 41 Substitute Connection Parameter Keywords
Parameter
|
Description
|
Incoming PAD
|
Outgoing Telnet
|
Outgoing PAD
|
Incoming Telnet
|
authorize-method ASCII-string
|
Connection authorization method to use that must match one of a fixed set of values.
|
X
|
—
|
—
|
X
|
authorize-tag ASCII-string
|
Connection authorization identity to supply, entered as an ASCII string.
|
X
|
—
|
—
|
X
|
binary flag
|
Flag that specifies whether 8-bit binary data is required, entered as one of the following characters to specify binary mode: Y, y, 1-9, T, t.
|
—
|
X
|
—
|
X
|
cud ASCII-string
|
Call user data (CUD) that occurs after the protocol identification (PID). For X.29 service, this is the optional, user-specified text included in the command to place a call.
|
X
|
—
|
X
|
—
|
dest-addr address
|
Destination IP (Telnet) or X.121 (PAD) address.
|
X
|
X
|
X
|
X
|
dest-addr-ext address
|
Network service access point (NSAP) destination address extension.
|
X
|
—
|
X
|
—
|
dest-port port
|
Destination port entered as a decimal number from one to five digits long.
|
—
|
X
|
—
|
X
|
dlci number
|
Frame Relay data-link connection identifier (DLCI) of an Annex G service entered as a number from one to seven digits in length, although a size of two to four digits is more likely, or the NULL string if not received on an Annex G service.
|
X
|
—
|
X
|
—
|
eor specification
|
A character set defining the End-of-Record (EOR) string for the protocol translation session, entered as an ASCII or hexadecimal specification from one to four bytes in length, aaa or 0x19, as examples.
|
—
|
X
|
—
|
X
|
eor-insert flag
|
Flag specifying that the EOR character set should be inserted for PAD data being forwarded to a Telnet session, and entered as a single character. Use one of the following characters to specify EOR insertion: Y, y, 1-9, T, t.
|
—
|
X
|
—
|
X
|
hostname address
|
Destination host name for Domain Name System (DNS) resolution entered as an ASCII string.
|
—
|
X
|
—
|
—
|
idle seconds
|
Number of seconds the PAD connection can be idle before being cleared.
|
X
|
—
|
X
|
—
|
interface type number
|
Interface to be used for the circuit, entered using standard Cisco IOS interface designations; Serial1/0:1, for example.
|
X
|
—
|
X
|
—
|
keepalive-period seconds
|
A number that indicates the number of seconds between TCP keepalives for the X.25 over TCP (XOT) connection.
TCP keepalive information applies only when a ruleset is configured to match an XOT destination address. Example:
match dest-addr ^5555.$ xot-dest-addr 5.5.5.2
|
X
|
—
|
X
|
—
|
keepalive-tries number
|
A number that indicates the number of TCP keepalives to send before the XOT connection is declared dead.
TCP keepalive information applies only when a ruleset is configured to match an XOT destination address. Example:
match dest-addr ^5555.$ xot-dest-addr 5.5.5.2
|
X
|
—
|
X
|
—
|
local flag
|
Flag specifying that Telnet control sequences should be forwarded, not processed, and entered as a single character. Use one of the following characters to specify local mode: Y, y, 1-9, T, t.
|
—
|
X
|
—
|
X
|
mac address
|
Connection-Mode Network Service (CMNS) service remote host MAC address entered as three hexadecimal numbers of four digits separated by a period, (0000.fc08.12ab, for example) or the NULL string if not received on a CMNS service.
|
X
|
—
|
X
|
—
|
no-reset
|
Suppress a PVC Reset packet at session startup.
|
X
|
—
|
X
|
—
|
packetsize size
|
X.25 maximum data packet sizes to request, entered as two numbers from the following choices: 16, 32, 64, 128, 256, 512, 1024, 2048, 4096.
|
X
|
—
|
X
|
—
|
pid byte-string
|
PID string specified in ASCII or hexadecimal. A hexadecimal PID must be prefixed by "0x." For example, 0x01000000 is the standard PAD PID. Although it is available for specifying a nonstandard Call PID, this parameter is not restricted to the common PID length and can be used to specify the entire user data field.
|
X
|
—
|
X
|
—
|
printer flag
|
Printer access mode. Flag specifying that the outgoing connection should be brought up before the incoming connection is confirmed. Use one of the following characters to specify printer mode: Y, y, 1-9, T, t.
An unsuccessful outgoing connection attempt results in the incoming connection to the ruleset being refused, rather than being accepted and then closed, which is the default behavior. Note that using this keyword will force the ruleset quiet keyword to be applied to the translation.
|
X
|
—
|
—
|
X
|
profile name
|
Named PAD profile to use.
|
X
|
—
|
X
|
—
|
pvc circuit-number
|
Permanent virtual circuit (PVC) entered as a number from 1 to 4095, or the null string if not a PVC.
|
—
|
—
|
X
|
—
|
reverse
|
Request reverse charging.
|
—
|
—
|
X
|
—
|
reversed flag
|
Flag to indicate whether a reverse charged Call is permitted. This flag applies to a switched virtual circuit (SVC) and is entered as a single character, Y or N, for yes or no.
|
X
|
—
|
—
|
—
|
rotor
|
Modifies the behavior of the host-name keyword by allowing one of the IP addresses defined by the ip host configuration command to be chosen randomly. If one address fails, another will be tried until a connection is made or all address choices are exhausted.
|
—
|
X
|
—
|
—
|
source-addr address
|
Source X.121 address.
|
X
|
—
|
X
|
X
|
source-addr-ext address
|
NSAP source address extension.
|
X
|
—
|
X
|
—
|
source-ifc type number
|
Interface from which to take the source IP address, entered using standard Cisco IOS interface designations: Loopback0, for example.
|
—
|
X
|
X
|
—
|
stream flag
|
Flag that specifies whether Telnet negotiation should be sent or accepted, entered as one of the following characters to specify stream mode: Y, y, 1-9, T, t.
|
—
|
X
|
—
|
X
|
swap flag
|
X.29 role reversal. Flag that indicates the PAD connection should not initiate X.29 commands when first connected. Use one of the following characters to swap behavior: Y, y, 1-9, T, t.
This parameter enables incoming and outgoing PAD connections to be swapped so that a protocol translation is treated like a PAD when it accepts a call. By default, the protocol translation functions like a PAD for calls that it initiates, and like an X.25 host for calls it accepts.
|
X
|
—
|
X
|
—
|
use-map map
|
Use the map defined for PAD service.
|
—
|
—
|
X
|
—
|
windowsize size
|
X.25 window sizes to request, entered as two numbers in a range from 1 to 127.
|
X
|
—
|
X
|
—
|
xot-dest-addr address
|
Destination IP address of an X.25 over TCP (XOT) service entered in standard IP address dotted decimal notation (10.0.0.127, for example) or the NULL string if not received on an XOT service.
|
X
|
—
|
X
|
—
|
xot-source-addr address
|
Source IP address of an XOT service entered in standard IP address dotted decimal notation (10.0.0.127, for example) or the NULL string if not received on an XOT service.
|
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 printer Y telnet binary Y
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
substitute telnet dest-port ^.(...). into pad source-addr
Related Commands
Command
|
Description
|
description (ruleset)
|
Adds a description about a translation ruleset.
|
match (ruleset)
|
Identifies a connection for processing by the translation ruleset.
|
options (ruleset)
|
Specifies protocol translation options in a translation ruleset.
|
set (ruleset)
|
Unconditionally sets one or more connection parameters to a fixed value for a translation ruleset.
|
show translate ruleset
|
Displays a summary of a specific or of all configured translation rulesets, behavioral parameters, and usage statistic.
|
skip (ruleset)
|
Identifies a connection for omission by the translation ruleset.
|
test (ruleset)
|
Tests parameter values in a translation ruleset using regular expressions.
|
test translate
|
Displays a trace of protocol translation behavior for a connection attempt.
|
translate ruleset
|
Defines a unique name for a translation ruleset, specifies translated protocols, and enters translate ruleset configuration mode.
|
x25 pvc translate ruleset
|
Configures PVCs that are valid for protocol translation ruleset handling.
|
telnet
To log in to a host that supports Telnet, use the telnet command in user EXEC or privileged EXEC mode.
telnet host [port] [keyword]
Syntax Description
host
|
A hostname or an IP address.
|
port
|
(Optional) A decimal TCP port number, or port name; the default is the Telnet router port (decimal 23) on the host.
|
keyword
|
(Optional) One of the keywords listed in Table 42.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(21)ST
|
The /ipv4 and /ipv6 keywords were added.
|
12.1
|
The /quiet keyword was added.
|
12.2(2)T
|
The /ipv4 and /ipv6 keywords were added.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(25)SG
|
This command was integrated into Cisco IOS Release 12.2(25)SG.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
Usage Guidelines
Table 42 lists the optional telnet command keywords.
Table 42 telnet Keyword Options
Option
|
Description
|
/debug
|
Enables Telnet debugging mode.
|
/encrypt kerberos
|
Enables an encrypted Telnet session. This keyword is available only if you have the Kerberized Telnet subsystem.
If you authenticate using Kerberos Credentials, the use of this keyword initiates an encryption negotiation with the remote server. If the encryption negotiation fails, the Telnet connection will be reset. If the encryption negotiation is successful, the Telnet connection will be established, and the Telnet session will continue in encrypted mode (all Telnet traffic for the session will be encrypted).
|
/ipv4
|
Specifies version 4 of the IP protocol. If a version of the IP protocol is not specified in a network that supports both the IPv4 and IPv6 protocol stacks, IPv6 is attempted first and is followed by IPv4.
|
/ipv6
|
Specifies version 6 of the IP protocol. If a version of the IP protocol is not specified in a network that supports both the IPv4 and IPv6 protocol stacks, IPv6 is attempted first and is followed by IPv4.
|
/line
|
Enables Telnet line mode. In this mode, the Cisco IOS software sends no data to the host until you press the Enter key. You can edit the line using the standard Cisco IOS software command-editing characters. The /line keyword is a local switch; the remote router is not notified of the mode change.
|
/noecho
|
Disables local echo.
|
/quiet
|
Prevents onscreen display of all messages from the Cisco IOS software.
|
/route: path
|
Specifies loose source routing. The path argument is a list of hostnames or IP addresses that specify network nodes and ends with the final destination.
|
/source-interface
|
Specifies the source interface.
|
/stream
|
Turns on stream processing, which enables a raw TCP stream with no Telnet control sequences. A stream connection does not process Telnet options and can be appropriate for connections to ports running UNIX-to-UNIX Copy Program (UUCP) and other non-Telnet protocols.
|
port-number
|
Port number.
|
bgp
|
Border Gateway Protocol.
|
chargen
|
Character generator.
|
cmd rcmd
|
Remote commands.
|
daytime
|
Daytime.
|
discard
|
Discard.
|
domain
|
Domain Name Service.
|
echo
|
Echo.
|
exec
|
EXEC.
|
finger
|
Finger.
|
ftp
|
File Transfer Protocol.
|
ftp-data
|
FTP data connections (used infrequently).
|
gopher
|
Gopher.
|
hostname
|
Hostname server.
|
ident
|
Ident Protocol.
|
irc
|
Internet Relay Chat.
|
klogin
|
Kerberos login.
|
kshell
|
Kerberos shell.
|
login
|
Login (rlogin).
|
lpd
|
Printer service.
|
nntp
|
Network News Transport Protocol.
|
pim-auto-rp
|
Protocol Independent Multicast (PIM) auto-rendezvous point (RP).
|
node
|
Connect to a specific Local-Area Transport (LAT) node.
|
pop2
|
Post Office Protocol v2.
|
pop3
|
Post Office Protocol v3.
|
port
|
Destination local-area transport (LAT) port name.
|
smtp
|
Simple Mail Transfer Protocol.
|
sunrpc
|
Sun Remote Procedure Call.
|
syslog
|
Syslog.
|
tacacs
|
Specifies TACACS security.
|
talk
|
Talk (517).
|
telnet
|
Telnet (23).
|
time
|
Time (37).
|
uucp
|
UNIX-to-UNIX Copy Program (540).
|
whois
|
Nickname (43).
|
www
|
World Wide Web (HTTP, 80).
|
With the Cisco IOS implementation of TCP/IP, you are not required to enter the connect or telnet command to establish a terminal connection. You can enter only the learned hostname—as long as the following conditions are met:
•
The hostname is different from a command word for the router.
•
The preferred transport protocol is set to telnet.
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 hostname, 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 and Shift keys and the 6 key). 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
|
|
Purpose
|
Ctrl-^ b
|
Break
|
Ctrl-^ c
|
Interrupt Process (IP and IPv6)
|
Ctrl-^ h
|
Erase Character (EC)
|
Ctrl-^ o
|
Abort Output (AO)
|
Ctrl-^ t
|
Are You There? (AYT)
|
Ctrl-^ u
|
Erase Line (EL)
|
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:
[Special telnet escape help]
You can have several concurrent Telnet sessions open and switch among 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:
•
close
•
disconnect
•
exit
•
logout
•
quit
Examples
The following example establishes an encrypted Telnet session from a router to a remote host named host1:
router> telnet host1 /encrypt kerberos
The following example routes packets from the source system host1 to example.com, then to 10.1.0.11, and finally back to host1:
router> telnet host1 /route:example.com 10.1.0.11 host1
The following example connects to a host with the logical name host1:
The following example suppresses all onscreen messages from the Cisco IOS software during login and logout:
router> telnet host2 /quiet
The following example shows the limited messages displayed when connection is made using the optional /quiet keyword:
Welcome to OpenVMS VAX version V6.1 on node CRAW
Last interactive login on Tuesday, 15-DEC-1998 11:01
Last non-interactive login on Sunday, 3-JAN-1999 22:32
User2 logged out at 16-FEB-2000 09:38:27.85
Related Commands
Command
|
Description
|
connect
|
Logs in to a host that supports Telnet, rlogin, or LAT.
|
kerberos clients mandatory
|
Causes the rsh, rcp, rlogin, and telnet commands to fail if they cannot negotiate the Kerberos Protocol with the remote server.
|
name connection
|
Assigns a logical name to a connection.
|
rlogin
|
Logs in to a UNIX host using rlogin.
|
show hosts
|
Displays the default domain name, the style of name lookup service, a list of name server hosts, and the cached list of hostnames and addresses.
|
show tcp
|
Displays the status of TCP connections.
|
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
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
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:
•
Several user Telnet programs send an Interrupt-Process command, but cannot send a Telnet BREAK signal.
•
Some Telnet programs implement a BREAK signal that sends an Interrupt-Process command.
•
Some EIA/TIA-232 hardware devices use a hardware BREAK signal for various purposes.
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.
location high-speed modem
Related Commands
Command
|
Description
|
connect
|
Logs in to a host that supports Telnet, rlogin, or LAT.
|
telnet
|
Logs in to a host that supports Telnet.
|
telnet transparent
|
Configures 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).
|
terminal telnet break-on-ip
|
Causes the access server to generate a hardware Break signal on the EIA/TIA-232 line, which is associated with a reverse Telnet connection, for the current line and sessions.
|
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
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
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:
telnet refuse-negotiations
Related Commands