-
Cisco IOS System Error Messages, Volume 1 of 2
-
About Cisco IOS Software
-
System Error Messages Overview
-
AT through BERT
-
BGP through C6KPWR
-
C6MSFC through CHOPIN_MAINBOARD_ASYNC_PQII
-
CI through COT
-
CPAD through DBCONN
-
DBUS through DSCREDCLK
-
DSC_REDUNDANCY through ENT_API
-
ENVM through FR_FRAG
-
FR_LMI through GSR_ENV
-
GSRIPC through IF
-
IFS through ISA
-
ISDN through LCCOREDUMP
-
LCFE through MBRI
-
MBUS through MODEM
-
MODEMCALLRECORD through NSP
-
Glossary of Acronyms
-
Table Of Contents
CHOPIN_MAINBOARD_ASYNC_PQII Messages
C6MSFC Messages
The following are C6MSFC (Draco) error messages.
Error Message%C6MSFC-4-BADFLASH : Unsupported flash type in the bootflash - [chars].
Explanation The Flash chip in the Flash SIMM is not supported by the platform.
Recommended Action Contact your Cisco technical support representative for assistance in updating your system.
Error Message%C6MSFC-3-CHASSIS : Unknown chassis model.
Explanation The data stored in the CPU ID PROM is bad or incomplete.
Recommended Action Contact your Cisco technical support representative for assistance in updating your system.
Error Message%C6MSFC-3-CONFIG : Recommended port adapter configuration exceeded
Explanation The number of port adapters configured is greater than the number supported for this system.
Recommended Action Verify that you are using the correct port adapters, check your system requirements, and correct the configuration.
Error Message%C6MSFC-4-COOKIE : Corrupt or missing MAC address cookie
using random base [enet]Explanation The MAC address could not be detected. It may have been corrupted or be missing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C6MSFC-3-IONOT0 : IO card discover in non-zero slot [dec]
Explanation An I/O card has been detected in the nonzero slot indicated in the error message.
Recommended Action Verify that the card is in the correct slot and that the configuration is correct. Try the operation again.
Error Message%C6MSFC-4-MACBLKSIZE : Unknown MAC address block size.
Explanation The data stored in the CPU ID PROM is bad or incomplete.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C6MSFC-3-NOCPUVER : Invalid CPU Revision [dec].
Explanation The CPU version could not be verified.
Recommended Action The system may need to be upgraded. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C6MSFC-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation The MAC address for the interface indicated in the message could not be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
C6SUP Messages
The following are C6SUP-specific error messages.
Error Message%C6SUP-3-NOVLANMAC : Can't allocate MAC address for VLAN interface [int]
Explanation The allocation of the MAC address has failed because the VLAN number is outside the range supported by the chassis.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
C7200 Messages
The following are error messages for the Cisco 7200 platform.
Error Message%C7200-2-BADDAT : PA interface data incorrect, [hex]
Explanation Incorrect port adapter (PA) interface data has been 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%C7200-2-BADIDB : PA interface idb incorrect, [hex]
Explanation The port adapter system control block (PASCB) data structure indicates a zero interface descriptor block (IDB).
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%C7200-2-BADINTERFACE : Out of range PCI Port Adaptor interface, [dec] on bay [dec]
Explanation The software specified an out-of-range port adapter 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%C7200-2-BADPA : PA interface pa incorrect, [hex]
Explanation An incorrect port adapter (PA) interface has been specified.
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%C7200-2-BADPA2 : PA null adapter, [hex]
Explanation A null port adapter (PA) interface has been specified.
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%C7200-2-BADPABAY : Out of range PCI Port Adaptor bay [dec]
Explanation The software specified an out-of-range port adapter bay.
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%C7200-2-BADPASCB : PA interface pascb incorrect, [hex]
Explanation The port adapter system control block (PASCB) data structure was incorrectly set in the command data structure.
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%C7200-2-BADPINST : PA interface port_inst incorrect, [hex]
Explanation An attempt to access port instance internal data 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%C7200-2-BADVCONT : PA interface vcont incorrect, [hex]
Explanation An incorrect virtual circuit (VC) interface has been specified.
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%C7200-3-BRINGUPFAIL : port adapter in bay [[dec]] failed to reset.
Explanation An attempt to reset and initialize the port adapter has timed out.
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%C7200-3-CONFIG : Recommended port adapter configuration exceeded
Explanation The total bandwidth of fast and medium bandwidth port adapters has exceeded the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed fast and medium bandwidth port adapters for the system.
Error Message%C7200-3-DEACTIVATED : port adapter in bay [[dec]] powered off
Explanation The port adapter is being powered off.
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%C7200-2-ILLEGALPA : Illegal Port Adaptor type [dec] in bay [dec] of [chars].
Explanation The port adapter is not supported by the controller into which it is plugged.
Recommended Action Remove the port adapter and return the controller to its original configuration.
Error Message%C7200-2-INCORRECTBRIDGEREG : Bad default register([hex]) setting([hex]) in PA bridge
Explanation The software is unable to configure certain settings for the port adapter protocol control information (PCI) bridge in the specified bay.
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%C7200-3-NOTSUPPORTED : PA in slot[dec] ([chars]) is not supported on this [chars]
Explanation This port adapter is not supported on this chassis or CPU 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%C7200-2-PABRIDGE : Failed to config bridge for PA [dec]
Explanation The system side protocol control information (PCI) bridge for this port adapter (PA) has failed initialization. The PA therefore will not be operational.
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%C7200-3-PACREATE : Unable to create driver for Port Adaptor type [dec] in bay [dec]
Explanation This message indicates a possible memory shortage or port adapter hardware 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%C7200-2-PARECUR : Recursive loop while getting the daughtercard info for PA type [dec]
Explanation While retrieving the daughter card information for the chassismib, the platform Simple Network Management Protocol (SNMP) code has gone into an infinite loop.
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%C7200-4-PCIVALID : PCI activation failed, bay [dec], 0x[hex]
Explanation The system has received an invalid protocol control information (PCI) signal from the specified port adapter. This error was probably caused by a hardware 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%C7200-2-QOVERFLOW : PA queue overflow, cmd [hex]
Explanation The port adapter (PA) queue has overflowed and the programming has been lost.
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%C7200-3-REVNOTSUPPORTED : PA in slot[dec] ([chars]) requires base h/w revision of ([dec].[dec]) for this [chars]
Explanation A newer hardware revision of the port adapter is required for functional operation on this chassis.
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%C7200-0-RUPTCONFLICT : Conflict detected when trying to install [chars] interrupt handler, bay [dec].
Explanation An attempt was made to register an interrupt handler either for a nonexistent port adapter or for the wrong interrupt priority level.
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%C7200-2-UNDEFPA : Undefined Port Adaptor type [dec] in bay [dec]
Explanation The software does not have a driver for the specified port adapter type located in the specified bay.
Recommended Action Ensure that the image you are running supports this card. Check that the card is properly seated. 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%C7200-2-UNDEFPABRIDGE : Unsupported Port Adaptor Bridge [hex] in bay [dec]
Explanation The software does not have a driver for that port adapter protocol control information (PCI) bridge located in the specified bay.
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.
C7200_TDM Messages
The following are Cisco 7200 midplane TDM bus error messages.
Error Message%C7200_TDM-3-TDM_CLOSE : MT90820 Midplane Close connection failed - STo[dec], CHo[dec]
Explanation An attempt to disable the midplane TDM connection has failed.
Recommended Action This message is informational. No action is required.
Error Message%C7200_TDM-3-TDM_INV_CONN_REQ : Upper Layer made invalid TDM request - STo[dec], CHo[dec]
Explanation An invalid request to use the TDM midplane has been made.
Recommended Action This message is informational. No action is required.
Error Message%C7200_TDM-3-TDM_INV_DISC_REQ : Upper Layer made invalid TDM request - STo[dec], CHo[dec]
Explanation An invalid request to use the TDM midplane has been made.
Recommended Action No action is required.
Error Message%C7200_TDM-3-TDM_OPEN : MT90820 Midplane Open connection failed - STi[dec], CHi[dec], STo[dec], CHo[dec]
Explanation An attempt to open a midplane TDM connection has failed.
Recommended Action This message is informational. No action is required.
CAIM Messages
The following are Compression Advanced Interface Module (CAIM) error messages.
Error Message%CAIM-1-ELMERREV : AIM in slot [int] not supported by this HW revision.
Explanation The revision level of the C2600 Elmer PLD does not support Compression AIM.
Recommended Action The C2600 Elmer PLD needs to be reprogrammed to a later revision. Refer to Cisco.com release notes for the Cisco C2600 and Compression AIM for an explanation of how to reprogram the PLD.
Error Message%CAIM-1-HIFNERR : Caim [int]: Hifn 9711 Errors reported: 9711 Status [hex] DMA status [hex]
Explanation The specified Compression AIM reported a Hifn9711 error.
Recommended Action This is an indication of a serious malfunction of the Compression AIM or of the system bus. The Compression AIM should be replaced.
Error Message%CAIM-1-HIFNREV : Compression AIM type in slot [int] is not supported by this platform.
Explanation The Compression AIM that is installed is not supported by this platform.
Recommended Action Power off and replace the Compression AIM card.
Error Message%CAIM-1-INITFAIL : CAIM [dec]: Initialization failed at [chars]
Explanation The Compression AIM device would not reset properly. This behavior indicates a Compression AIM hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CAIM-1-INVELMT : Invalid CAIM element: [dec]
Explanation The Compression AIM element number specified in the command is not valid.
Recommended Action Compression AIM element numbers range from 0 to one less than the number of Compression AIMs possible in your system. Verify the number of Compression AIMs present in your system.
Error Message%CAIM-1-NODEV : AIM slot [dec]: Could not locate Compression AIM; found PCI vendor id [hex] instead
Explanation The AIM ID PROM indicates that a Compression AIM is present but the PCI vendor or device ID was not the one that was expected for a Compression AIM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CAIM-1-NOMEMORY : CAIM [dec]: Memory allocation failure; could not allocate [chars]
Explanation An attempt to allocate memory for the specified Compression AIM has failed. More RAM may be required to execute this image.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CAIM-1-NOSUCH : No such CAIM element: [dec]
Explanation The Compression AIM element number specified is not present in the system.
Recommended Action Compression AIM element numbers range from 0 to one less than the number of Compression AIMs present in your system. Verify the number and presence of Compression AIMs in your system.
Error Message%CAIM-1-PCIABT : Caim [int]: PCI Abort reported: status [hex]
Explanation The specified Compression AIM has reported a bus error (PCI Abort).
Recommended Action This is an indication of a serious malfunction of the Compression AIM or of the system bus. The Compression AIM should be replaced. A second possible explanation is that there is a mismatch in the configured compression algorithm on either side of a serial link. Such a mismatch can also give rise to PCI Abort problems. The recommended action in such cases is to configure matching compression algorithms on either side of the link and then to reboot the router which experienced the PCI Abort.
Error Message%CAIM-6-SHUTDOWN : [chars] shutting down
Explanation The specified Compression AIM is shutting down. It may have been physically removed. This message also occurs when the clear aim command is used.
Recommended Action This is an informational message only and occurs in normal operation. No action is required.
Error Message%CAIM-6-STARTUP : [chars] starting up
Explanation The specified Compression AIM has initialized successfully.
Recommended Action This is an informational message only and occurs in normal operation. No action is required.
Error Message%CAIM-1-UNEXPINT : Unexpected AIM Interrupt
Explanation The system has received an AIM interrupt from an unknown AIM device. There is no recognizable AIM installed in the system, yet the AIM interrupt was received.
Recommended Action If there is a Compression AIM unit installed in the Cisco C2600, then it is defective and must be replaced. If there is some other AIM installed in the Cisco C2600, it must be removed. If there is no AIM installed, then the Cisco C2600 unit is defective and must be replaced.
CALL_CONTROL Messages
The following are network call control error messages.
Error Message%CALL_CONTROL-6-APP_NOT_EXIST : The requested application does not exist any more. The event for the callid [dec] is being discarded.\n
Explanation The event points to a session application that does not exist any more. The event is being discarded.
Recommended Action No action is required.
Error Message%CALL_CONTROL-6-APP_NOT_FOUND : Application [chars] in dial-peer [dec] not found.
Handing callid [dec] to default app.\nExplanation The inbound dial peer points to a session application that is not registered. The call is being handed to the default application.
Recommended Action Reconfigure the dial peer and assign it a valid application name.
Error Message%CALL_CONTROL-6-CALL_LOOP : The incoming call has a global identfier already present in the list of currently handled calls. It is being refused.\n
Explanation The incoming call has a global identifier that is already present in the list of currently handled calls. A global identifier can be used by only one call at a time.
Recommended Action Check your configuration. The call may be misdirected.
Error Message%CALL_CONTROL-6-MAX_CONNECTIONS : Maximum number of connections reached for dial-peer [dec]\n
Explanation The dial peer in question has reached its maximum number of configured connections. No more calls will be taken on this dial peer.
Recommended Action No action is required; however, to increase the number of connections allowed to this dial peer, you can adjust the maximum connections configuration setting while in dial-peer configuration mode.
Error Message%CALL_CONTROL-3-NORAWMSG : no free raw msg structure available from [chars] for signaling message
Explanation There were no raw message structures remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Verify that the voice port for which the event was reported is still operational. If the port is not operational, clear the voice port.
Error Message%CALL_CONTROL-6-NUMBERING_TYPE_NO_MATCH : The called number numbering type did not matchThe event for the callid [dec] is being discarded.\n
Explanation The event points to a session application that no longer exists. The event is being discarded.
Recommended Action This message is informational. No action is required.
CALL_MGMT Messages
The following are call management subsystem error messages.
Error Message%CALL_MGMT-4-CALL_DISC : [chars]
Explanation The specific message text is supplied by the call management software. This indicates that a call record is missing from the active call list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CALL_MGMT-1-CALL_LIST : [chars]
Explanation The specific message text is supplied by the call management software. This indicates that internal data was corrupted as a result of a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CALL_MGMT-1-CPM_Q_POOL : [chars]
Explanation The specific message text is supplied by the call management software; it indicates a condition of memory exhaustion.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CALL_MGMT-1-INITSYS : [chars]
Explanation The specific message text is supplied by the call management software. This indicates an initialization failure. When this occurs, the call management subsystem is not operational.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CALLPROG Messages
The following are error messages for the call progress notification subsystem.
Error Message%CALLPROG-3-API_INIT : api front init failed for [chars]
Explanation An attempt to initialize call progress notification support structures for APIs has failed.
Recommended Action The system is running low on available memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CALLPROG-3-API_USE : no free front-end q elt's; dropping api call info (func=[dec])
Explanation The system was unable to get a free element from the front end queue.
Recommended Action The platform requires additional free elements in order to function properly. Stop using call progress notification applications. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CALLRECORD Messages
The following are Modem Call Record error messages.
Error Message%CALLRECORD-3-MCOM_TERSE_CALL_FAILED_REC : [chars]
Explanation An attempt to write a terse Mcom call record has failed.
Recommended Action No action is required.
Error Message%CALLRECORD-3-MCOM_TERSE_CALL_REC : [chars]
Explanation A terse Mcom call record was written successfully.
Recommended Action No action is required.
Error Message%CALLRECORD-6-MICA_TERSE_CALL_FAILED_REC : [chars]
Explanation An attempt to write a terse MICA call record has failed.
Recommended Action No action is required.
Error Message%CALLRECORD-6-MICA_TERSE_CALL_REC : [chars]
Explanation A terse MICA call record was written.
Recommended Action No action is required.
Error Message%CALLRECORD-3-MODEM_CALL_REC_ERROR : [chars]
Explanation The generated record has exceeded the SYSLOG capacity.
Recommended Action No action is required.
CALLTRKR Messages
The following are Call Tracker subsystem error messages.
Error Message%CALLTRKR-3-CALL_REC_ERROR : [chars]
Explanation The generated record has exceeded the SYSLOG capacity.
Recommended Action No action is required.
Error Message%CALLTRKR-6-CALL_RECORD : [chars]
Explanation A terse Call Tracker call record was written.
Recommended Action No action is required.
Error Message%CALLTRKR-6-MODEM_CALL_REC : [chars]
Explanation A modem verbose Call Tracker call record has occurred.
Recommended Action No action is required.
Error Message%CALLTRKR-6-MODEM_INFO_CALL_REC : [chars]
Explanation A modem information verbose Call Tracker call record has occurred.
Recommended Action No action is required.
Error Message%CALLTRKR-6-MODEM_LINE_CALL_REC : [chars]
Explanation A modem line verbose Call Tracker call record has occurred.
Recommended Action No action is required.
Error Message%CALLTRKR-6-MODEM_NEG_CALL_REC : [chars]
Explanation A modem negotiation verbose Call Tracker call record has occurred.
Recommended Action No action is required.
Error Message%CALLTRKR-3-NO_MEM : Memory allocation failed for CT [chars] ([dec] bytes)
Explanation Call Tracker could not allocate a new record because no free memory was available.
Recommended Action Disable Call Tracker using the no calltracker enable command. Run the show memory command to find out where memory has been allocated. Adjust system activity and resources as necessary.
Error Message%CALLTRKR-3-PRINT_BUFFER : calltrkr cli print buffer [chars]
Explanation The Call Tracker command-line interface internal print buffer has reached overflow capacity.
Recommended Action Stop using Call Tracker show commands. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CALLTRKR-3-PROC : can't spawn [chars]
Explanation The Call Tracker process could not be started.
Recommended Action Disable Call Tracker using the no calltracker enable command. Enable it and try the process again.
Error Message%CALLTRKR-3-TBL_INIT : Init of CT's [chars] table failed; CT unusable
Explanation The Call Tracker record table could not be initialized.
Recommended Action Disable Call Tracker using the no calltracker enable command. Enable it and try the operation again.
CARRIER Messages
The following are DFC carrier error messages.
Error Message%CARRIER-2-CT3_8PRI_MIX : Cannot mix 8PRI and CT3 DFC in chassis, do not power up invalid card in slot [dec]\n
Explanation The user has put 8PRI and CT3 DFCs in the same chassis.
Recommended Action These card types cannot be mixed. Remove the extra 8PRI or CT3 DFC.
Error Message%CARRIER-3-DFC_INIT_ALREADY : DFC is already initialized - DFC [dec]
Explanation The DFC is already initialized; there is no need to initialize it again.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-DFC_INIT_FAIL : DFC initialization is failed - DFC [dec]
Explanation DFC initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-DFC_POWER_INT : DFC Power Changed - DFC [dec]
Explanation Power is fluctuating on the DFC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-INVALID_DFC : Invalid DFC - DFC [dec] type [dec]
Explanation The DFC has an invalid board ID or board type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-NO_DFC : DFC is not present - DFC [dec]
Explanation The DFC is not present in the carrier card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-PLATFORM_DFC : DFC Carrier Platform Init Failed - Slot [dec]
Explanation Initialization of the DFC carrier platform has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-POWER_DFC : DFC Power-On Failed - DFC [dec]
Explanation An attempt to power on the DFC has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-RESET_DFC : DFC Reset Failed - DFC [dec]
Explanation The DFC reset failed during the online removal process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-2-T1_E1_MIX : Cannot mix T1 and E1 8PRI DFC cards in chassis, do not power up invalid card in slot [dec]\n
Explanation T1 and E1 8PRI DFCs are present in the same chassis.
Recommended Action These card types cannot be mixed in the same system. Remove the extra T1 or E1 8PRI DFC.
Error Message%CARRIER-2-THREE_NP108_NOT_PRESENT : 3 NP108s were not found on Tetryl card, [dec] detected.
Explanation Tetryl requires 3 NP108 cards to be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-2-TOOMANY_8PRI : Too many 8PRI DFC cards, do not power up invalid card in slot [dec]\n
Explanation Too many 8PRI DFCs are installed in the chassis.
Recommended Action Remove the extra 8PRI DFC.
Error Message%CARRIER-2-TOOMANY_CT3 : Too many CT3 DFC cards, do not power up invalid card in slot [dec]\n
Explanation Too many CT3 DFCs are installed in the chassis.
Recommended Action Remove the extra CT3 DFC or the 8PRI DFC that is causing the problem.
CASA Messages
The following are Cisco Appliance and Services Architecture (CASA) error messages.
Error Message%CASA-4-BADMSG : Message parsing error: [chars]
Explanation An incoming packet could not be parsed.
Recommended Action If this message is occurring repeatedly, enable debugging by entering the debug ip casa error command and record the output. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CASA-3-BADVER : Incoming packet is CASA v[dec], this router is v[dec]
Explanation A packet was received for the wrong version of CASA.
Recommended Action Verify that all CASA devices are running the same version of the protocol.
Error Message%CASA-2-NOMEM : Out of memory: [chars]\n
Explanation CASA has failed to allocate memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CASA-4-PORTCHANGE : Wildcard overlap: [chars]
Explanation A CASA wildcard, received on one port, has been overwritten by a service manager sending to another port. This message may appear once if your service is migrating to a new forwarding-agent port; if it recurs, it could indicate a configuration problem.
Recommended Action Verify the configurations. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CASA-4-SECURITY_FAIL : [chars] security information in CASA packet.
Explanation A security check has failed.
Recommended Action Verify that all CASA systems are configured with the same password.
Error Message%CASA-4-UNEXPECTED : Unexpected error: [chars]
Explanation An unexpected error occurred during a CASA operation.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CASA-4-WARNING : Unexpected condition: [chars]
Explanation An unexpected condition was detected during a CASA operation.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CBUS Messages
The following are ciscoBus controller error messages.
Error Message%CBUS-3-ADDRFILTR : Interface [chars], address filter [chars] command failed, code [hex]
Explanation The specified address filter command, which was sent to the specified interface, has failed with the displayed error code.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS-3-AIPINVPLIM : Interface [chars], Invalid PLIM detected. Interface downed
Explanation A 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-BADRXEOFVEC : [chars] ustatus: [chars] ([hex]), [hex] [hex] [hex] [hex]
Explanation This message provides debugging information when an IP panic occurs.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-BADTXEOFVEC : [chars] ustatus: [chars] ([hex]), [hex] [hex] [hex] [hex]
Explanation This message provides debugging information when an IP panic occurs.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-BADTXSTATE : [chars] ustatus: [chars] ([hex]), [hex] [hex] [hex] [hex]
Explanation This message provides debugging information when an IP panic occurs.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-BADVC : [chars] [dec]/[dec] got bad VC packet
[hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation An interface has received a packet with bad VC encapsulation. This indicates either a software or hardware 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-BUFFER : Controller [dec], Error ([hex]), Buffersize = [dec], Bufferpool = [dec], number [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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CATMCFG : Interface [chars], Cannot config interface, CBus ATM MEM [hex], status [dec]
Explanation A 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CATMREJCMD : [chars] [chars] command failed (error code [hex])
Explanation The ciscoBus ATM microcode rejected a command sent by the route processor (RP). The error code is the status value returned by the command.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CATMRSET : Interface [chars], Error ([hex]) [chars] - aip_reset()
Explanation A 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CATMRSETU : Unit [dec], Error ([hex]) [chars] - cbus_atm_reset()
Explanation A 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-5-CBADVCSETUP : Interface [chars], setup vc failed with vci exceeding (vc-per-vp - 3) on the last vpi.
Explanation The TI1570 chip reserves three Rx DMA channels for OAM cells. As a result, the last three VCIs of the last VPI block cannot be used for regular traffic.
Recommended Action Avoid trying different VCI and VPI combinations.
Error Message%CBUS-3-CBUSBCE : Failed to select a BCE, response [hex] - cbus_bce_update_ifa()
Explanation 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. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CBUSBCEPERM : Failed to select a BCE, response [hex] - cbus_bce_permissions_update()
Explanation 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. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CCBCMDFAIL0 : Controller [dec], cmd ([dec]) failed ([hex])
Explanation A command that was sent from the system to an interface processor has failed to complete successfully.
Recommended Action The system recovered by generating and sending an error code to the requester. No action is required.
Error Message%CBUS-3-CCBCMDFAIL1 : Controller [dec], cmd ([dec] [hex]) failed ([hex])
Explanation A command that was sent from the system to an interface processor has failed to complete successfully.
Recommended Action The system recovered by generating and sending an error code to the requester. No action is required.
Error Message%CBUS-3-CE3DSX3ERR : ([chars])Illegal E3 value - unit is [dec]
Explanation The internal data structure is corrupted. The corruption has caused the "love letter" (operating status or configuration message) to be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CFGCMDDROPPED : Config queue is full, command was dropped, slot [dec]
Explanation The sending of a configuration command was retried. The receiving queues were still full after retries; therefore the command 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CMDTIMEOUT : Cmd timed out, CCB 0x[hex], slot [dec], cmd code [dec]
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. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CORRUPT : Controller [dec], wrote [hex], read [hex], loc [hex] - dci_memtest()
Explanation A hardware component has failed an internal diagnostic test.
Recommended Action Replace the malfunctioning device.
Error Message%CBUS-3-CT3STAT : Out of buffers--losing status information for CT3 on VIP card
Explanation An internal software resource has been exhausted.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CTRACHECK : Interface [chars], Adapter Check Error ([hex] [hex] [hex] [hex])
Explanation The Token Ring monitor firmware has detected a fatal error on the interface card.
Recommended Action Issue a clear interface command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS-3-CTRBADLOVE1 : Interface [chars], SRB_COMPLETE lovenote received with unknown command ([hex])
Explanation The system has received a message from the token-ring interface but does not recognize the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CTRBADLOVE1_DUMP : Dump of MEMB follows
-SRB_ADDR: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation The system is printing codes related to a previous "love letter" (operating status or configuration message) error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-4-CTRBADLOVE2 : Interface [chars], Unexpected SRB_COMPLETE lovenote, command=[hex], result=[hex]
Explanation The system has received an unsolicited message from the token-ring interface. The system ignored the message and continued normal processing.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS-3-CTRCMDFAILED : Interface [chars], CTR Command [chars] Failed, [chars] ([hex])
Explanation A command that was sent from the system to the token-ring interface has failed to complete successfully.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CTRCMDFAILED2 : Interface [chars], CTR Command [chars] Failed, Code [hex]
Explanation A command that was sent from the system to the token-ring interface has failed to complete successfully.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-CTRINIT : Interface [chars], CTR Initialization Failed - [chars]
Explanation The token-ring interface has failed one of its internal self-tests.
Recommended Action Issue a clear interface command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS-3-CTRLRCMDFAIL0 : Controller [dec], cmd ([dec]) failed ([hex]) count ([dec])
Explanation A command that was sent from the system to an interface processor has failed to complete successfully.
Recommended Action The system recovered by generating and sending an error code to the requester.
Error Message%CBUS-3-CTRLRCMDFAIL1 : Controller [dec], cmd ([dec] [hex]) failed ([hex]) count ([dec])
Explanation A command that was sent from the system to an interface processor has failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.
Error Message%CBUS-3-CTRRAMTEST : Interface [chars], RAM Addressing Test Failed - [chars]
Explanation The token-ring interface has failed its memory diagnostic tests.
Recommended Action Issue a clear interface command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS-3-CTRRSET : Interface [chars] failed to initialize
Explanation The token-ring interface failed to insert into the Token Ring. The interface is placed into a reset state and will not automatically try to reinsert itself.
Recommended Action Issue a clear interface command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS-3-CTRUCHECK : Interface [chars], Microcode Check Error
Explanation The token-ring interface microcode has detected an unrecoverable error.
Recommended Action Issue a clear interface command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS-3-DAUGHTER : Unit [dec], daughter controller [dec] failed [chars] test - interface disabled
Explanation A hardware component has failed an internal diagnostic test. Test output and descriptions are as follows:
•
Unit [dec] (ranges 0-14)—Indicates the Multibus jumper setting for the ciscoBus controller, or a slot number in the Cisco 7000.
•
•
If the failed test was memd write, writes to the memory device through the daughter card were not verified successfully with reads through the ciscoBus controller.
The daughter card under test responds successfully to some commands (otherwise the software would have received a DAUGHTER_NO_RSP message), but failed its memory device tests. The daughter card must be able to write to some memory device addresses; otherwise, it cannot respond to any commands.
Recommended Action First ensure that the daughter controller card is properly seated in its Multibus and ciscoBus connectors. Next, swap daughter cards and check whether the error follows the daughter card or the slot. If the message recurs, call your technical support representative for assistance.
Error Message%CBUS-3-DAUGHTER_NO_RSP : Unit [dec], daughter [dec], not responding ([hex]) - disabled
Explanation A hardware component failed an internal diagnostic test. Test output and descriptions of ranges are as follows:
•
•
The hardware of the daughter card was recognized across the ciscoBus backplane, but the daughter card did not respond to the first command that was issued to it.
This condition is a result of one of the following: the daughter card did not reset, or the microcode on the card is in a hung state, or the card cannot fully communicate across the ciscoBus backplane (cannot read or write shared MEMD or does not get the MALU_ATTENTION signal across the ciscoBus).
Recommended Action First, ensure that the daughter card is properly seated in its Multibus and ciscoBus connectors. If the message recurs, call your technical support representative.
Error Message%CBUS-3-FCICMDFAIL0 : Controller [dec], cmd ([dec]) failed ([hex]) count ([dec])
Explanation A command that was sent from the system to an interface processor has failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester. No action is required.
Error Message%CBUS-3-FCICMDFAIL1 : Controller [dec], cmd ([dec] [hex]) failed ([hex]) count ([dec])
Explanation A command that was sent from the system to an interface processor has failed to complete successfully.
Recommended Action The system recovered by generating and sending an error code to the requester. No action is required.
Error Message%CBUS-5-FDDICMD : '[chars]' is not supported on [chars]
Explanation The issued command is not supported on this FDDI interface.
Recommended Action No action is required.
Error Message%CBUS-3-FDDIRSET : Interface [chars], Error ([hex]) [chars] - fddi_reset()
Explanation The specified hardware device did not respond appropriately to a request.
Recommended Action Ensure that the specified hardware device is functioning and is configured correctly.
Error Message%CBUS-3-FDDIRSETU : Unit [dec], Error ([hex]) [chars] - fddi_reset()
Explanation The specified hardware device did not respond appropriately to a request.
Recommended Action Ensure that the specified hardware device is functioning and is configured correctly.
Error Message%CBUS-3-FSIPRSET : Interface [chars], Error ([hex]) [chars] - fsip_reset()
Explanation An FSIP did not respond to a reset request from the RP.
Recommended Action Check the FSIP electrical connections, cable, and ciscoBus connections. An FSIP microcode reload will be required. If the check of electrical connections reveals no problems and this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS-3-HSSIRSET : Interface [chars], Error ([hex]) [chars] - hssi_reset()
Explanation A hardware component did not respond to a reset command.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-INITERR : Interface [dec], Error ([hex]), idb [hex] [dec] [chars] - cbus_init()
Explanation The switch processor or ciscoBus controller has signalled an error while processing a packet or selecting an interface. This message indicates a software 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-INTR : Interface [dec], idb [hex] [dec] [chars] - cbus_interrupt()
Explanation The switch processor or ciscoBus controller has returned an invalid value.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-4-NOCOOKIE : [chars]-[dec] controller missing configuration data - disabled
Explanation The controller type was derived from a hardware probe. The controller number indicates the ciscoBus relative slot number. This message indicates a hardware error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-OUTHUNG : [chars]: tx[char] output hung ([hex] - [chars]), [chars]
Explanation A transmission attempt on an interface has failed. The interface might not be attached to a cable or there might be a software problem.
Recommended Action Check that the interfaces are all connected to the proper cables. If improper connection is not the problem, contact your Cisco technical support representative for assistance.
Error Message%CBUS-3-POLLFAIL : Interface [chars] failed to respond, debug info follows
Explanation A token-ring interface card failed to respond to periodic polling. This can indicate a software or hardware problem. See "CBUS-3-POLLFAILDAT" for the syntax of this message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-POLLFAILDAT : Int [dec]: [hex] [hex] [hex] [hex] [hex] [hex]
Explanation This is the debugging information for the "CBUS-3-POLLFAIL" error.
Recommended Action This is a debug message only. No action is required.
Error Message%CBUS-3-POTSTAT : Out of buffers--losing status information for POTENT on VIP card
Explanation An internal software resource has been exhausted.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-RESETNXI : Reset of removed interface [hex] ([chars])
Explanation An interface reset was attempted on an interface that had been removed from the router. This message appears if you use the shutdown command to bring down a previously removed interface.
Recommended Action No action is required.
Error Message%CBUS-4-RSETFAIL : Interface [chars] failed to reset properly in [chars], code [hex]
Explanation An interface reset command has failed. This may be a software or hardware 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-SERRSET : Interface [chars], Error ([hex]) [chars] - serial_reset()
Explanation A 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-TESTFAIL : Unit [dec], failed [chars] test - interface disabled
Explanation A hardware component has failed an internal diagnostic test.
Recommended Action Check the switch settings on the interface cards. Check for proper unit numbers. Reset the cards. Replace the malfunctioning device.
Error Message%CBUS-3-TXALLOC : Error ([hex]) tx_allocate - cbus_init()
Explanation A hardware device did not respond appropriately to a request.
Recommended Action Ensure that the device is functioning and is configured correctly.
Error Message%CBUS-3-TXSTARTPENDACTIVE : [chars] ustatus: [chars] ([hex]), [hex] [hex] [hex] [hex]
Explanation This message provides debugging information when an IP panics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS-3-UNKENC : Interface [chars], unknown encaps type [hex]
Explanation A packet was received from the CIP with an unknown encapsulation type. The packet will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CBUS-3-UNKNOWN : [chars] ustatus: [chars] ([hex]), [hex] [hex] [hex] [hex]
Explanation This message provides debugging information when an IP panics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CCH323 Messages
The following are Call Control for H323 error messages.
Error Message%CCH323-3-BAD_IP_ADDRESS : [chars]: illegal destination [chars]
Explanation The IP address that was passed from the Call Control API in the call setup request is invalid.
Recommended Action Check the dial-peer configuration for the dial peer that matches the called party number. Ensure that the session target field contains a valid IP address or DNS name.
Error Message%CCH323-3-CALL_SETUP_FAILED : [chars]: call setup failed
Explanation The call setup request has failed.
Recommended Action Verify that the remote destination identified by the IP address is reachable.
Error Message%CCH323-3-CANNOT_ALLOCATE_CALL_INFO : [chars]: cannot allocate call info data structure
Explanation Allocation of the CCH323 call information structure has failed. This condition may occur because the system memory pool is exhausted.
Recommended Action This call will be terminated because of a lack of resources.
Error Message%CCH323-3-CANNOT_ALLOCATE_CCB : [chars]: cannot allocate call control block
Explanation Allocation of the CCH323 call control block has failed. The allocation failure is possibly caused by an exhausted system memory pool.
Recommended Action This can be a catastrophic error. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CCH323-3-CANNOT_FIND_CCB : [chars]: cannot find CCH323 call control block based on callID [dec]
Explanation The system cannot find a CCH323 call control block based on the specified call ID. This is an indication that some events have occurred out of sequence.
Recommended Action No action is required.
Error Message%CCH323-3-CANNOT_INSERT_CCB : [chars]: cannot insert control block [hex] to tree
Explanation Insertion of the specified CCH323 call control block to the RBTree has failed. This condition can be related to a corrupted RBTree.
Recommended Action This can be a catastrophic error. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CCH323-3-CCAPI_CONNECT_ERROR : [chars]: cc_api_call_disconnected returns [dec]
Explanation An error is returned when CCH323 attempts to call cc_api_call_connected.
Recommended Action No action is required.
Error Message%CCH323-3-CCAPI_DISCONNECT_ERROR : [chars]: cc_api_call_disconnected returns [dec]
Explanation An error is returned when CCH323 attempts to call cc_api_call_disconnected.
Recommended Action No action is required.
Error Message%CCH323-3-CCH323_RSCMON_SETUP_FAILURE : [chars][dec]
Explanation A failure was encountered in setting up the monitoring of H.323 resources.
Recommended Action Power-cycle the system. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCH323-3-CCH323_UNKNOWN_EVENT : unknown event [hex]
Explanation An unknown CCH323 event has occurred.
Recommended Action No action is required.
Error Message%CCH323-2-E164_LENGTH_IS_NOT_SUPPORTED : [chars]: E164 address length [dec] is not supported
Explanation A packet was received with an E.164 address of a length that is not supported.
Recommended Action Report this event immediately to your Cisco technical support representative.
Error Message%CCH323-2-GTKP_UNREGSTR : Gatekeeper [chars] requested unregister from Gateway [chars]
Explanation The gatekeeper has requested that it be unregistered from Gateway.
Recommended Action Verify that this is an intended request. If it is not, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CCH323-2-GTWY_REGSTR_FAILED : Gateway [chars] failed to register with Gatekeeper [chars] even after [dec] retries
Explanation A gateway has failed to register with the gatekeeper.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CCH323-2-GTWY_REGSTR_FAILED_ALT_GK : Gateway [chars] failed attempt to register with Alternate Gatekeeper [chars]
Explanation A gateway has failed in an attempt to register with an alternate gatekeeper.
Recommended Action Report this error message immediately to your Cisco technical support representative. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CCH323-2-GTWY_UNREGSTR : Gateway [chars] unregistered from Gatekeeper [chars]
Explanation A gateway has unregistered from the gatekeeper.
Recommended Action Verify that this is an intended request. If it is not, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CCH323-3-OSS_INIT_FAILED : [chars]: OSS init failure: errno = [dec]
Explanation OSS ASN1 initialization has failed.
Recommended Action This can be a catastrophic occurrence. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CCH323-6-REGSTR : Gateway [chars] registered with Gatekeeper [chars]
Explanation A gateway has registered with the gatekeeper.
Recommended Action No action is required.
Error Message%CCH323-3-STRCALLHISFAIL :
cch323_store_call_history: [chars]Explanation An attempt to insert an active H323 call record into the call history list has failed.
Recommended Action No action is required.
CCPROXY Messages
The following are H.323 proxy error messages.
Error Message%CCPROXY-3-NOBLOCK_EVENT : During initialization of proxy, [chars]: cannot allocate event block\n
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCPROXY-3-NOCCAPI_INTERFACE : CCAPI new interface is not created in [chars]\n
Explanation The new call-control API interface was not created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCPROXY-3-NOCCB_FROM_CALLID : No call-control-block is found in [chars] for ([hex]).\n
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCPROXY-3-UNREGISTERED_BY_GK : H.323 Proxy registration is being removed by Gatekeeper [chars]\nCheck "show proxy h323 status" for details.
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
CDM Messages
The following are Cable Data Modem (CDM) error messages.
Error Message%CDM-6-CHANNELDOWN : Channel(vpi=[dec]) on [chars], changed state to down
Explanation The signaling connection to this system has gone down.
Recommended Action This is an informational message only. No action is required.
Error Message%CDM-6-CHANNELUP : Channel(vpi=[dec]) on [chars], changed state to up
Explanation The signaling connection to this system has been activated.
Recommended Action This is an informational message only. No action is required.
Error Message%CDM-6-CHANNELUPPENDING : Channel(vpi=[dec]) on [chars], changed state to up pending
Explanation 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 This is an informational message only. No action is required.
Error Message%CDM-3-CONFIG : Interface [chars] must be ACIP to run cable application
Explanation The named interface is not an ATM Cable Interface Processor interface.
Recommended Action An ATM Cable Interface Processor is required to run the CDM application. Verify that an ATM Cable Interface Processor is installed in the system.
Error Message%CDM-3-INIT : ACIP required to run this Cisco IOS image
Explanation No ATM Cable Interface Processor is installed in the system.
Recommended Action An ATM Cable Interface Processor is required to run the cable data modem (CDM) application. Install an ATM Cable Interface Processor.
Error Message%CDM-6-MODEMDOWN : Modem(vci=[dec]) on [chars], changed state to down
Explanation A modem was disconnected from the system.
Recommended Action No action is required. This message is informational only.
Error Message%CDM-6-MODEMUP : Modem(vci=[dec]) on [chars], changed state to up
Explanation A new modem was connected to the system.
Recommended Action No action is required. This message is informational only.
CDP Messages
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 CDP has discovered a mismatch of duplex configuration.
Recommended Action Configure the interfaces so they are both running at the same duplex (full- or half-duplex).
Error Message%CDP-4-NATIVE_VLAN_MISMATCH : Native VLAN mismatch discovered on [chars] ([dec]), with [chars] [chars] ([dec]).
Explanation CDP has discovered a mismatch of native VLAN configuration.
Recommended Action Configure the interfaces to use the same native VLAN.
CE3 Messages
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CE3-2-CE3FWCRASHED : CE3 F/W crashed: [hex] - VIP reset
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, contact 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, contact 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 bay
Explanation The CE3 hardware has failed. Some components on the board failed to initialize.
Recommended Action Replace the CE3 port adapter.
Error Message%CE3-1-DISCOVER : Found [dec] interfaces in bay [dec], shutting down bay
Explanation 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CE3-1-DWNLDFAIL : Microcode to slot [dec]
Explanation An attempt to download firmware into the CE3 port adapter has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CE3-1-ENABLEFAIL : [chars] could not be enabled by [chars]
Explanation The restart has failed to enable the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CE3-3-ERROR : [chars]
Explanation This message provides general error information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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, contact 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CE3-3-LOVEFAIL : [chars]: failed to send [chars] love letter
Explanation A "love letter" (operating status or configuration message) was not sent to the RSP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CE3-3-MBOXRECV : Failed to receive reply [dec] from bay [dec] firmware
Explanation 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, contact 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 firmware
Explanation 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, contact 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] firmware
Explanation 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, contact 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 firmware
Explanation A port-related message was not sent to CE3 firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CE3-3-NOACC : [chars] - Accumulator is not available
Explanation 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, contact 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 An attempt to detect the HDLC controller on the CE3 has failed.
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.
Recommended Action Replace the CE3 port adapter.
Error Message%CE3-1-NOTREADY : Slot [dec] for microcode download
Explanation An error was detected on the communication path between the VIP and the CE3 port adapters.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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, contact 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 has failed to reset the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CE3-1-STARTFAIL : [chars] could not be enabled by [chars]
Explanation The restart has failed to enable the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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, contact your Cisco technical support representative, and provide the representative with the gathered information.
CES Messages
The following are Circuit Emulation Service (CES) error messages.
Error Message%CES-2-INTERNAL_CRITICAL : [chars]
Explanation The 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CES-3-INTERNAL_ERROR : [chars]
Explanation The 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CES-4-INTERNAL_WARNING : [chars]
Explanation The 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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
CHOPIN Messages
The following are Cisco Chopin error messages.
Error Message%CHOPIN-3-BADADDR : chopin_little_endian_addr: Attempted conversion of invalid address ([hex])
Explanation A software error has occurred during an attempt to determine PCI device addressing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADADDR2 : chopin_big_endian_addr: Attempted conversion of invalid address ([hex])
Explanation A software error has occurred during an attempt to determine PCI device addressing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADBAYDEV : get_pci_dev_num: Invalid bay ([dec]) or device number offset ([dec])
Explanation A software error has occurred during an attempt to determine PCI device addressing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADDEVNO : pas_get_device_subunit: Invalid PCI device number: [dec]
Explanation A software error occurred during an attempt to determine PCI device addressing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADNV : Detected invalid NVRAM size: [dec] bytes
Explanation The detected size of NVRAM is not one of the supported sizes. The NVRAM may be faulty.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADPA : Invalid Port Adaptor type ([dec]) reported for mainboard
Explanation The virtual port adapter type that was derived from the main board type is not supported. One reason for this condition is that this main board is a new main board type and the software release that is running on the system does not support the new main board type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADPCIRD : PCI Configuration Read Cycle Failed for bus [dec], Device [dec], function [dec], register [dec]
Explanation A PCI Bus Configuration Read cycle has failed. The main board needs to be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADPCIWR : PCI Configuration Write Cycle Failed for bus [dec], Device [dec], function [dec], register [dec]
Explanation A PCI Bus Configuration Write cycle has failed. The main board needs to be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-INITFAIL : CHOPIN (bay [dec]), Init Failed at [chars] - line [dec] arg [hex]
Explanation The port adapter has failed to complete its hardware initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation A MAC address cannot be allocated for the specified interface because all available MAC addresses for the system have been allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-6-NOTDMBP : No TDM backplane is supported on slot [dec].
Explanation A TDM backplane is not supported on the specified slot; therefore, DS0 inter slot cannot be cross-connected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-6-NOTSUPPORT : Voice PA is not supported in this platform.
Explanation The port adapter is not supported on this platform.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-NVERASEFAIL : Failed to erase config due to internal error
Explanation The password protection feature has failed to erase a configuration because of an internal error.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-1-OVERTEMP : System detected OVERTEMPERATURE condition.
Putting the system in Power save mode and going to rommon.
Please resolve cooling problem and restart system!\nExplanation The environmental monitor has detected a high-temperature condition.
Recommended Action Make sure that the room temperature is within recommended ranges and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-6-RXDFILLFAIL : CHOPIN (bay [dec]), Data rx ring refill failed: rxd_fill_fail=[dec]
Explanation The port adapter has failed to refill the data Rx ring.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-6-RXVFILLFAIL : CHOPIN (bay [dec]), Voice rx ring refill failed: rxv_fill_fail=[dec]
Explanation The port adapter has failed to refill the voice Rx ring.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-1-STARTFAIL : [chars] channel not enabled
Explanation A software or hardware error has occurred. The Chopin serial interface is not responding to the commands that are used to initialize it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-TDMFAIL : CHOPIN-TDM, access failed at [chars] - line [dec], arg1=[dec],arg2=[dec]
Explanation The port adapter has failed to access the TDM switch.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-TSBUSY : CHOPIN (bay [dec]), TDM timeslot is busy: ST=[dec]/TS=[dec]
Explanation The port adapter has failed to grant a cross-connect setup request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-TSNONBUSY : CHOPIN (bay [dec]), TDM timeslot is non busy: ST=[dec]/TS=[dec]
Explanation The port adapter has failed to grant a cross-connect teardown request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-5-TXVFULL : CHOPIN (bay [dec]), Voice tx ring is full: dma_done=[dec], last_dma_done=[dec]
Explanation The voice Tx ring for the port adapter is full.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-UNEXPEVENT : CHOPIN (bay [dec]), received an unexpected event=[hex]
Explanation The port adapter has received an unexpected event from the firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CHOPIN_MAINBOARD_ASYNC_PQII Messages
The following are Chopin Main Board Asynchronous Driver error messages.
Error Message%CHOPIN_MAINBOARD_ASYNC_PQII-3-NOMEMORY : No memory for [chars] of unit [dec]
Explanation The router does not have enough memory to perform the requested function.
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.