Cisco_Systems_Server_11.0

Doc. No. 78-3610-09

Cisco IOS Release 11.0 BT Release Note and Update to Con???guration 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

Cisco IOS 11.0(11)BT

Cisco IOS 11.0(12)BT

Cisco IOS 11.0(13a)BT

Note Cisco IOS Release 11.0(13)BT was renumbered and released as 11.0(13a)BT.)

??? Cisco IOS 11.0(14)BT, Cisco IOS 11.0(14a)BT1

Note Shipment of Cisco IOS Release 11.0(14)BT was halted due to CSCdj05366. A ???x was implemented and the release was renumbered and released as 11.0(14a)BT1.

Corporate Headquarters

Cisco Systems, Inc.

170 West Tasman Drive

San Jose, CA 95134-1706

USA

Introduction

???

Cisco IOS 11.0(15)BT

Cisco IOS 11.0(16)BT

Cisco IOS 11.0(17)BT

Cisco IOS 11.0(18)BT

Cisco IOS 11.0(19)BT

Cisco IOS 11.0(20)BT

Cisco IOS 11.0(21)BT

Cisco IOS 11.0(22)BT

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:

???Release Note, page 2

??? Platform Support, page 3

???

???Cisco IOS Packaging, page 3

???Boot ROM Requirements, page 3

???CIP Boot Image Requirements, page 3

???Memory Requirements, page 3

???Microcode Software, page 4

???New Software Features in 11.0(10)BT, page 4 Update to Con???guration Guide, page 4

Update to Command Reference, page 19 Cisco Connection Online, page 57

Cisco Connection Documentation, page 57

Use this document in conjunction with the Router Products Release Notes for Cisco IOS

Release 11.0 and the Cisco IOS Release 11.0 con???guration guide and command reference

publications, speci???cally the Router Products Con???guration Guide Chapters 1 to 6 , Router Products Con???guration 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 To enable the TN3270 server feature, you must have a CIP card installed in a Cisco 7000 series router or Cisco 7500 series router. The TN3270 server is different from the TN3270 terminal emulation access feature described in the ???Con???guring TN3270??? chapter of the Access and Communication Servers Con???guration Guide .

2 Cisco IOS Release 11.0 BT Release Note and Update to Con???guration Guides and Command References

Release Note

Platform Support

Cisco IOS Release 11.0 BT supports the following router platforms:

???

Cisco 7500 series

Cisco 7000 series and Cisco 7000 series with RSP7000

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.

???

Enterprise (this feature set includes CIP)

Enterprise/CIP2

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 Table 1 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 Table 2. The CIP supports up to 128 Mb of memory.

Table 2 11.0 BT Memory Requirements

Cisco IOS Release 11.0 BT Release Note and Update to Configuration Guides and Command References 3

Update to Configuration Guide

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:

???Load Balancing and Redundancy???Provides effective CIP resource utilization and more consistent response times. (This feature is initially provided by means of an external, prototype implementation.)

???End-to-End Session Visibility???Provides enhanced resource management.

???Systems Network Architecture (SNA) Session Switching???Off-loads VTAM by providing session routing.

???TN3270E Support???In combination with a TN3270E client, provides advanced SNA management and SNA functionality, including printer support.

???Dynamic De???nition of Dependent Logical Units (LU)???Provides simpli???ed con???guration and network de???nition at the router and in VTAM.

???Dynamic Allocation of LUs???Makes ef???cient use of LU pool resources while supporting multiple SNA model types.

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 Of???oad, 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 Con???guration Guide

The information that follows is an update to the Router Products Con???guration Guide, Chapters 23 to 33. Add the TN3270 information as a standalone chapter following page 33-22.

4 Cisco IOS Release 11.0 BT Release Note and Update to Con???guration Guides and Command References

Cisco???s Implementation of TN3270 on a Channel Interface Processor

Con???guring 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 Figure 1. Functionally, it is useful to view the TN3270 server from two different perspectives: SNA functions and Telnet Server functions.

???SNA 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 traf???c by establishing APPN links with the primary LU hosts directly.

???Telnet Server Functions

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 speci???ed in RFC 1576 (referred to as ???traditional TN3270???) and RFC 1647 (referred to as ???TN3270E???).

Figure 1 TN3270 Implementation

S4735

TN3270 client

Because the TN3270 server con???guration is performed after an interface is con???gured for CIP SNA (CSNA) support, TN3270 con???guration issues and tasks are addressed separately from the interface con???guration tasks. The description of TN3270 con???guration issues and tasks begins in the section ???Con???guring TN3270 on a Channel Interface Processor,??? later in this chapter.

Configuring TN3270 Server on the Channel Interface Processor 5

Configuring TN3270 on a Channel Interface Processor

Note To enable the TN3270 server feature, you must have a CIP installed in a Cisco 7000 family router. The TN3270 server is different from the TN3270 terminal emulation access feature described in the ???Con???guring TN3270??? chapter of the Access Services Con???guration Guide .

Con???guring 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:

???

Dynamic LU Allocation

Formation of LU Model Type and Number

Speci???c LU Allocation

SNA Session Switch???End Node DLUR

Multiple Hosts Support

You will also need to understand the following information before proceeding with TN3270 con???guration tasks:

???

VTAM Host Con???guration Considerations for Dynamic LU Allocation

TN3270 Con???guration Modes

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:

???Form an EBCDIC string based on the model type and number requested by the client (see ???Formation of LU Model Type and Number??? for the algorithm used). This string is used as a ???eld in a Reply product set ID (PSID) network management vector transport (NMVT).

???Allocate a LOCADDR from the next available LU in the generic LU pool. This LOCADDR is used in the NMVT.

???Send the formatted Reply PSID NMVT to VTAM.

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 ???nd a match in the sample con???guration shown in Figure 2. 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 ???nd 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:

???IBM-<XXXX>-<Y>[-E]: This will be formatted as ???XXXX0Y???or ???XXXX0YE??? in the model type and number ???eld in the Reply PSID NMVT.

6 Con???guring TN3270 Server on the Channel Interface Processor

Configuring TN3270 on a Channel Interface Processor

???IBM-DYNAMIC: This will result in ???DYNAMIC??? being put in the model type and number ???eld. The VTAM con???guration will need to have ???DYNAMIC??? de???ned as a template in the LU group. In fact ???IBM-ZZ..Z,??? where ???ZZ..Z??? does not match the preceding syntax, will be forwarded as ???ZZ..Z.???

Note The ???E??? in the model string refers to 3270 extended datastream. It has no connection with the ???E??? in ???TN3270E???.

???Any other string is forwarded as is.

???In all cases, the string forwarded is translated from ASCII to EBCDIC and truncated at seven characters.

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 ???ow. All other clients require 3270 datastream on that ???ow. 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:

???If the client has negotiated to receive BIND-IMAGE, the character ???S??? is overlaid on the ???fth character of the string, or appended if the string is less than ???ve characters. (See Table 3.)

Table 3 Examples of Model String Mapping

Speci???c LU Allocation

A TN3270E client can request a speci???c 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 con???gured (that is, on DLUR PUs) the TN3270 server learns the

LU names from the ACTLUs.

For direct PUs, a ???seed??? name can be con???gured 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.

Configuring TN3270 Server on the Channel Interface Processor 7

VTAM Host Configuration Considerations for Dynamic LU Allocation

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 simpli???es the con???guration to support speci???cally requested LUs such as printers.

Multiple Hosts Support

The TN3270 server supports access to multiple hosts via the con???guration on a PU basis (Table 4). PUs connected to different hosts or applications can be con???gured with different IP address.

Table 4 Direct PU Con???guration in Router

From the pu (direct) TN3270 con???guration command values shown in Table 4, 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 de???ned 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 ???ow directly between the target host and the client without needing to go through the controlling VTAM.

VTAM Host Con???guration Considerations for Dynamic LU Allocation

Other non-Cisco implementations of TN3270 support depend on prede???ned, 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 con???gurations by using a VTAM release 3.4 feature, dynamic de???nition 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 de???ne any LU con???guration 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 de???ned in VTAM with LUSEED and LUGROUP parameters as shown in Figure 2.

8 Con???guring TN3270 Server on the Channel Interface Processor

VTAM Host Configuration Considerations for Dynamic LU Allocation

With the con???guration shown in Figure 2 de???ned 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 speci???cally de???ned LUs. In the sample con???guration shown in Figure 2, 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 speci???c LU cache and reserved for speci???c LU name requests only.

To allow suf???cient 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 de???ned 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 con???guration using the generic-pool deny TN3270 con???guration command.

Configuring TN3270 Server on the Channel Interface Processor 9

TN3270 Configuration Modes

After the VTAM activation, the server can support session requests from clients using dynamic or speci???c LU allocation.

TN3270 Con???guration Modes

The TN3270 con???guration modes and router command prompts are described in the following sections and displayed in Figure 3. The TN3270 server can be con???gured only on Port 2, the internal LAN port, of a CIP card.

Some con???guration 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 speci???c 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 ???rst 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 con???guration mode, perform the following task beginning in TN3270 DLUR con???guration mode:

To return later to the DLUR LSAP con???guration mode on the same entity, perform the following task beginning in TN3270 DLUR con???guration mode:

To remove an entity, the same identi???cation parameters are needed. Perform the following task beginning in TN3270 DLUR con???guration mode:

TN3270 con???guration modes described in this section include the following:

???TN3270 Server Con???guration Mode

???DLUR Con???guration Mode

???DLUR SAP Con???guration Mode

???PU Con???guration Mode

???Commands Allowed in Multiple Modes

10 Con???guring TN3270 Server on the Channel Interface Processor

TN3270 Configuration Modes

TN3270 configuration mode

Figure 3 TN3270 Con???guration Modes

Prompt:

tn3270-server>

Prompt:

TN3270 DLUR

configurationtn3270-dlur> mode

TN3270 Server Con???guration Mode

From interface con???guration mode, tn3270-server command puts you in TN3270 server con???guration mode.

Prompt:

tn3270-server>

DLUR Con???guration Mode

From TN3270 server con???guration mode, the dlur command puts you in DLUR con???guration mode.

Prompt:

tn3270-dlur>

Configuring TN3270 Server on the Channel Interface Processor 11

TN3270 Configuration Modes

DLUR SAP Con???guration Mode

From DLUR server con???guration mode, lsap command puts you in DLUR SAP con???guration mode.

Prompt:

tn3270-dlur-lsap>

PU Con???guration Mode

There are two paths to PU con???guration mode: from the TN3270 server con???guration mode, or from the DLUR con???guration mode. In either mode, the pu command puts you in PU con???guration mode.

From TN3270 con???guration 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 con???guration mode, the pu command to create a new PU is:

pu pu-name idblk-idnum ip-address

From either mode, to return to PU con???guration 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 con???guration mode, or in either variation of PU con???guration 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 con???guration mode override settings made in TN3270 con???guration mode. In addition, the no form of these commands entered in PU con???guration mode will restore the command value entered in TN3270 command mode.

12 Con???guring TN3270 Server on the Channel Interface Processor

TN3270 Configuration Task List

TN3270 Con???guration Task List

The following sections describe how to con???gure TN3270 server support on the CIP. Not all tasks are required. Refer to ???TN3270 Con???guration Example??? for con???guration examples.

Note The TN3270 server is con???gured on an internal LAN interface in the CIP, which is port 2 of a CIP. Port 0 and port 1 represent physical interface ports; port 2 is a ???virtual??? port and is always reserved for the internal LAN interface.

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 con???gure your PUs under DLUR. In this instance, perform the following tasks:

???

Con???gure SNA Support

Con???gure TN3270 Server

Con???gure DLUR

Con???gure SAPs under DLUR

Con???gure PUs under DLUR

Monitor the TN3270 Server

Note You can also use DLUR to reach a mix of APPN and non-APPN hosts. The host owning the PUs must be an APPN network node that also supports the subarea (that is, an interchange node). When an SLU starts a session with any of the APPN hosts, it can use session switching to reach that host directly. When it starts a session with a non-APPN host, the traf???c will be routed through the owning host.

Task List for Non-APPN Hosts

When the host site does not use APPN, or you have a single APPN host, you con???gure your PU parameters for a directly connected host. In this instance, perform the following tasks:

???

Con???gure SNA Support

Con???gure TN3270 Server

Con???gure PU Parameters on the TN3270 Server

Monitor the TN3270 Server

Con???gure SNA Support

CIP SNA support (CSNA) must be con???gured prior to con???guring TN3270 support. Refer to the section ???Con???gure IBM Channel Attach for CSNA Support,??? in the ???Con???guring IBM Channel Attach??? chapter of Bridging and IBM Networking Con???guration Guide .

After you have con???gured CSNA support, proceed with TN3270 con???guration.

Configuring TN3270 Server on the Channel Interface Processor 13

TN3270 Configuration Task List

Con???gure 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 con???guration mode:

When you use the tn3270-server command, you enter TN3270 con???guration mode and can use all other commands in the task list. You can later override many con???guration values you enter in TN3270 con???guration mode from PU con???guration 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 con???guration and can be optionally altered at each con???guration level.

Con???gure PU Parameters on the TN3270 Server

This task is required when con???guring PUs that do not use the SNA Session Switch feature. To con???gure PU parameters for the TN3270 server, perform the following tasks beginning in TN3270 con???guration mode.

14 Con???guring TN3270 Server on the Channel Interface Processor

TN3270 Configuration Task List

When you use the pu command, you enter PU con???guration mode and can use all other commands in this task list. Con???guration values you enter in PU con???guration mode will override other values entered while in TN3270 con???guration mode. In addition, you can enter PU con???guration mode from DLUR con???guration mode when con???guring PUs that are connected by means of DLUR.

If you are con???guring PUs for directly connected hosts, you need not perform any additional con???guration tasks.

Con???gure DLUR

This task is required when con???guring DLUR connected hosts. To con???gure DLUR parameters for the TN3270 server, perform the following tasks beginning in TN3270 con???guration mode.

Con???gure SAPs under DLUR

To con???gure SAPs under the DLUR function, perform the following tasks beginning in DLUR con???guration mode.

Configuring TN3270 Server on the Channel Interface Processor 15

TN3270 Configuration Task List

Con???gure PUs under DLUR

This task is required when con???guring DLUR connected hosts. To con???gure PUs under the DLUR function, perform the following tasks beginning in DLUR con???guration mode.

The pu command entered in DLUR con???guration mode has different parameters than when it is entered from TN3270 con???guration mode.

Monitor the TN3270 Server

The following table lists some of the monitoring tasks speci???c 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:

Display the status of the LU.

show extended channel tn3270-server pu-name lu lu-number [history]

16 Con???guring TN3270 Server on the Channel Interface Processor

TN3270 Configuration Task List

TN3270 Con???guration Example

The following con???guration has three PUs using DLUR and two more with direct connections.

The initial CIP con???guration is as follows:

interface Channel2/2

ip address 10.10.20.126 255.255.255.128 no ip redirects

no ip directed-broadcast ip pim query-interval 0 ip igmp query-interval 0 no ip route-cache

no keepalive

no clns checksum

clns congestion-threshold 0 clns erpdu-interval 0

clns rdpdu-interval 0 no clns route-cache no clns send-erpdu

no clns send-rdpdu lan TokenRing 0

source-bridge 223 1 2099 adapter 0 4100.cafe.0001 llc2 N1 2057

adapter 1 4100.cafe.0002 llc2 N1 2057

Con???guration dialog to con???gure 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 2 router(config)#int channel 2/2

!create TN3270 Server entity

router(config-if)#tn3270-server

!set server-wide defaults for PU parameters router(cfg-tn3270)#keepalive 0 router(cfg-tn3270)#unbind-action disconnect router(cfg-tn3270)#generic-pool permit

!define DLUR parameters and enter DLUR configuration mode router(cfg-tn3270)#dlur SYD.TN3020 SYD.VMG

!create PUs under DLUR

!Note that the first two share an IP address router(tn3270-dlur)#pu pu0 05d99001 10.10.20.1 router(tn3270-dlur-pu)#pu pu1 05d99002 10.10.20.1 router(tn3270-dlur-pu)#pu pu2 05d99003 10.10.20.2

!create a DLUR LSAP and enter DLUR LSAP configuration mode router(tn3270-dlur-pu)#lsap token-adapter 1

!specify the VRN name of the network containing this lsap router(tn3270-dlur-lsap)#vrn syd.lan4

!create a link from this lsap

router(tn3270-dlur-lsap)#link hosta rmac 4100.cafe.0001 rsap 8 router(tn3270-dlur-lsap)#link hostb rmac 4000.7470.0009 rsap 4 router(tn3270-dlur-lsap)#exit

router(tn3270-dlur)#exit

Configuring TN3270 Server on the Channel Interface Processor 17

Update 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 con???gure TN3270 support on the Channel Interface

Processor (CIP). For TN3270 con???guration tasks and examples, refer to the ???Con???guring TN3270

Server on the Channel Interface Processor??? update chapter of this Release Note.

The following commands are documented in this update chapter:

???

dlur, page 20

dlus-backup, page 21

generic-pool, page 22

idle-time, page 24

keepalive, page 25

link, page 26

lsap, page 28

maximum-lus, page 30

preferred-nnserver, page 31

pu (DLUR), page 35

pu (direct), page 32

show extended channel tn3270-server, page 36

show extended channel tn3270-server client-ip-address, page 39

show extended channel tn3270-server dlur, page 42

show extended channel tn3270-server dlurlink, page 44

show extended channel tn3270-server pu, page 45

show extended channel tn3270-server pu lu, page 48

shutdown, page 51

tcp-port, page 52

tn3270-server, page 54

timing-mark, page 53

unbind-action, page 55

vrn, page 56

TN3270 Server Commands 19

dlur

Use the dlur TN3270 con???guration command to enable the Systems Network Architecture (SNA) session switch function on the CIP, or to enter dependent logical unit requester (DLUR) con???guration 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 dlur

Usage Guidelines

If the SNA session switch function is already enabled, the dlur command with no arguments puts you in DLUR con???guration mode.

Several parameters in the DLUR con???guration mode consist of fully quali???ed names, as de???ned by the APPN architecture. Fully quali???ed 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 quali???ed 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 de???ned beneath it.

Example

The following command performs two functions: It enters DLUR con???guration mode; and it enables the DLUR function and de???nes 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.VMG

20 TN3270 Server Commands

dlus-backup

Use the dlus-backup DLUR con???guration 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-backup

Syntax Description

Default

No backup DLUS is speci???ed.

Command Mode

DLUR con???guration

Usage Guidelines

Only one backup DLUS can be speci???ed per CIP. If the backup DLUS speci???ed in the dlus-backup command is in use when a no dlus-backup is issued, the connection is not torn down.

Example

The following command speci???es SYD.VMX as the backup DLUS:

dlus-backup SYD.VMX

TN3270 Server Commands 21

generic-pool

Use the generic-pool TN3270 con???guration command to specify whether or not left over LUs will be made available to TN3270 sessions that do not request a speci???c 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-pool

Defaults

In TN3270 con???guration mode, generic pool use is permitted.

In PU con???guration mode, the default is the value currently con???gured in TN3270 con???guration mode.

Command Modes

TN3270 con???guration

PU con???guration

Usage Guidelines

A left over LU is de???ned as one for which all of the following conditions are true:

???The system services control point (SSCP) did not send an ACTLU during PU start up; and

???The PU controlling the LU is capable of carrying product set ID (PSID) vectors on network management vector transport (NMVT) messages, thus allowing dynamic de???nition of dependent LU (DDDLU) operation for that LU.

All LUs in the generic pool are, by de???nition, DDDLU capable.

Values entered for generic-pool in TN3270 con???guration mode apply to all PUs for that TN3270 server but can be changed in PU con???guration mode.

In PU con???guration mode, a no generic-pool command will restore the generic-pool value entered in TN3270 command mode.

In TN3270 con???guration 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 speci???ed 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.

22 TN3270 Server Commands

idle-time

Use the idle-time TN3270 con???guration 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-time

Defaults

The default in TN3270 con???guration mode is that the session is never disconnected (0).

The default in PU con???guration mode is the value currently con???gured in TN3270 con???guration mode.

Command Modes

TN3270 con???guration

PU con???guration

Usage Guidelines

The idle-time command can be entered in either TN3270 con???guration mode or PU con???guration mode. A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in PU con???guration mode.

A no idle-time command entered in PU con???guration 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 For the purposes of idle-time logic, TIMING-MARKs generated by the keepalive logic do not constitute ???activity.???

Examples

The following command sets an idle-time disconnect value of 10 minutes:

idle-time 600

The following command entered in TN3270 con???guration mode sets the default idle-time disconnect value to 0, or never disconnect:

no idle-time

24 TN3270 Server Commands

keepalive

Use the keepalive TN3270 con???guration 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 keepalive

Defaults

The default in TN3270 con???guration mode is 1800 seconds (30 minutes).

The default in PU con???guration mode is the value currently con???gured in TN3270 con???guration mode.

Command Modes

TN3270 con???guration

PU con???guration

Usage Guidelines

The keepalive command can be entered in either TN3270 con???guration mode or PU con???guration mode. A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in PU con???guration mode. A no keepalive command entered in PU con???guration 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 900

The following command entered in TN3270 con???guration mode sets the keepalive disconnect value to 1800 seconds, the default:

no keepalive

TN3270 Server Commands 25

link

Use the link DLUR SAP con???guration command to de???ne and activate a link to a host. Use the no form of this command to delete the link de???nition.

link name [rmac rmac] [rsap rsap] no link name

Defaults

No DLUR link is de???ned.

The default remote SAP address is 04 (hexadecimal).

Command Mode

DLUR SAP con???guration

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 de???nition, using the no link command, and recreating the link de???nition.

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 con???gure duplicate MAC addresses for fallback CSNA access to the host. By con???guring 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 de???nes a link name and a remote SAP address:

link LINK5 rsap 08

26 TN3270 Server Commands

lsap

Use the lsap DLUR con???guration command to create a SAP in the SNA session switch, or to enter DLUR SAP con???guration 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]

Default

The default value for lsap is hexadecimal C0.

Command Mode

DLUR con???guration

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 con???guration mode.

The lsap command can be entered only in DLUR con???guration mode.

The lsap command uses values that are de???ned in two other commands: the lan internal LAN con???guration command and the adapter internal LAN con???guration command. The lan type and adapter adapter-number values con???gured 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.

28 TN3270 Server Commands

maximum-lus

Use the maximum-lus TN3270 con???guration 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-lus

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 con???gure a value greater than the default, a license reminder is displayed.

Command Mode

TN3270 con???guration

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 de???nition 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 5000

Related Command

30 TN3270 Server Commands

preferred-nnserver

Use the preferred-nnserver DLUR con???guration 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-nnserver

Syntax Description

Default

This command has no defaults.

Command Mode

DLUR con???guration

Usage Guidelines

Fully quali???ed 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 quali???ed 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 speci???ed, the DLUR will request NN server support from the ???rst suitable node with which it makes contact. If refused, it will try the next one, and so on.

If a preferred server is speci???ed, 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.VMX

TN3270 Server Commands 31

pu (direct)

The default remote SAP address is 04 (hexadecimal).

Command Mode

TN3270 con???guration

Usage Guidelines

If the PU is already created, the pu pu-name command with no arguments puts you in PU con???guration mode, where you can modify an existing PU entity.

The pu (direct) command uses values that are de???ned in two other commands: the lan internal LAN con???guration command and the adapter internal LAN con???guration command. The lan type and adapter adapter-number values con???gured on the CIP internal LAN interface are used in the pu command.

Examples

The following commands con???gure the TN3270 server to be active, and has one PU, CAPPU1, trying to connect in. An LU seed using hexadecimal digits is de???ned.

tn3270-server

pu CAPPU1 05D18101 10.14.20.34 token-adapter 3 rmac 4000.0501.0001 lu-seed CAP01L##

The following example shows different adapter numbers con???gured on the same internal LAN to avoid SAP contention. The host uses SAP 4 on token ring adapter 0:

lan tokenring 0

adapter 0 4000.0000.0001 adapter 1 4000.0000.0002

tn3270-server

pu PU1 05d00001 10.0.0.1 token-adapter 1 8 rmac 4000.0000.0001 rsap 4

TN3270 Server Commands 33

pu (DLUR)

Use the pu DLUR con???guration command to create a PU entity that has no direct link to a host or to enter PU con???guration 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-name

Usage Guidelines

If the PU is already created, the pu pu-name command with no arguments puts you in PU con???guration 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 de???ned with PUs that have

LOGAPPL=TSO.

Example

The following sequence of commands de???ne 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.40 pu p1 05D99002 192.195.80.40 pu p2 05D99003 192.195.80.41

TN3270 Server Commands 35

show extended channel tn3270-server

Use the show extended channel tn3270-server privileged EXEC command to display current server con???guration parameters and the status of the PUs de???ned in each TN3270 server.

show extended channel slot/2 tn3270-server

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

Table 5 describes signi???cant ???elds in the display. Those ???elds not described correspond to con???gured values.

Table 5 Show tn3270-server Field Descriptions

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 speci???c IP address.

show extended channel slot/2 tn3270-server client-ip-address ip-address

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.130

TN3270 Server Commands 39

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

Sample Display

The following is sample output on the Cisco 7000 from the show extended channel tn3270-server dlur command:

Table 7 describes signi???cant ???elds in the display.

Table 7 Show tn3270-server dlur Field Descriptions

42 TN3270 Server Commands

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

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 P390

Table 8 describes signi???cant ???elds in the display.

Table 8 Show tn3270-server dlurlink Field Descriptions

44 TN3270 Server Commands

show extended channel tn3270-server pu

Use the show extended channel tn3270-server pu privileged EXEC command to display the PU con???guration parameters, statistics and all the LUs currently attached to the PU.

show extended channel slot/2 tn3270-server pu pu-name

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 EXT2

The 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 INT1

TN3270 Server Commands 45

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]

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 3

The 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 1

The 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 history

pu is PUS20, lu is DYNAMIC type 2, negotiated TN3270

bytes 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 out

traces:

48 TN3270 Server Commands

shutdown

Use the shutdown interface con???guration command to shutdown a physical interface or the internal LAN interface on the CIP when you are in interface con???guration mode. The shutdown command also shuts down TN3270 entities, such as PU, DLUR, and DLUR SAP, depending on which con???guration 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 shutdown

Syntax Description

This command has no arguments or keywords.

Default

The interface or entity is enabled.

Command Modes

CIP interface con???guration

TN3270 con???guration

PU con???guration

DLUR con???guration

DLUR SAP con???guration

Usage Guidelines

In CIP interface con???guration mode, the command applies to the entire CIP.

In TN3270 con???guration mode, the command applies to the whole TN3270 Server.

In PU con???guration mode, the command applies to the DLUR or direct PU.

In DLUR con???guration mode, the command applies to the whole DLUR subsystem.

In DLUR SAP con???guration, mode the command applies to the local SAP.

Example

The following command issued in TN3270 con???guration mode shuts down the entire TN3270 server:

shutdown

TN3270 Server Commands 51

tcp-port

Use the tcp-port TN3270 con???guration 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-port

Defaults

In TN3270 con???guration mode, the default is 23.

In PU con???guration mode the default is the value currently con???gured in TN3270 con???guration mode.

Command Modes

TN3270 con???guration

PU con???guration

Usage Guidelines

The tcp-port command can be entered in either TN3270 con???guration mode or PU con???guration mode. A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in PU con???guration mode. The tcp-port command affects only future TN3270 sessions.

The no tcp-port command entered in PU con???guration mode removes the override.

Example

The following command entered in TN3270 con???guration mode returns the TCP port value to 23:

no tcp-port

52 TN3270 Server Commands

timing-mark

Use the timing-mark TN3270 con???guration mode command to select whether a DO TIMING-MARK is transmitted when the host application needs an SNA response (de???nite 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-mark

Syntax Description

This command has no arguments or key words.

Default

No DO TIMING-MARKS are transmitted except by keepalive.

Command Mode

TN3270 con???guration

Usage Guidelines

If timing-mark is con???gured the TN3270 server will send DO TIMING-MARK as necessary to achieve an end-to-end response protocol. Speci???cally, DO TIMING-MARK will be sent if any of the following are true:

???The host application has requested a pacing response.

???The host application has requested a De???nite Response, and either the client is not using TN3270E, or the request is not Begin Chain.

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 con???gured where both of the following are true:

???

All clients support this usage.

The application bene???ts from end-to-end acknowledgment.

Example

The following command enables TIMING-MARK transmission:

timing-mark

Related Commands

idle-timer keepalive

TN3270 Server Commands 53

tn3270-server

Use the tn3270-server interface con???guration command to start the TN3270 server on a CIP or to enter TN3270 con???guration mode. Use the no form of this command to disable all TN3270 server activity on a CIP.

tn3270-server no tn3270-server

Syntax Description

This command has no arguments or keywords.

Default

No TN3270 server function is enabled.

Command Mode

Interface con???guration

Usage Guidelines

Only one TN3270 server can run on a CIP. It will always be con???gured 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 de???nitions deleted from the router con???guration. To restart a TN3270 server, you must recon???gure all parameters.

Example

The following command starts the TN3270 server and enters TN3270 con???guration mode:

tn3270-server

54 TN3270 Server Commands

unbind-action

Use the unbind-action TN3270 con???guration 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-action

Defaults

In TN3270 con???guration mode, the default is disconnect.

In PU con???guration mode the default is the value currently con???gured in TN3270 con???guration mode.

Command Modes

TN3270 con???guration

PU con???guration

Usage Guidelines

The unbind-action command can be entered in either TN3270 con???guration mode or PU con???guration mode. A value entered in TN3270 mode applies to all PUs for that TN3270 server, except as overridden by values entered in PU con???guration mode. The unbind-action command affects currently active and future TN3270 sessions

The no unbind-action command entered in PU con???guration mode removes the override.

The unbind-action command affects currently active and future TN3270 sessions.

Example

The following command prevents automatic disconnect:

unbind-action keep

TN3270 Server Commands 55

vrn

Use the vrn DLUR SAP con???guration 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 vrn

Syntax Description

Default

The adapter is not considered to be part of a connection network.

Command Mode

DLUR SAP con???guration

Usage Guidelines

The vrn command is used to discover routes without having to con???gure 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.

Example

The following command sets a VRN name for the TN3270 internal adapter on the CIP:

vrn SYD.BLAN25

Related Commands

adapter lan

56 TN3270 Server Commands

Cisco 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, con???guration notes, brochures, descriptions of service offerings, and download access to public and authorized ???les.

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, ???gures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

???

WWW: http://www.cisco.com

WWW: http://www-europe.cisco.com

WWW: http://www-china.cisco.com

Telnet: cco.cisco.com

???Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the

following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.

For a copy of CCO???s Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco???s Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387,

408 526-7208, or cs-rep@cisco.com.

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.

TN3270 Server Commands 57

Cisco Connection Documentation

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.com

This document is to be used in conjunction with the Router Products Release Notes for Cisco IOS Release 11.0 publication.

AccessPath, AtmDirector, the CCIE logo, CD-PAC, Centri, Centri Bronze, Centri Gold, Centri Security Manager, Centri Silver, the Cisco Capital logo, Cisco IOS, the Cisco IOS logo, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, the Cisco Press logo, ClickStart, ControlStream, Fast Step, FragmentFree, IGX, JumpStart, Kernel Proxy, LAN2LAN Enterprise, LAN2LAN Remote Of???ce, MICA, Natural Network Viewer, NetBeyond, Netsys Technologies, Packet, PIX, Point and Click Internetworking, Policy Builder, RouteStream, Secure Script, SMARTnet, StrataSphere, StrataSphere BILLder, StrataSphere Connection Manager, StrataSphere Modeler, StrataSphere Optimizer, Stratm, StreamView, SwitchProbe, The Cell, Traf???cDirector, VirtualStream, VlanDirector, Workgroup Director, Workgroup Stack, and XCI are trademarks; Empowering the Internet Generation and The Network Works. No Excuses. are service marks; and BPX, Catalyst, Cisco, Cisco Systems, the Cisco Systems logo, EtherChannel, FastHub, FastPacket, ForeSight, IPX, LightStream, OptiClass, Phase/IP, StrataCom, and StrataView Plus are registered trademarks of Cisco Systems, Inc. in the U.S. and certain other countries. All other trademarks mentioned in this document are the property of their respective owners.

58 TN3270 Server Commands