|
|
The following Channel Interface Processor (CIP) error messages are related to the offload protocol.
Error Message
%OFFL-6-ALIASNOTFOUND: Attempt to delete non-existing alias.Explanation The specified alias does not exist on the offload device.
Recommended Action Make sure that the offload device has the alias you are trying to delete. If it does, then capture the output of the show tech-support command and the error messages, and report them to your Cisco technical representative.
Error Message
%OFFL-4-BADDESC: Socket descriptor [dec] in request is bad: state [chars] compare [dec]Explanation The host sent a socket request with a socket descriptor that is invalid. The Cisco Mainframe Channel Connection (CMCC) has sent an error response to this socket request. This could be a host error or a CMCC internal logic error.
Recommended Action This message is followed by a hex dump of the request. Copy the error messages exactly as they appear, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-0-BADSCB: Unknown SCB type [dec]Explanation An internal logic error has occurred. An attempt was made to free a buffer with an unknown type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%OFFL-3-BADSEQ: Socket request [chars] should be last in sequenceExplanation The host sent a socket request that should be the last in a sequence but is not. This error is caused either by an internal logic error or by an incompatibility between the offload code on the mainframe and the offload code on the Cisco Mainframe Channel Connection (CMCC).
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%OFFL-6-COMMAND: Unrecognized offload command code [dec]Explanation The host sent an offload command with an invalid offload command code. The Cisco Mainframe Channel Connection (CMCC) ignored the request.
Recommended Action Check if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command output, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-6-DUPALIAS: Alias already exists on the offload device.Explanation The offload device already has the specified alias.
Recommended Action Enter the write terminal command to verify that the alias exists. If it does not, capture the output of the show tech-support command and all error messages, and report them to your Cisco technical representative.
Error Message
%OFFL-7-HEX16B: [hex]: [hex][hex][hex][hex] [hex][hex][hex][hex] [hex][hex][hex][hex] [hex][hex][hex][hex] [chars]Explanation This message contains a hex dump of data associated with the immediately preceding error message.
Recommended Action Refer to the description of the immediately preceding Cisco Mainframe Channel Connection (CMCC) error message for the recommended action.
Error Message
%OFFL-7-HEX4W: [hex]: [hex] [hex] [hex] [hex] [chars]Explanation This message contains a hex dump of data associated with the immediately preceding error message.
Recommended Action Refer to the description of the immediately preceding Cisco Mainframe Channel Connection (CMCC) error message for the recommended action.
Error Message
%OFFL-3-ILLALD: Illegal data alignment: 0x[hex] + [dec] bytes = 0x[hex]. xfer_element = 0x[hex]Explanation An internal logic error has occurred. The data following an offload message header crossed a buffer boundary. The Cisco Mainframe Channel Connection (CMCC) ignored the message. This error message is usually an indication that the CMCC has received bad data. Examples of this are Common Link Access to Workstation (CLAW) frames that are duplicated or arrive out of order. The offload messages contained in these corrupted CLAW frames are ignored, and this action can lead to hanging sessions or session loss.
Recommended Action Check if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-3-ILLALH: Illegal hdr alignment detected. Address 0x[hex] + [dec] bytes 0x[hex]. xfer_element = 0x[hex]Explanation An internal logic error has occurred. An offload message header crossed a buffer boundary. The Cisco Mainframe Channel Connection (CMCC) ignored the message. This error message is usually an indication that the CMCC has received bad data. Examples of this are Common Link Access to Workstation (CLAW) frames that are duplicated or arrive out of order. The offload messages contained in these corrupted Common Link Access to Workstation (CLAW) frames are ignored, and this action can lead to hanging sessions or session loss.
Recommended Action Check if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-3-ILLEN: Illegal byte count in offload data. [dec] specified, [dec] available. xfer_element = 0x[hex]Explanation The buffer length field in the offload message header does not equal the size of the data buffer. This condition typically means that the mainframe has sent bad data to the offload device. Examples of this are Common Link Access to Workstation (CLAW) frames that are duplicated or arrive out of order. The offload messages contained in these corrupted CLAW frames are ignored, and this action can lead to hanging sessions or session loss.
Recommended Action Check if there were any special events that coincided with this error message, like an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-0-ILLFREE1: SCB chain does not end with a read hdrExplanation An internal logic error has occurred. An attempt was made to free an incomplete sequence of buffers.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the error messages, issue the show tech-support command, and provide the information to your Cisco technical service representative.
Error Message
%OFFL-0-ILLFREE2: SCB ends with a read hdr with the MTC bit setExplanation An internal logic error has occurred. An attempt was made to free an incomplete sequence of buffers.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the error messages, issue the show tech-support command, and provide the information to your Cisco technical service representative.
Error Message
%OFFL-3-ILLNUM: Illegal number of socket requests. Rejected at [dec]Explanation The Cisco Mainframe Channel Connection (CMCC), received a Common Link Access to Workstation (CLAW) frame with too many offload messages. This typically means that the mainframe has sent bad data to the offload device. Examples of this are CLAW frames that are duplicated or arrive out of order. The offload messages contained in these corrupted CLAW frames are ignored, and this action can lead to hanging sessions or session loss.
Recommended Action Check if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-3-ILLRST: Received restart with [dec] intf, [dec] is max. xfer_element = 0x[hex]Explanation The host has sent an offload restart request with too many defined interfaces.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has ignored the request. Check your host configuration for this offload device. If you cannot find the problem, copy the error message exactly as it appears and call your Cisco technical service representative.
Error Message
%OFFL-6-LONGREC: Attempt to transmit too large a recordExplanation The amount of data being read by the channel exceeded the size of the read channel command word. The Cisco Mainframe Channel Connection (CMCC) freed the buffers associated with this read operation and continued.
Recommended Action This error message typically means that the host code and the CMCC code were out of synchrony on the read subchannel. Sometimes the condition corrects itself, but most of the time the subchannel has to be restarted, either by varying the device offline on the host or by unconfiguring and reconfiguring the affected offload device.
Error Message
%OFFL-3-MISRST: Received restart [chars] with unknown IP [dec].[dec].[dec].[dec]Explanation The host has sent an offload restart request with an unknown IP address for the Application Programming Interface (API) link. The Cisco Mainframe Channel Connection (CMCC) has ignored the mismatch.
Recommended Action Look for the DEVICE statement for the correct offload device in your TCPIP PROFILE. Check the IP address on the LINK statement for the API link and compare that address with the IP address configured on your CMCC's offload configuration command. Correct your configuration so the two IP addresses match.
Error Message
%OFFL-0-NOMBUF: Out of mbuf's for handling socket operationsExplanation An internal logic error has occurred. Not enough memory buffers were allocated to handle the current offload socket operation.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the error messages, issue the show tech-support command, and provide the information to your Cisco technical service representative.
Error Message
%OFFL-3-NOMEM: Not enough memory to start offload tasksExplanation Not enough free memory is available to start the TCP/IP offload tasks. The configuration request was ignored.
Recommended Action Install more memory for the Cisco Mainframe Channel Connection (CMCC), or configure fewer devices.
Error Message
%OFFL-3-NOMEMSOCK: Not enough memory to process socket requests, [dec] open, [dec] in holddown, MSGDEF_LIMIT_SLOWExplanation Not enough free memory is available to process a socket request. The socket request failed.
Recommended Action Install more memory for the Cisco Mainframe Channel Connection (CMCC), configure fewer devices, or limit the number of sessions through this offload device.
Error Message
%OFFL-3-NOMEMT: Insufficient memory ([chars]) for offload packet trace., MSGDEF_LIMIT_GLACIALExplanation Not enough free memory is available for TCP/IP offload PKTTRACE. Tracing of a packet is skipped.
Recommended Action Refine (limit) the PKTTRACE option on the mainframe to reduce the number of packets being traced.
Error Message
%OFFL-0-NOPEND: Trying to free buffer when no send is pending. Operation: [dec]Explanation An internal logic error has occurred. A request to free a send buffer was made even though there is no send pending.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the error messages, issue the show tech-support command, and provide this information to your Cisco technical service representative.
Error Message
%OFFL-6-OFFLNOTFOUND: No offload device found.Explanation No offload device was found for the IP address for which an alias is being configured.
Recommended Action Make sure the offload address specified in the offload alias command matches an offload configuration command. If an offload device exists for the specified IP address, then capture the output of the show tech-support command and all error messages, and report them to your Cisco technical representative.
Error Message
%OFFL-3-PENDREQ: Pending request [hex] deleted due to new request [hex]Explanation The offload application had to save a socket request for later execution while another request of the same type was pending. The first request was dropped. This situation typically means that the mainframe has sent duplicate Common Link Access to Workstation (CLAW) frames. Depending on what kind of offload message was duplicated, a variety of effects may follow, from nothing to session loss or even data corruption.
Recommended Action This error message is typically followed by a hex dump. Copy the error messages exactly as they appear, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-3-REGERR: Register of offload PKTTRACE failed. Packet tracing skipped.Explanation An internal error has occurred. The callback registry refused to add the offload tracing function to its list. The tracing of packets is skipped.
Recommended Action Copy the error messages exactly as they appear and report them to your Cisco technical support representative.
Error Message
%OFFL-3-REQFORM: Socket request [dec] uses invalid parameters. Offset [dec]: [hex]Explanation The host has sent a socket request with an invalid parameter. The Cisco Mainframe Channel Connection (CMCC) responded with an error code.
Recommended Action Check if there were any special events that coincided with this error message, such an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-3-REQLEN: Socket request [dec] has wrong length [dec]Explanation The host sent a socket request with an incorrect length. The Cisco Mainframe Channel Connection (CMCC) responded with an error code.
Recommended Action Check if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-3-REQTYPE: Unknown [chars] socket request code [dec]Explanation The host sent a socket request with an unknown type. An example could be an IOCTL request with a type code that is not implemented in the current release of Cisco Mainframe Channel Connection (CMCC) microcode. The CMCC responded with an error code.
Recommended Action Check if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-4-SENDERR: Bad serial number [hex] in send request - expected [hex]Explanation The host sent a send socket request that had an unexpected serial number in the header. This is most likely a bug on the host.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) sent an error response to the send socket request. The host TCP/IP stack will probably print the error message, "Unexpected result from Offload device..." Copy the error messages exactly as they appear and report them to your Cisco technical service representative.
Error Message
%OFFL-4-SOCLEFT: [dec] Sockets found after shutdownExplanation When the offload application quit, it detected sockets that were still waiting for cleanup. This is an internal logic error.
Recommended Action This message should be preceded by other error messages that provide further information. Copy the error messages exactly as they appear, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-6-SOCREQ: Unrecognized socket request code [dec]Explanation The host sent an offload socket request with an invalid request code. The Cisco Mainframe Channel Connection (CMCC) responded with an error code. This error message can occur if a particular feature of the offload protocol is not supported by the current version of CMCC microcode. This error message can also occur if the CMCC received bad data.
Recommended Action Check if there were any special events that coincided with this error message, such as an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-6-TOOMANYALIASES: Attempt to configure too many aliases.Explanation An attempt to configure too many aliases has been rejected. The offload application allows 8 aliases per offload device.
Recommended Action If the number of existing aliases is less than the allowed maximum, then capture the output of the show tech-support command and all error messages, and report them to your Cisco technical representative.
Error Message
%OFFL-6-TRDISA: Offload PKTTRACE disabled.Explanation The mainframe TCP/IP has disabled PKTTRACE tracing. This can occur because the Generalized Trace Facility (GTF) was terminated or because a NOTRACE command was issued.
Recommended Action No action is required.
Error Message
%OFFL-6-TRENAB: Offload PKTTRACE enabled.Explanation The mainframe TCP/IP has enabled tracing using PKTTRACE.
Recommended Action No action is required.
Error Message
%OFFL-4-TRRESU: Pending trace packets now [dec], tracing resumed ([dec]), MSGDEF_LIMIT_GLACIALExplanation The number of outstanding trace packets pending to go to the mainframe has reached an acceptable level. Tracing of packets is resumed now, but some packets received or sent by this offload device were not traced during the suspension. The number in parentheses is the count of how many times a suspend occurred. The number serves as a correlator to the suspend message.
Recommended Action No action is required.
Error Message
%OFFL-4-TRSUSP: Pending trace packet limit [dec] reached, tracing suspended ([dec]), MSGDEF_LIMIT_GLACIALExplanation The limit of outstanding trace packets pending to go to the mainframe has been reached. Tracing of packets is suspended temporarily rather than continuing to flood the channel with trace data. Note: This means that some of the packets received and/or sent by this offload device will not be traced. The number in parentheses is the count of how many times suspend occurred. The number serves as a correlator to the resume message.
Recommended Action A message indicating the resumption of tracing will be seen when the congestion abates. No action is required; however, reducing the amount of tracing being done might minimize such suspensions.
Error Message
%OFFL-6-UNEXP: Unexpected offload command code [dec]Explanation The host sent an offload command with an offload command code that cannot be handled by the Cisco Mainframe Channel Connection (CMCC). The CMCC ignored the request.
Recommended Action Check if there were any special events that coincided with this error message, such an IPL, a dropped session, channel errors, or any kind of debugging activity. Copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-6-VIRTOFFL: Offload device may not be created on a virtual port adapterExplanation An attempt was made to configure an offload device on the virtual port adapter. Offload devices are permitted on physical port adapters only.
Recommended Action The configuration request was ignored. No action is required.
Error Message
%OFFL-6-WRCHAIN: Received too long message, xfer_element 0x[hex] chains to 0x[hex]Explanation The offload application received a message on the Common Link Access to Workstation (CLAW) control link or the IP link that consisted of more than 16 CLAW buffers. This configuration is not supported.
Recommended Action If this error is reproducible, copy the error message exactly as it appears, issue the show tech-support command output, and provide the information to your Cisco technical support representative.
Error Message
%OFFL-6-WRITEREAD: Host Wrote data on read subchannel, MSGDEF_LIMIT_GLACIALExplanation The mainframe has written data to the read subchannel. This is most likely the result of a misconfiguration under a VM guest in which the write device is attached to the read subchannel.
Recommended Action Check the device definitions on the host. If running under VM, verify that the write device is attached to the write subchannel and the read device is attached to the read subchannel.
Error Message
%OFFL-0-WRONGFREE: Trying to free mbuf out of sequenceExplanation An internal logic error has occurred. An unexpected address was specified in a request to free a buffer.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the error messages, issue the show tech-support command, and provide this information to your Cisco technical service representative.
The following Channel Interface Processor (CIP) error messages are related to the packed extension to the Common Link Access to Workstation (CLAW) facility.
Error Message
%PACK-3-BADLEN: Invalid length in CLAW packed control message - act [dec], exp [dec]Explanation A control message was received under the packed Common Link Access to Workstation (CLAW) link, and the length did not match that of a known packed control message.
Recommended Action Get a Generalized Trace Facility (GTF) and a channel trace to verify that the host is sending the bad packed message.
Error Message
%PACK-3-BADSCBQ: Found data queued with channel queue partially empty.Explanation After a packet was received, the packed driver detected that packed data was waiting to be queued even though the channel queue was partially emptied.
Recommended Action This is an internal logic error. Report this error to your Cisco technical support representative.
Error Message
%PACK-0-BADSIZE: Invalid size in connection request- [dec] R, [dec] W; defined - [dec] R [dec] WExplanation In a packed connection request, either a read size requested was smaller than the packed type defined or a write size requested was larger than the packed type defined.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%PACK-0-BADSIZE2: Packed type names:[chars] - [chars]Explanation The specified packed type names have experienced a BADSIZE-PACK error.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%PACK-3-BADSTATE: Claw packed sublink [dec] is in an unknown state [dec]. Path=[hex][hex][hex] device=[hex] link=[hex]Explanation A packet was received from the host on a packed sublink for which the state was unknown. This is a logic error.
Recommended Action The packet was dropped. Report this error to your Cisco technical support representative.
Error Message
%PACK-0-BADTYPE: Host Packed names [chars] - [chars] do not match any configured names.Explanation An attempt was made to establish a packed connection, but the packed type names specified on the host do not match any of the packed names specified in the Cisco Mainframe Channel Connection (CMCC).
Recommended Action Correct the host configuration or upgrade CMCC microcode to a version that supports that packed type specified by the host.
Error Message
%PACK-0-BADTYPE2: Supported packed type names: [chars] - [chars]Explanation See explanation for BADTYPE-PACK.
Recommended Action Correct the host and/or router configuration.
Error Message
%PACK-0-BADVERSION: Host CLAW Packing version [dec] does not equal CMCC version [dec].Explanation The version specified in a packed Common Link Access to Workstation (CLAW) message from the host is not the same as the version specified in the Cisco Mainframe Channel Connection (CMCC).
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%PACK-6-COMMAND: Unrecognized CLAW packing control command code [dec].Explanation The host has sent a Common Link Access to Workstation (CLAW) packing control command with an invalid command code.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has ignored the request. Get a Generalized Trace Facility (GTF) and a channel trace to verify that the host is sending the bad packed message.
Error Message
%PACK-6-CTLERROR: Packed control error message received with return code of [dec].Explanation The host rejected a previously received Common Link Access for Workstations (CLAW) packed control message sent by the Cisco Mainframe Channel Connection (CMCC).
Recommended Action Check the return code and correct as appropriate.
Error Message
%PACK-3-ILLEN: Not enough data left in buffer for packed message - remaining [dec], length [dec]Explanation The host has written a block of packed messages, and the length of the block was inconsistent with the size of the packed messages.
Recommended Action Get a Generalized Trace Facility (GTF) and a channel trace to verify that the host is sending the bad packed message.
Error Message
%PACK-3-ILLEN2: Received zero length packed message, MSGDEF_LIMIT_GLACIALExplanation The host has written a block of packed messages, and the length of a packed message was zero. This is an invalid size.
Recommended Action Get a Generalized Trace Facility (GTF) and a channel trace to verify that the host is sending the bad packed message.
Error Message
%PACK-6-NOCONN: Channel wrote data on sublink [dec] without a valid connection. Path=[hex][hex][hex] device=[hex] link=[hex], MSGDEF_LIMIT_GLACIALExplanation A packet has been received from the host, but the packed sublink specified with the data does not represent a valid connection.
Recommended Action The packet was dropped. Report this error to your Cisco technical support representative.
Error Message
%PACK-0-NOLINKID: Unable to allocate sublink id for CLAW packing sublink.Explanation An attempt was made to allocate a sublink ID to assign to a connection request, but all sublink IDs were in use. This should not occur.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has recovered by generating a bad return code to the requestor. Report this error to your Cisco technical support representative.
Error Message
%PACK-3-NOMBUF: Couldn't allocate a new MBUF from the CLAW Packing pool.Explanation An attempt to allocate a new memory buffer from the CLAW Packing tool has failed. This is a design error. There should always be enough memory buffers for packed Common Link Access to Workstation (CLAW) data.
Recommended Action Contact your Cisco technical support representative.
Error Message
%PACK-3-NOMORE: Packed sublink [dec] doesn't support the more bitExplanation The host sent a packet message with the "More" bit on, and the sublink to which the message was sent does not support the "More" bit.
Recommended Action Get a Generalized Trace Facility (GTF) and a channel trace to verify that the host is sending the bad packed message.
Error Message
%PACK-6-NOTPRESENT: CLAW Packing sublink [dec] being freed was not present.Explanation The host software has attempted to disconnect a Common Link Access to Workstation (CLAW) packing sublink that was not established.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has ignored the request. Report this error to your Cisco technical support representative.
Error Message
%PACK-6-RANGE: CLAW packing sublink [dec] being freed is out of range.Explanation The Common Link Access to Workstation (CLAW) packing sublink ID in a disconnect is not in the valid range for all CLAW packed sublinks.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has recovered by ignoring this request. Report this error to your Cisco technical support representative.
Error Message
%PACK-6-RANGE2: Out of range sublink ([dec]) received in packed claw message.Explanation The Common Link Access to Workstation (CLAW) packing sublink ID in a packed message is not in the valid range for all CLAW packed sublinks.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has recovered by ignoring this request. Report this error to your Cisco technical support representative.
Error Message
%PACK-0-SYSMGT_ERROR1: CLAW detected error in sysmgt call: invalid CLAWPACK CONTROL lengthExplanation An invalid parameter was received in a system management call.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%PACK-0-SYSMGT_ERROR2: CLAW detected error in sysmgt call: invalid CLAWPACK SUBLINK lengthExplanation An invalid parameter was received in a system management call.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%PACK-3-TOOLARGE: Received [dec] byte message on packed sublink [dec] - max is [dec].Explanation The host has sent a packed message on a sublink that was larger than the write size negotiated during the Packed Connection Request sequence.
Recommended Action Get a Generalized Trace Facility (GTF) and a channel trace to verify that the host is sending the bad packed message.
The following are channel adapter error messages that are related to the packet switching Application Programming Interface (API).
Error Message
%PKTS-3-BUFLEN: Zero length buffer detected in [chars] for [chars]([hex]), MSGDEF_LIMIT_MEDIUMExplanation An application buffer error has been detected in the channel adapter packet-switching Application Programming Interface (API).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PKTS-3-CONSISTENCY: [chars] : [chars] [hex] [dec]Explanation A consistency error has been detected in the channel adapter packet-switching Application Programming Interface (API).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PKTS-3-INIT: [chars] ([dec])Explanation The Cisco Mainframe Channel Connection (CMCC) Packet Switching initialization has failed because of lack of memory on the card. Packets will not be switched between the CMCC card and the Route Processor.
Recommended Action Verify that the amount of memory installed on the CMCC card is capable of supporting the configured CMCC microcode.
Error Message
%PKTS-3-NOSUPP: [chars] ([hex], [hex])Explanation An attempt has been made to call a function in a packet-switching Application Programming Interface (API) control block that was not implemented or supported.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PKTS-3-NOTREADY: packet switching API not initialized - [chars]Explanation An attempt has been made to call a function in a packet-switching Application Programming Interface (API) before the initialization was complete.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%PKTS-3-SEGMENT: [chars] : [chars] [hex] [dec]Explanation A data buffer containing too many segments or particles to transmit to the platform route processor was detected. A packet is being dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following Channel Interface Processor (CIP) error messages are related to the storage control block.
Error Message
%SCB-6-BADSCB: Request to free SCB 0 ignoredExplanation An attempt has been made to free storage control block (SCB) 0. This is an internal logic error. The request was ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SCB-6-RESUME: SCB on port [dec] available, correlator: [dec] task: [chars] [hex], MSGDEF_LIMIT_GLACIALExplanation A task waiting for a channel storage control block (SCB) woke up. This message is typically preceded by the message, "SCB limit on port [dec] reached." The correlator value in this message and the following message indicate that the two messages form a pair. In most cases, the pair of messages indicates a burst of activity that resulted in an unusually long queue for the channel.
Recommended Action No action is required.
Error Message
%SCB-6-WAIT: SCB limit on port [dec] reached, correlator: [dec] task: [chars] [hex], MSGDEF_LIMIT_GLACIALExplanation A task tried to allocate a channel storage control block (SCB) when all blocks were in use. The task is now waiting for a block to become available. This message is typically followed by the message, "SCB on port [dec] available." The correlator value in this message and the following message indicate that the two messages form a pair. In most cases, the pair of messages indicates a burst of activity that resulted in an unusually long queue for the channel.
Recommended Action If this message is followed by any kind of indication that the Channel Interface Processor (CIP) has stopped working properly, report it to your Cisco technical support representative, along with the output of the show extended channel / subchannel, show extended channel / statistics, show version, show running-config, and show controller cbus commands. In addition, check the MVS syslog and the TCPIP job log (or equivalent for other mainframe operating systems) for unusual channel-related messages. Pay particular attention to anything related to TCP/IP offload.
The following error messages are related to the multitasking scheduler, the facility that is responsible for determining which process to run at a given time on the Channel Interface Processor (CIP).
Error Message
%SCHED-0-BADPRIORITY: Task priority of [dec] is not allowedExplanation A request has been made to create a task, but the priority for the task was not valid. The task was not created.
Recommended Action Tasks get created either at Channel Interface Processor (CIP) startup time or as a result of a configuration command. If this message was caused by a configuration command, the configuration command was rejected. If the error message was issued at CIP startup time, while system tasks are created, the CIP may not be fully functional. Note down the steps necessary to recreate the problem, issue the show tech-support command output, and provide the information to your Cisco technical support representative.
Error Message
%SCHED-0-INVLOCK1: Invalied lock word of [dec] used in lock requestExplanation An attempt has been made to request a lock, but the lock word contained invalid data. This is a fatal internal logic error.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the error messages, issue the show tech-support command, and provide the information to your Cisco technical service representative.
Error Message
%SCHED-0-INVLOCK2: Invalied lock word of [dec] used in unlock requestExplanation An attempt has been made to unlock a lock, but the data in the lock word was not valid. This is a fatal internal logic error.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the error messages, issue the show tech-support command, and provide this information to your Cisco technical service representative.
Error Message
%SCHED-0-NMLDATA: tcb_addr = 0x[hex] current_tcb = 0x[hex] lock_value = [dec]Explanation This message contains data that relates to the SCHED-0-NOTMYLOCK message.
Recommended Action Refer to the description under the SCHED-0-NOTMYLOCK error message.
Error Message
%SCHED-0-NOLOCK: Attempt was made to unlock resource that wasn't lockedExplanation An attempt has been made to unlock a lock that was not held. This is a fatal internal logic error.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the error messages, issue the show tech-support command, and provide this information to your Cisco technical service representative.
Error Message
%SCHED-0-NOPROCID: No process id available for process creationExplanation An attempt has been made to create more tasks than the Channel Interface Processor (CIP) is designed to allow. The task was not created.
Recommended Action Copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative. If your running configuration shows that you are trying to use a supported number of configuration commands, the limit on the number of tasks on the CIP has to be increased.
Error Message
%SCHED-0-NOSTACK: Could not allocate [dec] bytes for stack from memoryExplanation An attempt has been made to create a task, but sufficient memory was not available to contain the stack for the task. The task was not created.
Recommended Action If this message was caused by a configuration command, it is an indication that the Channel Interface Processor (CIP) does not have enough memory to run it. Install more memory for the CIP, or configure fewer devices. If this message occurred at CIP startup time, it is an indication that the version of CIP microcode you are running is not supported on a CIP with the amount of memory you have installed. Install more memory for the CIP in this case.
Error Message
%SCHED-0-NOTCB: Could not allocate [dec] bytes for tcb from memoryExplanation An attempt has been made to create a task, but sufficient memory was not available to contain the control block for the task. The task was not created.
Recommended Action If this message was caused by a configuration command, it is an indication that the Channel Interface Processor (CIP) does not have enough memory to run it. Install more memory for the CIP, or configure fewer devices. If this message occurred at CIP startup time, it is an indication that the version of CIP microcode you are running is not supported on a CIP with the amount of memory you have installed. Install more memory for the CIP in this case.
Error Message
%SCHED-0-NOTMYLOCK: Attempt was made to unlock another task's resourceExplanation An attempt has been made to unlock a lock that was set by another task. This is a fatal internal logic error.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the error messages, issue the show tech-support command, and provide this information to your Cisco technical service representative.
Error Message
%SCHED-0-NOTPROCES: Attempt was made to lock while not at process levelExplanation An attempt has been made to lock a resource while not at the process level. This is a fatal internal logic error.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the error messages, issue the show tech-support command, and provide this information to your Cisco technical service representative.
The following Channel Interface Processor (CIP) error messages are related to the serial link controller.
Error Message
%SLC-3-PCANMIRESET: Reset of Port [dec] NMI failedExplanation After the serial link controller had serviced a nonmaskable interrupt (NMI) from a parallel channel adapter (PCA) interface, the attempt to reset the interrupt failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SLC-3-SCANEP1: Scan of EP ring 1 failedExplanation An attempt to scan the first set of internal latches on the Enterprise System Connection (ESCON) processor has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SLC-3-SCANEP2: Scan of EP ring 2 failedExplanation An attempt to scan the second set of internal latches on the Enterprise System Connection (ESCON) processor has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SLC-3-SCANSLC: Scan of SLC ring failedExplanation An attempt to scan the internal latches of the serial link controller has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SLC-3-STOPBIDITO: Stop BIDI clock timed outExplanation An attempt was made to stop the clock on the interface between the Enterprise Systems Connection (ESCON) processor and the serial link controller. The serial link controller did not indicate that the bidirectional bus (BIDI) clock was stopped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SLC-3-STOPEPTO: Stop EP clock timed outExplanation An attempt was made to stop the clock on the Enterprise System Connection (ESCON) processor. The serial link controller did not indicate that the clock was stopped. The Channel Interface Processor (CIP) attempted to stop the bidirectional bus (BIDI) clock.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following Channel Interface Processor (CIP) error messages are related to the Signaling Link Code Interface (SLCI).
Error Message
%SLCI-3-BAD_TYPE_CODE: PA[dec] MPC [hex]-[hex] got unrecognized xfer_list type codeExplanation A Multipath Channel (MPC) process has received a transfer list with an unrecognized type code.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SLCI-6-FLUSH: PA[dec] MPC [hex]-[hex] Read data flushed.Explanation Because of an error on the channel, some data that was intended to be sent to the channel has not been sent to the channel. The virtual telecommunications access method (VTAM) will receive an error indication and should retry the operation.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SLCI-3-INBOUND_FSM_ERR: PA[dec] MPC [hex]-[hex] Event [chars], State [chars]Explanation An internal state machine has attempted to execute an event that is inconsistent with the state.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SLCI-3-INFLOW_FSM_ERR: PA[dec] MPC [hex]-[hex] Event [chars], State [chars]Explanation An internal state machine has attempted to execute an event that is inconsistent with the state.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SLCI-6-LONGREC: PA[dec] CTA [hex]-[hex] Attempt to transmit too large a record.Explanation The amount of data being read by the channel has exceeded the size of the read channel command word.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SLCI-0-NOMEM: Attempt to acquire memory by [chars] failed, pc: [hex], at [int]Explanation A call to create a pool or get a buffer has failed.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SLCI-0-STASH_EMPTY: Stash empty on read completeExplanation A read operation has completed, but there was no stashed data.
Recommended Action Report this error to your Cisco technical support representative.
The following Channel Interface Processor (CIP) SSI802 error messages are related to the Common Service System Service Interface (SSI) facility.
Error Message
%SSI802-6-DUMP: [chars]Explanation This message is used by the dump utility to display the hex dump of storage.
Recommended Action No action is required.
Error Message
%SSI802-3-FATAL_ERROR: SSI_ASSERT failure in [chars] @ [int] - [chars]Explanation The Cisco SNA (CSNA) has encountered unrecoverable error conditions that prevent it from continuing its normal operations.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SSI802-3-RTN_ADR: Return Address: 0x[hex]Explanation This is a debug feature to show the return address when an ASSERT is used in an inline function.
Recommended Action Action according to subsequent error.
The following are software subsystem error messages.
Error Message
%SUBSYS-2-BADCLASS: Bad subsystem clas ([dec]) - ignoring subsystemExplanation A software consistency check has failed.
Recommended Action Call your Cisco technical support representative for assistance.
Error Message
%SUBSYS-2-BADSEQUENCE: Subsystem ([chars]) has cross-class sequence for ([chars])Explanation A software consistency check has failed.
Recommended Action Call your Cisco technical support representative for assistance.
Error Message
%SUBSYS-2-BADVERSION: Bad subsystem version number ([dec]) - ignoring subsystemExplanation A software consistency check has failed.
Recommended Action Call your Cisco technical support representative for assistance.
Error Message
%SUBSYS-2-MAXRECUR: Too many levels of recursionExplanation A software consistency check has failed.
Recommended Action Call your Cisco technical support representative for assistance.
Error Message
%SUBSYS-2-MISMATCH: Kernel and subsystem version differ ([dec].[dec]) - ignoring subsystemExplanation A software consistency check has failed.
Recommended Action Call your Cisco technical support representative for assistance.
Error Message
%SUBSYS-2-NOTFOUND: Subsystem ([chars]) needs subsystem ([chars]) to startExplanation A software consistency check has failed.
Recommended Action Call your Cisco technical support representative for assistance.
The following are Channel Interface Processor (CIP) operating system error messages.
Error Message
%SYS-3-BADBLOCK: Bad block pointer [hex]Explanation A block of memory is corrupt at the indicated location.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-3-BADFREEMAGIC: Corrupt free block at [hex] (magic [hex])Explanation A block of memory is corrupt at the indicated location.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-3-BADFREEPTRS: Bad [chars] pointer [hex] at [hex] ([chars] = [hex])Explanation A pointer in the block header at the indicated location is corrupt.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-3-BADMAGIC: Corrupt block at [hex] (magic [hex])Explanation The free memory pool is corrupted.
Recommended Action Call your Cisco technical support representative for assistance.
Error Message
%SYS-2-BADSHARE: Bad refcount in [chars], ptr=[hex], count=[hex]Explanation An internal software error has occurred.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-6-BLKINFO: [chars]blk [hex], words [int], alloc [hex], [chars], dealloc [hex], rfcnt [hex]Explanation An internal software error has occurred.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-3-CACHED_PAGE_ADR: Uncached page pointer 0x[hex] in call to return_page_inlineExplanation The pointer to a page being returned to the page pool was a cached address.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SYS-3-CACHE_DIRTY_ADR: cache line 0x[hex] dirty, task: [chars]Explanation This error message reports the address at which a scan cache operation detected that the cache has not been flushed as expected.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SYS-6-CACHE_DIRTY_MSG: [chars][chars]Explanation This message provides additional information about a CACHE_DIRTY_ADR message.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SYS-2-FREEBAD: Attempted to free memory at [hex], not part of buffer poolExplanation An internal software error has occurred.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-2-FREEFREE: Attempted to free unassigned memory at [hex], alloc [hex], dealloc [hex]Explanation An internal software error has occurred.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-3-INUSEFREE: Block [hex] on free list [dec] in useExplanation An internal software error has occurred.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-3-INVMEMINT: Invalid memory action ([chars]) at interrupt levelExplanation A memory allocation or deallocation has been attempted from an interrupt handler.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-2-LOWMEM: Low memory debug exception (limit=[int] free=[int])Explanation The Channel Interface Processor (CIP) is running short on memory.
Recommended Action It may be necessary to free some memory by exiting a program. If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-2-MEMTOOSMALL: CIP software requires a minimum of 8MB of DRAMExplanation The Channel Interface Processor (CIP) software has become large enough that it will not run with only 2MB of DRAM.
Recommended Action Contact your support representative for a free 8-MB upgrade.
Error Message
%SYS-6-MTRACE: [chars]: addr, pcExplanation The free memory pool is corrupted.
Recommended Action If this message recurs, contact your Cisco technical support representative for assistance.
Error Message
%SYS-2-NOMEMFRG: Memory fragmentation check debug exception (fragment size [int])Explanation The system has detected an error while checking memory fragmentation.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-2-NOMEMORY: No memory available for [chars] [dec]Explanation An operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%SYS-3-NZREFCNT: Block [hex] on free list [dec] with ref count [dec]Explanation A block of memory in the free pool is actually in use. The number of processes using the memory block is indicated.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
Error Message
%SYS-3-OVERRUN: Block overrun at [hex] (redzone [hex])Explanation An internal software error has occurred.
Recommended Action If this message recurs, contact your Cisco technical support representative for assistance.
Error Message
%SYS-5-RELOAD: Reload requestedExplanation A reload or restart has been requested.
Recommended Action No action is required.
Error Message
%SYS-5-RESTART: System restarted --[chars]Explanation A reload or restart has been requested.
Recommended Action No action is required.
Error Message
%SYS-3-WRONGFREELIST: Block [hex], size [dec], on wrong free list ([dec], [dec])Explanation A freed buffer has been placed on the wrong list of free buffers.
Recommended Action If this message recurs, call your Cisco technical support representative for assistance.
The following are system management event error messages.
Error Message
%SYSMGT_EVENT-4-ERROR: [chars] - [chars]([chars])Explanation The system management event-sending operation has failed. Traps, alerts, and console messages for a channel event will not be generated.
Recommended Action If this error recurs, report it to your Cisco technical support representative.
The following are system management error messages that relate to the remote-procedure call (RPC) operation.
Error Message
%SYSMGT_RPC-3-ERROR: Error detected ([chars])Explanation A system error involving the system management remote-procedure call (RPC) operation has been detected.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SYSMGT_RPC-3-IPC_ERROR: [chars] [chars] failed ([chars]), MSGDEF_LIMIT_GLACIALExplanation A system management remote-procedure call (RPC) operation has failed. A request for information from the channel adapter card will not be processed.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%SYSMGT_RPC-3-NOMEM: [chars]Explanation The channel adapter system management (SYSMGT ) subsystem could not be initialized because of lack of memory available on the channel adapter. Since the channel adapter SYSMGT component was unable to be initialized, most show extended channel command information and all channel adapter event notifications will be unavailable to the user.
Recommended Action Upgrade the channel adapter with more memory.
Error Message
%SYSMGT_RPC-6-STATE_CHANGE: System Management [chars]Explanation The channel adapter system management subsystem has changed state.
Recommended Action No action is required.
Error Message
%SYSMGT_RPC-4-UNKNOWN: [chars] request for class [dec] contains unknown [chars] [dec], MSGDEF_LIMIT_SLOWExplanation The channel microcode has received a system management clear or query request with an unknown code on the this port.
Recommended Action Check your microcode version to ensure that it is compatible with this version of Cisco IOS software.
The following error messages relate to the TN3270 server terminal emulation feature of the Channel Interface Processor (CIP) card.
Error Message
%TN3270S-6-AVL_INSERT_FAILED: An AVL Insert failed in [chars]Explanation An attempt to add information to the approved vendor list (AVL) tree has failed. This is an indication of an internal program logic error.
Recommended Action Report this problem to your Cisco technical support representative.
Error Message
%TN3270S-6-BADTIMER: Bad timer operation([dec]), ra=[hex], funcPtr=[hex], oldFuncPtr=[hex], 3600*ONESECExplanation A bad timer operation was detected and aborted. The rest of the information is useful only to developers to debug the problem. Such bad-timer occurrences are usually harmless, but are reported because they may accompany a more serious problem.
Recommended Action It is important to report this problem to your Cisco technical support representative, because it reflects an internal program logic error.
Error Message
%TN3270S-4-BAD_MAX_LUS_CFG: Could not change maximum LUs to [dec]Explanation The TN3270 server could not change the maximum number of logical units (LUs) to the requested value. The previous number is still in use.
Recommended Action Review the previous error messages to discover what caused the failure, and take action based on those messages.
Error Message
%TN3270S-1-CREATE_MUXWAIT_FAILED: A TN3270 server related semaphore could not be created.Explanation An important semaphore could not be created.This failure is due to either memory shortage or some internal code error.
Recommended Action This error is most probably due to insufficient memory. Upgrade your board with additional memory. If you believe there is sufficient memory, it is possible that there is a memory leak. Report details of your configuration, output of the show controller cxbus command, and any action needed to reproduce this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-CREATE_POOL_FAILED: A TN3270 server related buffer pool could not be created.Explanation An important buffer pool could not be created. This failure is due to either memory shortage or some internal code error.
Recommended Action This error is most probably due to insufficient memory. Upgrade your board with additional memory. If you believe there is sufficient memory, it is possible that there is a memory leak. Report details of your configuration, output of the show controller cxbus command, and any action needed to reproduce this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-CREATE_THREAD_FAILED: A TN3270 server related thread could not be startedExplanation An important thread could not be created. This failure is due to either a memory shortage or some internal code error.
Recommended Action This error is most probably due to insufficient memory. Upgrade your board with additional memory. If you believe there is sufficient memory, it is possible that there is a memory leak. Report details of your configuration, output of the show controller cxbus command, and any action needed to reproduce this problem to your Cisco technical support representative.
Error Message
%TN3270S-4-DDDLU_NOT_SUPPORTED: Host does not support dddlu at IP addr [chars], port [dec], 600*ONESECExplanation The TN3270 server cannot complete one or more connection requests from a TN3270/E client because the host does not support DDDLU.
Recommended Action Check that all physical units (PUs) configured for use with DDDLU have the LUGROUP operand defined. Also check that the specified virtual telecommunications access method (VTAM) LUGROUP major node is active.
Error Message
%TN3270S-4-FUNC_NEGOT_LOOP: Client [chars]:[dec] in loop on TN3270E function negotiation [dec]., 600*ONESECExplanation The client software is not behaving as specified by the RFC requirements.
Recommended Action Try to locate the TN3270 client that caused the problem. There could be a bug in the client.
Error Message
%TN3270S-0-ILLEGAL_CCMUTEX_RELEASE: Releasing unacquired semaphore, lock_held [hex] lock_value [hex] ccMutex tcb [hex] thread tcb [hex]Explanation An exclusive lock is being released illegally by an executing thread. The lock is held either by no one or by some other thread.
Recommended Action Reload the Channel Interface Processor (CIP). Since this problem is very serious, the error might recur. In any case, send the output of this message and tasks on the CIP console to the your Cisco technical support representative. Also send information about your configuration and any action required to reproduce this problem.
Error Message
%TN3270S-4-ILLEGAL_SUBOPTION: Client [chars]:[dec] sent Telnet suboption [dec] illegally.Explanation The TN3270 client software is not behaving as specified by the RFC requirements.
Recommended Action Try to locate the TN3270 client that caused the problem. There could be a bug in the client.
Error Message
%TN3270S-6-INVALID_RESOURCE_LENGTH: Resource name length [chars] is greater than 8 bytesExplanation The resource name has a length greater than the prescribed maximum length, which is 8 bytes. This is an indication of an internal program logic error.
Recommended Action Report this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-LISTENFAIL: Listening on [hex] [dec] Failed; err [dec]Explanation There was an attempt to bring up a physical unit (PU) but listening on the corresponding TCP/IP port could not be started.
Recommended Action Ensure that there is sufficient memory on the Channel Interface Processor (CIP) card. If insufficient memory is not the problem, else report this message to your Cisco technical support representative.
Error Message
%TN3270S-2-LOW_MEM: Insufficient memory for TN3270 server, [dec] KBytes available, [dec] requiredExplanation Insufficient memory is preventing proper operation of the TN3270 server.
Recommended Action Make sure there is enough memory available on board. Upgrade the memory on board or cancel other services running on the Channel Interface Processor (CIP). If you believe there is sufficient memory, it is possible that there is a memory leak. Report details of your configuration, output of the show controller cxbus command, and any action needed to reproduce this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-LU_ERROR: lu error [chars]: [chars]:[dec] pu:[hex], tnet:[hex]Explanation An unexpected event was presented to the logical unit (LU) named by the LOCADDR and physical unit (PU). The error may cause the TN3270 session to work improperly. More detail on this error is contained in the LU_ERROR_INFO messages immediately following this message.
Recommended Action Report this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-LU_ERROR_INFO: LU info: Event [chars], state = [hex], snaState = [hex], flag = [hex]Explanation An internal software error has occurred. This message provides information about logical unit (LU) state, history, and flags before the error occurred.
Recommended Action Report this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-LU_NO_BUFFER: No buffer for lu: [chars], 600*ONESECExplanation Some preallocated logical unit (LU) buffer space for transmissions has run out. The transmission of the message is aborted. The LU session is left incomplete. In addition, the LU session could hang.
Recommended Action Use show commands to find out as much about the LU state as possible and report the findings to your Cisco technical support representative.
Error Message
%TN3270S-6-LU_THRESHOLD:Explanation The number of LU sessions is approaching the configured maximum-lus limit.
Recommended Action No action is required.
Error Message
%TN3270S-1-MEMORY_SHORTAGE: Insufficient memory on board; failed to allocate [dec] bytesExplanation Memory could not be allocated for an important operation.
Recommended Action Upgrade your board with additional memory. If you believe there is sufficient memory, it is possible that there is a memory leak. Report details of your configuration, output of the show controller cxbus command, and any action needed to reproduce this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-NAIL_NOT_FOUND: Deletion of the Client IP ([chars]) LU Nailing first ([dec]) to last ([dec]) failed because the configuration was not found.Explanation Deletion of the Client IP logical unit (LU) nailing command has failed because the command could not be found.
Recommended Action No action is required.
Error Message
%TN3270S-1-NegRsp_NO_CORRELATOR: TN3270E negative response correlation: [chars].[dec], client IP addr [chars], nextSqn=[dec], rspSqn=[dec], 600*ONESECExplanation A TN3270E client has sent a negative response to a TN3270 request sent previously by the server. The negative response does not have a sequence number that can be correlated by the server.
Recommended Action Determine the DLOGMOD used for the session. Review the outbound pacing bits used for this session and ensure that the pacing value is no bigger than 4. If the problem persists, contact the client software vendor and file a problem report.
Error Message
%TN3270S-6-NON_E_IPADDR_ELEMENT_NOT_FOUND: Deletion of the tn-parameter IP ([chars]) value ([dec]) command failed because the configuration was not found.Explanation Deletion of the tn-parameter command has failed because the command could not be found. This is an indication of an internal program logic error.
Recommended Action Report this problem to your Cisco technical support representative.
Error Message
%TN3270S-3-NO_BIND_REQ_RCVD: No BIND REQ received on LU [chars].[dec], 120*ONESECExplanation Either a BIND REQUEST or system services control points (SSCP)-LU data was expected (but not received) from the host within 30 seconds of the start of the SSCP-LU session for this TN3270 session. If the condition persists for another two minutes, the logical unit (LU) is declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening-point are in use.
Recommended Action Examine the SSCP host virtual telecommunications access method (VTAM) console for status of specified PU and logical unit (LU). Review VTAM console log output for relevant events, such deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, please report this error to your Cisco technical support representative. A temporary workaround is to simply recycle the affected LU at the VTAM console. This will put the LU back into normal circulation.
Error Message
%TN3270S-3-NO_DYN_ACTLU_REQ_RCVD: No ACTLU REQ received on LU [chars].[dec], 120*ONESECExplanation The host has not sent an ACTLU REQUEST within 30 seconds of sending a Reply-PSID RSP. If this condition persists for another two minutes, the current TN3270 session connected to the LU is disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening-point are in use.
Recommended Action Examine the system services control points (SSCP) host virtual telecommunications access method (VTAM) console for the status of the specified physical unit (PU) and logical unit (LU). Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message
%TN3270S-1-NO_EVENT_BUFS: No IPC sysmgt event buffers for at least one minute , 600*ONESECExplanation TN3270 server has events that will result in Simple Network Management Protocol (SNMP) traps and SNA Alerts, but it has not been able to allocate interprocess communication (IPC) buffer resources to report the events to the router system code. The TN3270 server will continue to try to report these events, but lack of buffers may continue until the Channel Interface Processor (CIP) microcode reload.
Recommended Action Report this problem to your Cisco technical representative. Include output from the following commands: show ipc status, show ipc queue, show ipc ports, show ipc nodes, show controller cbus, and show version As a workaround, reload the CIP microcode.
Error Message
%TN3270S-1-NO_LU_MEMORY: No memory on the CIP was available for completing a requested TN3270 LU sessionExplanation There is insufficient memory available to the TN3270 server to complete one or more requests by TN3270/E clients for logical unit (LU) sessions. The sessions have been disconnected.
Recommended Action Review the memory required to run the TN3270 server application in light of current client load. Install additional memory if necessary.
Error Message
%TN3270S-4-NO_LU_SESSIONS: No LU sessions left in :GENERIC for PUs at IP addr [chars], port [dec], 600*ONESECExplanation The TN3270 server cannot complete one or more connection requests from a TN3270/E client because there are no more available logical units (LUs) left in the generic pool associated with the specified IP listening-point address.
Recommended Action Review the LU requirements for endpoints of this application. Configure additional physical units (PUs) listening at the specified IP address and port number.
Error Message
%TN3270S-1-NO_NAIL_MEMORY: Insufficient memory available on the cip for Client IP LU NailingExplanation There is insufficient memory available to process the Client IP logical unit (LU) nailing command on the Channel Interface Processor (CIP).
Recommended Action No action is required.
Error Message
%TN3270S-3-NO_NTFY_AV_RSP_RCVD: No NOTIFY(available) RSP received on LU [chars].[dec], 120*ONESECExplanation No response to a power-on (available) notify request was received by the TN3270 server within 30 seconds of sending it to the host. If this condition persists for another two minutes, the current TN3270 session connected to the logical unit (LU) is disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening-point are in use.
Recommended Action Examine the system services control points (SSCP) host virtual telecommunications access method (VTAM) console for the status of the specified physical unit (PU) and LU. Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message
%TN3270S-3-NO_NTFY_UA_RSP_RCVD: No NOTIFY(UA) RSP received on LU [chars].[dec], 120*ONESECExplanation No response to a power-off (unavailable) notify request was received by the TN3270 server within 30 seconds of sending it to the host. If this condition persists for another two minutes, the current TN3270 session connected to the logical unit (LU) is disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening-point are in use.
Recommended Action Examine the system services control points (SSCP) host virtual telecommunications access method (VTAM) console for the status of the specified physical unit (PU) and LU. Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message
%TN3270S-3-NO_PSID_RSP_RCVD: No NMVT Reply PSID received on LU [chars].[dec], 120*ONESECExplanation No response to a reply PSID was received by the TN3270 server within 30 seconds of sending it to the host. This fault can occur only on dynamic logical units (LUs) that have been misconfigured or deactivated at the host. If this condition persists for another two minutes, the current TN3270 session connected to the LU is disconnected. Bad dynamic LUs are placed in a special area where no attempt to reuse them is made until all other generic-pool LUs of the IP listening have been exhausted.
Recommended Action Check the status of the LU through the virtual telecommunications access method (VTAM), and vary the LU active if appropriate. This action must happen within two minutes of the time this message appears; otherwise, the LU is placed in the "bad" LU area and will not be reused unless all good LUs are in use. Examine the host VTAM log for trouble. In particular, look for messages indicating a badly configured LUGROUP resource definition or file. Fix the configuration and recycle the affected major nodes.
Error Message
%TN3270S-3-NO_SDT_REQ_RCVD: No SDT REQ received on LU [chars].[dec], 120*ONESECExplanation No SDT (Start Data Transfer) REQ was received by the TN3270 server from the primary logical unit (PLU) host for the specified logical unit (LU). If the condition persists for another two minutes, the LU is declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening-point are in use.
Recommended Action Examine the system services control points (SSCP) host virtual telecommunications access method (VTAM) console for the status of the specified physical unit (PU) and LU. Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message
%TN3270S-3-NO_SDT_TMARK_RCVD: No SDT TIMING-MARK received on LU [chars].[dec], 120*ONESECExplanation No SDT (Start Data Transfer) TIMING-MARK response was received by the TN3270 server from the TN3270 client software for the specified TN3270 session. If the condition persists for another two minutes, the LU is declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening-point are in use.
Recommended Action Some TN3270 clients may not fully handle the TN3270 RFCs. Enable the client-side trace to figure out what the client is failing on. Replace the failing client software with software from the list of TN3270 software types that are known to work with the TN3270 server (see you technical representative for this). If the problem persists, report this error to your Cisco technical support representative.
Error Message
%TN3270S-3-NO_TERMSELF_RSP_RCVD: No TERMSELF RSP received on LU [chars].[dec], 120*ONESECExplanation No response to a TERMSELF request was received by the TN3270 server within 30 seconds of sending the request to the host. If this condition persists for another two minutes, the current TN3270 session connected to the LU is disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening-point are in use.
Recommended Action Examine the system services control points (SSCP) host virtual telecommunications access method (VTAM) console for the status of the specified physical unit (PU) and LU. Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message
%TN3270S-3-NO_UNBIND_RSP_RCVD: No UNBIND RSP received on LU [chars].[dec], 120*ONESECExplanation No response to an UNBIND request was received by the TN3270 server within 30 seconds of sending the request to the host. If this condition persists for another two minutes, the current TN3270 session connected to the LU is disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening-point are in use.
Recommended Action Examine the system services control points (SSCP) host virtual telecommunications access method (VTAM) console for the status of the specified physical unit (PU) and LU. Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message
%TN3270S-3-NO_UNBIND_TMARK_RCVD: No UNBIND-time TIMING-MARK received from client for LU [chars].[dec], 120*ONESECExplanation No UNBIND TIMING-MARK response was received by TN3270 server from the TN3270 client software for the specified TN3270 session. If the condition persists for another two minutes, the LU is declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening-point are in use.
Recommended Action Some TN3270 clients may not fully handle the TN3270 RFCs. Enable the client-side trace to figure out what the client is failing on. Replace the failing client software with software from the list of TN3270 software types that are known to work with TN3270 server (see your Cisco technical representative for this). If the problem persists, report this error to your Cisco technical support representative.
Error Message
%TN3270S-6-PARAMETERINIT: An Invalid parameter registry code [dec]Explanation During the TN3270 initialization, the supported tn-parameter codes have registered a routine. This routine will be used to process the configuration command. In this case an incorrect code was used. This is an indication of an internal program logic error.
Recommended Action Report this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-POOL_NOT_FOUND: Could not find the Pool [chars]Explanation The search routines could not find this pool in the approved vendor list (AVL) tree. This message is usually an effect of a different problem. This is an indication of an internal program logic error.
Recommended Action Report this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-RESOURCE_POOL_NOT_FOUND: Could not find the ResourceCB associated with the Pool [chars]Explanation The ResourceCB associated with the pool could not be found. This message is usually an effect of a different problem. This is an indication of an internal program logic error.
Recommended Action Report this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-RP_PU_CONFLICT: RP & CIP hold conflicting PU name([chars]) or index(%ld)Explanation The Route Processor (RP) has requested action (update or delete) on a PU resource from the Channel Interface Processor (CIP) TN3270 server that is stale or incorrect.
Recommended Action Reload the CIP microcode. If the problem recurs, run the following commands before reloading the CIP microcode (! for each CIP in router): show ext chan /2 tn3270, show controllers cbus wr t. Report all findings to your Cisco technical support representative.
Error Message
%TN3270S-1-RP_RTGROUP_CONFLICT: RP & CIP hold conflicting Response Time Group name([chars])Explanation The Route Processor (RP) has requested an action (update or delete) on a Response Time Group resource from the Channel Interface Processor (CIP) TN3270 server that is stale or incorrect.
Recommended Action Reload the CIP microcode. If problem recurs, run the following commands before reloading the CIP microcode (! for each CIP in router): show ext chan /2 tn3270, show controllers cbus wr t. Report all findings to your Cisco technical support representative.
Error Message
%TN3270S-4-SESSION_NEGOT_TIME_EXPIRED: A client session from [chars]:[dec] failed to negotiate TN3270/TN3270E., 600*ONESECExplanation A Telnet session that failed to negotiate TN3270/TN3270E within a time period has been disconnected. There could be a bug in the client, or it could be a transient network problem.
Recommended Action Try to locate the TN3270 client that caused the problem.
Error Message
%TN3270S-1-SNA_BAD_SEQUENCE: LU-LU session bad sequence number, lu [chars].[dec] expected snf = [dec], current snf = [dec]Explanation An unexpected LU-LU session sequence received. The logical unit (LU) was presented to the LU named by the LOCADDR and the physical unit (PU). The error will cause a negative response of sense code X2001 to be sent to the host.
Recommended Action Examine the system services control points (SSCP) host virtual telecommunications access method (VTAM) console for the status of the specified LU. Get a trace output for the specified LU and report this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-SNA_BAD_WSF: LU-LU session [chars].[dec] WSF data is illegalExplanation A WSF 3270DS write with an invalid data length has been received.
Recommended Action Examine what application in the host sends this WSF, and report this problem to your Cisco technical support representative.
Error Message
%TN3270S-1-SNA_NO_PU_RESPONSE: PU [chars] locaddr [dec] does not get a response in 30 secondsExplanation A physical unit (PU) sent a request to the host but did not receive a response within 30 seconds.
Recommended Action Check to see if the PU is still in an active or busy state. Verify that the virtual telecommunications access method (VTAM) can talk to the PU. Check the Logical Link Control, type 2 (LLC2) connection.
Error Message
%TN3270S-4-SO_SNDBUF_FAILED: TNSetBindParam:SO_SNDBUF setsockopt for session failed sendSize [dec] err [dec]Explanation An internal error occurred during the setting of the transmit window size for a TCP session. The session is using the default window size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. Also send information about your configuration, output of the show controller cxbus command, and any action required to reproduce this problem.
Error Message
%TN3270S-1-STARTUP_RACE: InitTimerService Failed;Previous timer service still upExplanation An attempt to restart the TN3270 server occurred before the previous shutdown could be completed.
Recommended Action If this problem is due to quick restart of TN3270 server, try again to start the TN3270 server. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. Also send information about your configuration, output of the show controller cxbus command, and any action required to reproduce this problem.
Error Message
%TN3270S-1-START_FAIL: Failed to start Tn3270-serverExplanation The TN3270 server failed to start correctly and is now not running. The immediately preceding error messages point to the cause of the failure.
Recommended Action Review the previous error messages to discover what caused the start failure, and take action based on those messages.
Error Message
%TN3270S-6-START_OK: Starting Tn3270-serverExplanation The TN3270 server subsystem has been brought up.
Recommended Action No action is required.
Error Message
%TN3270S-6-STOPPING: Stopping Tn3270-serverExplanation The TN3270 server subsystem has been shut down.
Recommended Action No action is required.
Error Message
%TN3270S-2-TELNETINITFAIL: Initialization of TN3270 server FailedExplanation Initialization of the Telnet component of the TN3270 server has failed.
Recommended Action This error is most probably caused by inadequate memory on the Channel Interface Processor (CIP) card. If the memory on the CIP card is not the problem, report this message to your Cisco technical support representative.
Error Message
%TN3270S-4-TN3270_CONFIG_INCOMPATIBLE: IOS sub-codepoint [dec] with length [dec] not understood, 600*ONESECExplanation The TN3270 server has received a configuration command from the Cisco IOS software that the Channel Interface Processor (CIP) does not recognize; some functionality may not be implemented.
Recommended Action Ensure that the Cisco IOS software version is compatible with the version of software running on the CIP.
Error Message
%TN3270S-6-TOOBIG: [dec] byte IP datagram exceeds TN3270 Server receive buffer limitExplanation The router has sent an IP datagram to the TN3270 server IP address that is larger than the maximum size of 4096. The IP datagram has been dropped.
Recommended Action No action is required.
Error Message
%TN3270S-4-TOO_MANY_HOST_WRITES: Client on PU [dec]:locaddr [dec] ip [chars]:[dec] is being disconnected;Check outbound LU pacing.Explanation The TN3270 client is being disconnected. This could either be a transient network problem or an internal error in the server.
Recommended Action Make sure LU outbound pacing is configured. If that is correct, try to locate the TN3270 client that caused the problem. There could be bug in the client. Also try to get Telnet trace of the session by reproducing the problem. Report this error to your Cisco technical support representative.
Error Message
%TN3270S-7-UNKNOWN_SNA_MSG: Unknown message for PU [chars], data: [chars]Explanation A Systems Network Architecture (SNA) message from the host is invalid.
Recommended Action If it only happens once, this could a transient problem due to a high volume of network activity. Record the message for later reference. If error persists, ensure that the host is configured correctly.
Error Message
%TN3270S-6-UNSUPPORTED_FUNCTIONALITY: The requested functionality is not currently supportedExplanation This functionality is not currently supported.
Recommended Action Please report this problem to your Cisco technical support representative.
Error Message
%TN3270S-6-UNSUPPORTED_LU_DELETION_OPTION: The LU Deletion Option is not supported.Explanation The logical unit (LU) deletion option is not supported by this version of the Channel Interface Processor (CIP).
Recommended Action Ensure that the Cisco IOS software and CIP versions match.
The following Channel Interface Processor (CIP) error messages are related to the channel adapter utilities.
Error Message
%UTIL-3-LINKLIST: [chars]([hex])Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are channel port adapter error messages.
Error Message
%XCPA-3-CKSUM_OFFSET: Invalid checksum offset: offset = [dec], length = [dec]Explanation The microcode was unable to update the packet checksum. The packet will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-2-MBX: [chars] - [dec]Explanation A software program error has occurred on the Channel Port Adapter Mailbox. This could affect console support on the PA, logger messages, and configuration commands.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-NOMEMORY: Out of memory trying to [chars]Explanation The channel port adapter does not have sufficient memory to allocate the necessary resources.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-2-PMC_TIMEOUT: PMC Timeout: poll_interval = 0x[hex]Explanation A timeout occurred while the channel port adapter was trying to access either memory or the channel interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%XCPA-3-SWVER_MISMATCH: Incompatible switching version, unable to find version [dec].Explanation The Cisco IOS and Cisco Mainframe Channel Connection (CMCC) microcode versions are incompatible.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Posted: Fri Jun 16 11:47:15 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.