cc/td/doc/product/software/ios121/121relnt
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Channel Interface Processor Microcode Release Note and Microcode Upgrade Requirements

Channel Interface Processor Microcode Release Note and Microcode Upgrade Requirements

July 24, 2000

This document contains the release notes for the unbundled CIP microcode software. Prior to Cisco IOS Release 11.1, CIP microcode was provided as part of the Cisco IOS software "bundle". In Cisco IOS Release 11.1 and later, the CIP microcode was unbundled from the Cisco IOS software. The CIP microcode is available as a separately loadable software module and you match the version of the CIP microcode to the Cisco IOS software release.

Refer to the "CIP Microcode and CIP Hardware Compatibility" section for a list of CIP microcode releases described by this document.

Caution If you are upgrading from a previous Cisco IOS release, a special microcode installation procedure is required or your CIP will not operate properly. For details, refer to the section "CIP Microcode Upgrade Overview."

Introduction

This CIP microcode release note describes the CIP microcode modifications and caveats for the latest versions of CIP microcode. It includes all CIP microcode releases described in the section "CIP Microcode and CIP Hardware Compatibility." Also included is an overview of the procedures required to upgrade to the latest version of CIP microcode depending on the CIP-compatible router platform you have.

This CIP microcode release note discusses the following topics:

Cisco IOS Software and Cisco 7000 Family Hardware Documentation

For documentation of CIP features in the Cisco IOS 11.1 Release, refer to Table 1.


Table 1: Cisco IOS Release 11.1 Publications
Cisco IOS Release 11.1 Publication Customer Order Number

Configuration Fundamentals Configuration Guide

DOC-CFCG11.1=

Configuration Fundamentals Command Reference

DOC-CFCR11.1=

Bridging and IBM Networking Configuration Guide

DOC-IBMNCG11.1=

Bridging and IBM Networking Command Reference

DOC-IBMNCR11.1=

Cisco IOS Software Command Summary

DOC-CIOSCS11.1=

System Error Messages

DOC-SYSEM11.1=

Release Notes for Cisco IOS Release 11.1

78-2886-xx

For documentation of CIP features in the Cisco IOS 11.2 Release, refer to Table 2.


Table 2: Cisco IOS Release 11.2 Publications
Cisco IOS Release 11.2 Publication Customer Order Number

Configuration Fundamentals Configuration Guide

DOC-CFCG11.2=

Configuration Fundamentals Command Reference

DOC-CFCR11.2=

Bridging and IBM Networking Configuration Guide

DOC-IBMNCG11.2=

Bridging and IBM Networking Command Reference

DOC-IBMNCR11.2=

Cisco IOS Software Command Summary

DOC-CIOSCS11.2=

System Error Messages

DOC-SYSEM11.2=

Release Notes for Cisco IOS Release 11.2

78-3648-xx

For documentation of CIP features in the Cisco IOS Release 11.2BC, refer to Table 3.


Table 3: Cisco IOS Release 11.2BC Publications
Cisco IOS Release 11.2BC Publication Customer Order Number

Release Notes for Cisco IOS Release 11.2

78-3648-xx

Release Notes for Cisco IOS Release 11.2BC

78-4694-xx

Feature Guide for Cisco IOS Release 11.2BC

78-4693-xx

For documentation of CIP features in the Cisco IOS Release 11.3, refer to Table 4.


Table 4: Cisco IOS Release 11.3 Publications
Cisco IOS 11.3 Release Publication Customer Order 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 CIP features in the Cisco IOS Release 11.3T, refer to Table 5.


Table 5: 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 CIP features in the Cisco IOS Release 12.0, refer to Table 6.


Table 6: Cisco IOS Release 12.0 Publications
Cisco IOS Release 12.0 Publication Customer Order 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 CIP features in the Cisco IOS Release 12.0T, refer to Table 7.


Table 7: 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 CIP features in Cisco IOS Release 12.1, refer to Table 8.


Table 8:
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

Cisco IOS Release 12.1 Publications

For documentation of CIP features in Cisco IOS Release 12.1T, refer to Table 9.


Table 9:
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 chassis-specific hardware configuration or troubleshooting information, refer to the following publications:

These hardware publications are available on Cisco Connection Online (CCO) in the Core/High-End Routers database.

How Does CIP Microcode Ship?

For the Cisco 7000 family routers (Cisco 7000 series routers and Cisco 7500 series), CIP microcode is available on Flash memory cards (which also include the Cisco IOS release compatible with the microcode version) and via CCO.

Starting with Cisco IOS Release 11.1, CIP microcode images are shipped separately from the Cisco IOS software. For Cisco 7000 family routers shipped with Cisco Release IOS 11.1 and later, the CIP microcode is shipped pre-installed on the Flash memory card. For Cisco IOS Release 11.1, 11.2, 11.2BC, 11.3, 11.3T, 12.0, 12.0T, 12.1, and 12.1T software upgrades, the CIP microcode is shipped or available on the following media:

CIP Microcode and CIP Hardware Compatibility

In Cisco IOS Release 11.1(5) and later, two versions of the CIP card are supported. The initial CIP card is no longer produced. The CIP2 card replaces the CIP.

There are no microcode issues associated with this change. The Route Switch Processor (RSP) card in the Cisco 7000 family router automatically determines which version of the microcode is appropriate for the installed CIP or CIP2.

Cisco IOS Release 11.1(5) and CIP microcode Version 22.6 and Cisco IOS Release 11.2(2) and CIP microcode Version 22.7 support both a CIP and a CIP2 card in the same router. Prior to this release, different versions of a CIP card in the same router are not supported.

CIP Microcode/Cisco IOS Software Compatibility Matrix

Table 10 lists CIP microcode version and Cisco IOS software compatibility for the Cisco 7000 family. The CIP microcode image is shipped in a bundle separate from the Cisco IOS software images.

Note Starting with Cisco IOS Releases 10.3(9) and 11.0(5), the Cisco 7000 series routers and the Cisco 7500 series routers use the same CIP microcode image. The first version of integrated CIP microcode in Cisco IOS Release 10.3 is cip20-5, in Cisco IOS Release 11.0 it is cip21-3. Cisco IOS Release 11.1 and later use the integrated CIP microcode rather than a separate microcode version for each chassis and processor type.


Table 10: Unbundled CIP Microcode Releases and Corresponding Cisco IOS Releases for the Cisco 7000 Family
Default CIP Microcode Version Cisco IOS Release 11.1 Cisco IOS Release 11.2 Cisco IOS Release 11.2 BC Cisco IOS Release 11.3 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

21-3

11.1(1)

22-0

11.1(1)

22-3

11.1(3)

22-6

11.1(5)

22-7

11.1(6)

22-10

11.1(7)

11.2(1), 11.2(2)

22-12

11.1(8)

11.2(3), 11.2(4)

22-14

11.1(9)

22-15

11.1(10)

22-17

11.2(5)

22-18

11.1(11)

22-19

11.2(6)

22-20

11.1 (12)

11.2(7)

22-21

11.1 (13)

11.2(8)

22-22

11.1(14)

11.2(9)

22-23

11.1(15)

22-25

11.1(16)

11.2(10)

22-26

11.1(17)

11.2(11)

22-27

11.1(18)

11.2(12), 11.2(13)

22-30

11.1(20)

11.2(14)

22-31

11.2(15)

22-32

11.1(22)

11.2(16)

22-34

11.1(24)

11.2(17)

22-35

11.2(18)

22-38

11.2(19)

22-39

11.2(20)

22-40

11.2(21)

22-41

11.2(22)

22-43

11.2(23)

22-45

11.2(24)

22-46

11.2(25)

24-0

11.2(8) BC

24-1

11.2(9) BC

24-2

11.2(10) BC

24-3

11.2(11) BC

24-4

11.2(12) BC

24-5

11.2(13) BC

24-6

11.2(14) BC

24-7

11.2(15) BC

24-8

11.2(16) BC

24-9

11.2(17) BC

24-11

11.2(18) BC

24-13

11.2(19) BC

24-14

11.2(20) BC

24-15

11.2(21) BC

24-16

11.2(22) BC

24-18

11.2(23) BC

25-3

11.3(1)

25-6

11.3(2)

25-7

11.3(3), 11.3(4)

25-8

11.3(5), 11.3(6)

25-9

11.3(7)

25-10

11.3(8)

25-11

11.3(9)

25-12

11.3(10)

25-13

11.3(11)

26-0

11.3(3)T

26-1

11.3(4)T

26-2

11.3(5)T, 11.3(6)T,

26-4

11.3(7)T

12.0(1), 12.0(2)

12.0(1)T, 12.0(2)T

26-5

11.3(8)T

12.0(3)

26-7

11.3(9)T

12.0(4)

26-8

11.3(10)T, 11.3(11)T

12.0(5)

26-9

12.0(6), 12.0(7)

26-10

12.0(8)

26-11

12.0(9)

26-12

12.0(10)

26-13

12.0(11)

26-15

12.0(12)

26-16

12.0(13)

26-17

12.0(14)

26-18

12.0(15)

26-20

12.0(16)

27-0

12.0(3)T

27-1

12.0(4)T

27-2

12.0(5)T

27-4

12.0(7)T

27-6

12.1(1)

12.1(1)T

27-7

12.1(2)

12.1(2)T

27-8

12.1(3)

12.1(3)T

27-9

12.1(4)

27-11

12.1(6)

27-13

12.1(7)

28-1

12.1(5)T

Note For Cisco IOS Release 11.2BC, the CIP card is supported only on the Cisco 7000 with RSP7000 and the Cisco 7500 series routers.

CIP Microcode Release cip27 Caveats and Modifications

The following section describes the caveats to current CIP microcode versions and the modifications made in current CIP microcode versions for cip27 microcode. The caveats listed apply to only the most serious problems. See Table 10 for the Cisco IOS software releases supported by cip27 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 10 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. [CSCdr33661]
  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 10 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 10 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 that is 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 10 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]
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. [CSCdp58083]
  There is no workaround. [CSCdp69064]
*Jan 18 00:56:35: %OIR-6-REMCARD: Card removed from slot 1, interfaces disabled
*Jan 18 00:56:40: %CIP2-6-MSG: slot5 %SYSMGT_RPC-6-STATE_CHANGE: System 
Management activated
*Jan 18 00:56:47: %CIP2-3-MSG: slot5 %LOVE-3-LOVELETTER: Error in love 
letter processing for port 0(0)
  There is no workaround. [CSCdp75240]
  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 10 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 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 10 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.2. All the caveats listed in this section are resolved in Version 27.3. See Table 10 for the Cisco IOS software release that corresponds to the 27.3 microcode version.

  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 10 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]
  The workaround is to not OIR IP cards in a Cisco 7500 series router when the CIP is running. [CSCdj90287]
  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]
  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]