Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco IOS Software Releases 12.2 Mainline

CIP and CPA Microcode Release Note and Upgrade Instructions

Downloads

Table Of Contents

Channel Interface Processor and Channel Port Adapter Microcode Release Note and Microcode Upgrade Requirements

Contents

Introduction

How to Obtain Microcode

System Requirements

CIP RSP and CPA Cisco 7200 DRAM Requirements

Hardware and Software Compatibility

Cisco IOS Software and Microcode Guidelines

Cisco IOS Software and Microcode Compatibility

Cisco IOS Software and Hardware Compatibility

Processor Module ROM Monitor Compatibility

Upgrading the CIP and CPA Microcode

Microcode Upgrade Configuration Guidelines

Microcode Upgrade Procedure

Microcode Command Examples

PCMCIA Examples

SanDisk Example

Caveats for CIP and CPA Microcode

Microcode Release 28 Caveats

Open Caveats in Version 28.24/Resolved Caveats in Version 28.25

Open Caveats in Version 28.23/Resolved Caveats in Version 28.24

Open Caveats in Version 28.22/Resolved Caveats in Version 28.23

Open Caveats in Version 28.21/Resolved Caveats in Version 28.22

Open Caveats in Version 28.20/Resolved Caveats in Version 28.21

Open Caveats in Version 28.19/Resolved Caveats in Version 28.20

Open Caveats in Version 28.18/Resolved Caveats in Version 28.19

Open Caveats in Version 28.17/Resolved Caveats in Version 28.18

Open Caveats in Version 28.16/Resolved Caveats in Version 28.17

Open Caveats in Version 28.15/Resolved Caveats in Version 28.16

Open Caveats in Version 28.14/Resolved Caveats in Version 28.15

Open Caveats in Version 28.13/Resolved Caveats in Version 28.14

Open Caveats in Version 28.12/Resolved Caveats in Version 28.13

Open Caveats in Version 28.11/Resolved Caveats in Version 28.12

Open Caveats in Version 28.10/Resolved Caveats in Version 28.11

Open Caveats in Version 28.9/Resolved Caveats in Version 28.10

Open Caveats in Version 28.8/Resolved Caveats in Version 28.9

Open Caveats in Version 28.7/Resolved Caveats in Version 28.8

Open Caveats in Version 28.6/Resolved Caveats in Version 28.7

Open Caveats in Version 28.5/Resolved Caveats in Version 28.6

Open Caveats in Version 28.4/Resolved Caveats in Version 28.5

Open Caveats in Version 28.3/Resolved Caveats in Version 28.4

Open Caveats in Version 28.2/Resolved Caveats in Version 28.3

Open Caveats in Version 28.1/Resolved Caveats in Version 28.2

Microcode Release 27 Caveats

Open Caveats in Version 27.35/Resolved Caveats in Version 27.36

Open Caveats in Version 27.34/Resolved Caveats in Version 27.35

Open Caveats in Version 27.33/Resolved Caveats in Version 27.34

Open Caveats in Version 27.29/Resolved Caveats in Version 27.30

Open Caveats in Version 27.28/Resolved Caveats in Version 27.29

Open Caveats in Version 27.27/Resolved Caveats in Version 27.28

Open Caveats in Version 27.26/Resolved Caveats in Version 27.27

Open Caveats in Version 27.25/Resolved Caveats in Version 27.26

Open Caveats in Version 27.24/Resolved Caveats in Version 27.25

Open Caveats in Version 27.23/Resolved Caveats in Version 27.24

Open Caveats in Version 27.22/Resolved Caveats in Version 27.23

Open Caveats in Version 27.21/Resolved Caveats in Version 27.22

Open Caveats in Version 27.20/Resolved Caveats in Version 27.21

Open Caveats in Version 27.19/Resolved Caveats in Version 27.20

Open Caveats in Version 27.18/Resolved Caveats in Version 27.19

Open Caveats in Version 27.17/Resolved Caveats in Version 27.18

Open Caveats in Version 27.16/Resolved Caveats in Version 27.17

Open Caveats in Version 27.15/Resolved Caveats in Version 27.16

Open Caveats in Version 27.13/Resolved Caveats in Version 27.14

Open Caveats in Version 27.12/Resolved Caveats in Version 27.13

Open Caveats in Version 27.11/Resolved Caveats in Version 27.12

Open Caveats in Version 27.10/Resolved Caveats in Version 27.11

Open Caveats in Version 27.9/Resolved Caveats in Version 27.10

Open Caveats in Version 27.8/Resolved Caveats in Version 27.9

Open Caveats in Version 27.7/Resolved Caveats in Version 27.8

Open Caveats in Version 27.6/Resolved Caveats in Version 27.7

Open Caveats in Version 27.5/Resolved Caveats in Version 27.6

Open Caveats in Version 27.4/Resolved Caveats in Version 27.5

Open Caveats in Version 27.3/Resolved Caveats in Version 27.4

Open Caveats in Version 27.2/Resolved Caveats in Version 27.3

Open Caveats in Version 27.1/Resolved Caveats in Version 27.2

Open Caveats in Version 27.0/Resolved Caveats in Version 27.1

Microcode Release 26 Caveats

Open Caveats in Version 26.31/Resolved Caveats in Version 26.32

Open Caveats in Version 26.30/Resolved Caveats in Version 26.31

Open Caveats in Version 26.29/Resolved Caveats in Version 26.30

Open Caveats in Version 26.28/Resolved Caveats in Version 26.29

Open Caveats in Version 26.27/Resolved Caveats in Version 26.28

Open Caveats in Version 26.26/Resolved Caveats in Version 26.27

Open Caveats in Version 26.25/Resolved Caveats in Version 26.26

Open Caveats in Version 26.24/Resolved Caveats in Version 26.25

Open Caveats in Version 26.23/Resolved Caveats in Version 26.24

Open Caveats in Version 26.22/Resolved Caveats in Version 26.23

Open Caveats in Version 26.21/Resolved Caveats in Version 26.22

Open Caveats in Version 26.20/Resolved Caveats in Version 26.21

Open Caveats in Version 26.19/Resolved Caveats in Version 26.20

Open Caveats in Version 26.18/Resolved Caveats in Version 26.19

Open Caveats in Version 26.17/Resolved Caveats in Version 26.18

Open Caveats in Version 26.16/Resolved Caveats in Version 26.17

Open Caveats in Version 26.15/Resolved Caveats in Version 26.16

Open Caveats in Version 26.14/Resolved Caveats in Version 26.15

Open Caveats in Version 26.13/Resolved Caveats in Version 26.14

Open Caveats in Version 26.12/Resolved Caveats in Version 26.13

Open Caveats in Version 26.11/Resolved Caveats in Version 26.12

Open Caveats in Version 26.10/Resolved Caveats in Version 26.11

Open Caveats in Version 26.9/Resolved Caveats in Version 26.10

Open Caveats in Version 26.8/Resolved Caveats in Version 26.9

Open Caveats in Version 26.7/Resolved Caveats in Version 26.8

Open Caveats in Version 26.5/Resolved Caveats in Version 26.7

Open Caveats in Version 26.4/Resolved Caveats in Version 26.5

Open Caveats in Version 26.2/Resolved Caveats in Version 26.4

Open Caveats in Version 26.1/Resolved Caveats in Version 26.2

Open Caveats in Version 26.0/Resolved Caveats in Version 26.1

Related Documentation

Hardware Documentation

Cisco 7000 Series Hardware Documentation

Cisco 7200 Series Hardware Documentation

Cisco 7500 Series Hardware Documentation

Release-Specific Documentation

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Product Alerts and Field Notices

Obtaining Technical Assistance

Cisco Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Channel Interface Processor and Channel Port Adapter Microcode Release Note and Microcode Upgrade Requirements

Dec. 28, 2006

Text Part Number OL-1951-26

Contents

This document provides cumulative information for the Channel Interface Processor (CIP) and Channel Port Adapter (CPA) unbundled microcode software releases. Much of the same microcode information and procedures apply to both the CIP and CPA hardware, including the caveats in this document. Where differences do occur, they are noted and identified as applicable to either the CIP or CPA.

This release note includes the following topics:

•Introduction

•How to Obtain Microcode

•System Requirements

•Upgrading the CIP and CPA Microcode

•Caveats for CIP and CPA Microcode

•Related Documentation

•Obtaining Documentation

•Documentation Feedback

•Cisco Product Security Overview

•Product Alerts and Field Notices

•Obtaining Technical Assistance

•Obtaining Additional Publications and Information

Introduction

This section provides some background information on the CIP and CPA microcode and upgrade guidelines.

The CPA includes the Enterprise Systems Connection (ESCON) CPA and the Parallel CPA. The ESCON CPA (ECPA) and Parallel CPA (PCPA) are additions to the Cisco Mainframe Channel Connection (CMCC) family of adapters, which also includes the Channel Interface Processor (CIP) and CIP2. The CPA microcode runs on both the ECPA and the PCPA. Cisco IOS Release 11.3(3)T and later supports the ECPA. Cisco IOS Release 11.3(7)T and later and Cisco IOS Release 12.0(1) and later support the PCPA. Cisco IOS Release 12.1(5)T and later supports the ECPA4.

Note Throughout the remainder of this document, CPA is used to refer to both the ECPA and PCPA. The ECPA and PCPA are no longer produced.

Any given Cisco IOS software release attempts to load a default level of the microcode software for the CIP and CPA. Prior to Cisco IOS Release 11.1 for the CIP, the microcode software was only available within the Cisco IOS software bundle.

In Cisco IOS Release 11.1 and later, the microcode became available unbundled from the Cisco IOS software. Therefore, you must obtain the microcode as a separately loadable software module.

There is a default setting in the Cisco IOS software that corresponds to a particular level of microcode that is already loaded on the router Flash memory card (or on the SanDisk memory device for the CPA) when you purchase a CIP or CPA with a system. But, if you order a CIP or CPA as a spare (shipped separately from a system), you might be required to download the microcode image from Cisco.com.

If you need to load a version of the microcode independently, you should be sure you are running a compatible version of the Cisco IOS software. For information about microcode and Cisco IOS software compatibility, see the "Hardware and Software Compatibility" section.

Caution If you are upgrading from a release prior to Cisco IOS Release 11.1, a special microcode installation procedure is required or your CIP will not operate properly. For details, refer to the section "Upgrading the CIP and CPA Microcode" section.

How to Obtain Microcode

When the CIP or CPA hardware is shipped as part of a system order, you will receive a copy of the Cisco IOS software image and the microcode software preinstalled on a Flash disk or Sandisk device.

When your order the CIP or CPA hardware as a spare that is not part of a system order, or if you want to upgrade your microcode, then you need to obtain the microcode from Cisco.com.

You can obtain the microcode images using electronic download from the Software Center on Cisco.com at: http://www.cisco.com/kobayashi/sw-center/interworks/cip/

System Requirements

This section provides important information about hardware and software requirements.

CIP RSP and CPA Cisco 7200 DRAM Requirements

For the Cisco Systems routers to take advantage of the CIP and CPA features in the Cisco IOS software, you might need to upgrade code, main system, or CIP/CPA memory. For specific Cisco IOS-related memory requirements, refer to the Cisco IOS software release note publications corresponding to your Cisco IOS software release. For a list of the related Cisco IOS software publications, refer to the "Release-Specific Documentation" section.

Hardware and Software Compatibility

This section provides Cisco IOS software, microcode, and ROM monitor software compatibility information for your CIP and CPA hardware and processor modules. It includes the following topics:

•Cisco IOS Software and Microcode Guidelines

•Cisco IOS Software and Microcode Compatibility

•Cisco IOS Software and Hardware Compatibility

•Processor Module ROM Monitor Compatibility

Cisco IOS Software and Microcode Guidelines

When identifying an appropriate microcode version and compatible Cisco IOS software release, you should consider the following important guidelines:

•Any given Cisco IOS software release is associated with a default microcode version. A list of the current Cisco IOS software releases and the default microcode versions associated with them are provided in Table 2. The router automatically attempts to load the default microcode version from slot 0.

•You are not required to load the default microcode version associated with a Cisco IOS software release. However, if the default microcode version is not located in slot 0, you will receive the "Failed to load cip microcode" error message. For more information, see the "Upgrading the CIP and CPA Microcode" section.

•Any given Cisco IOS software release is compatible with the microcode version that it loads by default, and any higher versions of that microcode release. Therefore, we recommend that you load the latest microcode version available within the microcode release that your Cisco IOS software supports. To determine the microcode release level required by a given Cisco IOS software release, see Table 1.

•If you need to upgrade to a new microcode release level (for example, you need to move from release 27 to release 28 of the microcode), then you should install the latest version of release 28 microcode and also the latest available Cisco IOS release associated with microcode release 28. See Table 1.

•The CIP and CPA hardware also require certain minimum Cisco IOS software releases. To verify these minimum requirements, see Table 3 and Table 4.

Note The End of Engineering (EOE) and End of Sales (EOS) dates for CIP and CPA microcode releases are now associated with the EOE and EOS dates for their associated Cisco IOS software releases. For example, when the EOE for Cisco IOS Release 12.0 is announced, the EOE for microcode release 26 will also occur. The product bulletin providing information about Cisco IOS software release dates and milestones is available at http://www.cisco.com/warp/customer/cc/pd/iosw/iore/prodlit/367_pb.htm. (To access this bulletin, you must have a valid Cisco.com account and be logged in.)

Cisco IOS Software and Microcode Compatibility

This section provides information about compatibility between microcode versions and Cisco IOS software releases for the Cisco 7000 series, Cisco 7200 series, and Cisco 7500 series routers. The CIP and CPA microcode images are shipped in a bundle separate from the Cisco IOS software images.

Required Microcode Releases for Cisco IOS Software

Table 1 provides a list of the microcode releases that are required for each of the currently available Cisco IOS software releases. For example, if you are running any version of the Cisco IOS Release 12.0 mainline software, then you must run release 26 of the CIP/CPA microcode. If you are running any release of Cisco IOS Release 12.0 T or Cisco IOS Release 12.1 T prior to Cisco IOS Release 12.1(5)T, then you must run release 27 of the microcode. Cisco IOS Release 12.1(5)T and later supports microcode release 28.

Table 1 Cisco IOS Software and CIP/CPA Microcode Release Requirements 

Cisco IOS Release
Required Microcode Release

12.3 T

28-xx

12.3

28-xx

12.2S

28-xx

12.2 T

28-xx

12.2

28-xx

12.1(5)T1

28-xx

12.1 T

27-xx

12.1

27-xx

12.1E

27-xx

12.0 T

27-xx

12.0

26-xx

12.4

28-xx

12.4T

28-xx

1 New commands and features were introduced for the CIP and CPA in Cisco IOS Release 12.1(5)T and release 28 of the microcode. Therefore, release 27 of the microcode is required for any Cisco IOS 12.1 T releases prior to Cisco IOS Release 12.1(5)T, and release 28 is required at Cisco IOS Release 12.1(5)T and later.


Note If you plan to upgrade to a new microcode release level (such as from 27 to 28), then we recommend that you obtain both the latest microcode release level and the latest Cisco IOS release available for that microcode. For example, if you are running Cisco IOS Release 12.1 supporting microcode release 27 level, and you plan to upgrade to microcode release 28 level, then you should also install Cisco IOS Release 12.2(16), or the latest Cisco IOS 12.2 release or Cisco IOS 12.2 T release available at the time that you upgrade. Otherwise, you might not receive the full feature and command support for that microcode release.

Default Microcode Versions Loaded by the Cisco IOS Software

Every Cisco IOS software release is associated with a default microcode version. Table 2 provides a list of each of the available microcode versions (organized by release level) and the corresponding Cisco IOS software releases that load that microcode version by default. Recall that you are not required to load the default microcode version associated with a Cisco IOS software release. For more information about microcode and Cisco IOS software guidelines, see the "Cisco IOS Software and Microcode Guidelines" section.

Note It is important to recognize that the router attempts to load the default microcode version from slot 0. If the default microcode version is not located in slot 0, you will receive the "Failed to load cip microcode" error message. Therefore, if you are loading a different microcode version or you are loading the microcode from a location other than slot 0, be sure that you configure the appropriate microcode command and specify the corresponding microcode filename and location. For more information, see the "Upgrading the CIP and CPA Microcode" section.

Note The XCPA microcode became available in Release 26.

Table 2 Default Microcode Versions for Cisco IOS Software Releases 

Default Microcode Version (CIP/ XCPA)
Loaded automatically from slot 0 by the following Cisco IOS software releases:

Microcode Release 28:

 

28-18

12.2(27), 12.3(12), 12.4(1), 12.2(27)S

28-14

12.2(21), 12.2(23), 12.2(20)S

28-12

12.2(16), 12.2(17)S

28-11

12.2(12), 12.2(13), 12.2(12)S

28-10

12.2(10), 12.2(11)S

28-9

12.2(7)

28-8

12.2(5), 12.2(6)S

28-6

12.2(3). 12.2(2)S

28-5

12.2(1), 12.2(2)T, 12.2(1)S

Microcode Release 27:

 

27-26

12.1(22), 12.1(22)E

27-23

12.1(18), 12.1(19), 12.1(20), 12.1(21), 12.1(19)E

27-22

12.1(16), 12.1(17)

27-21

12.1(14)

27-20

12.1(12), 12.1(12)E

27-19

12.1(11), 12.1(11)E

27-18

12.1(10)

27-17

12.1(9)

27-16

12.1(8)

27-13

12.1(7)

27-11

12.1(6)

27-9

12.1(4), 12.1(4)T

27-8

12.1(3), 12.1(3)T

27-7

12.1(2), 12.1(2)T

27-6

12.1(1), 12.1(1)T

27-5

12.1(1), 12.1(1)T

27-4

12.0(7)T, 12.0(8), 12.0(8)T, 12.0(9), 12.0(9)T

27-3

12.0(7)

27-2

12.0(5)T, 12.0(6)

27-1

12.0(4)T, 12.0(5), 12.0(6)

27-0

12.0(3)T, 12.0 (4), 12.0(5)

Microcode Release 26:

 

26-31

12.0(28)

26-29

12.0(26). 12.0(27)

26-28

12.0(25)

26-27

12.0(23), 12.0(24)

26-26

12.0(22)

26-25

12.0(20)

26-24

12.0(19)

26-23

12.0(18)

26-21

12.0(17)

26-20

12.0(16)

26-19

12.0(16)

26-18

12.0(15)

26-17

12.0(14)

26-16

12.0(13)

26-15

12.0(12)

26-13

12.0(11)

26-12

12.0(10)

26-11

12.0(9)

26-10

12.0(8)

26-9

12.0(6), 12.0(7)

26-8

11.3(10)T, 11.3(11)T, 12.0(5)

26-7

11.3(9)T, 12.0(4)

26-5

11.3(8)T, 12.0(3)

26-4

11.3(7)T, 12.0(1), 12.0(2), 12.0(1)T, 12.0(2)T


Cisco IOS Software and Hardware Compatibility

Table 3 lists the minimum Cisco IOS software releases and the corresponding default microcode versions that are available for CIP Version 5 hardware.

Table 3 Minimum Cisco IOS Software Releases for CIP Hardware Version 5 

CIP Hardware Version
Minimum Cisco IOS Release
Default Microcode Version

CIP2 Version 5.x

12.3(1)T

cip28-2

 

12.3(1)

cip28-2

 

12.2(1)T

cip28-2

 

12.2(1)

cip28-2

 

12.1(1)T

cip27-5

 

12.1(1)

cip27-5

 

12.0(1)T

cip26-4

 

12.0(1)

cip26-4


Table 4 lists the minimum Cisco IOS software releases and the corresponding default microcode versions that are available for the different CPA hardware versions.

Note The ECPA and PCPA are at End of Sale (EOS).

Table 4 Minimum Cisco IOS Software Releases by CPA Hardware Version 

CPA Hardware Version
Minimum Cisco IOS Release
Default CPA Microcode Version

ECPA4

12.3(1)T

xcpa28-2

 

12.3(1)

xcpa28-2

 

12.2(1)T

xcpa28-2

 

12.2(1)

xcpa28-2

 

12.1(5)T

xcpa28-2

     

PCPA

12.1(1)T

xcpa27-5

 

12.1(1)

xcpa27-5

 

12.0(1)T

xcpa26-4

 

12.0(1)

xcpa26-4

     

ECPA

12.2(1)T

xcpa28-2

 

12.2(1)

xcpa28-2

 

12.1(1)T

xcpa27-5

 

12.1(1)

xcpa27-5

 

12.0(1)T

xcpa26-1

 

12.0(1)

xcpa26-1


Processor Module ROM Monitor Compatibility

The ROM monitor (system bootstrap) versions for the CIP platform processor modules (RSP), as well as the ROM monitor versions for the Cisco 7200 series platform for the CPA, are typically independent of the Cisco IOS system software images. However, the CIP and CPA hardware do have minimum recommended microcode versions for each Cisco IOS software release. For more information, see the "Cisco IOS Software and Hardware Compatibility" section.

Table 5 provides the minimum CIP boot ROM and ROM monitor versions supported by router platform and processor type.

Table 5 Minimum Recommended CIP Boot ROM and ROM Monitor Versions

Platform and Processor
Processor ROM Monitor Version

Cisco 7000 series Route Switch Processor (RSP)

System Bootstrap Version 11.0 or later

Cisco 7500 series router with RSP1, RSP2, RSP4/4+, RSP8, and RSP16

System Bootstrap Version 11.0 or later


Table 6 provides the minimum processor ROM monitor versions supported by the CPA.

Table 6 Minimum Recommended ROM Monitor Versions for the CPA

Platform and Processor
Processor ROM Monitor Version

Cisco 7200 router

System Bootstrap Version 11.1 CA or later


Upgrading the CIP and CPA Microcode

Before you begin, read the "Cisco IOS Software and Microcode Guidelines" section to be sure that you are installing a compatible Cisco IOS software and microcode version.

Note It is important to recognize that the router attempts to load the default microcode version from slot 0. If the default microcode version is not located in slot 0, you will receive the "Failed to load cip microcode" error message. For a list of the default microcode versions automatically loaded by the Cisco IOS software, see Table 2. When you are loading a different microcode version than the default, or you are loading the microcode from a location other than slot 0, be sure that you configure the appropriate microcode command and specify the corresponding microcode filename and location. Read the guidelines and procedures in this section for more information.

This section includes the following topics:

•Microcode Upgrade Configuration Guidelines

•Microcode Upgrade Procedure

•Microcode Command Examples

Microcode Upgrade Configuration Guidelines

Consider the following guidelines as you configure your router to load CIP/CPA microcode:

•Be sure to download the microcode image in binary format. Verify that the file size on the FTP download site matches the file size that you have downloaded.

•In some Cisco IOS releases, the CPAs in Cisco 7200 series routers using SanDisk storage media fail to load default microcode from the SanDisk. If you are using a SanDisk on the CPA, then the Cisco IOS software image must support the SanDisk. For more information, refer to the field notice at http://www.cisco.com/en/US/partner/products/hw/modules/ps2033/products_field_notice09186a00800a6908.shtml.

•If you are using a microcode image other than the default for your Cisco IOS software image, or you are copying the image to a location other than slot 0, use one of the following microcode commands:

–For the CIP—microcode cip flash slotx:cipnn-nn, where x is the slot number, and nn-nn is the microcode release that you plan to load.

–For the CPA—microcode ecpa {sloty:xcpann-nn | disky:xcpann-nn}, where y is the slot or disk number, and nn-nn is the microcode release that you plan to load. Use the disky: argument when you are loading from a SanDisk.

•When you configure the microcode command, the command line interface (CLI) parser automatically adds the microcode reload command.

Microcode Upgrade Procedure

To upgrade CIP/CPA microcode from an image obtained on Cisco.com, complete the following steps:

Step 1 Download the microcode image from Cisco.com to a TFTP server.

Step 2 Copy the microcode image to the Flash memory card in slot 0 or slot 1, or to the SanDisk memory device in disk 0 or disk 1.

Step 3 Save your running configuration to a TFTP server, Flash memory, or SanDisk memory device.

Step 4 Configure the microcode global configuration command.

The microcode command should point to the microcode image that you stored in the Flash memory card in slot 0 or slot 1, or in the SanDisk memory device in disk 0 or disk 1.

Step 5 Load the new microcode by completing one of the following steps:

•To reload only the updated microcode, use the microcode reload global configuration command.

•To reload the microcode from a specific slot on a Cisco 7200 series router, use the microcode reload privileged EXEC configuration command.

•To reload the updated microcode and the entire router configuration, use the reload privileged EXEC command.

For more detailed information on the procedures to upgrade the CIP microcode, refer to the companion publication Upgrading Software and Microcode in Cisco 7000 Family Routers (document number 78-1144-xx). The Upgrading Software and Microcode in Cisco 7000 Family Routers publication includes information on upgrading software and microcode images, transferring files to and from TFTP servers, copying files between NVRAM and Flash memory, and between TFTP servers and Flash memory. The publication also includes basic instructions for booting your system.

For more detailed information on upgrading the CPA microcode image, refer to the following publications:

•PA-1C-E ESCON Channel Port Adapter Installation and Configuration

•PA-4C-E 1-Port High Performance ESCON Channel Port Adapter Installation and Configuration

•PA-1C-P Parallel Channel Port Adapter Installation and Configuration

Microcode Command Examples

This section provides a few examples of the microcode command when loading CIP or CPA microcode from different memory devices.

PCMCIA Examples

The following example specifies loading the cip28-12 microcode release from Flash slot0 for the CIP: 

Router(config)# microcode cip flash slot0:cip28-12

The following example specifies loading the xcpa28-12 microcode release from Flash slot0 for the CPA: 

Router(config)# microcode ecpa slot0:xcpa28-12

SanDisk Example

The following example specifies loading the xcpa28-12 microcode release from disk1 on a SanDisk for the CPA: 

Router(config)# microcode ecpa disk1:xcpa28-12

Caveats for CIP and CPA Microcode

Caveats describe unexpected behavior in the CIP and CPA microcode. This section provides a list of the most serious open caveats for the previous release, and resolved caveats in the current release of CIP and CPA microcode.

This section includes caveats for the following releases:

•Microcode Release 28 Caveats

•Microcode Release 27 Caveats

•Microcode Release 26 Caveats

Note The XCPA microcode became available in Release 26.

Microcode Release 28 Caveats

This section describes the open and resolved caveats for microcode release cip28 and xcpa28. The caveats listed apply to only the most serious problems.

Open Caveats in Version 28.24/Resolved Caveats in Version 28.25

This section describes possible unexpected behavior in Version 28.24. All the caveats listed in this section are resolved in Version 28.25.

•Clients connecting via TN3270 SSL are randomly disconnected by the CIP Router. The issue was seen only with TN3270 SSL configured.

The workaround is to move TN Clients to NON-SSL. [CSCse44399]

•The TN3270 server lu-seeds whose first character is numeric are rejected because they are not valid SNA names.

The workaround, to allow the initial numeric, is to configure:

tn-parameter code 21 [CSCsg03731]

•Cisco CMCC configured for CMPC LLC might fail due to a buffer shortage. The local major node for one side of the connection is inactive while the other side is attempting to connect.

The workaround is to configure the link to use the CSNA feature rather than CMPC. [CSCse91888]

•A VTAM USSMSG that is too large to fit on a 24x80 screen might cause the CMCC tn3270 server to fail. A VTAM USSTAB entry used by the TN3270 Clients was configured incorrectly as explained in IBM APAR II12568.

The workaround is to modify the USSTAB so that it fits on a 24x80 screen. Correct the misconfigured VTAM USSTAB entry per IBM recommendations in APAR II12568. [CSCsf26598]

•A Cisco CMCC running CMPC+ might reload unexpectedly if the mainframe forwards a malformed IP packet. The failure occurred while testing security issues on the MVS system. The open source suite ISIC was being used to flood the VIPA address with malformed TCP packets.

The workaround is to apply the fix for IBM APAR PK26843 to the mainframe TCP/IP stack. [CSCsg89060]

•A Cisco CMCC tn3270 server with SSL clients might reload unexpectedly. The ECPA4 was configured for TN3270 SSL and was being R-MAC'd into SNASwitch. It is not known at this time if any of these conditions had an effect or was the cause of the crash.

There is no workaround. [CSCsh19847]

Open Caveats in Version 28.23/Resolved Caveats in Version 28.24

This section describes possible unexpected behavior in Version 28.23. All the caveats listed in this section are resolved in Version 28.24.

•The CIP console commands tn3270 resources, tn3270 scan, and tn3270 stats may produce incorrect output if multiple commands are issued very quickly, for example, by pasting in multiple commands.

The workaround is to allow the previous command to complete displaying its output before entering a new command. [CSCsc79152]

•Version 28-24 is required to be able to use the ECPA4 with the NPE-G2. If an older release is used, the symptom is that all IP packets to the CMCC IP stack are dropped due to an invalid checksum.

There is no workaround. [CSCsd58468]

•CIP/xCPA CLAW packing trace entries do not show sufficient information to diagnose activation problems. This occurs under all conditions.

There is no workaround. [CSCsd96288]

•CIP/xCPA CLAW packed activation fails under unknown conditions.

There is no workaround. [CSCsd96278]

Open Caveats in Version 28.22/Resolved Caveats in Version 28.23

This section describes possible unexpected behavior in Version 28.22. All the caveats listed in this section are resolved in Version 28.23.

•Cisco posted Security Response on this issue. It is available at http://www.cisco.com/warp/public/707/cisco-response-20051202-openssl.shtml This is in response to the OpenSSL Advisory released on 2005-Oct-11. The advisory is posted at http://www.openssl.org/news/secadv_20051011.txt Some of the Cisco Systems product lines are affected by this vulnerability.

CIP/CPA software releases up to version 28-22 are affected. The first fixed software release will be 28-23. It is scheduled for release in December 2005. [CSCej54402]

Open Caveats in Version 28.21/Resolved Caveats in Version 28.22

This section describes possible unexpected behavior in Version 28.21. All the caveats listed in this section are resolved in Version 28.22.

•Customers are unable to access target applications via CIP Tn3270. Tn3270 Capture Trace indicates that NO PUs are available for usage, as shown here: 

Aug 3 11:40:44.371 EDT: %CIP2: slot0 [bad telnet 
connect]13[ipAddrClient]10.128.69.147:[tcpPortCl Aug 3 11:40:44.371 EDT: %CIP2: slot0 
----ient]0x891:[connectReasonCode]0x8:[tn3270eDeviceType]IBM Aug 3 11:40:44.371 EDT: 
%CIP2: slot0 -----3279-2-E:[tn3270eDeviceName]:[tn3270eSubErr]no pu:

This issue is seen when the CIP Card is low in memory. The following is output from the
show controller cbus command, 

Load metrics: Memory dram 1794472/32M ...

The workaround is to ensure that memory installed in CIP card can handle the current workload. A microcode reload or an OIR on the affected CIP card that is running low in memory can be used to recover the memory in the affected CIP card. [CSCsb70794]

•TN3270 clients cannot connect to CIP/ECPA TN3270-server listen-point after a change is made to the number of the clusters in a pool under a PU. This occurs when the change is made when the number of clusters allocated to the pool in the PU is at the limit on LUs. Specifically, if the pool as at the limit and the following is issued: 

no allocate lu 1 pool TEST clusters 5

allocate lu 1 pool TEST clusters 5


Then clients may fail to connect. This affects both LUs in the TEST pool as well as the LUs remaining 
in the generic pool (unassigned LUs).

The workaround is to reactivate the affected PUs. This can be accomplished either by a VTAM VARY INACT/ACT or by a shutdown | no shutdown of the PUs. [CSCei70033]

Open Caveats in Version 28.20/Resolved Caveats in Version 28.21

This section describes possible unexpected behavior in Version 28.20. All the caveats listed in this section are resolved in Version 28.21.

•Under very heavy load, a Cisco Channel Interface Processor, CIP2, or Channel Port Adapter, ECPA or ECPA4, might unexpected disconnect an LLC2 session.

The problem only occurs when LLC2 dynamic windowing, llc2 nw N, is configured and an LLC2 REJ frame is received.

The workaround is to remove the llc2 nw N command. [CSCeh50081]

•The CIP/xCPA llc badns command is erroneously reporting LLC sessions that did not experience the badns condition. This causes one to believe that an LLC session had a problem when it did not.

If an llc session experiences the badns condition, subsequently disconnects, and the control block representing that session is reused, the new LLC session shows as having experienced a badns condition in the output of the CIP/xCPA llc badns command.

There is no workaround. [CSCeh51794]

•CIP/CPA LLC sessions disconnect with FRMR. This occurs when a customer runs a very heavy traffic load on the CIP/CPA and retransmissions occur.

There is no workaround. [CSCeh75068]

Open Caveats in Version 28.19/Resolved Caveats in Version 28.20

This section describes possible unexpected behavior in Version 28.19. All the caveats listed in this section are resolved in Version 28.20.

•The Channel Interface Processor (CIP) running microcode cip27-29 crashes with Fatal Error (code=35) if the following command is entered without specifying a logical unit name: 

Router# % tn3270 stats lu

The workaround is to specify a logical unit name as a parameter on the command. [CSCeg31452]

•When shutting down the TN3270 server, a fatal error 35 may be experienced. This occurs after failure of a DLUR link.

There is no workaround. [CSCdz27554]

•SNA PUs cannot connect to VTAM through an CSNA/XCA connection. The CIP/CPA displays the following message: 

%MSG802-6-LLC_DUP_CCB: LLC Station : RMAC=4000.7507.0002 LMAC=4000.7507.0001 LSAP=04 
RSAP=0C

It might not be possible to reactivate a PU after it has been inactivated on the mainframe.

This problem occurs after a PU 2.1. That is, a PU that uses XID format 3 attempts to connect to VTAM and VTAM rejects the connection. This could be a transient condition, if, for example, the PU's Switched Major Node (SWN) was not active yet. When VTAM rejects the connection, it sends back an XID containing a Control Vector 22 (XID Negotiation Error) containing a sense code. The CIP or CPA mis-handles the XID containing the CV22, and places the PU's MAC/SAP four-tuple into an invalid state. When subsequent connection attempts are made, the CIP/CPA finds the MAC/SAP four-tuple already in use and displays the %MSG802-6-LLC_DUP_CCB message. This prevents the PU from connecting.

The workaround is to take the following action:

1. Re-configure the PU to point to a different MAC or different CIP/CPA router.

2. Reload the microcode.

3. Reload the router. [CSCeg46357]

•The following message may be seen from a CMCC adapter: 

%ECPA4-6-MSG: slot2 %MSG802-6-LLC_DUP_CCB: LLC Station : RMAC=4043.3333.9000 
LMAC=4041.2222.001F LSAP=08 RSAP=88

This message occurs when very many tn3270 PUs are configured.

There is no workaround. [CSCeg74214]

•When the CMPC+ connection is activated, the following message may be seen: 

%CIP2-3-MSG: slot1 %MPC-3-CMPCP_CV_ERR1: Unrecognized/Unexpected CV: 040C

The problem was reported after the mainframe operating system was upgraded to z/OS R1.5. The control vector 040C contains a list of supported functions and was added for IPV6 support on the mainframe. The CV is ignored on the CIP.

There is no workaround. [CSCeg84750]

Open Caveats in Version 28.18/Resolved Caveats in Version 28.19

This section describes possible unexpected behavior in Version 28.18. All the caveats listed in this section are resolved in Version 28.19.

•When many LUs are nailed to the same IP address, the client can see a long delay in getting a connection. This only happens when there are a large number of LUs nailed.

There is no workaround. [CSCef54044]

•Unable to issue the command hsma xca-query-interval XXX (where XXX is the desired query interval between 1-300 from the CIP console) to change the XCA query interval from the default of 30 seconds. The above command is rejected as being not valid.

The workaround is to use hsma xca-queryinterval XXX. After this change, hsma xca-query-interval XXX is correct . [CSCef73273]

•The initial implementation of the Hot Standby MAC Address (HSMA) in the CIP/ECPA4 did not include any exec mode show type commands. These are needed to determine the current state of the HSMA connection and which CIP/ECPA4 has the active MAC address.

There is no workaround. [CSCec87859]

•Below CMCC messages might be observed when TN3270 services stopped and started. The messages are : CMCC-4-CFGFAIL and CMCC-3-CFGCMDDROPPED: Config queue is full, command was dropped.

The problem happens if there are about 1800 Tn3270 Dlur PUs configured under virtual channel interface.

The workaround is to reduce the size of the Tn3270 PU configuration. Distribute Tn3270 PU configs to different CIP routers. [CSCee89157]The following messages are observed on a CIP/xCPA when attempting to configure a new TN3270-server PU: 

ECPA41-InsertPuIntoResourceTree: avl_insert failed for O41C0001. 

%CMCC-4-CFGFAIL: Interface Channel1/0: configuration command TN3270S_PU_NEW cmd 16 
failed

They can occur when adding PUs with the following characteristics: - The first 6 characters are the same as other PUs already defined - The PUs are not specifying the luseed parameter - PUs have statically defined LU names matching the 1st 6 characters of previously defined PUs.

The workaround is to ensure that all PU names are unique in the first 6 characters, or ensure that a unique lu-seed parameter is used on all PU definitions. [CSCef70598]

•The following message may be displayed on a client screen: 

THIS TERMINAL HAS REQUESTED A RESOURCE NOT KNOWN ON THE TN3270 SERVER. THEREFORE, IT 
IS BEING PLACED INTO A HOLD STATE. PLEASE CONTACT YOUR HELP DESK FOR RESOLUTION OF 
THIS PROBLEM.

Printers may print garbage characters. This will occur when a client IP has had 10 consecutive connect failures. This "feature" was added to prevent the CIP from wasting resources on answering a TN3270 client which was asking for an unavailable VTAM resource. There have been problems with this operation with printer servers where multiple printers may appear as the same client IP address. A customer requests a way to disable this feature.

There is no workaround. [CSCdr32459

•This changes adds a "dumpopts context" command to the CMCC console. It requests that the contents of storage around the registers be displayed if the CMCC ucode fails. It should be used at the request of technical support personnel. [CSCee40406]

•The Cisco CSNA virtual token-ring adapters respond to an LLC TEST frame with a DISC frame if the SAP is not open. The correct behaviour is to ignore the TEST.

There is no workaround. [CSCef66551]

•The CIP2 Fatal Error logout is sometimes truncated. It ends after the display of "lowcore".

[CSCee42880]

•A 7200 router with a PA-4C-E XCPA Port Adapter may incur a Fatal Error 35 Error code causing the XCPA adapter to reload. The IOS being run at the time was 12.2(10b) with XCPA microcode level 28-11.

There is no workaround. [CSCef05612]

•Channel interface processor got Fatal error 37 after the channel interface shut down to recover OSPF routes. CONFIG-3-WORKLEFT: Work pending on work queue when device terminated

There is no workaround. [CSCef28648]

•The CIP/xCPA running microcode cip27-29 will crash with Fatal Error (code=35) if the following command is entered without specifying a logical unit name:
% tn3270 stats lu
The failure only occurs if a logical unit name is not entered.

The workaround is to specify a logical unit name as a parameter on the command. [CSCeg31452]

Open Caveats in Version 28.17/Resolved Caveats in Version 28.18

This section describes possible unexpected behavior in Version 28.17. All the caveats listed in this section are resolved in Version 28.18.

•CIP core dump utility does not always work. When the CIP crashes, no useful content of the CIP memory can be dumped, so it is impossible to determine the root cause of the crash.

There is no workaround. [CSCee17767]

•The TN3270-server allows a client to acquire LUs outside of the range specified in the client nailing statement. The problem only occurs if the client specifies a specific LU name that is outside of the valid nailed range. If the client specifies "generic", then connection is not allowed to LUs outside the nailed range. Problem was caused as a result of the resolution for ea70079, and therefore only occurs in CIP/CPA releases 28-15, 28-16 and 28-17.

There is no workaround. [CSCee18021]

•Issuing HSMA DISPLAY from the cip console shows under HSMA Configured Peers Local state: Standby. This indicates the adapter should be in a "disabled" state until an event occurs to place it in an "Active" state. In this "disabled" state the adapter should not respond or transmit any MAC frame with the HSMA MAC adapter address. When using HSMA in a PU4/5 to PU4/5 network design the Standby adapter sends a TEST frame to the target device, accepts the positive response, then sends an XID. If communications was already established with the Active adapter a DISC will occur resulting in the tear down of the original established circuit. This behavior can be verified by going into the CIP Console. Verify that the adapter is in Standby by issuing the HSMA DISPLAY command. Then performing a CIP LLC TRACE (procedures can be found on CCO). This will show the two HSMA adapters communicating between themselves over an LLC session using SAP EC. When Standby Adapter's XCA is activated you'll see the LLC TEST being source by the Standby adapter MAC address.

There is no workaround. [CSCee79867]

•A fatal error 35 may occur when a PU with LU pools already present. This problem will occur if any of the LUs (associated with the new PU) have the same name as the previously added LU pool. LU names are created based on the first 6 characters of the PU name and appending a 2 digit (hex) locaddr. If this results in a name which is the same as an LU pool name, then this fatal error 35 will occur.

To workaround this problem, do not define pool names and PU names which are the same in the first 6 characters. If the pool and PU names happen to be the same in the first 6 characters, then lu-seed should be used on the PU definition so that the LU names created won't be the same as any pool name. [CSCee32607]

•%XCPA-3-STATUS: bay [x] Fatal error detected (code=35) %ECPA4-0-MSG: slotx %DEBUGGER-0-FATAL_ERROR: Fatal error (code=35)

Immediately following a NO SHUT on the channel interface, the ECPA4 encountered a fatal error and dumped.

There is no workaround. [CSCee40253]

•TN3270-server sends up many Signal Request-to-Send (RTS) RUs to VTAM causing a VTAM hot IO condition. A client, for unknown reasons, generated many IAC Breaks (or IAC IPs - Interrupt Process) which the TN3270-server converted into Signal Request-to-Send (RTS) RUs. At the same time the CIP/xCPA sent LSA flow_off to VTAM preventing it from sending the Signal +RSPs back to the TN3270-server. This caused the VTAM IOBUF pool to be exhausted. Either the ATTN key (which generates an IAC IP) or the Break key (which generates an IAC Break) will potentially cause this problem. Note: Each type of TN3270 client will map different key sequences to generate those TN3270 command sequences.

Workaround: Specifying MAXSLOW=15-30 (seconds) in the VTAM XCA major node will cause VTAM to terminate the PU if it remains in this flow off condition more than the time period. This will prevent the excessive IO from impacting VTAM. This only applies when the PU connects to VTAM via an XCA major node. [CSCef08617]

•A 7206vxr router with a PA-4C-E XCPA Port Adapter may incur a Fatal Error 35 Error code causing the XCPA adapter to reload.

There is no workaround. [CSCef05612]

Open Caveats in Version 28.16/Resolved Caveats in Version 28.17

This section describes possible unexpected behavior in Version 28.16. All the caveats listed in this section are resolved in Version 28.17.

•If a c7000 has a CIP card configured with many tn3270 server PUs, when the channel x/2 interface is shut (to allow a backup CIP to take over operation), IOS may issue the following message: 

%CIP2-3-MSG: slot0 %MSG802-3-HARD_ERROR: cls_cip_term: Cleanup takes too long-force 
takedown

The workaround is to issue a "microcode reload" to ensure that the CIP ucode integrity is restored. [CSCee03080]

•A Cisco Mainframe Channel Connection (CMCC) configured for CSNA might reload with a Fatal Error 35 if the connected mainframe stops responding.

These conditions are necessary to see the problem: The CMCC is configured for CSNA. The virtual interface is started then shutdown. The connected mainframe stops responding without shutting down the CSNA device. [CSCee03619]

•A vulnerability in the Transmission Control Protocol (TCP) specification (RFC793) has been discovered by an external researcher. The successful exploitation enables an adversary to reset any established TCP connection in a much shorter time than was previously discussed publicly. Depending on the application, the connection may get automatically re-established. In other cases, a user will have to repeat the action (for example, open a new Telnet or SSH session). Depending upon the attacked protocol, a successful attack may have additional consequences beyond terminated connection which must be considered. This attack vector is only applicable to the sessions which are terminating on a device (such as a router, switch, or computer) and not to the sessions that are only passing through the device (for example, transit traffic that is being routed by a router). In addition, this attack vector does not directly compromise data integrity or confidentiality.

All Cisco products which contain TCP stack are susceptible to this vulnerability.

This advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml, and it describes this vulnerability as it applies to Cisco products that run Cisco IOS® software.

A companion advisory that describes this vulnerability for products that do not run Cisco IOS software is available at http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml. [CSCee35335]

Open Caveats in Version 28.15/Resolved Caveats in Version 28.16

This section describes possible unexpected behavior in Version 28.15. All the caveats listed in this section are resolved in Version 28.16.

•The Tn3270 PUs in a WAIT state. The Virtual Channel Interface is in a Down/Down condition.

Messages seen in the log: TN3270S-0-ILLEGAL_CCMUTEX_RELEASE: CIP2 slot1 : Releasing
unacquired semaphore,lock_held 800A9C4C lock_value FFFFFFFF ccMutex tcb 8010FCD0 thread tcb 81459CB0

The Tn3270 PUs were hung and the Customer Shut/No Shut the Virtual Channel interface in an attempt to recover. The PUs would not recover.

The workaround is to reload the CIP Microcode. [CSCeb82536]

•In a Cisco 7500 router with a CIP2, the CIP2 may crash with a fatal error 32. The problem also may occur on a Cisco 7200 with an XCPA.

The problem may occur when a channel interface with CSNA(s) is shutdown or when a CSNA is unconfigured.

There is no workaround. [CSCec77620]

•%CIP2-6-MSG: slotx %ADAPTER-6-LOGOUT: ESCON dump output is followed by the %DEBUGGER-0-FATAL_ERROR: Fatal error (code=37) dump.

The write subchannel receives a HSCH or a CSCH while the read subchannel is waiting for access to the channel. This will only occur with very heavily utilized claw packing channels.

This behavior was observed with a feature of a mainframe TCP/IP stack that stopped and restarted a packed CLAW connection. The stack restarted the CLAW connection when there was no input from the CMCC.

The workaround is to avoid stopping packed CLAW links while there is traffic. [CSCed18702]

•If HSMA is configured on a Cisco Channel Adapter, the MAC address of a virtual adapter might be displayed incorrectly by the HSMA console command. The displayed MAC address will contain 6 extra "F"s if an odd (first, third, etc.) digit of the address is 8 or greater.

The problem is only in the display of the MAC address. [CSCed37522]

•PU activation is intermittent. Sense Code 10160004 will occur. The PU will eventually activate.

This occurred when running CIP28.14 and TN3270 configured with PUs defined.

There is no workaround. [CSCed38274]

•The message: SCB limit on port NN reached, correlator: NNNN task: NAME XXXXXXXXX. might be seen for a Channel interface, CIP2 or XCPA.

Many CSNA definitions are removed or shutdown.

The workaround is to reload the microcode on the interface. [CSCed42343]

Open Caveats in Version 28.14/Resolved Caveats in Version 28.15

This section describes possible unexpected behavior in Version 28.14. All the caveats listed in this section are resolved in Version 28.15.

•The customer was having problems connecting to PUs performing Inverse DNS
nailing. The client was getting rejected with a device type/unknown error. [CSCea70079]

•A TN3270 client will not receive the VTAM USSMSG10 screen or get a LOGAPPL session when its current LU-LU session ends if the DLUR/DLUS connection has failed and restarted during the active LU-LU session. This problem will only occur on TN3270 clients that are actively in session when/if a Backup DLUS takes over.

There is no work around. If the client disconnects from the LU and reconnects it will get a USSMSG10 or LOGAPPL session. [CSCec04176]

•Router started getting %ADAPTER-6-LOGDATA error then the CIP crashed with a Fatal Error 37. [CSCec07315

•The customer reports tn3270 clients are slow, or failing to connect to the tn3270 server in CIP/CPA.
Tn3270 is configured on CIP/CPA.

The workaround is to identify the client that is requesting a larger number of sessions and not completing the three-way handshake and use an ACL to filter. A temporary workaround would be to shut and no shut the Tn3270 or a specific PU identified as the clients destination IP address.[CSCec16766]

•The CIP/xCPA TN3270-server PUs go into ACT/BUSY state for extended periods of time. Eventually the PUs recover and return to ACTIVE state without any intervention. Another symptom is that LUs may go into P-NTF states. The PUs and/or LUs may enter the hung states when the upstream LLC2 link enters
local busy state. This is due to TN3270-server keeping buffers that it received from the upstream link until the client acknowledges them with a TCP level ACK. This occurs with both TN3270-server DLUR PUs and direct PUs.

There is no workaround. [CSCec57475]

•TN3270-server will allocate an LU to a TN3270 client even if the LU has never been unbound from VTAM. This can lead to session setup failures with sense code 0805000B - Session limit exceeded
This is known to occur under the following conditions:

TN3270-server is configured with:

–DLUR

–lu termination termself

–lu deletion never - This is the default

–Multiple upstream links

–Application that the LU is in session with is not on the DLUS host

–RESETLU=NO is coded on LU or LUGROUP definition in VTAM (this is the default)

It also can happen for any reason where the DLUS host cannot/does not notify
the application host of the termself.

The workaround is to specify RESETLU=YES causes VTAM to DACTLU/ACTLU the LU and notify the application host to send the UNBIND. This will prevent the problem. [CSCec58447]

•The XCPA/CIP experiences a Fatal Error 35. A TN3270 server PU configured with all dynamic LUs can put the TN server in a loop. When the client is trying to connect to the dynamic LU for the very first time, the LuCb is not yet created, and this was putting the server in the loop. This affects only cip/xcpa with microcode version 27-25.

In the customer's environment, they had dynamic LUs configured under all the PUs. And after they brought up the tn3270 server, after a microcode reload, the client tried connecting to those LUs.

There is no workaround. [CSCec59077]

•Part of the output of the Channel Interface Processor, CIP, console command tasks— CPU(1/5/60/busy): 1% 1% 0% 82%—is misleading. "Busy" includes time that will be used when there is other work to be done.

The workaround is to Disregard "busy". [CSCec62591]

•The TN3270-server DLUR controlled LU logon fails with either sense 80140003 or 087D0001. Topology on DLUS shows an ENDPT TG as OPER when in fact it is no longer operational. CIP/xCPA TN3270-server DLUR with multiple end point transmission groups (TGs). TN's DLUR name (CP name) must be greater in the collating sequence than the CP name of the DLUS.

The workaround is to determine the TG that is really not operational but is listed as operational on the DLUS host and delete it.

On the DLUS host issue:

D NET,ADJCP,ID=dlur_name,E - From this get the TG number from the IST1106I message. This is the current TG. D NET,TOPO,ORIG=dlur_name,DEST=dlus_name - This command should list out more than one operational (OPER) TG including the one that was shown in the D NET,ADJCP... command. Find the OPER TG that was not the current TGN.FNET,TOPO,ORIG=dlur_name,DEST=dlus_name,TGN=tg_number,FUNCTION=DELETE [CSCec70608]A CIP/XCPA adapter configured for CSNA may run out of memory over time. You may see the following error message posted in the router log when the memory has been exhausted.

%CIP2-6-MSG: slot0 %CTA-6-INACT_FREEMEM: Free Memory: 0x00090FE8
%CIP2-6-MSG: slot0 %CTA-6-INACT_SLOWDOWN: Slowdown Rcvd: Yes, 180001 ms
%CIP2-6-MSG: slot0 %CTA-6-INACT_SLOWDOWN: Slowdown Sent: Yes, 5089667 ms
%CIP2-6-MSG: slot0 %CTA-6-INACT_SCBS: SCBs in SLC: 128
%CIP2-6-MSG: slot0 %CTA-6-INACT_FLOW_COUNTS: Flow stop/resume 224/221
%CIP2-6-MSG: slot0 %CTA-6-INACT_ATTN_STATE: Attention FSM state: READ PENDING
%CIP2-6-MSG: slot0 %CTA-6-INACT_FLOW_QUEUED: Flow Resume queued in CTA: 0
%CIP2-6-MSG: slot0 %MSG802-6-FLOW_OFF_COUNT: On 505, Off<30 0, Off>30 0, total
505, max off time 0 ms

A buffer may be orphaned when an LLC2 session is terminated due to the T1 timer expiring N2 times.

The workaround is to issue a "microcode reload" command to free up the memory on the CIP/XCPA.
[CSCec76268]

•The CIP/xCPA TN3270 Server converts USSSCS USSMSGs to 3270 datastreams for TN3270E clients even if they have negotiated the SYSREQ function.

The TN3270 client must negotiate TN3270E and the SYSREQ function without negotiating the BIND-IMAGE function.

There is no workaround. [CSCed12577]

•CIP microcode unexpectedly reloads with fatal error 35. This is a rare occurence that can happen if a tn3270 client is disconnected during the processing of data to that client.

There is no workaround. [CSCed18618]

•The HSMA_LINK_STATE message contains an extra "now". Dec 9 07:32:13.092: %ECPA-6-MSG: slot2 %MSG802-6-HSMA_LINK_STATE: The hsma-partner link 4000.0000.0001 is now now unresolved.

This is a cosmetic issue. [CSCed19774]

Open Caveats in Version 28.13/Resolved Caveats in Version 28.14

This section describes possible unexpected behavior in Version 28.13. All the caveats listed in this section are resolved in Version 28.14.

•