-
Cisco IOS System Error Messages, Volume 2 of 2
-
About Cisco IOS Software
-
System Error Messages Overview
-
NPS_APS through POSDW
-
POSLC through PQUICC_ETHER
-
PQUICC_ETHERNET through RESOURCE_MON
-
RESYNCH through SDLC
-
SDLLC through SNAPSHOT
-
SNASW
-
SNMP through SW_VLAN
-
SYS through TCP
-
TDM through TXCONN
-
UBR7200 through VPD
-
VPDN through XTAGATM
-
CMCC System Error Messages
-
CMCC-ADAPTER
-
CMCC-BSQ through CMCC-DEBUGGER
-
CMCC-DIAG through CMCC-NEVADA
-
CMCC-OFFL through CMCC-XCPA
-
System Failure Messages
-
Glossary of Acronyms
-
Index
-
Table Of Contents
CMCC OFFL Messages
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, 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
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 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 message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
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 This error message is typically followed by a fatal error dump with code 37. Capture all the error messages and issue the show tech-support command to gather data that may help identify 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, contact 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 sequence
Explanation 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 CMCC. This message is followed by a hex dump of the request.
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 CMCC ignored the request.
Recommended Action Check to see 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 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-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, copy the error me 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-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 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 CMCC error message for the recommended action.
Error Message%OFFL-3-ILLALD : Illegal data alignment: [hex] + [dec] bytes >= [hex]. xfer_element = [hex]
Explanation An internal logic error has occurred. The data following an offload message header crossed a buffer boundary. The CMCC ignored the message. This error message is usually an indication that the CMCC has received bad data. Examples of such bad data 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 to see 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 on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-ILLALH : Illegal hdr alignment detected. Address [hex] + [dec] bytes > [hex]. xfer_element = [hex]
Explanation An internal logic error has occurred. An offload message header crossed a buffer boundary. The CMCC ignored the message. This error message is usually an indication that the CMCC has received bad data. Examples of such bad data 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 to see 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 on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-ILLEN : Illegal byte count in offload data. [dec] specified, [dec] available. xfer_element = [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 such bad data 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 to see 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 on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-0-ILLFREE1 : SCB chain does not end with a read hdr
Explanation 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 and issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-0-ILLFREE2 : SCB ends with a read hdr with the MTC bit set
Explanation An internal logic error 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 and issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-ILLNUM : Illegal number of socket requests. Rejected at [dec]
Explanation The CMCC has received a CLAW frame with too many offload messages. This condition typically means that the mainframe has sent bad data to the offload device. Examples of such bad data 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 to see 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 on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-ILLRST : Received restart with [dec] intf, [dec] is max. xfer_element = [hex]
Explanation The host has sent an offload restart request with too many defined interfaces.
Recommended Action The 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 on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OFFL-6-LONGREC : Attempt to transmit too large a record
Explanation The amount of data being read by the channel exceeded the size of the read channel command word. The 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 API link. The 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 the offload configuration command of your CMCC. Correct your configuration so the two IP addresses match.
Error Message%OFFL-0-NOMBUF : Out of mbuf's for handling socket operations
Explanation 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 and issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-NOMEM : Not enough memory to start offload tasks
Explanation 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 CMCC, or configure fewer devices.
Error Message%OFFL-3-NOMEMSOCK : Not enough memory to process socket requests, [dec] open, [dec] in holddown
Explanation Not enough free memory is available to process a socket request. The socket request failed.
Recommended Action Install more memory for the 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.
Explanation 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 and issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
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, 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
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 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 message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
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 message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OFFL-3-REQFORM : Socket request [dec] uses invalid parameters. Offset [dec]: [hex]
Explanation The host sent a socket request with an invalid parameter. The CMCC responded with an error code.
Recommended Action Check to see 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 on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-3-REQLEN : Socket request [dec] has wrong length [dec]
Explanation The host has sent a socket request with an incorrect length. The CMCC responded with an error code.
Recommended Action Check to see 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 on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
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 CMCC microcode. The CMCC responded with an error code.
Recommended Action Check to see 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 on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
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 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 message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OFFL-4-SOCLEFT : [dec] Sockets found after shutdown
Explanation 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 message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-6-SOCREQ : Unrecognized socket request code [dec]
Explanation The host sent an offload socket request with an invalid request code. The 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 has received bad data.
Recommended Action Check to see 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 on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
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 eight aliases per offload device.
Recommended Action If the number of existing aliases is less than the allowed maximum, 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-6-TRDISA : Offload PKTTRACE disabled.
Explanation The mainframe TCP/IP has disabled PKTTRACE tracing. This can occur because the 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]).
Explanation 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]).
Explanation 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 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 CMCC. The CMCC ignored the request.
Recommended Action Check to see 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 on the console or in the system log. Issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-6-VIRTOFFL : Offload device may not be created on a virtual port adapter
Explanation 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 required.
Error Message%OFFL-6-WRCHAIN : Received too long message, xfer_element [hex] chains to [hex]
Explanation The offload application received a message on the CLAW control link or the IP link that consisted of more than 16 CLAW buffers. This is not supported.
Recommended Action If this error is reproducible, 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OFFL-6-WRITEREAD : Host Wrote data on read subchannel.
Explanation 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 the system is 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 sequence
Explanation 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 and issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
CMCC PACK Messages
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 CLAW link, and the length did not match that of a known packed control message.
Recommended Action Get a 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. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-0-BADSIZE : Invalid size in connnection request- [dec] R, [dec] W; defined - [dec] R [dec] W
Explanation 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 Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-0-BADSIZE2 : Packed type names:"[chars]" - "[chars]"
Explanation The specified packed type names have experienced a BADSIZE-PACK error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 CMCC.
Recommended Action Correct the host configuration or upgrade the CMCC microcode to a version that supports the packed type specified by the host.
Error Message%PACK-0-BADTYPE2 : Supported packed type names: "[chars]" - "[chars]"
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 CMCC.
Recommended Action Correct the host 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 CLAW message from the host is not the same as the version specified in the CMCC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-6-COMMAND : Unrecognized CLAW packing control command code [dec].
Explanation The host has sent a CLAW packing control command with an invalid command code.
Recommended Action The CMCC has ignored the request. Get a 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 CLAW packed control message sent by the CMCC.
Recommended Action Check the return code and correct IT 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 GTF and a channel trace to verify that the host is sending the bad packed messages.
Error Message%PACK-3-ILLEN2 : Received zero length packed message.
Explanation 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 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]
Explanation 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 error should not occur.
Recommended Action The 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 pool has failed. This is a design error. There should always be enough memory buffers for packed CLAW data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-3-NOMORE : Packed sublink [dec] doesn't support the more bit
Explanation 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 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 CLAW packing sublink that was not established.
Recommended Action The 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 An attempt to disconnect a CLAW packing sublink has failed because the CLAW packing sublink ID is not in the valid range for all CLAW packed sublinks.
Recommended Action The 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 CLAW packing sublink ID in a packed message is not in the valid range for all CLAW packed sublinks.
Recommended Action The 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 length
Explanation An invalid parameter was received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-0-SYSMGT_ERROR2 : CLAW detected error in sysmgt call: invalid CLAWPACK SUBLINK length
Explanation An invalid parameter was received in a system management call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PACK-3-TOOBIG : Received packet [dec], packed header [dec], negotiated frame [dec], dropped the packet
Explanation The received packet together with the packed header is larger than negotiated CLAW read frame size, and the packet has been dropped.
Recommended Action Set the IP MTU to the negotiated CLAW frame size that is specified in the error message text, less 4 (for the CLAW packed header).
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 GTF and a channel trace to verify that the host is sending the bad packed message.
CMCC PCPA Messages
The CIP, CIP2, ECPA, ECPA4, and PCPA messages all use the same message format. For details on how to locate and interpret these messages, refer to CMCC CIP and CIP2 Messages.
CMCC PKTS Messages
The following are channel adapter error messages that are related to the packet switching API.
Error Message%PKTS-3-BUFLEN : Zero length buffer detected in [chars] for [chars]([hex])
Explanation An application buffer error has been detected in the channel adapter packet-switching API.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact 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 API.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%PKTS-3-INIT : [chars] ([dec])
Explanation The CMCC packet switching initialization has failed because of a 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 an the CMCC card is capable of supporting the configured CMCC microcode.
Error Message%PKTS-3-NOSUPP : [chars] ([hex],[hex])
Explanation An attempt was made to call a function in a packet-switching 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, contact 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 was made to call a function in a packet-switching API before the initialization of the API was complete.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact 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. The packet is being dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CMCC SCB Messages
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 ignored
Explanation An attempt has been made to free 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, contact 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]
Explanation A task waiting for a channel 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]
Explanation A task tried to allocate a channel 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 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.
CMCC SCHED Messages
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 allowed
Explanation A request was made to create a task, but the priority level for the task was not valid. The task was not created.
Recommended Action Tasks get created either at 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 were being created, the CIP may not be fully functional. Note the steps necessary to recreate the problem, 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 help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-0-INVLOCK1 : Invalied lock word of [dec] used in lock request
Explanation 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 and issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-0-INVLOCK2 : Invalied lock word of [dec] used in unlock request
Explanation 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 and issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-0-NMLDATA : tcb_addr = [hex] current_tcb = [hex] lock_value = [dec]
Explanation This message contains data that relates to the SCHED-0-NOTMYLOCK message.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the error messages and issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-0-NOLOCK : Attempt was made to unlock resource that wasn't locked
Explanation An attempt was 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 and issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-0-NOPROCID : No process id available for process creation
Explanation An attempt has been made to create one more task than the CIP is designed to allow. The task was not created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, 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 memory
Explanation 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 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 memory
Explanation 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 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. In this case, install more memory for the CIP.
Error Message%SCHED-0-NOTMYLOCK : Attempt was made to unlock another task's resource
Explanation 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 and issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-0-NOTPROCES : Attempt was made to lock while not at process level
Explanation 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 and issue the show tech-support command to gather data that may help identify 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, contact your Cisco technical support representative and provide the representative with the gathered information.
CMCC SLC Messages
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 failed
Explanation After the serial link controller had serviced an NMI from a parallel 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SLC-3-SCANEP1 : Scan of EP ring 1 failed
Explanation An attempt to scan the first set of internal latches on the ESCON processor has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SLC-3-SCANEP2 : Scan of EP ring 2 failed
Explanation An attempt to scan the second set of internal latches on the ESCON processor has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SLC-3-SCANSLC : Scan of SLC ring failed
Explanation 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SLC-3-STOPBIDITO : Stop BIDI clock timed out
Explanation An attempt was made to stop the clock on the interface between the ESCON processor and the serial link controller. The serial link controller did not indicate that the BIDI clock was stopped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SLC-3-STOPEPTO : Stop EP clock timed out
Explanation An attempt was made to stop the clock on the ESCON processor. The serial link controller did not indicate that the clock was stopped. The CIP attempted to stop the BIDI clock.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CMCC SLCI Messages
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 code
Explanation An MPC process has received a transfer list containing an unrecognized type code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 VTAM will receive an error indication and should retry the operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SLCI-0-STASH_EMPTY : Stash empty on read complete
Explanation A read operation has completed, but no data has been stashed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CMCC SSI802 Messages
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 CSNA has encountered unrecoverable error conditions that prevent it from continuing normal operations.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SSI802-3-RTN_ADR : Return Address: [hex]
Explanation This is a debug feature to show the return address when an ASSERT operation is used in an inline function.
Recommended Action Refer to the recommended action from the subsequent error.
CMCC SUBSYS Messages
The following are software subsystem error messages.
Error Message%SUBSYS-2-BADCLASS : Bad subsystem clas ([dec]) - ignoring subsystem
Explanation A software consistency check has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SUBSYS-2-BADSEQUENCE : Subsystem ([chars]) has cross-class sequence for ([chars])
Explanation A software consistency check has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SUBSYS-2-BADVERSION : Bad subsystem version number ([dec]) - ignoring subsystem
Explanation A software consistency check has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SUBSYS-2-MAXRECUR : Too many levels of recursion
Explanation A software consistency check has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SUBSYS-2-MISMATCH : Kernel and subsystem version differ ([dec].[dec]) - ignoring subsystem
Explanation A software consistency check has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SUBSYS-2-NOTFOUND : Subsystem ([chars]) needs subsystem ([chars]) to start
Explanation A software consistency check has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CMCC SYS Messages
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 specified location.
Recommended Action If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-3-BADFREEMAGIC : Corrupt free block at [hex] (magic [hex])
Explanation A block of memory is corrupt at the specified location.
Recommended Action If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-3-BADFREEPTRS : Bad [chars] pointer [hex] at [hex] ([chars] = [hex])
Explanation A pointer in the block header at the specified location is corrupt.
Recommended Action If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-3-BADMAGIC : Corrupt block at [hex] (magic [hex])
Explanation The free memory pool is corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-2-BADSHARE : Bad refcount in [chars], ptr=[hex], count=[hex]
Explanation An internal software error has occurred.
Recommended Action If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-3-CACHE_DIRTY_ADR : cache line [hex] dirty, task: [chars]
Explanation This error message reports the address at which a scan cache operation detected that the cache had not been flushed as expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-6-CACHE_DIRTY_MSG : [chars][chars]
Explanation This message provides additional information about the CACHE_DIRTY_ADR message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-3-CACHED_PAGE_ADR : Uncached page pointer [hex] in call to return_page_inline
Explanation The pointer to a page being returned to the page pool was a cached address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-2-FREEBAD : Attempted to free memory at [hex], not part of buffer pool
Explanation An internal software error has occurred.
Recommended Action If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 technical support representative for assistance.
Error Message%SYS-3-INUSEFREE : Block [hex] on free list [dec] in use
Explanation An internal software error has occurred.
Recommended Action If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-3-INVMEMINT : Invalid memory action ([chars]) at interrupt level
Explanation A memory allocation or deallocation has been attempted from an interrupt handler.
Recommended Action If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-2-LOWMEM : Low memory debug exception (limit=[int] free=[int])
Explanation The CIP is running short of memory.
Recommended Action It may be necessary to free some memory by exiting a program. If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-2-MEMTOOSMALL : CIP software requires a minimum of 8MB of DRAM
Explanation The CIP software has become large enough that it will not run with only 2 MB of DRAM.
Recommended Action Contact your Cisco support representative for a free 8-MB upgrade.
Error Message%SYS-6-MTRACE : [chars]: addr,pc\n [hex],[hex] [hex],[hex] [hex],[hex] [hex],[hex]\n [hex],[hex] [hex],[hex] [hex],[hex] [hex],[hex]
Explanation The free memory pool is corrupted.
Recommended Action If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-3-OVERRUN : Block overrun at [hex] (redzone [hex])
Explanation An internal software error has occurred.
Recommended Action If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SYS-5-RELOAD : Reload requested
Explanation A reload or restart has been requested.
Recommended Action No action is required.
Error Message%SYS-5-RESTART : System restarted --\n[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 messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CMCC SYSMGT_EVENT Messages
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 messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CMCC SYSMGT_RPC Messages
The following are error messages that relate to network management processing for system management remote-procedure call (RPC) operation.
Error Message