Configuring Cisco Mainframe Channel Connection Adapters

Configuring Cisco Mainframe
Channel Connection Adapters

This chapter describes how to configure the Cisco Mainframe Channel Connection (CMCC) family
of adapters. These adapters include the Channel Interface Processor (CIP) for Cisco 7500 and Cisco
7000 series routers, and the ESCON Channel Port Adapter(ECPA) and the Parallel Channel Port
Adapter (PCPA) for Cisco 7200 series routers.
Note In this chapter, references to Channel Port Adapter (CPA) correspond to both the ECPA and
the PCPA.
For hardware technical descriptions and information about installing the router interfaces, refer to
the hardware installation and maintenance publication for your product. For a complete description
of the CMCC adapter commands in this chapter, refer to the “Cisco Mainframe Channel Connection
Adapter Commands” chapter of the Bridging and IBM Networking Command Reference. To locate
documentation of other commands that appear in this chapter, use the command reference master
index or search online.
Cisco’s Mainframe Channel Connection Adapters

The CMCC adapter family supports the IBM channel attachment and includes the following
products:
• CIP on the Cisco 7000 and Cisco 7500 series routers
• ECPA on the Cisco 7200 series routers
• PCPA on the Cisco 7200 series routers
All CMCC adapters support the full range of channel software applications available in the Cisco
IOS software.
Configuring Cisco Mainframe Channel Connection Adapters BC-459

Cisco’s Mainframe Channel Connection Adapters
Figure 171 Cisco Mainframe Channel Connection Adapters
7500 Channel 1/0

LPAR1
with CIP LPAR2
ESCON
IP Parallel channel APPN

SNA Channel 1/1 (Bus-and-Tag) HPR
APPN
HPR
TN3270
TCP/IP
SNA
ESCON or Parallel
7200
13337
with CPA
Channel 1/0
CIP
The CIP for the Cisco 7000 and Cisco 7500 series is designed for high-end network environments
that demand high-performance, high-port density, high-capacity solutions.
The CIP provides support for the IBM ESCON Channel Adapter (ECA) and Bus-and-Tag Parallel
Channel Adapter (PCA) channel-attached interfaces from Cisco 7000 series routers to IBM
mainframes and in most cases, it eliminates the need for a separate front-end processor (FEP).
A single CIP can support up to two physical channel interfaces in any combination of either PCA or
ECA. The CIP’s Parallel channel interface is provided by the PCA, and the ESCON channel
interface is provided by the ECA. Each CIP is pre-configured with the appropriate channel adapters
at manufacturing time.
The Cisco 7000 and Cisco 7500 series routers support online insertion and removal (OIR), which
allows you to install or remove CIPs while the system is operating.
Benefits
The key benefits of the CIP are as follows:
• Maximum throughput for every application—For the individual applications supported on the
CIP, the CIP offers maximum throughput. For example, the number of users supported for
TCP/IP offload is 10,000 and the number of LLC2 session supported is 8000.
• Scalability—The CIP supports up to 22 channel connections on a Cisco 7000 and Cisco 7500
series router platforms.
• Multiple interface support—The CIP supports multiple ESCON and Bus-and-Tag channel
interfaces.
• Higher memory capacity—The CIP offers a high memory capacity of 128 MB that can be useful
for software applications utilizing a high number of sessions. An example of such an application
is the TN3270 server.
• Port density—The CIP contains two channel interfaces, as compared to the CPA which offers one
channel interface.
BC-460 Bridging and IBM Networking Configuration Guide

CPA
CPA
The CPA is available for the Cisco 7200 series routers. The CPA expands the value of Cisco’s IBM
channel solution by providing channel connectivity to mid-range mainframe configurations. The
CPA is a standard single-width port adapter supporting ESCON or Parallel channel interfaces to
IBM mainframes.
The only differences between CMCC software applications running on the CIP and a CPA are
performance and capacity. The performance difference is based upon differences in the internal bus
architecture of a CIP vs a CPA, and the capacity difference is based on the difference in maximum
memory configurations (128 MB for CIP and 32 MB for CPA).
Each CPA provides a single channel interface for Cisco 7200-series routers. In some situations, this
eliminates the need for a separate front-end processor (FEP). The CPA contains a single I/O
connector.
The Cisco 7200-series router supports online insertion and removal (OIR), which allows you to
install or remove port adapters while the system is operating.
Benefits
The key benefits of CPA are as follows:
• Cost-effective—Both a CPA and Cisco 7200-series router provide industry-leading price
performance.
• Simplified migration path—The CPA and CIP microcode support the same features and
applications, enabling seamless migration for network expansion.
• Flexibility—The Cisco 7200 series router platform provides a great number of features and
capabilities that can be used in conjunction with a CPA.
ECPA
An ECPA is classified as a high-speed port adapter providing a single ESCON physical channel
interface. Current Cisco 7200 configuration guidelines recommend using no more than three
high-speed port adapters in a single Cisco 7200 router. Refer to the Cisco 7200 Series Port Adapter
Hardware Configuration Guidelines publication for more details.
PCPA
A PCPA provides a single Parallel channel physical interface supporting both 3.0 and 4.5 MBps data
transfer rates.

Supported Environments
Differences between the CIP and CPA

Table 9 illustrates the differences between the CMCC adapters.
Table 9 Differences between the CIP and the CPA
Product Differences CIP ECPA PCPA

Router platform Cisco 7500 Cisco 7200 Cisco 7200
Cisco 7000 with
RSP7000
Channel interfaces ESCON ESCON Parallel
Parallel
Maximum number of interfaces 2 1 1
Maximum memory 128 MB 32 MB 32 MB
Cisco IOS release support Cisco IOS release Cisco IOS release Cisco IOS release
10.2 and later 11.3(3)T and later 11.3(3)T and later
Virtual port adapter 2 0 0
Channel interface state tracking Yes Disabled—Use the Disabled—Use the
(HSRP, SNMP alerts) state-tracks-signal state-tracks-signal
command to enable command to enable
The CMCC adapters provide support for the environments discussed in the following sections:
• TCP/IP Environments Using CLAW
• TCP/IP Offload Environments
• IP Host Backup Environment
• TN3270 Server Environments
• Cisco SNA Environments
• Cisco MultiPath Channel Environments
TCP/IP Environments Using CLAW

TCP/IP mainframe protocol environments for IBM operating systems Multiple Virtual Storage
(MVS) and Virtual Machine (VM) are supported. This support includes TCP/IP-based applications
such as terminal emulation (Telnet), the File Transfer Protocol (FTP), Simple Mail Transfer Protocol
(SMTP); and Network File System (NFS), a distributed file access system. In addition, Internet
Control Message Protocol (ICMP) and User Datagram Protocol (UDP) are supported.
The Cisco IOS implements the Common Link Access to Workstation (CLAW) channel protocol to
transport data between the mainframe and a CMCC adapter in TCP/IP environments. Each CLAW
connection requires two devices out of a maximum of 256. Although this allows for a maximum of
128 CLAW connections per interface, a maximum of 32 CLAW connections per interface is
recommended.
The CLAW packing feature enables the transport of multiple IP packets in a single channel operation
and significantly increases throughput performance between a mainframe and a CMCC adapter.
Currently, IBM’s TCP/IP stack does not support the CLAW packing feature.

TCP/IP Offload Environments
The CLAW packing feature requires changes to the mainframe CLAW driver support. In partnership
with Cisco Systems, Interlink Computer Science has made the corresponding CLAW driver change
to Cisco IOS for S/390 Release 2 and Interlink TCPaccess 5.2. Customers must make the necessary
changes to their host configurations in order to enable the CLAW packing feature.
TCP/IP Offload Environments

TCP/IP mainframe protocol environments for IBM operating systems MVS, VM, and Transaction
Processing Facility (TPF) are supported.
The TCP/IP offload feature for CMCC adapters delivers the same function as the TCP/IP offload
function on the 3172 Interconnect Controller (Model 3), but with increased performance.
IP Host Backup Environment

You can connect multiple mainframes to a single CMCC adapter using a ESCON. Often, these
mainframes run using the ESCON Multiple Image Facility (EMIF), which permits the physical
machine to be divided into multiple logical partitions (LPARs). By defining an unused partition on
another mainframe, a user can move the operating system from a failed mainframe or mainframe
partition to the unused partition. By having multiple paths to each device, the move is accomplished
without changing the mainframe software. This function also permits moving an IP stack between
multiple operating system images.
On the CMCC adapter, each IP connection is treated as a physical device. The CMCC adapter does
not support multiple active paths to a single IP connection (or device). Prior to IP Host Backup, the
router configuration had to be changed whenever the mainframe operating system was moved from
one mainframe or LPAR to another. The IP Host Backup feature permits the mainframe operating
system to be moved from one mainframe to another without requiring a change to the router
configuration at the time of the move.
Note IP Host Backup does not provide single system image or automatic failover to a waiting
backup application. Host operator action on the mainframe is required in these instances.
TN3270 Server Environments

The TN3270 server feature on a CMCC adapter card provides mapping between an SNA 3270 host
and a TN3270 client connected to a TCP/IP network as shown in Figure 172. 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 CMCC adapter, the TN3270 server
is an SNA device that supports multiple 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 VTAM hosts connected to the TN3270 server in the CMCC adapter 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
Advanced Peer-to-Peer Networking (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.
• Telnet Server Functions
From the perspective of a TN3270 client, the TN3270 server is a high-performance Telnet server
that supports Telnet connections, negotiation and data format. The server on the CMCC adapter
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 172 TN3270 Implementation
S4735
Token
Router Router Ring
TN3270
client
SNA TCP/IP
Unless the TN3270 server uses a Token Ring connection to a Front-End Processor (FEP) as its host
connection, it will require CSNA or CMPC support. For this reason, TN3270 configuration issues
and tasks begins in the section “Configure TN3270 on a CMCC Adapter,” later in this chapter.
Note To enable the TN3270 server feature, you must have a CMCC adapter installed in a Cisco
7000 with RSP7000, Cisco 7500 series router, or a Cisco 7200 router. The TN3270 server is very
different from the TN3270 terminal emulation access feature described in the “Configuring Dial-In
Terminal Services” chapter of the Dial Solutions Configuration Guide.
Cisco SNA Environments

The CSNA feature provides support for SNA protocols over both ESCON and Parallel interfaces to
the IBM mainframe. As an IBM 3172 replacement, a CMCC adapter supports the External
Communications Adapter (XCA) feature of Virtual Telecommunications Access Method (VTAM),
which allows VTAM to define Token Ring devices attached to the 3172 as switched devices.
In SNA environments, support for the XCA feature of VTAM allows the CMCC adapter to provide
an alternative to FEPs at sites where NCP is not required for SNA routing functions.
By providing CLS and the Logical Link Control type 2 (LLC2) protocol stack on the CMCC adapter
card, all frames destined to the CMCC adapter or from the CMCC adapter card are switched by the
router. The presentation of LAN media types allows the CSNA feature to take advantage of current
source-route bridging (SRB), remote source-route bridging (RSRB), data-link switching plus
(DLSw+), Source-Route Translational Bridging (SR/TLB), internal SDLC-LLC2 translational
bridging (SDLLC), Qualified Logical Link Control (QLLC) services and APPN.
The CSNA feature supports the following communication through a Cisco 7000 with RSP7000,
Cisco 7500, and Cisco 7200 series router:
• Communication between a channel-attached mainframe running VTAM and a LAN/WAN
attached Physical Unit (PU) 2.0 SNA node
attached PU 2.1 SNA node

Cisco MultiPath Channel Environments

attached PU 5/4 SNA node
• Communication between two mainframes running VTAM channel-attached to the same CMCC
adapter card or different CMCC adapter cards in a Cisco 7000 with RSP7000, Cisco 7500 series
router, or a Cisco 7200 router
The CSNA feature provides SNA connectivity through Media Access Control (MAC) addresses
configured for internal MAC adapters on the Cisco 7000 with RSP7000, Cisco 7500 series router
and the Cisco 7200 series router. These internal MAC adapters correspond to XCA major node
definitions in VTAM, providing access points (LAN gateway) to VTAM for SNA network nodes.
The internal MAC adapters are configured to exist on internal LANs located on a CMCC adapter
card. Each CMCC adapter card can be configured with multiple internal Token Ring LANs. Each
internal Token Ring LAN must be configured to participate in source-route bridging. There is a
maximum limit of 18 internal MAC adapters per CMCC adapter. The internal MAC adapter is an
emulation of LAN adapters in an IBM 3172 Interconnect Controller.
Cisco MultiPath Channel Environments

The CMPC feature provides support for APPN connections using both High Performance Routing
(HPR) and Intermediate Session Routing (ISR). It supports the VTAM Transport Resource List
(TRL) major node and the VTAM Local SNA major node.
The CMPC feature can be used to establish an APPN connection between VTAM and the following
APPN nodes:
• Another VTAM channel attached to the same CMCC adapter
• Another VTAM channel attached to a different CMCC adapter in the same router
• TN3270 server DLUR in the same CMCC adapter
• An APPN network node (NN) in the router with the CMCC adapter
• Other APPN nodes external to the CMCC adapter and router with the CMCC adapter: CS/2,
AS/400, other LAN or WAN attached VTAM nodes
The CMPC feature isolates VTAM from the actual network topology. The MPC protocol is
terminated on the CMCC adapter and converted to LLC protocols. Once converted to LLC protocols
other Cisco features are used to connect VTAM to other APPN nodes in the network. CMPC can be
used with DLSw+, RSRB, SR/TLB, SRB, SDLLC, QLLC, ATM LAN emulation, and FRAS host
to provide connectivity to VTAM.
CMCC Adapter Interface Configuration Task List

You can perform the tasks in the following sections to configure and maintain IBM channel attach
interfaces.
Some CMCC adapter software features are configured on a virtual port. On the CIP adapter cards
installed in a Cisco 7000 with RSP 7000 or a Cisco 7500 series router, there are up to two physical
ports, numbered 0 and 1, and a virtual port, numbered 2. However, on the CPA installed in a Cisco
7200 series router, the single physical port and the virtual port are configured using the same port
number ID, number 0.
Not all tasks are required. Your CMCC adapter image may be preloaded. You must select an
interface, after which you configure the features you want supported on that interface.

Load the CMCC Adapter Microcode Image
Note You can configure a CMCC adapter interface for any or all of the supported environments. If
you want only CSNA support, for example, you need not configure TCP/IP support.
• Load the CMCC Adapter Microcode Image

• Select the Interface
• Configure Channel Interface Tracking for HSRP or SNMP Alerts
• Configure TCP/IP CLAW or CLAW Packing Support
• Configure TCP/IP Offload Support
• Configure TN3270 on a CMCC Adapter
• Configure CSNA Support
• Configure the CMCC Adapters for IP Host Backup
• Select Host System Parameters
• Monitor and Maintain the Interface
• Configure TN3270 on a CMCC Adapter
See the end of this chapter for “CMCC Interface Configuration Examples.”
Because the TN3270 server configuration is performed after an interface is configured for CSNA
support, TN3270 configuration issues and tasks are addressed separately from the interface
configuration tasks. The TN3270 configuration task list begins in the section “TN3270
Configuration Task List,” later in this chapter.
Load the CMCC Adapter Microcode Image

This section provides information on loading the microcode images for the CIP and CPA.
CIP Microcode Image

Beginning with Cisco IOS Software Release 11.1, the CIP microcode (or CIP image) no longer is
bundled with the Cisco IOS software. You must have Flash memory installed on the Route Switch
Processor (RSP) card to use the IBM channel attach features in Cisco IOS Software Release 11.1
and later.
The CIP image is preloaded on Flash cards for all Cisco 7000 with RSP7000 and Cisco 7500 series
routers ordered with the CIP option for Cisco IOS Software Release 11.1 and later. Use the
commands in this section if you are upgrading the CIP image in your router.
To prepare the CIP, use the following commands beginning in privileged EXEC command mode:
Step Command Purpose

1 enable Enter the privileged EXEC mode
command interpreter.

CPA Microcode Image

2 copy tftp flash Copy the CIP image from a server
copy tftp slot0: (Flash card) to the Flash memory. Use the
copy tftp slot1: (Flash card on 7500 series router) appropriate command for your
copy tftp bootflash: (onboard Flash on 7500 series system. You must be running
router) Cisco IOS Release 11.1 or later
prior to executing a copy tftp
command.
3 configure terminal In privileged command mode,
enter router configuration mode
and specify that the console
terminal will be the source of the
configuration subcommands.
4 microcode cip flash bootflash:cipxxx-yy Configure your router to load the
or Flash image to
microcode cip flash slot n:cipxx-yy the CIP:
• Enter global configuration
mode and specify that the CIP
microcode load from a Flash
card in router slot n or from
embedded Flash.
• Load the image from Flash to
the CIP card.
5 microcode reload Force a microcode reload in router
configuration mode.
6 end Exit configuration mode.
7 copy running-config startup-config Save the running configuration as
the new startup configuration in
NVRAM.
8 show controllers cbus Exit configuration mode and
display images loaded on the CIP
card.
9 show running-config Verify the contents of the
configuration file.
10 show microcode Show the microcode images for
downloadable hardware.
CPA Microcode Image

The CPA microcode image is preloaded on Flash memory cards for Cisco 7200 series routers for
Cisco IOS Release 11.3(3)T and later. You may be required to copy a new image to Flash memory
when a new microcode image becomes available. Use the commands in this section if you are
upgrading or loading a microcode image other than the default.
To prepare the CPA, use the following commands beginning in privileged EXEC command mode:

1 enable Enter the privileged EXEC mode command
interpreter:
2 copy tftp:filename [bootflash | slot0: | Copy the CPA microcode image from a server to
slot1:]filename either of the Flash memory cards. The source of
the file is tftp:filename.

Select the Interface

3 configure terminal In privileged command mode, enter router
configuration mode and specify that the console
terminal will be the source of the configuration
subcommands.
4 microcode {ecpa | pcpa} filename To load the microcode from an individual
microcode image that is stored as a file on a
Flash memory card, enter the microcode
command, the processor type, the specific
memory location of the CPA microcode image,
and the exact argument for filename.
5 microcode reload Load the specified CPA image from router
or configuration mode
microcode reload {all | {{ ecpa | pcpa} or

slot number}} Force a microcode reload in privileged EXEC
mode, without entering global configuration
mode.
6 end Exit configuration mode.
7 copy running-config startup-config Save the running configuration as the new startup
configuration in NVRAM.
8 show controllers channel slot/port Verify that the correct microcode is loaded
according to the new instructions. The display
indicates the currently loaded and running
microcode version for each CPA display software
and hardware information for the CPAs in your
router.
9 show running-config Verify the contents of the configuration file.
10 show microcode Show the microcode images for downloadable
hardware.
Select the Interface

Before you configure your channel attach interface, you must select the interface. Use the following
command in global configuration mode:
Command Purpose
interface channel slot/port Select the channel attach interface and enter
interface configuration mode.
Use the show extended channel EXEC commands to display current CMCC adapter status. This
command provides a report for each interface configured to support IBM channel attach.

Configure Channel Interface Tracking for HSRP or SNMP Alerts
Configure Channel Interface Tracking for HSRP or SNMP Alerts

If you want to use Hot Standy Router Protocol (HSRP) or SNMP alerts to monitor channel interface
status for an ECPA or PCPA channel interface, use the following command in interface configuration
mode to enable physical interface signal tracking:
Command Purpose
state-tracks-signal Enables tracking of the physical interface signal
for an ECPA or PCPA channel interface.
The state-tracks-signal command is valid only on channel interfaces which combine the functions
of both a physical and virtual interface. The ECPA and PCPA are examples of this type of channel
interface. The command is not valid for the CIP, which has a separate channel interface for the virtual
channel functions.
Configure TCP/IP CLAW or CLAW Packing Support

The following sections describe how to configure CLAW support. This feature is configured on the
physical interface. All tasks, except for configuring other interface support are required.
• Assign an IP Address
• Configure the IBM Channel Attach Interface
• Select a Data Rate for the Parallel Channel Interfaces
• Configure Other Interface Support
See the section “Select Host System Parameters” for guidelines on matching interface configuration
values with host system values.
Assign an IP Address
You must assign an IP address to the channel interface so that it can communicate with other devices
(or tasks) on the network. The IP address you assign to the interface must be in the same subnetwork
as the hosts with which you wish to communicate.
To assign an IP address, use the following command in interface configuration mode:
Command Purpose
ip address address mask Assign an IP address and network mask to the
selected interface.
Configure the IBM Channel Attach Interface

You must define the devices, or tasks, supported on the interface. Some information you need to
perform this task is derived from the following host system configuration files: MVSIOCP, IOCP,
and the TCPIP configuration. Refer to the section “Select Host System Parameters” for guidelines
on matching interface configuration values with host system values.

Configure TCP/IP Offload Support
To configure an IBM channel interface, use the following command in interface configuration mode:
Command Purpose
claw path device-address ip-address host-name Define the CLAW parameters for this device.
device-name host-app device-app [broadcast]
[backup]
The CLAW Packing feature requires changes to the mainframe CLAW driver support. In partnership
with Cisco Systems, Interlink Computer Science has made the corresponding CLAW driver change
to Cisco IOS software for S/390 Release 2 and Interlink TCPaccess 5.2. Configuration parameters
in the host TCP/IP applications must change to enable the CLAW packing feature.
See the section “CMCC Interface Configuration Examples” for samples of claw commands for
different configurations.
Select a Data Rate for the Parallel Channel Interfaces

When you configure a Parallel channel attach interface, you must define a data rate of either 3 MBPS
or 4.5 MBPS.
To select a data rate, use the following command in interface configuration mode:
Command Purpose
channel-protocol [s | s4] Define the Parallel data transfer rate.
Configure Other Interface Support

To enhance the usefulness of IBM channel attach support, you can further define how the interface
and the router interoperate by using the following commands in interface configuration mode:

1 ip mtu 4096 (Recommended for CPA interfaces) Sets the
MTU size of IP packets sent on the interface to
4096 bytes. The default MTU is 4472 bytes
across the channel on a CPA. The CLAW
feature cannot accept packets larger than
4096 bytes on a CPA.
2 ip route-cache same-interface Include fast switching support for multiple IP
datagram applications running on the same
CMCC adapter, as required.
3 no ip redirects Always include this command when
configuring host-to-host communications
through the same interface.
Configure TCP/IP Offload Support

The following sections describe how to configure the IBM channel attach interface for TCP/IP
offload support. All tasks, except for configuring other interface support, are required:
• Assign an IP Address
• Configure the IBM Channel Attach Interface
• Configure Other Interface Support

See the section “Select Host System Parameters” for guidelines on matching interface configuration
values with host system values.
You must assign an IP address to the channel interface so that it can communicate with other devices
(or tasks) on the network. The IP address you assign to the interface must be in the same subnetwork
as the hosts with which you wish to communicate.
To assign an IP address, use the following command in interface configuration mode:
Command Purpose
ip address address mask Assign an IP address and network mask to the selected
interface.
Configure the IBM Channel Attach Interface

You must define the devices, or tasks supported on the interface. Some information you need to
and the TCP/IP configuration. Refer to the section “Select Host System Parameters” for guidelines
on matching interface configuration values with host system values.
To configure the IBM channel interface, use the following command in interface configuration
mode:
Command Purpose
offload path device-address ip-address host-name Define the offload parameters for this device.
device-name host-app device-app host-link
device-link [broadcast] [backup]
See the section “CMCC Interface Configuration Examples” for samples of offload commands for
different configurations.

When you configure a Parallel channel attach interface, you must define a data rate of either 3 MB
per second or 4.5 MB per second.
To select a data rate, use the following command in interface configuration mode:
Command Purpose

Configure CSNA Support
Configure Other Interface Support

You can further define how the interface and the router interoperate. You can use the following
commands in interface configuration mode to enhance the usefulness of IBM channel attach support:

1 ip mtu 4096 (Recommended for CPA interfaces) Sets the
MTU size of IP packets sent on the interface to
4096 bytes. The default MTU is 4472 bytes
across the channel on a CPA. Specifying 4096
eliminates fragmentation and increases
performance.
2 ip route-cache same-interface Include autonomous switching support for
multiple IP datagram applications running on
the same CMCC adapter, as required.
3 no ip redirects Always include this command when configuring
host-to-host communications through the same
ESCON interface.

The following sections describe how to configure the IBM channel attach interface for CSNA
support. This procedures requires the configuration of both the physical and virtual interfaces. The
last task, “Configure an Internal Adapter’s Link Characteristics,” is optional. All other tasks are
required.
• Configure the Subchannel Information
• Configure the Internal LAN
• Configure the Source Bridge
• Configure the LOCADDR Priority
• Configure the SAP Priority
• Configure Internal Adapters
• Name the Internal Adapter
• Configure an Internal Adapter’s Link Characteristics
• Configure an Internal Adapter’s Link Characteristics


When you configure a Parallel channel attach interface, you must define a data rate of either 3 MBps
or 4.5 MBps.
To configure the data rate, use the following command in interface configuration mode:
Command Purpose
Configure the Subchannel Information

To define an SNA subchannel supported by the CSNA feature, use the following command in
interface configuration mode for the physical channel interface:
Command Purpose
csna path device [maxpiu value] [time-delay Define the CSNA subchannel device.
value] [length-delay value]
Configure the Internal LAN

To configure an internal LAN, use the following commands beginning in global configuration mode:

1 interface channel slot/port Select the virtual interface.
2 lan tokenring lan-id Select the internal LAN interface and enter
internal LAN configuration mode.
Configure the Source Bridge

Select the bridging characteristics for the internal LAN. Use the following commands in internal
LAN configuration mode:
Command Purpose
source-bridge local-ring bridge-number Select source-route bridging for the selected
target-ring LAN interface.
Configure the LOCADDR Priority

Select the LOCADDR priority for the internal LAN. Use the following commands in internal LAN
configuration mode:
Command Purpose
locaddr-priority list-number Select locaddr priority for the selected LAN
interface.

Configure the SAP Priority

Select the SAP priority for the internal LAN. Use the following commands in internal LAN
configuration mode:
Command Purpose
sap-priority list-number Select sap priority for the selected LAN
interface.
Configure Internal Adapters

To select or configure an internal adapter, use the following command in internal LAN configuration
mode:
Command Purpose
adapter adapno mac-address Select the internal adapter to configure.
Name the Internal Adapter

Select a name for the internal adapter. Use the following command in internal adapter configuration
mode:
Command Purpose
name name Select a name for the internal adapter.
Configure an Internal Adapter’s Link Characteristics

To configure the LLC link characteristics of an internal adapter, use the following optional
commands in internal adapter configuration mode:
Command Purpose
llc2 N1 bytes Maximum size of an I-frame in bytes.
llc2 N2 retry-count Maximum retry count.
llc2 Nw window-size-increase Increase the window size for consecutive good
I-frame received (zero is disabled).
llc2 ack-delay-time milliseconds Maximum time for incoming I-frames to stay
unacknowledged.
llc2 ack-max frame-count Maximum number of I-frames received before an
acknowledgment must be sent.
llc2 idle-time milliseconds Frequency of polls during periods of idle traffic.
llc2 local-window frame-count Maximum number of I-frames to send before
waiting for an acknowledgment.
llc2 recv-window frame-count Receive window.
llc2 t1-time milliseconds Specify amount of time to wait for an
acknowledgment to transmit I-frames.
llc2 busy-time milliseconds Amount of time to wait while the other LLC2
station is in a busy state before attempting to poll
the remote station.

Configure an Internal Adapter’s Link Characteristics
Command Purpose
llc2 tpf-time milliseconds Amount of time to wait for a final response to a
poll frame before resending the original poll
frame.
llc2 trej-time milliseconds Amount of time to wait for resending a rejected
frame before sending the reject command.

Configure the CMCC Adapters for IP Host Backup
Configure the CMCC Adapters for IP Host Backup

The following sections describe how to configure the IBM channel attach interface for IP Host
Backup support. With IP Host Backup, you can configure a backup group for each CLAW or offload
device, one path at a time, or you can specify a group of IP host paths and then configure which
CLAW or offload IP addresses are used with those paths. Using the second method, specifying paths,
provides a shortcut to the one at a time method.
• Configure a CLAW IP Host Backup Group
• Configure an Offload IP Host Backup Group
• Configure an IP Host Backup Group Using Paths
Configure a CLAW IP Host Backup Group

You must define the devices, or tasks, supported on the interface. Some information you need to
and the TCPIP configuration.
To configure the CLAW IP Host Backup, use the following command in interface configuration
mode:
Command Purpose
claw path device-address ip-address host-name Define the CLAW parameters for this device.
device-name host-app device-app [broadcast]
backup
See the section “Configuration Tasks” for samples of claw commands for different configurations.
Configure an Offload IP Host Backup Group

You must define the devices, or tasks supported on the interface. Some information you need to
and the TCP/IP configuration.
To configure the Offload IP Host backup, use the following command in interface configuration
mode to configure an Offload device (read and write subchannel) for communication with a
mainframe TCP/IP stack in Offload mode:
Command Purpose
offload path device-address ip-address host-name Define the offload parameters for this device.
device-name host-ip-link device-ip-link
host-api-link device-api-link [broadcast] backup
See the section “Configuration Tasks” for samples of offload commands for different configurations.
Configure an IP Host Backup Group Using Paths

You can define a backup group by specifying a path, or group of paths, that are used as the IP Host
Backup. Under the backup group, you can have multiple backup connections defined that all use the
same IP address.

Select Host System Parameters
To configure the IP Host Backup using paths, use the following commands beginning in interface
configuration mode:
1 Command Purpose
2 path path [[path ...]] Define the backup path, or paths, for this
group and enter IP Host Backup
configuration mode.
3 claw device-address ip-address host-name Define the CLAW parameters for this
device-name host-app device-app device.
[broadcast]
4 offload path device-address ip-address Alternatively, you can define the offload
host-name device-name host-ip-link parameters for this device
device-ip-link host-api-link device-api-link
[broadcast]
5 exit Exit IP Host Backup configuration mode
and return to interface configuration mode.

This section describes how to correlate values found in the VM and MVS system I/O configuration
program (IOCP) files with the fields in the claw, csna, cmpc, and offload interface configuration
commands. In addition, for CLAW and Offload, you will need configuration information from the
host TCP/IP application configuration file. Refer to the following IBM operating system manuals for
specific IOCP configuration statement details:
• Transmission Control Protocol/Internet Protocol TCP/IP Version 2 Release 2.1 for MVS:
Planning and Customization, SC31-6085 (or later version)
• Transmission Control Protocol/Internet Protocol TCP/IP Version 2 Release 2 for VM: Planning
and Customization, SC31-6082 (or later version)
Values from the Host IOCP File

When you define CLAW or offload parameters, you must supply path information and device
address information to support routing on an IBM channel. The path information can be simple, in
the case of a channel directly attached to a router, or more challenging when the path includes an
ESCON director switch or multiple image facility support.
The path argument is a concatenation of three hexadecimal numbers that represent the values listed
in Table 10.
Table 10 CLAW Path Argument Values
CLAW Path Argument

Breakdown Values Description
Path 01–FF For a directly attached ESCON channel or any
Parallel channel, this value is 01 unless the system
administrator has configured another value.
For a channel attached through an ESCON
director switch, this value will be the path that,
from the Cisco IOS software point of view, exits
the switch and attaches to the host.

Table 10 CLAW Path Argument Values (continued)
CLAW Path Argument

Breakdown Values Description
Channel logical address 0–F For a Parallel channel, this value is 0. For a
directly attached ESCON channel, the value may
be non-zero.
If the host is running in Logical Partition (LPAR)
mode and the CHPID is defined as shared, this is
the partition number associated with the devices
configured in the IOCP.
The default for this part of the path argument is 0.
Otherwise, the channel logical address associated
with the channel is defined in the IOCP.
Control unit logical address 0–F For a Parallel channel, this value is 0. For a
directly attached ESCON channel, the value may
be non-zero.
If this value is specified in the IOCP, match that
value here.
Otherwise, the control unit logical address is
specified in the IOCP CNTLUNIT statement for
the host channel in the CUADD parameter.
In Figure 173, two host systems connect to the ESCON director switch on paths 23 and 29. The
channels both exit the switch on path 1B and attach to Router A.
Figure 173 System with an ESCON Director Switch and a Directly Attached Channel
Host A CH 23
198.92.2.12 ESCON director Router A
15 1B
19 18
Host B CH 29
198.92.2.13
Router B
Host C CH 42
S3027
198.92.2.14
Note that the path between Host A and Host B is dynamically switched within the ESCON director.
A third host is attached directly to Router B through path 42.

Values from the Host IOCP File
The IOCP control unit statements would look similar to the following examples:
• Host A
CNTLUNIT CUNUMBER=0001, PATH=(23), LINK=1B, UNITADD=((00,64)), UNIT=SCTC, CUADD=F
• Host B
CNTLUNIT CUNUMBER=0002, PATH=(29), LINK=1B, UNITADD=((00,64)), UNIT=SCTC, CUADD=A
• Host C
CNTLUNIT CUNUMBER=000A, PATH=(42), UNIT=SCTC, UNITADD=((00,64))
The system administrator can provide you with the values. For example the ESCON director ports
15 and 19 in Figure 173 are the channel attachments from the ESCON director to each host. Given
these values, the claw command path argument for the two channel attachments to Router A
becomes:
claw 150F
claw 190A
The offload command path argument for the two channel attachments to Router A becomes:
offload 150F
offload 190A
The claw command path argument for the directly attached channel to Router B is easy to determine:
claw 0100
Similarly, the offload command path argument for the directly attached channel to Router B is as
follows:
offload 0100
Next, determine the claw, csna, cmpc, or offload command device-address argument value, which
is shown as 00 in the UNITADD parameter for all three devices. Based on the above example, this
value can be any even value.
The UNITADD parameter in the CNTLUNIT macro of the IOCP file defines the valid range for
device addresses. In the example above, a UNITADD parameter of (00,64) means that the first valid
device address is 00 and the number of devices is 64 for a range of 00 to 63. In the hexadecimal
notation used by channel configuration commands this translates to a range of 00 to 3F.
The claw (or offload) commands now become:
• Router A (for the claw command)
claw 150F 00
claw 190A 00
• Router A (for the offload command)

offload 150F 00
offload 190A 00
• Router B (for the claw command)

claw 0100 02
• Router B (for the offload command)

offload 0100 02

Values from the Host TCP/IP File

The remainder of the claw and offload command arguments are derived from the DEVICE, LINK,
and HOME statements in the host TCP/IP configuration files. The csna and cmpc configuration
commands include only path and device. The statements will be similar to the following:
• Host A
DEVICE EVAL CLAW 500 VMSYSTEM C7000 NONE 20 20 4096 4096
LINK EVAL1 IP 0 EVAL
HOME 198.92.2.12 EVAL1
• Host B
DEVICE EVAL CLAW 600 STSYSTEM C7000 NONE 20 20 4096 4096
HOME 198.92.2.13 EVAL1
• Host C
DEVICE EVAL CLAW 700 RDUSYSTM C7000 NONE 20 20 4096 4096
HOME 198.92.2.14 EVAL1
The DEVICE statement lists the host-name and device-name values to use, which follows the
CLAW 500 entry in the DEVICE statement.
The LINK statement links the device name, EVAL, to EVAL1. The IP address for EVAL1 appears
in the HOME statement.
Based on this example, you can supply the remainder of the arguments for the sample claw
commands:
• Router A
claw 150F 00 198.92.2.12 VMSYSTEM C7000 TCPIP TCPIP
claw 190A 00 198.92.2.13 STSYSTEM C7000 TCPIP TCPIP
• Router B
claw 0100 02 198.92.2.14 RDUSYSTM C7000 TCPIP TCPIP
Similarly, the sample offload commands are as follows:

• Router A
offload 150F 00 198.92.2.12 VMSYSTEM C7000 TCPIP TCPIP TCPIP API
offload 190A 00 198.92.2.13 STSYSTEM C7000 TCPIP TCPIP TCPIP API
• Router B
offload 0100 02 198.92.2.14 RDUSYSTM C7000 TCPIP TCPIP TCPIP API

Example of a Derived Value
Example of a Derived Value

When you have a directly attached channel, the system administrator may provide you with a system
IODEVICE ADDRESS that you can use. In this case, you must work backwards through the IOCP
file to locate the proper device-address argument value for the claw command.
In this first example, the IODEVICE ADDRESS value is 800. Using this number, you locate the
IODEVICE ADDRESS statement in the IOCP file, which points you to the CNTLUNIT statement
that contains the device-address argument value for the claw, csna, cmpc or offload command:
IODEVICE ADDRESS=(0800,256),CUNUMBR=(0012),UNIT=SCTC
**** Address 800 points to CUNUMBR 0012 in the following statement
CNTLUNIT CUNUMBR=0012,PATH=(28),UNIT=SCTC,UNITADD=((00,256))
**** The device-address is the UNITADD value of 00
From this example, the claw command would be similar to the following:
claw 0100 00 197.91.2.12 CISCOVM EVAL TCPIP TCPIP
In the next example, the system administrator has given you an IODEVICE ADDRESS of 350,
which does not correspond exactly to a value in the IOCP file. In this instance you must calculate an
offset device-address argument value for the claw or offload command:
**** Address 350 (340 + 10) is in the range covered by CUNUMBER 0008
CNTLUNIT CUNUMBR=0008,PATH=(24),UNIT=SCTC,UNITADD=((40,64)),SHARED=N, X
**** The device-address is the UNITADD value of 40, offset by 10
**** The device-address to use is 50
From this example, the claw command would be similar to the following:
claw 0100 50 197.91.2.12 CISCOVM EVAL TCPIP TCPIP
Note In the IOCP examples for the IODEVICE and CNTLUNIT statements, UNIT=SCTC is the
usual value for ESCON channels. Parallel channels will have UNIT=3088 in the CNTLUNIT
statement and UNIT=CTC in the IODEVICE statement.
Caution When you are running MVS, you must disable the missing interrupt handler (MIH) to avoid
introducing errors into the CLAW algorithm. Refer to the IBM publication Transmission Control
Protocol/Internet Protocol TCP/IP Version 2 Release 2.1 for MVS: Planning and Customization (publication
SC31-6085 or later) for information on disabling the MIH.

Monitor and Maintain the Interface

You can perform the tasks in the following sections to monitor and maintain the interfaces:
• Monitor Interface Status
• Clear and Reset an Interface
• Monitor the Physical Channel Interface on the CPA
• Shut Down and Restart an Interface
• Run CMCC Adapter Interface Loopback Diagnostics
• Configure CMCC Adapter Core Dump
Monitor Interface Status

The software allows you to display information about the interface, including the version of the
software and the hardware, the controller status, and statistics about the interfaces. The following
table lists some of the interface monitoring commands. To display the full list of show commands,
enter show ? at the EXEC prompt.
Perform the following commands in EXEC mode to display information associated with each
command. All commands are applicable to all CMCC adapter interfaces (CIP and CPA), unless it is
mentioned that they are specific to a particular CMCC adapter. Commands are listed in alphabetic
order.
Command Purpose
show controllers cbus Display the cbus internal state for the Cisco
7000 with RSP7000 and Cisco 7500 series
routers. Also included in the display is
CIP-specific information such as the currently
loaded microcode, currently loaded
microcode application segments, and load
metrics.
show controllers channel [slot/port] Display CPA-specific information, including
the currently loaded microcode.
show extended channel slot/port backup Display information about CLAW and offload
[ip-address] commands for each backup group.
show extended channel slot/port cmpc [path Display information about each CMPC
[device]] subchannel configured on the specified
CMCC adapter interface.
show extended channel slot/port connection-map Display the number of active LLC2
llc2 connections for each SAP and the mapping of
the internal MAC adapter and the SAP to the
resource that activated the SAP.
show extended channel slot/port csna [admin | oper Display information about the CSNA
| stats] [path [device]] subchannels configured on the specified
CMCC adapter interface.
show extended channel slot/port llc2 [admin | oper | Display information about the LLC2 sessions
stats] [lmac [lsap [rmac [rsap]]]] running on the CMCC adapter interfaces.
show extended channel slot/port max-llc2-sessions Display information about the number of
LLC2 sessions supported on the CMCC
adapter.

Monitor Interface Status
Command Purpose
show extended channel slot/port icmp-stack Display information about the ICMP stack
[ip-address] running on the CMCC adapter interfaces.
show extended channel slot/port ip-stack Display information about the IP stack
[ip-address] running on the CMCC adapter interfaces
show extended channel slot/port llc2 [admin | oper | Display information about the LCC2 sessions
stats] [lmac [lsap [rmac [rsap]]]] running on the CMCC adapter interfaces.
show extended channel slot/port packing names Display CLAW packing names and their
[path [device]] connection state.
show extended channel slot/port packing stats Display CLAW packing statistics.
[path[device]]
show extended channel slot/port statistics [path Display information about CMCC adapter
[device]] [connected] interfaces for diagnostic purposes.
show extended channel slot/port subchannel Display information about the CMCC adapter
[connected] interfaces
show extended channel slot/port tcp-connections Display information about the TCP sockets
[[loc-ip-addr [loc-port [rem-ip-addr [rem-port]] on a channel interface.
[detail | summary]
show extended channel slot/port tcp-stack Display information about the TCP stack
show extended channel slot/port tg [oper | stats] Display configuration, operational, and
[detailed] [tg-name] statistics information for CMPC transmission
groups configured on a specified CMCC
adapter internal LAN interface.
show extended channel slot/port tn3270-server Display current configuration parameters and
the status of the PUs defined in each TN3270
server.
show extended channel slot/port tn3270-server Display information about all clients at a
client-ip-address ip-address [disconnected | specific IP address.
in-session | pending]
show extended channel slot/port tn3270-server dlur Display information about the SNA session
switch.
show extended channel slot/port tn3270-server Display information about the DLUIR
dlurlink name components.
show extended channel slot/port tn3270-server Display mappings between a nailed client IP
nailed-ip ip-address address and nailed LUs.
show extended channel slot/port tn3270-server pu Display the PU configuration parameters,
pu-name statistics, and all the LUs currently attached
to the PU.
show extended channel slot/port tn3270-server pu Display information about the TN3270 server
pu-name lu locaddr [history] LUs running on CMCC adapter interfaces.
show extended channel slot/port udp-listeners Display information about the UDP listener
[ip-address] sockets on the CMCC adapter interfaces.
show extended channel slot/port udp-stack Display information about the UDP stack
show interfaces channel slot/port accounting Display the number of packets for each
protocol type that has been sent through the
channel interface.

Command Purpose
show version Display the hardware configuration, software
version, names and sources of configuration
files, and boot images.
Clear and Reset an Interface

To clear the interface counters shown with the show interfaces command, use the following
command in EXEC mode:
Command Purpose
clear counters [type slot/port] Clear interface counters for router.
Note This command will not clear counters retrieved using Simple Network Management Protocol
(SNMP), but only those seen with the EXEC show interfaces command.
To clear the counters associated with application features configured on the CMCC adapters, use the
following command in EXEC mode:
Command Purpose
clear extended counters channel slot/port [csna | Clear counters for application features
icmp-stack | ip-stack | llc2 | statistics | configured on CMCC adapters.
tcp-connections | tcp-stack | tg | tn3270-server |
udp-stack]
Note This command will not clear counters retrieved using Simple Network Management Protocol
(SNMP), but only those seen with the EXEC show extended channel commands.
Use the following command in EXEC mode to clear and reset interfaces. Under normal
circumstances, you do not need to clear the hardware logic on interfaces.
Command Purpose
clear interface type slot/port Reset the hardware logic on an interface.
Monitor the Physical Channel Interface on the CPA

Unlike the CIP, which has a separate channel interface for the virtual channel functions, the ECPA
and PCPA have a single interface that combines the functions of both a physical and virtual channel
interface. For this reason, monitoring the physical channel interface on a CPA requires other
considerations in its implementation.
In Cisco IOS releases prior to 12.0(4.1), you could not configure how the state of the physical
interface on a CPA was tracked, particularly when the interface was configured for no shutdown. In
those previous Cisco IOS releases when the CPA channel interface was configured for no shutdown,
the channel interface status was always reported as UP/UP, even when no signal was present on the
physical connection.

Shut Down and Restart an Interface
In Cisco IOS release 12.0(4.1) and later, you can use the state-tracks-signal configuration command
to control how you want the state of the CPA’s channel interface to be reported. The
state-tracks-signal command is useful in environments where you are using Hot Standby Router
Protocol (HSRP) or SNMP alerts to monitor channel interface status.
Use the following command in interface configuration mode to enable physical interface signal
tracking:
Command Purpose
state-tracks-signal Enables tracking of the physical interface signal
for an ECPA or PCPA channel interface.
When the state-tracks-signal command is used on an interface that is configured for no shutdown,
then the state of the channel interface is reported according to the status of the physical channel
interface signal. If the physical channel interface signal is not present, then the channel interface
status is DOWN/DOWN.
When the channel interface is configured for no state-tracks-signal (the default) and no shutdown,
the channel interface status is always reported as UP/UP, even when there is no signal present on the
physical connection. This configuration is useful for TN3270 server environments that are operating
in a mode without any physical channel interface connections.
Shut Down and Restart an Interface

You can disable an interface. Doing so disables all functions on the specified interface and marks the
interface as unavailable on all monitoring command displays. This information is communicated to
other network servers through all dynamic routing protocols. The interface will not be mentioned in
any routing updates. On the CMCC adapter with ESCON interface, a command is sent to the host to
inform it of the impending shutdown. On the CMCC adapter’s Parallel interface, the shutdown
command disables the adapter card’s transceivers and the interface stops responding to all
commands.
For the following reasons, it is recommended that channel interfaces be shut down:
• For a CMCC adapter’s ESCON interface, you may want to change the interface type of a Cisco
7000 with RSP7000 or Cisco 7500 port online. To ensure that the system recognizes the new
interface type, shut down the interface, then reenable it after changing the interface. Refer to your
hardware documentation for more details.
• If you want to reload the router
• If, prior to reloading the microcode, you want to shut down the interface
• If you want to power off the router
• If it is recommended that channel interfaces be shut down
To shut down an interface and then restart it, use the following commands in interface configuration
mode:

1 shutdown Shut down an interface.
2 no shutdown Reenable an interface.
To check whether an interface is disabled, use the EXEC command show interfaces. An interface
that has been shut down is shown as administratively down in the show interfaces command display.

Configure TN3270 on a CMCC Adapter
Run CMCC Adapter Interface Loopback Diagnostics

The CMCC adapter does not provide software loopback support. You can use special loopback wrap
plugs to perform hardware loopback with the ESCON and Parallel channel interfaces. Hardware
loopback information is included in the hardware installation notes for the CMCC adapters.
Configure CMCC Adapter Core Dump

To obtain the output of a CMCC adapter core dump, use the following commands in global
configuration mode:

1 ip domain-name name Configure the router FTP services.
ip name-server address
ip ftp username name
ip ftp password password
2 exception slot [slot] protocol//:host/filename Configure the CMCC adapter core dump
feature.
Note The exception slot command is only supported on the Cisco 7000 with RSP7000 and Cisco
7500 series routers. On the Cisco 7200 series routers, only FTP is supported.
While the router is running, you can use the write EXEC command to write the contents of a CMCC
adapter that is not halted.
Command Purpose
write Write the contents of a CMCC adapter.
Note The output obtained by the exception slot command can be interpreted by a qualified Cisco
technical support person.

The following sections describe additional features of TN3270 server support on the CMCC adapter.
• Dynamic LU Allocation
• Formation of LU Model Type and Number
• Specific LU Allocation
• SNA Switching—End Node DLUR
• Multiple Hosts Support
• IP Type of Service and Precedence Setting

Dynamic LU Allocation
You will also need to understand the following information before proceeding with TN3270
configuration tasks:
• VTAM Host Configuration Considerations for Dynamic LU Allocation
• LU Address Mapping
• TN3270 Configuration 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” on the algorithm used). This string is used as a field
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 find a match in the
sample configuration shown in Figure 174. An ACTLU will be sent and a terminal session with the
model and type requested by the client can be 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:
• IBM-<XXXX>-<Y>[-E]: This will be formatted as “XXXX0Y”or “XXXX0YE” in the model
type and number field in the Reply PSID NMVT.
• IBM-DYNAMIC: This will result in “DYNAMIC” being put in the model type and number field.
The VTAM configuration will need to have “DYNAMIC” defined 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.
Clients that do not support TN3270E typically require a 3270 datastream on the SSCP-LU flow.
Clients that are TN3270E compliant will typically utilize the SNA Character Set (SCS) on the
SSCP-LU session. In order to accommodate these two classes of clients, the TN3270 server directs

them 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 TN3270E support, the character “S” is overlaid on the fifth character of
the string, or appended if the string is less than five characters. See Table 11.
Table 11 Examples of Model String Mapping
BIND-IMAGE
String from Client (ASCII) Requested? String to Host (EBCDIC)
IBM-3278-4 No 327804
IBM-3279-5E No 327905E
IBM-3279-3-E Yes 3279S5E
IBM-DYNAMIC Yes DYNASIC
ABC Yes ABCS
ABCDEFGH Yes ABCDSFG
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. 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.
SNA Switching—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 CMCC
adapter card rather than on the VTAM hosts. This feature is especially important with 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
requestable LUs such as printers.

Multiple Hosts Support
Multiple Hosts Support

The TN3270 server supports access to multiple hosts via the configuration on a PU basis (Table 12).
PUs connected to different hosts/applications can be configured with different IP address.
Table 12 Direct PU Configuration in Router
PU Adapter
Command Name Idblk IP-address Type number Lsap RMAC RMAC Lu-seed Lu-name
PU X1 05D300 192.195.80.4 tok 1 4 RMAC 4100.cafe.0001 lu-seed TN3X1###
01 0
PU X2 05D300 171.69.176.4 tok 1 8 RMAC 4100.cafe.0002 lu-seed TN3X2###
02 3
From the pu (direct) TN3270 configuration command values shown in Table 12, PU X2 establishes
a link to a host at SAP 4 (the default) 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.
IP Type of Service and Precedence Setting

The TN3270 server supports IP type of service (TOS) precedence setting. TOS is used in router
networks to make routing decisions for the generated IP packets. The TN3270 server generates
packets that comply to IP TOS and IP precedence values. (Refer to RFC 1349 for a description of IP
TOS and IP precedence.)
The Cisco implementation of IP precedence allows values of 0 to 7 while TOS allows values from
0 to 15. You must choose appropriate values for TN3270 screens and printers consistent with your
organization’s policy.
At the protocol level, IP precedence allows a router network to discriminate between different types
of traffic by giving different priorities to them. IP TOS allows router networks to discriminate
between different types of traffic by giving different routing characteristics to them. Precedence and
TOS values complement one another and provide flexibility in managing your network traffic.
In TN3270 server, two types of TN3270 clients connect: interactive screens or printers. Screens are
interactive while printers need bulk data transfer. IP TOS and IP precedence allows you to
discriminate between those two types of sessions and assign different precedence values to the
interactive connection and the bulk data connection.
IP TOS and IP precedence values can be specified either at the TN3270 server command level or on
the individual PU command level. Values can be specified on both levels, in which case siftdown will
be used to determine value on individual PU. Siftdown is used when you configure values in TN3270
server configuration mode that apply to all entities in the server, yet you still can configure individual
PUs at the PU configuration mode to alternative values. PU values not specifically changed use the
values configured at the TN3270 server configuration mode. This flexibility provides a powerful, yet
efficient, way to manage the values.

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 CMCC adapter 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 174.
Figure 174 VTAM Host Values Defining LUSEED and LUGROUP
Example VTAM host values defining LUSEED and LUGROUP name parameters:
TN3270PU PU . * define other PU parameters
IDBLK=05D,
IDNUM=30001,
LUSEED=TN3X1###, * define the seed component of
the LU names created by DDDLU
(e.g. LOCADDR 42 will have the
name TN3X1042)
LUGROUP=AGROUP * define the LU group name
*
TN3X1100 LU LOCADDR=100, * define a terminal which
MODETAB=AMODETAB requires a specific LU name
*
TN3X1101 LU LOCADDR=101, * define a printer which requires
DLOGMODE=M3287CS a specific LU name
Example VTAM host values defining LUGROUPname, AGROUP:

AGROUP LUGROUP * define LU group to support
various terminal types
327802E LU USSTAB=USSXXX, * define template to support IBM
LOGAPPL=TPXP001, 3278 terminal model 2 with
DLOGMOD=SNX32702, Extended Data Stream. Note that
SSCPFM=USS3270 the USS messages in USSXXX
should be in 3270 datastream.
3278S2E LU USSTAB=USSYYY, * define template to support IBM
LOGAPPL=TPXP001, 3278 terminal model 2 with
DLOGMOD=SNX32702, Extended Data Stream, for
SSCPFM=USSSCS TN3270E clients requesting
BIND-IMAGE.
327805 LU USSTAB=USSXXX, * define template to support IBM
LOGAPPL=TPXP001, 3279 terminal model 5
DLOGMOD=D4C32785,
SSCPFM=USS3270
@ LU USSTAB=USSXXX, this is the default template to
LOGAPPL=TPXP001, match any other terminal types
DLOGMOD=D4A32772,
SSCPFM=USS3270

With the configuration shown in Figure 174 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
network management vector transport (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 Figure 174,
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.
Note If your host computer is customized for a character set other than U.S. English EBCDIC, you
might need to code some VTAM configuration tables differently than indicated in the examples
provided by Cisco.
Some VTAM configurations include the number sign (#) and at symbol (@). In the U.S. English
EBCDIC character set, these characters are stored as the hexadecimal values 7B and 7C,
respectively. VTAM will look for those hexadecimal values when processing the configuration file.
The characters used to enter these values are different in other EBCDIC National Language
character sets. Table 13 lists the languages that have different characters for the 7B and 7C
hexadecimal values and the corresponding symbols used to enter the characters.
For example, the value for the LUSEED parameter in the PU definition called TN3270PU in
Figure 174 has a value of TN3X1###. To properly code this value for LUSEED for the French
National Language character set, the value should be TN3X1£££.
Table 13 International Character Sets for Hexadecimal Values
Hexadecimal value
7B 7C
Language Symbol Description Symbol Description
German # Number sign § Section symbol
German (alternate) Ä A-dieresis Ö O-dieresis
Belgian # Number sign à a-grave
Brazilian Õ O-tilde Ã A-tilde
Danish/Norwegian Æ AE-ligature Ø O-slash
English (U.S./UK) # Number sign @ At symbol
Finnish/Swedish Ä A-dieresis Ö O-dieresis
French £ Pound sterling à a-grave
Greek £ Pound sterling § Section symbol

LU Address Mapping
Table 13 International Character Sets for Hexadecimal Values
Hexadecimal value
7B 7C
Language Symbol Description Symbol Description
Icelandic # Number sign D Uppercase eth
Italian £ Pound sterling § Section symbol
Portuguese Õ O-tilde Ã A-tilde
Spanish Ñ N-tilde @ At symbol
Turkish Ö O-dieresis S S-cedilla
LU Address Mapping
Logical unit (LU) address mapping allows a client IP address to be mapped, or “nailed,” to one or
more LU local addresses on one or more physical units (PUs) by means of router configuration
commands. You can control the relationship between the TN3270 client and the LU.
Clients from traditional TN3270 (non-TN3270E) devices can connect to specific LUs, which
overcomes a limitation of TN3270 devices that cannot specify a “CONNECT LU.” LU nailing is
useful for TN3270E clients, because you can perform the configuration at the router, providing
central control, rather than at the client.
Handling Large Configurations

The largest size nonvolatile random-access memory (NVRAM) planned for the Cisco 7000, Cisco
7500 and Cisco 7200 series routers is 128 KB. The maximum number of nailing commands that can
be stored in a 128 KB NVRAM is approximately 4000. However, large configurations may map as
many as 10,000 IP addresses to LUs.
To maintain a configuration file that exceeds 128 KB there are two alternatives. The configuration
file can be stored compressed in NVRAM. Or, the configuration file can be stored in Flash memory
that is either internal Flash or on a PCMCIA card.
LU Nailing and Model Matching

The “model matching” feature of the CMCC TN3270 server is designed for efficient use of dynamic
LUs. Each client specifies a terminal model type at connection. When a non-nailed client connects
and does not request a specific LU, the LU allocation algorithm attempts to allocate an LU that
operated with that terminal model the last time it was used. If no such model is available, the next
choice is an LU that has not been used since the PU was last activated. Failing that, any available LU
is used; however, for dynamic LUs only, there is a short delay in connecting the session.
Where a client or set of clients is nailed to a set of more than one LU, the same logic applies. If the
configured LU nailing maps a screen client to a set of LUs, the LU nailing algorithm attempts to
match the client to a previously used LU that was most recently used with the same terminal model
type as requested by the client for this connection. If a match is found, that LU is used. If a match is
not found, any LU in the set that is not currently in use is chosen. If there is no available LU in the
set, the connection is rejected.

TN3270 Configuration Modes
For example, the following LUs are nailed to clients at address 192.195.80.40, and LUs BAGE1004
and BAGE1005, which were connected but are now disconnected.
lu name client-ip:tcp nail state model frames in out idle for
1 BAGE1001 192.195.80.40:3822 Y P-BIND 327904E 4 4 0:22:35
2 BAGE1002 192.195.80.40:3867 Y ACT/SESS 327904E 8 7 0:21:20
3 BAGE1003 192.195.80.40:3981 Y ACT/SESS 327803E 13 14 0:10:13
4 BAGE1004 192.195.80.40:3991 Y ACT/NA 327803E 8 9 0:0:7
5 BAGE1005 192.195.80.40:3997 Y ACT/NA 327805 8 9 0:7:8
If a client at IP address 192.195.80.40 requests a terminal model of type IBM-3278-5, LU

BAGE1005 will be selected over BAGE1004.
lu name client-ip:tcp nail state model frames in out idle for
1 BAGE1001 192.195.80.40:3822 Y P-BIND 327904E 4 4 0:23:29
2 BAGE1002 192.195.80.40:3867 Y ACT/SESS 327904E 8 7 0:22:14
3 BAGE1003 192.195.80.40:3981 Y ACT/SESS 327803E 13 14 0:11:7
4 BAGE1004 192.195.80.40:3991 Y ACT/NA 327803E 8 9 0:1:1
5 BAGE1005 192.195.80.40:4052 Y ACT/SESS 327805 13 14 0:0:16

The TN3270 configuration modes and router command prompts are described in the following
sections and displayed in Figure 175. The TN3270 server can be configured only on the virtual
interface of a CMCC adapter.
Some configuration commands create entities on the CMCC adapter. 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 that 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 tasks in this
section 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, use the following command
in TN3270 DLUR configuration mode:
Command Purpose
lsap token-adapter 1 84 Create a DLUR LSAP and enter DLUR LSAP
configuration mode.
To return later to the DLUR LSAP configuration mode on the same entity, use the following
command in TN3270 DLUR configuration mode:
Command Purpose
lsap token-adapter 1 Enter DLUR LSAP configuration mode on the
same LSAP.
To remove an entity, the same identification parameters are needed. Use the following command
beginning in TN3270 DLUR configuration mode:
Command Purpose
no lsap token-adapter 1 Remove a previously defined DLUR LSAP entity.

TN3270 configuration modes described in this section include the following:

• TN3270 Server Configuration Mode
• DLUR Configuration Mode
• DLUR SAP Configuration Mode
• PU Configuration Mode
• Commands Allowed in Multiple Modes
Figure 175 TN3270 Configuration Modes
TN3270 Prompt:
configuration
mode tn3270-server>
Prompt:
TN3270 DLUR
configuration tn3270-dlur>
mode
TN3270 DLUR SAP Prompt:

configuration
mode tn3270-dlur-lsap>
Prompts:
TN3270/PU
TN3270 DLUR PU tn3270-pu>
configuration mode tn3270-dlur>
Use TN3270 PU configuration mode when

the TN3270 server is attached to a non-APPN
host.
Use TN3270 DLUR PU configuration mode

S4736
when the TN3270 server is attached to an

APPN host.
TN3270 Server Configuration Mode

From interface configuration mode, tn3270-server command puts you in TN3270 server
configuration mode. The following prompt appears:
tn3270-server>

DLUR Configuration Mode
DLUR Configuration Mode

From TN3270 server configuration mode, the dlur command puts you in DLUR configuration
mode. The following prompt appears:
tn3270-dlur>
DLUR SAP Configuration Mode

From DLUR server configuration mode, lsap command puts you in DLUR SAP configuration mode.
The following prompt appears:
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
The following prompts appear, depending on which mode you are in:
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:
• generic-pool {permit | deny}
• idle-time seconds
• ip precedence {screen | printer} value
• ip tos {screen | printer} value
• keepalive seconds
• shutdown
• tcp-port port-number
• unbind-action {keep | disconnect}
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 a CMCC adapter’s
virtual interface. Not all tasks are required. Refer to “TN3270 Configuration Examples” for
configuration examples.
Task List for Multiple APPN Hosts

When the host site uses APPN and the TN3270 server can reach multiple hosts, we recommend you
use DLUR and configure your PUs under DLUR. In this instance, perform the following tasks:
• Configure SNA Support
• Configure TN3270 Server
• Configure IP Precedence
• Configure IP TOS
• Configure DLUR
• Configure SAPs under DLUR
• Configure PUs under DLUR
• Configure LU Nailing
• 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 traffic will be routed through the
owning host.
Task List for Non-APPN Hosts

When the host site does not use APPN, you configure your PU parameters for a directly-connected
host. In this instance, perform the following tasks:
• Configure SNA Support
• Configure TN3270 Server
• Configure IP Precedence
• Configure IP TOS
• Configure PU Parameters on the TN3270 Server
• Configure LU Nailing
• Monitor the TN3270 Server

Configure SNA Support
Configure SNA Support

Host connectivity must be configured prior to configuring TN3270 support. This is accomplished in
one of three ways:
• Configure CSNA support. Refer to the section “Configure CSNA Support”.
• Configure CMPC support. Refer to the section “Configure CMPC Support.”
• Configure Token Ring Attachment to a FEP. Refer to the section “TN3270 Configuration
Examples.”
After the host connection is configured, begin the TN3270 configuration.
Configure TN3270 Server

This task is required. To establish a TN3270 server on the internal LAN interface on the CMCC
adapter, use the following commands beginning in global configuration mode:

1 interface channel slot/port Select the channel attach internal LAN
interface and enter interface configuration
mode.
2 tn3270-server Specify a TN3270 server on the internal LAN
interface and enter TN3270 configuration
mode.
3 maximum-lus max-number-of-lu-allocated (Optional) Configure maximum number of LUs
allowed.
4 client [ip [ip-mask]] lu maximum number (Optional) Configure LU session limits for
each client IP address or IP subnetwork
address.
5 timing-mark (Optional) Configure transmission of a WILL
TIMING-MARK.
6 tcp-port port-nbr (Optional) Assign a TCP port other than the
default of 23. This command is also available in
PU configuration mode.
7 idle-time num-of-seconds (Optional) Specify the idle time for server
disconnect. This command is also available in
8 keepalive num-of-seconds (Optional) Specify the maximum time allowed
between keepalive marks before the server
disconnects. This command is also available in
9 unbind-action {keep | disconnect} (Optional) Specify whether the TN3270
session will disconnect when an UNBIND
command is received. This command is also
available in PU configuration mode.
10 generic-pool {permit | deny} (Optional) Select whether “left-over” LUs can
be used from a generic LU pool. This command
is also available in PU configuration mode.
11 ip precedence {screen | printer} value (Optional) Specify the precedence level for IP
traffic in the TN3270 server.
12 ip tos {screen | printer} value (Optional) Specify the TOS level for IP traffic
in the TN3270 server.

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 IP Precedence
To configure IP precedence, use the following command in TN3270 server or TN3270 PU
configuration mode:
Command Purpose
ip precedence {screen | printer} value Configure the IP level.
Use the no ip precedence screen or the no ip precedence printer commands to return the
precedence value to a default of 0.
Configure IP TOS
To configure IP TOS, use the following command in TN3270 server or TN3270 PU configuration
mode:
Command Purpose
ip tos {screen | printer} value Configure the IP TOS delay level.
Use the no ip tos screen or the no ip tos printer commands to return the precedence value to a
default of 0.
Configure PU Parameters on the TN3270 Server

This task is required when configuring PUs that do not use DLUR. The first command, pu rmac
rsap lu-seed command is required. All other commands are optional. To configure PU parameters
for the TN3270 server, use the following commands beginning in TN3270 configuration mode:
Command Purpose
pu pu-name idblk-idnum ip-address type Enter PU configuration mode and create or delete PUs
adapno lsap [rmac rmac] [rsap rsap] [lu-seed with direct host links.
lu-name-stem]
tcp-port port-nbr (Optional) Assign a TCP port other than the default of
23. This command is also available in TN3270
configuration mode.
idle-time num-of-seconds (Optional) Specify the idle time for server disconnect.
This command is also available in TN3270
configuration mode.

Configure DLUR
Command Purpose
keepalive num-of-seconds Note (Optional) Specify the maximum time allowed
between keepalive marks before the server disconnects.
configuration mode. Note: To enable sending of
power-off Reply product set identification (PSID)
network management vector transport (NMVT) to the
host, the value should be set to 50000 more than the
desired value. If the configured value is greater than
50000, the value used for the keepalive function will be
50000 less than the configured value.
unbind-action {keep | disconnect} (Optional) Specify whether the TN3270 session will
disconnect when an UNBIND command is received.
configuration mode.
generic-pool {permit | deny} (Optional) Select whether “left-over” LUs can be used
from a generic LU pool. This command is also
available in TN3270 configuration mode.
ip precedence {screen | printer} value (Optional) Specify the precedence level for IP traffic in
the TN3270 server.
ip tos {screen | printer} value (Optional) Specify the TOS level for IP traffic in the
TN3270 server.
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, use the following commands beginning in TN3270 configuration mode:

1 dlur fq-cpname fq-dlusname Create a DLUR function in the TN3270 server and enter
DLUR configuration mode.
2 dlus-backup dlusname2 (Optional) Specify the fallback choice for the DLUR
DLUS.
3 preferred-nnserver NNserver (Optional) Specify the preferred network node (NN)
server.
4 client [printer] ip ip-address [mask] lu (Optional) Configure the IP address and nail type and
first-locaddr [last-locaddr] specify the locaddr range.

Configure SAPs under DLUR

To configure SAPs under the DLUR function, use the following commands beginning in DLUR
configuration mode:

1 lsap type adapno [lsap] Create a SAP function under DLUR and enter DLUR
SAP configuration mode.
2 vrn vrn-name (Optional) Identify an APPN virtual routing node (VRN).
3 link name [rmac rmac] [rsap rsap] (Optional) Create named links to hosts. A link should be
configured to each potential NN server. (The alternative is
to configure the NN servers to connect to DLUR.) If
VRN is used it is not necessary to configure links to other
hosts. Do not configure multiple links to the same host.
Configure PUs under DLUR

This task is required when configuring DLUR connected hosts. To configure PUs under the DLUR
function, use the following commands beginning in DLUR configuration mode:

1 pu pu-name idblk-idnum ip-address Create a PU function under DLUR and enter PU
configuration mode.
2 tcp-port port-nbr Assign a TCP port other than the default of 23.
3 idle-time num-of-seconds Specify the idle time for server disconnect.
4 keepalive num-of-seconds Specify the maximum time allowed between keepalive
marks before the server disconnects.
5 unbind-action {keep | disconnect} Specify whether the TN3270 session will disconnect
when an UNBIND command is received.
6 generic-pool {permit | deny} Select whether “left-over” LUs can be used from a
generic LU pool.
7 ip precedence {screen | printer} value (Optional) Specify the precedence level for IP traffic in
the TN3270 server.
8 ip tos {screen | printer} value (Optional) Specify the TOS level for IP traffic in the
TN3270 server.
The pu command entered in DLUR configuration mode has different parameters than when it is
entered from TN3270 configuration mode.

Configure LU Nailing
Configure LU Nailing
To configure LU nailing, use the following command in TN3270 PU configuration mode:
Command Purpose
client [printer] ip ip-address [mask] lu first-locaddr Configure the IP address and nail type
[last-locaddr] and specify the locaddr range.
The client command allows a client with multiple TN3270 connections from the same IP address to
nail their screen connections to LUs that are configured as screen LUs at the host and to nail printer
connections to LUs that are configured as printers at the host. When the connection is made, a device
type of “328*” is matched to a printer definition, and any other device type is matched to a screen
definition.

Configure CMPC Support
Monitor the TN3270 Server

The following table lists the monitoring commands 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:
Command Purpose
show extended channel slot/port tn3270-server Display the current server configuration parameters
and the status of the PUs defined in each server.
show extended channel slot/port tn3270-server Display information about all clients at a specific IP
client-ip-address ip-address [disconnected | address.
in-session | pending]
show extended channel slot/port tn3270-server Display the PU configuration parameters, statistics
pu-name and all the LUs currently attached to the PU.
show extended channel slot/port tn3270-server Display information about the TN3270 server LUs
pu pu-name lu locaddr [history] running on a CMCC adapter interface.
show extended channel slot/port tn3270-server Display mappings between a nailed client IP
nailed-ip ip-address address and nailed LUs
show extended channel tn3270-server pu-name Display the status of the LU.
lu lu-number [history]
show extended channel tn3270-server Display the information about LUs that are defined
client-ip-address ip-address under an IP address.
show extended channel slot/port tn3270-server Display information about the SNA session switch.
dlur
show extended channel slot/port tn3270-server Display information about the DLUR components.
dlurlink name
Configure CMPC Support

Cisco MultiPath Channel (CMPC) is Cisco System’s implementation of IBM’s MultiPath Channel
(MPC) feature. CMPC allows VTAM to establish Advanced-Peer-to-Peer Networking (APPN)
connections using both High Performance Routing (HPR) and Intermediate Session Routing (ISR)
through a channel-attached router platforms.
With CMPC, Cisco 7000 with RSP7000, Cisco 7500, and Cisco 7200 series routers can be deployed
in Parallel MVS systems complex (sysplex) configurations.
CMPC can be used to establish an APPN connection between VTAM and the following APPN
nodes:
• Another VTAM channel attached to the same CMCC adapter
• Another VTAM channel attached to a different CMCC adapter in the same router
• TN3270 server DLUR in the same CMCC adapter
• APPN network node (NN) in the router with the CMCC adapter
• Other APPN nodes external to the CMCC adapter and router with the CMCC adapter: CS/2,
AS/400, other LAN or WAN attached VTAM hosts
One read subchannel and one write subchannel are supported for each MPC transmission group. The
read subchannel and write subchannel may be split over two physical channel connections on the
same CMCC adapter.

CMPC Requirements
CMPC insulates VTAM from the actual network topology. The MPC protocols are terminated on the
CMCC adapter and converted to LLC protocols. After they are converted to LLC protocols, other
Cisco features can be used to connect VTAM to other APPN nodes in the network. CMPC can be
used in conjunction with DLSw+, RSRB, SR/TLB, SRB, SDLLC, QLLC, ATM LAN emulation,
and FRAS host to provide connectivity to VTAM.
CMPC supports connections to PU 2.1 nodes: APPN NN, APPN EN, and LEN. Subarea connections
are not supported.
The CMPC feature coexists on a CMCC adapter with the TCP/IP Offload, IP Datagram, TN3270,
and CSNA features.
CMPC Requirements
The following are minimum host system requirements to support CMPC:
• VTAM V4.2+, for MPC APPN ISR connections
• VTAM V4.3+, for MPC APPN HPR connections
CMPC Configuration Overview

To configure the CMPC feature, you must configure the host VTAM parameters and the CMCC
adapter. The CMPC Configuration Examples for CMPC show the VTAM configuration parameters
and the router configuration commands for each example.
The following guidelines will help you prepare for CMPC configuration:
• A CMPC link uses two subchannels: one read and one write. Some IBM implementations of
MPC allow multiple read and multiple write subchannels. CMPC will not support multiple read
and write subchannels. Only one read subchannel and one write subchannel can be configured
for each CMPC link. A CMPC link is also referred to as a CMPC transmission group.
• Multiple CMPC links can be configured between the host and the CMCC adapter in the
Cisco 7500, 7000, or 7200 series router.
• The two subchannels in a CMPC link need not be adjacent devices. Either channel may be the
read subchannel and either channel may be the write subchannel. The two subchannels can be on
separate channel process IDs in the host.
• The two subchannels must be connected to the same CMCC adapter, however they do not have
to be connected to the same physical channel interface. In other words, it is possible to connect
a read subchannel to channel interface 0, while the write subchannel is connected to the channel
interface.
• Only APPN connections will be supported across CMPC. For this reason when TN3270 server
is configured with CMPC, it must be configured as an APPN end node with DLUR.
• You must know what device addresses you will be using and the associated channel path
statements.
• You must know whether or not you will use HPR.
• To configure the LLC2 interface for the CMCC adapter, you will need to choose a local MAC
address and a local SAP address.
• You must know the remote MAC address and remote SAP of the LLC2 peer with which the
CMPC communicates.

Configuration Tasks
• You must know how to configure source-bridge ring groups on the CMCC adapter.
• On the router, the combination of one read subchannel definition, one write subchannel
definition, and a transmission group definition, associated by a unique tg-name, makes up a
CMPC transmission group specification.
To help clarify the configuration process, refer to Figure 176, which shows the CMPC link between
the VTAM host, the router, and CMCC adapter card, and the communication to the LLC2 end point.
The read and write addresses defined in the VTAM host correspond to the read and write paths
defined for CMPC. CMPC communicates with the LLC2 stack, which communicates to the end
point of the connection by means of the IEEE 802.2 link.
Figure 176 Logical View of CMPC Link
CMPC LLC2 LLC2 peer

(on CMCC adapter) 802.2 end point
ReadAddr Read path connection
WriteAddr Write path
Local node Local macaddr Peer macaddr
S6226
TRL node Local SAP Peer SAP
Configuration Tasks
This section describes the following configuration tasks associated with the CMPC feature. The first
two tasks are performed on the VTAM host. The remaining tasks are performed on the router. All
tasks are required.
• Configure the VTAM Transport Resource List Major Node
• Configure the VTAM Local SNA Major Node
• Configure the CMPC Subchannels
• Configure the CMPC Transmission Groups
• Configure the CMCC Adapter Internal LAN for CMPC
Configure the VTAM Transport Resource List Major Node

To configure MPC on the host, define the Transport Resource List (TRL) major node. See the
following IBM documents for details on how to configure the TRL major node:
• VTAM Resource Definition Samples, SC31-6554
• VTAM Operation, SC31-6549
• VTAM Network Implementation Guide, SC31-6548
The following is an example of a typical configuration:
LAGTRLA VBUILD TYPE=TRL
LAGTRLEA TRLE LNCTL=MPC,MAXBFRU=8,REPLYTO=3.0, X
READ=(2F0), X
WRITE=(2F1)

Configure the VTAM Local SNA Major Node
In this example, device 2F0 has been configured for read and 2F1 has been configured for write. The
command to activate the TRL should be issued before activating the Local node. If your TRL data
set was named LAGTRLA, the activate command would be as follows:
v net,act,id=lagtrla,update=add
where the ID parameter refers to the name of the data set containing the TRL definition.
Note that “update=add” is preferred and is the default for later versions of VTAM. The argument
“update=all” can cause inactive TRLEs to be deleted unexpectedly from ISTTRL. However,
“update=all” must be used if you change an active TRL data set and wish the changes to become
active. The following commands are useful for displaying the current list of TRLEs:
d net,trl
d net,id=isttrl,e
d net,trl,trle=trle_name
Configure the VTAM Local SNA Major Node

To configure the MPC channel link on the VTAM host, define the local SNA major node.
The following is an example of a typical configuration:
LAGLNA VBUILD TYPE=LOCAL
LAGPUA PU TRLE=LAGTRLEA, X
ISTATUS=ACTIVE, X
XID=YES,CONNTYPE=APPN,CPCP=YES,HPR=YES
The TRLE parameter in the local node refers to the label on the TRLE statement from the TRL major
node LAGTRLA. Also, if you do not want to run HPR set the HPR parameter to “NO.” The local
SNA major node must be activated after the TRL node has been activated. If your local node data set
was named LAGLNA, the activate command is as follows:
v net,act,id=laglna
Configure the CMPC Subchannels

To define a CMPC read subchannel and CMPC write subchannel, use the following commands in
interface configuration mode on a CMCC adapter physical interface:

1 cmpc path device tg-name read Configure the CMPC read subchannel.
2 cmpc path device tg-name write Configure the CMPC write subchannel.
These statements define the subchannel addresses that CMPC will use to connect to the host, and
correspond to the definitions in the TRL major network node on the host. Specifically the last two
hexadecimal digits in the read parameter match the device value configuration in the cmpc
command. The last two hexadecimal digits in the write parameter match the device value in the
cmpc command.
Use the no cmpc path device command to remove the definition of a subchannel.

Configuration Tasks
Configure the CMPC Transmission Groups

To define a CMPC transmission group by name and specify its connection to the LLC2 stack, use
the following command in interface configuration mode on a CMCC adapter virtual interface:
Command Purpose
tg tg-name llc type adaptno lsap [rmac rmac] [rsap rsap] Define the CMPC transmission group
name.
The tg command defines an LLC connection with a complete addressing 4-tuple. The lsap, rmac,
and rsap are specified explicitly by parameters. The lmac is the LMAC of the adapter referred to by
the type and adaptno parameters.
The tg-name must match the name given in the cmpc command issued in the physical interfaces on
the same CMCC adapter.
Use the no tg command to remove a CMPC transmission group from the configuration, which will
deactivate the named CMPC transmission group.
To change any parameter of the tg statement, the statement must be removed by using the no tg
tg-name command.
Configure the CMCC Adapter Internal LAN for CMPC

Configuring CMPC support on the CMCC adapter internal LAN is similar to configuring CSNA
support. Many of the configuration tasks are the same. To configure the internal LAN adapter on the
CMCC adapter to support CMPC, perform the following tasks:
• Configure the CMCC Adapter Internal LANs
• Configure SRB
• Configure LOCADDR Priority
• Configure SAP Priority
• Configure Internal Adapters
• Name the Internal Adapter
• Configure the Internal Adapter and Its Link Characteristics
• Configure the Internal Adapter and Its Link Characteristics
Configure the CMCC Adapter Internal LANs

To select a CMCC adapter internal LAN interface, use the following commands beginning in global
configuration mode:

1 interface channel slot/port Select the virtual interface.
2 lan tokenring lan-id Select the internal LAN interface and enter
internal LAN configuration mode.
Use the no lan command to disconnect all LLC2 sessions established through all internal LAN
interfaces configured on a particular internal LAN.
Up to 18 internal adapters can be configured on a CMCC adapter.

Configure the CMCC Adapter Internal LAN for CMPC
Configure SRB
Select the bridging characteristics for Token Ring and FDDI, or Ethernet. Use the following
command in internal LAN configuration mode:
Command Purpose
source-bridge local-ring bridge-number target-ring Select source-route bridging for the selected
LAN interface.
Configure LOCADDR Priority

Select the locaddr priority for the internal LAN. Use the following commands in internal LAN
configuration mode:
Command Purpose
locaddr-priority list-number Select locaddr priority for the selected LAN
interface.
Configure SAP Priority

Select the sap priority for the internal LAN. Use the following commands in internal LAN
configuration mode:
Command Purpose
sap-priority list-number Select sap priority for the selected LAN
interface.
Configure Internal Adapters

To select or configure an internal adapter, use the following command in internal LAN configuration
mode:
Command Purpose
adapter adapno mac-address Select the internal adapter to configure.
Name the Internal Adapter

Select a name for the internal adapter. Use the following command in internal adapter configuration
mode:
Command Purpose
name name Select a name for the internal adapter.
Naming an internal adapter is optional.
Configure the Internal Adapter and Its Link Characteristics

To configure the link characteristics of the internal LAN adapter, use the following commands in
internal LAN configuration:
Command Purpose
llc2 N1 bytes Maximum size of an I-frame in bytes.

CMCC Interface Configuration Examples
Command Purpose
llc2 N2 retry-count Maximum retry count.
llc2 Nw window-size-increase Increase the window size for consecutive good
I-frame received (zero is disabled).
llc2 ack-delay-time milliseconds Maximum time for incoming I-frames to stay
unacknowledged.
llc2 ack-max frame-count Maximum number of I-frames received before an
acknowledgment must be sent.
llc2 idle-time milliseconds Frequency of polls during periods of idle traffic.
llc2 local-window frame-count Maximum number of I-frames to send before
waiting for an acknowledgment.
llc2 recv-window frame-count Receive window.
llc2 t1-time milliseconds Specify amount of time to wait for an
acknowledgment to transmit I-frames.
llc2 busy-time milliseconds Amount of time to wait while the other LLC2
station is in a busy state before attempting to poll
the remote station.
llc2 tpf-time milliseconds Amount of time to wait for a final response to a
poll frame before resending the original poll
frame.
llc2 trej-time milliseconds Amount of time to wait for resending a rejected
frame before sending the reject command.
Configuring LLC parameters is optional. Default values are used when no parameters are
configured.

The following sections include examples to help you understand some aspects of interface
configuration:
• CPA Microcode Load Example
• IP Address and Network Mask Configuration Example
• CLAW Configuration Example
• CLAW Packing Configuration Examples
• Offload Configuration Example
• CSNA Configuration Example
• TN3270 Configuration Examples
• Configure TN3270 DLUR with CMPC Host Connection
• Static and Dynamic LUs with LU Nailing Configuration Example
• Removing LU Nailing Definitions Example
• Configuring Different Values for Precedence and TOS Example
• Overriding Configured Values Example
• Configure IP Host Backup Example

CPA Microcode Load Example
• CMPC Configuration Examples for CMPC
CPA Microcode Load Example

The following example copies a new image to Flash memory:
router#copy tftp:xcpa26-2 slot0:xcpa26-2
Address or name of remote host []? neptune

Translating "neptune"...domain server (10.20.30.10) [OK]
Destination filename [xcpa26-2]?
Accessing tftp://neptune/xcpa26-2...
Loading motto/xcpa26-2 from 10.20.30.10 (via FastEthernet0/0): !
Expanding slot0:xcpa26-2_kernel_xcpa (343148 bytes):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Expanding slot0:xcpa26-2_seg_802 (237848 bytes):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Expanding slot0:xcpa26-2_seg_cmpc (319960 bytes):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Expanding slot0:xcpa26-2_seg_csna (89856 bytes): !!!!!!!!!!!!!!!!!!
Expanding slot0:xcpa26-2_seg_eca (461424 bytes):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!
Expanding slot0:xcpa26-2_seg_offload (80344 bytes): !!!!!!!!!!!!!!!!
Expanding slot0:xcpa26-2_seg_pca (69376 bytes): !!!!!!!!!!!!!!
Expanding slot0:xcpa26-2_pseg_push (15936 bytes): !!!
Expanding slot0:xcpa26-2_seg_tcpip (158896 bytes): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Expanding slot0:xcpa26-2_seg_tn3270 (601784 bytes):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 2387456/4774912 bytes]
2387456 bytes copied in 110.588 secs (21704 bytes/sec)
router#
After copying a CMCC ucode image to flash memory, a directory command of the flash device
displays the following:
Router#dir slot0:
Directory of slot0:/
1 -rw- 1 Aug 18 1998 12:29:12 xcpa26-2
2 -rw- 344438 Aug 18 1998 12:29:12 xcpa26-2.kernel_xcpa
3 -rw- 237848 Aug 18 1998 12:29:37 xcpa26-2.seg_802
4 -rw- 319960 Aug 18 1998 12:29:56 xcpa26-2.seg_cmpc
5 -rw- 89856 Aug 18 1998 12:30:15 xcpa26-2.seg_csna
6 -rw- 461424 Aug 18 1998 12:30:20 xcpa26-2.seg_eca
7 -rw- 80344 Aug 18 1998 12:31:03 xcpa26-2.seg_offload
8 -rw- 69376 Aug 18 1998 12:31:07 xcpa26-2.seg_pca
9 -rw- 15936 Aug 18 1998 12:31:11 xcpa26-2.seg_push
10 -rw- 158896 Aug 18 1998 12:31:12 xcpa26-2.seg_tcpip
11 -rw- 601784 Aug 18 1998 12:31:32 xcpa26-2.seg_tn3270
7995392 bytes total (5614116 bytes free)
The following example loads the microcode from an individual microcode image that is stored as a
file in Flash memory:
Router(config)# microcode ecpa slot0:xcpa26-2
Router(config)# microcode reload

IP Address and Network Mask Configuration Example

The following example assigns an IP address and network mask to the IBM channel attach interface
on the router:
ip address 197.91.2.5 255.255.255.0
CLAW Configuration Example

The following example configures the IBM channel attach interface to support a directly connected
device:
claw 0100 00 197.91.2.2 VMSYSTEM C7000 TCPIP TCPIP
CLAW Packing Configuration Examples

The following example configures the IBM channel attach interface to support CLAW packing on
HOSTA and HOSTC and the nonpacked version of CLAW on HOSTB:
interface Channel0/0
ip address 172.18.4.49 255.255.255.248

no keepalive
claw C010 F2 172.18.4.50 HOSTA RTRA PACKED PACKED
claw C020 F4 172.18.4.52 HOSTB RTRA TCPIP TCPIP
claw C030 F6 172.18.4.53 HOSTC RTRA PACKED PACKED
The following is an example of a CLAW definition in the host configuration file for IOS/390:
000100 *---------------------------------------------
000200 * Member: IOS390R2.V510.PARM(TCPCFGxx)
000300 * Description: TCP task group configuration
000400 *---------------------------------------------
000500
000600 * Define the virtual medium
000700
000800 MEDIA VIRTUAL MTU(4096) NAME(LOOPBACK)
000900
001000 * Define the physical medium
001100
001200 MEDIA CLAW MTU(4096) NAME(ROGCLAW) ASSIST
001300
001400 * Define the host
001500
001600 NETWORK IPADDRESS(172.18.4.50)
001700 SUBNET(255.255.255.248)
001800
001900 *
002000
002100 CLAW DEVADDR(8f2)
002200 BUFSIZE(32768)
002300 IBUF(5)
002400 OBUF(5)
002500 RESTART(60)
002600 HOSTNAME(HOSTA)
002700 WSNAME(RTRA)
002800 START
002900 PACKED
003000
003100 * Define gateway
003200
003300 ROUTE DEST(0.0.0.0) ROUTE(172.18.4.49)

CLAW Packing Configuration Examples
003400
003500 * Define the transport pr
003600
003700 TCP MAXRCVBUF(131072)
003800 MAXSNDBUF(131072)
003900 DEFRCVBUF(131072)
004000 DEFSNDBUF(131072)
004100 DELAYACK(2)
004200 FASTRX(3)
004300 MAXRXMIT(18)
004400 MINDEV(90)
004500 PORTUSE(1:4095)
004600 PORTASGN(4096:8191)
004700
004800 UDP MAXRCVBUF(64000)005200 PORTUS
004900 MAXSNDBUF(64000)
005000 DEFRCVBUF(64000)
005100 DEFSNDBUF(64000)005300 PORTAS
005200 PORTUSE(1:4095)
005300 PORTASGN(4096:8191)
005400
005500 RAW MAXRCV
005600 MAXSND
005700

Offload Configuration Example

The following example consists of the mainframe host profile statements, buffer poolsize
recommendations, and router configuration statements for the network shown in Figure 177.
Figure 177 Offload Network Configuration Block Diagram
Switch
Route
processor
processor
MEMD
CBus
MEMD handler
Interface
API link
processor TCP/IP
IP link stack
CIP1 Offload application
CLAW
ECA PCA
162.18.4.57
C3
ESCON
director
C6
162.18.4.59
ESCON channel Bus/Tag channel
CLAW
IBM TCP/IP stack

mainframe IP link
(CISCOVM) API
API link
S3711
SMTP FTP TCP/IP apps.
Host Profile Statements

; Device statement
DEVICE OFF CLAW 762 CISCOVM CIP1 NONE 20 20 4096 4096
!
; Link Statements (both needed)
LINK OFFL OFFLOADLINK1 1 OFF
LINK MEMD OFFLOADAPIBROAD 162.18.4.59 OFF OFFL
!
; Home Statement
; (No additional home statements are added for offload)
!
!
; Routing information (if you are not using the ROUTED SERVER)
GATEWAY
; NETWORK FIRST HOP DRIVER PCKT_SZ SUBN_MSK SUBN_VALUE
162.18 = MEMD 4096 0.0.255.248 0.0.4.56
DEFAULTNET = MEMD 1500 0
!

Offload Configuration Example
;START statements
START OFF
!
Router Configuration Statements

The following statements configure the offload feature in the router. When you configure a
host-to-host communication through the same channel interface, include the no ip redirects and
ip route-cache same-interface commands:
ip address 162.18.4.57 255.255.255.248
no ip redirects
ip route-cache same-interface
no keepalive
offload C300 62 162.18.4.59 CISCOVM CIP1 TCPIP TCPIP TCPIP API

CSNA Configuration Example

The following configuration is an example of configuring CSNA on a Cisco 7500 router with a CIP.
Figure 178 illustrates this configuration example.
Figure 178 CIP CSNA Internal LAN Network Diagram
VTAM 1 VTAM 2
CH4/0 PCA 0 Physical ECA 1 CH4/1 SAP values

channel are defined
interface in the XCA
major node.
CSNA 10100 80 CSNA E 200 20
4000.7500.4230 04 04 4000.7500.4234 Internal

Internal
adapters adapters
4000.7500.4231 08 0C 4000.7500.4238
SAP Local loopback only

Token
Token internal adapters.
Ring
Ring No bridging to
142
Cisco IOS.
Internal Internal
TR LAN 3 TR LAN 4
Virtual channel interface CIP
CH4/2 CBus
DLSw+ VRG SR/ TLB

2000 Bridge 1 444
TCP/IP TB group 1
Bridge 1
S1/0 TR2/0 E3/0 Cisco 7500
10.30.2.2
Token
Ring D2
120 D1
IP cloud
D3
10.30.2.1
D5
Cisco 4500
S3597
Token
Ring D4
201
source-bridge ring-group 2000

source-bridge transparent 2000 444 1 1
dlsw remote-peer 0 tcp 10.30.3.1
dlsw local-peer peer-id 10.30.2.2
!
interface serial 1/0
ip address 10.30.2.2 255.255.255.128

CSNA Configuration Example
clockrate 56000
!
interface tokenring 2/0
mac-address 4000.7500.0200
no ip address
ring-speed 16
source-bridge 120 1 2000
source-bridge spanning
!
interface ethernet 3/0
mac-address 0200.ae00.c000
no ip address
bridge-group 1
!
interface channel 4/0
no ip address
no ip directed-broadcast
no keepalive
csna 0100 80
!
no ip address
no keepalive
csna E200 20 maxpiu 65535 time-delay 100
!
no ip address
no keepalive
max-llc2-sessions 2500
lan TokenRing 3
adapter 0 4000.7500.4230
llc2 local-window 1
llc2 ack-max 1
adapter 1 4000.7500.4231
lan TokenRing 4
adapter 7 4000.7500.4234
adapter 8 4000.7500.4238
!
bridge 1 protocol ieee

ECPA CSNA Configuration Example

The following configuration is an example of configuring CSNA on a Cisco 7200 router with a
ECPA. Figure 179 illustrates this configuration example.
Figure 179 ECPA CSNA Translational Bridging Configuration Example
VTAM 1
Physical channel interface ECA 0 CH4/0 SAP values

are defined
in the XCA
major node.
CSNA E200 30 CSNA E200 40
4000.7500.4230 04 04 4000.7500.4234 Internal

Internal
adapters adapters
4000.7500.4231 08 0C 4000.7500.4238
SAP Local loopback only

Token
Token internal adapters.
Ring
Ring No bridging to
142
Cisco IOS.
Internal Internal
TR LAN 3 TR LAN 4
Virtual channel interface ECPA
CH4/0 CBus
DLSw+ VRG SR/ TLB

2000 Bridge 1 444
TCP/IP TB group 1
Bridge 1
S1/0 TR2/0 E3/0 C7200
10.30.2.2
Token
Ring D2
IP cloud 120 D1
D3
10.30.2.1
D5
Cisco 4500
15017
Token
Ring D4
201

source-bridge transparent 2000 444 1 1
dlsw remote-peer 0 tcp 10.30.3.1
dlsw local-peer peer-id 10.30.2.2
!
interface serial 1/0
ip address 10.30.2.2 255.255.255.128
clockrate 56000
!

TN3270 Configuration Examples
interface tokenring 2/0

mac-address 4000.7500.0200
no ip address
ring-speed 16
source-bridge spanning
!
interface ethernet 3/0
mac-address 0200.ae00.c000
no ip address
bridge-group 1
!
no ip address
no keepalive
csna E200 30 maxpiu 65535
CSNA E200 40 maxpiu 65535
max-llc2-sessions 2500
lan TokenRing 3
adapter 0 4000.7500.4230
llc2 local-window 1
llc2 ack-max 1
adapter 1 4000.7500.4231
lan TokenRing 4
adapter 7 4000.7500.4234
adapter 8 4000.7500.4238
!
bridge 1 protocol ieee
TN3270 Configuration Examples

The following configuration has three PUs using DLUR and two more with direct connections.
The initial CIP configuration is as follows:
ip address 10.10.20.126 255.255.255.128
no ip redirects
no keepalive
lan TokenRing 0
adapter 0 4100.cafe.0001
llc2 N1 2057
llc2 N1 2057
Configuration 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 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
! create direct pus for the non-APPN Host

! note that they must use different lsaps because they go to the same Host
router(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)#end
The resulting configuration from the initial configuration and the configuration dialog follows:
ip address 10.10.20.126 255.255.255.128
no ip redirects
no keepalive
lan TokenRing 0
llc2 N1 2057
llc2 N1 2057
tn3270-server
pu 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.VMG
lsap token-adapter 1
vrn SYD.LAN4
link HOSTB rmac 4000.7470.0009
link HOSTA rmac 4100.cafe.0001 rsap 08
pu PU0 05D99001 10.10.20.1
pu PU1 05D99002 10.10.20.1
pu PU2 05D99003 10.10.20.2

Configure TN3270 DLUR with CMPC Host Connection
Configure TN3270 DLUR with CMPC Host Connection

The following example shows a DLUR PU with a CMPC host connection.
no ip address
no keepalive
cmpc C010 E5 LPAR1TG READ
cmpc C010 E6 LPAR1TG WRITE
cmpc C020 00 LPAR2TG READ
cmpc C020 01 LPAR2TG WRITE
!
ip address 172.18.5.1 255.255.255.224
no keepalive
lan TokenRing 0
adapter 0 4000.4040.0000 ! for cmpc
adapter 1 4000.6060.0000 ! TN3270 server
adapter 2 4000.7070.0000
tn3270-server
maximum-lus 20000 ! optional
idle-time 64800 ! optional
timing-mark ! optional
tcp-port 24 ! optional
client 10.10.10.0 255.255.255.0 lu maximum 10000 ! optional
dlur NETA.TN3270CP NETA.CPAC
dlus-backup NETA.MVS2 ! optional
preferred-NNserver NETA.CPAC ! optional
lsap token-adapter 1 04 ! TN3270 server uses cmcc adapter 1 and sap=04
link LINK1 rmac 4000.4040.0000 rsap 08 ! link to cmpc on adapter 0
lsap token-adapter 2 04
link LINK2 rmac 4000.7070.0000 rsap 08 ! link to cmpc on adapter 2
pu TNPU1 0175 4321 172.18.5.2
!
tg LPAR1TG llc token-adapter 0 08 rmac 4000.6060.0000 rsap 04 ! rsap optional
tg LPAR2TG llc token-adapter 2 08 rmac 4000.7070.0000 ! rsap=04 by default"
Static and Dynamic LUs with LU Nailing Configuration Example

The following example shows a direct PU and a DLUR PU configured with the same listening point.
The PUs are configured with the same nailed client IP address.
tn3270-server
pu PU1 05D18081 172.28.1.82 token-adapter 1 24 rmac 4100.cafe.0001 lu-seed PU3###
client ip 192.195.80.40 lu 1 10
dlur
pu PU2 05D190B3 172.28.1.82 token-adapter 1 28 rmac 4100.cafe.0001 lu-seed PU4###
client ip 192.195.80.40 lu 1 10
Assuming each PU has three static LUs, which are ACTLU enabled and not connected, then these
LUs are the first to be nailed. That is, the first six connections from client IP address 192.195.80.40
use the static LUs and subsequent connections use the remaining dynamic LUs.

Removing LU Nailing Definitions Example

In the following example, locaddrs 1 to 50 are reserved for all remote screen devices in the
171.69.176.0 subnet.
tn3270-server
pu BAGE4
client ip 171.69.176.28 255.255.255.0 lu 1 50
To remove a nailing definition, the complete range of locaddrs must be specified as configured. So
for the example above, the following command would remove the LU nailing definition.
no client ip 171.69.176.28 255.255.255.0 lu 1 50
If an attempt is made to remove a subset of the range of configured locaddrs then the command is
rejected.
no client ip 171.69.176.28 255.255.255.0 lu 1 20
% client ip 171.69.176.28 lu not matched with configured lu 1 50
Configuring Different Values for Precedence and TOS Example

The following example changes IP precedence and IP TOS to different values under the TN3270
server for both the screen and printer. Note that any PUs defined under this configuration will inherit
these values unless the corresponding parameter is specifically changed for that PU.
tn3270-server
ip precedence screen 6
ip precedence printer 3
ip tos screen 8
ip tos printer 4
Overriding Configured Values Example

In the following example, the PU PUS1 uses the IP TOS precedence screen and printer values from
the values provided in TN3270 server configuration mode. PUS2 uses the IP TOS screen and printer
values defined in TN3270 server configuration mode. However, different values for IP precedence
are provided for PUS2 under PU configuration mode.
tn3270-server
ip tos screen 8
ip tos printer 4
pu PUS1 05D18009 172.28.1.101 token-adapter 0 AC rsap 08
pu PUS2 05D18071 172.28.1.99 token-adapter 0 A4 rmac 4000.7470.00e7
Configure IP Host Backup Example

Figure 180 shows the backup connection occurring between System B mainframe3 when mainframe
2 fails.

Configure IP Host Backup Example
Figure 180 IP Host Backup Configuration
Normal operation
LPAR 1
LPAR 2
LPAR 3
System A ESCON director
198.92.5.2 Mainframe 1
C0
LPAR 1 C1 C5 CIP
LPAR 2
LPAR 3 C2 Cisco 7500
System B router
LPAR 1
LPAR 2
LPAR 3
System C
Mainframe 2 fails
LPAR 1
LPAR 2
LPAR 3
C0
LPAR 1 C1 C5 CIP
LPAR 2
System B router
LPAR 1
LPAR 2
System C LPAR 3
Mainframes 1 and 2 fail

LPAR 1
LPAR 2
LPAR 3
C0
LPAR 1 C1 C5 CIP
LPAR 2
System B
router
LPAR 1
LPAR 2
System C LPAR 3
10408

The intent of this backup configuration is that the system named A will be loaded on one of the
mainframes in LPAR1 on that mainframe. The DASD for that system will be shared among all the
mainframes but only one of them will ever IPL the system at one time. The same holds for LPAR2
and LPAR3.
The ESCON director has the following connections:
• A Cisco 7500 series router with a CIP connected to port C5
• Mainframe1 connected to C0
The following examples show how to configure IP Host Backup for three mainframe hosts,
Mainframe 1, Mainframe 2, and Mainframe 3, as shown in Figure 180. Each mainframe is
configured for at least three logical partitions (LPARs).
Excerpts from the host TCP/IP profiles show how the host might be configured. Excerpts from the
router configuration show how the IP Host Backup configuration statements are configured.
Host TCP/IP Profiles

The DEVICE and HOME statements in the nine TCP/IP profiles are similar to the following:
LPAR1 (mainframes 1, 2, 3):
DEVICE CIP1 CLAW 630 LPAR1 CIP1 NONE 20 20 4096 4096
LINK CIP1L IP 0 CIP1
HOME
198.92.5.2 CIP1L

HOME
198.92.5.3 CIP1L

HOME
198.92.5.4 CIP1L
Router Configuration
On the router, the CIP is located in slot 3 and port 1 is connected to the ESCON director. The path
commands define the group of paths that are used as the IP Host Backup.
ip address 198.92.5.1 255.255.255.128
path c010 c110 c210
claw 30 198.92.5.2 lpar1 cip1 tcpip tcpip
path c020 c120 c220
path c030 c130 c230

CMPC Configuration Examples for CMPC

This section provides sample configurations for the CMPC feature. Throughout these configuration
samples, a Cisco 7500 router with an RSP is used to illustrate the configurations. The configurations
also apply to a Cisco 7000 router with an RP or an RSP installed. All SAP values are written in
hexadecimal form.
Refer to the following configuration examples to see how different networked systems can be
configured:
• Connecting VTAM to a Remote PC with Communications Server/2 Example
• Connecting VTAM to the APPN NN on the CIP Example
• Connecting Two VTAM Nodes Using Two CIPs in the Same Router Example
• Connecting VTAM to the APPN NN on a Remote Router with DLUR Example
• TN3270 Server DLUR Running on the Same CIP Example
Connecting VTAM to a Remote PC with Communications Server/2 Example

Figure 181 shows the physical components for this example. Figure 182 shows the various
parameters for each component in the configuration example.
Figure 181 Topology for VTAM-to-Remote PC with Communications Server/2
Mainframe 1
VTAM
CMPC
LLC2
CIP
APPN
Bridging network
subsystem
S6221
RSP PC running
Communications Server/2
Cisco 7500
In Figure 181, the following activity occurs:

• VTAM connects to the CMPC driver on the CIP.
• The CMPC driver converts the data to an LLC data stream and passes the data to the LLC2 stack
on the CIP.
• The LLC2 stack on the CIP passes the data to the bridging code on the RSP.
• The bridging code on the RSP passes the data to the APPN network.

Figure 182 Parameters for VTAM-to-Remote PC with Communications Server/2
Mainframe neta.mvs2 Router Honduras
2F0 read CIP. slot 6

2F1 write cmpc-tg lagunaa
Adapter 1
4000.0000.aaaa
Ring 88
3
PC Laguna
Communications
Server/2
Ring 100
S6227
TR0/0
Link: LAGUNAA
4 Ring 500 SAP: 14
LMAC: 4000.0000.beef
The example in Figure 182 shows CMPC running on the CIP and communicating with a PC running
Communications Server/2. APPN is not running on the router. It is only running in VTAM and on
the PC.
The configuration examples for the VTAM host and the router follow.
TRL Node LAGTRLA on MVS2
LAGTRA VBUILD TYPE=TRL

LAGTRLA TRLE LNCTL=MPC,MAXBFRU=8,REPLYTO=3.0, X
READ=(2F0), X
WRITE=(2F1)
Local Node LAGLNA on MVS2
LAGNNA VBUILD TYPE=LOCAL

LAGPUA PU TRLE=LAGTRLA, X
ISTATUS=ACTIVE, X
XID=YES,CONNTYPE=APPN,CPCP=YES,HPR=YES

Connecting VTAM to a Remote PC with Communications Server/2 Example
Configuration for Honduras Router

!
interface TokenRing0/0
no ip address
ring-speed 16
!
interface Ethernet1/0
ip address 172.18.3.24 255.255.255.0
!
no ip address
no keepalive
cmpc C020 F0 LAGUNAA READ
cmpc C020 F1 LAGUNAA WRITE
!
no ip address
no keepalive
lan TokenRing 0
adapter 1 4000.aaaa.aaaa
tg LAGUNAA llc token-adapter 1 18 rmac 4000.0000.beef rsap 14
Activate the Configuration

To activate the configuration, issue the following commands from MVS2:
v net,act,id=lagtrla,update=add
v net,act,id=laglna

Connecting VTAM to the APPN NN on the CIP Example

Figure 183 Topology for VTAM-to-APPN NN Connection on the CIP
Mainframe 1
VTAM
CMPC
LLC2
CIP
LLC2
APPN
APPN network
S6222
RSP
PC running
Cisco 7500 Communications
Server/2

• VTAM connects to the CMPC driver on the CIP.
• The CMPC driver converts the data to an LLC data stream and passes the data to the LLC2 stack
on the CIP.
• The LLC2 stack on the CIP passes the data to the LLC2 stack on the RSP.
• The LLC2 stack on the RSP passes the data to APPN on the RSP.
• APPN on the RSP sends the data to the APPN network.

Connecting VTAM to the APPN NN on the CIP Example
Figure 184 Parameters for VTAM-to-APPN NN Connection on the CIP
Mainframe neta.mvs2 Router Honduras
CIP. slot 6
2F2 read cmpc-tg lagunab
2F3 write
Adapter 2
SAP 20
4000.bbbb.bbbb
Ring 88
3
PC Laguna
Communications
Server/2
Ring 100
4
2 TR0/0
Link: dynamic
Ring 61 Ring 500 SAP: 14
4000.0000.bbbb
SAP 24
APPN port: rsrport
Dest: 4000.0000.beef
Dest: SAP 14
APPN link: lagunab
APPN CP,
S6228
NETA.HONDURAS
The configuration illustrated in Figure 184 is more complex because you must configure APPN on
the router. There are many different ways to configure APPN. The example is a simple APPN
configuration in which SRB is used to connect the APPN NN on the RSP to VTAM and the
token-ring attached PC.
It is possible to connect directly to the Token Ring port, an option not shown in the example.
When configuring APPN on the router, you must type the complete command before exiting an
APPN configuration subsection. If you need to change an APPN configuration subsection, you must
type the no complete command before you can change the subsection. Remember to type complete
before exiting the subsection. The router ignores the new APPN configuration commands until you
type the complete command.
Configuration for TRL Node LAGTRLB
LAGTRB VBUILD TYPE=TRL

LAGTRLB TRLE LNCTL=MPC,MAXBFRU=8,REPLYTO=3.0, X
READ=(2F2), X
WRITE=(2F3)

Local SNA Major Node LAGLNB
LAGNNB VBUILD TYPE=LOCAL

LAGPUB PU TRLE=LAGTRLB, X
ISTATUS=ACTIVE, X
XID=YES,CONNTYPE=APPN,CPCP=YES
Honduras Router
no ip address
no keepalive
cmpc C020 F2 LAGUNAB READ
cmpc C020 F3 LAGUNAB WRITE
!
no ip address
no keepalive
lan TokenRing 0
adapter 2 4000.bbbb.bbbb
lan TokenRing 2
tg LAGUNAB llc token-adapter 2 20 rmac 4000.0000.bbbb rsap 24
!
!
appn control-point NETA.HONDURAS
complete
!
appn port RSRBPORT rsrb
local-sap 24
desired-max-send-btu-size 4096
max-rcv-btu-size 4096
rsrb-virtual-station 4000.0000.bbbb 61 2 100
complete
!
appn link-station LAGUNAB
port RSRBPORT
lan-dest-address 4000.0000.beef 14
complete
router eigrp 109
network 172.18.0.0

After all configurations are in place, the following commands can be used to start up the links. On
the MVS system, use the following commands:
v net,act,id=lagtrlb,update=add
v net,act,id=laglnb
On the router, use the following command from the global configuration mode:
appn start

Connecting Two VTAM Nodes Using Two CIPs in the Same Router Example
Figure 185 Topology for VTAM-to-VTAM Connection
Mainframe 1 Mainframe 2
VTAM VTAM
CIP LLC2 provides the

link-layer communication
services between the
two CIP cards
CMPC CMPC
LLC2 LLC2
CIP 1 CIP 2
LLC2 stack
on RSP
RSP is not used
S6223
Cisco 7500

• VTAM on Mainframe 1 passes MPC data to the CMPC driver on CIP 1.
• The CMPC driver on CIP 1 passes the data to the LLC2 stack.
• LLC2 sends the data to CIP 2 in the same router via IEEE 802.2.
• The LLC2 stack on CIP 2 passes the data to the CMPC driver on CIP 2, which passes the data to
VTAM on Mainframe 2.
The CIPs could be in different routers or both VTAM connections could be to the same CIP.
Figure 186 shows parameters for VTAM-to-VTAM connection.

Figure 186 Parameters for VTAM-to-VTAM Connection
neta.mvs2 neta.cpac
mvs2trlc cpactrlc
mvs2lnc cpaclnc
Read Write Read Write

2F4 2F5 840 841
mvs2c CIP CIP cpac2c
Adapter 3 Adapter 3
4000.cccc.cccc 4000.0000.cccc
SAP: 30 SAP: 34
Ring 88 Ring 43
S6229
Ring 100
Cisco 7500
Differing solutions can be configured for the example shown in Figure 186. For example, you can
have two CIPs in different routers connected via LLC2. You can also configure host connections
going into the same CIP card rather than two separate CIP cards.
mvs2trlc
MVS2TRC VBUILD TYPE=TRL

MVS2TRLC TRLE LNCTL=MPC,MAXBFRU=8,REPLYTO=3.0, X
READ=(2F4), X
WRITE=(2F5)
mvs2lnc
MVS2NNC VBUILD TYPE=LOCAL

MVS2PUC PU TRLE=MVS2TRLC, X
ISTATUS=ACTIVE, X
cpactrlc
CPACTRC VBUILD TYPE=TRL

CPACTRLC TRLE LNCTL=MPC,MAXBFRU=8,REPLYTO=3.0, X
READ=(840), X
WRITE=(841)

cpaclnc
CPACNNC VBUILD TYPE=LOCAL

CPACPUC PU TRLE=CPACTRLC, X
ISTATUS=ACTIVE, X
Router
no ip address
no keepalive
cmpc C010 40 CPACC READ
cmpc C010 41 CPACC WRITE
!
no ip address
no keepalive
lan TokenRing 0
adapter 3 4000.0000.cccc
tg CPACC llc token-adapter 3 34 rmac 4000.cccc.cccc rsap 30
!
no ip address
no keepalive
cmpc C020 F4 MVS2C READ
cmpc C020 F5 MVS2C WRITE
!
lan TokenRing 0
adapter 3 4000.cccc.cccc
tg MVS2C llc token-adapter 3 30 rmac 4000.0000.cccc rsap 34

On the MVS system MVS2, use the following commands to activate the configuration:
v net,act,id=mvs2trlc,update=add
v net,act,id=mvs2lnc
On the MVS system CPAC, use the following commands to activate the configuration:
v net,act,id=cpactrlc,update=add
v net,act,id=cpaclnc

Connecting VTAM to the APPN NN on a Remote Router with DLUR Example

Figure 187 shows the physical components for the DLUS-to-DLUR configuration. Figure 188
shows the various parameters for each component in the configuration example.
Figure 187 Topology for VTAM-to-APPN NN on a Remote Router with DLUR Connection
VTAM
NN
DLUS
PU 2.0
CMPC
LLC2 APPN
LAN/WAN
DLUR
CIP Remote node
Cisco 7500
S6224
LAN/WAN
PU 2.1

Connecting VTAM to the APPN NN on a Remote Router with DLUR Example
Figure 188 Parameters for VTAM-to-APPN NN on a Remote Router with DLUR Connection
Mainframe neta.mvs2 Cisco 7500 Honduras

neta.mvs2
CIP. slot 6
2F6 read cmpc-tg configd
DLUS
2F7 write
Adapter 4
mvs2trld 4000.dddd.dddd
mvs2lnd SAP 40
Ring 88
3 PC Laguna
Communications
Ring 100
Server/2
TR0/0
Link: dynamic
Ring 500 SAP: 14
2
Ring 84
Ring 94
4000.0000.dddd
SAP 44
APPN port: rsrport
Dest: 4000.0000.beef
Dest: SAP 14
APPN link: lagunad
DLUR
APPN CP,
S6230
NETA.DUSTIN
Cisco 4000
In the example shown in Figure 188, DLUS is running on the MVS host. DLUR is running on a
remote Cisco 4000 router. The connection from MPC to the APPN stack on the Cisco 4000 is via
LLC2. There is no NN on the Cisco 7500. The PC is running Communications Server/2.
mvs2trld
MVS2TRD VBUILD TYPE=TRL

MVS2TRLD TRLE LNCTL=MPC,MAXBFRU=8,REPLYTO=3.0, X
READ=(2F7), X
WRITE=(2F6)

mvs2lnd
MVS2NND VBUILD TYPE=LOCAL

MVS2PUD PU TRLE=MVS2TRLD, X
ISTATUS=ACTIVE, X
Additional Configuration for Router Honduras
cmpc C020 F6 CONFIGD WRITE
cmpc C020 F7 CONFIGD READ
!
lan TokenRing 0
adapter 4 4000.dddd.dddd
tg CONFIGD llc token-adapter 4 40 rmac 4000.0000.dddd rsap 44
Router Dustin
interface Ethernet0
ip address 172.18.3.36 255.255.255.0
media-type 10BaseT
!
interface TokenRing0
no ip address
ring-speed 16
!
appn control-point NETA.DUSTIN
dlus NETA.MVS2
dlur
complete
!
appn port RSRBPORT rsrb
local-sap 44
desired-max-send-btu-size 4096
max-rcv-btu-size 4096
rsrb-virtual-station 4000.0000.dddd 94 5 84
complete
!
appn link-station LAGUNAD
port RSRBPORT
lan-dest-address 4000.0000.beef 14
complete
!
appn link-station MVS2D
port RSRBPORT
lan-dest-address 4000.dddd.dddd 40
complete

TN3270 Server DLUR Running on the Same CIP Example

On the MVS2 system, use the following commands to activate the configuration:
v net,act,id=mvs2trld,update=add
v net,act,id=mvs2lnd
On the router Dustin, use the following command from the global configuration mode:
appn start

Figure 189 Topology for VTAM-to-TN3270 Server DLUR Running on the Same CIP
Connection
VTAM
NN
CMPC TN3270 server, EN

IP connection
LLC2 TCP/IP
S6225
TN3270 client
Cisco 7500

• The TN3270 server on the CMCC adapter takes on the role of an APPN EN running DLUR.
• The APPN NN in VTAM communicates with the CMPC driver over the channel.
• The CMPC driver on the CMCC adapter passes the data to the LLC2 stack on the CIP via a
fast-path loopback driver to the TN3270 server on the CIP.
• The TN3270 server converts the 3270 data stream to a TN3270 data stream and forwards the
packets to the IP TN3270 clients in the IP network.
The TN3270 server does not have to be in the same CMCC adapter as the CMPC driver.

Figure 190 Parameters for VTAM-to-TN3270 DLUR Running on the Same Connection
Mainframe neta.mvs2
neta.mvs2
CIP, slot 6
2F8 read cmpc-tg lagunab TN3270 server
2F9 write
mvs2trle Adapter 5
mvs2lne SAP: 50
4000.eeee.eeee Adapter 3
4000.0000.eeee
SAP: 34
S6231
Ring 88
172.18.1.218
Cisco 7500 Honduras IP connection
PC Laguna
172.18.1.1.30
TN3270 client
The following configurations apply to the example shown in Figure 190.
mvs2trle
MVS2TRE VBUILD TYPE=TRL

MVS2TRLE TRLE LNCTL=MPC,MAXBFRU=8,REPLYTO=3.0,
READ=(2F8),
WRITE=(2F9)
mvs2lne
MVS2NNE VBUILD TYPE=LOCAL

MVS2PUE PU TRLE=MVS2TRLE,
ISTATUS=ACTIVE,
swlagtn
SWLAGTN VBUILD TYPE=SWNET,MAXGRP=10,MAXNO=10,MAXDLUR=10

LAGTNPU PU ADDR=01, X
MAXPATH=1, X
IDBLK=017,IDNUM=EFEED, X
PUTYPE=2, X
MAXDATA=4096, X
LUGROUP=TNGRP1,LUSEED=LAGLU##

tngrp1
TNGRP1E VBUILD TYPE=LUGROUP

TNGRP1 LUGROUP
DYNAMIC LU DLOGMOD=D4C32XX3, X
MODETAB=ISTINCLM,USSTAB=USSTCPIP,SSCPFM=USS3270
@ LU DLOGMOD=D4C32784, X
MODETAB=ISTINCLM,USSTAB=USSTCPIP,SSCPFM=USS3270
Additional Router Configuration for Router Honduras
cmpc C020 F8 CONFIGE READ
cmpc C020 F9 CONFIGE WRITE
!
lan TokenRing 0
adapter 5 4000.eeee.eeee
adapter 6 4000.0000.eeee
tn3270-server
dlur NETA.HOND327S NETA.MVS2
lsap token-adapter 6 54
link MVS2TN rmac 4000.eeee.eeee rsap 50
pu TNPU 017EFEED 172.18.1.218
tg CONFIGE llc token-adapter 6 50 rmac 4000.eeee.eeee rsap 54

On the MVS system, use the following commands to activate the configuration:
v net,act,id=mvstrle,update=add
v net,act,id=mvslne
v net,act,id=swhondpu
v net,act,id=swlagtn
v net,act,id=swhondcp
v net,act,id=tngrp1
On the router Honduras, use the following command from TN3270 configuration mode:
no shutdown


Configuring Cisco Mainframe Channel Connection Adapters

Uploaded by

Copyright:

Available Formats

Configuring Cisco Mainframe Channel Connection Adapters

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuring Cisco Mainframe Channel Connection Adapters

Uploaded by

Copyright:

Available Formats

Configuring Cisco Mainframe

Channel Connection Adapters

Cisco’s Mainframe Channel Connection Adapters

Configuring Cisco Mainframe Channel Connection Adapters BC-459

Figure 171 Cisco Mainframe Channel Connection Adapters

7500 Channel 1/0

IP Parallel channel APPN

BC-460 Bridging and IBM Networking Configuration Guide

Configuring Cisco Mainframe Channel Connection Adapters BC-461

Differences between the CIP and CPA

Table 9 Differences between the CIP and the CPA

Product Differences CIP ECPA PCPA

TCP/IP Environments Using CLAW

BC-462 Bridging and IBM Networking Configuration Guide

TCP/IP Offload Environments

IP Host Backup Environment

TN3270 Server Environments

Configuring Cisco Mainframe Channel Connection Adapters BC-463

Figure 172 TN3270 Implementation

Cisco SNA Environments

BC-464 Bridging and IBM Networking Configuration Guide

• Communication between a channel-attached mainframe running VTAM and a LAN/WAN

Cisco MultiPath Channel Environments

CMCC Adapter Interface Configuration Task List

Configuring Cisco Mainframe Channel Connection Adapters BC-465

• Load the CMCC Adapter Microcode Image

Load the CMCC Adapter Microcode Image

CIP Microcode Image

Step Command Purpose

BC-466 Bridging and IBM Networking Configuration Guide

Step Command Purpose

CPA Microcode Image

Step Command Purpose

Configuring Cisco Mainframe Channel Connection Adapters BC-467

Step Command Purpose

microcode reload {all | {{ ecpa | pcpa} or

Select the Interface

BC-468 Bridging and IBM Networking Configuration Guide

Configure Channel Interface Tracking for HSRP or SNMP Alerts

Configure TCP/IP CLAW or CLAW Packing Support

Configure the IBM Channel Attach Interface

Configuring Cisco Mainframe Channel Connection Adapters BC-469

Select a Data Rate for the Parallel Channel Interfaces

Configure Other Interface Support

Step Command Purpose

Configure TCP/IP Offload Support

• Configure Other Interface Support

Configure the IBM Channel Attach Interface

Select a Data Rate for the Parallel Channel Interfaces

Configuring Cisco Mainframe Channel Connection Adapters BC-471

Configure Other Interface Support

Step Command Purpose

Configure CSNA Support

BC-472 Bridging and IBM Networking Configuration Guide

Select a Data Rate for the Parallel Channel Interfaces

Configure the Subchannel Information

Configure the Internal LAN

Step Command Purpose

Configure the Source Bridge

Configure the LOCADDR Priority