Table Of Contents
Cisco IOS Release 11.0 BT Release Note and Update to Configuration Guides and Command References
New Software Features in 11.0(10)BT
Configuring TN3270 Server on the Channel Interface Processor
Cisco's Implementation of TN3270 on a Channel Interface Processor
Configuring TN3270 on a Channel Interface Processor
Formation of LU Model Type and Number
SNA Session Switch—End Node DLUR
VTAM Host Configuration Considerations for Dynamic LU Allocation
TN3270 Server Configuration Mode
Commands Allowed in Multiple Modes
TN3270 Configuration Task List
Task List for Multiple APPN Hosts
Configure PU Parameters on the TN3270 Server
show extended channel tn3270-server
show extended channel tn3270-server client-ip-address
show extended channel tn3270-server dlur
show extended channel tn3270-server dlurlink
show extended channel tn3270-server pu
show extended channel tn3270-server pu lu
Cisco Connection Documentation
Cisco IOS Release 11.0 BT Release Note and Update to Configuration Guides and Command References
January 15, 1999
This document supplements the Cisco IOS Release 11.0 documentation set with new and changed commands that support Cisco IOS Release 11.0(10)BT and later. Note that Cisco IOS Release 11.0(10)BT is the initial release of Cisco IOS Release 11.0 BT. No prior versions of Cisco IOS Release 11.0 BT exist. The TN3270 server function is supported on a Channel Interface Processor card in a Cisco 7000 series or Cisco 7500 series router. The following Cisco IOS releases are covered by this release note publication:
•
Cisco IOS 11.0(10)BT
•
•
•
Note
•
Note
•
•
•
•
•
•
•
•
Cisco IOS Release 11.0 BT is based on Cisco IOS Release 11.0.
Introduction
This Release Note and Update is divided into the following sections:
•
•
•
Use this document in conjunction with the Router Products Release Notes for Cisco IOS Release 11.0 and the Cisco IOS Release 11.0 configuration guide and command reference publications, specifically the Router Products Configuration Guide Chapters 1 to 6, Router Products Configuration Guide Chapters 22 to 33, Router Products Command Reference Chapters 1 to 6, Router Products Command Reference Chapters 22 to 33.
Release Note
Cisco IOS Release 11.0 BT introduces TN3270 server support on Channel Interface Processor (CIP) cards.
Note
Platform Support
Cisco IOS Release 11.0 BT supports the following router platforms:
•
•
Cisco IOS Packaging
The following feature sets are available in Release 11.0 BT. Refer to the Router Products Release Notes for Cisco IOS Release 11.0 for a list of the features provided in the Cisco 7000 and Cisco 7500 series feature sets.
•
•
Boot ROM Requirements
Boot ROMs that support Cisco IOS Release 11.0 are required. No special requirements exist for Cisco IOS Release 11.0 BT.
CIP Boot Image Requirements
The CIP boot image is bundled in the Cisco IOS Release 11.0 BT image. You must have the image that supports your CIP or your CIP2 hardware. You cannot run a CIP and a CIP2 card in the same router. See for a list of image names and supported CIP or CIP2 cards.
Table 1 11.0 BT Image Names for CIP and CIP2 Hardware
Memory Requirements
The memory requirements for Cisco IOS 11.0 BT are shown in . The CIP supports up to 128 Mb of memory.
Table 2 11.0 BT Memory Requirements
Microcode Software
Note that microcode software images are bundled with the system software image. Bundling eliminates the need to store separate microcode images. When the router starts up, the system software unpacks the microcode software bundle and loads the proper software on all the interface processor boards.
New Software Features in 11.0(10)BT
The TN3270 server is a new feature on the CIP of the Cisco 7000 family of routers. The TN3270 server allows TN3270 clients access to IBM and IBM-compatible mainframes. It can reduce the cycles spent by the mainframe on TCP/IP and TN3270 processing by a factor of ten or more and off-load the TCP/IP and TN3270 cycles from the mainframe.
The TN3270 server supports up to 8000 (CIP1) or up to 16000 (CIP2) concurrent sessions, while most external gateway solutions can support only 1000 to 2000 sessions. The TN3270 server offers the following capabilities:
•
•
•
•
•
•
TN3270 server requires 32 MB of CIP dynamic RAM to support up to 4000 sessions, 64 MB to support 8000 sessions, and 128 MB to support 16000 sessions (CIP2 only). TN3270 server can run concurrently with any of the other CIP applications (IP Datagram, TCP/IP Offload, or CIP SNA (CSNA)), but operation of any of these features will affect the total number of sessions supported because of contention for CIP processor cycles.
Update to Configuration Guide
The information that follows is an update to the Router Products Configuration Guide, Chapters 23 to 33. Add the TN3270 information as a standalone chapter following page 33-22.
Configuring TN3270 Server on the Channel Interface Processor
This chapter describes TN3270 server support provided by the Channel Interface Processor (CIP) card for Systems Network Architecture (SNA) devices. For a complete description of the commands mentioned in this chapter, refer to the "TN3270 Server Commands" update chapter.
Cisco's Implementation of TN3270 on a Channel Interface Processor
The TN3270 server feature on a CIP card provides mapping between an SNA 3270 host and a TN3270 client connected to a TCP/IP network as shown in . Functionally, it is useful to view the TN3270 server from two different perspectives: SNA functions and Telnet Server functions.
•
From the perspective of an SNA 3270 host connected to the CIP, the TN3270 server is an SNA device that supports multiple physical units (PUs), with each PU supporting up to 255 logical units (LUs). The LU can be Type 1, 2, or 3. The SNA host is unaware of the existence of the TCP/IP extension on the implementation of these LUs.
The LUs implemented by TN3270 server are dependent LUs. To route these dependent LU sessions to multiple virtual telecommunications access method (VTAM) hosts connected to the server in the CIP card, rather than routing in the VTAM hosts, the TN3270 server implements a SNA session switch with end node dependent LU requester (DLUR) function. Using the DLUR is optional so that the TN3270 server can be used with VTAM versions prior to version 4.2, which provide no APPN support.
SNA session switch allows you to eliminate SNA subarea routing between hosts of TN3270 traffic by establishing APPN links with the primary LU hosts directly.
•
From the perspective of a TN3270 client, the TN3270 server is a Telnet server that can support approximately 8000 (CIP1) or 16000 (CIP2) concurrent Telnet sessions. The server on the CIP card supports Telnet connection negotiation and data format as specified in RFC 1576 (referred to as "traditional TN3270") and RFC 1647 (referred to as "TN3270E").
Figure 1 TN3270 Implementation
Because the TN3270 server configuration is performed after an interface is configured for CIP SNA (CSNA) support, TN3270 configuration issues and tasks are addressed separately from the interface configuration tasks. The description of TN3270 configuration issues and tasks begins in the section "Configuring TN3270 on a Channel Interface Processor," later in this chapter.
Note
Configuring TN3270 on a Channel Interface Processor
The following sections describe additional features of TN3270 server support on the CIP. The features discussed include the following:
•
•
You will also need to understand the following information before proceeding with TN3270 configuration tasks:
•
Dynamic LU Allocation
This will be the most common form of request from TN3270 clients emulating a TN3270 terminal. The user typically wants to specify emulating a particular terminal type and normally is not interested in what LOCADDR or LU name is allocated by the host, as long as a network solicitor logon menu is presented. The server will perform the following on such a session request:
•
•
•
When VTAM receives the NMVT, it will use the EBCDIC model type and number string to look up an LU template under the LUGROUP. For example, the string "327802E" will find a match in the sample configuration shown in . An ACTLU will be sent and a terminal session with the model and type requested by the client is established.
Formation of LU Model Type and Number
VTAM requires a model type and number from the Reply PSID NMVT to use as a key to look up in the LU group to find an LU template. The model type is a four character string; the model number is a two or three character string. The server will accept the following formats of terminal type string from the client:
•
•
Note
•
•
A complication arises with TN3270E clients that request a copy of the BIND-IMAGE. Such clients require system control services (SCS) datastream on the system services control point (SSCP)-LU flow. All other clients require 3270 datastream on that flow. Therefore, these two kinds of client must be directed to different LUGROUP entries at the host. To make this as easy as possible, the SCS requirement is also encoded into the model string sent to the host. Following the previously described terminal type string formats accepted by the server, this additional condition is applied:
•
Specific LU Allocation
A TN3270E client can request a specific LU name by using the TN3270E command CONNECT as documented in RFC 1647. The name requested must match the name by which the TN3270 server knows the LU (see the section "LU Names in the TN3270 Server"), and the host must have activated the LU (with ACTLU).
LU Names in the TN3270 Server
Where SNA session switching is configured (that is, on DLUR PUs) the TN3270 server learns the LU names from the ACTLUs.
For direct PUs, a "seed" name can be configured on the PU. The TN3270 server uses this name in conjunction with the LOCADDRS to generate names for the LUs. It is best to use the same naming convention as the host, if possible.
SNA Session Switch—End Node DLUR
An end node DLUR function is implemented as part of the TN3270 server. The purpose of the DLUR is to allow the routing of TN3270 LUs to multiple VTAM hosts to be performed in the CIP card rather than on the VTAM hosts. The need for this feature will increase with the introduction of the new multi-CPU CMOS mainframe which comprises up to 16 CPUs that appear as separate VTAMs.
The implementation of TN3270 server LUs under DLUR also allows the server to learn about the LU names on the ACTLU, which greatly simplifies the configuration to support specifically requested LUs such as printers.
Multiple Hosts Support
The TN3270 server supports access to multiple hosts via the configuration on a PU basis (). PUs connected to different hosts or applications can be configured with different IP address.
From the pu (direct) TN3270 configuration command values shown in , PU X2 establishes a link to a host at SAP 8 on MAC address 4100.cafe.0002. A client connecting to IP address 171.69.176.43 is allocated an LU from that PU and is routed to that host.
Note that by using the DLUR function, all the LUs in the server can be defined and owned by a controlling VTAM. When a client requests an application residing on a different VTAM host, the controlling VTAM will issue the request to the target host which will send a BIND directly to the client. All LU-LU data will then flow directly between the target host and the client without needing to go through the controlling VTAM.
VTAM Host Configuration Considerations for Dynamic LU Allocation
Other non-Cisco implementations of TN3270 support depend on predefined, static pools of LUs to support different terminal types requested by the TN3270 clients. The CIP TN3270 server implementation removes the static nature of these configurations by using a VTAM release 3.4 feature, dynamic definition of dependent LU (DDDLU). (Refer to the VTAM operating system manuals for your host system, under the descriptions for LUGROUP for additional information.) DDDLU dynamically requests LUs using the terminal type provided by TN3270 clients. The dynamic request eliminates the need to define any LU configuration in the server to support TN3270 clients emulating a generic TN3270 terminal.
To support DDDLU, the PUs used by the TN3270 server have to be defined in VTAM with LUSEED and LUGROUP parameters as shown in .
Figure 2 VTAM Host Values Defining LUSEED and LUGROUP
With the configuration shown in defined in the host, the ACTPU sent by VTAM for the PU TN3270PU will have the "Unsolicited NMVT Support" set in the system services control point (SSCP) capabilities control vector. This allows the PU to dynamically allocate LUs by sending NMVT with a "Reply Product Set ID" control vector.
After the TN3270 server sends a positive response to the ACTPU, it will wait for VTAM to send ACTLUs for all specifically defined LUs. In the sample configuration shown in , ACTLUs will be sent for TN3X1100 and TN3X1101. The server sends a positive response and sets SLU DISABLED. The LOCADDR of these LUs are put into the specific LU cache and reserved for specific LU name requests only.
To allow sufficient time for the VTAM host to send all the ACTLUs, a 30-second timer is started and restarted when an ACTLU is received. When the time expires, it is assumed all ACTLUs defined in VTAM for the PU have been sent. All LUs that have not been activated are available in a generic LU pool to be used for DDDLU unless they have been reserved by the configuration using the generic-pool deny TN3270 configuration command.
After the VTAM activation, the server can support session requests from clients using dynamic or specific LU allocation.
TN3270 Configuration Modes
The TN3270 configuration modes and router command prompts are described in the following sections and displayed in . The TN3270 server can be configured only on Port 2, the internal LAN port, of a CIP card.
Some configuration commands create entities on the CIP. For most of these, the command changes to the mode associated with that entity (for example, a PU). In general, the parameters provided to create the entity come in two sets: those which identify the specific instance of the entity (for example, a PU name) and those that merely set operating parameters. To return to the mode later, the same command is used but with only the first set of parameters. The following example tasks clarify how to return to a command mode without necessarily creating a new entity:
To create a DLUR LSAP and enter DLUR LSAP configuration mode, perform the following task beginning in TN3270 DLUR configuration mode:
To return later to the DLUR LSAP configuration mode on the same entity, perform the following task beginning in TN3270 DLUR configuration mode:
To remove an entity, the same identification parameters are needed. Perform the following task beginning in TN3270 DLUR configuration mode:
TN3270 configuration modes described in this section include the following:
•
•
Figure 3 TN3270 Configuration Modes
TN3270 Server Configuration Mode
From interface configuration mode, tn3270-server command puts you in TN3270 server configuration mode.
Prompt:
tn3270-server>DLUR Configuration Mode
From TN3270 server configuration mode, the dlur command puts you in DLUR configuration mode.
Prompt:
tn3270-dlur>DLUR SAP Configuration Mode
From DLUR server configuration mode, lsap command puts you in DLUR SAP configuration mode.
Prompt:
tn3270-dlur-lsap>PU Configuration Mode
There are two paths to PU configuration mode: from the TN3270 server configuration mode, or from the DLUR configuration mode. In either mode, the pu command puts you in PU configuration mode.
From TN3270 configuration mode, the pu command to create a new PU is:
pu pu-name idblk-idnum ip-address type adapno lsap [rmac rmac] [rsap rsap] [lu-seed
lu-name-stem]From DLUR configuration mode, the pu command to create a new PU is:
pu pu-name idblk-idnum ip-address
From either mode, to return to PU configuration mode on PU pu-name the command is:
pu pu-name
Prompts:
tn3270-pu>tn3270-dlur-pu>Commands Allowed in Multiple Modes
The following commands are valid in TN3270 configuration mode, or in either variation of PU configuration mode:
[no] tcp-port port-number
[no] idle-time seconds
[no] keepalive seconds
[no] unbind-action {keep | disconnect}
[no] generic-pool {permit | deny}
[no] shutdown
Values entered in PU configuration mode override settings made in TN3270 configuration mode. In addition, the no form of these commands entered in PU configuration mode will restore the command value entered in TN3270 command mode.
TN3270 Configuration Task List
The following sections describe how to configure TN3270 server support on the CIP. Not all tasks are required. Refer to "TN3270 Configuration Example" for configuration examples.
Note
Task List for Multiple APPN Hosts
When the host site uses APPN and the TN3270 server can reach multiple hosts, we recommend you use the SNA Session Switch feature and configure your PUs under DLUR. In this instance, perform the following tasks:
Note
Task List for Non-APPN Hosts
When the host site does not use APPN, or you have a single APPN host, you configure your PU parameters for a directly connected host. In this instance, perform the following tasks:
•
Configure SNA Support
CIP SNA support (CSNA) must be configured prior to configuring TN3270 support. Refer to the section "Configure IBM Channel Attach for CSNA Support," in the "Configuring IBM Channel Attach" chapter of Bridging and IBM Networking Configuration Guide.
After you have configured CSNA support, proceed with TN3270 configuration.
Configure TN3270 Server
This task is required. To establish a TN3270 server on the internal LAN interface on the CIP, perform the following tasks beginning in global configuration mode:
When you use the tn3270-server command, you enter TN3270 configuration mode and can use all other commands in the task list. You can later override many configuration values you enter in TN3270 configuration mode from PU configuration mode. On IBM host systems, these types of commands are often referred to as "sift down" commands because their values can sift down through several levels of configuration and can be optionally altered at each configuration level.
Configure PU Parameters on the TN3270 Server
This task is required when configuring PUs that do not use the SNA Session Switch feature. To configure PU parameters for the TN3270 server, perform the following tasks beginning in TN3270 configuration mode.
When you use the pu command, you enter PU configuration mode and can use all other commands in this task list. Configuration values you enter in PU configuration mode will override other values entered while in TN3270 configuration mode. In addition, you can enter PU configuration mode from DLUR configuration mode when configuring PUs that are connected by means of DLUR.
If you are configuring PUs for directly connected hosts, you need not perform any additional configuration tasks.
Configure DLUR
This task is required when configuring DLUR connected hosts. To configure DLUR parameters for the TN3270 server, perform the following tasks beginning in TN3270 configuration mode.
Configure SAPs under DLUR
To configure SAPs under the DLUR function, perform the following tasks beginning in DLUR configuration mode.
Configure PUs under DLUR
This task is required when configuring DLUR connected hosts. To configure PUs under the DLUR function, perform the following tasks beginning in DLUR configuration mode.
The pu command entered in DLUR configuration mode has different parameters than when it is entered from TN3270 configuration mode.
Monitor the TN3270 Server
The following table lists some of the monitoring tasks specific to the TN3270 server. To display the full list of show commands, enter show ? at the EXEC prompt.
Use the following commands in privileged EXEC mode:
TN3270 Configuration Example
The following configuration has three PUs using DLUR and two more with direct connections.
The initial CIP configuration is as follows:
interface Channel2/2ip address 10.10.20.126 255.255.255.128no ip redirectsno ip directed-broadcastip pim query-interval 0ip igmp query-interval 0no ip route-cacheno keepaliveno clns checksumclns congestion-threshold 0clns erpdu-interval 0clns rdpdu-interval 0no clns route-cacheno clns send-erpduno clns send-rdpdulan TokenRing 0source-bridge 223 1 2099adapter 0 4100.cafe.0001llc2 N1 2057adapter 1 4100.cafe.0002llc2 N1 2057Configuration dialog to configure the TN3270 function follows:
! HOSTA is channel-attached and will open SAP 8 on adapter 0.! HOSTB is reached via token-ring! HOSTC is channel-attached non-APPN and will open SAP 4 on adapter 0.! enter interface configuration mode for the virtual interface in slot 2router(config)#int channel 2/2! create TN3270 Server entityrouter(config-if)#tn3270-server! set server-wide defaults for PU parametersrouter(cfg-tn3270)#keepalive 0router(cfg-tn3270)#unbind-action disconnectrouter(cfg-tn3270)#generic-pool permit! define DLUR parameters and enter DLUR configuration moderouter(cfg-tn3270)#dlur SYD.TN3020 SYD.VMG! create PUs under DLUR! Note that the first two share an IP addressrouter(tn3270-dlur)#pu pu0 05d99001 10.10.20.1router(tn3270-dlur-pu)#pu pu1 05d99002 10.10.20.1router(tn3270-dlur-pu)#pu pu2 05d99003 10.10.20.2! create a DLUR LSAP and enter DLUR LSAP configuration moderouter(tn3270-dlur-pu)#lsap token-adapter 1! specify the VRN name of the network containing this lsaprouter(tn3270-dlur-lsap)#vrn syd.lan4! create a link from this lsaprouter(tn3270-dlur-lsap)#link hosta rmac 4100.cafe.0001 rsap 8router(tn3270-dlur-lsap)#link hostb rmac 4000.7470.0009 rsap 4router(tn3270-dlur-lsap)#exitrouter(tn3270-dlur)#exit! create direct pus for the non-APPN Host! note that they must use different lsaps because they go to the same Hostrouter(cfg-tn3270)#pu pu3 05d00001 10.10.20.5 tok 1 24 rmac 4100.cafe.0001 lu-seed pu3###router(tn3270-pu)#pu pu4 05d00002 10.10.20.5 tok 1 28 rmac 4100.cafe.0001 lu-seed pu4###router(tn3270-pu)#endThe resulting configuration from the initial configuration and the configuration dialog follows:
interface Channel2/2ip address 10.10.20.126 255.255.255.128no ip redirectsno ip directed-broadcastip pim query-interval 0ip igmp query-interval 0no ip route-cacheno keepaliveno clns checksumclns congestion-threshold 0clns erpdu-interval 0clns rdpdu-interval 0no clns route-cacheno clns send-erpduno clns send-rdpdulan TokenRing 0source-bridge 223 1 2099adapter 0 4100.cafe.0001llc2 N1 2057adapter 1 4100.cafe.0002llc2 N1 2057tn3270-serverpu PU3 05D00001 10.10.20.5 token-adapter 1 24 rmac 4100.cafe.0001 lu-seed PU3###pu PU4 05D00002 10.10.20.5 token-adapter 1 28 rmac 4100.cafe.0001 lu-seed PU4###dlur SYD.TN3020 SYD.VMGlsap token-adapter 1vrn SYD.LAN4link HOSTB rmac 4000.7470.0009link HOSTA rmac 4100.cafe.0001 rsap 08pu PU0 05D99001 10.10.20.1pu PU1 05D99002 10.10.20.1pu PU2 05D99003 10.10.20.2Update to Command Reference
The information that follows is an update to the Router Products Command Reference, Chapters 23 to 33. Add the TN3270 information as a standalone chapter following page 33-30.
TN3270 Server Commands
This update describes the commands to configure TN3270 support on the Channel Interface Processor (CIP). For TN3270 configuration tasks and examples, refer to the "Configuring TN3270 Server on the Channel Interface Processor" update chapter of this Release Note.
The following commands are documented in this update chapter:
•
•
•
•
•
•
•
•
•
•
dlur
Use the dlur TN3270 configuration command to enable the Systems Network Architecture (SNA) session switch function on the CIP, or to enter dependent logical unit requester (DLUR) configuration mode. Use the no form of this command to disable the SNA session switch function and discard all parameter values associated with the SNA session switch.
dlur
dlur fq-cpname fq-dlusname
no dlurSyntax Description
Default
No DLUR function is enabled.
Command Mode
TN3270 configuration
Usage Guidelines
If the SNA session switch function is already enabled, the dlur command with no arguments puts you in DLUR configuration mode.
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 eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID and is shared between entities in the same logical network.
The no dlur command hierarchically deletes all resources defined beneath it.
Example
The following command 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 NETID portion of both names is the same:
dlur SYD.TN3020 SYD.VMGdlus-backup
Use the dlus-backup DLUR configuration command to specify a backup DLUS for the DLUR function. Use the no form of this command to remove a backup DLUS name.
dlus-backup dlusname2
no dlus-backupSyntax Description
Default
No backup DLUS is specified.
Command Mode
DLUR configuration
Usage Guidelines
Only one backup DLUS can be specified per CIP. If the backup DLUS specified in the dlus-backup command is in use when a no dlus-backup 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 eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID and is shared between entities in the same logical network.
Example
The following command specifies SYD.VMX as the backup DLUS:
dlus-backup SYD.VMXgeneric-pool
Use the generic-pool TN3270 configuration command to specify whether or not left over LUs will be made available to TN3270 sessions that do not request a specific LU or LU pool through TN3270E. Use the no form of this command to selectively remove the permit or deny condition of generic pool use.
generic-pool {permit | deny}
no generic-poolSyntax Description
Defaults
In TN3270 configuration mode, generic pool use is permitted.
In PU configuration mode, the default is the value currently configured in TN3270 configuration mode.
Command Modes
TN3270 configuration
PU configuration
Usage Guidelines
A left over 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 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 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.
Example
The following command permits generic LU pool use:
generic-pool permitidle-time
Use the idle-time TN3270 configuration command to specify how many seconds of LU inactivity, from both host and client, before the TN3270 session is disconnected. Use the no form of this command to cancel the idle time period and return to the default.
idle-time seconds
no idle-timeSyntax Description
Defaults
The default in TN3270 configuration mode is that the session is never disconnected (0).
The default in PU configuration mode is the value currently configured in TN3270 configuration mode.
Command Modes
TN3270 configuration
PU configuration
Usage Guidelines
The idle-time command can be entered in either TN3270 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 configuration mode sets the default idle-time disconnect value to 0, or never disconnect:
no idle-timekeepalive
Use the keepalive TN3270 configuration command to specify how many seconds of inactivity elapse before transmission of a DO TIMING-MARK to the TN3270 client. Use the no form of this command to cancel the keepalive period and return to the default.
keepalive seconds
no keepaliveSyntax Description
seconds
Number of seconds, from 0 to 65535. A value of 0 means no keepalive signals are sent. The default is 1800 seconds (30 minutes).
Defaults
The default in TN3270 configuration mode is 1800 seconds (30 minutes).
The default in PU configuration mode is the value currently configured in TN3270 configuration mode.
Command Modes
TN3270 configuration
PU configuration
Usage Guidelines
The keepalive command can be entered in either TN3270 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 keepalive command entered in PU configuration mode will restore the keepalive value entered in TN3270 command mode.
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.
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 will usually take much less than 30 minutes.
The keepalive command affects currently active and future TN3270 sessions. For example, reducing the value to a smaller nonzero value will cause 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.
Examples
The following command sets a keepalive disconnect value of 15 minutes (900 seconds):
keepalive 900The following command entered in TN3270 configuration mode sets the keepalive disconnect value to 1800 seconds, the default:
no keepalivelink
Use the link DLUR SAP configuration command to define and activate a link to a host. Use the no form of this command to delete the link definition.
link name [rmac rmac] [rsap rsap]
no link nameSyntax Description
Defaults
No DLUR link is defined.
The default remote SAP address is 04 (hexadecimal).
Command Mode
DLUR SAP configuration
Usage Guidelines
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 CIP, the TN3270 server and the hosts should open different adapters in the same internal LAN. Using different adapters avoids any contention for SAP numbers, and is also necessary if you configure duplicate MAC addresses for fallback CSNA access to the host. By configuring the adapters in the same internal LAN, you achieve the same performance—bypassing the DLC stacks—as looping back on a single adapter.
Examples
The following command 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 4lsap
Use the lsap DLUR configuration command to create a SAP in the SNA session switch, or to enter DLUR SAP configuration mode. Use the no form of this command to delete a SAP and all SNA session switch links using the internal LAN interface.
lsap
lsap type adapter-number [lsap]
[no] lsap type adapter-number [lsap]Syntax Description
Default
The default value for lsap is hexadecimal C0.
Command Mode
DLUR configuration
Usage Guidelines
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 CIP internal LAN interface are used in the lsap command.
However, the lan type keyword is a little different. Where the type on the lan command is tokenring, the corresponding type 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.
Example
The following command defines an adapter type, an adapter number, and a local SAP:
lsap token 0 B0Related Commands
adapter
lanmaximum-lus
Use the maximum-lus TN3270 configuration command to limit the number of LU control blocks that will be allocated for TN3270 server use. Use the no form of this command to restore the default value.
maximum-lus number
no maximum-lusSyntax Description
Default
Because of the license structure, the default is 2100, which represents the limit of a typical license (2000) plus a 5 percent buffer. If you configure a value greater than the default, a license reminder is displayed.
Command Mode
TN3270 configuration
Usage Guidelines
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 constant warning displays, 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 CIP functions. The control blocks themselves take about 1 K bytes per LU. During session activity, a further 2 K 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.
Example
The following command allows 5000 LU control blocks to be allocated:
maximum-lus 5000Related Command
pu
preferred-nnserver
Use the preferred-nnserver DLUR configuration command to specify a preferred network node (NN) as server. Use the no form of this command to remove the preference.
preferred-nnserver name
no preferred-nnserverSyntax Description
Default
This command has no defaults.
Command Mode
DLUR configuration
Usage Guidelines
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 eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID 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.
Example
The following command selects SYD.VMX as the preferred NN server:
preferred-nnserver SYD.VMXpu (direct)
Use the pu TN3270 configuration command to create a PU entity that has its own direct link to a host, or to enter PU configuration mode. Use the no form of this command to remove the PU entity.
pu pu-name
pu pu-name idblk-idnum ip-address type adapter-number lsap [rmac rmac] [rsap rsap]
[lu-seed lu-name-stem]
no pu pu-nameSyntax Description
Defaults
No PU is defined.
The default remote SAP address is 04 (hexadecimal).
Command Mode
TN3270 configuration
Usage Guidelines
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 (direct) 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 CIP, the TN3270 server and the hosts should open different adapters in the same internal LAN. Using different adapters avoids any contention for SAP numbers, and is also necessary if you configure duplicate MAC addresses for fallback CSNA access to the host. By configuring the adapters in the same internal LAN, you achieve the same performance—bypassing the DLC stacks—as looping back on a single adapter.
Examples
The following commands configure 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
adapter
lanpu (DLUR)
Use the pu DLUR configuration command to create a PU entity that has no direct link to a host or to enter PU configuration mode. Use the no form of this command to remove the PU entity.
pu pu-name
pu pu-name idblk-idnum ip-address
no pu pu-nameSyntax Description
Default
No PU is defined.
Command Mode
DLUR configuration
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.
Example
The following sequence of commands 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.41show extended channel tn3270-server
Use the show extended channel tn3270-server privileged EXEC command to display current server configuration parameters and the status of the PUs defined in each TN3270 server.
show extended channel slot/2 tn3270-server
Syntax Description
slot/2
Specifies a particular CIP in the router where slot is the slot number. The port value for a TN3270 server is always 2.
Command Mode
Privileged EXEC
Sample Display
The following is sample output on the Cisco 7000 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-markdlur MPX.GOANCP status NOTQRYD 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 dlurdescribes significant fields in the display. Those fields not described correspond to configured values.
show extended channel tn3270-server client-ip-address
Use the show extended channel tn3270-server client-ip-address privileged EXEC command to display information about all clients at a specific IP address.
show extended channel slot/2 tn3270-server client-ip-address ip-address
Syntax Description
slot/2
(Optional) Specifies a particular CIP in the router where slot is the slot number. The port value for a TN3270 server will always be 2.
ip-address
IP address of the client.
Command Mode
Privileged EXEC
Sample Display
The following is sample output on the Cisco 7000 from the show extended channel tn3270-server client-ip-address command:
router# show extended channel 3/2 tn3270-server client-ip 171.69.136.130lu name client-ip:tcp state model frames in out idle for1 171.69.136.130:3736 INACTIVE 327904E 23 18 3:37:58pu is TN3PU02, lu is DYNAMIC type 0, negotiated TN3270bytes 509 in, 3438 out; RuSize 0 in, 0 out; NegRsp 0 in, 0 outpacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 outtraces:dynamic timer expiredwarm actpu reqwarm actpu reqwarm actpu reqwarm actpu reqwarm actpu reqwarm actpu reqwarm actpu reqIN len=9 2C0001010009838100OUT len=15 2Cxxxxxxxx0A038120F3000501FFIN len=9 2C000101000A838100IN len=170 xxxxxxxxxx0403922088000D818080OUT len=1730 2Cxxxxxxxx0B0381207EC3110000IN len=9 2C000101000B838100OUT len=55 2Dxxxxxxxx276B8000320F000000IN len=10 2D000101D427EB800032lu name client-ip:tcp state model frames in out idle for4 171.69.136.130:4074 INACTIVE 327904E 77 58 6:49:55pu is TN3PU02, lu is DYNAMIC type 0, negotiated TN3270bytes 1308 in, 21068 out; RuSize 0 in, 0 out; NegRsp 0 in, 0 outpacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 outtraces:Reply PSID pos rspactlu reqbind reqsdt requnbind reqClient disconnect reqnotify respwarm actpu reqOUT len=28 2Cxxxxxxxx16038100F14011C3F0IN len=9 2C0001040016838100OUT len=35 2Dxxxxxxxx3D6B80003201000000IN len=10 2D000104043DEB800032OUT len=132 2Cxxxxxxxx0303800005C21D607CIN len=9 2C0000040003838000IN len=20 xxxxxxxxxx110B80008106200C0600OUT len=12 2Cxxxxxxxx118B8000810620describes significant fields in the display.
show extended channel tn3270-server dlur
Use the show extended channel tn3270-server dlur privileged EXEC command to display information about the SNA session switch.
show extended channel slot/2 tn3270-server dlur
Syntax Description
slot/2
Specifies a particular CIP in the router where slot is the slot number. The port value for a TN3270 server will always be 2.
Command Mode
Privileged EXEC
Sample Display
The following is sample output on the Cisco 7000 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 ACTIVE
describes significant fields in the display.
show extended channel tn3270-server dlurlink
Use the show extended channel tn3270-server dlurlink privileged EXEC command to display information about the DLUR components.
show extended channel slot/2 tn3270-server dlurlink name
Syntax Description
slot/2
Specifies a particular CIP in the router where slot is the slot number. The port value for a TN3270 server will always be 2.
name
Name of the SNA session switch link to be displayed.
Command Mode
Privileged EXEC
Sample Display
The following is sample output on the Cisco 7000 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 1033describes significant fields in the display.
show extended channel tn3270-server pu
Use the show extended channel tn3270-server pu privileged EXEC command to display the PU configuration parameters, statistics and all the LUs currently attached to the PU.
show extended channel slot/2 tn3270-server pu pu-name
Syntax Description
Command Mode
Privileged EXEC
Usage Guideline
The display shown depends on whether the PU is a direct PU or a SNA session switch PU.
Sample Displays
The following is sample output on the Cisco 7000 from the show extended channel tn3270-server pu command for a direct PU:
router# show extended channel 3/2 tn3270-server pu EXT2name(index) ip:tcp xid state link destination r-lsapEXT2(1) 172.28.1.106:23 05D18092 ACTIVE tok 0 4000.7470.00e7 08 04idle-time 0 keepalive 0 unbind-act discon generic-pool permbytes 100 in, out; frames 90 in, 4 out; NegRsp 6 in, 0 outactlus 4, dactlus 0, binds 0lu name client-ip:tcp state model frames in out idle for1 EXT2001 171.69.176.34:1897 ACTIVE 327805 1 1 4:32:492 EXT2002 never connected ACTIVE 1 1 4:32:49The following is sample output on the Cisco 7000 from the show extended channel tn3270-server pu command for a SNA session switch PU:
router# show extended channel 3/2 tn3270-server pu INT1name(index) ip:tcp xid state link destination r-lsapINT1(5) 172.28.1.106:23 05D18091 ACTIVE dlur MPX.GOAN1idle-time 0 keepalive 0 unbind-act discon generic-pool permbytes 50 in, out; frames 87 in, 2 out; NegRsp 3 in, 0 outactlus 2, dactlus 0, binds 0lu name client-ip:tcp state model frames in out idle for1 GOAN1X01 never connected ACTIVE 1 1 0:32:142 GOAN1X02 never connected ACTIVE 1 1 0:32:14describes significant fields in the display.
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 CIP interface in a Cisco 7000 series.
show extended channel slot/2 tn3270-server pu pu-name lu locaddr [history]
Syntax Description
Command Mode
Privileged EXEC
Sample Displays
The following is sample output on the Cisco 7000 from the show extended channel tn3270-server pu lu command for a direct PU:
router# show extended channel 3/2 tn3270 pu ext2 lu 3lu name client-ip:tcp state model frames in out idle for3 EXT2003 171.69.176.77:3829 ACTIVE 327902E 8 9 0:4:43pu is EXT2, lu is DYNAMIC type 0, negotiated TN3270bytes 203 in, 2954 out; RuSize 0 in, 0 out; NegRsp 1 in, 0 outpacing window 0 in, 1 out; credits 0 in, queue-size 0 in, 0 outThe following is sample output on the Cisco 7000 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 1lu name client-ip:tcp state model frames in out idle for1 GOAN1X01 171.69.176.77:3828 ACTIVE 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 on the Cisco 7000 from the show extended channel tn3270-server pu lu history command:
router# show extended channel 3/2 tn3270 pu pus20 lu 1 historylu name client-ip:tcp state model frames in out idle for1 PUS20001 192.195.80.40:2480 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 2C0001010001838100describes significant fields in the display.
shutdown
Use the shutdown interface configuration command to shutdown a physical interface or the internal LAN interface on the CIP when you are in interface configuration mode. The shutdown command also shuts down TN3270 entities, such as PU, DLUR, and DLUR SAP, depending on which configuration mode you are in when the command is issued. Use the no form of this command to restart the interface or entity. The entity affected depends on the mode in which the command is issued.
shutdown
no shutdownSyntax Description
This command has no arguments or keywords.
Default
The interface or entity is enabled.
Command Modes
CIP interface configuration
TN3270 configuration
PU configuration
DLUR configuration
DLUR SAP configuration
Usage Guidelines
In CIP interface configuration mode, the command applies to the entire CIP.
In TN3270 configuration mode, the command applies to the whole TN3270 Server.
In PU configuration mode, the command applies to the DLUR or direct PU.
In DLUR configuration mode, the command applies to the whole DLUR subsystem.
In DLUR SAP configuration, mode the command applies to the local SAP.
Example
The following command issued in TN3270 configuration mode shuts down the entire TN3270 server:
shutdowntcp-port
Use the tcp-port TN3270 configuration command to override the default TCP port setting of 23. Use the no form of this command to restore the default.
tcp-port port-number
no tcp-portSyntax 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 configuration mode, the default is 23.
In PU configuration mode the default is the value currently configured in TN3270 configuration mode.
Command Modes
TN3270 configuration
PU configuration
Usage Guidelines
The tcp-port command can be entered in either TN3270 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.
Example
The following command entered in TN3270 configuration mode returns the TCP port value to 23:
no tcp-porttiming-mark
Use the timing-mark TN3270 configuration mode command to select whether a DO TIMING-MARK is transmitted when the host application needs an SNA response (definite or pacing response). Use the no form of the command to turn off DO TIMING-MARK transmission except as used by the keepalive function.
timing-mark
no timing-markSyntax Description
This command has no arguments or key words.
Default
No DO TIMING-MARKS are transmitted except by keepalive.
Command Mode
TN3270 configuration
Usage Guidelines
If timing-mark is configured the TN3270 server will send DO TIMING-MARK as necessary to achieve an end-to-end response protocol. Specifically, DO TIMING-MARK will be sent if any of the following are true:
•
•
The use of the timing-mark command can degrade performance. Some clients do not support timing-mark used in this way. Therefore, timing-mark should only be configured where both of the following are true:
•
•
Example
The following command enables TIMING-MARK transmission:
timing-markRelated Commands
idle-timer
keepalivetn3270-server
Use the tn3270-server interface configuration command to start the TN3270 server on a CIP or to enter TN3270 configuration mode. Use the no form of this command to disable all TN3270 server activity on a CIP.
tn3270-server
no tn3270-serverSyntax Description
This command has no arguments or keywords.
Default
No TN3270 server function is enabled.
Command Mode
Interface configuration
Usage Guidelines
Only one TN3270 server can run on a CIP. It will always be configured on port 2, which is the internal LAN interface port.
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.
Example
The following command starts the TN3270 server and enters TN3270 configuration mode:
tn3270-serverunbind-action
Use the unbind-action TN3270 configuration command to select what action to take when the TN3270 server receives an UNBIND. Use the no form of this command to restore the default.
unbind-action {keep | disconnect}
no unbind-actionSyntax Description
Defaults
In TN3270 configuration mode, the default is disconnect.
In PU configuration mode the default is the value currently configured in TN3270 configuration mode.
Command Modes
TN3270 configuration
PU configuration
Usage Guidelines
The unbind-action command can be entered in either TN3270 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.
Example
The following command prevents automatic disconnect:
unbind-action keepvrn
Use the vrn DLUR SAP configuration command to tell the SNA session switch which connection network the internal adapter interface on the CIP card belongs to. Use the no form of this command to remove a network name.
vrn vrn-name
no vrnSyntax Description
Default
The adapter is not considered to be part of a connection network.
Command Mode
DLUR SAP configuration
Usage Guidelines
The vrn 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 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 eight characters long; for example, RA12.NODM1PP. The portion of the name before the period is the NETID and is shared between entities in the same logical network.
Example
The following command sets a VRN name for the TN3270 internal adapter on the CIP:
vrn SYD.BLAN25Related Commands
adapter
lanCisco Connection Online
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
•
•
•
•
•
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
Note
Cisco Connection Documentation
The complete caveats against this release are available on the Cisco Connection Documentation, Enterprise Series CD—formerly UniverCD—which is the Cisco library of product information on CD-ROM. On CD, access the Cisco IOS 11.0 caveats in the Cisco IOS Release 11.0 database.
The CD is updated and shipped monthly so it might be more current than printed documentation. To order the CD, contact your local sales representative or call Customer Service. The CD is available both as a single CD and as an annual subscription. You can also access Cisco technical documentation on the World Wide Web URL
http://www.cisco.com78-3610-09
