Table Of Contents
LU Pooling (ASSOCIATE) and Response Time MIB
Sliding-window Average Response Times
Specification of LU Names of DDDLUs
TN3270 Server Configuration Mode
Listen-Point Configuration Mode
Listen-Point PU Configuration Mode
Response-Time Configuration Mode
Configuring TN3270 Siftdown Commands
Configuring the TN3270 Server and LU Pooling for a Non-APPN Environment
Guidelines for LU Pool Configuration
Configuring the TN3270 Server and LU Pooling for an APPN Environment
Verifying the TN3270 Server Configuration
Configuring Client Subnet Response-Time Groups
Verifying Response-Time Configuration
Monitoring and Maintaining LU Pooling and Response Time
Basic LU Pooling Configuration
Comprehensive LU Pooling Configuration
show extended channel tn3270-server
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
LU Pooling (ASSOCIATE) and Response Time MIB
Feature Overview
Cisco IOS release 12.0(5)T contains several TN3270 server configuration enhancements, which are described in this document:
•
Specification of LU Names of DDDLUs
LU Pooling
The TN3270 server enhancements in Cisco IOS release 12.0(5)T support the ASSOCIATE request through LU pooling. The LU pooling feature enables the TN3270 server to identify the relationships between screen and printer LUs.
The LU pool configuration is an option to the LU nailing feature that allows clients to be nailed to LUs. The LU pooling feature allows you to configure clients in the router and nail clients into groups of LUs. These groups of LUs are called clusters. Each cluster is given a unique pool name. An LU pool consists of one or more LU clusters that are related to each other. This allows logically related clients to connect to LUs that have the same logical relationship with the host. A cluster can contain screen LUs and their associated printer LUs. LU nailing is supported for LU pools.
The pool name can be used instead of a device name on a CONNECT request. The pool name must be eight characters or less in length and must comply with VTAM naming rules, which allow the following characters (alphabetic characters are not case sensitive):
•
•
These naming rules are enforced by the TN3270 server 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 eight characters or at an invalid character (whichever comes first) when processing the CONNECT request.
provides an overview of clusters configured within PUs.
Figure 1 LU Pooling
Support for the ASSOCIATE request enables you to define a partner printer in the TN3270 server for a given terminal LU pool or single terminal. As a result, the TN3270 server maintains a knowledge of printer and terminal relationships. The client does not need to know the LU name of the partner printer in advance. Typically, a client can request a pool name, a specific LU, or a resource without citing a pool name or LU name.
If the client sends an ASSOCIATE request for a resource name to the TN3270 server, the server provides the client with a resource LU name.
In , the client requests an LU from unixpool and is granted an LU from the specified pool. The client then initiates a new process by requesting the printer device associated with the given resource LU name.
The client requests a printer LU associated with termabc and the server grants the printer LU associated with termabc. Based on the configuration in the router that specifies the clusters of printer and screen LUs for pools, the TN3270 server assigns and allows the client to use the printer LU associated with its terminal LU.
Figure 2 Client Request for LU from a Specific Pool and Printer LU Association
shows the client request for a specific LU termxyz and then a request for a printer LU associated with the LU termxyz. The TN3270 server grants the screen LU and connects the printer associated with termxyz.
Figure 3 Client Request for a Specific LU and Printer LU Association
Response-Time Collection
Response-time MIB support enables you to capture response-time statistics for either individual sessions and clients or for groups of sessions and clients.
If SNMP is enabled on the router, an NMS system or users can use well-known and router-configured client group names to obtain response-time statistics. Response-time data collection is always enabled for all in-session clients. shows the types of client groups that are monitored:
Table 1
Client Types and Client Group Names
In Cisco IOS release 12.0(5)T, traps are not generated by the MIB.
Response-time data is collected using the following methods:
•
Sliding-window Average Response Times
The sliding-window response-time method uses a moving average. It reflects the most recent response time and discounts the old response times. When there is no activity, this method preserves the old response times. The algorithm used for the sliding-window method is similar to the moving-average method. For detailed information about sliding-window average times, refer to the TN3270E-RT-MIB.
Response-time Buckets
Response-time buckets contain counts of transactions with total response times that fall into a set of specified ranges. Response-time data gathered into a set of five buckets is suitable for verifying service-level agreements or for identifying performance problems through a network management application. The total response times collected in the buckets is governed by whether IP network transit times are included in the totals.
In , four bucket boundaries are specified for a response-time collection, which results in five buckets.
Figure 4 Response-Time Boundaries
The first response-time bucket counts transactions with total response times that are less than or equal to boundary 1 (B-1), the second bucket counts transactions with response times greater than B-1 but less than or equal to B-2, and so on. The fifth bucket is unbounded, and it counts all transactions with response times greater than boundary 4.
The four bucket boundaries have default values of 1 second, 2 seconds, 5 seconds, and 10 seconds, respectively.
For a detailed explanation of response-time buckets, refer to the TN3270E-RT-MIB.
Specification of LU Names of DDDLUs
LU name requests to be fulfilled by DDDLUs for PUs configured with the generic-pool deny command are supported. The CMCC adapter sends a REPLY-PSID poweroff for these LUs unless the lu deletion never command or lu deletion non-generic command is configured.
LU Termination
The lu termination command has been added to support SNA TERMSELF RU. The termself argument for the lu termination command orders termination of all sessions and session requests associated with an LU when users turn off their device or disconnect from the server. This is an important feature for applications such as CICS.
If you use an UNBIND request for session termination with 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.
LU Deletion
The lu deletion command specifies whether the TN3270 server sends a REPLY-PSID poweroff request to VTAM when a client disconnects. This command is recommended in host environments running VTAM version 4.4.1. Previous versions of VTAM are not compatible with NMVT REPLY-PSID.
Keepalive Enhancement
In the TN3270 server configuration, the keepalive command enables you to specify the maximum time allowed between keepalive marks before the server disconnects. This command is enhanced to allow control over how the keepalive timing marks are generated and how the keepalive responses are handled by the CMCC adapter.
TN3270 Configuration Modes
TN3270 configuration modes supported in the Cisco IOS release 12.0(5)T are:
•
•
•
•
shows TN3270 configuration modes supported in the Cisco IOS release 12.0(5)T.
Figure 5 TN3270 Configuration Modes
Note
TN3270 Server Configuration Mode
From interface configuration mode, tn3270-server command puts you in TN3270 server configuration mode. The following prompt appears:
(cfg-tn3270)#Listen-Point Configuration Mode
From the TN3270 server configuration mode, the listen-point command puts you in listen-point configuration mode. The following prompt appears:
(tn3270-lpoint)#Listen-Point PU Configuration Mode
From the listen-point configuration mode, the pu command puts you in the listen-point PU configuration mode and creates a new PU:
pu pu-name idblk-idnum type adapno lsap [rmac rmac] [rsap rsap] [lu-seed lu-name-stem]
The following prompt appears when the PU is configured:
(tn3270-lpoint-pu)#From listen-point configuration mode, the pu command to create a new PU for DLUR is:
pu pu-name idblk-idnum dlur
The pu command puts you in the PU configuration mode and the following prompt appears:
(tn3270-lpoint-pu)#DLUR Configuration Mode
From TN3270 server configuration mode, the dlur command puts you in DLUR configuration mode. The following prompt appears:
(tn3270-dlur)#DLUR SAP Configuration Mode
From DLUR server configuration mode, the lsap command puts you in DLUR SAP configuration mode. The following prompt appears:
(tn3270-dlur-lsap)#Response-Time Configuration Mode
From the TN3270 server configuration mode, the response-time group command puts you in response-time configuration mode. The following prompt appears:
(tn3270-resp-time)#PU Configuration Mode
From the TN3270 server configuration mode, the pu command puts you in PU configuration mode. The following prompt appears:
(tn3270-pu)#Benefits
This section describes the benefits of the TN3270 server features introduced in Cisco IOS release 12.0(5)T:
•
•
•
•
•
•
•
•
Related Documents
For details on the host server configuration and optional commands used with the TN3270 server, refer to the following documents:
•
•
•
For details on SNMP configuration, refer to the Cisco IOS Configuration Fundamentals Guide.
Supported Platforms
The TN3270 server enhancement features are supported on the following platforms using Cisco IOS release 12.0(5)T:
•
•
•
Prerequisites
Before configuring the TN3270 server with LU pooling or response-time client groups, host connectivity must be configured using one of the following methods:
•
•
•
For information about configuring CMPC or CSNA, refer to the Cisco IOS Bridging and IBM Networking Configuration Guide.
To use the response-time MIB, SNMP must be enabled on the router. For details on configuring SNMP, refer to the Cisco IOS Configuration Fundamentals Guide.
Supported MIBs and RFCs
MIBs
•
For descriptions of supported MIBs and how to use MIBs, see Cisco's MIB web site on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
RFCs
•
•
List of Terms and Acronyms
ASSOCIATE request—A feature of the TN3270 server that allows a client to connect to a printer LU that is attached to a terminal LU pool or a single terminal LU.
Cluster—Logical grouping of screens and printers of a defined layout in an LU pool.
DDDLU—Dynamic Definition of Dependent LU. A feature of VTAM that allows LUs to be created as needed and not be predefined under a switched PU. The CIP TN3270 server supports DDDLU.
Direct PU—A PU 2 that has its own LLC2 link to the owning VTAM. Several direct PUs can share a local SAP, but each must have a unique local/remote MAC/SAP quadruple.
DLUR—Dependent LU Requester. A feature of APPN that allows traditional 3270 traffic to be routed over the APPN network. The DLUR feature in the CIP creates an LU 6.2 session (pipe) with DLUS (Dependent LU Server) in VTAM (VTAM version 4R2 or higher). DLUR is defined as a separate switched PU to VTAM. All 3270 session control traffic (SSCP-to-PU and SSCP-to-LU) flows over this DLUR-DLUS pipe. Session data traffic, however, can be routed directly from LU to LU using APPN routing. The CIP DLUR is implemented as an APPN end node (EN).
DLUR PU—A PU 2 that uses the DLUR-DLUS pipe to send and receive all session control traffic. It does not use its own source SAP because it uses the DLUR SAP. Similarly, it does not have its own LLC session to the mainframe gateway because it rides on top of the DLUR LLC link.
LU deletion—A feature of the TN3270 server in Cisco IOS release 12.0(5)T that allows you to specify whether the TN3270 server sends a REPLY-PSID poweroff request to VTAM to delete an LU when a client disconnects.
LU nailing—A method by which you can associate a client's connection request with a specific LU. In Cisco IOS release 12.0(5)T, LU nailing is extended to support association of LU pools with a particular client IP address.
LU pool—A group of LUs that can contain logical clusters to establish relationships between screen and printer LUs.
LU termination—A feature of the TN3270 server in Cisco IOS release 12.0(5)T that supports SNA's TERMSELF RU, which allows the TN3270 server to order termination of all sessions and session requests associated with an LU when users turn off their device or disconnect from the server.
NMVT—Network Management Vector Transport. An SNA message consisting of a series of vectors conveying network management information.
REPLY-PSID—Request sent to VTAM for a particular product-set identification (PSID). The PSID is used in SNA to identify the hardware and software products that implement a network component.
Siftdown command—Command with values that are applied down through several levels of configuration and are optionally altered at each configuration level.
TERMSELF RU—An SNA request/response unit that forces termination of all sessions and session requests associated with an LU.
Configuration Tasks
The following sections describe how to configure LU pooling and response-time client groups, and use the new or modified TN3270 server configuration commands:
•
•
•
•
•
•
Refer to the "Configuration Examples" section for examples.
Note
Configuring TN3270 Siftdown Commands
There are many siftdown commands supported by the TN3270 server in multiple configuration modes. Values that you enter for a siftdown command in a subsequent configuration mode might override the values that you have entered for the same command (for the applicable PU only) in a previous configuration mode. Consider the following example in which the keepalive command is configured in more than one command 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 12In this example the keepalive command is first configured in TN3270 server configuration mode, which applies to all PUs supported by the TN3270 server. The keepalive command is specified again under the listen-point PU configuration mode for PU1, which overrides the previously specified keepalive 300 value, for PU1 only. PU2 continues to use the value of the keepalive command in the TN3270 server configuration level.
provides a list of the TN3270 siftdown commands and the associated configuration modes in which they are supported. An X in the column indicates that the command is supported. A "-" indicates that the command is not supported.
Table 2 Supported Configuration Modes for TN3270 Siftdown Commands
Note
Configuring the TN3270 Server and LU Pooling for a Non-APPN Environment
The following sections describe how to configure the TN3270 server and LU pooling for a non-APPN environment:
•
Guidelines for LU Pool Configuration
To configure LU pools on the TN3270 server on a CMCC adapter, perform the following steps:
•
•
•
When configured, the pool becomes one of the several criteria used by the TN3270 server to assign an LU to a client. When a client requests a connection, the TN3270 server determines the authorized capabilities of the client. For example, the TN3270 server attempts to determine whether LU nailing definitions exist for the client.
Client preferences are taken into consideration. Examples of client preferences are:
•
•
•
When the client criteria is processed, the TN3270 server assigns the first available LU in the group to the client. If an appropriate LU is not found, the TN3270 connection is closed.
The first client in a cluster is given an LU in a cluster that currently has no LUs assigned to clients. Subsequent clients in the cluster are given suitable LUs from within the cluster.
Configuring TN3270
To establish a TN3270 server on the internal LAN interface on the CMCC adapter and configure LU pooling, use the following commands beginning in global configuration mode:
Configuring Listen-Point
To configure listen point on the internal LAN interface on the CMCC adapter and configure LU pooling, use the following commands beginning in TN3270 server configuration mode.
When you use the listen-point command, you enter listen-point configuration mode and can use all other commands in this task list. Values that you enter for siftdown commands in listen-point configuration mode will override values that you previously entered in TN3270 server configuration mode.
Configuring Listen-Point PU
To configure listen point PU on the internal LAN interface on the CMCC adapter and configure LU pooling, use the following commands beginning in listen-point configuration mode.
When you use the pu command, you enter listen-point PU configuration mode and can use all other commands in this task list. Values that you enter for siftdown commands in listen-point PU configuration mode will override values that you previously entered in listen-point configuration mode.
Configuring the TN3270 Server and LU Pooling for an APPN Environment
This section provides the following procedures:
Configuring TN3270
To establish a TN3270 server on the internal LAN interface on the CMCC adapter and configure LU pooling, use the following commands beginning in global configuration mode. When you use the tn3270-server command, you enter TN3270 server configuration mode and can use all other commands in the task list.
Configuring Listen-Point
To configure listen point on the internal LAN interface on the CMCC adapter and configure LU pooling, use the following commands beginning in TN3270 server configuration mode.
When you use the listen-point command, you enter listen-point configuration mode and can use all other commands in this task list. Values that you enter for siftdown commands in listen-point configuration mode will override values that you previously entered in TN3270 server configuration mode.
Configuring Listen-Point PU
To configure listen-point PU on the internal LAN interface on the CMCC adapter and configure LU pooling, use the following commands beginning in listen-point configuration mode.
When you use the pu command, you enter listen-point PU configuration mode and can use all other commands in this task list. Values that you enter for siftdown commands in listen-point PU configuration mode will override values that you previously entered in listen-point configuration mode.
Verifying the TN3270 Server Configuration
This section provides a basic procedure that you can use to verify a TN3270 server configuration that uses LU pooling. Additional commands are available for you to perform further verification, but they depend upon the TN3270 configuration scenario and the particular information that you need to verify.
For detailed examples of configuration verification procedures for specific TN3270 server scenarios, see the Cisco TN3270 Design and Implementation Guide.
To verify a TN3270 server configuration that uses LU pooling, perform the following steps:
Step 1
router#show runBuilding configuration...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 10Step 2
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 unbind-act discon generic-pool permip-preced-screen 0 ip-preced-printer 0 ip-tos-screen 0 ip-tos-printer 0bytes 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/1Step 3
D NET,ID=CBSWN6,EConfiguring Client Subnet Response-Time Groups
To configure client subnet response-time groups, use the following commands in response-time configuration mode:
Verifying Response-Time Configuration
To verify the configuration of the client subnet response-time groups, use the show extended channel tn3270-server response-time subnet command in response-time configuration mode.
•
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 100•
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 50Monitoring and Maintaining LU Pooling and Response Time
Use the following commands in privileged EXEC mode to monitor the TN3270 server:
Configuration Examples
This section provides examples of how router configurations change with the implementation of new commands in this release. It also lists LU pooling configuration examples with DLUR and with direct PU:
•
•
Note
Basic LU Pooling Configuration
The following example shows a router with an existing TN3270 server configuration and PU specification:
tn3270-serverpu PU1 94223456 10.10.10.1 tok 1 08tcp-port 40keepalive 10The following example shows the same router with TN3270 server configuration that replaces the existing configuration and uses the listen-point command to accomplish LU pooling. The listen-point command was first introduced in Cisco IOS release 11.2(18)BC.
tn3270-serverlisten-point 10.10.10.1 tcp-port 40pu PU1 94223456 tok 1 08keepalive 10Note that in the new configuration, the IP address is not configured in the PU. Instead, the IP address is configured as a listen point and the PU is configured within the scope of the listen point. The tcp-port command is not configured within the scope of the PU, instead it is specified with the listen-point command.
Listen-Point Direct PU
The following example shows a router with an existing configuration that contains different PUs configured with the same IP addresses:
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 08The following example shows the same router replaced with a configuration that uses the listen-point command introduced in Cisco IOS release 11.2(18)BC:
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 16In 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.
Listen-Point DLUR PU
The following example shows a router with an existing configuration for DLUR:
tn3270-serverdlur NETA.RTR1 NETA.HOSTdlus-backup NETA.HOSTlsap token-adapter 15 08link MVS2TN rmac 4000.b0ca.0016pu PU1 017ABCDE 10.10.10.6The following example shows the same router replaced with a configuration that uses the new listen-point command introduced in Cisco IOS release 11.2(18)BC:
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 dlurIn this example, the PU is not configured within the scope of DLUR. Instead the PU is configured within the listen-point scope. The keyword dlur differentiates the listen-point direct PU from the listen-point DLUR PU. Note that the DLUR configuration must be completed before PU1 is configured.
Any siftdown commands configured within the scope of 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.
Comprehensive LU Pooling Configuration
shows a router running the TN3270 server (with DLUR and direct PU) and its LU pooling configuration.
Figure 6
TN3270 Server Using LU Pooling
The following router configuration shows an example of commands used to define the TN3270 server with LU pools.
Router Configuration
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 NEREGION cluster layout 1apool PCPOOL cluster layout 4s1ppool UNIXPOOL cluster layout 49s1pdlur NETA.SHEK NETA.MVSDlsap token-adapter 15 04link SHE1 rmac 4000.b0ca.0016listen-point 172.18.4.18client ip 10.20.20.30 pool UNIXPOOLclient ip 10.20.40.0 255.255.255.0 pool PCPOOLclient ip 10.20.30.0 255.255.255.128 pool NEREGIONpu PU1 91903315 dlurallocate lu 1 pool PCPOOL clusters 10allocate lu 51 pool UNIXPOOL clusters 2allocate lu 200 pool NEREGION clusters 50listen-point 172.18.4.19client ip 20.30.40.40 pool UNIXPOOLclient ip 20.40.34.0 255.255.255.0 pool PCPOOLclient ip 20.40.50.0 255.255.255.128 pool NEREGIONpu PU2 91913315 dlurallocate lu 1 pool UNIXPOOL clusters 2allocate lu 101 pool NEREGION clusters 100allocate lu 201 pool PCPOOL clusters 10shows cluster layouts for PU1 in the TN3270 server.
Figure 7 Cluster Layouts for PU1 in the TN3270 Server
shows cluster layouts for PU2 in the TN3270 server.
Figure 8 Cluster Layouts for PU2 in the TN3270 Server
Command Reference
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS release 12.0 Bridging and IBM Networking Command Reference.
•
•
•
•
•
•
•
•
•
In Cisco IOS release 12.0(1)T or later, you can search and filter the output for show and more commands. This functionality is useful when you need to sort through large amounts of output, or if you want to exclude output that you do not need to see.
To use this functionality, enter a show or more command followed by the "pipe" character (|), one of the keywords begin, include, or exclude, and an expression that you want to search or filter on:
command | {begin | include | exclude} regular-expression
Following is an example of the show atm vc command in which you want the command output to begin with the first line where the expression "PeakRate" appears:
show atm vc | begin PeakRate
For more information on the search and filter functionality, refer to the Cisco IOS Release 12.0(1)T feature module titled CLI String Search.
allocate lu
Use the allocate lu listen-point PU configuration command to assign LUs to a pool. Use the no form of this command to remove LUs assigned to a pool.
allocate lu lu-address pool poolname clusters count
no allocate lu lu-address pool poolname clusters count
Syntax Description
Default
This command has no defaults.
Command Mode
Listen-point PU configuration
Command History
Usage Guidelines
The following guidelines apply to the allocate lu command:
•
•
•
•
Example
In the following example, the starting LOCADDR is 10. Each cluster has 10 LOCADDRs, therefore 50 LOCADDRs are allocated to the pool name LOT1.
interface channel 0/2 tn3270-server pool LOT1 cluster layout 4s1p listen-point 10.20.30.40 pu PU1 allocate lu 10 pool LOT1 clusters 5As a result of this configuration, the following LOCADDRs are created in each cluster:
Cluster 1
LOCADDR 10—Screen
LOCADDR 11—Screen
LOCADDR 12—Screen
LOCADDR 13—Screen
LOCADDR 14—PrinterCluster 2
LOCADDR 15—Screen
LOCADDR 16—Screen
LOCADDR 17—Screen
LOCADDR 18—Screen
LOCADDR 19—PrinterAll of the LUs in these clusters are allocated to pool LOT1.
Related Commands
client ip
Use the client ip response-time configuration command to add an IP subnet to a client subnet response-time group. Use the no form of this command to remove an IP subnet from a client subnet response-time group.
client ip ip-address [ip-mask]
no client ip ip-address [ip-mask]
Syntax Description
Default
This command has no defaults.
Command Mode
Response-time configuration
Command History
Example
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 for application client groups.
Displays information about the global client group.
Displays information about host link client groups.
show extended channel tn3270-server response-time listen-point
Displays information about listen-point client groups.
Displays information about subnet client groups.
tn3270-server
Starts the TN3270 server on a CMCC adapter and enters TN3270 configuration mode.
client ip pool
Use the client ip pool listen-point configuration command to nail clients to pools. Use the no form of this command to remove clients from pools.
client ip ip-address [ip-mask] pool poolname
no client ip ip-address [ip-mask] pool poolname
Syntax Description
Default
This command has no defaults.
Command Mode
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 name spaces do not clash.
Example
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
keepalive
Use the keepalive TN3270 configuration command 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 no form of this command to cancel the keepalive period and return to the previously configured siftdown value or the default.
keepalive seconds [send {nop | timing-mark [max-response-time]}]
no keepalive
Syntax Description
Defaults
The default behavior is to send timing-mark 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 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.
PU configuration—The keepalive command at this level applies only to the specified PU.
Command History
11.2
This command was first 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 the transmission of 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, 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 transmits a DO TIMING-MARK in 15-minute (900-second) intervals and the client must respond within 30 seconds (the default for the timing-mark max-response-time when not specified):
keepalive 900The following example entered in TN3270 configuration mode specifies that the TN3270 server transmits 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 when not specified):
no keepaliveThe following example specifies that the TN3270 server transmits 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 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
listen-point
Use the listen-point TN3270 server configuration command to define an IP address for the TN3270 server. Use the no form of this command to remove a listen point for the TN3270 server.
listen-point ip-address [tcp-port number]
no listen-point ip-address [tcp-port number]
Syntax Description
Default
This command has no defaults.
Command Mode
TN3270 server configuration
Command History
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 dlurExample
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
lu deletion
Use the lu deletion configuration command 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 no form of this command to remove LU deletion from the current configuration scope.
lu deletion {always | normal | non-generic | never}
no lu deletion
Syntax Description
always
Always delete dynamic LUs upon disconnect.
normal
Delete screen LUs only upon disconnect.
non-generic
Delete only specified LUs upon disconnect.
never
Never delete LUs upon disconnect.
Default
The default keyword is never.
Command Mode
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.
PU configuration—The lu deletion command at this level applies only to the specified PU.
Note
Command History
Usage Guidelines
Use the always mode of LU deletion when you have only screen LUs, but they are all of different sizes. This prevents screen LUs from attaching to a previously used LU with an incompatible screen size designated by a previous session.
Use the normal mode of LU deletion when you have both screen and printer LUs. This is important because printers are acquired by the host application and are 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.
Example
Following is an example of the lu deletion command specifying that the TN3270 server sends a REPLY-PSID poweroff request to delete only screen LUs upon session disconnect for any PUs supported by the TN3270 server:
tn3270-serverlu deletion normallu termination
Use the lu termination configuration command 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 no form of this command to remove LU termination from the current configuration scope.
lu termination {termself | unbind}
no lu termination
Syntax Description
termself
Orders termination of all sessions and session requests associated with an LU upon disconnect.
unbind
Requests termination of the session by the application upon LU disconnect.
Default
Unbind is the default.
Command Mode
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.
PU configuration—The lu termination command at this level applies only to the specified PU.
Note
Command History
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.
Example
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 termselfpool
Use the pool TN3270 server configuration command to define pool names for the TN3270 server and specify the number of screens and printers in each logical cluster. Use the no form of this command to remove a client IP pool.
pool poolname [cluster layout layout-spec-string]
no pool poolname
Syntax Description
Default
The default value is "1a" for the layout-spec-string.
Command Mode
TN3270 server configuration
Command History
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 eight 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 listening 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:
•
•
•
•
Example
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 configuration mode.
pu (listen-point)
Use the pu listen-point configuration command to create a PU entity that has a direct link to a host or to enter listen-point PU configuration mode. Use the no form of this command to remove the PU entity.
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 Mode
Listen-point configuration
Command History
11.2
This command was first introduced.
11.2(18)BC
Listen-point PU configuration was added.
12.0(5)T
None.
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 dlur (listen-point)
Use the pu dlur listen point configuration command to create a PU entity that has no direct link to a host or to enter listen-point PU configuration mode. Use the no form of this command to remove the PU entity.
pu pu-name idblk-idnum dlur
no pu pu-name
Syntax Description
Default
No PU is defined.
Command Mode
Listen-point configuration
Command History
11.2
This command was first introduced.
11.2(18)BC
Listen-point PU configuration was added.
12.0(5)T
None.
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.
Example
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 dlurRelated Commands
response-time group
Use the response-time group TN3270 configuration command to configure a client subnet group for response-time measurements. Use the no form of this command to remove a client subnet group from response-time measurements.
response-time group name [bucket boundaries t1 t2 t3 t4...] [multiplier m]
no response-time group name
Syntax Description
Default
Bucket boundaries and the multiplier value are fixed to the following defaults:
•
•
Command Mode
TN3270 server configuration
Command History
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 MYSUBNETExample
In 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 for application client groups.
Displays information about the global client group.
Displays information about host link client groups.
show extended channel tn3270-server response-time listen-point
Displays information about listen-point client groups.
Displays information about subnet client groups.
show extended channel tn3270-server
Use the show extended channel tn3270-server EXEC command to display current server configuration parameters and the status of the PUs defined for the TN3270 server.
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
The port value for a TN3270 server will always be 2.
Default
This command has no defaults.
Command Mode
EXEC
Command History
11.2
This command was first introduced.
12.0(5)T
The lu-termination and lu-deletion fields were added to the output display.
Example
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 20000idle-time 0 keepalive 1800 unbind-action disconnecttcp-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 dlurprovides descriptions for the new lu-termination and lu-deletion output fields.
Table 3 New Output Field Descriptions in the Show Extended Channel TN3270-Server Command
show extended channel tn3270-server pu
Use the show extended channel tn3270-server pu privileged EXEC command to display configuration parameters for a PU and all the LUs currently attached to the PU, including the LU cluster layout and pool name.
show extended channel slot/virtual channel tn3270-server pu pu-name [cluster]
Syntax Description
Default
This command has no defaults.
Command Mode
Privileged EXEC
Command History
11.2
This command was first introduced.
11.2(18)BC
The cluster keyword was added.
12.0(5)T
The lu-termination and lu-deletion fields were added to the output display.
Usage Guidelines
The output for the show extended channel tn3270-server pu command varies by whether you are 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.
Example
This example shows a sample router configuration and the corresponding output using the show extended channel tn3270-server pu command.
Router Configuration
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 output for 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 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 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 output for 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 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
provides descriptions for the new lu-termination and lu-deletion output fields.
Table 4 New Output Field Descriptions in the Show Extended Channel TN3270-Server PU Command
Related Commands
show extended channel tn3270-server pu lu
Use the show extended channel tn3270-server pu lu privileged EXEC command to display information about the TN3270 server LUs running on a CMCC adapter interface.
show extended channel slot/port tn3270-server pu pu-name lu locaddr [history]
Syntax Description
Default
This command has no defaults.
Command Mode
Privileged EXEC
Command History
Usage Guidelines
The show extended channel tn3270-server pu lu command is valid only on the virtual channel interface.
Example
This 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 64provides descriptions for the new response-time output fields.
Table 5 New Output Field Descriptions in the Show Extended Channel TN3270-Server PU LU Command
Related Commands
show extended channel tn3270-server response-time application
Use the show extended channel tn3270-server response-time application privileged EXEC command to display information for application client groups.
show extended channel slot/virtual channel tn3270-server response-time application [appl-name [detail]]
Syntax Description
Default
This command has no defaults.
Command Mode
Privileged EXEC
Command History
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.
Example
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 100provides descriptions of the output fields for the show extended channel tn3270-server response-time application command.
Note
Table 6 Output Field Descriptions for the Show Extended Channel TN3270-Server Response-time Application Command
Related Commands
Configures a client subnet group for response-time measurements.
Displays information about the global client group.
Displays information about host link client groups.
show extended channel tn3270-server response-time listen-point
Displays information about listen-point client groups.
Displays information about subnet client groups.
show extended channel tn3270-server response-time global
Use the show extended channel tn3270-server response-time global privileged EXEC command to display information about the global client group.
show extended channel slot/virtual channel tn3270-server response-time global
Syntax Description
Default
This command has no defaults.
Command Mode
Privileged EXEC
Command History
Usage Guidelines
The show extended channel tn3270-server response-time global command displays collection control parameters for the global client group.
Example
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 647provides descriptions of the output fields for the show extended channel tn3270-server response-time global command.
Note
Table 7 Output Field Descriptions for the Show Extended Channel TN3270-Server Response-time Global Command
Related Commands
Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application
Displays information for application client groups.
Displays information about host link client groups.
show extended channel tn3270-server response-time listen-point
Displays information about listen-point client groups.
Displays information about subnet client groups.
show extended channel tn3270-server response-time link
Use the show extended channel tn3270-server response-time link privileged EXEC command to display information about host link client groups.
show extended channel slot/virtual channel tn3270-server response-time link [link-name]
Syntax Description
slot
Slot number.
virtual channel
Port number.
link-name
PU name for a direct PU or link name for a DLUR PU.
Default
This command has no defaults.
Command Mode
Privileged EXEC
Command History
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 link-name is specified, only the client group corresponding to that link is displayed.
Example
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 69provides descriptions of the output fields for the show extended channel tn3270-server response-time link command.
Note
Table 8 Output Field Descriptions for the Show Extended Channel TN3270-Server Response-time Link Command
Related Commands
Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application
Displays information for application client groups.
Displays information about the global client group.
show extended channel tn3270-server response-time listen-point
Displays information about listen-point client groups.
Displays information about subnet client groups.
show extended channel tn3270-server response-time listen-point
Use the show extended channel tn3270-server response-time listen-point privileged EXEC command to display information about listen-point client groups.
show extended channel slot/virtual channel tn3270-server listen-point
Syntax Description
Default
This command has no defaults.
Command Mode
Privileged EXEC
Command History
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.
Example
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 1969provides descriptions of the output fields for the show extended channel tn3270-server response-time listen-point command.
Note
Table 9 Output Field Descriptions for the Show Extended Channel TN3270-Server Response-time Listen-point Command
Related Commands
Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application
Displays information for application client groups.
Displays information about the global client group.
Displays information about host link client groups.
Displays information about subnet client groups.
show extended channel tn3270-server response-time subnet
Use the show extended channel tn3270-server response-time subnet privileged EXEC command to display information about subnet client groups.
show extended channel slot/virtual channel tn3270 response-time subnet [ip-address ip-mask [detail]]
Syntax Description
Default
This command has no defaults.
Command Mode
Privileged EXEC
Command History
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 the ip-address and ip-mask, 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 50provides descriptions of the output fields for the show extended channel tn3270-server response-time subnet command.
Note
Table 10 Output Field Descriptions for the Show Extended Channel TN3270-Server Response-time Subnet Command
Related Commands
Configures a client subnet group for response-time measurements.
show extended channel tn3270-server response-time application
Displays information for application client groups.
Displays information about the global client group.
Displays information about host link client groups.
show extended channel tn3270-server response-time listen-point
Displays information about listen-point client groups.
