CIP System Error Messages

The system can report error conditions in numerous facility codes related to the Channel Interface Processor (CIP). As shown in the following example, the format of the error messages for the CIP differs from the format of other system error messages:

%CIP3-6-MSG:%ADAPTER-6-DIAGBEGIN: [chars] diagnostic starting

All CIP-related error messages begin with a percent sign (%), the facility code CIP, and a number (3 in the preceding example) that indicates the slot where the CIP is installed. The message severity level, 6, follows the slot number along with the mnemonic MSG. This format parallels the format for other system error messages, but it indicates that the CIP generated an error message.

The information that follows the initial error message is the CIP facility subcode, severity level, and mnemonic (%ADAPTER-6-DIAGBEGIN in the preceding example).

The CIP error messages are organized alphabetically into sections by subfacility, beginning with CIP-ADAPTER. Within each subfacility section, messages appear alphabetically by mnemonic.

Note CIP and the slot number are not shown in the error message listings that follow.

CIP-ADAPTER Error Messages

CIP error messages for the adapter task

Error Message
%ADAPTER-6-BADREQUEST : Bad request code [dec] generated on port [dec]

Explanation A request was sent to the function that handles general requests for the specified port. The request code was not in a range recognized by that function.

Recommended Action The CIP recovered by ignoring the request. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%ADAPTER-6-BADSTATE : Bad state: port [dec], request code [dec], state [dec], flags [hex]

Explanation The specified port was in an invalid state while it attempted to process the specified general request.

Recommended Action The CIP recovered by forcing the port into a well-known state. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%ADAPTER-6-DIAGBEGIN : [chars] diagnostic starting

Explanation The user has used the test cbus command to request a particular adapter diagnostic to be run. This message is to inform the user that the diagnostic routine has started.

Recommended Action Wait for the next message.

Error Message
%ADAPTER-0-DIAGDATA : Module Call: [hex][hex] Error ID: [hex][hex], MSGDEF_LIMIT_FAST

Explanation A diagnostic routine has detected a failure in the ESCON channel adapter (ECA) hardware. These codes are used to locate the specific component that failed.

Recommended Action Report this message to your technical support representative.

Error Message
%ADAPTER-6-DIAGDATA2 : Module Call: [hex][hex] Error ID: [hex][hex]

Explanation A diagnostic routine has detected a failure in the ESCON channel adapter (ECA) hardware. These codes are used to locate the specific component that failed.

Recommended Action Report this message to your technical support representative.

Error Message
%ADAPTER-0-DIAGFAIL : Port [dec] failed the [chars] diagnostic, MSGDEF_LIMIT_FAST

Explanation A diagnostic routine has failed. The specified port will not be used.

Recommended Action Report this message to your technical support representative.

Error Message
%ADAPTER-6-DIAGFAIL2 : [chars] diagnostic failed

Explanation A diagnostic requested by the test cbus command failed.

Recommended Action Report this message to your technical support representative.

Error Message
%ADAPTER-6-DIAGGOOD2 : [chars] diagnostic ran successfully

Explanation A diagnostic requested by the test cbus command completed successfully.

Recommended Action No action is required.

Error Message
%ADAPTER-6-DIAGRANGE : Diagnostic number ([dec]) out of range 0-[dec]

Explanation The diagnostic number requested by the test cbus command is not a valid diagnostic number.

Recommended Action Enter the command again with a valid diagnostic number.

Error Message
%ADAPTER-6-DIAGSTOP : Interface must be shutdown to run diagnostic

Explanation The test cbus command was used to run a diagnostic on an active interface.

Recommended Action Use the shutdown command to stop the interface and then reissue the diagnostic request.

Error Message
%ADAPTER-0-DIAGTERM : Port [dec]: The [chars] diagnostic failed to terminate, MSGDEF_LIMIT_FAST

Explanation A diagnostic routine did not complete execution. The specified port will not be used.

Recommended Action Report this message to your technical support representative.

Error Message
%ADAPTER-6-DIAGTERM2 : [chars] diagnostic failed to terminate

Explanation A diagnostic requested via the test cbus command did not terminate.

Recommended Action Report this message to your technical support representative.

Error Message
%ADAPTER-0-LOADFAIL : Port [dec] microcode load failed

Explanation Each adapter has an onboard microprocessor. This message indicates that the operation to load the code for that microprocessor failed.

Recommended Action Report this message to your technical support representative.

Error Message
%ADAPTER-6-LOGDATA : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation An error occurred in the adapter. The information displayed will help personnel in software development to determine the nature of the error.

Recommended Action Report this message to your technical support representative.

Error Message
%ADAPTER-6-LOGOUT : Port [dec] logout data. Adapter microcode [hex]

Explanation This message is displayed at the start of the logout data. Logout data occurs whenever a problem is detected on the port adapter or, with an ESCON channel adapter (ECA), on the fiber.

Recommended Action If this message is being continually generated on a new installation, it may be an indication that the fiber is not connected properly. Verify that the connector is firmly seated. If a loose fiber was not the cause of these messages, report this message to your technical support representative.

Error Message
%ADAPTER-6-LOGSAME : [hex] to [hex] same as above

Explanation This message is used when logout information is displayed in order to avoid printing duplicate data.

Recommended Action Report this message to your technical support representative.

Error Message
%ADAPTER-6-NO_CHAN_EV_BUF : No channel event buffer: Daughter board [dec], 60*ONESEC

Explanation Channel link incident events are being dropped by the channel adapter because of an overflow of incidents.

Recommended Action Use SNMP get to poll the CIP for the current link incident report (LIR) counts.

Error Message
%ADAPTER-6-NO_CHAN_EV_POOL : Could not allocate channel event pool

Explanation There is insufficient memory on the channel adapter to allocate buffers used for generating channel adapter events. Unless the memory is increased, no channel link incident events (SNMP trap) will be generated.

Recommended Action Report this error to your technical support representative.

Error Message
%ADAPTER-6-SCAN : Port [dec] scan data. Adapter microcode [hex]

Explanation This message precedes SCANDATA for the adapter in the specified port. This scan is usually produced as a result of a hardware error.

Recommended Action Report the entire error message and SCANDATA to your technical support representative.

Error Message
%ADAPTER-6-SCANDATA : [hex] [hex] [hex] [hex] [hex]

Explanation The data in this message is related to a hardware failure of an adapter.

Recommended Action Report the entire error message and scan data to your technical support representative.

Error Message
%ADAPTER-0-START_FAIL : Diagnostics failed for port [dec], start request ignored

Explanation Prior to the adapter receiving a start command from the route processor, a set of diagnostics is run. If one of them fails, the adapter will not be started when the start command is issued.

Recommended Action Report this message to your technical support representative.

Error Message
%ADAPTER-6-WRAP : Wrap plug detected in port [dec]. Wrap loop started., MSGDEF_LIMIT_FAST

Explanation A wrap plug is installed in the specified port. Wrap diagnostics will run until the plug is removed if this is the only adapter, or if both adapters have wrap plugs installed.

Recommended Action Remove the wrap plug and connect the interface to a channel.

Error Message
%ADAPTER-6-WRAPSTOP1 : Wrap plug removed from port [dec]. Wrap loop ended., MSGDEF_LIMIT_FAST

Explanation The wrap plug has been removed, causing the wrap diagnostics to terminate.

Recommended Action No action is required.

Error Message
%ADAPTER-6-WRAPSTOP2 : Port [dec] active. Port [dec] wrap loop ended., MSGDEF_LIMIT_FAST

Explanation The wrap diagnostics have been terminated because the other adapter is active.

Recommended Action Remove the wrap plug and connect the interface to a channel if you want to use this adapter. Otherwise, no action is required.

CIP-BSQ Error Messages

CIP error messages for buffer status queue processing

Error Message
%BSQ-0-INCMPLT_XFER : Incomplete Data Transfer received for non-read operation

Explanation An Incomplete Data Transfer Notice was received for a channel command word (CCW) that did not perform a read, or read backward. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Error Message
%BSQ-0-MTC_CHAIN : Incomplete More-To-Come chain queued

Explanation Could not find the end of a more-to-come chain. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Error Message
%BSQ-0-SCB_CHAIN : Read SCB chain is out of sequence

Explanation The sequence of buffer status queue entries received for read commands does not match the sequence of the storage control blocks used for the reads. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

CIP-CBUS_ATTN Error Message

CIP error message relating to the CBUS_ATTN routine, the facility that receives configuration requests and gathers statistics

Error Message
%CBUS_ATTN-3-BADADDR : Bad memory address ([hex]) requested

Explanation The route processor (RP) requested that the CIP store a configuration command at an invalid memory address. The CIP recovered by ignoring the request.

Recommended Action Report this error to your technical support representative.

CIP-CBUS_WRITE Error Messages

CIP error messages for the CBUS_WRITE facility, which is used by the enhanced online insertion and removal (EOIR) support on the CIP to track write operations to the memory device and reissue them if a ciscoBus problem occurs

Error Message
%CBUS_WRITE-3-BADTYPE : Invalid write type [dec]

Explanation The type parameter in the write tracking table is invalid. This is an internal CIP logic error. The CIP recovered by ignoring the entry.

Recommended Action Report this error to your technical support representative.

Error Message
%CBUS_WRITE-3-INVALID : Valid bit not set in IO exception register ([hex])

Explanation A write error interrupt occurred, but the hardware that keeps track of the address of the error does not have a valid address.

Recommended Action Report this error to your technical support representative.

Error Message
%CBUS_WRITE-3-MISSING : Entry for address [hex] not found

Explanation A write error was detected, but there was no corresponding entry in the table that keeps track of these entries. This is an internal CIP logic error. The CIP recovered by ignoring the write error.

Recommended Action Report this error to your technical support representative.

Error Message
%CBUS_WRITE-3-STACK : [dec] [dec] [hex] [hex] [hex]

Explanation This is a debugging print of the CBUS write stack. It is associated with the CBUS_WRITE-3-MISSING error message.

Recommended Action Report this error to your technical support representative.

Error Message
%CBUS_WRITE-3-UNEXPECTED : Unexpected IO write error. Address=[hex]

Explanation A write operation to an address other than the memory device (MEMD) timed out. This is probably a hardware problem. The CIP failed and attempted to restart.

Recommended Action Record the address indicated in the error message. The address will enable a support representative to determine which component to replace. Report this error to your technical support representative.

CIP-CCA Error Messages

CIP error messages for channel card adapter processing

Error Message
%CCA-3-ACR : Accept command response status received

Explanation The adapter notified the CIP that an accept command response was issued. The CIP does not request notification of accept command response messages. Therefore, this message means the adapter has generated an unexpected message.

Recommended Action Normal processing will resume, but it would be useful for software development personnel to know that this message has occurred. Report this message to your technical support representative.

Error Message
%CCA-0-BADCCA : Undefined CCA code received CCA=[hex] [hex]

Explanation The adapter presented the CIP with a message using an undefined code point. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Error Message
%CCA-0-BSQ_FULL : Buffer status queue is full

Explanation The adapter notified the CIP that the buffer status queue was full. The CIP never provides enough buffers to the adapter to cause the buffer status queue to become full. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Error Message
%CCA-3-BYPASS : Select bypass switch may be in bypass position for port [dec]

Explanation A user attempted to start the parallel channel adapter (PCA) with the select bypass switch in the BYPASS position. The PCA cannot go online with the switch in the BYPASS position.

Recommended Action Move the select bypass switch on the PCA-Y cable from the BYPASS position to the SELECT position.

Error Message
%CCA-3-CANCEL1 : Invalid cancel code ([hex])

Explanation The adapter notified the CIP that a halt subchannel command was issued by the host, but provided the CIP with an undefined type of cancel.

Recommended Action The CIP software recovered, but software development personnel should be informed. Report this message to your technical support representative.

Error Message
%CCA-3-CANCEL2 : Cancel received for undefined path ([hex])

Explanation The adapter notified the CIP that a halt subchannel command was issued by the host for an undefined path. This is an internal logic error.

Recommended Action The CIP software recovered, but software development personnel should know about this problem. Report this message to your technical support representative.

Error Message
%CCA-3-COMMAND_PATH : Command connection received for undefined path ([hex])

Explanation The adapter notified the CIP that a start subchannel command was issued by the host for an undefined path. This is an internal logic error.

Recommended Action The CIP software recovered, but software development personnel should know about this problem. Report this message to your technical support representative.

Error Message
%CCA-3-CONN_RESULT : Connection result for device [hex][hex] expected [hex][hex]

Explanation The adapter notified the CIP that a connection was established for a device other than the one that the CIP had just requested. This is an internal logic error.

Recommended Action The CIP software recovered, but software development personnel should know about the problem. Report this message to your technical support representative.

Error Message
%CCA-0-DEV_ERR1 : Undefined device error type ([hex])

Explanation When a device error occurs, the adapter specifies the type of error so that the correct recovery action can be performed. The type specified is not defined. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Error Message
%CCA-0-DEV_ERR2 : Device error but no active defined device

Explanation A device error was generated and either it occurred while status was being presented but no device was active, or it occurred for an undefined device. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Error Message
%CCA-0-DEV_ERR3 : Device error received for undefined path ([hex])

Explanation A device error occurred, but the path specified in the device error message is not defined. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Error Message
%CCA-3-DEV_ERR4 : Control Unit Busy timer wasn't started for device [hex][hex]

Explanation During a device-level error, the control unit busy statistic was not updated because the timer was never started.

Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.

Error Message
%CCA-3-END_STATUS : Ending status interrupt received for [hex] CCW

Explanation The adapter reported an ending status interrupt for a channel command word that should not have caused the CIP to be notified. This is an internal logic error.

Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.

Error Message
%CCA-3-LOGOUT : Invalid logout command modifier ([hex])

Explanation The adapter sent a request to the CIP to perform a logout, but the command modifier in the message was not a valid value. This is an internal logic error.

Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.

Error Message
%CCA-3-REQUEST_STATUS : Request status received for undefined path ([hex])

Explanation The adapter requested that the CIP present the status of an undefined path. This is an internal logic error.

Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.

Error Message
%CCA-3-RESET_PATH : Reset received for undefined path ([hex])

Explanation The adapter has requested the CIP to perform reset processing for an undefined path. This is an internal logic error.

Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.

Error Message
%CCA-3-RLP1 : Invalid rlp flags ([hex])

Explanation The adapter requested that the CIP reset a logical path, but the flags on the reset request were not valid. This is an internal logic error.

Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.

Error Message
%CCA-0-SCBNRDY : Unexpected SCB not ready CCA=[hex] [hex]

Explanation The CIP was notified that an I/O operation was attempted with a storage control block that was marked as not ready. The specified I/O operation should never have a not ready storage control block. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

Error Message
%CCA-3-SEL_RESET1 : Invalid selective reset code ([hex])

Explanation The adapter requested that the CIP perform a selective reset, but the request code in the message was not a valid value. This is an internal logic error.

Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.

Error Message
%CCA-3-SEL_RESET2 : Selective reset received for undefined path ([hex])

Explanation The adapter has requested that the CIP perform a selective reset on an undefined logical path. This is an internal logic error.

Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.

Error Message
%CCA-3-STATUS_NOTICE : Undefined status notice request code [hex]

Explanation The adapter has presented the CIP with notification that status was accepted by the channel, but the request code in the status message was not a valid code. This is an internal logic error.

Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.

Error Message
%CCA-3-STATUS_NOTICE2 : Control Unit Busy timer wasn't started for device [hex][hex]

Explanation During status presentation, the control unit busy statistic was not updated because the timer was never started.

Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.

Error Message
%CCA-3-SYS_RESET : Invalid system reset code ([hex])

Explanation The adapter requested that the CIP perform a system reset, but the request code in the message was not a valid value. This is an internal logic error.

Recommended Action The CIP software has recovered, but software development personnel should be notified of the problem. Report this message to your technical support representative.

Error Message
%CCA-0-TOOMANY : Too many buffers ([dec]) required for a write operation

Explanation The mainframe wrote data to the CIP and the number of buffers required to hold all the data being written was more than the total number of buffers allocated on the CIP for that purpose. This is a fatal error.

Recommended Action Report this message to your technical support representative.

Error Message
%CCA-3-WRAPPLUG : Wrap plug is installed on port [dec]

Explanation The wrap plug is installed on the parallel channel adapter (PCA) in the specified port. The PCA cannot be used unless connected to a channel.

Recommended Action Remove the wrap plug and connect the channel cables.

Error Message
%CCA-0-WRITE_FAIL : Write of response CCA failed

Explanation The adapter requested that the CIP perform a request. When the CIP tried to present the response to the request, it was not able to write the common communication area. This is a fatal internal logic error.

Recommended Action Report this message to your technical support representative.

CIP-CIOS Error Messages

Channel adapter IOS wrappers error messages

Error Message
%CIOS-3-BADPAK : pak=[hex], size=[dec]

Explanation An internal software error occurred while generating this message from the Channel Adapter. It indicates that a buffer has been corrupted.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CIOS-3-BADREFCNT : pak=[hex], size=[dec]

Explanation An internal software error occurred while generating this message from the Channel Adapter. It indicates that a buffer has been freed twice.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CIOS-2-BUGINF : Message too big(%lu)

Explanation An internal software error occurred while generating debug messages from the Channel Adapter.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Turn off IPC debugging on the Channel Adapter until this can be fixed.

Error Message
%CIOS-3-CHUNKFREE : [chars] - chunk=[hex] data=[hex]

Explanation An internal software error occurred while generating this message from the Channel Adapter.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CIOS-3-CONSISTENCY : [chars]([hex])

Explanation An internal software error occurred while generating debug messages from the Channel Adapter.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Turn off IPC debugging on the Channel Adpater until this can be fixed.

Error Message
%CIOS-3-MGD_TMR : mgd_timer[chars] not set, 10 * ONESEC

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CIOS-3-NOMEM : Not enough memory to allocate [chars]

Explanation The Channel Adpater is not equipped with enough memory to accommodate all the configured Channel Adapter features. The Channel Adpater may be rendered inoperable, or certain features may not work properly.

Recommended Action Upgrade the Channel Adapter with more memory.

Error Message
%CIOS-3-PROC : process [chars](%lu), 10 * ONESEC

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CIOS-3-TIMERNEG : Cannot start timer ([hex]) with negative offset (%lu)., 10 * ONESEC

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CIOS-3-WI : [chars] - process [chars](%lu)

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

CIP-CLAW Error Messages

CIP error messages related to the Common Link Access for Workstations (CLAW) facility

Error Message
%CLAW-0-BADAPPL : Host Appl. names [chars] - [chars] do not match any configured names.

Explanation An attempt was made to establish a connection, but the application names specified on the host do not match any of the application names specified in the router configuration.

Recommended Action Correct the host and/or router configuration.

Error Message
%CLAW-0-BADAPPL2 : Configured names: [chars] - [chars]

Explanation An attempt was made to establish a connection, but the application names specified on the host do not match any of the application names specified in the router configuration.

Recommended Action Correct the host and/or router configuration.

Error Message
%CLAW-6-BADCHAIN : Too many buffers in an IP Datagram write chain

Explanation All the data sent in an IP datagram should fit in one transfer list element. This message required more than one.

Recommended Action Report this error to your technical support representative.

Error Message
%CLAW-0-BADHNAME : Host system names do not match.Host is [chars]. Control Unit is [chars]

Explanation During the system-validate processing, the host name configured in the router did not match the host name configured on the host.

Recommended Action Correct the host and/or router configuration.

Error Message
%CLAW-0-BADRSIZE : Host read frame size of [dec] is less than Control Unit size of [dec]

Explanation The host is configured to receive frames that are smaller than the CIP is designed to send.

Recommended Action The CIP has notified the host of the problem. Reconfigure the frame size on the host to be 4096 or larger.

Error Message
%CLAW-6-BADSVR : System Validate Response had a return code of [dec]

Explanation The host has generated a bad return code in the response to the system-validate request sent by the CIP.

Recommended Action Check the return code and correct the configuration as appropriate.

Error Message
%CLAW-0-BADVERSION : Host CLAW version [dec] does not equal control unit version [dec]

Explanation The version specified in a message from the host is not the same as the version specified in the CIP.

Recommended Action Report this error to your technical support representative.

Error Message
%CLAW-0-BADWNAME : Workstation system names do not match.Host is [chars]. Control Unit is [chars]

Explanation During the system-validate processing, the workstation name configured in the router did not match the workstation name configured on the host.

Recommended Action Correct the host and/or router configuration.

Error Message
%CLAW-0-BADWSIZE : Host write frame size of [dec] is greater than Control Unit size of [dec]

Explanation The host is configured to write more data in a single frame to the CIP than the CIP is designed to receive.

Recommended Action The CIP will notify the host of the problem. Reconfigure the frame size on the host to be 4096 or smaller.

Error Message
%CLAW-6-COMMAND : Unrecognized CLAW command code [dec]. xfer_element = 0x[hex]

Explanation The host sent a CLAW command with an invalid CLAW command code.

Recommended Action The CIP will ignore the request. Report this error to your technical support representative.

Error Message
%CLAW-6-INVALIDLINK : Invalid CLAW link [dec] specified for option [dec]

Explanation The host sent a CLAW option request command for an invalid link.

Recommended Action The CIP will ignore the request. Report this error to your technical support representative.

Error Message
%CLAW-6-LINKEXISTS : An attempt was made to redefine application [chars] [chars], application already defined

Explanation The host sent a CLAW option request to define an application that already exists.

Recommended Action The CIP will ignore the request. Report this error to your technical support representative.

Error Message
%CLAW-6-LONGREC : Attempt to transmit too large a record., MSGDEF_LIMIT_MEDIUM

Explanation The amount of data being read by the channel exceeded the size of the read channel command word (CCW).

Recommended Action Report this error to your technical support representative.

Error Message
%CLAW-6-NOCONN : Channel wrote data on link [dec] without a valid connection. Path=[hex][hex][hex] device=[hex], MSGDEF_LIMIT_GLACIAL

Explanation A packet was received from the host, but the logical link specified with the data does not represent a valid connection.

Recommended Action The packet was dropped. Report this error to your technical support representative.

Error Message
%CLAW-0-NOLINKID : Unable to allocate link id

Explanation An attempt was made to allocate a link ID to assign to a connection request, but all link IDs were in use. This should not occur.

Recommended Action The CIP software has recovered by generating a bad return code to the requester. Report this error to your technical support representative.

Error Message
%CLAW-6-NOTPRESENT : Link [dec] being freed was not present

Explanation The host software attempted to disconnect a link that was not established.

Recommended Action The CIP software has ignored the request. Report this error to your technical support representative.

Error Message
%CLAW-6-NOTXBUF : Unable to allocate txbuf., MSGDEF_LIMIT_GLACIAL

Explanation No available transmit buffers exist, but the CLAW connection has not reached its transmit buffer limit.

Recommended Action The packet has been dropped. Report this error to your technical support representative.

Error Message
%CLAW-6-OPTION : Unrecognized CLAW option request code [dec]

Explanation The host sent an unknown CLAW option request command.

Recommended Action The CIP software has ignored the request. Report this error to your technical support representative.

Error Message
%CLAW-6-RANGE : Link [dec] being freed is out of range

Explanation The link ID in a disconnect is not in the valid range for all CLAW links.

Recommended Action The CIP software has recovered by ignoring this request. Report this error to your technical support representative.

Error Message
%CLAW-6-TOOBIG : [dec] byte IP datagram exceeds CLAW MTU for device [dec]/[hex][hex][hex]/[hex], MSGDEF_LIMIT_GLACIAL

Explanation The router has sent an IP datagram to the CIP that is larger than the maximum transmission unit (MTU) for the CIP. The MTU for the CLAW connection is set on the DEVICE statement for the CLAW device in the host TCPIP configuration file (PROFILE.TCPIP). The IP datagram has been dropped.

Recommended Action Check the configured IP MTU on the CIP, and the host configuration file. If correct, report this problem to your technical support representative.

Error Message
%CLAW-6-TYPE : Unrecognized type code [dec] in CLAW. xfer_element = 0x[hex]

Explanation The request type in a transfer element is not a valid value. This is an internal logic error.

Recommended Action The CIP software has recovered by ignoring the transfer element. Report this error to your technical support representative.

Error Message
%CLAW-6-UNEXPECTED : Unexpected type code [dec] in CLAW. xfer_element = 0x[hex]

Explanation The request type in a transfer element is valid but is not expected to occur at this time. This is an internal logic error.

Recommended Action The CIP software has recovered by ignoring the transfer element. Report this error to your technical support representative.

Error Message
%CLAW-6-VIRTCLAW : CLAW device may not be created on a virtual port adapter

Explanation An attempt was made to configure a CLAW device on the virtual port adapter. CLAW devices are only permitted on real port adapters.

Recommended Action The configuration request was ignored. Report this error to your technical support representative.

CIP-CMPCTG Error Messages

LLC Transmission group error messages

Error Message
%CMPCTG-6-ACTIVE : CMPC-TG [chars] ACTIVE

Explanation This is an informative message given when a CMPC TG is in the active state.

Recommended Action No action is required.

Error Message
%CMPCTG-3-CFG_ERR : TG [chars] configured with invalid Loop Back Sap

Explanation This error message is given when a loop back TG is configured by using the same local and remote SAP values.

Recommended Action For loopback configurations, the local and remote SAPs should be different. Change one of the SAP values.

Error Message
%CMPCTG-3-CFG_FSM_ERR : TG Name: [chars], Event [chars], State [chars]

Explanation This error message is given when an internal state machine attempts to execute an event inconsistent with the state.

Recommended Action Report this error to your technical support representative.

Error Message
%CMPCTG-6-INB_SENSE : CMPC-TG [chars] Inbound Sense [hex]

Explanation This is an informative message given when a CMPC TG notices a CV22 with sense data.

Recommended Action Indicates that an endpoint of the APPN session has detected a protocol problem. No action on this router is required. Check the log for each of the two endpoints and take appropriate action.

Error Message
%CMPCTG-6-INIT : CMPC-TG [chars] initialized

Explanation This is an informative message given when a CMPC TG is initialized. The message indicates which TG has been configured.

Recommended Action No action is required.

Error Message
%CMPCTG-3-LS_FSM_ERR : TG Name: [chars], Event [chars], State [chars]

Explanation This error message is given when an internal state machine attempts to execute an event inconsistent with the state.

Recommended Action Report this error to your technical support representative.

Error Message
%CMPCTG-0-NOADAP : CMPC-TG [chars] attempt to open adapter failed, pc: [hex]

Explanation This message is given when an attempt by CMPC TG to open the Logical Link Control (LLC) adapter failed.

Recommended Action Ensure that the LLC adapter referenced by this TG is configured.

Error Message
%CMPCTG-0-NOMEM : CMPC-TG [chars] attempt to acquire memory failed, pc: [hex]

Explanation A call to create a pool or get a buffer failed.

Recommended Action Report this error to your technical support representative.

Error Message
%CMPCTG-6-NOTACTIVE : CMPC-TG [chars] NOT ACTIVE

Explanation This is an informative message given when a CMPC TG is no longer in the active state.

Recommended Action No action is required.

Error Message
%CMPCTG-6-OUTB_SENSE : CMPC-TG [chars] Outbound Sense [hex]

Explanation This is an informative message given when a CMPC TG notices a CV22 with sense data.

Error Message
%CMPCTG-6-REMOVED : CMPC-TG [chars] removed

Explanation This is an informative message given when a CMPC TG is removed.

Recommended Action No action is required.

Error Message
%CMPCTG-0-SYSMGT_ERROR3 : Llc-Tg detected error in sysmgt call: invalid operation [dec]

Explanation This message is given when an invalid parameter was received in a SYSMGT call.

Recommended Action Report this error to your technical support representative.

Error Message
%CMPCTG-0-SYSMGT_ERROR4 : Llc-Tg detected error in sysmgt call: invalid length

Explanation This message is given when an invalid parameter was received in a SYSMGT call.

Recommended Action Report this error to your technical support representative.

CIP-CONFIG Error Messages

CIP error messages related to the configuration facility

Error Message
%CONFIG-6-BADCONFIG : Bad configuration type ([dec]) in update_tx_max

Explanation The router encountered an unrecognized configuration type when it attempted to update the maximum number of transmit buffers to be used by a device. This is an internal logic error.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-6-BAD_DBTYPE : Bad port type ([dec])

Explanation The port type function returned an invalid port type. This is an internal logic error.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-6-BADDEVT : Bad device type ([dec])

Explanation The device type specified by the route processor in a configuration request is not a valid device type. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-3-BADFLUSH : Buffers not freed prior to shutdown: scb=[hex], addr=[hex]

Explanation During the shutdown processing, buffers were found queued to the channel. One of the device tasks did not properly flush the data prior to shutting down.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-0-BADSPEED : Incorrect PCA speed passed to cbus attention exit routine

Explanation The router has attempted to configure a parallel channel adapter (PCA) with an invalid channel speed.

Recommended Action The CIP has recovered by ignoring the request. Report this error to your technical support representative.

Error Message
%CONFIG-3-BADVCN : Virtual circuit number ([dec]) too large

Explanation The virtual circuit number specified by the route processor on a configuration request is too large. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-3-CLAWDEV : CLAW device address ([hex]) must be even

Explanation The route processor attempted to configure an odd address for a CLAW device. CLAW configuration requests must specify an even address. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-3-CONFIGINIT : Invalid config registry identifier [dec]

Explanation During initialization, each application that will receive configuration commands from the system registers routines to process its configuration commands. An incorrect registration identifier was used.

Recommended Action This is a fatal error. The CIP has been restarted. Report this message to your technical support representative.

Error Message
%CONFIG-3-DIFFDEVT : Device type ([dec]) does not match device [hex] device type ([dec])

Explanation The route processor attempted to reconfigure an existing device without first removing the device. This is an internal logic error. The original configuration remains.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-3-DOWNREV : The [chars] feature is not supported on CIP HW rev [dec].[dec]. Please upgrade your CIP

Explanation A feature was configured that is not supported on this CIP hardware revision. The feature was activated, but is not guaranteed to work properly.

Recommended Action Upgrade your CIP to either a CIP with hardware revision 4.4 or to a CIP2.

Error Message
%CONFIG-3-DUPDEV : Duplicate device address ([hex])

Explanation The route processor attempted to configure an existing device. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-3-DUPVCN : Virtual circuit number already in use. Path=[hex][hex][hex] Device=[hex]

Explanation The route processor attempted to configure a device using a virtual circuit number that was already in use by another device. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-3-DUPVCN2 : VCN [dec] already in use: routine [hex] parm [hex]. No device found.

Explanation The route processor attempted to configure a device using a virtual circuit number that was already in use. There was no device found associated with this virtual circuit number. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-3-NOAPPLSPC : Error allocating storage for application block

Explanation The CIP does not have sufficient storage to allocate an application block. The configuration request was ignored.

Recommended Action Purchase the next-larger storage size for the CIP, or configure fewer devices.

Error Message
%CONFIG-3-NOCONFIG : No configuration routine registered for entry [dec]: [chars]

Explanation Configuration command processing is dynamically set up when features are added to an image. The required feature to process a configuration command is not a part of the current image.

Recommended Action Either run a CIP microcode load that supports the configuration command being issued, or do not issue that configuration command.

Error Message
%CONFIG-3-NOCUI : Control unit image does not exist for [hex][hex]

Explanation The route processor attempted to unconfigure a device, but the control unit image for the device could not be located. This is an internal logic error. The unconfigure request was ignored.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-3-NODEV : Device [hex] is not defined

Explanation The route processor attempted to unconfigure a device, but the device was not defined. This is an internal logic error. The unconfigure request was ignored.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-3-NODEVSPC : Error allocating storage for device block

Explanation No storage was available for the device block. The configuration request is ignored.

Recommended Action Purchase the next-larger storage size for the CIP, or configure fewer devices.

Error Message
%CONFIG-3-NOFREEPATH : No free paths - only 64 may be specified

Explanation An attempt was made to configure more than 64 different paths. Only 64 paths are supported. The configuration request was ignored.

Recommended Action Configure fewer paths.

Error Message
%CONFIG-3-NOPATHSPC : Error allocating storage for logical path table

Explanation No storage was available for the logical path table. The configuration request was ignored.

Recommended Action Purchase the next-larger storage size for the CIP, or configure fewer devices.

Error Message
%CONFIG-3-NOSPACE : No space to build configuration confirmation

Explanation Whenever the system sends a configuration command to the CIP, it responds with a confirmation message. There was not sufficient available memory on the CIP to allocate a block to hold a confirmation message.

Recommended Action If you are not at the maximum CIP memory configuration, additional memory may be installed on the CIP. Otherwise, configure fewer channel connections.

Error Message
%CONFIG-3-NOVCN : Virtual circuit number ([dec]) is not defined

Explanation The route processor attempted to unconfigure a device, but the virtual circuit number for the device is not defined. This is an internal logic error. The unconfigure request was ignored.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-3-OFFLDEV : OFFLOAD device address ([hex]) must be even

Explanation The route processor attempted to configure an odd address for an offload device. Offload configuration requests must specify an even address. This is an internal logic error. The configuration request was ignored.

Recommended Action Report this message to your technical support representative.

Error Message
%CONFIG-3-STATEINIT : Too many state change notification routines

Explanation During initialization, each application that uses the virtual port adapter registers to receive notification when the shutdown or no shutdown commands are issued on that adapter. The table to hold these registration requests is too small.

Recommended Action This is a fatal error. The CIP has been restarted. Report this message to your technical support representative.

Error Message
%CONFIG-3-TOOMANYDEV : Too many devices defined. Only 256 may be used

Explanation An attempt was made to define more than 256 devices. Only 256 devices are supported on an adapter. The configuration request was ignored.

Recommended Action Configure fewer devices.

Error Message
%CONFIG-3-UNEXPCFG : Configuration command code [dec] is not supported

Explanation Configuration command processing is dynamically set up when features are added to an image. The required feature to process a configuration command is not a part of the current image.

Recommended Action Either run a CIP microcode load that supports the configuration command being issued, or do not issue that configuration command.

Error Message
%CONFIG-3-WORKLEFT : Work pending on work queue when device terminated

Explanation Work was pending when the router finished processing an unconfigure request. This is an internal logic error.

Recommended Action Report this message to your technical support representative.

CIP-CTA Error Messages

CIP error messages for the channel transport architecture device task/mapper

Error Message
%CTA-6-BADCHAIN : PA[dec] CTA [hex]-[hex] Too many buffers in a CSNA write chain

Explanation All the data sent in a CSNA write should fit in one transfer list element. This message required more than one.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-ERRSTASH : PA[dec] CTA [hex]-[hex] buffer 0x[hex] not in stash, pc: 0x[hex]

Explanation An error has been detected in the processing of host-bound messages.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-ERRSTATE1 : PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]

Explanation A host write was received while the setup state equalled "pending open."

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-ERRSTATE2 : PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]

Explanation A host read was received while the setup state equalled "setup open."

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-ERRSTATE3 : PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]

Explanation A host read was received while the setup state equalled "pending complete."

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-ERRSTATE4 : PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]

Explanation A host write was received while the setup state equalled "setup complete."

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-6-FLUSH : PA[dec] CTA [hex]-[hex] Read data flushed

Explanation Because of an error on the channel, some data intended to be sent to the channel was not sent to the channel. Virtual Telecommunications Access Method (VTAM) will receive an error indication and should retry the operation.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-INACTIVE : PA[dec] CTA [hex]-[hex] reset after being inactive for [dec] seconds

Explanation This subchannel has been inactive for more than the subchannel timeout interval. Most likely, the host has been halted or Virtual Telecommunications Access Method (VTAM) has been terminated by a Z NET,CANCEL command.

Recommended Action Restart the VTAM/HOST and activate the XCA major node.

Error Message
%CTA-6-INIT : PA[dec] CTA [hex]-[hex] Device initialized

Explanation This is an informative message given when a CSNA device is initialized. The device string is in the form CSNAx/yyyy/zz, where x is the daughter board number, yyyy is the path, and zz is the device number.

Recommended Action No action is required.

Error Message
%CTA-6-LONGREC : PA[dec] CTA [hex]-[hex] 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 (CCW).

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-MSGERR1 : PA[dec] CTA [hex]-[hex] mismatch between channel block size and msg counts

Explanation An error occurred in the message from the host, as indicated by the description.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-MSGERR2 : PA[dec] CTA [hex]-[hex] msg size less than DLC hdr size

Explanation An error occurred in the message from the host, as indicated by the description.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-MSGERR3 : PA[dec] CTA [hex]-[hex]

Explanation A received CTA command code is not in the valid range.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-NOMEM : CTA attempt to acquire memory failed, pc: [hex]

Explanation A call to create a pool or get a buffer failed.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-QUEUE_ERROR : PA[dec] CTA [hex]-[hex] attempt to init or alloc a queue failed at 0x[hex]

Explanation A queue init/alloc failed.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-6-SHUTDOWN : PA[dec] CTA [hex]-[hex] Device shutdown

Explanation This is an informative message given when a CSNA device is shutdown. The device string is in the form CTA n/mmmm/yy, where n is the daughterboard number, mmmm is the path, and yy is the device number.

Recommended Action No action is required.

Error Message
%CTA-0-SYSMGT_ERROR1 : CTA detected error in sysmgt call: invalid CSNA DEVICE length

Explanation An invalid parameter was received in a SYSMGT call.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-SYSMGT_ERROR2 : CTA detected error in sysmgt call: invalid LLC2 CONN length

Explanation An invalid parameter was received in a SYSMGT call.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-SYSMGT_ERROR3 : CTA detected error in sysmgt call: invalid CSNA type

Explanation An invalid parameter was received in a SYSMGT call.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA_TEST_TOOL-3-INVALIDLEN : CTA Test-Tool configured incorrectly for a CTA command, cmd: [hex]

Explanation The offset and length of a cta-test-tool command was out of range for a CTA command buffer. The CTA command will not be processed by the CTA Test-Tool.

Recommended Action Verify the cta-test-tool command configured offset and length with the values in the CTA formats and protocol document. If you do not have a configuration error, report this error to your technical support representative.

Error Message
%CTA_TEST_TOOL-3-INVALIDMBUF : CTA Test-Tool detected an invalid CTA command mbuf, cmd: [hex]

Explanation A CTA command mbuf has an invalid format that the CTA Test-Tool cannot identify. The CTA command cannot be processed by the CTA Test-Tool.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA_TEST_TOOL-3-INVALID_CFGBLK_LEN : CTA Test-Tool configuration block length invalid

Explanation A cta-test-tool configuration command was received where the configuration block length was invalid. The configuration command has be ignored.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA_TEST_TOOL-3-NOMEMORY : CTA Test-Tool code could not allocate memory, pc: [hex]

Explanation An attempt was made to allocate memory for the CTA Test-Tool utility. Not enough memory was available at the time the cta-test-tool configuration command was processed on the CIP. The cta-test-tool command will not take affect.

Recommended Action Retry the cta-test-tool configuration command at a later time. Install more memory on the CIP card. If neither of these actions resolves this problem, report the error to your technical support representative.

Error Message
%CTA-0-UNEXP_EVENT : PA[dec] CTA [hex]-[hex] received unrecognized type code 0x[hex] at 0x[hex]

Explanation An XFER element type code not in the valid range was received.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-UNEXP_LSI_CMD : PA[dec] CTA [hex]-[hex] received LSI command 0x[hex] at 0x[hex]

Explanation An LSI command code not in the valid range was received.

Recommended Action Report this error to your technical support representative.

Error Message
%CTA-0-UNEXP_LSI_STATUS : CTA received status 0x[hex] in LSI cmd 0x[hex]

Explanation An LSI status code not valid for the command was received.

Recommended Action Report this error to your technical support representative.

CIP-DEBUGGER Error Messages

CIP error messages issued when nonrecoverable errors occur on the CIP

Error Message
%DEBUGGER-0-CIP_HWVINFO : SNr. [dec] HWRev. [int].[int] EPROM [int].[int] VPLD [int].[int]

Explanation A fatal internal CIP error occurred. The message includes hardware version information.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%DEBUGGER-0-CIP_SWVINFO : [chars] [dec].[dec] [chars]

Explanation A fatal internal CIP error occurred. The message includes software version information.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%DEBUGGER-0-FATAL_ERROR : Fatal error (code=%02d)

Explanation A fatal internal CIP error occurred. The CIP failed.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-INVALID_ADDR : address 0x[hex] is invalid

Explanation The message detects invalid addresses while trying to perform a stack dump.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%DEBUGGER-0-LCORE_DATA : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation The message displays data from the low core area of the CIP.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%DEBUGGER-0-LCORE_START : Dump of lowcore

Explanation The CIP has failed. The low core area of the CIP will begin to dump.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%DEBUGGER-0-RESTART : Restart due to breakpoint

Explanation This indicates the CIP has finished dumping all debugging information and is attempting a restart.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK1 : [hex] [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK2 : [hex] [hex] [hex] [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK3 : [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK4 : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK_DATA1 : [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK_DATA2 : [hex] [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK_DATA3 : [hex] [hex] [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK_DATA4 : [hex] [hex] [hex] [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK_DATA5 : [hex] [hex] [hex] [hex] [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK_DATA6 : [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK_DATA7 : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK_DATA8 : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation This is a line of internal interrupt stack information.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-STACK_DUMP : Task:[chars], base=0x[hex], stack_size=0x[hex], sp=0x[hex]

Explanation The CIP has failed. The current TCB stack area of the CIP will begin to dump.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%DEBUGGER-0-STACK_OVERFLOW : overflow condition detected for this task: [chars]

Explanation The message displays stack information of the stack overflow task.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%DEBUGGER-0-STACK_START : Stack addr: [hex]

Explanation This message begins a dump of the internal interrupt stack. If this has occurred, the CIP has failed.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-TRACE_ADDR : Table:[hex] Next:[hex] First:[hex] Last:[hex] Full:[hex]

Explanation This is a display of the internal trace table header.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-TRACE_DATA : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation This is a single entry from the internal trace table.

Recommended Action Report this to your technical support representative.

Error Message
%DEBUGGER-0-TRACE_START : Dump of trace table

Explanation This message begins a dump of the internal trace table. If this has occurred, the CIP has failed.

Recommended Action Report this to your technical support representative.

CIP-DIAG Error Messages

CIP error messages for diagnostic processing

Error Message
%DIAG-6-BADCODE : Invalid request code ([dec]) to run_diag

Explanation A request was made to run an ESCON channel adapter (ECA) diagnostic, but the number of the diagnostic to run was not valid. This is an internal logic error. The request to run the diagnostic is ignored.

Recommended Action Report this message to your technical support representative.

Error Message
%DIAG-6-BADLOAD : Firmware load error. Unable to run_diag

Explanation A request was made to run an ESCON channel adapter (ECA) diagnostic, but the firmware for the port adapter did not load properly. This is an internal logic error. The request to run the diagnostic is ignored.

Recommended Action Report this message to your technical support representative.

CIP-DMA Error Messages

Error messages for the function on the CIP that is responsible for transferring data between the dynamic RAM (DRAM) on the CIP and memory device facility

Error Message
%DMA-0-BADFIFO : FIFO failure detected during transfer ([dec] [hex])

Explanation An error occurred in one of the hardware FIFOs used in the DMA transfer operation. This failure was detected and resulted in a packet being dropped.

Recommended Action Report this error to your technical support representative.

Error Message
%DMA-3-CBUSERR : CBUS error (no ACK neither NACK) 0x[hex]

Explanation The CBUS controller started a read or write operation and did not receive a response from the CBUS indicating the completion status. The packet was dropped.

Recommended Action Report this error to your technical support representative. This could be an indication that the CIP is not properly seated in its slot.

Error Message
%DMA-3-CBUSPARITY : CBUS parity error 0x[hex]

Explanation A parity error was detected on the CBUS during a data transfer.

Recommended Action The packet has been dropped. Report this error to your technical support representative.

Error Message
%DMA-4-DATAPARITY : DMA Data FPGA parity error 0x[hex]

Explanation A parity error was detected during data transfer.

Recommended Action The packet has been dropped. Report this error to your technical support representative.

Error Message
%DMA-0-INCOMPL : DMA transfer incomplete on interrupt

Explanation The CIP was notified that the current DMA transfer had completed, but the DMA status register indicated the transfer was still in progress.

Recommended Action The CIP has restarted. Report this error to your technical support representative.

Error Message
%DMA-3-LOGICERR : CBUS timeout (10 us) 0x[hex]

Explanation The CBUS did not respond to the DMA controller within 10 microseconds.

Recommended Action The packet has been dropped. Report this error to your technical support representative.

Error Message
%DMA-0-NOXFER : No transfer pending on DMA interrupt

Explanation A DMA interrupt occurred, but no transfer was pending. This is either an internal logic error, or a hardware failure.

Recommended Action The CIP has restarted. Report this error to your technical support representative.

Error Message
%DMA-0-REGISTERS : [hex] [hex] [hex] [hex]

Explanation An error occurred during a DMA transfer. These are the DMA hardware controller registers at the end of the transfer.

Recommended Action Report this error to your technical support representative.

CIP-GET_DATA Error Message

CIP error message related to the internal routine for allocating transfer elements

Error Message
%GET_DATA-0-NOMEMORY : cannot allocate storage for xfer elements

Explanation An attempt was made to allocate a transfer element and no storage was available. This is a fatal error.

Recommended Action The CIP has restarted. Report this error to your technical support representative.

CIP-INT Error Messages

CIP error messages for the interrupt handler interface

Error Message
%INT-0-ADDFAST : Add: Invalid fast io code [dec]

Explanation A request was made to add an interrupt handler to the fast I/O path with an invalid interrupt type. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Error Message
%INT-0-ADDFLIH : Add: Invalid interrupt code [dec]

Explanation A request was made to add an interrupt handler with an invalid interrupt number. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Error Message
%INT-0-ADDFULL : Add: Invalid full io code [dec]

Explanation A request was made to add an I/O interrupt handler with an invalid interrupt code. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Error Message
%INT-0-ADDTRAP : Add: Invalid trap code [dec]

Explanation A request was made to add a system call handler with an invalid system call number. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Error Message
%INT-0-REMOVEFAST : Remove: Invalid fast io code [dec]

Explanation A request was made to remove an interrupt handler from the fast I/O path with an invalid interrupt type. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Error Message
%INT-0-REMOVEFLIH : Remove: Invalid interrupt code [dec]

Explanation A request was made to remove an interrupt handler with an invalid interrupt number. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Error Message
%INT-0-REMOVEFULL : Remove: Invalid full io code [dec]

Explanation A request was made to remove an I/O interrupt handler with an invalid interrupt code. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

Error Message
%INT-0-REMOVETRAP : Remove: Invalid trap code [dec]

Explanation A request was made to add a system call handler with an invalid system call number. This is a fatal internal logic error.

Recommended Action Report this error to your technical support representative.

CIP-IPC Error Messages

CIP error messages related to the interprocess communication (IPC) subfacility

Error Message
%IPC-2-CANT_SEND : Cannot send IPC message: [chars]

Explanation An error occurred in the IPC slave-discovery mechanism. It might result in a malfunction in the operation of the IPC.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.

Error Message
%IPC-4-CONSISTENCY : Message failed consistency check: [chars]

Explanation An internal inconsistency was found in some IPC data structures.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.

Error Message
%IPC-3-DELETED : Attempt to delete an IPC message (0x[hex]) a second time, MSGDEF_LIMIT_FAST

Explanation An internal inconsistency was found in some IPC data structures.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative, along with the output of the show ipc status and show ipc queue commands.

Error Message
%IPC-3-GIANT : Request for giant IPC packet denied. Request size = [dec], MSGDEF_LIMIT_FAST

Explanation Someone requested a message that was too large for the IPC system.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative, along with the output of the show ipc status command.

Error Message
%IPC-2-LOCK : Lock done a deleted element

Explanation An internal inconsistency was found in some IPC data structures.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.

Error Message
%IPC-3-NOBUFF : The [chars] IPC message header cache has emptied

Explanation The given IPC message header cache has emptied.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative, along with the output of the show ipc status command.

Error Message
%IPC-5-NODELFUNC : Delayed init function not available

Explanation The IPC application cannot be initialized because its initialization function does not appear in the IPC initialization function list.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.

Error Message
%IPC-2-NODISPATCH : Message for [dec].[dec] has no receive queue or dispatch routine, MSGDEF_LIMIT_FAST

Explanation The IPC user failed to provide any means of handling the received message.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative, along with the output of the show ipc ports command.

Error Message
%IPC-2-NOMEM : No memory available for [chars]

Explanation The IPC protocol subsystem could not obtain the memory it needed.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.

Error Message
%IPC-2-ONINT : Called from interrupt level: [chars]

Explanation The IPC user attempted a prohibited call into IPC while IPC was running on the interrupt stack.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative, along with the output of the show ipc status command.

Error Message
%IPC-5-SLAVELOG : VIP-[chars]

Explanation The Cisco IOS software, running on a Versatile Interface Processor (VIP) card, generated this message. The error message has been passed up to the Route Processor (RP) or Route Switch Processor (RSP) for display. This message appears only if the user has configured the service slavelog command.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.

Error Message
%IPC-2-UNLOCK : Unlock done on already unlocked element

Explanation An internal inconsistency was found in some IPC data structures.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.

CIP-IPC_CBUS Error Messages

CIP error messages related to the IPC cBus system

Error Message
%IPC_CBUS-2-DMAERR : DMA Error detected - [chars]([dec])

Explanation The IPC CBUS DMA Process has detected a DMA transfer error.

Recommended Action The IPC subsystem is used by the Channel Adapter loader and Channel Adapter network management. A single DMA error will not impact these Channel Adapter functions. However, if you are experiencing problems loading the Channel Adapter or retrieving information from the Channel Adapter, you must reload the Channel Adapter microcode. In any case, report this message to your technical support representative.

Error Message
%IPC_CBUS-4-NOMEM : Unable to obtain [chars] buffers, MSGDEF_LIMIT_GLACIAL

Explanation The IPC CBUS transport subsystem could not obtain the memory it needed.

Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.

Table of Contents

CIP System Error Messages