|
|
The following are buffer status queue processing error messages.
Error Message
%BSQ-0-INCMPLT_XFER:Incomplete Data Transfer received for non-read operationExplanation An Incomplete Data Transfer Notice was received for a channel command word (CCW) that did not perform a read or that has read backward. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%BSQ-0-MTC_CHAIN:Incomplete More-To-Come chain queuedExplanation The Channel Interface Processor (CIP) could not find the end of a more-to-come chain. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%BSQ-0-NULLREAD:Unexpected read of zero bytes, BSQ=[hex] [hex] [hex] [hex]Explanation The Channel Interface Processor (CIP) was notified that a read I/O operation has been completed with a storage control block that had a length of 0.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%BSQ-0-SCB_CHAIN:Read SCB chain is out of sequenceExplanation 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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Channel Interface Processor (CIP) error messages relating to the ciscoBus controller statistics routine, the facility that receives configuration requests and gathers statistics.
Error Message
%CBUS_ATTN-3-BADADDR:Bad memory address ([hex]) requestedExplanation The Route Processor (RP) requested that the Channel Interface Processor (CIP) store a configuration command at an invalid memory address. The CIP has ignored 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.
The following are Channel Interface Processor (CIP) error messages for ciscoBus controller write support. The ciscoBus controller write feature 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 logic error. The Channel Interface Processor (CIP) recovered by ignoring the entry.
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
%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. The Channel Interface Processor (CIP) ignored this error condition.
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
%CBUS_WRITE-3-MISSING:Entry for address [hex] not foundExplanation A write error was detected, but there was no corresponding entry in the table that keeps track of these entries. This is an internal logic error. The Channel Interface Processor (CIP) recovered by ignoring the write error.
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
%CBUS_WRITE-3-STACK: [dec] [dec] [hex] [hex] [hex]Explanation This is a debugging display from the ciscoBus (CBUS) write stack and is associated with the CBUS_WRITE-3-MISSING error message.
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
%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 Channel Interface Processor (CIP) failed and attempted to restart. The CIP will probably have to be replaced.
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.
The following are Channel Interface Processor (CIP) error messages for channel card adapter processing.
Error Message
%CCA-3-ACR:Accept command response status receivedExplanation The adapter notified the Channel Interface Processor (CIP) that an accept command response has been issued. The CIP does not request notification of accept command response messages. Therefore, this message means that the adapter has generated an unexpected message.
Recommended Action Normal processing will resume, but it would be useful for the software developers to know that this message has occurred. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-0-BADCCA:Undefined CCA code received CCA=[hex] [hex]Explanation The adapter has presented the Channel Interface Processor (CIP) with a message using an undefined code point. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-0-BSQ_FULL: Buffer status queue is fullExplanation The adapter has notified the Channel Interface Processor (CIP) that the buffer status queue is 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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-BYPASS: Select bypass switch may be in bypass position for port [dec]Explanation A user has 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 Channel Interface Processor (CIP) that a halt subchannel command has been issued by the host, but provided the CIP with an undefined type of cancel.
Recommended Action The CIP will recover, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-CANCEL2: Cancel received for undefined path ([hex])Explanation The adapter notified the Channel Interface Processor (CIP) that a halt subchannel command has been issued by the host for an undefined path. This is an internal logic error.
Recommended Action The CIP software recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-COMMAND_PATH: Command connection received for undefined path ([hex])Explanation The adapter notified the Channel Interface Processor (CIP) that a start subchannel command has been issued by the host for an undefined path. This is an internal logic error.
Recommended Action The CIP software recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-CONN_RESULT: Connection result for device [hex][hex] expected [hex][hex]Explanation The adapter notified the Channel Interface Processor (CIP) that a connection has been 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 the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-0-DEV_ERR2: Device error but no active defined deviceExplanation 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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 Channel Interface Processor (CIP) has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-END_STATUS: Ending status interrupt received for [hex] CCWExplanation The adapter reported an ending status interrupt for a channel command word that should not have caused the Channel Interface Processor (CIP) to be notified. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-LOGOUT: Invalid logout command modifier ([hex])Explanation The adapter sent a request to the Channel Interface Processor (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 has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-REQUEST_STATUS: Request status received for undefined path ([hex])Explanation The adapter requested that the Channel Interface Processor (CIP) present the status of an undefined path. This is an internal logic error.
Recommended Action The CIP recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-RESET_PATH: Reset received for undefined path ([hex])Explanation The adapter has requested the Channel Interface Processor (CIP) to perform reset processing for an undefined path. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-RLP1: Invalid rlp flags ([hex])Explanation The adapter requested that the Channel Interface Processor (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 recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-RLP2: RLP received for undefined path ([hex])Explanation The adapter requested that the Channel Interface Processor (CIP) reset a logical path for an undefined path.
Recommended Action The Channel Interface Processor (CIP) recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-0-SCBNRDY: Unexpected SCB not ready CCA=[hex] [hex]Explanation The Channel Interface Processor (CIP) was notified that an I/O operation has been 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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-SEL_RESET1: Invalid selective reset code ([hex])Explanation The adapter requested that the Channel Interface Processor (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 recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-SEL_RESET2: Selective reset received for undefined path ([hex])Explanation The adapter has requested the Channel Interface Processor (CIP) to perform a selective reset on an undefined logical path. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-STATUS_NOTICE: Undefined status notice request code [hex]Explanation The adapter has presented the Channel Interface Processor (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 Channel Interface Processor (CIP) has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
%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 Channel Interface Processor (CIP) has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-3-SYS_RESET: Invalid system reset code ([hex])Explanation The adapter requested the Channel Interface Processor (CIP) to perform a system reset, but the request code in the message was not a valid value. This is an internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 Channel Interface Processor (CIP) has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CCA-0-TOOMANY: Too many buffers ([dec]) required for a write operation.Explanation The mainframe wrote data to the Channel Interface Processor (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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 can not be used unless it is 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 the Channel Interface Processor (CIP) to perform a request. When the CIP tried to present the response to the request, it was not able to write to the common communication area. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are channel adapter Cisco IOS wrapper error messages.
Error Message
%CIOS-3-BADPAK: pak=[hex], size=[dec]Explanation An internal software error occurred while messages were being generated by the channel adapter. It indicates that a buffer has been corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CIOS-3-BADREFCNT: pak=[hex], size=[dec]Explanation An internal software error occurred while messages were being generated by the channel adapter. It indicates that a buffer has been freed twice.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CIOS-2-BUGINF: Message too big(%lu)Explanation An internal software error occurred while debug messages were being generated by the channel adapter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. Turn off interprocess communication (IPC) debugging on the channel adapter until this can be fixed.
Error Message
%CIOS-3-CHUNKFREE: [chars] - chunk=[hex] name=[chars] ([hex])Explanation An internal software error occurred while messages were being generated by the channel adapter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CIOS-3-CONSISTENCY: [chars] - [chars]([hex])Explanation An internal software error occurred while debug messages were being generated by the channel adapter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. Turn off interprocess communication (IPC) debugging on the channel adapter until this can be fixed.
Error Message
%CIOS-3-MGD_TMR: mgd_timer[chars] not set, 10 * ONESECExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CIOS-3-NOMEM: Not enough memory to allocate [chars]Explanation The channel adapter is not equipped with enough memory to accommodate all the configured channel adapter features. The channel adapter 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 * ONESECExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CIOS-3-TIMERNEG: Cannot start timer ([hex]) with negative offset (%lu)., 10 * ONESECExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CIOS-3-WI: [chars] - process [chars](%lu)Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following Channel Interface Processor (CIP) error messages are 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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CLAW-0-BADHNAME: Host system names do not match.Explanation During the system validation 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 those that the Cisco Mainframe Channel Connection (CMCC) is designed to send.
Recommended Action The CMCC 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 Cisco Mainframe Channel Connection (CMCC).
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 Cisco Mainframe Channel Connection (CMCC).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CLAW-0-BADWNAME: Workstation system names do not match.Explanation During the system validation processing, the work station name configured in the router did not match the work station 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 Cisco Mainframe Channel Connection (CMCC) than the CMCC is designed to receive.
Recommended Action The CMCC has notified 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 has sent a Common Link Access for Workstations (CLAW) command with an invalid CLAW command code.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has ignored the request. Report this error to your Cisco technical support representative.
Error Message
%CLAW-0-DELFAILED: Tree deletion failed but entry was found, key=[hex].Explanation When running with IP Host Backup enabled, the application that owns the IP address is stored in a tree. When the application that owns the IP address is done with the IP address, the owner removes itself from the tree. Before removing itself, a check is made to see if it exists. It did exist, but the delete request failed.
Recommended Action This is a fatal internal logic error. The Channel Interface Processor (CIP) microcode has been reinitialized. If this error persists, stop using the IP Host Backup feature until the problem can be corrected.
Error Message
%CLAW-3-DELNOTHERE: Tree deletion requested but entry does not exist, requestor=[hex][hex][hex] [hex].Explanation When running with IP Host Backup enabled, the application that owns the IP address is stored in a tree. When the application that owns the IP address is done with the IP address, the owner removes itself from the tree. Before the owner removes itself, a check is made to see if it exists. The owner did exist, but the delete request failed.
Recommended Action This is an internal logic error. It may prevent IP Host Backup from working properly. If this error persists, stop using the IP Host Backup feature until the problem can be corrected.
Error Message
%CLAW-3-DELNOTME: Tree deletion requested but entry not owned, requestor=[hex][hex][hex] [hex], owner=[hex][hex][hex] [hex].Explanation When running with IP Host Backup enabled, the application that owns the IP address is stored in a tree. When the application that owns the IP address is done with the IP address, the owner removes itself from the tree. Before the owner removes itself, a check is made to see if it exists. The owner did exist, but the delete request failed.
Recommended Action This is an internal logic error. It may prevent IP Host Backup from working properly. If this error persists, stop using the IP Host Backup feature until the problem can be corrected.
Error Message
%CLAW-0-DUPMISSING: Tree insertion failed but duplicate entry not found, key=[hex].Explanation When running with IP Host Backup enabled, the application that owns the IP address is stored in a tree. When an attempt is made to claim the IP address, the application is inserted into the tree. If the insert fails, the tree is searched to find the owner of the application so that an appropriate error message may be issued. If the search fails, this message is issued to indicate that the tree is corrupted.
Recommended Action This is a fatal internal logic error. The Channel Interface Processor (CIP) microcode has been reinitialized. If this error persists, stop using the IP Host Backup feature until the problem can be corrected.
Error Message
%CLAW-6-INVALIDLINK: Invalid CLAW link [dec] specified for option [dec]Explanation The host has sent a Common Link Access for Workstations (CLAW) option request command for an invalid link.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has ignored the request. Report this error to your Cisco technical support representative.
Error Message
%CLAW-3-IPINUSE: Device [hex][hex][hex] [hex] requested IP address [dec].[dec].[dec].[dec] already in use by device [hex][hex][hex] [hex].Explanation When running in IP Host Backup mode, the first device listed attempted to establish a Common Link Access for Workstations (CLAW) connection to use the specified IP address. The IP address is already in use by the second device.
Recommended Action If the second CLAW device is the desired owner of the IP address, then stop the first CLAW device and restart the second CLAW device. If not, stop the second CLAW device.
Error Message
%CLAW-6-LINKEXISTS: An attempt was made to redefine application [chars] [chars], application already defined.Explanation The host has sent a Common Link Access for Workstations (CLAW) option request to define an application that already exists.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has ignored the request. Report this error to your Cisco technical support representative.
Error Message
%CLAW-6-LONGREC: Attempt to transmit too large a record, MSGDEF_LIMIT_MEDIUMExplanation The amount of data being read by the channel has exceeded the size of the read channel command word (CCW).
Recommended Action Report this error to your Cisco 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_GLACIALExplanation 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 Cisco 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 Cisco Mainframe Channel Connection (CMCC) has recovered by generating a bad return code to the requester. Report this error to your Cisco technical support representative.
Error Message
%CLAW-3-NOMEM: Not enough memory for host write., MSGDEF_LIMIT_SLOWExplanation Not enough free memory is available for the Common Link Access for Workstations (CLAW) task to replenish the channel buffers after getting a write buffer.
Recommended Action Install more memory for the Cisco Mainframe Channel Connection (CMCC) or configure fewer devices.
Error Message
%CLAW-3-NOSYSVAL: Device [hex][hex][hex] [hex] connection request [chars] [chars] without system validateExplanation The Common Link Access for Workstations (CLAW) connection request sequence was attempted without successful completion of a system validation sequence. This is a CLAW protocol error.
Recommended Action Restart the host application and the Cisco Mainframe Channel Connection (CMCC) application. If this problem persists, contact your Cisco 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 had not been established.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has ignored the request. Report this error to your Cisco technical support representative.
Error Message
%CLAW-6-NOTXBUF: Unable to allocate txbuf., MSGDEF_LIMIT_GLACIALExplanation No available transmit buffers exist, but the Common Link Access for Workstations (CLAW) connection has not reached its transmit buffer limit.
Recommended Action The packet has been dropped. Report this error to your Cisco technical support representative.
Error Message
%CLAW-6-OPTION: Unrecognized CLAW option request code [dec]Explanation The host has sent an unknown Common Link Access for Workstations (CLAW) option request command.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has ignored the request. Report this error to your Cisco 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 within the valid range for all Common Link Access for Workstations (CLAW) links.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has recovered by ignoring this request. Report this error to your Cisco technical support representative.
Error Message
%CLAW-6-SCBTYPE: Unrecognized SCB type code [dec]Explanation Each storage control block (SCB) pointing to data for the host is classified as a particular type before being queued to the host. After sending a block of data, the Common Link Access for Workstations (CLAW) application detected an invalid type defining the data. This is an internal logic error.
Recommended Action The Cisco Mainframe Channel Connection (CMCC) has recovered by ignoring the transfer. Report this error to your Cisco technical support representative.
Error Message
%CLAW-0-SYSMGT_ERROR1: CLAW detected error in sysmgt call: invalid type [dec]Explanation An invalid parameter was received in a system management call.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CLAW-6-TOOBIG: [dec] byte IP datagram exceeds CLAW MTU for device [dec]/[hex][hex][hex]/[hex], MSGDEF_LIMIT_GLACIALExplanation The router has sent an IP datagram to the Cisco Mainframe Channel Connection (CMCC) that is larger than the maximum transmission unit (MTU) for the CMCC. The MTU for the Common Link Access for Workstations (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 CMCC, and check the host configuration file. If the configurations are correct, report this problem to your Cisco technical support representative.
Error Message
%CLAW-6-TOOSMALL: [dec] byte IP datagram is too small, device [dec]/[hex][hex][hex]/[hex], MSGDEF_LIMIT_MEDIUMExplanation The router has sent an IP datagram to the Channel Interface Processor (CIP) that is smaller than an IP header. The packet has been dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
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 Cisco Mainframe Channel Connection (CMCC) has recovered by ignoring the transfer element. Report this error to your Cisco 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 Cisco Mainframe Channel Connection (CMCC) has recovered by ignoring the transfer element. Report this error to your Cisco 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 Common Link Access for Workstations (CLAW) device on the virtual port adapter. CLAW devices are permitted only on real port adapters.
Recommended Action The configuration request was ignored.
Error Message
%CLAW-6-WRITEREAD: Host Wrote data on read subchannel, MSGDEF_LIMIT_GLACIALExplanation The mainframe has written data to the read subchannel. This is most likely the result of a misconfiguration under a VM guest in which the write device is attached to the read subchannel.
Recommended Action Check the device definitions on the host and, if running under VM, verify that the write device is attached to the write subchannel and the read device is attached to the read subchannel.
The following are Logical Link Control (LLC) Transmission Group error messages.
Error Message
%CMPCTG-6-ACTIVE: CMPC-TG [chars] ACTIVEExplanation The Cisco Multipath Channel (CMPC)-Transmission Group (TG) is in the active state.
Recommended Action No action is required.
Error Message
%CMPCTG-3-BAD_XID3_LEN: Xid3 CV length exceeds Msg LengthExplanation The length values in Xid3 Control Vectors have exceeded the length field in the Xid3 message. The contents of the Xid3 follow immediately.
Recommended Action No action is required.
Error Message
%CMPCTG-3-CFG_ERR: TG [chars] configured with invalid Loop Back SapExplanation A loopback Transmission Group (TG) has been configured using the same local and remote remote service access point (SAP) values. For loopback configurations, the local and remote service access points (SAPs) should be different.
Recommended Action Change one of the SAP values.
Error Message
%CMPCTG-3-CFG_FSM_ERR: TG Name: [chars], Event [chars], State [chars]Explanation An internal state machine (FSM) has attempted to execute an event inconsistent with the state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CMPCTG-6-INB_SENSE: CMPC-TG [chars] Inbound Sense [hex]Explanation A Cisco Multipath Channel (CMPC)-Transmission Group (TG) has noticed a cv22 with sense data. This message indicates that an endpoint of the Advanced Peer-to-Peer Networking (APPN) session has detected a protocol problem.
Recommended Action 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] initializedExplanation A Cisco Multipath Channel (CMPC)-Transmission Group (TG) has been initialized. This message indicates which Transmission Group (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 An internal state machine (FSM) has attempted to execute an event inconsistent with the state.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CMPCTG-0-NOADAP: CMPC-TG [chars] attempt to open adapter failed, pc: [hex]Explanation An attempt by Cisco Multipath Channel (CMPC)-Transmission Group (TG) to open the Logical Link Control (LLC) adapter has failed.
Recommended Action Make sure that the LLC adapter referenced by this Transmission Group (TG) is configured.
Error Message
%CMPCTG-0-NOMEM: CMPC-TG [chars] attempt to acquire memory failed, pc: [hex], at [int]Explanation A call to create a pool or get a buffer has failed.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CMPCTG-6-NOTACTIVE: CMPC-TG [chars] NOT ACTIVEExplanation A Cisco Multipath Channel (CMPC)-Transmission Group (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 A Cisco Multipath Channel (CMPC)-Transmission Group (TG) has noticed a cv22 with sense data. This message indicates that an endpoint of the Advanced Peer-to-Peer Networking (APPN) session has detected a protocol problem.
Recommended Action No action on this router is required. Check the log for each of the two endpoints and take appropriate action.
Error Message
%CMPCTG-6-REMOVED: CMPC-TG [chars] removedExplanation A Cisco Multipath Channel (CMPC)-Transmission Group (TG) has been removed.
Recommended Action No action is required.
Error Message
%CMPCTG-0-SYSMGT_ERROR3: Llc-Tg detected error in sysmgt call: invalid operation [dec]Explanation An invalid parameter has been received in a system management call.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CMPCTG-0-SYSMGT_ERROR4: Llc-Tg detected error in sysmgt call: invalid lengthExplanation An invalid parameter has been received in a system management call.
Recommended Action Report this error to your Cisco technical support representative.
The following are Channel Interface Processor (CIP) error messages that relate to the configuration processing facility.
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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CONFIG-0-BADSPEED: Incorrect PCA speed passed to cbus attention exit routineExplanation The router has attempted to configure a parallel channel adapter (PCA) with an invalid channel speed.
Recommended Action The Channel Interface Processor (CIP) has recovered by ignoring the request. Report this error to your Cisco technical support representative.
Error Message
%CONFIG-3-BADVCN: Virtual circuit number ([dec]) too largeExplanation 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. This error message should happen only when a new configuration statement is added to a Channel Interface Processor (CIP).
Recommended Action Issue the show extended channel command, or the show extended vc command, as well as the show tech-support command, and report all the command output to your Cisco technical support representative.
Error Message
%CONFIG-6-BAD_DBTYPE: Bad port type ([dec])Explanation The port type function has returned an invalid port type. This is an indication that the port adapter hardware is not working properly. This error message should occur only during Channel Interface Processor (CIP) startup.
Recommended Action If this error message is reproducible or occurs randomly and repeatedly, copy the message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%CONFIG-3-CLAWDEV: CLAW device address ([hex]) must be evenExplanation The route processor has attempted to configure an odd address for a Common Link Access to Workstation (CLAW) device. CLAW configuration requests must specify an even address. This is an internal logic error. The configuration request was ignored.
Recommended Action Issue the show extended channel command, or the show extended vc command, as well as the show tech-support command, and report all the command output to your Cisco technical support representative.
Error Message
%CONFIG-3-CONFIGINIT: Invalid config registry identifier [dec]Explanation During initialization, each application will receive configuration commands from the system registers routines to process its configuration commands. An incorrect registration identifier was used. This is a fatal error.
Recommended Action The Channel Interface Processor (CIP) has been restarted. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CONFIG-3-DIFFDEVT: Device type ([dec]) does not match device [hex] device type ([dec])Explanation The router has attempted to remove an existing device but provided an incorrect device type. This is an internal logic error. The original configuration remains.
Recommended Action If this error message occurs repeatedly, copy the error message exactly as it appears, issue the show extended channel subchannel EXEC command and the show tech-support commands, and provide your Cisco technical service representative with the command output.
Error Message
%CONFIG-3-DOWNREV: The [chars] feature is not supported on CIP HW rev [dec].[dec]. Please upgrade your CIPExplanation A feature was configured that is not supported on this Channel Interface Processor (CIP) hardware revision. The feature was activated but is not guaranteed to work properly.
Recommended Action Upgrade your CIP either to a CIP with hardware version 4.4 or to a CIP2.
Error Message
%CONFIG-3-DUPDEV: Duplicate device address ([hex])Explanation The route processor has attempted to configure a device that already exists. This is an internal logic error. The configuration request was ignored.
Recommended Action If this problem is reproducible, provide the information on how to reproduce it to your Cisco technical service representative together with the output of show extended channel | vc and show tech-support commands.
Error Message
%CONFIG-3-DUPVCN: Virtual circuit number [dec] 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 This error message should only happen when a new configuration statement is added to a Channel Interface Processor (CIP). Issue the show extended channel | vc command, copy the error message exactly as it appears, issue the show tech-support command, and provide the gathered information to your Cisco technical support representative.
Error Message
%CONFIG-3-DUPVCN2: VCN [dec] already in use: ([hex]-[hex]-[hex]), no device foundExplanation The route processor has 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 This error message only should happen when a new configuration statement is added to a Channel Interface Processor (CIP). Issue the show extended channel | vc command, copy the error message exactly as it appears, issue the show tech-support command, and provide the gathered information to your Cisco technical support representative.
Error Message
%CONFIG-3-NOAPPLSPC: Error allocating storage for application blockExplanation No memory was available to allocate for an application control block. The configuration request was ignored.
Recommended Action Install more memory for the Channel Interface Processor (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 feature required to process a configuration command is not a part of the current image.
Recommended Action Either run a Channel Interface Processor (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 Copy the error message exactly as it appears, issue the show extended channel | sub and the show tech-support commands, and provide the information to your Cisco technical support representative.
Error Message
%CONFIG-3-NODEV: Device [hex] is not definedExplanation 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 Copy the error message exactly as it appears, issue the show extended channel | sub and the show tech-support commands, and provide the information to your Cisco technical support representative.
Error Message
%CONFIG-3-NODEVSPC: Error allocating storage for device blockExplanation No memory was available to allocate for a device block. The configuration request is ignored.
Recommended Action Install more memory for the Channel Interface Processor (CIP), or configure fewer devices.
Error Message
%CONFIG-3-NOFREEPATH: No free paths - only 64 may be specifiedExplanation 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-NOMEM: [chars]Explanation Not enough memory is available to process configuration commands on the channel adapter.
Recommended Action Verify the amount of memory installed on the channel adapter and upgrade if necessary.
Error Message
%CONFIG-3-NOPATHSPC: Error allocating storage for logical path tableExplanation No memory was available to allocate for the logical path table. The configuration request was ignored.
Recommended Action Install more memory for the Channel Interface Processor (CIP), or configure fewer devices.
Error Message
%CONFIG-3-NOSPACE: No space to build configuration confirmationExplanation Whenever the system sends a configuration command to the Channel Interface Processor (CIP), the CIP responds with a confirmation message. Sufficient memory was not available on the CIP to allocate a block to hold a confirmation message.
Recommended Action If you are not at the maximum Channel Interface Processor (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 definedExplanation 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. This error message only should happen when a configuration statement is removed from a Channel Interface Processor (CIP).
Recommended Action Issue the show extended channel | vc command, copy the error message exactly as it appears, issue the show tech-support command, and provide the information to your Cisco technical support representative.
Error Message
%CONFIG-3-OFFLDEV: Offload device address ([hex]) must be evenExplanation 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 If this problem is reproducible, provide the information on how to reproduce it to your Cisco technical service representative together with the output of the show extended channel | vc and show tech-support commands.
Error Message
%CONFIG-3-STATEINIT: Too many state change notification routinesExplanation 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. This is a fatal error. The Channel Interface Processor (CIP) has been restarted.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CONFIG-3-TOOBIG: Configuration comand ([dec]) is too large ([dec]) to processExplanation A feature was configured in which the configuration command is larger than the channel adapter can process. The configuration command will be ignored by the channel adapter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CONFIG-3-TOOMANYDEV: Too many devices defined. Only 256 may be usedExplanation 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 supportedExplanation 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 Channel Interface Processor (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 terminatedExplanation The Channel Interface Processor (CIP) unconfigured a device and found that there were still messages left in its work queues. This is an internal logic error.
Recommended Action If this message occurs repeatedly or if it is reproducible, copy the error message exactly as it appears, issue the show extended channel / sub and the show tech-support commands, and provide the information to your Cisco technical support representative.
The following are Channel Interface Processor (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 Cisco SNA (CSNA) write should fit in one transfer list element. The data sent in the CSNA required more than one.
Recommended Action Report this error to your Cisco 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 Cisco technical support representative.
Error Message
%CTA-0-ERRSTATE1: PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]Explanation A sequence error has occurred. A host write had been received when the subchannel setup was in a "pending open" state.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-0-ERRSTATE2: PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]Explanation A sequence error has occurred. A host write had been received when the subchannel setup was in a "pending open" state.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-0-ERRSTATE3: PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]Explanation A sequence error has occurred. A host write had been received when the subchannel setup was in a "pending open" state.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-0-ERRSTATE4: PA[dec] CTA [hex]-[hex] sequence error during subchannel setup, pc: [hex]Explanation A sequence error has occurred. A host write had been received when the subchannel setup was in a "pending open" state.
Recommended Action Report this error to your Cisco 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 that was intended to be sent to the channel was not sent to the channel. The virtual telecommunications access method (VTAM) will receive an error indication and should retry the operation.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-0-INACTIVE: PA[dec] CTA [hex]-[hex] reset after being inactive for [dec] secondsExplanation This subchannel has been inactive for longer than the subchannel timeout interval. Most likely the host has been halted or the virtual telecommunications access method (VTAM) has been terminated by a Z NET, CANCEL command.
Recommended Action Restart the virtual telecommunications access method (VTAM)/HOST and activate the Cisco Multipath Channel (CMPC)-Transmission Group (TG) major node.
Error Message
%CTA-6-INACT_ATTN_STATE: Attention FSM state: [chars]Explanation This message indicates the state of the finite state machine (FSM). This message is associated with the previous INACTIVE message. An error involving the FSM has occurred.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-6-INACT_FLOW_COUNTS: Flow stop/resume [int]/[int]Explanation This message indicates the total count of flow stop and flow resume frames that were passed by CTA to the host. This message is associated with the previous INACTIVE message. An error involving the channel transport architecture device task/mapper has occurred.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-6-INACT_FLOW_QUEUED: Flow Resume queued in CTA: [int]Explanation This message indicates the number of flow resume messages that were queued to the host in the CTA. This message is associated with the previous INACTIVE message. An error involving the channel transport architecture device task/mapper has occurred.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-6-INACT_FREEMEM: Free Memory: 0x[hex]Explanation This message indicates the current amount of free memory. This message is associated with the previous INACTIVE message. An error involving the channel transport architecture device task/mapper has occurred.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-6-INACT_SCBS: SCBs in SLC: [dec]Explanation This message indicates the number of storage control blocks (SCBs) queued signaling link code (SLC). This message is associated with the previous INACTIVE message. An error involving the channel transport architecture device task/mapper has occurred.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-6-INACT_SLOWDOWN: Slowdown [chars]: [chars], [int] msExplanation This message indicates the slowdown state and duration. This message is associated with the previous INACTIVE message. An error involving the channel transport architecture device task/mapper has occurred.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-6-INIT: PA[dec] CTA [hex]-[hex] Device initializedExplanation A Cisco SNA (CSNA) device has been initialized. The device string is in the form CSNA x/yyyy/zz, where x is the daughterboard 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 has exceeded the size of the read channel command word (CCW).
Recommended Action If this message occurs with Cisco SNA (CSNA) and the MAXPIU is set to less than 4500, then increase the MAXPIU value. Otherwise, report this error to your Cisco technical support representative.
Error Message
%CTA-0-MSGERR1: PA[dec] CTA [hex]-[hex] mismatch between channel block size and msg countsExplanation An error involving a mismatch between the channel block size and the message counts has occurred.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-0-MSGERR2: PA[dec] CTA [hex]-[hex] msg size less than DLC hdr sizeExplanation The host has sent an invalid message. The message size is less than the data-link connection (DLC) header size.host as indicated by description.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-0-MSGERR3: PA[dec] CTA [hex]-[hex] Received CTA command not recognizedExplanation A channel transport architecture (CTA) command code has been received that is not in the valid range.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-0-NOMEM: CTA attempt to acquire memory failed, pc: [hex]Explanation An attempt by the channel transport architecture (CTA) to create a pool or allocate a buffer has failed.
Recommended Action Report this error to your Cisco 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 An attempt by the channel transport architecture (CTA) to initialize or allocate a queue has failed.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-6-SHUTDOWN: PA[dec] CTA [hex]-[hex] Device shutdownExplanation A CSNA device has been shut down. The device string is in the form CTAn/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 lengthExplanation An invalid parameter has been received in a system management call.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-0-SYSMGT_ERROR2: CTA detected error in sysmgt call: invalid LLC2 CONN lengthExplanation An invalid parameter has been received in a system management call.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-0-SYSMGT_ERROR3: CTA detected error in sysmgt call: invalid CSNA typeExplanation An invalid parameter has been received in a system management call.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-0-UNEXP_ATTN_EVENT: PA[dec] CTA [hex]-[hex] unexpected event [int] in attn state [int], setup state [int]Explanation An unrecognized event has been received by the channel transport architecture (CTA) attention finite state machine (FSM). The receipt of the unrecognized event is an unrecoverable situation. This instance of CTA is initialized, and the Cisco Multipath Channel (CMPC)-Transmission Group (TG) node must be cycled to resume operation.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA-0-UNEXP_EVENT: PA[dec] CTA [hex]-[hex] received unrecognized type code 0x[hex] at 0x[hex]Explanation A transfer element type code not in the valid range has been received.
Recommended Action Report this error to your Cisco 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 has been received.
Recommended Action Report this error to your Cisco 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 has been received.
Recommended Action Report this error to your Cisco 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 channel transport architecture (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 Cisco technical support representative.
Error Message
%CTA_TEST_TOOL-3-INVALIDMBUF: CTA Test-Tool detected an invalid CTA command mbuf, cmd: [hex]Explanation The m-buffer of a channel transport architecture (CTA) command 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 Cisco technical support representative.
Error Message
%CTA_TEST_TOOL-3-INVALID_CFGBLK_LEN: CTA Test-Tool configuration block length invalidExplanation A CTA Test-Tool configuration command with an invalid configuration block length has been received. The configuration command will be ignored.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%CTA_TEST_TOOL-3-NOMEMORY: CTA Test-Tool code could not allocate memory, pc: [hex]Explanation An attempt has been made to allocate memory for the where the configuration block length Test-Tool utility. Not enough memory was available at the time that the CTA Test-Tool configuration command was processed on the Channel Interface Processor (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 the these actions resolves this problem, report this error to your Cisco technical support representative.
The following are Channel Interface Processor (CIP) error messages that are issued when nonrecoverable errors occur on the CIP.
Error Message
%DEBUGGER-0-CCHAIN: [chars]Explanation This message shows a line from the call chain and is part of a fatal error dump. The Channel Interface Processor (CIP) has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message %DEBUGGER-0-FATAL_ERROR: Fatal error (code=%02d)
Explanation A fatal internal Channel Interface Processor (CIP) error occurred. The CIP has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-CIP_HWVINFO: SNr. [dec] HWRev. [int].[int] EPROM [int].[int] VPLD [int].[int]Explanation This message contains hardware version information. This is part of a fatal error dump. The Channel Interface Processor (CIP) has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Explanation To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-CIP_SWVINFO: [chars] [dec].[dec] [chars]Explanation This message contains software version information. This is part of a fatal error dump. The Channel Interface Processor (CIP) has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-3-CONSOLE_IP: Invalid IP console registry identifier [dec]Explanation During initialization, each application that uses an IP address registers a routine to be used by the console dbcb command to fetch the IP address. The identifier associated with a routine was not within a valid range. This is a fatal error. The Channel Interface Processor (CIP) has been restarted.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%DEBUGGER-3-CONSOLE_TX: Invalid TX buffer console registry identifier [dec]Explanation During initialization, each application that uses global transmit buffers registers a routine to be used by the console dbcb command to fetch the buffer counts. The identifier associated with a routine was not within a valid range. This is a fatal error. The Channel Interface Processor (CIP) has been restarted.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%DEBUGGER-0-FATAL_ERROR: Fatal error (code=%02d)Explanation A fatal internal Channel Interface Processor (CIP) error has occurred. The CIP has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-INVALID_ADDR: address 0x[hex] is invalidExplanation An invalid address has been detected while trying to perform a stack dump. This is part of a fatal error dump. The Channel Interface Processor (CIP) has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-LCORE_DATA: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation This message displays data from the low core area of the Channel Interface Processor (CIP). This is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-LCORE_START: Dump of lowcoreExplanation This message begins a dump of the Channel Interface Processor (CIP) low core memory. This is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-RESTART: Restart due to breakpointExplanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates that the CIP has finished printing all debugging information and is attempting a restart. This is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK1: [hex] [hex] [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates a line of stack information. This is part of a fatal error dump. The Channel Interface Processor (CIP) has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK2: [hex] [hex] [hex] [hex] [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates a line of stack information. This is part of a fatal error dump. The Channel Interface Processor (CIP) has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK3: [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates a line of stack information. This is part of a fatal error dump. The Channel Interface Processor (CIP) has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK4: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates a line of stack information. This is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK_DATA1: [hex] [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates a line of internal interrupt stack information. This is part of a fatal error dump. The Channel Interface Processor (CIP) has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK_DATA2: [hex] [hex] [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates a line of internal interrupt stack information. This is part of a fatal error dump. The Channel Interface Processor (CIP) has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK_DATA3: [hex] [hex] [hex] [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates a line of internal interrupt stack information. This is part of a fatal error dump. The Channel Interface Processor (CIP) has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK_DATA5: [hex] [hex] [hex] [hex] [hex] [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates a line of internal interrupt stack information. This is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK_DATA6: [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates a line of internal interrupt stack information. This is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK_DATA8: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates a line of internal interrupt stack information. This is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is printing out contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK_DUMP0: [chars], base=[hex], stack_size=[hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates the beginning of the stack for the current task and is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is providing contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK_DUMP1: sp=[hex], pc=[hex], ra=[hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates the second line from the dump of the stack for the current task and is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is providing contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK_OVERFLOW: overflow condition detected for this task: [chars]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates that the current task has overflown its stack and is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is providing contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-STACK_START: Stack addr: [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This messages indicates the beginning of a dump of the internal interrupt stack and is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is providing contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-TRACE_ADDR: Table:[hex] Next:[hex] First:[hex] Last:[hex] Full:[hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates the internal trace table header, which is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is providing contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-TRACE_DATA: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates a single entry from the internal trace table, which is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is providing contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%DEBUGGER-0-TRACE_START: Dump of trace tableExplanation A fatal internal Channel Interface Processor (CIP) error occurred. This message indicates the beginning of a dump of the internal trace table. This is part of a fatal error dump. The CIP has encountered an unrecoverable problem and is providing contextual information about where the problem occurred. A fatal error dump consists of the following parts:
Recommended Action To capture all these error messages, ensure that you have set the logging buffered command to 64000, or log to a system log server. Frequently such a fatal error dump is immediately preceded by some additional CIP error messages. Ensure that you capture those messages as well. Call your Cisco technical support representative and provide the representative with the gathered information.
Posted: Fri Jun 16 11:46:16 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.