cc/td/doc/product/software
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Channel Port Adapter Microcode Release Note and Microcode Upgrade Requirements

Channel Port Adapter Microcode Release Note and Microcode Upgrade Requirements

July 24, 2000

This document contains the release notes for the Channel Port Adapter (CPA) microcode software. 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.

Note In this document, references to CPA correspond to both the ECPA and PCPA.

The CPA microcode is unbundled from the Cisco IOS software. Therefore, you can obtain the CPA microcode as a separately loadable software module and match a version of the CPA microcode to the Cisco IOS software. Refer to the section "CPA Microcode/Cisco IOS Software Compatibility Matrix" for more information.

Cisco IOS Release 11.3(3)T and later supports the ECPA. Cisco IOS Release 11.3(7)T and later and Release 12.0(1) and later support the PCPA. There is a default setting in the Cisco IOS software that corresponds to a particular microcode that is already loaded on the router Flash memory card when a CPA is purchased as a system. Refer to the section "CPA Microcode/Cisco IOS Software Compatibility Matrix" for more information. However, when the CPA is ordered as a spare (shipped separately from a system), you might be required to download the microcode image from Cisco Connection Online (CCO).

Note We recommend that you load and use the version of CPA microcode that corresponds with your Cisco IOS software, in which case the following step is not necessary.

If you choose to use a version of the CPA microcode other than the one that corresponds with your Cisco IOS software, you must copy a CPA microcode image onto the router Flash memory card and use the microcode router configuration command to specify this microcode image rather than the default microcode image.

For general information on CPA microcode, refer to the PA-1C-E ESCON Channel Port Adapter Installation and Configuration document or the PA-1C-P Parallel Channel Port Adapter Installation and Configuration document that shipped with the port adapter.

Introduction

This release note describes the CPA microcode caveats for the latest version of CPA microcode. It includes the CPA microcode releases described in the "CPA Microcode Release xcpa26 Caveats" section. Also included is an overview of the procedures required to upgrade to the latest versions of CPA microcode.

This CPA microcode release note discusses the following topics:

Cisco IOS Software and Cisco 7200 Family Hardware Documentation

For documentation of CPA features in the Cisco IOS Release 11.3, refer to Table 1.


Table 1: Cisco IOS Release 11.3 Publications
Cisco IOS 11.3 Release Publication Tracking Number

Configuration Fundamentals Configuration Guide

DOC-CFCG11.3=

Configuration Fundamentals Command Reference

DOC-CFCR11.3=

Bridging and IBM Networking Configuration Guide

DOC-IBMNCG11.3=

Bridging and IBM Networking Command Reference

DOC-IBMNCR11.3=

Cisco IOS Software Command Summary

DOC-CIOSCS11.3=

System Error Messages

DOC-SYSEM11.3=

Release Notes for Cisco IOS Release 11.3

78-4998-xx

For documentation of CPA features in the Cisco IOS Release 11.3T, refer to Table 2.


Table 2: Cisco IOS Release 11.3T Publications
Cisco IOS Release 11.3T Publication Tracking Number

Release Notes for Cisco IOS Release 11.3

78-4998-xx

Release Notes for Cisco 7000 Family for Cisco IOS Release 11.3T

78-5015-xx

Cisco IOS Release 11.3T New Features

Available on CCO only

For documentation of CPA features in the Cisco IOS Release 12.0, refer to Table 3.


Table 3: Cisco IOS Release 12.0 Publications
Cisco IOS Release 12.0 Publication Tracking Number

Configuration Fundamentals Configuration Guide

DOC-785829=

Configuration Fundamentals Command Reference

DOC-785830=

Bridging and IBM Networking Configuration Guide

DOC-785850=

Bridging and IBM Networking Command Reference

DOC-785851=

Cisco IOS Software Command Summary

DOC-785859=

Cisco IOS Software System Error Messages

DOC-785860=

Debug Command Reference

DOC-785858=

Release Notes for Cisco IOS Release 12.0

78-6035-xx

For documentation of CPA features in the Cisco IOS Release 12.0T, refer to Table 4.


Table 4: Cisco IOS Release 12.0T Publications
Cisco IOS Release 12.0T Publication Tracking Number

Release Notes for Cisco IOS Release 12.0

78-6035-xx

Release Notes for Cisco 7000 Family for Cisco IOS Release 12.0T

78-6055-xx

Cisco IOS Release 12.0T New Features

Available on CCO only

For documentation of CPA features in the Cisco IOS Release 12.1, refer to Table 5.


Table 5: Cisco IOS Release 12.1 Publication
Cisco IOS Release 12.1 Publication Tracking Number

Cisco IOS Configuration Fundamentals Configuration Guide

DOC-7810222=

Cisco IOS Configuration Fundamentals Command Reference

DOC-7810223=

Cisco IOS Bridging and IBM Networking Configuration Guide

DOC-7810256=

Cisco IOS Bridging and IBM Networking Command Reference, Volume I

DOC-7810257=

Cisco IOS Bridging and IBM Networking Command Reference, Volume II

DOC-7810520=

Cisco IOS Command Summary

DOC-7810262=

Cisco IOS System Error Messages

DOC-7810263=

Cisco IOS Debug Command Reference

DOC-7810264=

Release Notes for Cisco IOS Release 12.1

78-10724-xx

For documentation of CPA features in the Cisco IOS Release 12.1T, refer to Table 6.


Table 6:
Cisco IOS Release 12.1T Publication Tracking Number

Release Notes for Cisco IOS Release 12.1

78-10724-xx

Release Notes for Cisco 7000 Family for Cisco IOS Release 12.1T

78-10811-xx

Cisco IOS Release 12.1T New Features

Available on CCO only

Cisco IOS Release 12.1T Publications

For hardware installation and configuration information on the CPA, refer to the PA-1C-E ESCON Channel Port Adapter Installation and Configuration document and the PA-1C-P Parallel Channel Port Adapter Installation and Configuration document that shipped with the port adapter.

To obtain general information about documentation, refer to the section "Cisco Connection Online" or call customer service at 800 553-6387 or 408 526-7208. Customer service hours are 5:00 a.m. to 6:00 p.m. Pacific time, Monday through Friday (excluding Cisco-observed holidays). You can also send e-mail to cs-rep@cisco.com, or you can refer to the Cisco Information Packet that shipped with your router.

How Does CPA Microcode Ship?

In Cisco IOS Release 11.3(3)T and later, the CPA microcode is available from the following sources:

CPA Microcode Release xcpa27 Caveats

The following section describes the caveats to current CPA microcode versions and the modifications made in current CPA microcode versions for xcpa27 microcode. The caveats listed apply to only the most serious problems. See Table 7 for the Cisco IOS software releases supported by xcpa27 microcode.

Caveats for Version 27.8/Version 27.9 Modifications

This section describes possible unexpected behavior by Version 27.8. All the caveats listed in this section are resolved in Version 27.9. See Table 7 for the Cisco IOS software release that corresponds to the 27.9 microcode version.

The workaround is to configure the TN3270 server to assign a different LU. [CSCdk30136]
The workaround is to reload the microcode. [CSCdm44279]
The workaround is to define alternate links to the same VTAM host only at the host end, or avoid multiple links to the same VTAM host. [CSCdp02702]
CIP2-3-MSG: slot0 %SSI802-3-FATAL_ERROR: SSI_ASSERT failure in ../ssi/ssi_buff.c @ 1035 - msgP->m_next
Jan 31 15:40:12: %CIP2-0-MSG: slot0 %DEBUGGER-0-FATAL_ERROR: Fatal error (code=09)
There is no workaround. [CSCdp84989]
There is no workaround. [CSCdr28173]
The workaround is to shutdown and restart the TN3270 server using the shutdown command. [CSCdr30174]
The workaround is to avoid manipulating nailing definitions without issuing the microcode reload command. [CSCdr32205]
There is no workaround. [CSCdr38323]
The workaround is to configure the nop or timing-mark parameters. [CSCdr59806]

Caveats for Version 27.7/Version 27.8 Modifications

This section describes possible unexpected behavior by Version 27.7. All the caveats listed in this section are resolved in Version 27.8. See Table 7 for the Cisco IOS software release that corresponds to the 27.8 microcode version.

The workaround for customers who are using pool-based LU nailing is to avoid configuring the no shut command multiple times on the same PU. [CSCdm24372]
The workaround is to not disconnect a client during the logon process; that is, after requesting an application from the SSCP screen, but before establishing the LU-LU session with that application. [CSCdm51110]
bad error-code 12 given
This valid error code indicates a missing TERMSELF response. The code to log and format this specific error into a console message is missing.
There is no workaround. [CSCdm55961]
The workaround is to not configure the TN3270 monitor or a similar product. [CSCdp16086]
There is no workaround. [CSCdp18803]
The workaround is to configure the OpenConnect client to use a single device name. [CSCdp24684]
There is no workaround. [CSCdp51038]
The workaround is to configure fewer DLUR links. [CSCdp79125]
There is no workaround. [CSCdp99538]
The workaround is to recycle the XCA major node. [CSCdr03103]
Offload time out
This problem occurs when the client establishes a connection to the server, issues a request, gets the response and then closes the connection by sending a RST (reset) segment.
The server issues a read to the connection, the read message is blocked and returns with the error message. The read message should return with a 0 message, meaning that the connection was closed. This problem happens after one minute.
There is no workaround. [CSCdr05011]
There is no workaround. [CSCdr09662]
The workaround is to use only Definite Response flows. [CSCdr10939]
There is no workaround. [CSCdr12567]
%ECPA-4-MSG: slotx %TN3270S-4-NO_LU_SESSIONS
: No LU sessions left in :GENERIC for PUs at IP addr xxx.xxx.xxx.xxx, port 23
The TN3270 server PU output displays skipped LUs. The TN3270 server does not select these LUs. All other LUs are set to ACT/SESS. Note that there is no LU display for lu4 and lu9.
lu    name   client-ip:tcp       nail   state    model frames in out   idle for
1   ABCD2001 xxx.xxx.xxx.x:1042    N   ACT/SESS 3278S5E  38418   19615   0:6:6
2   ABCD2002 xxx.xxx.xxx.xxx:1043  N   ACT/SESS 3278S2E  21473   14085   0:18:11
3   ABCD2003 xxx.xxx.xxx.xx:1665   N   ACT/SESS 3278S5E  9992    6147    0:0:6
5   ABCD2005 xxx.xxx.xxx.x:1046    N   ACT/SESS 3278S5E  12731   8074    10:33:7
6   ABCD2006 xxx.xxx.xxx.x:4033    N   ACT/SESS 3278S2E  31367   18838   2:0:51
7   ABCD2007 xxx.xxx.xxx.x:1045    N   ACT/SESS 3278S5E  8184    4413    2:55:4
8   ABCD2008 xxx.xxx.xxx.xx:1323   N   ACT/SESS 3278S2E  16274   7580    4:28:19
10  ABCD200A xxx.xxx.xxx.xxx:1205  N   ACT/SESS 3278S2E  7752    4175    1:3:39
The workaround is to add more PUs to the TN3270 server and VTAM configuration. [CSCdr13016]
The workaround is for the TN3270E client to specify PAC004 instead of PAC04. [CSCdr13524]
%CTA-0-INACTIVE: PA1 CTA 7C00-50 reset after being inactive for 180 seconds
The workaround is to shutdown the CSNA subchannel before shutting down VTAM. [CSCdr13804]
The workaround is to ignore or activate the PU to correct the lu-available number. [CSCdr17334]
A workaround is to avoid restarting the TN3270 server when there is a heavy processing load. [CSCdr18250]
There is no workaround. [CSCdr19257]
The workaround is to remove the response time group configuration. [CSCdr20842]
  struct {short PACKED(pktLength); short PACKED(len); 
          unsigned char PACKED(bytes[16]);}
This is a cosmetic failure and is present in all CIP and CPA microcode releases.
There is no workaround. [CSCdr24412]
There is no workaround. [CSCdr28173]

Caveats for Version 27.6/Version 27.7 Modifications

This section describes possible unexpected behavior by Version 27.6. All the caveats listed in this section are resolved in Version 27.7. See Table 7 for the Cisco IOS software release that corresponds to the 27.7 microcode version.

There is no workaround. [CSCdj90734]
The workaround is to reload the microcode. [CSCdm44279]
Get CMPCP_DUPL_TOKEN:
This problem occurs when bringing up a TG from the host activating a transport resource list entry (TRLE) and when multiple TGs are configured with paths to multiple mainframes via a director.
The workaround is to activate the TRLE again. [CSCdp66330]
The workaround is to configure fewer DLUR links. [CSCdp79125]
%CIP2-4-MSG: slot0 %OFFL-4-BADDESC: 0/9300/60 Socket descriptor 259 in request is bad: state DESC_Holddown compare 259
This is a cosmetic problem that should not impact performance.
There is no workaround. [CSCdp84965]
The workaround is to configure fewer Offload and CLAW statements. [CSCdp85560]
There is no workaround. [CSCdp85890]
There is no workaround. [CSCdp90214]
The workaround is to avoid name conflicts by specifying lu-seed names on every PU in the configuration that do not overlap with the host-defined names. [CSCdr06007]
The workaround is to reject any connect requests for that LU until the Notify/Unavailable message transmission is complete. [CSCdp66402]
There is no workaround. [CSCdp88662]

Caveats for Version 27.5/Version 27.6 Modifications

This section describes possible unexpected behavior by Version 27.5. All the caveats listed in this section are resolved in Version 27.6. See Table 7 for the Cisco IOS software release that corresponds to the 27.6 microcode version.

There is no workaround. [CSCdk21633]
%CONFIG-3-WORKLEFT:Work pending on work queue when device terminated 
%DEBUGGER-0-FATAL_ERROR:Fatal error (code=37)
There is no workaround. [CSCp54593]
To enable this passive activation, enter the tn-parameter code codevalue command with a code value of 3. This command tells the Server to put all PUs in a waiting state and not to send ReqACTPU or TEST/XID messages to the host. [CSCdm80770]
The workaround is to specify XTX=7 on the route.nlm. [CSCdp09295]
%CIP2-3-MSG: slot0 %SSI802-3-FATAL_ERROR: SSI_ASSERT failure in ../cta802/ciptask.c @ 322 - !mxcb->mx_next
%CIP2-0-MSG: slot0 %DEBUGGER-0-FATAL_ERROR: Fatal error (code=09)
The assertion is intended to detect messages with 15 or more memory buffers (mbufs). There is no workaround. [CSCdp13245]
The workaround is to avoid creating idle subchannel conditions by not using the Z NET cancel command. Other possible workarounds include shutting down the router channel interface or removing the CSNA configuration statement before issuing the Z NET cancel command. [CSCdp31175]
The workaround is to not configure a listen-point PU and another PU with the same IP address and TCP port pair. [CSCdp45166]
There is no workaround. [CSCdp58083]
dec 20 05:48:57 UTC: %CBUS-3-CIPCFGFAIL: Channel0/2: configuration command TN3270S_LISTEN_POINT_PU_LU_POOL  cmd 40 failed
There is no workaround. [CSCdp56576]
There is no workaround. [CSCdp69064]
The workaround is to configure the tn-parameter code codevalue command with a code value of 9. This workaround applies only if the client is capable of requesting a specific LU name. If the client does not specify an LU name, then an LU will be awarded based on the LU Nailing rules configured. [CSCdp58041]

Caveats for Version 27.4/Version 27.5 Modifications

This section describes possible unexpected behavior by Version 27.4. All the caveats listed in this section are resolved in Version 27.5. See Table 7 for the Cisco IOS software release that corresponds to the 27.5 microcode version.

There is no workaround. [CSCdk21633]
This problem occurs in CMCC microcode releases cip22-35, cip24-10, cip25-10, cip26-5, xcpa 26-5, cip27-0, xcpa27-0, and later.
The workaround is to perform the shutdown procedure when there is no activity on the TN3270 sessions. [CSCdm35562]
This setting is incorrect for a LEN node direct connect configuration and causes connection failure problems when connecting to the SNA Switch. The SNA Switch expects the device to negotiate a TG number, but the TN3270 Server does not support this action. The TN3270 Server must either negotiate a TG number or not configure a TG-capable bit setting.
The workaround is to configure the snasw port command with the conntype len keyword specified on the SNA Switch port to which the TN3270 Server connects. The TN3270 Server will no longer set the parallel TGs supported bit during the XID exchange for direct PUs. [CSCdm71315]
There is no workaround. [CSCdm73361]
This fix adds a 10 second delay between receiving the shutdown command and responding to the shutdown command. This time window will allow any data that is in queue to transmit before the shutdown procedure.
There is no workaround. [CSCdm80945]
The workaround is to upgrade the CMCC microcode or to restart the external communication adapter (XCA) nodes. [CSCdm88239]
%TN3270S-1-NO_BIND_REQ_RCVD: No BIND REQ received on LU [chars].[dec], 120*ONESEC
This error and several others are logged as priority 1 (alert) messages in error reports. The priority level of the following error messages is now priority level 3:
NO_PSID_RSP_RCVD
NO_NTFY_AV_RSP_RCVD
NO_BIND_REQ_RCVD
NO_SDT_REQ_RCVD
NO_SDT_TMARK_RCVD
NO_UNBIND_TMARK_RCVD
NO_NTFY_UA_RSP_RCVD
NO_DYN_ACTLU_REQ_RCVD
NO_UNBIND_RSP_RCVD 
NO_TERMSELF_RSP_RCVD
[CSCdm94788]
VTAM indicates whether it can receive the CV64 by setting a bit in the PU Capabilities vector (CV80) in the outbound ACTPU Request message. For DLUR PUs with all static LUs, the VTAM may not send the CV80 and the TN3270 Server will not send the CV64.
If the parameter INCLUD0E=YES is coded for this PU in the switched major node, the VTAM will send CV80 and enable the TN3270 Server to send the CV64. [CSCdp06211]
There is no workaround. [CSCdp06760]
The workaround is to specify XTX=7 on the route.nlm. [CSCdp09295]
The workaround is to code an lu-seed in the router on the PU, then connect to a TN3270E client configured with the correct LU name. [CSCdp09708]
There is no workaround. [CSCdp24670]
J+FKP4390E UNEXPECTED DATA RECEIVED.QUE.HELD.LU="LUname"
There is no workaround. [CSCdp30854]
The workaround is to avoid creating idle subchannel conditions by not using the Z NET cancel command. Other possible workarounds include shutting down the router channel interface or removing the CSNA configuration statement before issuing the Z NET cancel command. [CSCdp31175]
The workaround is to stop and restart the CLAW driver causing the CLAW control link to synchronize again. [CSCdp32675]
There is no workaround. [CSCdp43223]
The workaround is to add an additional 3 LUs to the VTAM switched major node, leaving the print server to request only 10 TNET connections. [CSCdp43253]
The workaround is to code the LUGROUP parameter with one of the following values: SSCPFM=USS3270 or SSCPFM=USS3270. [CSCdp46564]
There is no workaround. [CSCdp47885]
There is no workaround. [CSCdp55519]
There is no workaround. [CSCdp34029]

Caveats for Version 27.3/Version 27.4 Modifications

This section describes possible unexpected behavior by Version 27.3. All the caveats listed in this section are resolved in Version 27.4. See Table 7 for the Cisco IOS software release that corresponds to the 27.4 microcode version.

The CMCC TN3270 Server does not use this client IP address for matching on LU nailing statements in the configuration. [CSCdj44584]
The workaround is to make sure that the RMAC TN3270 server PU resides on the same CMCC adapter as the TN3270 Server. [CSCdm01837]
The workaround is to configure the maximum LLC or threshold to equal the number of XCA lines configured. [CSCdm29597]
This problem occurs in CMCC microcode releases cip22-35, cip24-10, cip25-10, cip26-5, xcpa 26-5, cip27-0, xcpa27-0, and later.
The workaround is to perform the shutdown procedure when there is no activity on the TN3270 sessions. [CSCdm35562]
The workaround is to remove the PATH statements. [CSCdm42103]
The workaround is to reload the microcode. [CSCdm44279]
The workaround is to not disconnect a client during the logon process; that is, after requesting an application from the SSCP screen, but before establishing the LU-LU session with that application. [CSCdm51110]
A workaround is available. Contact the Cisco TN3270 Server development engineers for the interim fix. [CSCdm61159]
This fix adds a debug message to the log and marks the ACTLU as not processed.
There is no workaround. [CSCdm69186]
The workaround is to space out the TCP/IP requests. [CSCdm75120]
%CIP2-3-MSG: slot0 %OFFL-3-NOMEM2: Not enough memory to process socket requests,              0 open, 0 in holddown
The workaround is to increase memory. [CSCdm76552]
%DEBUGGER-0-FATAL_ERROR: Fatal error (code=35)
This error occurs when the TN3270 Server is shut down while traffic is still transmitting. [CSCdm78261]
There is no workaround. [CSCdm82521]
The workaround is to delay the shutdown for 20 ms after the last send() message. [CSCdm85311]
The workaround is to set the RU size so that it is at least as big as the MTU on the file transfer path. [CSCdm86734]
There is no workaround. [CSCdm88195]
The workaround is to not perform the shutdown-writing. [CSCdm92713]
The workaround is to use buffers that are 2000 bytes or less or non-structured fields (presentation space transfer. To enable the fix in CMCC releases cip27-4 and greater and xcpa27-4 and greater, you must configure the TN3270 tn-parameter code codevalue command with a code value of 7. [CSCdm93990]
There is no workaround. [CSCdp00921]
slot0:Fix this
This error will not cause any serious problems.
There is no workaround. [CSCdp04360]
There is no workaround. [CSCdp06877]
pu CISCO    04921002 157.2.196.101   token-adapter 31 24 rmac 4000.7206.0001
client ip 157.2.0.0 255.255.255.0 lu 4 20
The problem occurs when the client ip or no tn3270 server command is entered. The problem also can occur when the interface is shut down.
There is no workaround. [CSCdp07729]
There is no workaround. [CSCdp08103]

Caveats for Version 27.2/Version 27.3 Modifications

This section describes possible unexpected behavior by Version 27.1. All the caveats listed in this section are resolved in Version 27.2. See Table 7 for the Cisco IOS software release that corresponds to the 27.2 microcode version.

The workaround is to not enter the no tn3270 command.
There is no workaround. [CSCdk83774]
%CIP2-1-MSG: slot1 %TN3270S-1-RP_PU_CONFLICT:RP & CIP hold conflicting PU    name(xxxxxxxx) or index(92)
Where "xxxxxxxx" is the PU name.
%CBUS-3-CIPCFGFAIL: Channel1/2: configuration command TN3270S_DLUR_PU_NEW cmd 18    failed
%CIP2-0-MSG: slot1 %DEBUGGER-0-FATAL_ERROR: Fatal error (code=32)
The workaround is to perform the shutdown when the server load is light. [CSCdk83807]
The workaround is to issue the shut command only after the client traffic terminates. [CSCdk87658]
The workaround is to upgrade to the recommended CIP microcode version which corresponds to your Cisco IOS software. [CSCdm28629]
This problem occurs in CMCC microcode releases cip22-35, cip24-10, cip25-10, cip26-5, xcpa 26-5, cip27-0, xcpa27-0, and later.
The workaround is to perform the shutdown procedure when there is no activity on the TN3270 sessions. [CSCdm35562]
There is no workaround.
To enable the fix in the cip24-13 microcode, the maximum-lu command must be added to the TN3270 Server configuration file. [CSCdm36152]
There is no workaround. [CSCdm37663]
The workaround is to use Cisco IOS Release 11.2(16)BC and CIP microcode version cip24-10. [CSCdm53220]
To enable this fix and filter out the PA1 messages, you must configure the TN3270 tn-parameter code codevalue command with a code value of 2.
There is no workaround. [CSCdm54076]
There is no workaround. [CSCdm55234]
bad error-code 12 given
This valid error code indicates a missing TERMSELF response. The code to log and format this specific error into a console message is missing.
There is no workaround. [CSCdm55961]
The workaround is to reload the CMCC adapter after changing the DLUR configuration. [CSCdm56389]
The workaround is to upgrade to Attachmate software release 6.3. [CSCdm58334]
The problem occurs because the client network maximum segment size (MSS) is set to 4000 and the server network MSS is set to 1500. The CMCC TCP stack attempts to increase the maximum transmission unit (MTU) from 1500 to 4000 every 10 minutes for each TCP connection. The Cisco IOS software sends only one or two ICMP messages per second, therefore some TCP packets are dropped and must be retransmitted. The retransmission intervals increase exponentially and these intervals appear to the user as a delay in response time.
To enable this fix in microcode version cip22-39 and later, you must configure the TN3270 server keepalive seconds command with a value of 14444. To enable this fix in microcode version cip27-3, xcpa27-3 and later, you must configure the TN3270 server tn-parameter code codevalue value minutes command with a code value of 5. Value is the number of minutes between path MTU discovery retries. The default is 10 minutes. A value of 0 implies an infinite timer value.
There is no workaround for other microcode versions. [CSCdm61803]
The workaround is to close and re-open the server socket by restarting the server application on the host. [CSCdm63283]
There is no workaround. [CSCdm69837]
This problem occurs when the TN3270 server DLUR component improperly saves RU chain bits from the original request to create a response message. This generates the +RSP sense data 400B0000.
The workaround is to increase the RU sizes on the DLUR/DLUS sessions. To increase the RU sizes on the DLUR/DLUS sessions, the user must do the following:
%CIP2-3-MSG: slot0 %OFFL-3-NOMEM2: Not enough memory to process socket requests,              0 open, 0 in holddown
The workaround is to increase memory. [CSCdm76552]
To enable the CSCdk83774 fix in microcode versions cip27-3, xcpa27-3 and later, you must configure the TN3270 tn-parameter code codevalue command with a code value of 6. [CSCdm76554]

Caveats for Version 27.1/Version 27.2 Modifications

This section describes possible unexpected behavior by Version 27.1. All the caveats listed in this section are resolved in Version 27.2. See Table 7 for the Cisco IOS software release that corresponds to the 27.2 microcode version.

The workaround is to reload the CMCC microcode. [CSCdj08904]
VTAM version 4.3 introduced restrictions for the PORT TIMER value. The TIMER value cannot be less than the CMCC's T1 * N2. VTAM uses a hard-coded N2 value of 2. Before this fix, the CMCC reported a T1 value of 10. The VTAM documentation indicates that the T1 value is measured in tenths of a second. Therefore, a T1 value of 10 should equal 1 second. However, VTAM interprets the T1 value in seconds so a T1 value of 10 equals 10 seconds, not 1 second. VTAM then multiplies the value by 2 to get a minimum TIMER value of 20 seconds.
The CMCC's reported T1 value is not the CMCC LLC T1 value. Because VTAM overloads the use of the PORT TIMER, do not adjust the CMCC's real LLC T1 value to alter the PORT TIMER. These adjustments can cause severe LLC2 problems.
VTAM overloads the use of PORT TIMER. TIMER is used to set TEST request interval on connect outs. After each TEST request is sent, VTAM sets a timer equal to the PORT TIMER number of seconds and waits for a TEST response. If the TEST response is not received by VTAM before the timer expires, the next TEST request is sent. In CMCC scenarios, the first TEST request is a TEST local, the second is a spanning-route explorer.
For the CMCC, most VTAM initiated LLC connections will not complete before the PORT TIMER seconds expire because the local TEST does not leave the CMCC's internal LAN. LLC connection setup requires a minimum of 20 seconds. VTAM will timeout on LSA commands if a response is not received within the set PORT TIMER value. For example, when VTAM sends a CONNECT request the CONNECT CONFIRM must be received before the PORT TIMER expires. The SABME and UA must be exchanged within the value set in PORT TIMER. If the SABME must be retried, the PORT ITMER might expire before the CONNECT CONFIRM is returned to VTAM.
The workaround is to set the PORT TIMER value to 20 seconds or more unless the user is confident that the LSA commands will not timeout. [CSCdj45782]
A window exists for brief TCP connections when a connection is made with TCP/IP on the CMCC and then broken (FIN received) before Offload has received and processed an Accept socket request from the host. In this situation, Offload misses the notification from TCP/IP that the connection had been terminated.
There is no workaround. [CSCdk12291]
INOP STATUS
The workaround is to reactivate the external communication adapter (XCA) major node. [CSCdk36329]
There is no workaround.
A new channel interface configuration command which is valid only for the CPA, state-tracks-signal, fixes this problem. This command directs the CPA's channel interface state to follow the physical signal value when the interface is in the no shut state. [CSCdk44052]
The workaround is to shut down and restart the PU or to cycle the PU in VTAM. [CSCdk57112]
The workaround is to restart the session. [CSCdk57453]
The workaround is to deactivate the LU or the owning PU in VTAM. [CSCdk60263]
There is no workaround. [CSCdk83774]
Other SYSREQ key errors that occur when the TN3270 server is configured include:
The workaround is to not use the SYSREQ key. [CSCdk83960]
There is no workaround. [CSCdk89383]
There is no workaround. [CSCdk91964]
A workaround is to distribute the traffic to multiple boxes to avoid a channel capacity of 95 percent or greater. [CSCdk92004]
This problem does not occur when using select() under VM or MVS because select() is issued for one socket at a time. This problem occurs when using TPF if the select() request contains 28 or more socket descriptors.
There is no workaround for this problem. This DDTS is a continuation of CSCdk86184. [CSCdm02126]
CLAW-6-TOOSMALL: xx byte IP datagram is to small, device x/yyyy/zz
The workaround is to modify the network so that IP fragments do not occur. [CSCdm11522]
%CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF50, slot 3, cmd code 2
%CMCC-3-RSETFAIL: Interface Channel3/2: Error (8010) enable
%DEBUGGER-0-FATAL_ERROR: Fatal error (code=35)
The problem occurs when the CMCC virtual interface is shut down or when a no tg hsas-ip or tg ip command is issued.
There is no workaround. [CSCdm21378]
The workaround is to upgrade to the recommended CIP microcode version which corresponds to your Cisco IOS software. [CSCdm28629]
The following trace scenario illustrates the problem:
*Apr 26 13:36:24: %CMCC: slot0 Out Lu 5.54: len=10,2C003601 00AE4B81 00C8
*Apr 26 13:36:24: %CMCC: slot0 Out Lu 5.54: sna-state=8501,lu-flags=0D24D204
*Apr 26 13:36:24: %CMCC: slot0 In Lu 5.54: len=10,2C000136 00AECB81 00C8
*Apr 26 13:36:24: %CMCC: slot0 In Tnet 212: len=13,00000100 42F7D7F5 11D7F5FF      EF
*Apr 26 13:36:24: %CMCC: slot0 Out Lu 5.54: sna-state=8D01,lu-flags=0D24D204
*Apr 26 13:36:24: %CMCC: slot0 Out Lu 5.54: len=1484,2C003601 00AF0381      80F10611 5D611DE8
*Apr 26 13:36:24: %CMCC: slot0 Out Lu 5.54: sna-state=8D01,lu-flags=0D24D204
*Apr 26 13:36:24: %CMCC: slot0 Out Tnet 212: len=1482,00000200 6C010411      5D611DE8 40404040
*Apr 26 13:36:24: %CMCC: slot0 In Tnet 212: len=8,02000000 6C00FFEF
*Apr 26 13:36:24: %CMCC: slot0 Out Lu 5.54: sna-state=8509,lu-flags=0B24D204
*Apr 26 13:36:24: %CMCC: slot0 In Lu 5.54: len=9,2C000136 00AF8381 00
*Apr 26 13:36:24: %CMCC: slot0 In Lu 5.54: len=15,2C000136 00200392 20F7D7F5      11D7F5
*Apr 26 13:36:24: %CMCC: slot0 Out Lu 5.54: len=9,2C003601 00B00391 40
There is no workaround. [CSCdm31347]
The following messages appear on the TN3270 console:
%CMCC: slot4 [bad telnet connect]13[ipAddrClient]172.16.25.255:[tcpPortCl
%CMCC: slot4 ----ient]0x40C:[connectReasonCode]0xE:[tn3270eDeviceType]IBM
%CMCC: slot4 -----3278-5-E:[tn3270eDeviceName]:[tn3270eSubErr]no-naill:
The workaround is to remove LU Nailing and restart the TN3270 server. Removing the LU Nailing command is not sufficient. Another workaround is to use a dynamic LU build. This build works with LU Nailing. [CSCdm36117]

Caveats for Version 27.0/Version 27.1 Modifications

This section describes possible unexpected behavior by Version 27.0. All the caveats listed in this section are resolved in Version 27.1. See Table 7 for the Cisco IOS software release that corresponds to the 27.1 microcode version.

The workaround is to increase the maxpiu value, preferably to the default which is 20470 bytes. [CSCdk71668]
The workaround is to limit the number of sockets selected in a single select request to 27 or less. [CSCdk86184]
%ADAPTER-0-DIAGFAIL: Port 0 failed the PCA Diagnostic Mode 1 diagnostic
%ADAPTER-0-DIAGDATA: Module Call: 0 0 Error ID: 0 F0000000
A workaround is to change the Cisco 7200 series NPE memory to 64 MB or to replace the 32 MB of memory on the PCPA with 16 MB of memory. [CSCdm09617]
%CBUS-3-CMDTIMEOUT: Cmd timed out, CCB 0x5800FF50, slot 3, cmd code 2
%CMCC-3-RSETFAIL: Interface Channel3/2: Error (8010) enable
%DEBUGGER-0-FATAL_ERROR: Fatal error (code=35)
The problem occurs when the CMCC virtual interface is shut down or when a no tg hsas-ip or tg ip command is issued.
There is no workaround. [CSCdm21378]

CPA Microcode Release xcpa26 Caveats

The following section describes the caveats to current CPA microcode versions and the modifications made in current CPA microcode versions for xcpa26 microcode. The caveats listed apply to only the most serious problems. See Table 7 for the Cisco IOS software releases supported by xcpa26 microcode.

Caveats for Version 26.14/Version 26.15 Modifications

This section describes possible unexpected behavior by Version 26.14. All the caveats listed in this section are resolved in Version 26.15. See Table 7 for the Cisco IOS software release that corresponds to the 26.15 microcode version.

The workaround is to define alternate links to the same VTAM host only at the host end, or avoid multiple links to the same VTAM host. [CSCdp02702]
CIP2-3-MSG: slot0 %SSI802-3-FATAL_ERROR: SSI_ASSERT failure in ../ssi/ssi_buff.c @ 1035 - msgP->m_next
Jan 31 15:40:12: %CIP2-0-MSG: slot0 %DEBUGGER-0-FATAL_ERROR: Fatal error (code=09)
There is no workaround. [CSCdp84989]
There is no workaround. [CSCdr54396]

Caveats for Version 26.13/Version 26.14 Modifications

This section describes possible unexpected behavior by Version 26.13. All the caveats listed in this section are resolved in Version 26.14. See Table 7 for the Cisco IOS software release that corresponds to the 26.14 microcode version.

The workaround is to not disconnect a client during the logon process; that is, after requesting an application from the SSCP screen, but before establishing the LU-LU session with that application. [CSCdm51110]
bad error-code 12 given
This valid error code indicates a missing TERMSELF response. The code to log and format this specific error into a console message is missing.
There is no workaround. [CSCdm55961]
The workaround is to not configure the TN3270 monitor or a similar product. [CSCdp16086]
There is no workaround.[CSCdp51038]
The workaround is to configure fewer DLUR links. [CSCdp79125]
%TN3270S-1-RP_PU_CONFLICT:RP & CIP hold conflicting PU name(XXXXX) or index(xxx)
This problem occurs when multiple PUs are defined and the no pu command is issued to remove a PU that is not the last in chain. The problem also may occur when DLUR is configured.
The workaround is to remove the last PUs in the list first (also known as last in first out [LIFO] order). [CSCdp98933]
There is no workaround. [CSCdp99538]
The workaround is to recycle the XCA major node. [CSCdr03103]
%CTA-0-INACTIVE: PA1 CTA 7C00-50 reset after being inactive for 180 seconds
The workaround is to shutdown the CSNA subchannel before shutting down VTAM. [CSCdr13804]
  struct {short PACKED(pktLength); short PACKED(len); 
          unsigned char PACKED(bytes[16]);}
This is a cosmetic failure and is present in all CIP and CPA microcode releases. There is no workaround. [CSCdr24412]
There is no workaround. [CSCdr28173]

Caveats for Version 26.12/Version 26.13 Modifications

This section describes possible unexpected behavior by Version 26.12. All the caveats listed in this section are resolved in Version 26.13. See Table 7 for the Cisco IOS software release that corresponds to the 26.13 microcode version.

The workaround is to reload the microcode. [CSCdm44279]
Offload time out
This problem occurs when the client establishes a connection to the server, issues a request, gets the response and then closes the connection by sending a RST (reset) segment.
The server issues a read to the connection, the read message is blocked and returns with the error message. The read message should return with a 0 message, meaning that the connection was closed. This problem happens after one minute.
There is no workaround. [CSCdr05011]
%CIP2-4-MSG: slot0 %OFFL-4-BADDESC: 0/9300/60 Socket descriptor 259 in request is bad: state DESC_Holddown compare 259
This is a cosmetic problem that should not impact performance.
There is no workaround. [CSCdp84965]
The workaround is to configure fewer Offload and CLAW statements. [CSCdp85560]
There is no workaround. [CSCdp85890]

Caveats for Version 26.11/Version 26.12 Modifications

This section describes possible unexpected behavior by Version 26.11. All the caveats listed in this section are resolved in Version 26.12. See Table 7 for the Cisco IOS software release that corresponds to the 26.12 microcode version.

There is no workaround. [CSCdk21633]
%CONFIG-3-WORKLEFT:Work pending on work queue when device terminated 
%DEBUGGER-0-FATAL_ERROR:Fatal error (code=37)
There is no workaround. [CSCp54593]
%SSI802-3-FATAL_ERROR: SSI_ASSERT failure in ./cta802/dlu.c Fatal error (09).
[CSCdm22660]
The workaround is to specify XTX=7 on the route.nlm. [CSCdp09295]
%CIP2-3-MSG: slot0 %SSI802-3-FATAL_ERROR: SSI_ASSERT failure in ../cta802/ciptask.c @ 322 - !mxcb->mx_next
%CIP2-0-MSG: slot0 %DEBUGGER-0-FATAL_ERROR: Fatal error (code=09)
The assertion is intended to detect messages with 15 or more memory buffers (mbufs). There is no workaround. [CSCdp13245]
The workaround is to avoid creating idle subchannel conditions by not using the Z NET cancel command. Other possible workarounds include shutting down the router channel interface or removing the CSNA configuration statement before issuing the Z NET cancel command. [CSCdp31175]
The workaround is to add an additional 3 LUs to the VTAM switched major node, leaving the print server to request only 10 TNET connections. [CSCdp43253]

Caveats for Version 26.10/Version 26.11 Modifications

This section describes possible unexpected behavior by Version 26.10. All the caveats listed in this section are resolved in Version 26.11. See Table 7 for the Cisco IOS software release that corresponds to the 26.11 microcode version.

This problem occurs in CMCC microcode releases cip22-35, cip24-10, cip25-10, cip26-5, xcpa 26-5, cip27-0, xcpa27-0, and later.
The workaround is to perform the shutdown procedure when there is no activity on the TN3270 sessions. [CSCdm35562]
bad error-code 12 given
This valid error code indicates a missing TERMSELF response. The code to log and format this specific error into a console message is missing.
There is no workaround. [CSCdm55961]
The workaround is to upgrade the CMCC microcode or to restart the external communication adapter (XCA) nodes. [CSCdm88239]
%TN3270S-1-NO_BIND_REQ_RCVD: No BIND REQ received on LU [chars].[dec], 120*ONESEC
This error and several others are logged as priority 1 (alert) messages in error reports. The priority level of the following error messages is now priority level 3:
NO_PSID_RSP_RCVD
NO_NTFY_AV_RSP_RCVD
NO_BIND_REQ_RCVD
NO_SDT_REQ_RCVD
NO_SDT_TMARK_RCVD
NO_UNBIND_TMARK_RCVD
NO_NTFY_UA_RSP_RCVD
NO_DYN_ACTLU_REQ_RCVD
NO_UNBIND_RSP_RCVD 
NO_TERMSELF_RSP_RCVD
[CSCdm94788]
The workaround is to specify XTX=7 on the route.nlm. [CSCdp09295]
There is no workaround. [CSCdp24670]
The workaround is to avoid creating idle subchannel conditions by not using the Z NET cancel command. Other possible workarounds include shutting down the router channel interface or removing the CSNA configuration statement before issuing the Z NET cancel command. [CSCdp31175]
The workaround is to stop and restart the CLAW driver causing the CLAW control link to synchronize again. [CSCdp32675]
The workaround is to code the LUGROUP parameter with one of the following values: SSCPFM=USS3270 or SSCPFM=USS3270. [CSCdp46564]
There is no workaround. [CSCdp47885]

Caveats for Version 26.9/Version 26.10 Modifications

This section describes possible unexpected behavior by Version 26.9. All the caveats listed in this section are resolved in Version 26.10. See Table 7 for the Cisco IOS software release that corresponds to the 26.10 microcode version.

The CMCC TN3270 Server does not use this client IP address for matching on LU nailing statements in the configuration. [CSCdj44584]
The workaround is to make sure that the RMAC TN3270 server PU resides on the same CMCC adapter as the TN3270 Server. [CSCdm01837]
The workaround is to configure the maximum LLC or threshold to equal the number of XCA lines configured. [CSCdm29597]
This problem occurs in CMCC microcode releases cip22-35, cip24-10, cip25-10, cip26-5, xcpa 26-5, cip27-0, xcpa27-0, and later.
The workaround is to perform the shutdown procedure when there is no activity on the TN3270 sessions. [CSCdm35562]
The workaround is to remove the PATH statements. [CSCdm42103]
The workaround is to reload the microcode. [CSCdm44279]
The workaround is to not disconnect a client during the logon process; that is, after requesting an application from the SSCP screen, but before establishing the LU-LU session with that application. [CSCdm51110]
A workaround is available. Contact the Cisco TN3270 Server development engineers for the interim fix. [CSCdm61159]
This fix adds a debug message to the log and marks the ACTLU as not processed.
There is no workaround. [CSCdm69186]
This problem occurs when the TN3270 server DLUR component improperly saves RU chain bits from the original request to create a response message. This generates the +RSP sense data 400B0000.
The workaround is to increase the RU sizes on the DLUR/DLUS sessions. To increase the RU sizes on the DLUR/DLUS sessions, the user must do the following:
The workaround is to space out the TCP/IP requests. [CSCdm75120]
%CIP2-3-MSG: slot0 %OFFL-3-NOMEM2: Not enough memory to process socket requests,              0 open, 0 in holddown
The workaround is to increase memory. [CSCdm76552]
%DEBUGGER-0-FATAL_ERROR: Fatal error (code=35)
This error occurs when the TN3270 Server is shut down while traffic is still transmitting. [CSCdm78261]
There is no workaround. [CSCdm82521]
The workaround is to delay the shutdown for 20 ms after the last send() message. [CSCdm85311]
The workaround is to set the RU size so that it is at least as big as the MTU on the file transfer path. [CSCdm86734]
There is no workaround. [CSCdm88195]
The workaround is to not perform the shutdown-writing. [CSCdm92713]
The workaround is to use buffers that are 2000 bytes or less or non-structured fields (presentation space transfer. To enable the fix in CMCC releases cip27-4 and greater and xcpa27-4 and greater, you must configure the TN3270 tn-parameter code codevalue command with a code value of 7. [CSCdm93990]
There is no workaround. [CSCdp00921]
There is no workaround. [CSCdp08103]

Caveats for Version 26.8/Version 26.9 Modifications

This section describes possible unexpected behavior by Version 26.7. All the caveats listed in this section are resolved in Version 26.8. See Table 7 for the Cisco IOS software release that corresponds to the 26.8 microcode version.

The workaround is to reload the CMCC microcode. [CSCdj08904]
VTAM version 4.3 introduced restrictions for the PORT TIMER value. The TIMER value cannot be less than the CMCC's T1 * N2. VTAM uses a hard-coded N2 value of 2. Before this fix, the CMCC reported a T1 value of 10. The VTAM documentation indicates that the T1 value is measured in tenths of a second. Therefore, a T1 value of 10 should equal 1 second. However, VTAM interprets the T1 value in seconds so a T1 value of 10 equals 10 seconds, not 1 second. VTAM then multiplies the value by 2 to get a minimum TIMER value of 20 seconds.
The CMCC's reported T1 value is not the CMCC LLC T1 value. Because VTAM overloads the use of the PORT TIMER, do not adjust the CMCC's real LLC T1 value to alter the PORT TIMER. These adjustments can cause severe LLC2 problems.
VTAM overloads the use of PORT TIMER. TIMER is used to set TEST request interval on connect outs. After each TEST request is sent, VTAM sets a timer equal to the PORT TIMER number of seconds and waits for a TEST response. If the TEST response is not received by VTAM before the timer expires, the next TEST request is sent. In CMCC scenarios, the first TEST request is a TEST local, the second is a spanning-route explorer.
For the CMCC, most VTAM initiated LLC connections will not complete before the PORT TIMER seconds expire because the local TEST does not leave the CMCC's internal LAN. LLC connection setup requires a minimum of 20 seconds. VTAM will timeout on LSA commands if a response is not received within the set PORT TIMER value. For example, when VTAM sends a CONNECT request the CONNECT CONFIRM must be received before the PORT TIMER expires. The SABME and UA must be exchanged within the value set in PORT TIMER. If the SABME must be retried, the PORT ITMER might expire before the CONNECT CONFIRM is returned to VTAM.
The workaround is to set the PORT TIMER value to 20 seconds or more unless the user is confident that the LSA commands will not timeout. [CSCdj45782]
A window exists for brief TCP connections when a connection is made with TCP/IP on the CMCC and then broken (FIN received) before Offload has received and processed an Accept socket request from the host. In this situation, Offload misses the notification from TCP/IP that the connection had been terminated.
There is no workaround. [CSCdk12291]
INOP STATUS
The workaround is to reactivate the external communication adapter (XCA) major node. [CSCdk36329]
If a prior connection to the MDH from the server does not exist, it might take several attempts to make a connection. Once the initial connection is made, all subsequent connections will work.
Note IBM VTAM has opened an APAR for the 8002 sense portion of this problem. Users must get the APAR PTF from IBM to get MDH to work with the virtual routing node on the CMCC.
[CSCdk37107]
There is no workaround.
A new channel interface configuration command which is valid only for the CPA, state-tracks-signal, fixes this problem. This command directs the CPA's channel interface state to follow the physical signal value when the interface is in the no shut state. [CSCdk44052]
The workaround is to shut down and restart the PU or to cycle the PU in VTAM. [CSCdk57112]
The workaround is to restart the session. [CSCdk57453]
The workaround is to deactivate the LU or the owning PU in VTAM. [CSCdk60263]
There is no workaround. [CSCdk83774]
%CIP2-1-MSG: slot1 %TN3270S-1-RP_PU_CONFLICT:RP & CIP hold conflicting PU    name(xxxxxxxx) or index(92)
Where "xxxxxxxx" is the PU name.
%CBUS-3-CIPCFGFAIL: Channel1/2: configuration command TN3270S_DLUR_PU_NEW cmd 18    failed
%CIP2-0-MSG: slot1 %DEBUGGER-0-FATAL_ERROR: Fatal error (code=32)
The workaround is to perform the shutdown when the server load is light. [CSCdk83807]
Other SYSREQ key errors that occur when the TN3270 server is configured include:
The workaround is to not use the SYSREQ key. [CSCdk83960]
The workaround is to issue the shut command only after the client traffic terminates. [CSCdk87658]
There is no workaround. [CSCdk89383]
There is no workaround. [CSCdk91964]
A workaround is to distribute the traffic to multiple boxes to avoid a channel capacity of 95 percent or greater. [CSCdk92004]
This problem does not occur when using select() under VM or MVS because select() is issued for one socket at a time. This problem occurs when using TPF if the select() request contains 28 or more socket descriptors.
There is no workaround for this problem. This DDTS is a continuation of CSCdk86184. [CSCdm02126]
The workaround is to use DLUR or DDDLU, or to specify the INCLUD0E = YES field on the SWM. [CSCdm13637]
CLAW-6-TOOSMALL: xx byte IP datagram is to small, device x/yyyy/zz
The workaround is to modify the network so that IP fragments do not occur. [CSCdm11522]
The fix limits the number of NOP messages sent to the clients. No configuration is required to enable the fix.
There is no workaround. [CSCdm23252]
The workaround is to upgrade to the recommended CIP microcode version which corresponds to your Cisco IOS software. [CSCdm28629]
The following trace scenario illustrates the problem:
*Apr 26 13:36:24: %CIP: slot0 Out Lu 5.54: len=10,2C003601 00AE4B81 00C8
*Apr 26 13:36:24: %CIP: slot0 Out Lu 5.54: sna-state=8501,lu-flags=0D24D204
*Apr 26 13:36:24: %CIP: slot0 In Lu 5.54: len=10,2C000136 00AECB81 00C8
*Apr 26 13:36:24: %CIP: slot0 In Tnet 212: len=13,00000100 42F7D7F5 11D7F5FF      EF
*Apr 26 13:36:24: slot0 Out Lu 5.54: sna-state=8D01,lu-flags=0D24D204
*Apr 26 13:36:24: %CIP: slot0 Out Lu 5.54: len=1484,2C003601 00AF0381      80F10611 5D611DE8
*Apr 26 13:36:24: %CIP: slot0 Out Lu 5.54: sna-state=8D01,lu-flags=0D24D204
*Apr 26 13:36:24: %CIP: slot0 Out Tnet 212: len=1482,00000200 6C010411      5D611DE8 40404040
*Apr 26 13:36:24: %CIP: slot0 In Tnet 212: len=8,02000000 6C00FFEF
*Apr 26 13:36:24: %CIP: slot0 Out Lu 5.54: sna-state=8509,lu-flags=0B24D204
*Apr 26 13:36:24: %CIP: slot0 In Lu 5.54: len=9,2C000136 00AF8381 00
*Apr 26 13:36:24: %CIP: slot0 In Lu 5.54: len=15,2C000136 00200392 20F7D7F5      11D7F5
*Apr 26 13:36:24: %CIP: slot0 Out Lu 5.54: len=9,2C003601 00B00391 40
There is no workaround. [CSCdm31347]
This problem occurs in CMCC microcode releases cip22-35, cip24-10, cip25-10, cip26-5, xcpa 26-5, cip27-0, xcpa27-0, and later.
The workaround is to perform the shutdown procedure when there is no activity on the TN3270 sessions. [CSCdm35562]
There is no workaround.
To enable the fix in the cip24-13 microcode, the maximum-lu command must be added to the TN3270 Server configuration file. [CSCdm36152]
There is no workaround. [CSCdm37663]
There is no workaround. [CSCdm55234]
The workaround is to close and re-open the server socket by restarting the server application on the host. [CSCdm63283]

Caveats for Version 26.7/Version 26.8 Modifications

This section describes possible unexpected behavior by Version 26.7. All the caveats listed in this section are resolved in Version 26.8. See Table 7 for the Cisco IOS software release that corresponds to the 26.8 microcode version.

The workaround is to upgrade to the recommended CIP microcode version which corresponds to your Cisco IOS software. [CSCdm28629]

Caveats for Version 26.5/Version 26.7 Modifications

This section describes possible unexpected behavior by Version 26.5. All the caveats listed in this section are resolved in Version 26.7. See Table 7 for the Cisco IOS software release that corresponds to the 26.7 microcode version.

%ADAPTER-0-DIAGFAIL: Port 0 failed the PCA Diagnostic Mode 1 diagnostic
%ADAPTER-0-DIAGDATA: Module Call: 0 0 Error ID: 0 F0000000
A workaround is to change the Cisco 7200 series NPE memory to 64 MB or to replace the 32 MB of memory on the PCPA with 16 MB of memory. [CSCdm09617]
The workaround is to increase the maxpiu value, preferably to the default which is 20470 bytes. [CSCdk71668]
The workaround is to limit the number of sockets selected in a single select request to 27 or less. [CSCdk86184]
This problem does not occur when using select() under VM or MVS because select() is issued for a one socket at a time. This problem occurs when using TPF if the select() request contains 28 or more socket descriptors.
There is no workaround for this problem. This DDTS is a continuation of CSCdk86184. [CSCdm02126]

Caveats for Version 26.4/Version 26.5 Modifications

This section describes possible unexpected behavior by Version 26.4. All the caveats listed in this section are resolved in Version 26.5. See Table 7 for the Cisco IOS software release that corresponds to the 26.5 microcode version.

A workaround is to use the CIP core dump feature which is available in Cisco IOS Release 11.2BC and later. This feature saves all CIP memory to a file on an FTP server. The missing LOGDATA can be extracted from the core dump file. This workaround applies only for the CIP. [CSCdj61710]
There is no workaround. [CSCdk27199]
There is no workaround. [CSCdk41469]
interface Channel2/2
no ip address
no keepalive
lan TokenRing 2
  source-bridge 102 1 400
  adapter 2 4000.8001.0102
tg PAN12    llc token-adapter 2  10 rmac 4000.9000.beef
tg PAN2     llc token-adapter 2  10 rmac 4000.8000.beef

The error occurs if PAN2 is in the LocatingRemoteLinkStation state and the local SNA associated with PAN2 is deactivated then reactivated.
Possible workarounds include reconfiguring the router not to use the same local MAC or SAP, or deactivating then reactivating all local SNA nodes associated with that local MAC or SAP. Another workaround is to reload the microcode on the CMCC having the problem. [CSCdk41506]
offload e200 50 80.11.198.2 ciscovm rispix tcpip tcpip tcpip api
Reconfigure the offload statement as follows:
no offload e200 50 80.11.198.2 ciscovm rispix tcpip tcpip tcpip api
offload e100 52 80.11.198.2 ciscovm rispix tcpip tcpip tcpip api
To workaround, after deconfiguring the offload statement, exit the configuration and issue the show extended channel slot/port ip-stack ip address command. When the offload deconfiguration is complete for the indicated offload statement IP address, the output should indicate "...No IP statistics found". At this point the new offload statement using the same IP address can be configured.
The following is an example configuration:
rispix#show ext ch 0/1 ip-stack
IP Statistics for IP Address 80.11.198.2
Forwarding : no DefaultTTL : 64 InReceives : 0
InHdrErrors : 0 InAddrErrors : 0 ForwDatagrams: 0
InUnknownProtos: 0 InDiscards : 0 InDelivers : 0
OutRequests : 0 OutDiscards : 0 OutNoRoutes : 0
ReasmTimeout : 60 ReasmReqds : 0 ReasmOKs : 0
ReasmFails : 0 FragOKs : 0 FragFails : 0
FragCreates : 0 RoutingDiscards: 0

rispix#config t
Enter configuration commands, one per line. End with CNTL/Z.
rispix(config)#in ch 0/1
rispix(config-if)#no offload e200 50
rispix(config-if)#end
rispix#
01:22:25: %SYS-5-CONFIG_I: Configured from console by console
rispix#show ext ch 0/1 ip-stack
...No IP statistics found
[CSCdk45042]
The workaround is to complete the following tasks:

Step 1 Log into the CMCC console: 

if-con <CCMCC Slot> c

Step 2 Display the current state of this RFC: 

ipconf <Offload IP Address> tcp_rfc1323

Step 3 Disable this RFC:

ipconf <Offload IP Address> tcp_rfc1323 off


Step 4	 Verify the configuration change using Step 2. This RFC can be re-enabled, if necessary, using the same command but with the "on" option. 


ipconf <Offload IP Address> tcp_rfc1323 on


Step 5	 Exit the CMCC console:


quit (CIP21-x/CIP204-x releases)
if-quit or ^C^C^C (CIP22-x/CIP205-x and all later releases or XCPA26-x/XCPA214-x and all later releases)

Unlike configuration commands issued from the router console, this CMCC configuration command is not retained if the CMCC or the router reloads or crashes and reloads. [CSCdk57139]





The workaround is to print the job using Type 3 printing or to reconfigure the print application to send the SNA RU chains with DR (definite response) requested. [CSCdk59063]





%PKTS-3-NOSUPP:
 

There is no workaround. [CSCdk67396]




 Caveats for Version 26.2/Version 26.4 Modifications


 This section describes possible unexpected behavior by Version 26.2. All the caveats listed in this section are resolved in Version 26.4. See Table 7 for the Cisco IOS software release that corresponds to the 26.4 microcode version. 



The message is misleading because the host application must sometimes use the host descriptor if it has not been notified of the offload box socket descriptor. This occurs when an error is detected during socket connection establishment. The WRONGDESC error message has been removed. [CSCdj92653]





A window exists for brief TCP connections when a connection is made with TCP/IP on the CMCC and then broken (FIN received) before Offload has received and processed an Accept socket request from the host. In this situation, Offload misses the notification from TCP/IP that the connection had been terminated.


There is no workaround. [CSCdk12291]





Parallel TGs can be used to provide redundancy. [CSCdk15431]





The workaround is that once the DLUR-DLUS pipe is established additional links will be reported if they become active.[CSCdk15446]





A workaround is to close and then reopen the DLUS-DLUR pipe by using the VTAM V NET,INACT,ID=dlurname command. This will not disrupt the LU-LU sessions if the dependent PUs are configured ANS=CONT. New sessions cannot be established while the pipe is down. [CSCdk21067]





There is no workaround. [CSCdk21633]





The workaround is to delay reconnecting for six seconds or to disconnect and reconnect immediately upon noticing the delay. [CSCdk28081]





 Caveats for Version 26.1/Version 26.2 Modifications


 This section describes possible unexpected behavior by Version 26.1. All the caveats listed in this section are resolved in Version 26.2. See Table 7 for the Cisco IOS software release that corresponds to the 26.2 microcode version. 



The workaround is to increase the inbound RU size defined in the host logmode tables. [CSCdj76007]





%CMPCTG-3-LS_FSM_ERR: TG Name: CMPCTG -CnlsLs, Event ITestInd, State SCnlsConnected
%MBUF-0-MFREEx2: mfree: mbuf 845F0160 already free'ed from pc=8015D228 ra=80044040 @(pc=80057F20ra=80044040)




This is a cosmetic problem. There is no workaround. [CSCdj91905]





There is no workaround. [CSCdk00532]





The workaround is to tune the LLC timers to reflect true delays in the network. [CSCdk02032]





bad LU on DISC...




This error is caused by CSCdj81522. The crash may occur if a TN3270E client connects and does not negotiate bind-image.


The workaround is to ensure that all clients support bind-image. [CSCdk02535]





The workaround is to shut and then no shut the TN3270 Server. [CSCdk03985]





The workaround is to reconnect. [CSCdk06887]





%SSI802-3-FATAL_ERROR: SSI_ASSERT failure in ../mpc/mpcxid.C @ 66 - nextCv <= (Cv *) ((byte *) &fmtType + xidLength)
 

The workaround is to fix the component that is generating the corrupted XID3 message. See CSCdk10071. [CSCdk08437]





There is no workaround. [CSCdk08438]





The workaround is to ensure that all PUs are either shutdown or connected. [CSCdk09978]





There is no workaround. [CSCdk10071]





The workaround is to locally clear the keyboard lock, if the client supports such a feature. Otherwise, the user must disconnect and reconnect. [CSCdk10200]





There is no workaround. [CSCdk11113]





The workaround is to recycle the LU in VTAM and restart the session.[CSCdk11361]





The workaround is to reduce the number of LLC links available to DLUR until the DLUR-DLUS pipe is established. [CSCdk11790]





There is no workaround. [CSCdk14244]





SSI802-3-FATAL_ERROR: SSI_ASSERT failure in ../cta/cta.c @ 350 - FALSE




There is no workaround. The user must cycle the XCA node. [CSCdk14424]




 Caveats for Version 26.0/Version 26.1 Modifications


 This section describes possible unexpected behavior by Version 26.0. All the caveats listed in this section are resolved in Version 26.1. See Table 7 for the Cisco IOS software release that corresponds to the 26.1 microcode version. 



To confirm that the IP option caused path MTU discovery not to work, get a sniffer trace to show the TCP segments from the CMCC Adapter as well as any ICMPs going back to it. If the router that sends the ICMPs is the CMCC router, collect the output of the following commands before and after a session is dropped:


[CSCdj65774]





The workaround is to artificially limit the rate at which remote stations can connect by adding delays to a startup script. [CSCdj69281]





The workaround for the offload problem is to reconfigure for IP datagram mode. There is no workaround available for the bug in the kernel timeout function. [CSCdj72646]





A workaround is to issue a shut and then a no shut command on the TN3270 server, causing the connections to be brought down quickly. [CSCdj76280] 





%CTA-0-UNEXP_LSI_CMD: PA1 CTA C020-56 received LSI command 0x4D11 at 0x8042CA8C
 

An unrecognized command code was recognized during communication between the LLC2 and CSNA components on the CMCC Adapter. This problem has never been detected in customer use, and has only been seen during the debugging of a new feature. However, the problem could be caused by configuring High Performance Routing (HPR) in a remote device.


The workaround is to reconfigure the remote device to not specify HPR. [CSCdj79403] 





%CIP24-4-MSG: %TN3270S-4-NO_LU_SESSIONS: No LU sessions left for PUs at IP addr a.b.c.d, port x
 

The problem may occur when the maximum-lu limit has been reached or when no more LUs are available at a given TN3270 server listening point. 


The workaround is to increase the maximum-lu limit to a level that will not be reached during operation of the server. Also, the user should increase the number of PUs (really LUs) on each listening point. [CSCdj80602]





There is no workaround. [CSCdj80990]





The problem occurs only with certain clients (for example, PC3270 and Attachmate) and when the user enters data before the host application sends out its first screen (most applications send a screen of data immediately after the bind, start data traffic).


Because the problem only occurs in TN3270E mode, and some clients have an option to disable TN3270E mode, it is possible to bypass this problem in situations where TN3270E mode is not required. The alternatives are to use a different client or change the host application. [CSCdj84064]





"unsupported function".
 

This problem occurs if the same LU can be used by TN3270 and TN3270E clients.


The workaround is to retry the logon request. [CSCdj84122]





The workaround is to not configure preferred-NNserver. [CSCdj87854]





There is no workaround. [CSCdj88636]





There is no workaround. [CSCdj90734]





There is no workaround. [CSCdj90738]





The workaround is to not use the show lu history command. [CSCdj91756]





The workaround is to increase the maximum-lu in the configuration so that the maximum-lu will not be reached. [CSCdj92158]





There is no workaround. [CSCdj93915]





The workaround is to make sure the TG statement is configured before the associated CMCC statements. [CSCdk01922]





The workaround is to tune the LLC timers to reflect true delays in the network. [CSCdk02032]





bad LU on DISC...




This error is caused by CSCdj81522. The crash may occur if a TN3270E client connects and does not negotiate bind-image.


The workaround is to ensure that all clients support bind-image. [CSCdk02535]





The workaround is to limit the number of TG statements to 32. The changes incorporated by this DDTS increase the TG limit to 64. [CSCdk03733]





%SSI802-3-FATAL_ERROR: SSI_ASSERT failure in ../mpc/mpcxid.C @ 66 - nextCv <= (Cv *) ((byte *) &fmtType + xidLength)
 

The workaround is to fix the component that is generating the corrupted XID3 message. See CSCdk10071. [CSCdk08437]





There is no workaround. [CSCdk10071]




 CPA Microcode/Cisco IOS Software Compatibility Matrix

 
 Table 7 lists the CPA microcode version and Cisco IOS software compatibility for the Cisco 7200 family. 

Table 7: CPA Microcode Releases and Corresponding Cisco IOS Releases for the Cisco 7200 Family




Default CPA Microcode Version
Cisco IOS Release 11.3T
Cisco IOS Release
12.0
Cisco IOS Release 12.0T
Cisco IOS Release
12.1
Cisco IOS Release 12.1T



 xcpa26-0


 11.3(3) T


 


 


 


 




 xcpa26-1


 11.3(4)T


 


 


 


 




 xcpa26-2


 11.3(5)T, 11.3(6)T


 


 


 


 




 xcpa26-4


 11.3(7)T


 12.0(1), 12.0(2)


 12.0(1)T, 12.0(2)T


 


 




 xcpa26-5


 11.3(8)T


 12.0(3)


 


 


 




 xcpa26-7


 11.3(9)T


 12.0(4)


 


 


 




 xcpa26-8


 11.3(10)T, 11.3(11)T


 12.0(5)


 


 


 




 xcpa26-9


 


 12.0(6), 12.0(7)


 


 


 




 xcpa26-10


 


 12.0(8)


 


 


 




 xcpa26-11


 


 12.0(9)


 


 


 




 xcpa26-12


 


 12.0(10)


 


 


 




 xcpa26-13


 


 12.0(11)


 


 


 




 xcpa26-15


 


 12.0(12)


 


 


 




 xcpa27-0


 


 


 12.0(3)T


 


 




 xcpa27-1


 


 


 12.0(4)T


 


 




 xcpa27-2


 


 


 12.0(5)T


 


 




 xcpa27-4


 


 


 12.0(7)T


 


 




 xcpa27-6


 


 


 


 12.1(1)


 12.1(1)T




 xcpa27-7


 


 


 


 12.1(2)


 12.1(2)T




 xcpa27-8


 


 


 


 12.1(3)


 12.1(3)T














Caution   
With microcode levels prior to xcpa26-7, the PCPA will fail adapter diagnostics when the PCPA has 32 MB of memory and is installed in a Cisco 7200 series router that has a Network Processing Engine (NPE) with 128 MB of memory. Possible workarounds include upgrading to microcode versions xcpa26-7, or changing the Cisco 7200 series NPE memory to 64 MB or replacing the 32 MB of memory on the PCPA with 16 MB of memory.


 CPA-Related Caveats for Cisco IOS Releases

 
 For a complete list of caveats against the Cisco IOS Releases, use Cisco Documentation CD-ROM or access Cisco Connection Online as described in the section "Cisco Connection Online" later in this document. You can also refer to the following publications, which are available on Cisco Connection Documentation:



 CPA and Processor Module ROM Monitor Recommendations

 
 CPA and Cisco 7200 series ROM monitor (system bootstrap) versions and system software images are typically independent of each other; however, the CPA hardware version does have minimum requirements in terms of Cisco IOS release and CPA microcode version as listed in Table 8. Other microcode versions can be used, but only when specifically instructed to do so by technical support personnel. Table 9 identifies the processor module monitor versions.


 Use the show diag EXEC command to display the CPA hardware version. The CPA card is identified as version 1.0. 

Table 8: CPA Hardware, Cisco IOS Release, and CPA Microcode Compatibility




CPA Hardware Version
Minimum Cisco IOS Release Required
Minimum CPA Microcode Version Recommended 



 ESCON Channel Port Adapter


 11.3(3)T


 xcpa26.0




 


 12.0(1)


 xcpa26.4




 


 12.0(1)T


 xcpa26.4




 Parallel Channel Port Adapter


 11.3(9)T


 xcpa26.7




 


 12.0(4)


 xcpa26.7




 


 12.0(3)T


 xcpa27.0




 


 12.1(1)


 xcpa27.6




 


 12.1(1)T


 xcpa27.6















Table 9: Minimum Recommended CPA Boot ROM Versions 



Platform and Processor
Processor ROM Monitor Version



 Cisco 7200 router


 System Bootstrap Version 11.1 CA or later











 

 CPA and Cisco 7200 DRAM Requirements

 
 For the Cisco routers to take advantage of the Cisco IOS release CPA features, you might need to upgrade code, main system, or CPA memory. For specific Cisco IOS-related memory requirements, refer to the Release Notes for Cisco 7000 Family for Cisco IOS Release 11.3T, the Release Notes for Cisco IOS Release 12.0(x), the Release Notes for Cisco IOS Release 12.0(x)T, the Release Notes for Cisco IOS Release 12.1(x), or the Release Notes for Cisco IOS Release 12.1(x)T publication which is available on Cisco Connection Online.


 CPA Microcode Upgrade Overview

 
 To upgrade CPA microcode, complete the following steps.



Note You must be running Cisco IOS Release 11.3(3)T or later to complete the following steps. 



Caution   
With microcode levels prior to xcpa26-7, the PCPA will fail adapter diagnostics when the PCPA has 32 MB of memory and is installed in a Cisco 7200 series router that has a Network Processing Engine (NPE) with 128 MB of memory. Possible workarounds include upgrading to microcode versions xcpa26-7, or changing the Cisco 7200 series NPE memory to 64 MB or replacing the 32 MB of memory on the PCPA with 16 MB of memory.


 Upgrading from CCO


 To upgrade to CPA microcode images obtained from CCO, do the following:



Step 1	 Download the CPA microcode image from CCO to a TFTP server.



Step 2	 Remove any configuration commands that specify a CPA microcode image from the running configuration.



Step 3	 Copy the CPA microcode image to the Flash memory card in slot 0 or slot 1. 



Step 4	 Reconfigure the router, as necessary, to use the CPA microcode image stored in the Flash memory card in slot 0 or slot 1. 



Step 5	 Save your running configuration to a TFTP server or Flash memory. 



Step 6	 Perform a microcode reload. 


 For more detailed information on upgrading the CPA microcode image, refer to the PA-1C-E ESCON Channel Port Adapter Installation and Configuration note and the PA-1C-P Parallel Channel Port Adapter Installation and Configuration note.


 Cisco Connection Online

 
 Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.


 Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.


 CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.


 You can access CCO in the following ways:



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



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



 Documentation CD-ROM

 
 Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com,  http://www-china.cisco.com,  or http://www-europe.cisco.com.
  

 If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.


  



 





hometocprevnextglossaryfeedbacksearchhelp


Posted: Mon Jul 24 10:16:00 PDT 2000

Copyright 1989-2000©Cisco Systems Inc.