Guest

Cisco IOS Software Releases 11.0

Field Notice - CIP Microcode Defect for Offload Feature: CIP Fatal Error 35 CIP buffer corruption when hitting IBM mainframe APAR PQ02051 [CSCdj30387]


August 15, 1997



Microcode Affected

The following CIP Microcode is affected when used with the Offload feature:

  • cip(p)21-17, Cisco IOS 11.0(16.1)

  • cip(p)21-18, Cisco IOS 11.0(16.2), 11.0(16.3)

  • cip22-21 for Cisco IOS 11.0BT, 11.1 and 11.2

  • cip22-22 for Cisco IOS 11.0BT, 11.1 and 11.2.

Hardware Affected

The following hardware is affected when used in conjunction with the CIP Microcode mentioned above and the IP Offload feature:

  • cx-cip-pca1, cx-cip-pca2

  • cx-cip-eca1, cx-cip-eca2

  • cx-cip-ecap1

  • cx-cip2-pca1, cx-cip2-pca2

  • cx-cip2-eca1, cx-cip2-eca2

  • cx-cip2-ecap1

Problem Description [CSCdj30387]

The CIP resets with a "fatal error code=35" because the global queue of 4KB buffers contains 0x00010001 instead of a valid address.

The following fatal error message is displayed:

%DEBUGGER-0-STACK_DATA8: 0000 FFFFFFFF 803F0010 00000000 00010001 ...

The second doubleword "00000000 00010001" indicates that this bug caused the CIP reset. Apart from "0x00010001," there are other arbitrary values that may be seen, but due to the nature of the problem, they are much less likely.

Background

This bug occurs when IBM mainframe APAR PQ02051 is encountered. Because APAR PQ02051 is difficult to detect, it is important to follow the solution recommended below in this field notice.

Workaround/Solution

Do not run cip(p)21-17, cip(p)21-18, cip22-21 or cip22-22 microcode for the CIP IP Offload feature. Use the following interim code levels for the CIP IP Offload features until the CIP microcode maintenance cip21-19 and cip22-23 are available in September 1997:

  • cip204-170 for Cisco IOS 11.0

  • cip206-221 for Cisco IOS 11.0BT, 11.1 and 11.2

All other CIP features (IP datagram, CSNA, TN3270 server) are not affected by this software bug.

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods: