-
Cisco IOS Bridging and IBM Networking Configuration Guide, Release 12.4
-
Overview of SNA Internetworking
- Part 1: Bridging
-
Part 2: IBM Networking
-
Overview of IBM Networking
-
Configuring Remote Source-Route Bridging
-
Configuring Data-Link Switching Plus
- Configuring Serial Tunnel and Block Serial Tunnel
-
Configuring LLC2 and SDLC Parameters
-
Configuring IBM Network Media Translation
-
Configuring SNA Frame Relay Access Support
-
Configuring NCIA Client/Server
-
Configuring the Airline Product Set
-
Configuring DSPU and SNA Service Point Support
-
Configuring SNA Switching Services
- Configuring Cisco Transaction Connection
-
Configuring Cisco Mainframe Channel Connection Adapters
-
Configuring CLAW and TCP/IP Offload Support
-
Configuring CSNA and CMPC
-
Configuring CMPC+
-
Configuring the TN3270 Server
-
-
Table Of Contents
Configuring Cisco Mainframe Channel Connection Adapters
Differences between the CIP and CPA
Preparing to Configure a CMCC Adapter
Mainframe Host Configuration Considerations
Defining the Channel Subsystem for the Router
Correlating Channel Configuration Parameters
Determining the Device Argument
Determining the Device Argument from an IODEVICE Address
Disabling the Missing Interrupt Handler
Disabling the MIH on Mainframes Running MVS
Disabling the MIH on Mainframes Running VM
CMCC Adapter Configuration Task List
Loading the CMCC Adapter Microcode Image
Loading the CIP Microcode Image for All Adapters in the Router
Upgrading the CIP Microcode Image
Upgrading the CPA Microcode Image for All Adapters in the Router
Upgrading the CPA Microcode Image for a Particular Adapter
Verifying the CIP and CPA Microcode Image
Selecting a Data Rate for the Parallel Channel Interfaces
Configuring Channel Interface Tracking for HSRP or SNMP Alerts
Monitoring and Maintaining a CMCC Adapter
Clearing and Resetting an Interface
Clearing Interface Statistics Counters
Clearing Feature-Specific Statistics Counters
Clearing the Hardware Logic on an Interface
Monitoring the Physical Channel Interface on the CPA
Shutting Down and Restarting an Interface
Running CMCC Adapter Interface Loopback Diagnostics
Configuring a CMCC Adapter Core Dump
CPA Microcode Load Configuration Examples
Configuring Cisco Mainframe Channel Connection Adapters
This chapter provides an introduction to the Cisco Mainframe Channel Connection Adapters (CMCCs) and provides information about the basic tasks required to configure any CMCC adapter on a Cisco router. This information is described in the following sections:
•
Overview of the CMCC Adapters
•
•
•
•
Details about configuring the Cisco IOS features that are supported by the CMCCs are described in the related chapters of this publication. For more information about the functions supported on a CMCC, see the "Supported Environments" section.
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 IOS Bridging and IBM Networking Command Reference (Volume 2 of 2). To locate documentation of other commands that appear in this chapter, use the command reference master index or search online.
To identify the hardware platform or software image information associated with a feature, use the Feature Navigator on Cisco.com to search for information about the feature or refer to the software release notes for a specific release. For more information, see the "Identifying Platform Support for Cisco IOS Software Features" section on page li in the "Using Cisco IOS Software" chapter.
Overview of the CMCC Adapters
A CMCC adapter is installed in a Cisco router to provide IBM channel attachment from the router to a mainframe host. The Cisco family of CMCC adapters consists of two basic types of adapters:
•
•
Each type of adapter (CIP or CPA) supports both ESCON and parallel channel attachment to the host and can eliminate the need for a separate front-end processor (FEP).
All CMCC adapters support the full range of channel software applications available in the Cisco IOS software including support for the Common Link Access to Workstation (CLAW) protocol, TCP/IP offload, IP host backup, Cisco SNA (CSNA), Cisco Multipath Channel (CMPC), Cisco Multipath Channel+ (CMPC+), and the TN3270 server.
Figure 1 shows the type of channel connections and environments supported by the CMCC adapters.
Figure 1 Cisco Mainframe Channel Connection Adapters
The following topics in this section provide additional overview information about the CMCC adapters:
•
Channel Interface Processor
The CIP for the Cisco 7000 with RSP7000 and Cisco 7500 series routers is designed for high-end network environments that demand high-performance, high-port density, and high-capacity solutions.
The CIP provides support for IBM ESCON and bus-and-tag parallel channel attachment using the following types of interfaces:
•
•
A single CIP can support up to two physical channel interfaces in any combination of either PCA or ECA. Each CIP is pre-configured with the appropriate channel adapters at manufacturing time.
The Cisco 7000 with RSP7000 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 of the CIP
The CIP provides the following primary benefits:
•
•
•
•
•
Channel Port Adapter
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 that provides support for IBM ESCON and bus-and-tag parallel channel attachment using the following types of interfaces:
•
•
Each CPA provides a single channel interface (with a single I/O connector) for Cisco 7200 series routers. In some situations, this eliminates the need for a separate FEP.
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 and a CPA, and the capacity difference is based on the difference in maximum memory configurations (128 MB for CIP and 32 MB for CPA). For more information about differences between the CIP and CPA, see the "Differences between the CIP and CPA" section.
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.
Note
Benefits of the CPA
The CPA provides the following primary benefits:
•
•
•
ESCON Channel Port Adapter
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.
Parallel Channel Port Adapter
A Parallel Channel Port Adapter (PCPA) provides a single parallel channel physical interface supporting 3.0 or 4.5 Mbps data transfer rates.
Differences between the CIP and CPA
Table 1 illustrates the differences between the CMCC adapters.
Supported Environments
The CMCC adapters provide support for the following environments:
•
For more information about configuring a CMCC adapter for CLAW, see the "Configuring CLAW and TCP/IP Offload Support" chapter in this publication.
•
For more information about configuring a CMCC adapter to support TCP/IP offload, see the "Configuring CLAW and TCP/IP Offload Support" chapter in this publication.
•
For more information about configuring a CMCC adapter for IP host backup support, see the "Configuring CLAW and TCP/IP Offload Support" chapter in this publication.
•
For more information about configuring a CMCC adapter for CSNA, see the "Configuring CSNA and CMPC" chapter in this publication.
•
For more information about configuring a CMCC adapter for CMPC, see the "Configuring CSNA and CMPC" chapter in this publication.
•
For more information about configuring a CMCC adapter for CMPC+, see the "Configuring CMPC+" chapter in this publication.
•
For more information about configuring a CMCC adapter to support the TN3270 server, see the "Configuring the TN3270 Server" chapter in this publication.
Preparing to Configure a CMCC Adapter
This section provides guidelines to consider when preparing to configure a CMCC adapter. It includes limitations on the number of entities that you can configure on a CMCC adapter and provides information about correlating host configuration elements with your router configuration.
These guidelines are provided in the following subsections:
•
•
CMCC Configuration Guidelines
Each CMCC adapter can support the following number of configuration entities:
•
Note
•
•
Note
SAP Configuration Guidelines
Configuring Cisco IOS software application features on a CMCC adapter for communication with the mainframe host requires the configuration of SAPs. SAPs are used by the CMCC adapter to establish communication with the Virtual Telecommunications Access Method (VTAM) on the mainframe and to identify Logical Link Control (LLC) sessions on a CMCC's internal adapter.
To uniquely identify an LLC session, a combination of the following four entities are used in a CMCC adapter. This combination of values is sometimes referred to as the MAC/SAP quadruple:
•
•
•
•
When you are configuring SAPs on a CMCC, it is important to remember how the SAP is used in combination with these other entities to establish a unique LLC session. In order for the LLC session to be unique, there cannot be an LLC session that duplicates all four values of the MAC/SAP quadruple. In fact, only one of the values needs to be unique to qualify the particular session. Understanding this requirement is a key factor in successfully configuring a CMCC adapter to support multiple entities.
To establish the LLC sessions between external network traffic and a feature such as CSNA on a CMCC adapter in the router, an internal LAN along with an internal adapter is defined. MAC addresses are established for the internal adapters that are defined on the internal LAN in the CMCC. An internal LAN can have multiple internal adapters, and therefore, multiple MAC addresses associated with it. When LLC sessions on the CMCC are established using the same internal adapter (and therefore, the same MAC address) and are destined for the same SAP and MAC address, the source SAP must uniquely identify the session.
Consider the following guidelines when configuring SAPs on a CMCC adapter:
•
–
–
–
Note
•
•
•
Reference for IEEE and Manufacturer Administered SAPs
The information in Table 2 and Table 3 is useful as a reference for understanding some of the administered LSAPs that might be encountered on the network external to the router. Remember that these are not values that the CMCC adapter enforces, and they do not specifically pertain to limitations in configuring the CMCCs.
Mainframe Host Configuration Considerations
Configuring a CMCC adapter and its associated features requires that you perform tasks for configuration of the mainframe and the router sides of the network environment.
Often in the mixed network environment of mainframes and LANs, an MVS systems programmer installs and maintains the mainframe side of the network, while a network engineer manages the routers on the LAN side of the network. In such an environment, the successful configuration of the CMCC adapter and its supported features requires the close coordination between these job functions at a customer site.
This section contains information for both the network engineer and the MVS systems programmer to properly configure the channel subsystem for the router and includes the following topics:
•
•
Other chapters in this publication that discuss configuration of supported features on a CMCC adapter provide additional information about host-related and router-related configuration tasks associated with that feature.
Defining the Channel Subsystem for the Router
To establish the path and allocate the range of subchannel addresses that the CMCC adapter can use for communication with the mainframe, you need to specify the channel subsystem definitions in the Input/Output Control Program (IOCP) or Hardware Configuration Definition (HCD) on the host.
The following sample configuration shows the CHPID, CNTLUNIT, and IODEVICE statements that might be defined in an IOCP file for parallel channels and ESCON channels on the CIP or CPA. The parameters in bold indicate values that might vary by the type of channel being defined.
************************************************************************************** Parallel channel--CIP or CPA may be subchannel addresses 580-58F*************************************************************************************CHPID PATH=((21)),TYPE=BLCNTLUNIT CUNUMBER=0580,PATH=(21),UNIT=3088,UNITADD=((80,16)),SHARED=N,PROTOCOL=S4IODEVICE ADDRESS=(580,16),CUNUMBER=(0580),UNIT=CTC************************************************************************************** ESCON channel--CIP or CPA may be subchannel addresses D00-D0F*************************************************************************************CHPID PATH=((1F)),TYPE=CNCCNTLUNIT CUNUMBER=0D00,PATH=(1F),UNIT=3172,UNITADD=((00,16))IODEVICE ADDRESS=(D00,16),CUNUMBER=(0D00),UNIT=SCTC************************************************************************************** ESCON channel with ESCON director--CIP or CPA may be subchannel addresses 700-70F*************************************************************************************CHPID PATH=((1C)),TYPE=CNC,SWITCH=01CNTLUNIT CUNUMBER=0700,PATH=(1C),UNIT=3172,UNITADD=((00,16)),LINK=(C4)IODEVICE ADDRESS=(700,16),CUNUMBER=(0700),UNIT=SCTCThe subchannel parameters differ by the type of channel that you are defining. For example, to support a CMCC parallel channel always use the channel type BL for block multiplexor, data streaming mode. ESCON channels use a channel type of CNC for Native ESCON (or type CVC might be used if an ESCON Converter is in use).
In addition, the UNIT types specified in the CNTLUNIT and IODEVICE statements differ for parallel and ESCON channels. The ESCON director also implements the additional parameters for SWITCH and LINK to identify a number for the ESCON director and specify the port in the ESCON director to which the router is connected.
Note
Correlating Channel Configuration Parameters
This section provides detailed information about correlating values found in the VM and MVS system I/O configuration files with the arguments required in the claw, csna, cmpc, and offload interface configuration commands on the CMCC adapter.
To properly configure the channel subsystem on the router side you need to know the following information:
•
–
–
–
•
This information is defined on the host in the IOCP. In versions of MVS 5.2 and later, an HCD might be used as an alternative method to define this information. To locate this information or to configure it on the mainframe host, contact your site's systems programmer.
Determining the Path Argument
When you define CLAW, CSNA, CMPC or CMPC+, and Offload parameters on a CMCC adapter, 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 using bus and tag cables, or more complex when the path includes an ESCON director switch or multiple image facility (EMIF) support.
This example shows the syntax for the CMCC adapter commands that require subchannel information, which is configured in the path and device arguments of the following commands:
claw path device ip-address host-name device-name host-app device-app [broadcast]csna path device [maxpiu value][time-delay value][length-delay value]cmpc path device tg-name {read | write}offload path device ip-address host-name device-name host-ip-link device-ip-link host-api-link device-api-link [broadcast] [backup]The path argument in each of the commands is a four-digit hexadecimal value that concatenates the path value (2 digits), EMIF partition number (1 digit), and control unit logical address (1 digit) as described in Table 4.
For bus and tag channel connections, the path value is always 0100. You do not need the information in Table 4 to determine the path value.
Consider the network configuration in Figure 2, where 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. Note that the path between Host A and Host B is dynamically switched within the ESCON director. Host C is attached directly to Router B through path 42.
Figure 2 System with an ESCON Director Switch and a Directly Attached Channel
The IOCP control unit statements to configure the channel paths shown in Figure 2 might look similar to the following sample configuration statements:
Sample IOCP Control Unit Statements for Host A
CNTLUNIT CUNUMBER=0001, PATH=(23), LINK=1B, UNITADD=((00,64)), UNIT=SCTC, CUADD=FSample IOCP Control Unit Statements for Host B
CNTLUNIT CUNUMBER=0002, PATH=(29), LINK=1B, UNITADD=((00,64)), UNIT=SCTC, CUADD=ASample IOCP Control Unit Statements for Host C
CNTLUNIT CUNUMBER=000A, PATH=(42), UNIT=SCTC, UNITADD=((00,64))
Note
Using the above IOCP values as an example and following the guidelines provided in Table 4, the following path argument is used as shown in the example csna or cmpc commands for the two channel attachments to Router A:
csna 150Fcsna 190Acmpc 150Fcmpc 190AIn Figure 2 the ESCON director ports 15 and 19 are the channel attachments from the ESCON director to each host. Note that the outbound ports from the ESCON director to the host are the values used in the first 2 digits of the path argument.
The following path argument is used for the directly attached channel to Router B, as shown in the example csna or cmpc commands:
csna 0100cmpc 0100Determining the Device Argument
When you define CLAW, CSNA, CMPC or CMPC+, and Offload parameters on a CMCC adapter, you must supply path information and device address information to support routing on an IBM channel. To determine the value for the device argument in the claw, csna, cmpc, or offload interface configuration commands on the CMCC adapter, find the UNITADD parameter in the host IOCP definition.
The UNITADD parameter in the CNTLUNIT macro of the IOCP file defines the valid range for device addresses. For example, a UNITADD parameter of (00,64) means that the first valid device address is 00 and the number of devices is 64. In the hexadecimal notation used by channel configuration commands this translates to a range of 00 to 3F.
Using that unit address information, the example csna and cmpc commands now add values for the device arguments to the two channel attachments to Router A:
csna 150F 00csna 190A 01cmpc 150F 02cmpc 150F 03cmpc 190A 03cmpc 190A 04The following example csna and cmpc commands show the path and device arguments for the directly attached channel to Router B:
csna 0100 00cmpc 0100 01cmpc 0100 02
Note
Determining the Device Argument from an IODEVICE Address
When you have a directly attached channel, the mainframe systems programmer might provide you with a system IODEVICE ADDRESS that you can use to determine the required subchannel information. In this case, you must work backwards through the IOCP file to locate the proper device argument value for the CMCC adapter interface commands.
Example 1
In this first example, the IODEVICE ADDRESS value is 800. Using this number you can locate the IODEVICE ADDRESS statement in the IOCP file, which points you to the CNTLUNIT statement that contains the device argument values for the claw, csna, cmpc or offload commands:
IODEVICE ADDRESS=(0800,256),CUNUMBR=(0012),UNIT=SCTC**** Address 800 points to CUNUMBR 0012 in the following statementCNTLUNIT CUNUMBR=0012,PATH=(28),UNIT=SCTC,UNITADD=((00,256))**** A valid value for the device argument is the UNITADD value of 00From this example, the csna command would be similar to the following:
csna 0100 00Example 2
In this example the mainframe systems programmer provides an available IODEVICE ADDRESS of 350, which does not directly correspond to a value in the IOCP file, but is within a range of 64 addresses beginning at device address 340 (as shown in the IODEVICE ADDRESS=(340,64) statement). The value 350 is at an offset of 10 from the beginning value of 340 in this statement:
IODEVICE ADDRESS=(0340,64),CUNUMBR=(0008),UNIT=SCTCIODEVICE ADDRESS=(0380,64),CUNUMBR=(0009),UNIT=SCTC**** Address 350 is in the range of 64 addresses beginning at address 340 corresponding **** to CUNUMBER 0008CNTLUNIT CUNUMBR=0008,PATH=(24),UNIT=SCTC,UNITADD=((40,64)),SHARED=N, X**** The device is the UNITADD value of 40, offset by 10, which is 50To determine the unit address for the device argument value in the claw, csna, cmpc or offload commands, you must use the same offset that you determined for the IODEVICE ADDRESS and calculate the UNITADD parameter from the corresponding CNTLUNIT statement. In this example, CUNUMBR=0008 is the corresponding CNTLUNIT statement for IODEVICE ADDRESS 350. The first unit address in that CNTLUNIT statement is 40 (in parameter UNITADD), which correlates to the first IODEVICE ADDRESS of 340. To determine the corresponding unit address for IODEVICE ADDRESS 350, determine the value at offset 10 from 40, which is 50.
In this example, the csna command would be similar to the following:
csna 0100 50
Note
Tip
Disabling the Missing Interrupt Handler
Because the appropriate configuration of the missing interrupt handler (MIH) varies according to the protocols and software releases used, Cisco offers the following guidance:
•
•
This section includes the following topics:
•
•
For additional information about disabling the MIH, 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).
Disabling the MIH on Mainframes Running MVS
To disable the MIH on an MVS host, you need to configure a statement in the IECIOSxx member of the SYS1.PARMLIB partitioned dataset. To properly identify the IECIOSxx member to use, there must be a corresponding statement IOS=xx in the member IEASYS00 (where 00 is the default suffix).
Note
To disable the MIH on an MVS host, perform the following steps:
Step 1
MIH TIME=00:00:00, DEV=(yyy-yyy)This configures the MVS host to disable the MIH every time that MVS is restarted (an Initial Program Load (IPL) is performed).
Step 2
/SETIOS MIH DEV=xxx, TIME=00:00Step 3
/D IOS,MIH
Note
Disabling the MIH on Mainframes Running VM
To disable the MIH on a VM host, you need to configure a statement in the PROFILE EXEC for the AUTOLOG1 userid (or equivalent userid for your site).
To disable the MIH on a VM host, perform the following steps:
Step 1
SET MITIME yyy-yyy 00:00or
SET MITIME yyy-yyy OFFThis configures the VM host to disable the MIH every time that VM is restarted (an Initial Program Load (IPL) is performed).
Step 2
Step 3
Q MITIME
Note
CMCC Adapter Configuration Task List
This section describes some of the global tasks that apply to configuring any CMCC adapter. Information about configuring features on a CMCC adapter are described in the related chapters of this guide.
This section includes the following configuration tasks:
•
•
•
See the "CPA Microcode Load Configuration Examples" section for examples.
Loading the CMCC Adapter Microcode Image
This section provides information on loading, upgrading and verifying the microcode images for the CIP and CPA in the following topics:
•
•
•
•
•
Loading the CIP Microcode Image for All Adapters in the Router
Beginning with Cisco IOS 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-attachment features in Cisco IOS 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 Release 11.1 and later.
Use the commands in this section if you are loading the CIP microcode image for the first time, or for all adapters in your router.
Caution
To prepare the CIP, use the following commands beginning in privileged EXEC command mode:
Upgrading the CIP Microcode Image
Beginning with Cisco IOS 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 RSP card to use the IBM channel-attachment features in Cisco IOS 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 Release 11.1 and later.
Use the commands in this section if you are upgrading the CIP image in your router.
To upgrade the CIP microcode, use the following commands beginning in privileged EXEC command mode:
Upgrading the CPA Microcode Image for All Adapters in the Router
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 image for all adapters in the router.
Caution
To prepare the CPA, use the following commands beginning in privileged EXEC command mode:
Upgrading the CPA Microcode Image for a Particular Adapter
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 image for a particular CPA adapter.
To prepare the CPA, use the following commands beginning in privileged EXEC command mode:
Verifying the CIP and CPA Microcode Image
When a router is starting and the bootflash is loading, the router searches for the default CIP or CPA microcode associated with the current bootflash image. This microcode image might not be the current image that you have loaded. This produces some messages that seem to indicate that the microcode is not loading properly. However, these messages (as shown in the following example for the CIP) are part of the normal loading process:
*Oct 1 13:37:28.078: %SYS-5-RELOAD: Reload requestedSystem Bootstrap, Version 11.1(2) [nitin 2], RELEASE SOFTWARE (fc1)Copyright (c) 1994 by cisco Systems, Inc.SLOT 2 RSP2 is system masterRSP2 processor with 65536 KB of main memoryCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCreading the file into memory...Self decompressing the image : ########################################################################################## ########################################################################################## ################### [OK]%DBUS-3-NOSUPPORT: No driver support in this image for CIP2 in slot 4 (card type
