|
|
The following are H.323 proxy error messages.
Error Message
%CCPROXY-3-NOBLOCK_EVENT:Explanation During the initialization of a proxy, an event block could not be allocated.
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.
%CCPROXY-3-NOCCAPI_INTERFACE:Explanation The new call-control Application Programming Interface (API) interface was not created.
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
%CCPROXY-3-NOCCB_FROM_CALLID:Explanation No call-control block was found.
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
%CCPROXY-3-UNREGISTERED_BY_GK:Explanation The H.323 proxy registration is being removed by the Gatekeeper. For more details, enter the show proxy h323 status command.
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 Cable Data Modem (CDM)) subsystem error messages.
Error Message
%CDM-3-CONFIG: Interface [chars] must be ACIP to run cable applicationExplanation The named interface is not an ATM Cable Interface Processor (ACIP) interface.
Recommended Action An ACIP is required in order to run the cable data modem (CDM) application. Ensure that an ACIP is installed in the system.
Error Message
%CDM-6-CHANNELDOWN: Channel(vpi=[dec]) on [chars], changed state to downExplanation The signalling connection to this system has gone down.
Recommended Action No action is required.
Error Message
%CDM-6-CHANNELUP: Channel(vpi=[dec]) on [chars], changed state to upExplanation The signalling connection to this system has been activated.
Recommended Action No action is required.
Error Message
%CDM-6-CHANNELUPPENDING: Channel(vpi=[dec]) on [chars], changed state to up pendingExplanation The local interface is up, but the remote interface or system does not respond. It is probably not connected or is powered down.
Recommended Action No action is required.
Error Message
%CDM-3-INIT: ACIP required to run this Cisco IOS imageExplanation No ATM Cable Interface Processor (ACIP) is installed in the system. An ACIP is required to run the cable data modem (CDM) application.
Recommended Action Install an ACIP.
Error Message
%CDM-6-MODEMDOWN: Modem(vci=[dec]) on [chars], changed state to downExplanation A modem has been disconnected from the system.
Recommended Action No action is required.
Error Message
%CDM-6-MODEMUP: Modem(vci=[dec]) on [chars], changed state to upExplanation A new modem has been connected to the system.
Recommended Action No action is required.
The following are Cisco Discovery Protocol (CDP) error messages.
Error Message
%CDP-4-DUPLEX_MISMATCH: duplex mismatch discovered on [chars] ([chars]), with [chars] [chars] ([chars])Explanation Cisco Discovery Protocol (CDP) has discovered a mismatch of duplex configuration.
Recommended Action Configure the interfaces to the same duplex (full or half).
Error Message
%CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on [chars] ([dec]), with [chars] [chars] ([dec])Explanation Cisco Discovery Protocol (CDP) has discovered a mismatch of native VLAN configuration.
Recommended Action Configure the interfaces to the same native VLAN.
The following are CE3 port adapter error messages.
Error Message
%CE3-3-BADMSG: Received unexpected mailbox message (id = [dec])Explanation An unexpected message was received from the CE3 firmware.
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
%CE3-2-CE3FWCRASHED: CE3 F/W crashed: [hex] - VIP resetExplanation The CE3 firmware did not update the software watchdog.
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
%CE3-2-CE3FWCRASHEDINFO: [hex] [hex] [hex] [hex]Explanation The CE3 firmware did not update the software watchdog.
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
%CE3-1-CONFIGURE: Failed to configure [dec] interfaces in bay [dec], shutting down bayExplanation The CE3 hardware has failed. Some components on the board failed to initialize.
Recommended Action Replace the CE3 port adapter. If the problem persists, 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
%CE3-1-DISCOVER: Found [dec] interfaces in bay [dec], shutting down bayExplanation The CE3 hardware has failed. Some components on the board failed to initialize.
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
%CE3-1-DWNLDFAIL: Microcode to slot [dec]Explanation The firmware did not download successfully into the CE3 port 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
%CE3-1-ENABLEFAIL: [chars] could not be enabled by [chars]Explanation The restart failed to enable the interface.
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
%CE3-3-ERROR: [chars]Explanation This message contains general error information.
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
%CE3-1-INITFAIL: Slot [dec] firmware init ([chars])Explanation The CE3 firmware initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CE3-1-INITFAILP: [chars] init failed at [chars]Explanation The CE3 firmware initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CE3-3-LOVEFAIL: [chars]: failed to send [chars] love letterExplanation A love letter was not sent to the Route Switch Processor (RSP).
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
%CE3-3-MBOXRECV: Failed to receive reply [dec] from bay [dec] firmwareExplanation A message was not received from the CE3 firmware.
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
%CE3-3-MBOXRECVP: Failed to receive reply [dec] to [chars] driver firmwareExplanation A port-related message was not received from the CE3 firmware.
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
%CE3-3-MBOXSEND: Failed to send msg [dec] to bay [dec] firmwareExplanation A message was not sent to the CE3 firmware.
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
%CE3-3-MBOXSENDP: Failed to send msg [dec] to [chars] driver firmwareExplanation A port-related message was not sent to the CE3 firmware.
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
%CE3-3-NOACC: [chars] - Accumulator is not availableExplanation An invalid TX accumulator has been detected.
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
%CE3-3-NOTFREEDM: Slot [dec] device ID seen as [hex], expected [hex] (FREEDM)Explanation The High-Level Data Link Control (HDLC) controller was not detected on the CE3 port adapter.
Recommended Action Replace the CE3 port adapter.
Error Message
%CE3-3-NOTPLX: Slot [dec] device ID seen as [hex], expected [hex] (PLX9060)Explanation The PLX 9060 was not detected on the CE3 port adapter.
Recommended Action Replace the CE3 port adapter.
Error Message
%CE3-1-NOTREADY: Slot [dec] for microcode downloadExplanation An error was detected on the communication path between the Virtual Interface Processor (VIP) and the CE3.
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
%CE3-2-NOVC: [chars]: packet received for unknown VC [dec]Explanation The virtual channel encapsulation is 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
%CE3-1-RESTARTFAIL: [chars] could not be reset by [chars]Explanation The restart failed to reset the interface.
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
%CE3-1-STARTFAIL: [chars] could not be enabled by [chars]Explanation The restart failed to enable the interface.
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
%CE3-1-STOPFAIL: [chars] could not be disabled by [chars]Explanation The shutdown failed to disable the interface.
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 Circuit Emulation Service (CES) error messages.
Error Message
%CES-2-INTERNAL_CRITICAL: [chars]Explanation The Circuit Emulation Service (CES) subsystem has encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
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
%CES-3-INTERNAL_ERROR: [chars]Explanation The Circuit Emulation Service (CES) subsystem has encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
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
%CES-4-INTERNAL_WARNING: [chars]Explanation The Circuit Emulation Service (CES) subsystem has encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
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 Cisco 7500 platform chassis interface error messages.
Error Message
%CI-3-ASPMEM: LS1010 equipped with [chars] requires at least [dec] MB of RAM; Only [dec] MB of RAM installedExplanation The LS1010 requires more RAM.
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
%CI-3-ASPREV: ***WARNING*** Hot swapping the ASP will cause hardware damageExplanation Hot-swapping the ATM switch processor (ASP) will cause hardware damage.
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
%CI-3-ASPREVC5500: ***WARNING*** Cannot determine Power Supply type/detect Power Supply fan alarmExplanation The ATM switch processor (ASP) does not recognize the power supply to the fan.
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
%CI-3-BLOWER: Fan failureExplanation One of the cooling fans of the router has failed.
Recommended Action Replace the fan as soon as possible or the router may shut itself down.
Error Message
%CI-3-FCTYPE: Cannot recognize Feature CardExplanation The ATM switch processor (ASP) does not recognize the feature card.
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
%CI-3-NOACK: Access to [chars] temperature sensor failedExplanation The Chassis Interface (CI) software has failed to communicate with the temperature sensor.
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
%CI-3-NOFORK: Couldn't start environment polling daemonExplanation The Chassis Interface (CI) software could not start the environment polling daemon.
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
%CI-3-PSFAIL: Power supply [int] failureExplanation One of the power supplies to the router has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CI-3-PSFANFAIL: Power supply fan [int] failureExplanation The power supply to one of the router fans has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CI-3-PSTYPE: ***WARNING*** Incompatible power supply types - One is AC, other is DCExplanation The Chassis Interface (CI) software has detected incompatible power supply types. One is AC and one is DC. Failure to make the power supplies compatible will cause hardware damage.
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
%CI-0-SHUTFANFAIL:Explanation The system is shutting down because of a total fan tray failure.
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
%CI-3-SHUTDOWN: Shutting down due to overheatExplanation The router is shutting down because of overheating.
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
%CI-3-TEMP: Temperature overheatExplanation The router is overheating.
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) core dump error messages.
Error Message
%CIPDUMP-3-CIP_CORE_DUMP_ERROR: CIP core dump error, slot [dec]: [chars]Explanation An error occurred during a Channel Interface Processor (CIP) core dump.
Recommended Action No action is required.
Error Message
%CIPDUMP-6-CIP_CORE_DUMP_PROGRESS: Dump of slot [dec] core [chars].Explanation This message contains progress updates for the Channel Interface Processor (CIP) core dump.
Recommended Action No action is required.
The following are CD2430 asynchronous controller error messages.
Error Message
%CIRRUS-3-BADHDXFSM: Interface serial [dec], Unexpected HDX state [dec], event [dec]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. 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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CIRRUS-3-BADMODE: Interface serial [dec], Bad mode encountered in initExplanation An internal software error has occurred.
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 command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CIRRUS-3-BADRXISR: Interface serial [dec], Unexpected situation in receive ISRExplanation An internal software error occurred while the asynchronous controller was receiving data.
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
%CIRRUS-3-BADTXISR: Interface serial [dec], Unexpected situation in transmit ISRExplanation An internal software error occurred while the asynchronous controller was sending data.
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
%CIRRUS-4-DOWNREV_NM: Network Module card in slot [dec] is incompatible with the systemExplanation The network module in this slot is an old one that is not compatible with this system.
Recommended Action Upgrade the network module.
Error Message
%CIRRUS-5-LINEFLAP: Unit [dec] excessive modem control changesExplanation The specified asynchronous interface was determined to have too many automatic control changes in too short a span of time. This error may indicate a hardware or software error in the interface.
Recommended Action Reset the interface. If the message recurs, 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
%CIRRUS-1-NOMEMORY: msgtxt_nomemoryExplanation An operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%CIRRUS-3-RESETERR: CD2430 serial controller [dec], Reset timeout errorExplanation The asynchronous controller failed to respond to a reset command. This error may indicate a hardware failure.
Recommended Action Reset the interface or controller. Cycle the power if necessary. If the message recurs, 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
%CIRRUS-3-SETCHAN: Serial[dec]: setchan called in CD2430 interrupt contextExplanation An internal software error has occurred.
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 slow-speed asynchronous/synchronous port module error messages.
Error Message
%CIRRUS_PM-3-BADLOOPCABLE: Loopback not supported for DTE/X.21 port [dec] in slot [dec]Explanation The DTE/X.21 cable does not support loopback.
Recommended Action Use the proper cable for loopback testing.
Error Message
%CIRRUS_PM-3-DISCOVER: CIRRUS PM at slot [dec]: PCI discovery failedExplanation The software failed to initialize the network module.
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
%CIRRUS_PM-2-NOBUFPOOL_ASYNC: Unable to create buffer pool for async mode interfaceExplanation There is not enough memory for a per-channel control block of the CD2430 asynchronous driver.
Recommended Action Ensure that the router has sufficient memory available. If the message recurs, copy the error message exactly as it appears, and report it to your Cisco technical support representative.
Error Message
%CIRRUS_PM-3-NOTCD2430: Device reported [hex]Explanation The network module hardware reports that a port module other than a low-speed one was detected.
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
%CIRRUS_PM-3-UNKNOWNPLATFORM: Unknown Platform type to support CD2430 interfacesExplanation The network module is not compatible with the current platform into which it is being plugged.
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 clear facility error messages.
Error Message
%CLEAR-5-COUNTERS: Clear counter on [chars] [chars] by [chars]Explanation The counters have been cleared on the interface.
Recommended Action No action is required.
Error Message
%CLEAR-5-EXT_COUNT: Clear extended [chars] counters on [chars] by [chars]Explanation The extended counters have been cleared on the interface.
Recommended Action No action is required.
The following are OSI Connectionless Network Service (CLNS) error messages.
Error Message
%CLNS-5-ADJCHANGE: [chars]: Adjacency to [chars] ([chars]) [chars], [chars]Explanation An Intermediate Syste-m-to-Intermediate System (IS-IS) Protocol or NetWare Link Services Protocol (NLSP) adjacency with a neighboring router has either come up or gone down. The message describes the change and the reason for it. This message appears only if the log-adjacency-changes command is configured for the IS-IS or NLSP process.
Recommended Action This informational message normally appears as routers and links go up or down. However, unexpected adjacency loss might indicate high error rates or high packet loss in the network and should be investigated.
Error Message
%CLNS-5-ADJCLEAR: [chars][chars]: All [chars]adjacencies clearedExplanation All Intermediate System-to-Intermediate System (IS-IS) Protocol or NetWare Link Services Protocol (NLSP) adjacencies of the specified type have been cleared. This message appears only if the log-adjacency-changes command is configured for the IS-IS or NLSP process.
Recommended Action This informational message appears as a normal side effect of appropriate console or configuration commands.
Error Message
%CLNS-4-AREALOST: Too many IS-IS areas--can't route to area [chars]Explanation Intermediate System-to-Intermediate System (IS-IS) Protocol allows for only three area addresses per area. Multiple routers having at least one area address in common merge all of their configured area addresses into a single set. If the resulting set includes more than three area addresses, this message appears and indicates that there will be a loss of connectivity to the specified area.
Recommended Action Reconfigure the network so that the area has fewer area addresses, or split the area into multiple areas.
Error Message
%CLNS-3-BADIFNUM: ISIS: Bad if number, pdb [hex], idb [hex], if [hex]Explanation An internal error has occurred involving the Intermediate System-to-Intermediate System (IS-IS) Protocol or NetWare Link Services Protocol (NLSP). An inconsistency was detected in an internal data structure related to tracking the protocol or interface state, possibly related to the enabling or disabling of the protocol on an interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CLNS-3-BADPACKET: [chars]: [chars], [chars][chars] from [chars] ([chars])Explanation An invalid packet has been received from a neighboring router.
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
%CLNS-1-BKUPERR: ISIS: [chars] in [hex], ndb_next [hex], ndb_prev [hex], lsp_next [hex], lsp_prev [hex], metric [hex], index [dec], [chars] [hex]Explanation An internal error has occurred in the maintenance of the Intermediate System-to-Intermediate System (IS-IS) Protocol backup route table.
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
%CLNS-3-CKSUMERR: [chars]: L[dec] LSP [chars] database checksum error, restartingExplanation A hardware or 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
%CLNS-4-DUPSYSTEM: [chars]: possible duplicate system ID [chars] detectedExplanation A configuration error has occurred, possibly resulting in duplicate system IDs.
Recommended Action One of the duplicate IDs must be corrected.
Error Message
%CLNS-4-EDATFAIL: Encapsulation failed, dst= [chars]Explanation This message can occur when an interface is down and a static neighbor entry exists in the Connectionless Network Service (CLNS) routing table of the system. If this is not the case, the message indicates an internal software error.
Recommended Action Check the interface. If the interface is not down and no static neighbor entry exists for that interface, call your Cisco technical support representative for assistance.
Error Message
%CLNS-1-LINKERR: ISIS: [chars] in [hex], lsp_next [hex], lsp_prev [hex], index [dec], ver [dec], [chars] [hex]Explanation An internal error has occurred in the maintenance of Intermediate System--to-Intermediate System (IS-IS) Protocol or NetWare Link Services Protocol (NLSP) link-state packet (LSP) linkages.
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
%CLNS-3-LSPCHAIN: [chars]: non-null [chars] pointer [hex] on freed LSP, index [dec]Explanation An internal error has occurred in the Intermediate System-to-Intermediate System (IS-IS) Protocol or NetWare Link Services Protocol (NLSP).
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
%CLNS-4-LSPCKSUM: [chars]: Bad L[dec] LSP [chars] checksum [hex] received on [chars], length [dec], should be [hex], bad count [dec]Explanation A link-state packet (LSP) was received for either the Intermediate System-to-Intermediate System (IS-IS) Protocol or the NetWare Link Services Protocol (NLSP), which failed an internal data checksum, but which passed the data-link checksum. The interface on which the LSP was received is indicated, along with the total count of checksum errors received, the LSP ID, and the level of the failing LSP. This message usually indicates data corruption occurring on a link, but it might also indicate data corruption in the memory of a neighboring router.
Recommended Action If the error is in the memory of a neighboring router, the problem will correct itself within 15 minutes. That router will detect its internal error and regenerate the corrupted data. This case is usually indicated by a single LSP ID appearing repeatedly in these messages. The same LSP ID might appear in this message on other routers as well. If data-link corruption has caused the error, check the link for errors and deal with them appropriately. This case is usually indicated by a number of different LSP IDs appearing in these messages.
Error Message
%CLNS-3-LSPDB: [chars]: Inconsistent LSPIX entry, lsp [hex], index [dec], ixentry [hex], ixentry->lsp [hex]Explanation An internal error has occurred in the Intermediate System-to-Intermediate System (IS-IS) Protocol or NetWare Link Services Protocol (NLSP).
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
%CLNS-3-LSPFULL: [chars]: L[dec] LSP filled to capacity, dropping routesExplanation A hardware or software has error 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
%CLNS-3-LSPIXARRMATCH: [chars]: LSPix entry [dec] mismatch with LSP [hex], LSP [chars] is [dec], entry [dec]Explanation An internal error has occurred in the Intermediate System-to-Intermediate System (IS-IS) Protocol or NetWare Link Services Protocol (NLSP).
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
%CLNS-3-LSPIXARRNULL: [chars]: LSPix entry [dec] should be null, is [hex]Explanation An internal error has occurred in the Intermediate System-to-Intermediate System (IS-IS) Protocol or NetWare Link Services Protocol (NLSP).
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
%CLNS-3-LSPIXHEAD: [chars]: LSPix [chars] [dec] head [hex] doesn't match first prev [hex]Explanation An internal error has occurred in the Intermediate System-to-Intermediate System (IS-IS) Protocol or NetWare Link Services Protocol (NLSP).
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
%CLNS-3-LSPTOOBIG: [chars]: L[dec] LSP [chars] size [dec] bigger than interface [chars] MTU [dec], LSP droppedExplanation A software or hardware 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
%CLNS-5-MULTICAST: [chars]: [chars]cast address in use on [chars]Explanation A NetWare Link Services Protocol (NLSP) adjacency with a neighboring router has either come up or gone down. The message describes whether the NLSP multicast address is in use for future updates sent on the LAN. This message appears only if the log-adjacency-changes command is configured for the NLSP process.
Recommended Action This message is primarily informational and appears normally when routers and links go up or down.
Error Message
%CLNS-3-NSAPES: Invalid NSAP type in ES table: [hex] for [chars]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.
Error Message
%CLNS-4-NSAPIS: Invalid NSAP type in IS table: [hex] [dec]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.
Error Message
%CLNS-3-ONLIST: ISIS: entry already threaded, prev [hex], next [hex], area = [chars] , index [dec], ver [dec], lsp area = [chars], lspid [chars], addr [int] [int]Explanation An internal error has occurred in the Intermediate System-to-Intermediate System (IS-IS) Protocol or NetWare Link Services Protocol (NLSP).
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
%CLNS-4-REDIRECT: Redirect found for non-route entry, dst= [chars], next-hop= [chars]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.
Error Message
%CLNS-3-TENT: [chars]: [chars]Explanation An internal error has occurred in the Intermediate System-to-Intermediate System (IS-IS) Protocol or NetWare Link Services Protocol (NLSP).
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 Cisco 6400 network clocking error messages.
Error Message
%CLOCKSW-3-BOGUS_PLIMTYPE: [chars]: bogus plimtype 0x[hex]Explanation An internal error has occurred in the internal data block (IDB). This interface cannot be selected as a network clocking source.
Recommended Action Select another interface as the network clocking source.
Error Message
%CLOCKSW-3-CLOCK_ALL_FAIL: All selected network clock sources have failedExplanation All the configured network clocking sources have failed.
Recommended Action Restore proper operation to one or more of the selected interfaces.
Error Message
%CLOCKSW-3-CLOCK_FAIL: Network clock source [chars], priority [dec], failureExplanation The specified network clocking source has failed.
Recommended Action Restore proper operation to the selected interface.
Error Message
%CLOCKSW-6-CLOCK_OK: Network clock source [chars], priority [dec], okExplanation The specified network clocking source is operational.
Recommended Action No action is required.
Error Message
%CLOCKSW-6-PFQ_PLL_BYPASS: Bypassing FC-PFQ PLLExplanation The feature card per-flow queueing (FC-PFQ) clock is nonoperational and is being bypassed.
Recommended Action No action is required.
Error Message
%CLOCKSW-6-SWITCH_SOURCES: Switching from [chars] to [chars] at priority level [dec]Explanation The network clock has changed from one source to another.
Recommended Action No action is required.
The following are Cisco link services (CLS) error messages.
Error Message
%CLS-3-BOGUSOP: Unknown CLS verb for [chars] context, DlcOpcodeT=[hex]Explanation An invalid operation code was generated by the Data-Link Control (DLC) for the STN or the connection end point (CEP).
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
%CLS-3-CLSFAIL: CLS: Assertion failed: [chars]Explanation A software or hardware 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
%CLS-3-CLSMSG: [chars]Explanation A software error was detected while CLSIMsg objects were being manipulated.
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 Cisco link services (CLS) driver error messages.
Error Message
%CLSDR-3-ERRRTN: [chars] failed error 0x[hex]Explanation An error was returned from Cisco Link Services Interface (CLSI) to the destination logical unit (DLU) because CLSI did not perform the action desired by the DLU.
Recommended Action Refer to CLSI software documentation for more information about this error. Report this error to your Cisco technical support representative.
Error Message
%CLSDR-3-INCORRECTPORT: Incorrect port pointer in USapIdExplanation Cisco Link Services Interface (CLSI) has returned an incorrect port pointer in the USapID.
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
%CLSDR-3-MSGERR: [chars] couldn't get a messageExplanation The destination logical unit (DLU) could not send a correct message to Cisco Link Services Interface (CLSI) because the message was formed incorrectly. CLSI will not perform the desired action.
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
%CLSDR-3-NOCEP: Cannot found cep in free poolExplanation A software or hardware 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
%CLSDR-3-NOCLSSERVER: unable to start the Server processExplanation Could not start the CLSDRIVER process, possibly because of a resource problem. The subsystem using the CLSDRIVER does not work.
Recommended Action Remove and then restore the destination logical unit (DLU) in the configuration file and try to reboot the system. 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
%CLSDR-3-NODLUCREATE: Cannot create DLU for this type [dec]Explanation The CLSDRIVER does not understand the destination logical unit (DLU) type. Currently, only the Serial tunnel (STUN) uses the CLSDRIVER. Any other value results in an 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
%CLSDR-3-NOINIT: CLSDRIVER not initializedExplanation A CLSDRIVER initialization failed earlier. Trying to use the driver now results in an error condition.
Recommended Action Remove and then restore the destination logical unit (DLU) in the configuration file and try to reboot the system. 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
%CLSDR-3-NOPORTCREATE: Cannot create PORT structureExplanation The CLSDRIVER cannot enable this port for processing.
Recommended Action Try rebooting the router. 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
%CLSDR-3-NOREMOVECEP: RemoveCep : Cep 0x[hex] not on listExplanation The destination logical unit (DLU) is trying to remove a nonexistent connection end point (CEP) from the internal data structure. The attempted removal creates a problem in the CEP maintenance logic.
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
%CLSDR-3-NOREMOVEPORT: RemovePort: port 0x[hex] not on listExplanation The destination logical unit (DLU) is trying to remove a nonexistent port from the list of active ports because it does not have the correct list of active ports.
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
%CLSDR-3-WRONGMSG: Should never be here, cls message type unknown 0x[hex]Explanation The Cisco link services (CLS) message type is unknown to the destination logical unit (DLU).
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 ATM line card driver error messages.
Error Message
%CM622_CM155-4-ATMCLKINT: ([dec]/[dec]) ATM Clock Internal Set on ([dec]/[dec]) tooExplanation CM155 ATM Clock Internal is enabled for the other channel on the same framer, and the framer defines one bit for both channels.
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
%CM622_CM155-4-FRMROP: Error: ([dec]/[dec]) [chars] (value=0x[hex])Explanation A line card ATM driver framer operation 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
%CM622_CM155-4-FWCKSUM: [chars] SAR firmware selftest failure (expected 0x[hex], obtained 0x[hex])Explanation A line card ATM segmentation and reassembly (SAR) firmware checksum has error 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
%CM622_CM155-4-OP: Error: ([dec]/[dec]) [chars]Explanation A line card ATM driver general operation error 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
%CM622_CM155-4-RPCMD: [chars] command error: [chars]Explanation An error involving a line card ATM driver Route Processor (RP) command 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
%CM622_CM155-4-RXSARIND: ([dec]/[dec]) RX SAR doing [chars] error: [chars] (indication=0x[hex] 0x[hex] 0x[hex])Explanation A line card ATM driver RX segmentation and reassembly (SAR) indication 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
%CM622_CM155-4-SAROP: [chars] SAR doing [chars] error: [chars]Explanation A line card ATM driver segmentation and reassembly (SAR) operation 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
%CM622_CM155-4-TXSARIND: TX SAR [chars] command error: [chars] (indication=0x[hex])Explanation A line card ATM driver TX segmentation and reassembly (SAR) indication 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
%CM622_CM155-4-VCCLOSE: ([dec]/[dec]) VC:[int] is close pendingExplanation The virtual circuit (VC) is in the TX segmentation and reassembly (SAR) close pending 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
%CM622_CM155-4-VCCMD: ([dec]/[dec]) VC:[int] [chars] error (cause: [chars])Explanation A CM622 or a CM155 ATM segmentation and reassembly (SAR) virtual circuit (VC) operation 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
%CM622_CM155-4-VCTYPE: ([dec]/[dec]) VC:[int] unsupported vc encapsulation type=[int]Explanation A CM622 or a CM155 ATM segmentation and reassembly (SAR) virtual circuit (VC) operation error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Multimedia Cable Network System Partners, Ltd. (MCNS), baseline privacy key management error messages.
Error Message
%CMBPKM-1-AUTHREJECT: Authorization request rejected by CMTS: [chars]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.
Error Message
%CMBPKM-1-KEYREJECT: Key request rejected by CMTS: [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Cisco Mainframe Channel Connection (CMCC) interfaces error messages.
Error Message
%CMCC-6-ADAPTERCHNG: Interface [chars]: adapter type changed from [chars] to [chars]Explanation The interface has reported a different interface type from what reported previously. The interface should not report a different interface type unless the Cisco Mainframe Channel Connection (CMCC) card was removed and replaced with one that has an interface of the reported type.
Recommended Action No action is required.
Error Message
%CMCC-4-BADENCAPSZ: Interface [chars]: encapsulated msg size ([dec]) exceeds max ([dec] truncatedExplanation An encapsulated control message had a size greater than the maximum expected size. The message was truncated.
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
%CMCC-3-CFGCMDDROPPED: Config queue is full, command was dropped, slot [dec]Explanation A configuration command was resent, but the receiving queues were still full. Therefore, the command was dropped.
Recommended Action Issue the debug channel events command and try each of the following tasks in sequence. If an action corrects the problem, you are not required to do the remaining tasks. Reissue the configuration command.
If the error recurs, copy the error message exactly as it appears. Record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%CMCC-4-CFGFAIL: Interface [chars]: configuration command [chars] [chars] failedExplanation An error occurred when the configuration command was sent to the Cisco Mainframe Channel Connections (CMCC) card, or the CMCC negatively acknowledged the command.
Recommended Action Reissue the configuration command.
Error Message
%CMCC-4-DTRFAIL: Interface [chars]: Channel-protocol [chars] cmd failed; resetting to defaultExplanation The channel-protocol configuration command sent after a reset has failed to complete successfully. The channel data transfer rate was reset to the default value.
Recommended Action Reissue the configuration command.
Error Message
%CMCC-3-NODEED: Interface [chars]: No elements avail for msg ([hex] [hex] interface resetExplanation An encapsulated control message has arrived, but no elements were available to receive it. It is likely that a configuration will now be in a PENDING state. An interface reset was attempted to clear this condition.
Recommended Action Issue the debug channel events command and try each of the following tasks in sequence. If an action corrects the problem, you will not be required to do the remaining tasks.
If the error recurs, copy the error message exactly as it appears. Record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%CMCC-3-NOENABLE: Interface [chars]: No preallocated buffers available; enable not sentExplanation An attempt to get a preallocated buffer for the enable command was unsuccessful. The interface will not be enabled.
Recommended Action Issue the debug channel events command and try each of the following tasks in sequence. If an action corrects the problem, you will not be required to do the remaining tasks.
If the error recurs, copy the error message exactly as it appears. Record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%CMCC-4-NOPREQ: Interface [chars]: Unable to pre allocate response element; cfg not sentExplanation An attempt to allocate a buffer for the configuration response, or for the configuration state change request, was unsuccessful. The configuration request was not sent.
Recommended Action The configuration command must be reissued.
Error Message
%CMCC-3-RSETFAIL: Interface [chars]: Error ([hex]) [chars]Explanation An error occurred when the interface enable or disable command was used.
Recommended Action The interface was reset by the software. If the problem was not resolved issue the debug channel events command and try each of the following tasks in sequence. If an action corrects the problem, you will not be required to do the remaining tasks.
If the error recurs, copy the error message exactly as it appears. Record the output from the following commands:
Provide this information to your Cisco technical support representative.
Error Message
%CMCC-3-SMALLENCAPSZ: Interface [chars]: encaps msg size ([dec]) smaller than min ([dec] droppedExplanation An encapsulated control message had a smaller size than the minimum expected size. The message was dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CMCC-3-UNKENCAP: Interface [chars]: unknown encapsulated msg([dec]) len([dec])Explanation An encapsulated control message had an unknown encapsulation type. The message was dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Digital Signal Processor Resource Manager (DSPRM) error messages.
Error Message
%CM_DSPRM-1-INTERNALERROR: DSPRM internal error[[chars]:[dec]Explanation The router or access server has detected an internal 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
%CM_DSPRM-1-NODSPRMEVENTS: DSPRM event unavailableExplanation The router or access server could not allocate internal resources.
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
%CM_DSPRM-1-NOIOSBUFFERS: IOS buffer pool unavailable [[chars]:[dec]]Explanation The router or access server could not allocate internal resources.
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
%CM_DSPRM-1-NOIOSMEMORY: IOS memory unavailable [[chars]:[dec]]Explanation The router or access server could not allocate memory for internal data structures.
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 Cisco Network Services Event Service Client error messages.
Error Message
%CNSES-4-NODNS: DNS lookup failedExplanation A lookup attempt for the IP address of a router through Domain Name Server (DNS) has failed.
Recommended Action Configure DNS on the router, or enter the ip host command.
Error Message
%CNSES-4-NODNS_USEHOST: DNS lookup failed, use Hostname [chars] insteadExplanation A lookup attempt for the IP address of a router through Domain Name Server (DNS) failed.
Recommended Action Configure DNS on the router, or enter the ip host command.
Error Message
%CNSES-3-SOCSELECT: Server socket listener failed: port=[dec] errno=[dec]Explanation The attempt to emulate a TCP server has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CNSES-3-SRVR_ERROR: CNS/AD Event Service Server cannot be startedExplanation The attempt to start Cisco Networking Services (CNS)/ AD Event Service Server failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CNSES-6-TESTAPP: ...Test App app_id=[dec] Callback ...Explanation The local IP address has been found.
Recommended Action No action is required.
Cisco Network Services (CNS) Configuration Change Agent error messages.
Error Message
%CNS_AGENT_CFGCHG-3-SRVR_ERROR: CNS Config Change Agent cannot be startedExplanation The attempt to start the CNS configuration change agent failed for one of several possible reasons.
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
%CNS_AGENT_CFGCHG-6-TESTAPP: ...CNS Config Change Agent=[dec] Callback ...Explanation This is only a status message.
Recommended Action No action is required.
The following are point-to-point compression error messages.
Error Message
%COMP-3-BADCOMP: Interface [chars] Bad status returned from packet compression operationExplanation 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
%COMP-3-BADCRC: Interface [chars] Decompression check-byte data is incorrectExplanation 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
%COMP-3-BADSEQNUM: Interface [chars] Unexpected compressed packet sequence numberExplanation A packet drop or transient line error has occurred, but it will self-correct.
Recommended Action No action is required.
Error Message
%COMP-3-COMPERR: [chars]: COMPRESS: (stac error!) status: [dec], size in: [dec], size out: [dec]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.
Error Message
%COMP-3-CONFIGBAD: Interface [chars] Compression internal configuration errorExplanation 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
%COMP-3-DESTEXST: Interface [chars] Destination decompression buffer ran out of spaceExplanation 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
%COMP-5-NOBUF: Interface [chars] [chars]Explanation An interface serial0 compression getbuffer failed, causing Link Access Procedure, Balanced (LAPB) retransmissions.
Recommended Action Configure large additional buffers.
Error Message
%COMP-3-NOEND: Interface [chars] No end-bit detected on compressed packetExplanation 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
%COMP-3-SIZEBAD: Interface [chars] Decompression size errorExplanation Both interfaces need to be configured for predictor compression. This message indicates that only one interface is configured for predictor compression.
Recommended Action Configure both interfaces for predictor compression.
Error Message
%COMP-3-SRCREMAINS: Interface [chars] Not all packet data was used by decompressorExplanation 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
%COMP-3-SUBBLOCKERR: Interface [chars] compression subblock creation failed.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.
Error Message
%COMP-3-SYNCBAD: Interface [chars] Decompression sync errorExplanation Both interfaces need to be configured for predictor compression. This message indicates that only one interface is configured for predictor compression.
Recommended Action Configure both interfaces for predictor compression.
Error Message
%COMP-3-VERSIONBAD: Interface [chars] Compression Version mismatch expected [hex] received [hex]Explanation Both interfaces need to be configured for predictor compression. This message indicates that only one interface is configured for predictor compression.
Recommended Action Configure both interfaces for predictor compression.
The following are continuity test (COT) error messages.
Error Message
%COT-1-DSP_MEM: [chars]Explanation No memory was allocated for the continuity test (COT) digital signal processor (DSP) event queue.
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
%COT-1-DSP_Q: [chars]Explanation A digital signal processor (DSP) event was not added to the continuity test (COT) DSP event queue.
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
%COT-1-INITSYS: [chars]Explanation A periodic process, chunk pool, continuity test (COT) queue, or digital signal processor (DSP) queue for COT was not created.
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 pulse amplitude modulation (PAM) port driver error messages.
Error Message
%COUGAR_EHSA-4-ACPM_CAPABILITY:Explanation The primary and secondary ACPM capabilities do not match.
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
%COUGAR_EHSA-5-CAPABILITY:Explanation The capabilities of the primary and secondary ACPMs match fully and the system is operating in a fully redundant configuration.
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
%COUGAR_EHSA-3-CAP_REQ_FAIL: Unable to send Capability request to the secondary, even after 10 retries (over 100 seconds)Explanation Capability requests cannot be sent to the secondary ACPM.
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
%COUGAR_EHSA-3-CPU_MISMATCH_FUNCVER_MAJOR:Explanation A mismatch in the CPU Major Functional Version number between the primary and secondary ACPMs has occurred. This mismatch can cause the loss of functionality that is currently available in the primary ACPM, in the event of a CPU switchover. The system is now running in a conditionally redundant state and is therefore at risk of losing some functionality currently available in the primary ACPM in the event of a CPU switchover.
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
%COUGAR_EHSA-4-CPU_MISMATCH_FUNCVER_MINORExplanation The primary ACPM has a different CPU minor version number that is different from the CPU minor version number of the secondary ACPM. The primary and secondary ACPMs should have identical packet memory sizes. This mismatch can cause the loss of functionality that is currently available in the primary ACPM, in the event of a CPU switchover. The system is now running in a conditionally redundant state and is therefore at risk of losing some functionality currently available in the primary ACPM in the event of a CPU switchover.
Recommended Action Copy the message exactly as it appears in the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information
Error Message
%COUGAR_EHSA-3-CPU_MISMATCH_HWVER_MAJOR:Explanation A mismatch in the CPU Major Functional Version number between the primary and secondary ACPMs has occurred. This mismatch can cause the loss of functionality that is currently available in the primary ACPM, in the event of a CPU switchover. The system is now running in a conditionally redundant state and is therefore at risk of losing some functionality currently available in the primary ACPM in the event of a CPU switchover.
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
%COUGAR_EHSA-4-CPU_MISMATCH_HWVER_MINOR:Explanation The primary ACPM has a CPU minor hardware version number that is different from the CPU minor hardware version number of the secondary ACPM. This mismatch can cause the loss of functionality that is currently available in the primary ACPM, in the event of a CPU switchover. The system is now running in a conditionally redundant state and is therefore at risk of losing some functionality currently available in the primary ACPM in the event of a CPU switchover.
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
%COUGAR_EHSA-3-DRAM_MISMATCH:Explanation There is a mismatch in the dynamic random-access memory (DRAM) size between primary and secondary ACPMs. The primary and secondary ACPMs should have identical DRAM sizes. The mismatch may cause some connections to be lost in the event of a CPU switchover. The system is now running conditionally redundant, and will therefore be at risk of losing connections in the event of a CPU switchover, until the DRAM sizes are made identical in the hardware.
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
%COUGAR_EHSA-3-DRIVER_FUNCVER_MISMATCH:Explanation A mismatch in the functional version of a driver between the two CPUs has occurred. This mismatch may cause a loss of functionality of the corresponding controller and may result in a loss of connections. The system will be conditionally redundant until this mismatch is resolved by upgrading the software on the secondary CPU.
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
%COUGAR_EHSA-3-DRIVER_MISSING:Explanation The driver support in the Secondary CPU is missing. The driver in the primary CPU is not available in the Secondary CPU. The missing driver support will cause the corresponding pulse amplitude modulation (PAM) to go down in the event of a switchover, causing a loss of connections going through that controller. The system will be conditionally redundant until this mismatch is resolved by upgrading the software on the secondary CPU.
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
%COUGAR_EHSA-3-FEAT_ABSENT:Explanation The switch card in one slot does not have the same feature card hardware as the switch card in the other slot. The mismatch in feature card hardware is an invalid hardware configuration. The switch cards will not come up until the feature card hardware on the switch cards match.
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
%COUGAR_EHSA-3-FEAT_FUNCVER_MISMATCH:Explanation The switch card in one slot does not have the same switch card functional version number as the switch card in the other slot. The mismatch in switch feature card version numbers is an invalid hardware configuration. The switch cards will not be brought up until their switch feature card version numbers match.
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
%COUGAR_EHSA-3-FEAT_FUNCVER_RED_MISMATCH:Explanation The switch card in one slot does not have the same switch card functional version number as the switch card in the other slot. The mismatch in switch feature card version numbers is an invalid hardware configuration. The redundant switch card will not be brought up, and the system is running in a nonredundant mode. In the event of a switch card failure, the system will go 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
%COUGAR_EHSA-3-FEAT_HWVER_MISMATCH:Explanation The switch card in one slot does not have the same switch card functional version number as the switch card in the other slot. The mismatch in switch feature card version numbers is an invalid hardware configuration. The switch cards will not be brought up until their hardware versions match.
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
%COUGAR_EHSA-3-FEAT_HWVER_RED_MISMATCH:Explanation The switch card in one slot does not have the same functional version number as the switch card in the other slot. The mismatch in switch feature card version numbers is an invalid hardware configuration. The redundant switch card will not be brought up, and the system is running in a nonredundant mode. In the event of a switch card failure, the system will go 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
%COUGAR_EHSA-4-FLASH_MISMATCH:Explanation The primary ACPM has a BOOTFLASH SIMM size different from the BOOTFLASH SIMM size of the secondary ACPM. The primary and secondary ACPMs should have identical BOOTFLASH SIMM sizes. Because of the BOOTFLASH SIMM size mismatch, the files that fit in the BOOTFLASH of the primary ACPM may not fit in the BOOTFLASH of the secondary ACPM, if and when a switchover occurs. Inadequate space for the files may cause a loss of information. The system is now running in a conditionally redundant state and is therefore at risk of information loss in the event of a CPU switchover.
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
%COUGAR_EHSA-3-NCLK_ABSENT:Explanation The primary ACPM has a network clock module, but the secondary ACPM does not have one. The missing network clock module may lead to loss of network clocking functionality, in the event of a CPU switchover. The system is now running in a conditionally redundant state and is therefore at risk of losing networking functionality in the event of a CPU switchover.
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
%COUGAR_EHSA-3-NCLK_FUNCVER_MISMATCH:Explanation The primary ACPM has a different network clock functional version number from the secondary ACPM. The mismatch in network clock functional version numbers may lead to a loss of network clocking functionality if and when a CPU switchover occurs. The system is now running in a conditionally redundant state and is therefore at risk of losing network clocking functionality in the event of a CPU switchover.
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
%COUGAR_EHSA-4-NCLK_HWVER_MISMATCH:Explanation The primary ACPM has a network clock module version different from the network clock module version of the secondary ACPM. The mismatch in network clock module versions may lead to a loss of network clocking functionality in the event of a CPU switchover. The system is now running in a conditionally redundant state and is therefore at risk of losing network clocking functionality in the event of a CPU switchover. Refer to the hardware reference guide to find out the exact functional differences between the two hardware versions.
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
%COUGAR_EHSA-3-NVRAM_MISMATCH:Explanation The primary ACPM has a different nonvolatile RAM (NVRAM) size from the NVRAM size of the secondary ACPM. The mismatch in NVRAM sizes may lead to a loss of configuration information if and when a CPU switchover occurs. The system is now running in a conditionally redundant state and is therefore at risk of losing configuration information in the event of a CPU switchover.
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
%COUGAR_EHSA-3-PMEM_MISMATCH:Explanation The primary ACPM has a different packet memory size from the packet memory size of the secondary ACPM. The primary and secondary ACPMs should have identical packet memory sizes. The mismatch in packet memory sizes may lead to a loss of some connections if and when a CPU switchover occurs. The system is now running in a conditionally redundant state and is therefore at risk of losing some connections in the event of a CPU switchover.
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
%COUGAR_EHSA-3-SWC_FUNCVER_MISMATCH:Explanation The switch card in one slot does not have the same functional version number as the switch card in the other slot. The mismatch in switch card functional version numbers is an invalid hardware configuration. The switch cards will not be brought up until their functional version numbers match.
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
%COUGAR_EHSA-3-SWC_FUNCVER_RED_MISMATCH:Explanation The switch card in one slot does not have the same functional version number as the switch card in the other slot. The mismatch in switch card version numbers is an invalid hardware configuration. The redundant switch card will not be brought up, and the system is running in a nonredundant mode. In the event of a switch card failure, the system will go 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
%COUGAR_EHSA-3-SWC_HWVER_MISMATCH_MAJOR:Explanation The switch card in one slot does not have the same major version number as the switch card in the other slot. The mismatch in switch card major version numbers is an invalid hardware configuration. The switch cards will not be brought up until their major version numbers match.
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
%COUGAR_EHSA-3-SWC_HWVER_MISMATCH_MINOR:Explanation The switch card in one slot does not have the same minor version number as the switch card in the other slot. The mismatch in switch card minor version numbers is an invalid hardware configuration. The switch cards will not be brought up until their major version numbers match.
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
%COUGAR_EHSA-3-SWC_HWVER_RED_MISMATCH_MAJOR:Explanation The switch card in one slot does not have the same major version number as switch card in the other slot. The mismatch in switch card major version numbers is an invalid hardware configuration. The redundant switch card will not be brought up and the system is running in a nonredundant mode. In the event of a switch card failure, the system will go 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
%COUGAR_EHSA-3-SWC_HWVER_RED_MISMATCH_MINOR:Explanation The switch card in one slot does not have the same minor version number as the switch card in the other slot. The redundant switch card will not be brought up, and the system is running in a nonredundant mode. In the event of a switch card failure, the system will go 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
%COUGAR_EHSA-3-SWC_TABLE_MISMATCH:Explanation The switch card in one slot does not have the same table size as the switch card in the other slot. The switch cards will not be brought up until their table sizes match.
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
%COUGAR_EHSA-4-SWC_TABLE_RED_MISMATCH:Explanation The switch card in one slot does not have the same table size as the the switch card in the other slot. The redundant switch card will not be brought up, and the system is running in a nonredundant mode. In the event of a switch card failure, the system will go 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.
The following are compression service adapter (CSA) error messages.
Error Message
%CPAD-1-ERROR: [chars]: [chars]Explanation An error has occurred in the application using the compression service adapter (CSA).
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
%CPAD-1-INITFAIL: Slot [dec]: [chars]Explanation The compression service adapter (CSA) driver failed to initialize at the specified point.
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
%CPAD-1-NOMEMORY: [chars] creation failed for slot [dec]Explanation The compression service adapter (CSA) driver, in its initialization phase, could not allocate memory for the specified data structure.
Recommended Action Consider adding more shared memory. 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
%CPAD-1-PLXINIT: bay [dec] Invalid vendor/device id [dec]Explanation The compression service adapter (CSA) driver, during its initialization phase, encountered a communication failure with the CSA in the specified bay.
Recommended Action Consider reseating the specified CSA. 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
%CPAD-1-SHUTCARD: bay [dec]: Deactivating cardExplanation An error occurred during initialization. The compression service adapter (CSA) is being deactivated.
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
%CPAD-6-SHUTDOWN: [chars] shutting downExplanation The specified compression service adapter (CSA) is shutting down. It may have been physically removed.
Recommended Action No action is required.
Error Message
%CPAD-6-STARTUP: [chars] starting upExplanation The specified compression service adapter (CSA) has initialized successfully.
Recommended Action No action is required.
The following are Combo Port Module (CPM) device driver error messages.
Error Message
%CPM-3-DISCOVER: CPM at slot [dec]: PCI discovery failed count = [dec]Explanation One of the interface controller devices on the module did not initialize properly.
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
%CPM-3-INCORRECT_ID: CPM at slot [dec]: PCI device not supportedExplanation An interface controller device did not report the correct protocol control information (PCI) device ID.
Recommended Action Power down, reinsert the port module, and reboot. If the message recurs, call your Cisco technical support representative for assistance.
The following are encryption error messages.
Error Message
%CRYPTO-0-AUDITFAIL: Encryption audit check found the wrong level of encryption in this imageExplanation The audit check that verifies encryption entitlement within Cisco IOS images has found either encryption in a nonencryption image or the wrong strength within a Cisco IOS encryption image. Use of the encryption may violate U.S. export laws and regulations.
Recommended Action Contact Cisco to obtain a replacement Cisco IOS image.
Error Message
%CRYPTO-4-AUDITWARN: Encryption audit check could not be performedExplanation The audit check verifying encryption entitlement within the Cisco IOS image could not be performed because of incomplete system configuration.
Recommended Action Manually verify that this Cisco IOS image is entitled to contain encryption.
Error Message
%CRYPTO-3-BADFP: Certificate fingerprint mismatch for certificate - certificate not acceptedExplanation The fingerprint of a certificate received from a Certificate Authority did not match a fingerprint saved in nonvolatile RAM (NVRAM). The certificate may not be valid.
Recommended Action Contact the Certificate Authority administrator to compare the certificate fingerprint manually.
Error Message
%CRYPTO-3-BADMAGIC: Bad [chars] magic number ([hex])Explanation An internal software has error 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
%CRYPTO-3-CERTCHECK: Certificate with invalid status has been detected!!!Explanation After checking the certificates saved in the memory with the certificate revocation list (CRL), the system has detected invalid certificates.
Recommended Action Check the status and contact Certification Authority (CA) administrator. Enrollment may be required.
Error Message
%CRYPTO-6-CERTFAIL: Certificate enrollment failedExplanation The certificate enrollment has encountered a fatal error.
Recommended Action Contact the Certification Authority (CA) administrator.
Error Message
%CRYPTO-6-CERTPENDING: Enter manual authentication ...Explanation The Certification Authority (CA) server may request the user to authenticate the router manually.
Recommended Action Follow the manual authentication procedure.
Error Message
%CRYPTO-6-CERTREJECT: Certificate enrollment request was rejected by Certificate AuthorityExplanation The previously sent certificate enrollment request has been received by the Certificate Authority. The Certificate Authority has rejected the enrollment request.
Recommended Action Contact the Certificate Authority administrator.
Error Message
%CRYPTO-6-CERTRET: Certificate received from Certificate AuthorityExplanation The previously sent certificate enrollment request has been received by the Certificate Authority. The Certificate Authority has issued the certificate and sent back a copy.
Recommended Action No action is required.
Error Message
%CRYPTO-3-CERTRETFAIL: Certificate enrollment failedExplanation The certificate enrollment (CE) transaction has failed because of an internal error.
Recommended Action Contact a CE administrator.
Error Message
%CRYPTO-6-CERT_FATAL_ERR: [chars]Explanation The certificate enrollment has encountered a fatal error and will abort.
Recommended Action Contact the Certification Authority (CA) administrator.
Error Message
%CRYPTO-6-ENROLL_CANCEL: Certificate enrollment is canceledExplanation The current certificate enrollment is cancelled.
Recommended Action Retry the system again when it is ready.
Error Message
%CRYPTO-3-GETCACERT: Failed to find CA cert in memoryExplanation The Certification Authority (CA) certificate was not found in memory.
Recommended Action Check the status and contact the CA administrator.
Error Message
%CRYPTO-3-GETCARACERT: Failed to receive RA/CA certificatesExplanation Certification Authority (CA) or Registration Authority (RA) certificates could not be parsed or processed.
Recommended Action Check the status and contact the CA administrator.
Error Message
%CRYPTO-6-GETCERTINITIAL: Certificate enrollment failed in manual modeExplanation The current certificate enrollment has failed in manual mode.
Recommended Action Contact the Certificate Authority (CA) administrator.
Error Message
%CRYPTO-3-GETCRL: Query the Certificate Revocation List from CA failedExplanation The attempt to query the Certificate Revocation List from the Certificate Authority (CA) server failed for one of several possible reasons.
Recommended Action Contact the CA administrator.
Error Message
%CRYPTO-3-HTTPSEND: Failed to send out message to CA server.Explanation A failure was caused by an HTTP transaction.
Recommended Action Check the HTTP connection to the Certification Authority (CA) server
Error Message
%CRYPTO-6-IKE_TED_BAD_REPLY: Received TED reply that did not correspond to a TED probeExplanation The received Tunnel Endpoint Discovery (TED) reply does not match the TED probe currently outstanding. The mismatch may be a one-time occurrence caused by the delay of the TED reply. It may also be caused by ill-formed packets sent by the peer. This activity could be considered a "hostile event" such as an attempt by an unauthorized user to break into a network.
Recommended Action If the problem occurs more than once, contact the peer administrator.
Error Message
%CRYPTO-3-IKMPPAKFAIL: Failed to build reply packetExplanation A reply packet could not be built as part of an Internet Key Exchange (IKE). This error can be caused by a shortage of memory or a failure of the hardware or software of the encryption engine.
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
%CRYPTO-6-IKMP_ADD_KEY_FAIL: Unable to add public key for [chars] (%15i) to key ringExplanation Keys are stored in key rings on the router. An attempt to add another key to the ring has failed.
Recommended Action Check the local key rings. This error was probably caused by other failures.
Error Message
%CRYPTO-6-IKMP_AUTH_FAIL: Authentication method [dec] failed with host %15iExplanation The Internet Key Exchange (IKE) process was unable to authenticate its security association with its remote peer.
Recommended Action Contact the administrator of the remote peer.
Error Message
%CRYPTO-6-IKMP_BAD_CERT_USE: Certificate for peer at %15i prohibits attempted use ([chars])Explanation X.509v3 certificates can contain usage restrictions that limit the use of the certificate for signatures or for key exchange (encryption). The peer attempted to use the certificate in a manner that violated these restrictions.
Recommended Action Contact the remote peer and the Certification Authority (CA) of the remote peer.
Error Message
%CRYPTO-6-IKMP_BAD_DOI_NOTIFY: DOI of [dec] in notify message from %15iExplanation The Domain of Interpretation (DOI) field in the notify messages gives the receiver a context in which to understand the message being notified. This DOI value is not understood, and therefore the message cannot be understood.
Recommended Action If this situation persists, contact the remote peer.
Error Message
%CRYPTO-6-IKMP_BAD_DOI_SA: DOI value [dec] from SA offer from %15i is invalidExplanation The Domain of Interpretation (DOI) field of a security association (SA) offer defines how to parse the fields. The SAs that have an unknown DOI cannot be parsed.
Recommended Action If this situation persists, contact the administrator of the remote peer.
Error Message
%CRYPTO-4-IKMP_BAD_MESSAGE: IKE message from %15i failed its sanity check or is malformedExplanation A quick verification check is done on all received Internet Key Exchange (IKE) messages to ensure that all component payload types are valid and that the sum of their individual lengths equals the total length of the received message. This message indicates a failed verification check. Persistently bad messages could mean a denial-of-service attack or bad decryption.
Recommended Action Contact the administrator of the remote peer.
Error Message
%CRYPTO-6-IKMP_CRYPT_FAILURE: IKE (connection id [dec]) unable to [chars] packetExplanation Encryption or decryption on a particular Internet Key Exchange (IKE) thread has failed.
Recommended Action Contact the remote peer.
Error Message
%CRYPTO-5-IKMP_INVAL_CERT: Certificate received from %15i is bad: [chars]Explanation The certificate given by remote peer either has been revoked or has expired (the certificate is invalid) or the signature check on the certificate has failed (invalid signature).
Recommended Action Contact the Certification Authority (CA) of the remote peer. The CA certificate may be invalid.
Error Message
%CRYPTO-6-IKMP_MODE_FAILURE: Processing of [chars] mode failed with peer at %15iExplanation Negotiation with the remote peer has failed.
Recommended Action If this situation persists, contact the remote peer.
Error Message
%CRYPTO-6-IKMP_NO_ID_CERT_ADDR_MATCH: ID of %15i (type [dec]) and certificate addr with %15iExplanation Internet Key Exchange (IKE) entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information taken from the IP address of the peer certificate.
Recommended Action If this situation persists, contact the remote peer.
Error Message
%CRYPTO-6-IKMP_NO_ID_CERT_DN_MATCH: ID of [chars] (type [dec]) and certificate DN with [chars]Explanation Internet Key Exchange (IKE) entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the identity information taken from the name on the peer certificate.
Recommended Action If this situation persists, contact the remote peer.
Error Message
%CRYPTO-6-IKMP_NO_ID_CERT_FQDN_MATCH: ID of [chars] (type [dec]) and certificate fqdn with [chars]Explanation Internet Key Exchange (IKE) entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information taken from the fully qualified domain name (FQDN) of the peer certificate.
Recommended Action If this situation persists, contact the remote peer.
Error Message
%CRYPTO-6-IKMP_NO_ID_CERT_USER_FQDN_MATCH: ID of [chars] (type [dec]) and certificate user fqdn with [chars]Explanation Internet Key Exchange (IKE) entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information taken from the fully qualified domain name (FQDN) of the peer certificate.
Recommended Action If this situation persists, contact the remote peer.
Error Message
%CRYPTO-6-IKMP_NOT_ENCRYPTED: IKE packet from %15i was not encrypted and it should've beenExplanation A portion of the Internet Key Exchange (IKE) is unencrypted and a portion is encrypted. This message should have been encrypted but was not.
Recommended Action Contact the remote peer.
Error Message
%CRYPTO-4-IKMP_NO_SA: IKE message from %15i has no SA and is not an initialization offerExplanation Internet Key Exchange (IKE) maintains the state for a communication in the form of security associations. No security association exists for this packet, and it is not an initial offer from the peer to establish one. This situation could denote a denial-of-service attack.
Recommended Action Contact the remote peer and the administrator of the remote peer.
Error Message
%CRYPTO-3-IKMP_PEER_INIT_FAILURE: IKE failed to create IKE peer tree.Explanation Internet Key Exchange (IKE) failed to allocate memory for the IKE peer tree.
Recommended Action More DRAM may be required in order to run the image.
Error Message
%CRYPTO-4-IKMP_PKT_OVERFLOW: ISAKMP message from %15i larger (%ld) than the UDP packet length (%ld)Explanation Internet Key Exchange (IKE) messages are carried in User Datagram Protocol (UDP) packets and have their own message length field. The message length field of this message was greater than the length of the UDP packet. This situation could indicate a denial-of-service attack.
Recommended Action Contact the remote peer and the administrator of the remote peer.
Error Message
%CRYPTO-6-IKMP_SA_NOT_AUTH: Cannot accept Quick Mode exchange from %15i if SA is not authenticated!Explanation Even though the Internet Key Exchange (IKE) security association with the remote peer was not authenticated, the peer attempted to begin a Quick Mode exchange. This exchange can be performed only with an authenticated security association.
Recommended Action Contact the remote peer.
Error Message
%CRYPTO-6-IKMP_SA_NOT_OFFERED: Remote peer %15i responded with attribute [chars] not offered or changedExplanation Internet Key Exchange (IKE) peers negotiate policy by having the initiator offer a list of possible protection suites. The responder has returned a protection suite type that the initiator did not offer.
Recommended Action Contact the remote peer.
Error Message
%CRYPTO-6-IKMP_UNK_EXCHANGE: IKE peer at %15i sent a message with unknown exchange [dec]Explanation Internet Key Exchange (IKE) performs actions on messages based on defined exchanges. The message received had an unknown exchange.
Recommended Action Contact the administrator of the remote peer.
Error Message
%CRYPTO-3-INVALIDCACERT: Failed to process CA certificateExplanation The Certification Authority (CA) certificate received from the CA server could not be processed.
Recommended Action Use the crypto ca authenticate command and try again. If the problem persists, 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
%CRYPTO-3-INVALID_INPUT: The input to the parser command is not correctExplanation The input to the parser command is not correct.
Recommended Action Repeat the command. If the problem persists, 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
%CRYPTO-3-PKIINPUT: Wait response from server ....Explanation The public key infrastructure (PKI) client is waiting for the response from the server.
Recommended Action No action is required.
Error Message
%CRYPTO-4-PKT_REPLAY_ERR: [chars] connection id=[dec]Explanation The replay processing has failed. The failed replay processing may be a temporary condition caused by the wait for new security associations (SAs) to be established. In the inbound case, this error may also be caused by an actual replay attack. This activity might be considered a "hostile event" such as an attempt by an unauthorized user to break into a network.
Recommended Action If the problem appears to be more than a transient one, contact the peer administrator.
Error Message
%CRYPTO-3-POLLCACERT: Polling CA certificate .....Explanation Polling Certification Authority (CA) certificate.
Recommended Action Check if the CA or (IDAP) server is online.
Error Message
%CRYPTO-3-POLLING: Polling for certificate response...Explanation GetCertInitial is polling for a certificate response.
Recommended Action Wait for the server response or cancel the polling. If the problem persists, 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
%CRYPTO-3-POLLRACERT: Polling RA certificate .....Explanation Polling for a Registration Authority (RA) certificate.
Recommended Action Check if Certification Authority (CA) or IDAP server is online.
Error Message
%CRYPTO-3-POLLROUTERCERT: Polling Router certificate .....Explanation Polling for a router certificate.
Recommended Action Check if Certification Authority (CA) or IDAP server is online.
Error Message
%CRYPTO-6-PRINTABORT: [chars] caused early termination of show output[chars]Explanation While a list was being shown, the list or the elements changed. The list or the elements can change if the security associations (SAs) were renegotiated at the time that the show command was paused, or if a user reconfigured or cleared the SAs. This is not an error, but a side effect of a dynamic system.
Recommended Action In general, this is merely a warning that the output from the show command is probably incomplete. Reentering the show command should provide the newest information. On a busy system, with SAs that change often, this message may appear frequently.
Error Message
%CRYPTO-3-QUERYCACERT: Failed to query CA certificateExplanation A query against the Certification Authority (CA) certificate from the CA server failed.
Recommended Action Use the crypto ca authenticate command and try again.
Error Message
%CRYPTO-3-QUERYRACERT: Failed to query RA certificateExplanation Registration Authority (RA) certificates could not be found.
Recommended Action Check if the Certification Authority (CA) or IDAP server is online.
Error Message
%CRYPTO-3-QUERYROUTERCERT: Failed to query router certificate.Explanation A query against the router certificate has failed.
Recommended Action Check if the Certification Authority (CA) or IDAP server is online.
Error Message
%CRYPTO-3-QUERY_KEY: Querying key pair failedExplanation The attempt to query the public key/private key using the subject name has failed.
Recommended Action Resubmit the enrollment request. Check the subject name. If the problem persists, 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
%CRYPTO-4-RECVD_PKT_FAIL_DECOMPRESS: pcp: [dec] byte packet failed to decompress pcp: dest_addr=[int], src_addr=[int]Explanation The received IPPCP packet failed to decompress, because of a decompression buffer 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
%CRYPTO-4-RECVD_PKT_INV_IDENTITY: [chars] (ip) dest_addr= [int], src_addr= [int], prot= [dec] (ident) local=[int], remote=[int] local proxy=[int]/[int]/[dec]/[dec], remote_proxy=[int]/[int]/[dec]/[dec]Explanation A decapsulated IP Security Protocol (IPSec) packet does not match the negotiated identity. An security association (SA) selection error is causing the peer to send other traffic through this SA. This activity could be considered a "hostile event" such as an attempt by an unauthorized user to break into a network.
Recommended Action Contact the peer administrator to compare policy settings.
Error Message
%CRYPTO-4-RECVD_PKT_INV_IDENTITY_ACL: ipsec check access: identity not allowed by ACL (ip) dest_addr= [int], src_addr= [int], prot= [dec]Explanation A decapsulated packet has failed the Access Control Lists (ACL) check. The peer is sending other traffic through this security association (SA). It may be caused by an SA selection error by the peer. This activity could be considered a "hostile event" such as an attempt by an unauthorized user to break into a network.
Recommended Action Contact the peer administrator to compare policy settings.
Error Message
%CRYPTO-4-RECVD_PKT_INV_PROT: decapsulate: packet missing [chars], destadr=[int], actual prot=[dec]Explanation A received IP Security Protocol (IPSec) packet was missing an expected Authentication Header (AH) or Extended Services Processor (ESP) header. The peer is sending packets that do not match the negotiated security policy. This activity could be considered a "hostile event" such as an attempt by an unauthorized user to break into a network.
Recommended Action Contact the peer administrator.
Error Message
%CRYPTO-4-RECVD_PKT_INV_SPI: decaps: rec'd IPSEC packet has invalid spi for destaddr=[int], prot=[dec], spi=0x[hex]([dec])Explanation A received IP Security Protocol (IPSec) packet specifies security parameter index (SPI) that does not exist in the security association database (SADB). This may be a temporary condition because of slight differences in aging of SAs between the IPSec peers, or because the local SAs have been cleared. It may also be caused by invalid packets being sent by the IPSec peer. This activity could be considered a "hostile event" such as an attempt by an unauthorized user to break into a network.
Recommended Action If the local SAs have been cleared, the peer may not know. In this case, if a new connection is established from the local router, the two peers may reestablish connection successfully. If the problem occurs for more than a brief period, either attempt to establish a new connection or contact the peer administrator.
Error Message
%CRYPTO-4-RECVD_PKT_MAC_ERR: decrypt: mac verify failed for connection id=[dec]Explanation The MAC verify processing failed. This may be caused by the use of the wrong key by either party during the MAC calculations. This activity could be considered a "hostile event" such as an attempt by an unauthorized user to break into a network.
Recommended Action Contact the peer administrator.
Error Message
%CRYPTO-4-RECVD_PKT_MSG_LEN_ERR: decapsulate: packet has bad [chars] length destadr=[int], prot=[dec], len([dec]Explanation The received IP Security Protocol (IPSec) packet is malformed, possibly because of an encapsulation error. The peer is sending malformed packets. This activity could be considered a "hostile event" such as an attempt by an unauthorized user to break into a network.
Recommended Action Contact the peer administrator.
Error Message
%CRYPTO-4-RECVD_PKT_NOT_IPSEC: Rec'd packet not an IPSEC packet.(ip) dest_addr= [int], src_addr= [int], prot= [dec]Explanation The received packet matches the crypto map Access Control List (ACL), but is not encapsulated by the IP Security Protocol (IPSec). The IPSec peer is sending unencapsulated packets. There may simply be a policy setup error on the peer. This activity could be considered a "hostile event" such as an attempt by an unauthorized user to break into a network.
Recommended Action Contact the peer administrator to compare policy settings.
Error Message
%CRYPTO-4-RECVD_PKT_NO_CPI: pcp: wrong CPI, [hex], in packet from [int]Explanation The received IPPCP packet had an improper Common Part Indicator (CPI). This may be caused by the use of an old IPPCP security association.
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
%CRYPTO-3-REQCERT: Certificate enrollment message send out ...Explanation The certificate enrollment message is being sent.
Recommended Action No action is required.
Error Message
%CRYPTO-3-SOCKETSELECT: Failed to select the socketExplanation The failure is caused by an unsuccessful socket selection.
Recommended Action Check the TCP/socket debugging message. If the problem persists, 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 call switching module (CSM) error messages.
Error Message
%CSM-5-CAS_IPC_QUEUED: CAS mbox at [hex] in use - message has been [chars]Explanation A channel associated signaling (CAS) interprocess communication (IPC) message has been queued because the mailbox is in use.
Recommended Action This is a notification message. If the modems are not functional or this message appears frequently, 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
%CSM-1-CAS_MSG_DEPLETED: An error was encountered in enqueuing a CAS message - [chars]Explanation The modem may no longer be operational because the amount of memory available in the router may not be sufficient.
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
%CSM-1-CSM_BAD_EVENT: [chars]: [dec]/[dec] received invalid event [dec]Explanation An invalid operation has been detected by the router.
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
%CSM-1-CSM_MODEM_BAD: Modem [dec]/[dec] has been marked as bad by the router softwareExplanation The modem is no longer operational because of a run-time error.
Recommended Action The modem may become operational following a reset of the router. If not, 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
%CSM-1-HWIDB: [chars]: hwidb is NULLExplanation An invalid operation has been detected by the router.
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
%CSM-1-HWREV: The T1 or E1 network module is incompatible with the digital modems: [chars]Explanation The T1 or E1 network module cannot be used with digital modems.
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
%CSM-1-INITPORT: [chars] at slot [dec], port [dec]Explanation An initialization error occurred on the specified port. The error message specifies more details.
Recommended Action Try resetting the port or power-cycling the system. If the message recurs, 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
%CSM-1-INITSYS: [chars]Explanation The modem signalling module failed initialization.
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
%CSM-5-MBRI: [chars] at slot [dec], unit [dec], with index [dec]Explanation An ISDN Multiport Basic Rate Interface (MBRI) has changed states. Details of the new state are shown in the error message.
Recommended Action No action is required.
Error Message
%CSM-5-PRI: [chars] at slot [dec], unit [dec], channel [dec] with index [dec]Explanation An ISDN primary Rate Interface (PRI) has changed states. Details of the new state are shown in the error message.
Recommended Action No action is required.
Error Message
%CSM-1-QUEUE_ERROR: An error was encountered in enqueuing a [chars] ([dec]) for slot/port [dec]/[dec]Explanation The modem may no longer be operational. The amount of memory available in the router may not be sufficient.
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
%CSM-1-UNEXPECTEDEVENT: An Unexpected event received by tone process - [dec] [dec]Explanation An invalid operation has been detected by the router.
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 call switching mode (CSM) voice subsystem error messages.
Error Message
%CSM_VOICE-3-ADDINTRFFAIL: The Voice Telephony Service Provider has rejected our request to add this voice interface ([dec]/[dec]:[dec])Explanation The voice software was unable to report a new signalling interface to the Voice Telephony Service Provider.
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
%CSM_VOICE-3-MALLOC: No memory is available to build any internal data structure for the voice softwareExplanation The voice software was unable allocate memory to build any internal data structures. The system may be out of memory.
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
%CSM_VOICE-3-NOMEM: No memory is available to build the voice interface ([dec]:[dec])Explanation The voice software was unable allocate memory to build a voice interface data structure. The system may be out of memory.
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
%CSM_VOICE-3-NOSDB: No signaling data block is available to build the voice interface([dec]/[dec]:[dec])Explanation The voice software was unable to obtain a signalling data block from the Voice Telephony Service Provider. The system may be out of memory.
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
%CSM_VOICE-3-UNDEFDSX0: Undefined dsx0 interface for controller([dec]/[dec])Explanation The dsx0 interface for the specified controller is not defined, but the voice software has used it.
Recommended Action An internal software error has occurred. Contact your field service representative if this message is coincident with dropped calls.
Error Message
%CSM_VOICE-3-UNDEFVOICEINTRF: Invalid interface slot:controller:group([dec]/[dec]:[dec])Explanation The voice interface defined by slot:controller:group is not yet defined within the voice software, but attempts were made to use this interface.
Recommended Action An internal software error has occurred. Contact your field service representative if this message is coincident with dropped calls.
The following are channelized T3 (CT3) port adapter error messages.
Error Message
%CT3-3-BADMSG: Received unexpected mailbox message (id = [dec])Explanation An unexpected message has been received from the channelized T3 (CT3) firmware.
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
%CT3-1-CONFIGURE: Failed to configure [dec] interfaces in bay [dec], shutting down bayExplanation The channelized T3 (CT3) hardware has failed. Some components on the board failed to initialize.
Recommended Action Replace the CT3 port adapter. If the problem persists, 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
%CT3-2-CT3FWCRASHED: CT3 F/W crashed in bay [dec]: [hex] - VIP resetExplanation The channelized T3 (CT3) firmware does not update the software watchdog.
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
%CT3-2-CT3FWCRASHEDINFO: [hex] [hex] [hex] [hex]Explanation This error messages contains channelized T3 (CT3) firmware failure information.
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
%CT3-3-CT3NOACC: [chars] - Accumulator is not availableExplanation An invalid TX accumulator was detected.
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
%CT3-1-DISCOVER: Found [dec] interfaces in bay [dec], shutting down bayExplanation The channelized T3 (CT3) hardware has failed. Some components on the board failed to initialize.
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
%CT3-1-DWNLDFAIL: Microcode to slot [dec]Explanation The firmware download into the channelized T3 (CT3) port adapter failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CT3-3-ERROR: [chars]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.
Error Message
%CT3-1-INITFAIL: Slot [dec] firmware init ([chars])Explanation The channelized T3 (CT3) firmware initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CT3-1-INITFAILP: [chars] init failed at [chars]Explanation The channelized T3 (CT3) initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%CT3-3-LOVEFAIL: [chars]: failed to send [chars] love letterExplanation A love letter was not sent to the Route Switch Processor (RSP).
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
%CT3-3-MBOXRECV: Failed to receive reply [dec] from bay [dec] firmwareExplanation A message was not received from the channelized T3 (CT3) firmware.
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
%CT3-3-MBOXSEND: Failed to send msg [dec] to bay [dec] firmwareExplanation The specified message was not sent to the channelized T3 (CT3) firmware.
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
%CT3-3-MBOXSENDM: Failed to send msg [chars] to bay [dec] firmwareExplanation The specified message was not sent to the channelized T3 (CT3) firmware.
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
%CT3-3-MBOXSENDP: Failed to send msg [dec] to [chars] driver firmwareExplanation A port-related message was not sent to the channelized T3 (CT3) firmware.
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
%CT3-3-NOTMXT: Slot [dec] device ID seen as [hex], expected [hex] (Mueslix)Explanation The High Level Data Link Control (HDLC) controller was not detected on the channelized T3 (CT3).
Recommended Action Replace the CT3 port adapter. If the problem persists, 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
%CT3-3-NOTPLX: Slot [dec] device ID seen as [hex], expected [hex] (PLX9060)Explanation The PLX 9060 was not detected on the channelized T3 (CT3).
Recommended Action Replace the CT3 port adapter. If the problem persists, 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
%CT3-1-NOTREADY: Slot [dec] for microcode downloadExplanation An error was detected on the communication path between the Versatile Interface Processor (VIP) and the channelized T3 (CT3) hardware.
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
%CT3-2-NOVC: [chars]: packet received for unknown VC [dec]Explanation The virtual channel encapsulation is 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
%CT3-3-OWNERR: [chars] packet buffer, pak=0x[hex]Explanation A software or hardware error has occurred. The channelized T3 (CT3) driver detected that the transmit ring is in an inconsistent and unrecoverable 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
%CT3-1-RESTARTFAIL: [chars] could not be reset by [chars]Explanation The restart failed to reset the interface.
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
%CT3-1-STARTFAIL: [chars] could not be enabled by [chars]Explanation The restart failed to enable the interface.
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
%CT3-1-STOPFAIL: [chars] could not be disabled by [chars]Explanation The shutdown failed to disable the interface.
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
%CT3-1-UNSUPPORTED: [chars]Explanation A channelized T3 (CT3) port adapter with a revision earlier than Revision 3 was detected. This port adapter predates the router platform it has been installed in, and is not a supported combination.
Recommended Action Upgrade to a CT3 port adapter that is Revision 3 or higher. If the problem persists, 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 Cisco Transaction Connection (CTRC) error messages.
Error Message
%CTRC-3-APPCERROR: [chars]Explanation An Advanced Program-to-Program Communication (APPC) error occurred. Cisco Transaction Connection (CTRC) uses APPC Application Programming Interface (API) calls to SNA Switch Services (SNASw) to communicate with the remote database server.
Recommended Action This error usually indicates a problem in the Systems Network Architecture (SNA) network. Try the ctrc ping command to test connectivity to the remote database server. If the ctrc ping command fails, check the status of the SNA link to the remote database server with the show snasw link command. If the link is active, try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. If the message recurs, 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. If possible, also provide the output of the debug ctrc appc command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared.
Error Message
%CTRC-3-APPCVERB: Unexpected APPC error: opcode [hex], primary code [hex], secondary code %08lxExplanation An unexpected Advanced Program-to-Program Communication (APPC) error occurred. The Cisco Transaction Connection (CTRC) uses APPC Application Programming Interface (API) calls to SNA Switch Services (SNASw) to communicate with the remote database server. The opcode identifies the APPC API call that received the error. Primary and secondary return codes are returned by the APPC API.
Recommended Action This error usually indicates a problem in the Systems Network Architecture (SNA) network. Try the ctrc ping command to test connectivity to the remote database server. If the ctrc ping command fails, check the status of the SNA link to the remote database server with the show snasw link command. If the link is active, try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. If the message recurs, 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. If possible, also provide the output of the debug ctrc appc command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared.
Error Message
%CTRC-4-APPCWARN: [chars]Explanation An Advanced Program-to-Program Communication (APPC) error has occurred. The Cisco Transaction Connection (CTRC) uses APPC Application Programming Interface (API) calls to SNA Switch Services (SNASw) to communicate 3ith the remote database server.
Recommended Action This error usually indicates a temporary problem in the Systems Network Architecture (SNA) network. Try the ctrc ping command to test connectivity to the remote database server. If the ctrc ping command fails, check the status of the SNA link to the remote database server with the show snasw link command. If the link is active, try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. If the message recurs, 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. If possible, also provide the output of the debug ctrc appc command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared.
Error Message
%CTRC-3-SNASWNOTSTARTED: SNASW is not started -- unable to connect to remote database.Explanation A client connected to a Cisco Transaction Connection (CTRC) server, but the CTRC was unable to connect out to the remote database because SNA Switch Services (SNASw) has not been started. The CTRC uses SNASW to connect to the remote database server. You must start SNASW before CTRC clients attempt to connect.
Recommended Action Start SNASW and retry the client connection. If the problem persists, 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
%CTRC-3-SNASWSTOPPED: SNASW was stopped -- existing connections have been closed.Explanation SNA Switch Services (SNASw) was stopped while Cisco Transaction Connection (CTRC) connections were open. Stopping SNASW caused all open Systems Network Architecture (SNA) network connections to the remote database server to be lost. As a result, all client connections were disconnected. You should not stop SNASW while there are open CTRC connections.
Recommended Action Restart SNASW. Disconnected clients must reconnect.
Posted: Fri Jun 16 11:45:58 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.