Feedback
Table Of Contents
show extended channel tn3270-server
show extended channel tn3270-server client-ip-address
show extended channel tn3270-server client-name
show extended channel tn3270-server dlur
show extended channel tn3270-server dlurlink
show extended channel tn3270-server nailed-domain
show extended channel tn3270-server nailed-ip
show extended channel tn3270-server nailed-name
show extended channel tn3270-server pu
show extended channel tn3270-server pu lu
show extended channel tn3270-server response-time application
show extended channel tn3270-server response-time global
show extended channel tn3270-server response-time link
show extended channel tn3270-server response-time listen-point
show extended channel tn3270-server response-time subnet
show extended channel tn3270-server security
TN3270 Server Commands
Use the commands in this chapter to configure and monitor the Cisco Mainframe Channel Connection (CMCC) products, which include the Channel Interface Processor (CIP) and the Channel Port Adapter (CPA). For hardware technical descriptions and for information about installing the router interfaces, refer to the hardware installation and maintenance publication for your particular product.
Note
Unless otherwise specified, all commands in this chapter are supported on the Cisco 7000 with RSP7000, Cisco 7500 and the Cisco 7200 series routers.
For interface configuration information and examples, refer to the "Configuring the TN3270 Server" chapter of the Cisco IOS Bridging and IBM Networking Configuration Guide.
For a conversion table of the modular products and Cisco 7000 family processors, refer to the "Platform Support" appendix of the Cisco IOS Configuration Fundamentals Command Reference.
allocate lu
To assign logical units (LUs) to a pool, use the allocate lu listen-point PU configuration command. To remove LUs assigned to a pool, use the no form of this command.
allocate lu lu-address pool poolname clusters count
no allocate lu lu-address pool poolname clusters count
Syntax Description
Defaults
No default behavior or values.
Command Modes
Listen-point PU configuration
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
The following guidelines apply to the allocate lu command:
•
•
•
•
Examples
In the following example, the starting LOCADDR is 10. Each cluster has 5 LOCADDRs, therefore 25 LOCADDRs (10 through 34) are allocated to the pool name LOT1.
interface channel 0/2tn3270-serverpool LOT1 cluster layout 4s1plisten-point 10.20.30.40pu PU1allocate lu 10 pool LOT1 clusters 5As a result of this configuration, the following LOCADDRs are created in each cluster:
•
–
–
–
–
–
•
–
–
–
–
–
All of the LUs in these clusters are allocated to pool LOT1.
Related Commands
certificate reload
To configure SSL Encryption Support enabled to read the profile security certificate from the file specified in the servercert command, use the certificate reload profile configuration command.
certificate reload
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Profile configuration
Command History
Usage Guidelines
There is not a no form for this command.
The TN3270 server must be configured for security.
Examples
The following example configures the TN3270 server with SSL Encryption Support to read the profile security certificate from the file specified in the servercert command:
certificate reloadRelated Commands
servercert
Specifies the location of the TN3270 server's security certificate in the Flash memory.
client ip
To add an IP subnet to a client subnet response-time group, use the client ip response-time configuration command. To remove an IP subnet from a client subnet response-time group, use the no form of this command.
client ip ip-address [ip-mask]
no client ip ip-address [ip-mask]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Response-time configuration
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Examples
Following is an example of the client ip command:
tn3270-serverresponse-time group acctgclient ip 10.1.2.3 255.0.0.0Related Commands
Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application
Displays information about application response-time client groups.
Displays information about the global response-time client group.
Displays information about host link response-time client groups.
show extended channel tn3270-server response-time listen-point
Displays information about listen point response-time client groups.
Displays information about Subnet response-time client groups.
tn3270-server
Starts the TN3270 server on a CMCC adapter and enters TN3270 server configuration mode.
client ip lu
To define a specific LU or range of LUs to a client at the IP address or subnet, use the client ip lu TN3270 PU configuration mode command. To cancel this definition, use the no form of this command.
client [printer] ip ip-address [ip-mask] lu first-locaddr [last-locaddr]
no client [printer] ip ip-address [ip-mask] lu first-locaddr [last-locaddr]
Syntax Description
Defaults
No LUs are nailed. They are all available to any client.
Command Modes
TN3270 PU configuration mode
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. Multiple statements can be configured for one IP address or nail type either on one PU or multiple PUs. But each LU can only appear in one client statement.
A client with a nailed IP address can request one of the nailed LUs via the TN3270 device name. If the requested LU is not available then the connection is rejected.
A client with a nailed IP address cannot request an LU outside the range of nailed LUs for its type (screen or printer).
A client with a nonnailed IP address cannot request an LU that is configured as nailed.
The command will be rejected if some of the locaddrs are already nailed. If the locaddrs are currently in use by other remote clients, the nailing statement will take effect only when the locaddr is made available.
To cancel the definition, the no client form of the command must be entered exactly as the client command was originally configured. If a range of locaddrs was specified, to cancel this definition the whole range of locaddrs must be specified. There is no way to cancel only one locaddr if a whole range of locaddrs was configured.
Examples
In the following example, locaddrs 1 to 50 are reserved for remote devices in the 171.69.176.0 subnet:
interface channel 2/2tn3270-serverpu BAGE4client ip 171.69.176.28 255.255.255.0 lu 1 50In the following example, locaddrs 1 to 40 are reserved for screen devices in the 171.69.176.0 subnet, while 41 to 50 are reserved for printers in that subnet:
interface channel 2/2tn3270-serverpu BAGE4client ip 171.69.176.28 255.255.255.0 lu 1 40client printer ip 171.69.176.28 255.255.255.0 lu 41 50In the following example, there is an attempt to cancel a definition but this is rejected because it does not specify the full range of locaddrs and the second attempt fails to specify the correct nail type:
interface channel 2/2tn3270-serverpu BAGE4client printer ip 171.69.176.50 255.255.255.0 lu 1 100no client printer ip 171.69.176.50 255.255.255.0 lu 1%Invalid LU range specifiedno client ip 171.69.176.50 255.255.255.0 lu 1 100%client ip 171.69.176.50 nail type not matched with configured nail type printerRelated Commands
Creates a PU entity that has no direct link to a host and enters DLUR PU configuration mode.
client ip pool
To nail clients to pools, use the client ip pool listen-point configuration command. To remove clients from pools, use the no form of this command.
client ip ip-address [ip-mask] pool poolname
no client ip ip-address [ip-mask] pool poolname
Syntax Description
Defaults
No default behavior or values.
Command Modes
Listen-point configuration
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
If the pool is configured while LUs are in use, existing clients are allowed to complete their sessions. A pool name can be identical to an LU name. When assigning an LU, the TN3270 server searches the LU name space first for specific requests, such as connections that specify a device name on CONNECT or LU name in the terminal type negotiation. The request is assumed to be directed to the specific LU rather than to the pool. Make sure the name spaces do not clash.
Examples
The following is an example of the client ip pool command that nails the client at IP address 10.1.2.3 with an IP mask of 255.255.255.0 to the pool named OMAHA:
tn3270-serverpool OMAHA cluster layout 10s1plisten-point 172.18.4.18client ip 10.1.2.3 255.255.255.0 pool OMAHARelated Commands
client lu maximum
To limit the number of LU sessions that can be established for each client IP address or IP subnet address, use the client lu maximum TN3270 server configuration command. To remove a single LU limit associated with a particular IP address, use the no form of this command.
client [ip [ip-mask]] lu maximum number
no client [ip [ip-mask]]
Syntax Description
Defaults
The default is that there is no limit on the number of concurrent sessions from one client IP address.
The default value for the ip-mask argument is 255.255.255.255.
In the no form of this command, the default value for the number argument is 65535.
Command Modes
TN3270 server configuration
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. An instance of the client (lu limit) command on a given tn3270-server is uniquely identified by the ip-mask and the logical AND of the ip-address with that mask. For example, if the command is entered as the following:
client 10.1.1.62 255.255.255.192 lu maximum 2Then it will be stored (and subsequently displayed by write term) as:
client 10.1.1.0 255.255.255.192 lu maximum 2The maximum specified on the command can be changed simply by reissuing the command with the new value. It is not necessary to remove the command first.
When you use the no client command, only the corresponding client lu maximum statement is removed, as identified by the IP address and IP address mask combination. You cannot use no client to specify an unlimited number of LU sessions. The lu number keyword is optional in the no form of the command.
For example, if a service bureau has 8000 clients and each client IP address is limited to four LU sessions, you will never need more than 32000 concurrent LU definitions even when the service is running at 100 percent capacity.
Examples
The following example limits all clients to a maximum of two LU sessions:
client lu maximum 2The following example limits a client at IP address 10.1.1.28 to a maximum of three LU sessions:
client 10.1.1.28 lu maximum 3The LU limit can be applied to different subnets as shown in the following example. The most exact match to the client IP address is chosen. Clients with IP addresses that reside in the subnet 10.1.1.64 (those with IP addresses in the range of 10.1.1.64 through 10.1.1.127) are limited to a maximum of 5 LU sessions while other clients with IP addresses in the subnet 10.1.1.0 are limited to a maximum of 4 LU sessions.
client 10.1.1.0 255.255.255.0 lu maximum 4client 10.1.1.64 255.255.255.192 lu maximum 5The following example prevents an LU session for the client at IP address 10.1.1.28:
client 10.1.1.28 lu maximum 0Related Commands
Limits the number of LU control blocks that will be allocated for TN3270 server use.
client pool
To nail clients to pools, use the client pool listen-point configuration command. To remove clients from pools, use the no form of this command.
client {[ip ip-address [ip-mask]] | [name DNS-name [DNS-domain-identifier]] | [domain-name DNS-domain] | [domain-id DNS-domain-identifier]} pool poolname
no client {[ip ip-address [ip-mask]] | [name DNS-name [DNS-domain-identifier]] | [domain-name DNS-domain] | [domain-id DNS-domain-identifier]} pool poolname
Syntax Description
Defaults
No default behavior or values.
Command Modes
Listen-point configuration
Command History
Usage Guidelines
If the pool is configured while LUs are in use, existing clients are allowed to complete their sessions. A pool name can be identical to an LU name. When assigning an LU, the TN3270 server searches the LU name space first for specific requests, such as connections that specify a device name on CONNECT or LU name in the terminal type negotiation. The request is assumed to be directed to the specific LU rather than to the pool. Make sure the LU names do not conflict.
Examples
Nailing Clients to Pools by IP Address
The following is an example of the client pool command with the ip keyword configured. The command nails the client at IP address 10.1.2.3 with an IP mask of 255.255.255.0 to the pool named OMAHA:
tn3270-serverpool OMAHA cluster layout 10s1plisten-point 172.18.4.18client ip 10.1.2.3 255.255.255.0 pool OMAHANailing Clients to Pools by Device Name
The following is an example of the client pool command with the name keyword configured. The command nails the client at device name george-isdn29.cisco.com to the pool named GENERAL:
tn3270-serverpool GENERAL cluster layout 4s1plisten-point 172.18.5.168pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001allocate lu 1 pool GENERAL clusters 1client name george-isdn29.cisco.com pool GENERALNailing Clients to Pools by Device Name using a Domain ID
The following is an example of the client pool command with the name keyword and the optional DNS-domain-identifier argument configured. The command nails the client at device name lucy-isdn49.cisco.com to the pool named GENERAL:
tn3270-serverdomain-id 23 .cisco.compool GENERAL cluster layout 4s1plisten-point 172.18.5.168pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001allocate lu 1 pool GENERAL clusters 1client name lucy-isdn49 23 pool GENERALNailing Clients to Pools by Domain Name
The following is an example of the client pool command with the domain-name keyword configured. The command nails any client at domain name .cisco.com to the pool named GENERAL:
tn3270-serverpool GENERAL cluster layout 4s1plisten-point 172.18.5.168pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001allocate lu 1 pool GENERAL clusters 1client domain-name .cisco.com pool GENERALNailing Clients to Pools by Domain Name Using a Domain ID
The following is an example of the client pool command with the domain-id keyword configured. The command nails any client at domain name cisco.com to the pool named GENERAL:
tn3270-serverdomain-id 23 .cisco.compool GENERAL cluster layout 4s1plisten-point 172.18.5.168pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001allocate lu 1 pool GENERAL clusters 1client domain-id 23 pool GENERALRelated Commands
default-profile
To specify the name of the profile to be applied as a default to all the listen points, use the default-profile security command. To disable the default profile specification, use the no form of this command.
default-profile profilename
no default-profile profilename
Syntax Description
Defaults
No default profile.
Command Modes
Security configuration
Command History
Usage Guidelines
If this command is configured, this profile name and all of its attributes will be associated with all listen points that do not specify an individual profile with the sec-profile command.
Profile names cannot be duplicated.
Entering the no form of this command removes the default specification and any listen points that do not have the sec-profile command specified will revert to a non-secure mode.
This command has no retroactive effect. If a listen point is specified using the listen-point command, and the sec-profile command was already configured for that listen point then all client connections to that listen point will be secure.
If a listen point is specified using the listen-point command, and the default-profile command is not configured, then all client connections to that listen point will not be secure. However, if the default-profile command is later configured, then all now connections to that listen point will be secure using the specified default-profile. This will not affect the non-secure connections.
The following example specifies DOMESTIC as the default profile name for all clients connecting to listen point 10.10.10.1 until the default-profile LAM command is configured. Once the default-profile LAM command is configured, all new client connections will use LAM as the default profile.
tn3270securityprofile NOSECURITY nonedefault-profile DOMESTICpu DIRECT 012ABCDE tok 0 04default-profile LAMlisten-point 10.10.10.1Related Commands
disable (TN3270)
To turn off security in the TN3270 server, use the disable (TN3270) security configuration command.
disable
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Security configuration
Command History
Usage Guidelines
Configuring the disable (TN3270) command does not terminate any active secure or non-secure connections. This command specifies that all new connections established with the TN3270 server will be non-secure. If a client initiates a change cipher specification for an existing secure connection then the TN3270 server will process the request.
There is not a no form for this command. The enable command is equivalent to the no form of this command.
Examples
The following example turns off security in the TN3270 server so that all new connections established with the TN3270 server will be non-secure:
disableRelated Commands
dlur
To enable the Systems Network Architecture (SNA) session switch function on the CMCC adapter and enter dependent logical unit requester (DLUR) configuration mode, use the dlur TN3270 server configuration command. To disable the SNA session switch function and discard all parameter values associated with the SNA session switch, use the no form of this command.
dlur [fq-cpname fq-dlusname]
no dlur
Syntax Description
Defaults
No DLUR function is enabled.
Command Modes
TN3270 server configuration
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. If the SNA session switch function is already enabled, the dlur command with no arguments puts you in DLUR configuration mode. The session switch function implements an End Node DLUR.
Several parameters in the DLUR configuration mode consist of fully qualified names, as defined by the APPN architecture. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to 8 characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NET ID and is shared between entities in the same logical network.
The no dlur command hierarchically deletes all resources defined beneath it.
Examples
The following example performs two functions: it enters DLUR configuration mode; and it enables the DLUR function and defines the LU name for the DLUR as SYD.TN3020 and the primary choice for DLUS as SYD.VMG. Note that the NET ID portion of both names is the same:
dlur SYD.TN3020 SYD.VMGRelated Commands
dlus-backup
To specify a backup DLUS for the DLUR function, use the dlus-backup DLUR configuration command. To remove a backup DLUS name, use the no form of this command.
dlus-backup dlusname2
no dlus-backup
Syntax Description
Defaults
No backup DLUS is specified.
Command Modes
DLUR configuration
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. Only one backup DLUS can be specified per CMCC adapter. If the backup DLUS specified in the dlus-backup command is in use when a no dlus-backup command is issued, the connection is not torn down.
Several parameters in the DLUR configuration mode consist of fully qualified names, as defined by the APPN architecture. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to 8 characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NET ID and is shared between entities in the same logical network.
Examples
The following example specifies SYD.VMX as the backup DLUS:
dlus-backup SYD.VMXRelated Commands
domain-id
To specify a domain name suffix that the TN3270 server appends to a configured machine name to form a fully qualified name when configuring inverse DNS nailing, use the domain-id TN3270 server configuration command. To disable this specification, use the no form of this command.
domain-id DNS-domain-identifier DNS-domain
no domain-id DNS-domain-identifier DNS-domain
Syntax Description
Defaults
No default behavior or values.
Command Modes
TN3270 server configuration
Command History
Usage Guidelines
The user can configure up to 255 domain names, one per statement.
This command must be configured you configure the client pool command with either the domain-id keyword or the name keyword and the optional DNS-domain-identifier argument.
Examples
In the following example, the domain-id command specifies 23 as the DNS-domain-identifier for the .cisco.com domain name. All clients nailed to the pool GENERAL will use .cisco.com as the domain name suffix. For example, the client name ally-isdn1 will become ally-isdn1.cisco.com.
tn3270-serverdomain-id 23 .cisco.compool GENERAL cluster layout 4s1plisten-point 172.18.5.168pu T240CA 91922363 token-adapter 31 12 rmac 4000.4000.0001allocate lu 1 pool GENERAL clusters 1client name ally-isdn1 23 pool GENERALRelated Commands
enable (TN3270)
To turn on security in the TN3270 server, use the enable (TN3270) security configuration mode command.
enable
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Security configuration
Command History
Usage Guidelines
There is not a no form for this command.
If the security command has been disabled, then issuing this command does not affect existing connections.
This command is not displayed in the show running configuration command output because the security functionality is enabled by default.
Examples
The following example turns on security in the TN3270 server:
enableRelated Commands
security (TN3270)
Enables security on the TN3270 server.
disable (TN3270)
Turns off security in the TN3270 server.
encryptorder
To specify the security encryption algorithm for the SSL Encryption Support, use the encryptorder profile configuration command.
encryptorder [DES] [3DES] [RC4] [RC2] [RC5]
Syntax Description
Defaults
The default encryption order is RC4, RC2, RC5, DES, 3DES for domestic software. The default encryption order is RC4, RC2, DES for exportable software.
Command Modes
Profile configuration
Command History
Usage Guidelines
There is not a no form for this command.
These algorithms may be entered in any order, but can be specified only once per encryptorder command.
Exportable versions of software cannot accept the 3DES or RC5 encryption algorithms.
Examples
The following example specifies RC4, DES, and RC2 as the encryption algorithms:
tn3270securityprofile DOMESTIC SSLencryptorder RC4 DES RC2generic-pool
To specify whether or not leftover LUs will be made available to TN3270 sessions that do not request a specific LU or LU pool through TN3270E, use the generic-pool TN3270 server configuration command. To selectively remove the permit or deny condition of generic pool use, use the no form of this command.
generic-pool {permit | deny}
no generic-pool
Syntax Description
Defaults
In TN3270 server configuration mode, generic pool use is permitted.
In PU configuration mode, the default is the value currently configured in TN3270 server configuration mode.
Command Modes
TN3270 server configuration—The generic-pool command at this level applies to all PUs supported by the TN3270 server.
Listen-point configuration—The generic-pool command at this level applies to all PUs defined at the listen point.
Listen-point PU configuration—The generic-pool command at this level applies only to the specified PU.
DLUR PU configuration—The generic-pool command at this level applies to all PUs defined under DLUR configuration mode.
PU configuration—The generic-pool command at this level applies only to the specified PU.
Command History
Usage Guidelines
This command is valid only on the virtual channel interface.
A leftover LU is defined as one for which all of the following conditions are true:
•
•
All LUs in the generic pool are, by definition, DDDLU capable.
Values entered for generic-pool in TN3270 server configuration mode apply to all PUs for that TN3270 server but can be changed in PU configuration mode.
In PU configuration mode, a no generic-pool command will restore the generic-pool value entered in TN3270 command mode.
In TN3270 server configuration mode, the no generic-pool command reverts to the default, which permits generic pool use.
The command takes effect immediately. If generic-pool deny is specified on a PU, no further dynamic connections to it will be allowed. Existing sessions are unaffected, but as they terminate the LUs will not become available for dynamic connections.
Similarly, if generic-pool permit is specified, any inactive LUs are immediately available for dynamic connections. Moreover, any active LUs that were dynamic previously (before generic-pool deny was issued) return to being dynamic.
Examples
The following example permits generic LU pool use:
generic-pool permitRelated Commands
idle-time
To specify how many seconds of LU inactivity, from both host and client, before the TN3270 session is disconnected, use the idle-time TN3270 server configuration command. To cancel the idle time period and return to the default, use the no form of this command.
idle-time seconds
no idle-time
Syntax Description
seconds
Idle time in seconds, from 0 to 65535. A value of 0 means the session is never disconnected.
Defaults
The default in TN3270 server configuration mode is that the session is never disconnected (0).
The default in PU configuration mode is the value currently configured in TN3270 server configuration mode.
Command Modes
TN3270 server configuration—The idle-time command at this level applies to all PUs supported by the TN3270 server.
Listen-point configuration—The idle-time command at this level applies to all PUs defined at the listen point.
Listen-point PU configuration—The idle-time command at this level applies only to the specified PU.
DLUR PU configuration—The idle-time command at this level applies to all PUs defined under DLUR configuration mode.
PU configuration—The idle-time command at this level applies only to the specified PU.
Command History
Usage Guidelines
The idle-time command is valid only on the virtual channel interface, and can be entered in either TN3270 server configuration mode or PU configuration mode. A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in PU configuration mode.
A no idle-time command entered in PU configuration mode will restore the idle-time value entered in TN3270 command mode.
The idle-time command affects currently active and future TN3270 sessions. For example, if the idle-time value is reduced from 900 seconds to 600 seconds, sessions that have been idle for between 600 and 900 seconds are immediately disconnected.
Note
Examples
The following command sets an idle-time disconnect value of 10 minutes:
idle-time 600The following command entered in TN3270 server configuration mode sets the default idle-time disconnect value to 0, or never disconnect:
no idle-timeRelated Commands
ip precedence (TN3270)
To specify the precedence level for voice over IP traffic in the TN3270 server, use the ip precedence TN3270 server configuration command. To remove the precedence value, use the no form of this command.
ip precedence {screen | printer} value
no ip precedence {screen | printer}
Syntax Description
Defaults
The default is a precedence value of 0 for both screens and printers.
Command Modes
TN3270 server configuration—The ip precedence (TN3270) command at this level applies to all PUs supported by the TN3270 server.
Listen-point configuration—The ip precedence (TN3270) command at this level applies to all PUs defined at the listen point.
DLUR PU configuration—The ip precedence (TN3270) command at this level applies to all PUs defined under DLUR configuration mode.
PU configuration—The ip precedence (TN3270) command at this level applies only to the specified PU.
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. Precedence values applied in TN3270 PU configuration mode override values applied in TN3270 server configuration mode.
You can enter new or different values for IP precedence without first using the no form of this command.
During initial Telnet negotiations to establish, or bind, the session an IP precedence value of 0 and IP ToS value of 0 is used. These values are used until the bind takes place. When the session is a type 2 bind, the TN3270 client is assumed to be a screen; otherwise the client is assumed to be a printer.
Examples
The following example assigns a precedence value of 3 to printers:
ip precedence printer 3Related Commands
ip tos
To specify the Type of Service (ToS) level for IP traffic in the TN3270 server, use the ip tos TN3270 server configuration command. To remove the ToS value, use the no form of this command.
ip tos {screen | printer} value
no ip tos {screen | printer}
Syntax Description
screen
Specifies the ToS is for screen devices.
printer
Specifies the ToS is for printer devices.
value
Sets the ToS priority. A value between 0 and 15. The default is 0.
Defaults
The default is a ToS value of 0 for both screens and printers.
Command Modes
TN3270 server configuration—The ip tos command at this level applies to all PUs supported by the TN3270 server.
Listen-point configuration—The ip tos command at this level applies to all PUs defined at the listen point.
DLUR PU configuration—The ip tos command at this level applies to all PUs defined under DLUR configuration mode.
PU configuration—The ip tos command at this level applies only to the specified PU.
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. ToS values applied in TN3270 PU configuration mode override values applied in TN3270 server configuration mode.
The default ToS values for screen and printer are 0. However, RFC 1349 recommends different default values. Specifically, the RFC recommends a default minimize screen delay value of 8 and a default maximize printer throughput value of 4. You must configure these values using the ip tos command if you want to comply to the defaults as stated in the RFC.
Table 35 shows the values described in RFC 1349.
.
During initial Telnet negotiations to establish, or bind, the session, an IP precedence value of 0 and IP ToS value of 0 is used. These values are used until the bind takes place. When the session is a type 2 bind, the TN3270 client is assumed to be a screen; otherwise the client is assumed to be a printer.
When you use the no form of the command, the ToS value is either set to 0 for that configuration mode or the value set at a previous (higher) configuration mode is used. For example, if you are at the TN3270 PU configuration mode and issue a no ip tos screen command, any value you configured previously at the TN3270 server configuration mode will take effect.
You can enter new or different values for ToS without first using the no form of this command.
Examples
In the following example, the TN3270 server ToS screen value is set to 10 and a specific PU ToS screen value is set to 0:
interface channel 3/2 tn3270-server ip tos screen 8 ip tos printer 4 pu PUS2 ip tos screen 0Related Commands
keepalive (TN3270)
To specify how many seconds of inactivity elapse before the TN3270 server transmits a DO TIMING-MARK or Telnet no operation (nop) to the TN3270 client, use the keepalive TN3270 server configuration command. To cancel the keepalive period and return to the previously configured siftdown value or the default, use the no form of this command.
keepalive seconds [send {nop | timing-mark [max-response-time]}]
no keepalive
Syntax Description
Defaults
The default behavior is to send timing marks with a keepalive interval of 1800 seconds (30 minutes). If you specify only the keepalive interval, the TN3270 server sends timing-marks.
The default value of the send timing-mark max-response-time command is 30 seconds if the keepalive interval is greater than or equal to 30 seconds. If the value of the keepalive interval is less than 30 seconds, then the default max-response-time is the value of the interval.
Command Modes
TN3270 server configuration—The keepalive command at this level applies to all PUs supported by the TN3270 server.
Listen-point configuration—The keepalive command at this level applies to all PUs defined at the listen point.
Listen-point PU configuration—The keepalive command at this level applies only to the specified PU.
DLUR PU configuration—The keepalive command at this level applies to all PUs defined under DLUR configuration mode.
PU configuration—The keepalive command at this level applies only to the specified PU.
Command History
11.2
This command was introduced.
12.0(5)T
The send {nop | timing-mark [max-response-time]} keywords were added.
Usage Guidelines
The keepalive command is valid only on the virtual channel interface. This command can be entered in one of four command modes (TN3270 configuration, Listen-point configuration, Listen-point PU configuration, or PU configuration mode). A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in the other supported configuration modes. A no keepalive command entered in a subsequent configuration mode will restore the keepalive value entered in the previous command mode.
In Cisco IOS releases prior to 12.0(5)T in which the keepalive command is supported, you cannot specify the period of time in which the client must respond to the DO TIMING-MARK before the TN3270 server disconnects the session. By default in prior releases, if the client does not reply within 30 minutes of sending the DO TIMING-MARK, the TN3270 server disconnects the TN3270 session. (The DO TIMING-MARK is a Telnet protocol operation that does not affect the client operation.)
With the addition of the send timing-mark max-response-time keywords in Cisco IOS release 12.0(5)T, you can specify the period of time in which the client must respond to the DO TIMING-MARK before being disconnected by the server. If you do not specify the max-response-time argument, the default value is determined by the size of the keepalive interval. The default is 30 seconds if the keepalive interval is greater than or equal to 30 seconds. If the value of the keepalive interval is less than 30 seconds, then the default max-response-time is the value of the interval.
If the IP path to the client is broken, the TCP layer will detect the failure to acknowledge the DO TIMING-MARK and initiate disconnection. This action usually takes much less than 30 seconds.
The keepalive command affects currently active and future TN3270 sessions. For example, reducing the keepalive interval to a smaller nonzero value causes an immediate burst of DO TIMING-MARKs on those sessions that have been inactive for a period of time greater than the new, smaller value.
Use the keepalive send nop command when you are using older TN3270 clients that do not support TIMING-MARK or are DOS-based clients. When you use the keepalive send nop command to monitor the client connection, no response is required by the client to the TN3270 server. However, the TCP/IP stack can detect that the physical connection still exists. This command is useful for those clients that can be swapped out when a DO TIMING-MARK has been sent by the TN3270 server. If the client is swapped out and cannot respond to the DO TIMING-MARK from the TN3270 server, the session is disconnected. However, if the client is swapped out and the Telnet nop command is sent by the server, the physical connection is still verifiable by the TCP/IP stack and the client remains connected to the server.
If your client supports the use of timing-marks and is not subject to being swapped out, then using timing-marks is preferable to the Telnet nop command for keepalive monitoring. The required response by TN3270 clients to timing-marks sent by the server provides a better indication of the health of the client-server connection.
Examples
The following example specifies that the TN3270 server sends a DO TIMING-MARK in 15-minute (900-second) intervals and the client must respond within 30 seconds (the default value for the timing-mark max-response-time command when not specified):
keepalive 900The following example entered in TN3270 server configuration mode specifies that the TN3270 server sends a DO TIMING-MARK in 30-minute (1800-second) intervals (the default interval) and the client must respond within 30 seconds (the default for the timing-mark max-response-time command when not specified):
no keepaliveThe following example specifies that the TN3270 server sends a DO TIMING-MARK in 40-minute (2400-second) intervals and the client must respond within 1 minute (60 seconds):
keepalive 2400 send timing-mark 60Consider the following example in which the keepalive command is configured in more than one command mode. In this example the keepalive command is first configured in TN3270 server configuration mode, followed by Listen-point PU configuration mode. The keepalive command values specified under the listen-point PU overrides the keepalive 300 value specified under the tn3270-server for PU1. In this example, all other PUs except PU1 use the value of the keepalive 300 command specified in TN3270 server configuration mode.
tn3270-serverkeepalive 300listen-point 10.10.10.1 tcp-port 40pu PU1 94223456 tok 1 08keepalive 10 send timing-mark 5pu PU2 94223457 tok 2 12Related Commands
keylen
To specify the maximum bit length for the encryption keys for SSL Encryption Support, use the keylen 128 profile configuration command. To disable this specification and thereby set the key length to the default of 40 bits, use the no form of this command or keylen 40.
keylen {40 | 128}
no keylen [40 | 128]
Syntax Description
40
Specifies the bit length for the encryption keys to 40.
128
Specifies the bit length for the encryption keys to 128.
Defaults
The default encryption key length is 40 bits.
Command Modes
Profile configuration.
Command History
Usage Guidelines
Exportable software versions cannot accept encryption key lengths greater than 40 bits.
The length is optional on the no form of this command. Entering the no form of this command with no length resets the length to the default value of 40 bits.
If the key length is changed, all new connections will use the new value. If an active session renegotiates its security specifications, it will use the new key length value.
Examples
The following example specifies the maximum encryption key length value to 128 bits:
tn3270-serversecurityprofile DOMESTIC SSLencryptorder RC4 DES RC2keylen 128link (TN3270)
To define and activate a link to a host, use the link DLUR SAP configuration command. To delete the link definition, use the no form of this command.
link name [rmac rmac] [rsap rsap]
no link name
Syntax Description
Defaults
No DLUR link is defined.
The default remote SAP address is 04 (hexadecimal).
Command Modes
DLUR SAP configuration
Command History
Usage Guidelines
This command is valid only on the virtual channel interface. The combination of rmac and rsap must be unique within the DLUR SAP function. These values can only be changed by deleting the link definition, using the no link command, and recreating the link definition.
For a link via a channel on this CMCC adapter, the TN3270 server and the hosts should open different adapters. Using different adapters avoids any contention for SAP numbers, and is also necessary if you configure duplicate MAC addresses for fallback CSNA or CMPC access to the host.
Examples
The following example defines a link name and a remote SAP address:
link LINK5 rsap 08The following example shows different adapter numbers configured on the same internal LAN to avoid SAP contention. The host uses SAP 4 on Token Ring adapter 0.
lan tokenring 0adapter 0 4000.0000.0001adapter 1 4000.0000.0002tn3270-serverdlur ...lsap token-adapter 1link HOST rmac 4000.0000.0001 rsap 4Related Commands
adapter
Configures internal adapters.
Nails clients to pools.
Creates a SAP in the SNA session switch and enters DLUR SAP configuration mode.
listen-point
To define an IP address for the TN3270 server, use the listen-point TN3270 server configuration command. To remove a listen point for the TN3270 server, use the no form of this command.
listen-point ip-address [tcp-port number]
no listen-point ip-address [tcp-port number]
Syntax Description
Defaults
The default tcp-port number is 23.
Command Modes
TN3270 server configuration
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
Use the listen-point command to create a unique listen point for every IP address and TCP-port pair. In this mode, the IP address and the TCP port are no longer configured in the PU. Configure the PUs under the appropriate listen point. The other siftdown configuration commands remain the same.
For example, in the old configuration the following statements were used to configure the IP address and TCP port in the PU:
tn3270-serverpu PU1 94223456 10.10.10.1 tok 1 08tcp-port 40keepalive 10In the new listen-point configuration, the following statements are used to configure the IP address and TCP port at the listen point:
tn3270-serverlisten-point 10.10.10.1 tcp-port 40pu PU1 94223456 tok 1 08keepalive 10You can also use the listen-point configuration to assign the same IP address to multiple PUs. In the old configuration the following statements were used:
tn3270-serverpu PU1 94201231 10.10.10.2 tok 1 10pu PU2 94201232 10.10.10.3 tok 1 12pu PU3 94201234 10.10.10.3 tok 1 14pu PU4 94201235 10.10.10.4 tok 1 16tcp-port 40pu PU5 94201236 10.10.10.4 tok 2 08In the new listen point configuration, the old statements are replaced by the following configuration commands. In this example, PU2 and PU3 are grouped into one listen point because they have the same IP address. Note that even though PU4's IP address is identical to PU5's IP address, they are not configured within the same listen point because the listen point indicates a unique IP address and TCP port pair. If you do not specify the TCP port, the default port value is 23.
tn3270-serverlisten-point 10.10.10.2pu PU1 94201231 tok 1 10listen-point 10.10.10.3pu PU2 94201232 tok 1 12pu PU3 94201234 tok 1 14listen-point 10.10.10.4pu PU5 94201236 tok 2 08listen-point 10.10.10.4 tcp-port 40pu PU4 94201235 tok 1 16The next example shows how the configuration changes for a DLUR PU. In this mode, the DLUR PU is no longer configured under DLUR, but is configured in the listen point.
In the old configuration, the following statements were used:
tn3270-serverdlur NETA.RTR1 NETA.HOSTdlus-backup NETA.HOSTlsap token-adapter 15 08link MVS2TN rmac 4000.b0ca.0016pu PU1 017ABCDE 10.10.10.6These statements are replaced by the following statements in the new listen-point configuration. The keyword dlur differentiates the listen-point direct PU from the listen point DLUR PU. The DLUR configuration must be completed before configuring the PU in the listen point. Any siftdown commands configured within the scope of the listen point are automatically inherited by the PUs that are configured within the scope of that listen point. To override the siftdown configurations, you can explicitly configure the siftdown configuration commands within the scope of the listen-point PU.
tn3270-serverdlur NETA.RTR1 NETA.HOSTdlus-backup NETA.HOSTlsap token-adapter 15 08link MVS2TN rmac 4000.b0ca.0016listen-point 10.10.10.6pu PU1 017ABCDE dlurExamples
Following is an example of the listen-point command showing PU7 grouped into the listen point at IP address 10.10.10.1 and TCP port 40:
tn3270-serverlisten-point 10.10.10.1 tcp-port 40pu PU7 94201237 tok 1 17Related Commands
lsap
To create a SAP in the SNA session switch and enter DLUR SAP configuration mode, use the lsap DLUR configuration command. To delete a SAP and all SNA session switch links using the internal LAN interface, use the no form of this command.
lsap type adapter-number [lsap]
no lsap type adapter-number [lsap]
Syntax Description
Defaults
The default value for the lsap argument is hexadecimal C0.
Command Modes
DLUR configuration
Command History
Usage Guidelines
The lsap command is valid only on the virtual channel interface. If the SAP in the SNA session switch function is already created, the lsap command with no arguments puts you in DLUR SAP configuration mode.
The lsap command can be entered only in DLUR configuration mode.
The lsap command uses values that are defined in two other commands: the lan internal LAN configuration command and the adapter internal LAN configuration command. The lan type and adapter adapter-number values configured on the CMCC internal LAN interface are used in the lsap command. However, the lan type keyword is a little different. Where the value for the type argument on the lan command is tokenring, the corresponding value for the type argument on lsap is token-adapter. This emphasizes that the number that follows is an adapter number, not a lan number.
The no lsap command hierarchically deletes any links using it. Any sessions using those links are lost.
Examples
The following example defines an adapter type, an adapter number, and a local SAP:
lsap token 0 B0Related Commands
adapter
Configures internal adapters.
Nails clients to pools.
Specifies the maximum bit length for the encryption keys for SSL Encryption Support.
lu deletion
To specify whether the TN3270 server sends a REPLY-PSID poweroff request to VTAM to delete the corresponding LU when a client disconnects, use the lu deletion TN3270 server configuration command. To remove LU deletion from the current configuration scope, use the no form of this command.
lu deletion {always | normal | non-generic | never | named}
no lu deletion
Syntax Description
Defaults
The default keyword is never.
Command Modes
TN3270 server configuration—The lu deletion command at this level applies to all PUs supported by the TN3270 server.
Listen-point configuration—The lu deletion command at this level applies to all PUs defined at the listen point.
Listen-point PU configuration—The lu deletion command at this level applies only to the specified PU.
DLUR PU configuration—The lu deletion command at this level applies to all PUs defined under DLUR configuration mode.
PU configuration—The lu deletion command at this level applies only to the specified PU.
Note
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated in to Cisco IOS Release 12.0 T.
12.1(5)T
This command was modified to add the named keyword.
Usage Guidelines
Use the always keyword of the lu deletion command when you have only screen LUs, and they are all different sizes. This prevents screen LUs from attaching to a previously used LU with an incompatible screen size.
Use the normal keyword of the lu deletion command when you have both screen and printer LUs. This is important because printers are acquired by the host application, and not logged on manually. If VTAM deletes the LU, then there is nothing for a host application (such as CICS) to acquire.
You can use the non-generic mode of LU deletion if VTAM can support deletion of specifically-named LUs. (The support of this mode is not currently available in VTAM, as of VTAM version 4.4.1.)
Use the never mode of LU deletion when you have only screen LUs and they all use the same screen size.
Use the named keyword of the lu deletion command when you have configured dynamic LU names from the TN3270 server side.
Examples
Following is an example of the lu deletion command specifying that the TN3270 server send a REPLY-PSID poweroff request to delete only screen LUs upon session disconnect for any PUs supported by the TN3270 server:
tn3270-serverlu deletion normalFollowing is an example of the lu deletion command configuring a listen-point PU to define DLUR PUs using dynamic LU naming:
tn3270-serverlisten-point 172.18.4.18pu pu1 05D9901 dlurlu deletion namedRelated Commands
lu termination
To specify whether a TERMSELF or UNBIND RU is sent by the TN3270 server when a client turns off his device or disconnects, use the lu termination TN3270 server configuration command. To remove LU termination from the current configuration scope, use the no form of this command.
lu termination {termself | unbind}
no lu termination
Syntax Description
Defaults
Unbind is the default.
Command Modes
TN3270 server configuration—The lu termination command at this level applies to all PUs supported by the TN3270 server.
Listen-point configuration—The lu termination command at this level applies to all PUs defined at the listen point.
Listen-point PU configuration—The lu termination command at this level applies only to the specified PU.
DLUR PU configuration—The lu termination command at this level applies to all PUs defined under DLUR configuration mode.
PU configuration—The lu termination command at this level applies only to the specified PU.
Note
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
Use the termself keyword when you want to be sure that the application terminates the session when the LU disconnects. This is important for certain applications such as CICS.
If you use the unbind keyword for session termination with applications such as CICS, VTAM security problems can arise. When CICS terminates a session from an UNBIND request, the application may reestablish a previous user's session with a new user, who is now assigned to the same freed LU.
Examples
Following is an example of the lu termination configuration command to force termination of the session when an LU disconnects for any PUs supported by the TN3270 server:
tn3270-serverlu termination termselfmaximum-lus
To limit the number of LU control blocks that will be allocated for the TN3270 server, use the maximum-lus TN3270 server configuration command. To restore the default value, use the no form of this command.
maximum-lus number
no maximum-lus
Syntax Description
Defaults
Because of the license structure, the default is 2100, which represents the limit of the lower-priced license (2000) plus a five percent buffer. If you configure a value greater than the default, a license reminder is displayed.
Command Modes
TN3270 server configuration
Command History
Usage Guidelines
The maximum-lus command is valid only on the virtual channel interface. Although the value may be varied at any time, reducing it below the current number of LU control blocks will not release those blocks until a PU is inactivated by DACTPU or by using the no pu command.
If the number of LUs in use reaches 94 percent of the current setting of maximum-lus, a warning message is displayed on the console. To prevent redundant messages, the threshold for generating such messages is raised for a period.
The TN3270 server attempts to allocate one LU control block for each LU activated by the hosts. In the case of dynamic definition of dependent LU (DDDLU) the control block is allocated when the client requests the LU, in anticipation of an ACTLU from the SSCP host.
By limiting the number of LU control blocks allocated, you can make sure enough memory is available to support other CMCC functions. The control blocks themselves take about 1K bytes per LU. During session activity, a further 2K per LU may be needed for data. On a CIP, 32 MB of memory will support 4000 LUs. To support more than 4000 LUs, we recommend 64 MB of memory. On an XCPA, 8 MB of memory supports 1000 LUs.
Examples
The following example allows 5000 LU control blocks to be allocated:
maximum-lus 5000Related Commands
pool
To define pool names for the TN3270 server and specify the number of screens and printers in each logical cluster, use the pool TN3270 server configuration command. To remove a client IP pool, use the no form of this command.
pool poolname [cluster layout layout-spec-string]
no pool poolname
Syntax Description
Defaults
The default value for the layout-spec-string argument is "1a."
Command Modes
TN3270 server configuration
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
The pool and allocate lu commands enable the TN3270 server to know the relationships between screen and printer LUs. These commands are an alternative to the LU nailing feature that allows clients to be nailed to LUs.
The pool command is configured in the TN3270 scope. The pool command provides the pool names and the definitions of the number of screens and printers in one logical cluster. Each pool statement must have a unique pool name.
The TN3270 server validates pool names when configuring a pool name and when processing the name received on a CONNECT request from the client. The TN3270 server rejects an invalid name and truncates the name received in the CONNECT request from the client to 8 characters or at an invalid character (whichever comes first) when processing the CONNECT request.
When using a pool command to create a cluster, a combination of the following values is used in the layout-spec-string:
•
•
•
Use the following format to define the layout-spec-string, where decimal_num is a decimal number between 1 and 255:
pool poolname cluster layout {decimal_nums}{decimal_nump}{decimal_numa}The total sum of the numbers must be less than or equal to 255. No spaces are used between the entries in the layout-spec-string. The default is 1a, which defines 1 screen or 1 printer. A screen, printer, or a wildcard definition cannot be followed by a definition of the same type. A screen definition can only be followed by a printer or wildcard. Similarly, a printer definition can be followed only by a wildcard or a screen definition.
The following are examples of invalid layout-spec-string values, and the corresponding corrected specification:
•
•
•
The combination of a screen, printer, and wildcard constitute a group. The layout-spec-string can support a maximum of 4 groups.
Consider the following example:
pool CISCO cluster layout 2s3p4a5s6a7s8p9sThere are 4 groups in this definition: 2s3p4a, 5s6a, 7s8p and 9s.
Pools must be defined before any pool references under the listen points are defined. Also, pools must be defined before they are referenced by other statements in the configuration. Failure to define the pool before it is referenced will cause the referencing configuration to be rejected.
Pools that are deleted (using the no form of the command) will cause all statements referencing the pool to be deleted.
The following criteria apply to the creation of pool names and LOCADDRs:
•
•
•
•
The following example uses the pool command to create two pools, pcpool and unixpool:
tn3270-serverpool pcpool cluster layout 4s1ppool unixpool cluster layout 49s1plisten-point 10.20.30.40client ip 10.10.10.2 pool pcpoolpu PU1 91903315 dlurallocate lu 1 pool pcpool clusters 50pu PU2 91903345 dlurallocate lu 1 pool unixpool clusters 5In this example, the pcpool contains a cluster of 4 screens and 1 printer per cluster. The total number of devices in a cluster cannot exceed 255, therefore the pcpool contains a total of 50 clusters with each cluster containing 5 LUs. Note that the remaining 5 LUs automatically go to the generic pool.
The unixpool contains 49 screens and 1 printer per cluster. The total number of devices in a cluster cannot exceed 255, therefore the unixpool contains a total of 5 clusters with each cluster containing 50 LUs. Again, note that the last 5 LUs automatically go to the generic pool.
Related Commands
tn3270-server
Starts the TN3270 server on a CMCC adapter and enters TN3270 server configuration mode.
preferred-nnserver
To specify a preferred network node (NN) as server, use the preferred-nnserver DLUR configuration command. To remove the preference, use the no form of this command.
preferred-nnserver name
no preferred-nnserver
Syntax Description
Defaults
No default behavior or values.
Command Modes
DLUR configuration
Command History
Usage Guidelines
The preferred-nnserver command is valid only on the virtual channel interface. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to 8 characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NET ID and is shared between entities in the same logical network.
When no preferred server is specified, the DLUR will request NN server support from the first suitable node with which it makes contact. If refused, it will try the next one, and so on.
If a preferred server is specified, then DLUR will wait a short time to allow a link to the preferred server to materialize. If the preferred server is not found in that time, any suitable node can be used, as above.
DLUR will not relinquish the current NN server merely because the preferred server becomes available.
Examples
The following example selects SYD.VMX as the preferred NN server:
preferred-nnserver SYD.VMXRelated Commands
profile
To specify a name and a security protocol for a security profile and enter profile configuration mode, use the profile security configuration command. To remove this name and protocol specification, use the no form of this command.
Create a new profile:
profile profilename {ssl | none}
Modify an existing profile:
profile profilename
Delete a profile:
no profile profilename {ssl | none}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Security configuration
Command History
Usage Guidelines
This command creates or modifies a security profile. To create a profile, specify the name of the new profile along with the security type. To modify a security profile, specify the name of the profile without the security type. The security type is only required when creating a profile. Using the security type when modifying a profile will result in an error.
Profile names cannot be duplicated.
Entering the no form of this command deletes the profile definition and all of its subcommand definitions (encryptorder, servercert, keylen, certificate reload commands). Entering the no form of this command deletes the sec-profile command specifications on all listen points where it is currently defined.
Entering the profile command moves the user into the profile configuration mode. Entering the no form of the command moves the user into the security configuration mode.
This command has no retroactive effect.
Examples
The following example specifies LAM as the profile name and ssl as the security protocol. When the no profile LAM command is configured, all new client connections will be non-secure.
tn3270-serversecurityprofile LAM sslkeylen 40servercert slot0:lamcertificate reloadlisten-point 10.10.10.1sec-profile LAMpu DIRECT 012ABCDE tok 0 04no profile LAMRelated Commands
pu (DLUR)
To create a PU entity that has no direct link to a host or to enter PU configuration mode, use the pu DLUR configuration command. To remove the PU entity, use the no form of this command.
pu pu-name idblk-idnum ip-address
no pu pu-name
Syntax Description
Defaults
No PU is defined.
Command Modes
DLUR configuration
Command History
Usage Guidelines
If the PU is already created, the pu pu-name command with no arguments puts you in PU configuration mode. In this mode you can modify an existing PU DLUR entity.
A typical usage for the IP address is to reserve an IP address per host application. For example, clients wanting to connect to TSO specify an IP address that will be defined with PUs that have LOGAPPL=TSO.
Examples
The following example defines define three PUs. Two of the PUs share the same IP address and the third PU has a separate IP address:
pu p0 05D99001 192.195.80.40pu p1 05D99002 192.195.80.40pu p2 05D99003 192.195.80.41Related Commands
Nails clients to pools.
Creates a PU entity that has no direct link to a host and enters listen-point PU configuration mode.
pu (listen-point)
To create a PU entity that has a direct link to a host or to enter listen-point PU configuration mode, use the pu listen-point configuration command. To remove the PU entity, use the no form of this command.
pu pu-name idblk-idnum type adapter-number lsap [rmac rmac] [rsap rsap] [lu-seed lu-name-stem]
no pu pu-name
Syntax Description
Defaults
The default remote SAP address is 04 (hexadecimal).
Command Modes
Listen-point configuration
Command History
11.2
This command was introduced.
11.2(18)BC
Listen-point PU configuration was added.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
The pu pu-name command is valid only on the virtual channel interface. If the PU is already created, the pu pu-name command with no arguments puts you in listen-point PU configuration mode, where you can modify an existing PU entity.
The pu listen-point command uses values that are defined in two other commands: the lan internal LAN configuration command and the adapter internal LAN configuration command. The lan type and adapter adapter-number values configured on the CIP internal LAN interface are used in the pu command.
For a link via a channel on this CMCC adapter, the TN3270 server and the hosts should open different adapters. Using different adapters avoids contention for SAP numbers and is also necessary if you configure duplicate MAC addresses for fallback CSNA or CMPC access to the host.
Examples
The following example configures the TN3270 server to be active and has one PU, CAPPU1, trying to connect. An LU seed using hexadecimal digits is defined.
tn3270-serverpu CAPPU1 05D18101 token-adapter 3 04 rmac 4000.0501.0001 lu-seed CAP01L##The following example shows different adapter numbers configured on the same internal LAN to avoid SAP contention. The host uses SAP 4 on Token Ring adapter 0.
lan tokenring 0adapter 0 4000.0000.0001adapter 1 4000.0000.0002tn3270-serverlisten-point 10.20.30.40pu PU1 05d00001 token-adapter 1 8 rmac 4000.0000.0001 rsap 4Related Commands
pu (TN3270)
To create a PU entity that has its own direct link to a host and enter PU configuration mode, use the pu TN3270 server configuration command. To remove the PU entity, use the no form of this command.
pu pu-name idblk-idnum ip-address type adapter-number lsap [rmac rmac] [rsap rsap] [lu-seed lu-name-stem]
no pu pu-name
Syntax Description
Defaults
No PU is defined.
The default remote SAP address is 04 (hexadecimal).
Command Modes
TN3270 server configuration
Command History
Usage Guidelines
The pu pu-name command is valid only on the virtual channel interface. If the PU is already created, the pu pu-name command with no arguments puts you in PU configuration mode, where you can modify an existing PU entity.
The pu (TN3270) command uses values that are defined in two other commands: the lan internal LAN configuration command and the adapter internal LAN configuration command. The lan type and adapter adapter-number values configured on the CIP internal LAN interface are used in the pu command.
For a link via a channel on this CMCC adapter, the TN3270 server and the hosts should open different adapters. Using different adapters avoids any contention for SAP numbers, and is also necessary if you configure duplicate MAC addresses for fallback CSNA or CMPC access to the host.
Examples
The following example configures the TN3270 server to be active, and has one PU, CAPPU1, trying to connect in. An LU seed using hexadecimal digits is defined.
tn3270-serverpu CAPPU1 05D18101 10.14.20.34 token-adapter 3 rmac 4000.0501.0001 lu-seed CAP01L##The following example shows different adapter numbers configured on the same internal LAN to avoid SAP contention. The host uses SAP 4 on token ring adapter 0.
lan tokenring 0adapter 0 4000.0000.0001adapter 1 4000.0000.0002tn3270-serverpu PU1 05d00001 10.0.0.1 token-adapter 1 8 rmac 4000.0000.0001 rsap 4Related Commands
pu dlur (listen-point)
To create a PU entity that has no direct link to a host or to enter listen-point PU configuration mode, use the pu dlur listen-point configuration command. To remove the PU entity, use the no form of this command.
pu pu-name idblk-idnum dlur [lu-seed lu-name-stem]
no pu pu-name idblk-idnum dlur [lu-seed lu-name-stem]
Syntax Description
Defaults
No PU is defined.
Command Modes
Listen-point configuration
Command History
Usage Guidelines
If the PU is already created, the pu dlur command without any arguments starts listen-point PU configuration mode. In this mode you can modify an existing listen-point DLUR PU entity.
You should define the DLUR before you configure the listen-point DLUR PU.
A typical usage for the IP address is to reserve an IP address for each application. For example, clients wanting to connect to TSO specify an IP address that is defined with PUs that have LOGAPPL=TSO.
If the lu-seed option is not configured, the PU name is used as the implicit lu-seed to generate the LU name. If the lu-seed option is configured, then there is an explicit LU name.
If the explicit LU names conflict, the TN3270 server will reject the PU configuration. If the implicit LU names (i.e., the PU names) conflict, the TN3270 server will accept the PU definitions, but the LU names will consist of a modified, truncated version of the PU name and the LOCADDR.
Table 36 LU Seed Name Examples
NC##RAL
NC#RAL
USA##NC
#GEORGE
#####
Examples
The following example defines three PUs in the listen point with an IP address of 172.18.4.18:
tn3270-serverlisten-point 172.18.4.18pu p0 05D99001 dlurpu p1 05D99002 dlurpu p2 05D99003 dlurThe following is an example of the TN3270 server configured with LU pooling. A listen-point PU is configured to define DLUR PUs using the dynamic LU naming. Note that the lu deletion command must be configured with the named option. The PU pu1 is defined with lu-seed abc##pqr. Using hexadecimal numbers for ##, the LU names for this PU are ABC01PQR, ABC02PQR, ABC0APQR.... up to ABCFFPQR. Similarly, the PU pu2 is defined with lu-seed pqr###. Using decimal numbers for ###, the LU names for this PU are PQR001, PQR002... up to PQR255.
The LUs ABC01PQR through ABC32PQR and PQR100 through PQR199 are allocated to the pool SIMPLE. The LUs ABC64PQR through ABC96PQR and PQR010 through PQR035 are allocated to the pool PCPOOL. The remaining LUs are in the generic pool.
tn3270-serverpool simple cluster layout 1spool pcpool cluster layout 4s1plu deletion nameddlur neta.shek neta.mvsdlsap tok 15 04link she1 rmac 4000.b0ca.0016listen-point 172.18.4.18pu pu1 91903315 tok 16 08 lu-seed abc##pqrallocate lu 1 pool simple clusters 50allocate lu 100 pool pcpool clusters 10pu pu2 91913315 dlur lu-seed pqr###allocate lu 10 pool pcpool clusters 5allocate lu 100 pool simple clusters 100Related Commands
dlur
Enables the SNA session switch function on the CMCC adapter and enters DLUR configuration mode.
listen-point
Defines an IP address for the TN3270 server.
response-time group
To configure a client subnet group for response-time measurements, use the response-time group TN3270 server configuration command. To remove a client subnet group from response-time measurements, use the no form of this command.
response-time group name [bucket boundaries t1 t2 t3 t4...] [multiplier m]
no response-time group name
Syntax Description
Defaults
Bucket boundaries and the multiplier value are fixed to the following defaults:
•
•
Command Modes
TN3270 server configuration
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
Multiple response-time groups can be configured within the scope of available memory. When using this command, up to 1024 IP subnets can be defined per response-time group with the client ip command. All TN3270 clients belonging to subnets configured within a specific response-time group are added to the response-time group when they connect as clients.
If the IP address and mask combination already exists within any response-time group, the following error message is displayed:
Subnet 10.1.1.0 255.255.255.248 already exists in client group MYSUBNETIn the following example, the response-time group MYSUBNET is configured:
tn3270-serverresponse-time group MYSUBNET bucket boundaries 15 25 60 120 multiplier 35client ip 10.1.1.0 255.255.255.248client ip 10.1.2.0 255.255.255.248Related Commands
Adds an IP subnet to a client subnet response-time group.
show extended channel tn3270-server response-time application
Displays information about application response-time client groups.
Displays information about the global response-time client group.
Displays information about host link response-time client groups.
show extended channel tn3270-server response-time listen-point
Displays information about listen point response-time client groups.
Displays information about Subnet response-time client groups.
sec-profile
To specify a security profile to be associated with a listen point, use the sec-profile listen-point configuration command. To remove this specification, use the no form of this command.
sec-profile profilename
no sec-profile profilename
Syntax Description
Defaults
No default behavior or values.
Command Modes
TN3270 listen-point configuration
Command History
Usage Guidelines
If this command is not entered or if the no form of the command is entered, the security profile reverts to the profile configured in the default-profile command. If no default profile is specified, the listen point accepts only nonsecure connections
This command has no retroactive effect.
Examples
The following example specifies LAM as the security profile name for all new clients connecting to listen point 10.10.10.1 until the sec-profile LAM1 command is configured. Once the sec-profile LAM1 command is configured, all new client connections to 10.10.10.1 will use LAM1 as the profile name.
tn3270-serversecurityprofile LAM sslkeylen 128servercert slot0:lamcertificate reloadprofile LAM1 sslkeylen 40servercert slot0:lam1certificate reloadlisten-point 10.10.10.1sec-profile LAMpu DIRECT 012ABCDE tok 0 04Sec-profile LAM1Related Commands
security (TN3270)
To enable security on the TN3270 server, use the security command. To turn off security on the TN3270 server, use the no form of this command.
security
no security
Syntax Description
This command has no arguments or keywords.
Defaults
The default is to have security enabled.
Command Modes
TN3270 server configuration
Command History
Usage Guidelines
If the no form of this command is configured, any listen points that contain a security profile definition are reconfigured and are no longer secure. Sessions already established on the listen point will continue to run in the same mode (secure or non-secure) as originally configured. If sessions are active on a listen point, a message will be sent to the console stating that the listen point has sessions running with an outdated security specification. A shutdown/restart sequence must be performed on the listen point if the user wants the sessions on the listen point to use the new specification.
Entering the security command moves the user into the security configuration mode. Entering the no form of this command moves the user to a TN3270 server configuration mode.
This command has no retroactive effect.
Examples
In the following example, security is enabled on the TN3270 server:
tn3270-serversecurityservercert
To specify the location of the TN3270 server's security certificate in the router's Flash memory, use the servercert profile configuration command.
servercert location
Syntax Description
location
Hexadecimal string of up to 63 characters specifying the location of the server's certificate in the Flash memory.
Defaults
No default behavior or values.
Command Modes
Profile configuration
Command History
Usage Guidelines
The certificate is in X.509 format, signed by a Certificate Authority (CA). The certificate must be created offline. It cannot be created using using the Cisco IOS software. Use third-party software or a Windows-based utility. The certificate should be in PEM or Base 64 format. The output from the certificate generation contains two parts: the certificate and the private key. Concatenate these two files to create a single certificate file in PEM or Base 64 format.
Store the concatenated file in Flash memory using TFIP and the location entered using the servercert location command. If the file does not exist in the Flash memory when the command is entered, an error message is displayed indicating that the file does not exist. The first time this command is configured the certificate is automatically loaded from the specified location. Subsequent changes to the location file do not cause the certificate to be read automatically into system's memory. The certificate reload command must be entered to read the certificate into memory. If the user exits from the profile configuration mode without configuring the servercert command, a warning message is displayed. The warning message indicates that it is mandatory to configure a certificate using the servercert command.
The following example specifies that slot0:lam is the location of the security certificate:
tn3270-serversecurityprofile LAM sslkeylen 512servercert slot0:lamcertificate reloadRelated Commands
profile
Specifies a name and a security protocol for a security profile and enters profile configuration mode.
show extended channel tn3270-server
To display current server configuration parameters and the status of the PUs defined for the TN3270 server, use the show extended channel tn3270-server EXEC command.
show extended channel slot/port tn3270-server
Syntax Description
slot
Specifies a particular CMCC adapter in the router where slot is the slot number.
port
Port value for a TN3270 server will always be 2.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show extended channel tn3270-server command:
Router# show extended channel 3/2 tn3270-server<current stats> < connection stats > <response time(ms)>server-ip:tcp lu in-use connect disconn fail host tcp172.28.1.106:23 510 1 12 11 0 54 40172.28.1.107:23 511 0 0 0 0 0 0172.28.1.108:23 255 0 0 0 0 0 0total 1276 1configured max_lu 20000 unbind-action disconnectidle-time 0 keepalive 1800 (send nop)tcp-port 23 generic-pool permit no timing-marklu-termination unbind lu-deletion neverdlur MPX.GOANCP status SHUTdlus MPX.NGMVMPCname(index) ip:tcp xid state link destination r-lsapEXT2(1) 172.28.1.106:23 05D18092 ACTIVE tok 0 4000.7470.00e7 08 04PUS10(2) 172.28.1.107:23 05D19010 ACTIVE tok 0 4000.7470.00e7 08 2CPUS11(3) 172.28.1.107:23 05D19011 ACTIVE tok 0 4000.7470.00e7 08 28PUS12(4) 172.28.1.108:23 05D19012 ACTIVE tok 0 4000.7470.00e7 08 24PUS9(5) 172.28.1.109:23 05D18509 SHUT tok 0 4001.3745.1088 04 40SDTF(7) 172.28.1.107:23 12345678 ACTIVE tok 0 0800.5a4b.1cbc 04 08TEST(8) 172.28.1.106:23 05D18091 ACTIVE tok 0 4000.7470.00e7 08 30INT1(6) 172.28.1.106:23 05D18091 SHUT dlurTable 37 describes significant fields in the display. Those fields not described correspond to configured values.
show extended channel tn3270-server client-ip-address
To display information about all clients at a specific IP address, use the show extended channel tn3270-server client-ip-address EXEC command.
show extended channel slot/port tn3270-server client-ip-address ip-address [disconnected | in-session | pending]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The show extended channel tn3270-server client-ip-address command is valid only on the virtual channel interface. Note that this command does not show information about LUs that have never been connected.
Examples
The following is sample output from the show extended channel tn3270-server client-ip-address command. The example shows only active sessions because no other session types exist at this client IP address.
Router# show extended channel 3/2 tn3270-server client-ip 192.195.80.40lu name client-ip:tcp nail state model frames in out idle for1 PUS11001 192.195.80.40:3169 Y ACT/SESS 327804 5 5 0:5:47pu is PUS11, lu is DYNAMIC type 2, negotiated TN3270bytes 155 in, 1758 out; RuSize 1024 in, 3840 out; NegRsp 0 in, 0 outpacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 outThe following is sample output using the disconnected keyword:
Router# show extended channel 2/2 tn3270 client-ip 10.14.1.21 disconnectedTotal 2 clients found using 10.14.1.21The following is sample output using the in-session keyword:
Router# show extended channel 2/2 tn3270 client-ip 10.14.1.21 in-sessionNote: if state is ACT/NA then the client is disconnectedlu name client-ip:tcp nail state model frames in out idle for3 PU1L03 10.14.1.21:35215 N ACT/SESS 327804 317 316 0:0:1pu is PU1, lu is DYNAMIC type 2, negotiated TN3270bytes 12167 in, 225476 out; RuSize 2048 in, 1536 out; NegRsp 0 in, 0 outpacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 outNote: if state is ACT/NA then the client is disconnectedlu name client-ip:tcp nail state model frames in out idle for4 PU1L04 10.14.1.21:35216 N ACT/SESS 327804 317 316 0:0:1pu is PU1, lu is DYNAMIC type 2, negotiated TN3270bytes 12167 in, 225476 out; RuSize 2048 in, 1536 out; NegRsp 0 in, 0 outpacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 outNote: if state is ACT/NA then the client is disconnectedTotal 2 clients found using 10.14.1.21The following is sample output using the pending keyword:
Router# show extended channel 2/2 tn3270 client-ip 10.14.1.21 pendingTotal 2 clients found using 10.14.1.21Table 38 describes significant fields in the display.
Related Commands
show extended channel tn3270-server client-name
To display information about all connected clients with a specific machine name, use the show extended channel tn3270-server client-name EXEC command.
show extended channel slot/virtual channel tn3270-server client-name name
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
There is not a no form for this command.
Examples
The following is sample output from the show extended channel tn3270-server client-name command:
Router# show extended channel 4/2 tn3270-server client-name dhcp-rtp-34-40.cisco.comNote: if state is ACT/NA then the client is disconnectedlu name client-name nail state model frames in out idle for6 dhcp-rtp-34-40.cisco. N P-ACTLU 3278S2E 1 0 0:1:59pu is T240CA, lu is DYNAMIC unbound, negotiated TN3270Ebytes 101 in, 0 out; RuSize 256 in, 256 out; NegRsp 0 in, 0 outpacing window 0 in, 0 out; credits 0 in, queue-size 0 in, 0 outresponse time buckets 0 0 0 0 0average total response time 0 average IP response time 0number of transactions 0Note: if state is ACT/NA then the client is disconnectedlu name client-name nail state model frames in out idle for7 T240DA07 dhcp-rtp-34-40.cisco. N P-BIND 3278S2E 4 3 0:1:32pu is T240CA, lu is DYNAMIC unbound, negotiated TN3270Ebytes 199 in, 407 out; RuSize 256 in, 256 out; NegRsp 0 in, 0 outpacing window 0 in, 0 out; credits 0 in, queue-size 0 in, 0 outresponse time buckets 0 0 0 0 0average total response time 0 average IP response time 0number of transactions 0Total 2 clients found using dhcp-rtp-34-40.cisco.comTable 38 describes significant fields in the display.
show extended channel tn3270-server dlur
To display information about the SNA session switch, use the show extended channel tn3270-server dlur EXEC command.
show extended channel slot/port tn3270-server dlur
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The show extended channel tn3270-server dlur command is valid only on the virtual channel interface.
Examples
The following is sample output from the show extended channel tn3270-server dlur command:
Router# show extended channel 3/2 tn3270-server dlurdlur MPX.GOANCPcurrent dlus MPX.NGMVMPC dlur-dlus status ACTIVEpreferred dlus MPX.NGMVMPC backup dlus MPX.NGMVMPBpreferred server MPX.NGMVMPAlsap token-adapter 0 5C vrn MPX.LAN4 status ACTIVElink P390 remote 4000.7470.00e7 08 status ACTIVETable 40 describes significant fields in the display.
show extended channel tn3270-server dlurlink
To display information about the DLUR components, use the show extended channel tn3270-server dlurlink EXEC command.
show extended channel slot/port tn3270-server dlurlink name
Syntax Description
slot
Specifies a particular CMCC adapter in the router where slot is the slot number.
port
Port number.
name
Name of the SNA session switch link to be displayed.
Command Modes
EXEC
Command History
Usage Guidelines
The show extended channel tn3270-server dlurlink command is valid only on the virtual channel interface.
Examples
The following is sample output from the show extended channel tn3270-server dlurlink command:
Router# show extended channel 3/2 tn3270-server dlurlink P390lsap token-adapter 0 5C vrn MPX.LAN4 status ACTIVElink P390 remote 4000.7470.00e7 08 status ACTIVEpartner MPX.NGMVMPC tgn 1 maxdata 1033Table 41 describes significant fields in the display.
Related Commands
show extended channel tn3270-server nailed-domain
To list all nailing statements with a specific nailed-domain name, use the show extended channel tn3270-server nailed-domain EXEC command.
show extended channel slot/virtual channel tn3270-server nailed-domain name
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
There is not a no form for this command.
Examples
The following is sample output from the show extended channel tn3270-server nailed-domain command:
Router# show extended channel 1/2 tn3270-server nailed-domain .cisco.com.CISCO.COM listen-point 172.18.4.18 pool PCPOOLTable 42 describes significant fields in the display.
show extended channel tn3270-server nailed-ip
To display mappings between a nailed client IP address and nailed LUs, use the show extended channel tn3270-server nailed-ip EXEC command.
show extended channel slot/port tn3270-server nailed-ip ip-address
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The show extended channel tn3270-server nailed-ip command is valid only on the virtual channel interface.
Examples
The following is sample output from the show extended channel tn3270-server nailed-ip command:
Router# show extended channel 3/2 tn3270-server nailed-ip 172.28.0.0172.28.1.0 255.255.255.192 pu BAGE1 lu 1 50172.28.1.80 255.255.255.248 pu BAGE2 lu 100 200 printer172.28.1.83 pu BAGE3 lu 1 60 printer172.28.1.82 pu BAGE1 lu 100 200Table 43 describes significant fields in the display.
Related Commands
show extended channel tn3270-server nailed-name
To list all nailing statements with a specific nailed machine name, use the show extended channel tn3270-server nailed-name EXEC command.
show extended channel slot/virtual channel tn3270-server nailed-name name
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
There is not a no form for this command.
Examples
The following is sample output from the show extended channel tn3270-server nailed-name command:
Router# show extended channel 1/2 tn3270-server nailed-name myclient.cisco.comMYCLIENT.CISCO.COM listen-point 172.18.4.18 pool PCPOOLHISCLIENT.CISCO.COM listen-point 172.18.4.18 pool UNIXPOOLHERCLIENT.CISCO.COM listen-point 172.18.4.19 pool GENERALPOOLTable 44 describes significant fields in the display.
show extended channel tn3270-server pu
To display configuration parameters for a PU and all the LUs currently attached to the PU, including the LU cluster layout and pool name, use the show extended channel tn3270-server pu EXEC command.
show extended channel slot/virtual channel tn3270-server pu pu-name [cluster | client-name]
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
The show extended channel tn3270-server pu command is valid only on the virtual channel interface. The display shown depends on whether the PU is a direct PU or a SNA session switch PU.
The output for the show extended channel tn3270-server pu command varies based on using the optional cluster keyword. Without the cluster keyword, the output column headings for the LU information appear as "model," "frames in out," and "idle for."
When you use the cluster keyword, the output column headings for the LU information appear as "cluster," "pool," and "count." The cluster heading lists the specific cluster within the pool to which the LU belongs along with the specific cluster layout after the slash.
The pool heading identifies the corresponding pool name, and the count heading identifies the cluster number out of the total number of clusters in the pool.
There is not a no form for this command.
Examples
This example shows a sample router configuration and the corresponding output using the show extended channel tn3270-server pu command:
interface Channel6/1no ip addressno keepalivecsna E160 40!interface Channel6/2ip address 172.18.4.17 255.255.255.248no keepalivelan TokenRing 15source-bridge 15 1 500adapter 15 4000.b0ca.0015lan TokenRing 16source-bridge 16 1 500adapter 16 4000.b0ca.0016tn3270-serverpool PCPOOL cluster layout 4s1ppool SIMPLE cluster layout 1apool UNIXPOOL cluster layout 49s1pdlur NETA.SHEK NETA.MVSDlsap token-adapter 15 04link SHE1 rmac 4000.b0ca.0016listen-point 172.18.4.18 tcp-port 23pu PU1 91903315 dlurallocate lu 1 pool PCPOOL clusters 10allocate lu 51 pool UNIXPOOL clusters 2allocate lu 200 pool SIMPLE clusters 50listen-point 172.18.4.19 tcp-port 2023pu PU2 91913315 token-adapter 16 08allocate lu 1 pool UNIXPOOL clusters 2allocate lu 101 pool SIMPLE clusters 100allocate lu 201 pool PCPOOL clusters 10Following is an example of the output from the show extended channel tn3270-server pu command without the cluster keyword for a PU named PU1:
Router# show extended channel 6/2 tn3270-server pu pu1name(index) ip:tcp xid state link destination r-lsapPU1(1) 172.18.4.18:23 91903315 ACTIVE dlur NETA.SHPU1idle-time 0 keepalive 1800 (send nop) unbind-act disconnect generic-poolpermip-preced-screen 0 ip-preced-printer 0 ip-tos-screen 0 ip-tos-printer 0lu-termination unbind lu-deletion neverbytes 27019 in, 73751 out; frames 1144 in, 869 out; NegRsp 0 in, 0 outactlus 5, dactlus 0, binds 5Note: if state is ACT/NA then the client is disconnectedlu name client-ip:tcp nail state model frames in out idle for1 SHED1001 161.44.100.162:1538 N ACT/SESS 3278S2E 228 172 0:0:251 SHED1051 161.44.100.162:1539 N ACT/SESS 3278S2E 240 181 0:0:2151 SHED1151 161.44.100.162:1536 N ACT/SESS 327802E 212 160 0:0:5152 SHED1152 161.44.100.162:1537 N ACT/SESS 3278S2E 220 166 0:0:4200 SHED1200 161.44.100.162:1557 N ACT/SESS 3278S2E 244 184 0:0:2Following is an example of the output from the show extended channel tn3270-server pu command with the cluster keyword for a PU named PU1. In the example below, 1/1a identifies cluster 1 with a layout of 1a, which contains 1 LU of any type.
Router# show extended channel 6/2 tn3270-server pu pu1 clustername(index) ip:tcp xid state link destination r-lsapPU1(1) 172.18.4.18:23 91903315 ACTIVE dlur NETA.SHPU1idle-time 0 keepalive 1800 (send nop) unbind-act discon generic-poolpermip-preced-screen 0 ip-preced-printer 0 ip-tos-screen 0 ip-tos-printer 0lu-termination unbind lu-deletion neverbytes 27489 in, 74761 out; frames 1164 in, 884 out; NegRsp 0 in, 0 outactlus 5, dactlus 0, binds 5Note: if state is ACT/NA then the client is disconnectedlu name client-ip:tcp nail state cluster pool count1 SHED1001 161.44.100.162:1538 N ACT/SESS 1/4s1p PCPOOL 1/551 SHED1051 161.44.100.162:1539 N ACT/SESS 1/49s1p UNIXPOOL 1/50151 SHED1151 161.44.100.162:1536 N ACT/SESS 1/1a :GENERIC 1/1152 SHED1152 161.44.100.162:1537 N ACT/SESS 1/1a :GENERIC 1/1200 SHED1200 161.44.100.162:1557 N ACT/SESS 1/1a SIMPLE 1/1
Note
Following is an example of the output from the show extended channel tn3270-server pu command with the client-name keyword for a PU named JADOEPU:
Router# show extended channel 1/2 tn3270-server pu jadoepu client-namename(index) ip:tcp xid state link destination r-lsapJADOEPU(1) 172.18.5.168:23 91922362 ACTIVE tok 31 4000.4000.0001 04 10idle-time 0 keepalive 30 unbind-act discon generic-pool permip-preced-screen 0 ip-preced-printer 0 ip-tos-screen 0 ip-tos-printer 0lu-termination unbind lu-deletion neverbytes 824 in, 2619 out; frames 36 in, 39 out; NegRsp 0 in, 0 outactlus 4, dactlus 0, binds 3Note: if state is ACT/NA then the client is disconnectedlu name client-name nail state model frames in out idle for1 VINCDP01 never connected Y ACT/NA 1 1 2:31:432 VINCDP02 never connected Y ACT/NA 1 1 2:31:435 VINDG005 HERCLIENT.CISCO.COM Y ACT/SESS 327904E 22 21 0:0:66 VINDG006 HISCLIENT.CISCO.COM Y ACT/NA 327904E 12 12 1:44:47client-ip mask nail-type lu-first lu-last10.20.30.40 screen 1 220.30.40.50 screen 9 10client-name nail-type lu-first lu-lastMYCLIENT.CISCO.COM screen 5 10.CISCO.COM screen 11 15Table 45 describes significant fields in the display.
Related Commands
show extended channel tn3270-server pu lu
To display information about the TN3270 server LUs running on CMCC adapter interface, use the show extended channel tn3270-server pu lu EXEC command.
show extended channel slot/port tn3270-server pu pu-name lu locaddr [history]
Syntax Description
DefaultsDefaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
The show extended channel tn3270-server pu lu command is valid only on the virtual channel interface.
Examples
The following is sample output from the show extended channel tn3270-server pu lu command for a SNA session switch PU:
Router# show extended channel 3/2 tn3270 pu int1 lu 1Note: if state is ACT/NA then the client is disconnectedlu name client-ip:tcp nail state model frames in out idle for1 GOAN1X01 171.69.176.77:3828 N ACT/NA 4 4 0:4:51pu is INT1, lu is STATIC type 0, negotiated TN3270Ebytes 74 in, 1219 out; RuSize 0 in, 0 out; NegRsp 0 in, 0 outpacing window 0 in, 0 out; credits 0 in, queue-size 0 in, 0 outThe following is sample output from the show extended channel tn3270-server pu lu history command:
Router# show extended channel 3/2 tn3270 pu pus20 lu 1 historyNote: if state is ACT/NA then the client is disconnectedlu name client-ip:tcp nail state model frames in out idle for1 PUS20001 192.195.80.40:2480 N ACT/SESS 327804 5 4 0:0:8pu is PUS20, lu is DYNAMIC type 2, negotiated TN3270bytes 155 in, 1752 out; RuSize 1024 in, 3840 out; NegRsp 0 in, 0 out>pacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 outtraces:Client connect reqReply PSID pos rspactlu reqbind reqsdt reqOUT len=12 2Dxxxxxxxx456B80000D0201IN len=25 xxxxxxxxxx45EB80000D0201000000OUT len=53 2Dxxxxxxxx466B800031010303B1IN len=10 2D0001010646EB800031OUT len=10 2D00010106476B8000A0IN len=10 2D0001010647EB8000A0OUT len=1677 2Cxxxxxxxx010381C07EC7114040IN len=9 2C0001010001838100This example shows the response-time information using the show extended channel tn3270-server pu lu command for the LU at LOCADDR 1 associated with the PU named vincdpu:
sydney# show extended channel 1/2 tn3270-server pu vincdpu lu 1Note: if state is ACT/NA then the client is disconnectedlu name client-ip:tcp nail state model frames in out idle for1 VINDG001 161.44.100.210:1315 N ACT/NA 3278S2E 12 11 0:0:18pu is VINCDPU, lu is DYNAMIC unbound, negotiated TN3270Ebytes 253 in, 954 out; RuSize 0 in, 0 out; NegRsp 1 in, 0 outpacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 outresponse time buckets 14 31 15 3 1average total response time 19 average IP response time 8number of transactions 64Table 46 describes significant fields in the display.
Related Commands
show extended channel tn3270-server response-time application
To display information for application client groups, use the show extended channel tn3270-server response-time application privileged EXEC command.
show extended channel slot/virtual channel tn3270-server response-time application [appl-name [detail]]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
If optional keywords are not used for the show extended channel tn3270-server response-time application command, a complete list of currently existing per-application client groups is displayed along with their collection control parameters. If you specify the appl-name keyword, only the client group corresponding to that application is displayed. If you specify the detail keyword, the client group entry is followed by a list of its client members and their response-time statistics.
Examples
Following is an example of output for the show extended channel tn3270-server response-time application:
Router# show extended channel 3/2 tn3270-server response-time application MYAPPLgroup APPL MYAPPLaggregate NO excludeip NO dynamic definite response NOsample period multiplier 30bucket boundaries 10 20 50 100Table 47 provides descriptions of the output fields for the show extended channel tn3270-server response-time application command.
Note
Related Commands
Configures a client subnet group for response-time measurements.
Displays information about the global response-time client group.
Displays information about host link response-time client groups.
show extended channel tn3270-server response-time listen-point
Displays information about listen point response-time client groups.
Displays information about Subnet response-time client groups.
show extended channel tn3270-server response-time global
To display information about the global client group, use the show extended channel tn3270-server response-time global privileged EXEC command.
show extended channel slot/virtual channel tn3270-server response-time global
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.2(18)BC
This command was introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
The show extended channel tn3270-server response-time global command displays collection control parameters for the global client group.
Examples
Following is an example of output for the show extended channel tn3270-server response-time global command:
Router# show extended channel 3/2 tn3270-server response-time globalgroup CLIENT GLOBALaggregate YES excludeip NO dynamic definite response NOsample period multiplier 30bucket boundaries 10 20 50 100buckets 105 118 211 109 104average total response time 33 average IP response time 24number of transactions 647Table 48 provides descriptions of the output fields for the show extended channel tn3270-server response-time global command.
Note
Related Commands
Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application
Displays information about application response-time client groups.
Displays information about host link response-time client groups.
show extended channel tn3270-server response-time listen-point
Displays information about listen point response-time client groups.
Displays information about Subnet response-time client groups.
show extended channel tn3270-server response-time link
To display information about host link client groups, use the show extended channel tn3270-server response-time link privileged EXEC command.
show extended channel slot/virtual channel tn3270-server response-time link [link-name]
Syntax Description
slot
Slot number.
virtual channel
Port number.
link-name
(Optional) PU name for a direct PU or link name for a DLUR PU.
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.2(18)BC
This command was first introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
This command displays information clients groups by host link. If no optional keywords are specified, a complete list of currently existing client groups by host link is displayed along with their collection control parameters and aggregate response-time statistics. If a value for the link-name argument is specified, only the client group corresponding to that link is displayed.
Examples
Following is an example of the output for the show extended channel tn3270-server response-time link command without optional keywords, which shows all current client groups by host link:
Router# show extended channel 3/2 tn3270-server response-time linkgroup DIRECT LINK MYLINKaggregate YES excludeip YES dynamic definite response NOsample period multiplier 30bucket boundaries 10 20 50 100buckets 10 18 21 10 10average total response time 37 average IP response time 23number of transactions 69group DLUR LINK HISLINKaggregate YES excludeip YES dynamic definite response NOsample period multiplier 30bucket boundaries 10 20 50 100buckets 14 31 15 3 1average total response time 19 average IP response time 8number of transactions 64Following is an example of the output for the show extended channel tn3270-server response-time link command for the link named DIRECT LINK MYLINK:
Router# show extended channel 3/2 tn3270-server response-time link direct link mylinkgroup DIRECT LINK MYLINKaggregate YES excludeip YES dynamic definite response NOsample period multiplier 30bucket boundaries 10 20 50 100buckets 10 18 21 10 10average total response time 37 average IP response time 23number of transactions 69Table 49 provides descriptions of the output fields for the show extended channel tn3270-server response-time link command.
Note
Related Commands
Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application
Displays information about application response-time client groups.
Displays information about the global response-time client group.
show extended channel tn3270-server response-time listen-point
Displays information about listen point response-time client groups.
Displays information about Subnet response-time client groups.
show extended channel tn3270-server response-time listen-point
To display information about listen point client groups, use the show extended channel tn3270-server response-time listen-point privileged EXEC command.
show extended channel slot/virtual channel tn3270-server response-time listen-point
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.2(18)BC
This command was first introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
The show extended channel tn3270-server response-time listen-point command displays information about groups of clients summarized by listen point. A complete list of currently existing listen-point client groups is displayed along with their collection control parameters and aggregate response-time statistics.
Examples
Following is an example of the output for the show extended channel tn3270-server listen-point command:
Router# show extended channel 3/2 tn3270-server response-time listen-pointgroup LP 10.20.30.40:23aggregate YES excludeip NO dynamic definite response NOsample period multiplier 30bucket boundaries 10 20 50 100buckets 10 18 21 10 10average total response time 37 average IP response time 23number of transactions 69group LP 50.60.70.80:23aggregate YES excludeip NO dynamic definite response NOsample period multiplier 30bucket boundaries 10 20 50 100buckets 310 418 521 510 210average total response time 27 average IP response time 20number of transactions 1969Table 50 provides descriptions of the output fields for the show extended channel tn3270-server response-time listen-point command.
Note
Related Commands
Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application
Displays information about application response-time client groups.
Displays information about the global response-time client group.
Displays information about host link response-time client groups.
Displays information about Subnet response-time client groups.
show extended channel tn3270-server response-time subnet
To display information about Subnet client groups, use the show extended channel tn3270-server response-time subnet privileged EXEC command.
show extended channel slot/virtual channel tn3270-server response-time subnet [ip-address ip-mask [detail]]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
11.2(18)BC
This command was first introduced.
12.0(5)T
This command was integrated into Cisco IOS Release 12.0 T.
Usage Guidelines
This command shows information about client subnet client groups. This includes all configured groups plus the CLIENT SUBNET OTHER group. If no optional parameters are specified, a complete list of client subnet client groups is displayed along with their collection control parameters. If you specify values for the ip-address and ip-mask arguments, only client groups containing that subnet are displayed. If you specify the detail keyword, each client group entry is followed by a list of its client members and their response-time statistics.
Examples
Following is an example of the output for all configured client groups using the show extended channel tn3270-server response-time subnet command:
Router# show extended channel 3/2 tn3270-server response-time subnetgroup SUBNETGROUP1subnet 10.10.10.0 255.255.255.192aggregate NO excludeip NO dynamic definite response NOsample period multiplier 30bucket boundaries 10 20 50 100group SUBNETGROUP2subnet 10.10.10.128 255.255.255.192subnet 10.10.10.192 255.255.255.192aggregate NO exclude ip NO dynamic definite response NOsample period multiplier 40bucket boundaries 20 30 60 120group CLIENT SUBNET OTHERaggregate NO exclude ip NO dynamic definite response NOsample period multiplier 30bucket boundaries 10 20 50 100Following is an example of the output for subnet 10.10.10.0 with IP mask 255.255.255.192, which shows a list of the client members and their response-time statistics:
Router# show extended channel 3/2 tn3270-server response-time subnet10.10.10.0 255.255.255.192 detailgroup SUBNETGROUP1subnet 10.10.10.0 255.255.255.192aggregate NO excludeip NO dynamic definite response NOsample period multiplier 30bucket boundaries 10 20 50 100client 10.10.10.129:23buckets 5 8 11 9 4average total response time 33 average IP response time 24number of transactions 37client 10.10.10.130:23buckets 6 9 10 10 2average total response time 32 average IP response time 25number of transactions 37client 10.10.10.131:23buckets 11 14 10 8 7average total response time 27 average IP response time 19number of transactions 50Table 51 provides descriptions of the output fields for the show extended channel tn3270-server response-time subnet command.
Note
Related Commands
Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application
Displays information about application response-time client groups.
Displays information about the global response-time client group.
Displays information about host link response-time client groups.
show extended channel tn3270-server response-time listen-point
Displays information about listen point response-time client groups.
show extended channel tn3270-server security
To display information about the TN3270 security enhancement, use the show extended channel tn3270-server security EXEC command.
show extended channel slot/virtual channel tn3270-server security [[sec-profile profilename] [listen-point ipaddress [tcp-port number]]]
Syntax Description
Defaults
The default tcp-port value is 23.
Command Modes
EXEC
Command History
Usage Guidelines
There is not a no form for this command.
Examples
The following is sample output from the show extended channel tn3270-server security command with the optional Sec-profile keyword configured:
Router# show extended channel 3/2 tn3270-server security sec-profile cert40status:ENABLE Default Profile: (Not Configured)Name Active LUs keylen encryptorder MechanismCERT40 0 40 RC4 RC2 RC5 DES 3DES SSLServercert:slot0:coach188.pemCertificate Loaded:YES Default-Profile:NOThe following is sample output from the show extended channel tn3270-server security command with the optional listen-point keyword configured:
Router# show extended channel 3/2 tn3270-server security listen-point 172.18.5.188status:ENABLE Default Profile: (Not Configured)IPaddress tcp-port Security-Profile active-sessions Type State172.18.5.188 23 CERT40 0 Secure ACTIVEActive Sessions using Deleted Profile:0Table 52 describes significant fields in the display.
Related Commands
sec-profile
Specifies the security profile to be associated with a listen point.
listen-point
Defines an IP address for the TN3270 server.
shutdown (TN3270)
To shut down TN3270 entities, such as PU, DLUR, and DLUR SAP, use the shutdown command in one of the TN3270 server command modes. The shutdown TN3270 command shuts down the TN3270 entities according to which configuration mode you are in when the command is issued. To restart the interface or entity, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Defaults
The interface or entity is enabled.
Command Modes
TN3270 server configuration
PU configuration
DLUR configuration
DLUR PU configuration
DLUR SAP configuration
Listen-point configuration
Listen-point PU configuration
Command History
Usage Guidelines
In TN3270 server configuration mode, the command shuts down the entire TN3270 server function.
In PU configuration mode, the command shuts down an individual PU entity within the TN3270 server.
In DLUR configuration mode, the command shuts down the whole DLUR subsystem within the TN3270 server.
In DLUR PU configuration mode, the command shuts down an individual PU within the SNA session switch configuration in the TN3270 server.
In DLUR SAP configuration mode, the command shuts down the local SAP and its associated links within the SNA session switch configuration.
Examples
The following example issued in TN3270 server configuration mode shuts down the entire TN3270 server:
shutdowntcp-port
To override the default TCP port setting of 23, use the tcp-port TN3270 server configuration command. To restore the default, use the no form of this command.
tcp-port port-number
no tcp-port
Syntax Description
port-number
A valid TCP port number in the range of 0 to 65534. The default is 23, which is the IETF standard. The value 65535 is reserved by the TN3270 server.
Defaults
In TN3270 server configuration mode, the default is 23.
In PU configuration mode the default is the value currently configured in TN3270 server configuration mode.
Command Modes
TN3270 server configuration—The tcp-port command at this level applies to all PUs supported by the TN3270 server.
DLUR PU configuration—The tcp-port command at this level applies to all PUs defined under DLUR configuration mode.
PU configuration—The tcp-port command at this level applies only to the specified PU.
Command History
Usage Guidelines
The tcp-port command is valid only on the virtual channel interface, and it can be entered in either TN3270 server configuration mode or PU configuration mode. A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in PU configuration mode. The tcp-port command affects only future TN3270 sessions.
The no tcp-port command entered in PU configuration mode removes the override.
Examples
The following example entered in TN3270 server configuration mode returns the TCP port value to 23:
no tcp-portRelated Commands
timing-mark
To select whether a WILL TIMING-MARK is transmitted when the host application needs an SNA response (definite or pacing response), use the timing-mark TN3270 server configuration command. To turn off WILL TIMING-MARK transmission except as used by the keepalive function, use the no form of this command.
timing-mark
no timing-mark
Syntax Description
This command has no arguments or keywords.
Defaults
No WILL TIMING-MARKS are sent except by keepalive.
Command Modes
TN3270 server configuration
Command History
Usage Guidelines
If the timing-mark command is configured the TN3270 server will send WILL TIMING-MARK as necessary to achieve an end-to-end response protocol. Specifically, TIMING-MARK will be sent if either of the following conditions is true:
•
•
The use of the timing-mark command can degrade performance. Some clients do not support the timing-mark command used in this way. Therefore, the timing-mark command should be configured only when both of the following conditions are true:
•
•
Examples
The following example enables the sending of the TIMING-MARK:
timing-markRelated Commands
tn3270-server
To start the TN3270 server on a CMCC adapter or to enter TN3270 server configuration mode, use the tn3270-server interface configuration command. To remove the existing TN3270 server configuration, use the no form of this command.
tn3270-server
no tn3270-server
Syntax Description
This command has no arguments or keywords.
Defaults
No TN3270 server function is enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
The tn3270-server command is valid only on the virtual channel interface. Only one TN3270 server can run on a CMCC adapter. It will always be configured on a virtual channel interface.
The no tn3270-server command shuts down TN3270 server immediately. All active sessions will be disconnected and all DLUR and PU definitions deleted from the router configuration. To restart a TN3270 server, you must reconfigure all parameters.
Examples
The following example starts the TN3270 server and enters TN3270 server configuration mode:
tn3270-serverunbind-action
To select what action to take when the TN3270 server receives an UNBIND request, use the unbind-action TN3270 server configuration command. To restore the default, use the no form of this command.
unbind-action {keep | disconnect}
no unbind-action
Syntax Description
keep
No automatic disconnect will be made by the server on receipt of an UNBIND.
disconnect
Session will be disconnected upon receipt of an UNBIND.
Defaults
In TN3270 server configuration mode, the default is disconnect.
In PU configuration mode the default is the value currently configured in TN3270 server configuration mode.
Command Modes
TN3270 server configuration—The unbind-action command at this level applies to all PUs supported by the TN3270 server.
Listen-point configuration—The unbind-action command at this level applies to all PUs defined at the listen point.
Listen-point PU configuration—The unbind-action command at this level applies only to the specified PU.
DLUR PU configuration—The unbind-action command at this level applies to all PUs defined under DLUR configuration mode.
PU configuration—The unbind-action command at this level applies only to the specified PU.
Command History
Usage Guidelines
The unbind-action command is valid only on the virtual channel interface. This command can be entered in either TN3270 server configuration mode or PU configuration mode. A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in PU configuration mode. The unbind-action command affects currently active and future TN3270 sessions.
The no unbind-action command entered in PU configuration mode removes the override.
The unbind-action command affects currently active and future TN3270 sessions.
Examples
The following example prevents automatic disconnect:
unbind-action keepvrn
To tell the SNA session switch the connection network to which the internal adapter interface on the CMCC adapter belongs, use the vrn DLUR SAP configuration command. To remove a network name, use the no form of this command.
vrn vrn-name
no vrn
Syntax Description
Defaults
The adapter is not considered to be part of a connection network.
Command Modes
DLUR SAP configuration
Command History
Usage Guidelines
The vrn command is valid only on the virtual channel interface. This command is used to discover routes without having to configure all possible links.
A connection network is also known as a shared-access transport facility (SATF). This means, at the MAC level, that all nodes in the network can reach each other using the same addressing scheme and without requiring the services of SNA session routing. A bridged LAN (whether source-route or transparent) is an example. Such a network is represented in the APPN topology as a kind of node, termed a virtual routing node (VRN).
To make use of this function, all APPN nodes must use the same VRN name for the SATF.
Refer to the VTAM operating system documentation for your host system for additional information regarding the VTAM VNGROUP and VNNAME parameters on the PORT statement of an XCA major node.
Several parameters in the DLUR configuration mode consist of fully qualified names, as defined by the APPN architecture. Fully qualified names consist of two case-insensitive alphanumeric strings, separated by a period. However, for compatibility with existing APPN products, including VTAM, the characters "#" (pound), "@" (at), and "$" (dollar) are allowed in the fully qualified name strings. Each string is from one to 8 characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NET ID and is shared between entities in the same logical network.
Examples
The following example sets a VRN name:
vrn SYD.BLAN25Related Commands
