-
Cisco IOS Release 12.4 System Messages, Volume 1 of 2
-
System Messages Overview
-
AAA through ASPP
-
AT through BGP
-
BIT through C6KPWR
-
C6MSFC through CHOPIN_MAINBOARD_ASYNC_PQII
-
CI through COT
-
CPAD through DBUS
-
DCV through DSCREDCLK
-
DSI through ENT
-
ENV_MON through FR_FRAG
-
FR_LMI through GSR_ENV
-
GSRIPC through IF
-
IFINDEX through ISA
-
ISDN through LCCOREDUMP
-
LCINFO through MBRI
-
Volume 1 Glossary
-
Table Of Contents
CHOPIN_MAINBOARD_ASYNC_PQII Messages
C6MSFC Messages
The following are C6MSFC (Draco) messages.
Error Message%C6MSFC-3-BADCPUTYPE : Invalid CPU Type [dec].
Explanation The software does not recognize the MSFC on which it is operating. This problem might be caused by an improperly programmed or defective identification programmable read-only memory (IDPROM). [dec] is the invalid CPU type.
Recommended Action Contact your Cisco technical support representative to update your system.
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 content of the MAC address EEPROM is invalid. The system is providing a random MAC address. [enet] is the MAC address
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
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 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 Contact technical support to update your system.
Error Message%C6MSFC-3-NOCPUVER : Invalid CPU Revision [dec].
Explanation The CPU ID could not be read from the EEPROM. This condition occurs when there is a hardware failure or when an incorrect Cisco IOS software image is loaded on the platform.
Recommended Action Ensure that the correct Cisco IOS software image is loaded on the platform.
Error Message%C6MSFC-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation The MAC address allocation failed because of an incorrect slot and interface combination, which exceeds the maximum available hardware. [num] / [num] are the module and interface numbers.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%C6MSFC-4-PCIVALID : PCI activation failed, bay [dec], [hex]
Explanation Unavailable.
Recommended Action Unavailable.
C6SUP Messages
The following are C6SUP-specific 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
C7200_TDM Messages
The following are Cisco 7200 midplane TDM bus 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 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 was made to use the TDM midplane.
Recommended Action 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 was made to use the TDM midplane.
Recommended Action No action is required.
Error Message%C7200_TDM-4-TDM_MONITOR : \nTDM Monitor running, counter = [dec], failed = [dec]\n
Explanation The TDM monitor is now running.
Recommended Action No action is required.
Error Message%C7200_TDM-4-TDM_MONITOR_DONE : \nTDM Monitor stopped, counter = [dec], failed = [dec]\n
Explanation The TDM monitor has completed its task.
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 No action is required.
C830_HW_CRYPTO Messages
The following are C830 Hifn messages.
Error Message%C830_HW_CRYPTO-0-HIFN_KAT_FAILURE : Hifn 7902 Known Answer Test failed ([chars])
Explanation One of the known answer tests has failed. The hardware crypto engine is not operable in this state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
C950 Messages
The following are Cisco 950 messages.
Error Message%C950-3-BADADDR : c950_little_endian_addr: Attempted conversion of invalid address ([hex])
Explanation A software error occurred during an attempt to determine PCI device addressing. This condition is most likely caused by a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C950-3-BADADDR2 : c950_big_endian_addr: Attempted conversion of invalid address ([hex])
Explanation A software error occurred during an attempt to determine PCI device addressing. This condition is most likely caused by a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C950-3-BADBAYDEV : get_pci_dev_num: Invalid bay ([dec]) or device number offset ([dec])
Explanation A software error occurred during an attempt to determine PCI device addressing. This condition is most likely caused by a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C950-3-BADDEVNO : pas_get_device_subunit: Invalid PCI device number: [dec]
Explanation A software error occurred during an attempt to determine PCI device addressing. This condition is most likely caused by a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C950-3-BADNV : Detected invalid NVRAM size: [dec] bytes
Explanation The detected size of NVRAM is not one of the supported sizes. The NVRAM might be corrupt.
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%C950-3-BADPA : Invalid Port Adaptor type ([dec]) reported for mainboard
Explanation The virtual port adapter type derived from the mainboard type is not one of the supported types. It may be that this mainboard is a new mainboard type and the software release that the system is running does not support the new mainboard 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%C950-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.
Recommended Action Replace the mainboard. 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%C950-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.
Recommended Action Replace the mainboard. 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%C950-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation 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%C950-3-NVERASEFAIL : Failed to erase config due to internal error
Explanation The password protection feature failed to erase the 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%C950-1-OVERTEMP : System detected OVERTEMPERATURE condition.\nPutting the system in Power save mode and going to rommon.\nPlease resolve cooling problem and restart system!\n
Explanation The environmental monitor has detected a high-temperature condition.
Recommended Action Make sure that the room temperature is not too high 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.
CAIM Messages
The following are Compression Advanced Interface Module (CAIM) 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 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 the alternate app [chars].\n
Explanation The inbound dial peer is pointing to an unavailable application.The call is being handed to the alternate application or is rejected.
Recommended Action Reconfigure the dial peer to have a valid application name, or verify that the application is accessible at its location.
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-3-CCAPI_DB_ERR : ccapi database error
Explanation An internal CCAPI conference or call record database error has occurred. This message represents an internal software fault that can appear in the system as either dropped or hung calls.
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_CONTROL-3-INVALID_PARAMETER : An invalid parameter is passed to the function
Explanation A coding error has been detected.
Recommended Action No action is required.
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.
Error Message%CALL_CONTROL-3-STAT_MEMORY_CORRUPTED : Memory corruption detected in memory=[hex] allocated for RTCP statistic
Explanation A coding error has been detected.
Recommended Action No action is required.
Error Message%CALL_CONTROL-6-UNKNOWN_EXT_AGENT_RESET_ATTEMPT : Request to reset an uknown external agent (ID [dec]) attempted. Attempt ignored.\n
Explanation An attempt to reset an external agent has failed (such as the H323 Gatekeeper or the MGCP CA). A failed attempt is not a router error. However, it does indicate that the external agent never received the reset request.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
CALL_MGMT Messages
The following are call management subsystem 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 might 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 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 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.
Error Message%CALLRECORD-3-SCM_TERSE_CALL_FAILED_REC : [chars]
Explanation An attempt to write a terse SCM call record has failed.
Recommended Action No action is required.
Error Message%CALLRECORD-3-SCM_TERSE_CALL_REC : [chars]
Explanation A terse SCM call record has been successfully written.
Recommended Action No action is required.
CALLTREAT Messages
The following are Call treatment messages.
Error Message%CALLTREAT-3-HIGH_CPU_5SEC_LOAD : System experiencing high cpu utilization. Processing for callID([dec]) is rejected.\n
Explanation The system does not have enough CPU resources available to accept a new call. The specified call was rejected.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Enter the show proc cpu command to determine which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the five-second CPU utilization on the gateway exceeds 89%. The default value can be overridden by enabling call treatment and entering the call threshold global cpu-5sec command.
Error Message%CALLTREAT-3-HIGH_CPU_AVERAGE_LOAD : System experiencing high average cpu utilization. Processing for callID([dec]) is rejected.\n
Explanation Based on the average CPU utilization over a 60-second interval or an interval configured through the call threshold poll-interval command, the system does not have enough CPU resources available to accept a new call. The specified call was rejected.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Check to see if the current call setup rate is supported on this gateway. Enter the show proc cpu command to determine which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the five-second CPU utilization on the gateway exceeds 98%. The default value can be overridden by enabling call treatment and entering the call threshold global cpu-avg command.
Error Message%CALLTREAT-3-HIGH_CPU_ONE_MIN_LOAD : System experiencing high cpu utilization over one minute interval. Processing for callID([dec]) is rejected.\n
Explanation Based on the average CPU utilization over a 60-second interval, the system does not have enough CPU resources available to accept a new call. The specified call was rejected.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Enter the show proc cpu command to determine which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the five-second CPU utilization on the gateway exceeds 98%.
Error Message%CALLTREAT-3-HIGH_IOMEM_USAGE : System running low on I/O memory. Processing for callID([dec]) is rejected.\n
Explanation The system does not have enough free I/O memory to accept a new call. The specified call was rejected.
Recommended Action Ensure that the gateway has the recommended amount of I/O memory for this Cisco IOS feature set and version. Enter the show mem and show proc mem commands to determine which processes are consuming the most memory. Check if the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. The high and low thresholds for I/O memory utilization can be configured by enabling call treatment and entering the call threshold global io-mem command.
Error Message%CALLTREAT-3-HIGH_MEMORY_USAGE : System running low on memory. Processing for callID([dec]) is rejected.\n
Explanation The system does not have enough free memory to accept a new call. The specified call was rejected.
Recommended Action Ensure that the gateway has the recommended amount of memory for this Cisco IOS feature set and version. Enter the show mem and show proc mem commands to determine which processes are consuming the most memory. Check if the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. By default, the system will reject calls if there is less than 2% free processor memory on the gateway. This value can be overridden by enabling call treatment and entering the call threshold global total-mem command.
Error Message%CALLTREAT-3-HIGH_PROCMEM_USAGE : System running low on processor memory. Processing for callID([dec]) is rejected.\n
Explanation The system does not have enough free processor memory to accept a new call. The specified call was rejected.
Recommended Action Ensure that the gateway has the recommended amount of processor memory for this Cisco IOS feature set and version. Enter the show mem and show proc mem commands to determine which processes are consuming the most memory. Check if the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. The high and low thresholds for processor memory utilization can be configured by enabling call treatment and entering the call threshold global proc-mem command.
Error Message%CALLTREAT-3-HIGH_TOTAL_CALLS : High call volume. Processing for callID([dec]) is rejected.\n
Explanation The system is experiencing a high call volume. There are not enough resources to accept a new call. The specified call was rejected.
Recommended Action Disable call threshold, modify the call threshold global high and low values, or investigate the cause of the high resource utilization. The high and low thresholds for total number of calls can be configured by enabling call treatment and entering the call threshold global proc-mem command.
CALLTREAT_NOSIGNAL Messages
The following are Call Treatment (TREAT) messages.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_CPU_5SEC_LOAD : System experiencing high cpu utilization.
Explanation The system does not have enough CPU resources available to allocate a new resource.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Enter the show processes cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the 5-second CPU utilization on the gateway exceeds 89 percent. The default value can be overridden by enabling call treatment and entering the call threshold global cpu-5sec command.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_CPU_AVERAGE_LOAD : System experiencing high average cpu utilization.
Explanation On the basis of the average CPU utilization over a 60-second interval or over an interval configured through the call threshold poll-interval command, the system does not have enough available CPU resources to accept a new call.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Verify that the current call setup rate is supported on this gateway. Enter the show processes cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the 5-second CPU utilization on the gateway exceeds 98 percent. The default value can be overridden by enabling call treatment and entering the call threshold global cpu-avg command.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_CPU_ONE_MIN_LOAD : System experiencing high cpu utilization over one minute interval.
Explanation On the basis of the average CPU utilization over a 60 second interval, the system does not have sufficient available CPU resources.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Enter the show processes cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject resource allocation if the 5-second CPU utilization on the gateway exceeds 98 percent.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_IOMEM_USAGE : System running low on I/O memory.
Explanation The system does not have enough free I/O memory.
Recommended Action Ensure that the gateway has the recommended amount of I/O memory for this Cisco IOS software feature set and version. Enter the show memory and show processes memory commands to see which processes are consuming the most memory. Verify that the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. The high and low thresholds for I/O memory utilization can be configured by enabling call treatment and entering the call threshold global io-mem command.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_MEMORY_USAGE : System running low on memory.
Explanation The system does not have enough free memory to allocate a new resource.
Recommended Action Ensure that the gateway has the recommended amount of memory for this Cisco IOS software feature set and version. Enter the show memory and show processes memory commands to see which processes are consuming the most memory. Verify that the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. By default, the system will reject calls if there is less than 2 percent free processor memory on the gateway. This value can be overridden by enabling call treatment and entering the call threshold global total-mem command.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_PROCMEM_USAGE : System running low on processor memory.
Explanation The system does not have enough free processor memory.
Recommended Action Ensure that the gateway has the recommended amount of processor memory for this Cisco IOS software feature set and version. Enter the show memory and show processes memory commands to see which processes are consuming the most memory. Verify that the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. The high and low thresholds for processor memory utilization can be configured by enabling call treatment and entering the call threshold global proc-mem command.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_TOTAL_CALLS : High call volume.\n
Explanation The system is experiencing a high call volume.
Recommended Action Perform one or all of the following actions:
•
Disable the call threshold feature.
•
•
CALLTRKR Messages
The following are call tracker subsystem 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-6-MODEM_V92_V44_CALL_REC : [chars]
Explanation A modem V92 and V44 verbose CallTracker 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 might 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 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-2-CT3_E1_MIX : Cannot mix E1 PRI and CT3 DFC in chassis, do not power up invalid card in slot [dec]\n
Explanation The user has put E1 PRI and CT3 DFC cards in the same chasis. Do not install these cards in the same chassis.
Recommended Action Remove the extra E1 PRI or CT3 DFC card.
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-2-HYBRID_CARD_INVALID_DFC_CONFIG : Invalid DFC combination found on Hybrid card, [dec] Trunk DFC and [dec] NP108 DFCs detected.
Explanation A hybrid card requires one trunk DFC and two NP108 DFCs 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-INVALID_DFC : Feature board in slot [dec] does not have valid DFCs!
Explanation The feature board in the specified slot contains invalid DFCs.
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.
Error Message%CARRIER-2-TOOMANY_TRUNK : Too many trunk DFC cards, do not power up invalid card in slot [dec]\n
Explanation Too many trunk DFC cards are present in the chassis.
Recommended Action Remove the extra trunk DFC card.
Error Message%CARRIER-2-TRUNK_DFC_ANALYZE : One of the Trunk DFCs in slot [dec] has failed initialization!
Explanation One of the trunk DFCs in this slot has failed its 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.
CASA Messages
The following are Cisco Appliance and Services Architecture (CASA) 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 can 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 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 might 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 might 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 might 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 might 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 \n [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 might 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 might 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 might 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 might 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 might 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 might 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 might 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 might 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 might 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 might 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 might 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-CE3DSX3ERR : ([chars])Illegal E3 value - unit is [dec]
Explanation A status information message was received from the CT3 VIP, but during message processing it was detected that an element in the data structure corresponding to the status information message has not been set. This condition may be caused by either an element that has not been passed by the VIP or a corruption in the status message.
Recommended Action If this error recurs, copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS-3-CT3STAT : Out of buffers--losing status information for CT3 on VIP card
Explanation A status information message from the VIP was received. A memory buffer is required to process the status information message, but the memory allocation routine failed because of insufficient system buffer memory, and the status information message was not processed. This condition may be caused either by heavy memory utilization at the time of the memory buffer request or by insufficient memory in the system.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs or appears regularly, contact your Cisco technical support representative to upgrade the memory of the system.
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 might 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\n -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 might 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 might 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 might 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 failed an internal diagnostic test. Test output and descriptions of ranges follow:
–
Unit [dec](ranges 0—14): Indicates the Multibus jumper setting for the ciscoBus controller, or a slot number in the Cisco 7000.–
daughter controller [dec](ranges 0—3): Indicates the ciscoBus relative slot number (0 to 3, or, in the Cisco 7000, 0 to 4) of the daughter card that failed the test.–
failed [chars] test ([chars]=memd read,memd write): If the failed test was `memd read', the processor was able to write to shared ciscoBus buffer memory from the ciscoBus registers, but was unable to read back that memory through special commands to the daughter card. 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 its memory device tests failed. The daughter card must be able to write to some memory device addresses; otherwise, it cannot respond to any commands.
Recommended Action First, check 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, 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_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:
–
Unit [dec](ranges 0—14): Indicates the Multibus jumper setting for the ciscoBus controller.–
daughter controller [dec](ranges 0—3): Indicates the ciscoBus relative slot number (0 to 3, or, in the Cisco 7000, 0 to 4) of the daughter card that failed the test.The daughter card hardware was recognized across the CBus backplane, but the daughter card did not respond to the first command issued to it.
This condition is a result of one of the following: the daughter card did not reset, 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 did 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 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-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-HALSDHERR : ([chars])Illegal sdh value - unit is [dec]
Explanation The internal data structure has been corrupted, causing 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 might 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-HALSTAT : Out of buffers--losing status information for ChSTM-1 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 might 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-HSSIRSET : Interface [chars], Error ([hex]) [chars] - hssi_reset()
Explanation A command to reset an HSSI interface was issued by the RSP, but the interface did not respond to the command within the expected time delay. The delay is given for the processor to return the buffers that it has allocated and to perform any necessary cleanup. This condition may be caused by the allocation of a large number of buffers by the interface due to either heavy traffic or a hardware problem with the interface.
Recommended Action Verify that the card is properly seated. If this error recurs, issue the show tech-support and show logging commands, 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 might 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 might 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 might 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 might 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 might 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 might 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 might 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-SRPRSET : Interface [chars], Error ([hex]) [chars] - srp_reset()
Explanation A command to reset an SRP interface was issued by the RSP, but the interface did not respond to the command within the expected time delay. The delay is given for the processor to return the buffers that it has allocated and to perform any necessary cleanup. This condition may be caused by a large number of buffers that have been allocated by the interface due to either heavy traffic or a hardware problem with the interface.
Recommended Action Verify that the card is properly seated. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
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 might 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.
CBUS_ATTN Messages
The following are CMCC Channel Interface Processor (CIP) messages relating to the ciscoBus controller statistics routine, the facility that receives configuration requests and gathers statistics.
Error Message%CBUS_ATTN-3-BADADDR : Bad memory address ([hex]) requested
Explanation The RP requested that the CIP store a configuration command at an invalid memory address. The CIP has ignored the request.
Recommended Action Check if there were any special events that coincided with this error message. Pay particular attention to any unusual output from show, debug, or configuration commands. If this message occurs repeatedly, issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS_ATTN-3-DUMPUCODE : Dump of the CIP microcode has been requested
Explanation An "output stuck" condition has been detected by the Cisco IOS software. When this error occurs, it means that a CIP software problem has occurred, such as a loop that prevents messages destined for the CIP from being processed.
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.
CBUS_WRITE Messages
The following are CMCC Channel Interface Processor (CIP) messages for ciscoBus controller write support. The ciscoBus controller write feature is used by the enhanced online insertion and removal (EOIR) support on the CIP to track write operations to the memory device and reissue them if a ciscoBus problem occurs.
Error Message%CBUS_WRITE-3-BADTYPE : Invalid write type [dec]
Explanation The type parameter in the write tracking table is invalid. This is an internal logic error. The CIP recovered by ignoring the entry.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS_WRITE-3-INVALID : Valid bit not set in IO exception register ([hex])
Explanation A write error interrupt occurred, but the hardware that keeps track of the address of the error does not have a valid address. The CIP ignored this error condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS_WRITE-3-MISSING : Entry for address [hex] not found
Explanation A write error was detected, but there was no corresponding entry in the table that keeps track of these entries. This is an internal logic error. The CIP recovered by ignoring the write error.
Recommended Action This error message is followed by a number of CBUS_WRITE-STACK messages. Copy the messages exactly as they appear on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS_WRITE-3-STACK : [dec] [dec] [hex] [hex] [hex]
Explanation This is a debugging display from the CBUS write stack and is associated with the CBUS_WRITE-3-MISSING error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS_WRITE-3-UNEXPECTED : Unexpected IO write error. Address=[hex]
Explanation A write operation to an address other than the memory device (MEMD) has timed out. This is probably a hardware problem. The CIP failed and attempted to restart. The CIP will probably have to be replaced.
Recommended Action The CIP might need to be replaced. 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.
CCA Messages
The following are CMCC Channel Interface Processor (CIP) messages for channel card adapter processing.
Error Message%CCA-3-ACR : Accept command response status received
Explanation The adapter has notified the CIP that an accept command response was been issued. The CIP does not request notification of accept command response messages. Therefore, this message means that the adapter has generated an unexpected message.
Recommended Action Normal processing will resume, but the software developers should be notified that this message has occurred. 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%CCA-0-BADCCA : Undefined CCA code received CCA=[hex] [hex]
Explanation The adapter has presented the CIP with a message using an undefined code point. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-0-BSQ_FULL : Buffer status queue is full
Explanation The adapter has notified the CIP that the buffer status queue is full. The CIP never provides enough buffers to the adapter to cause the buffer status queue to become full. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-BYPASS : Select bypass switch may be in bypass position for port [dec]
Explanation A user has attempted to start the PCA with the select bypass switch in the BYPASS position. The PCA cannot go online with the switch in the BYPASS position.
Recommended Action Move the select bypass switch on the PCA-Y cable from the BYPASS position to the SELECT position.
Error Message%CCA-3-CANCEL1 : Invalid cancel code ([hex])
Explanation The adapter has notified the CIP that a halt subchannel command was issued by the host, but has provided the CIP with an undefined type of cancel.
Recommended Action The CIP will recover, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-CANCEL2 : Cancel received for undefined path ([hex])
Explanation The adapter has notified the CIP that a halt subchannel command was issued by the host for an undefined path. This is an internal logic error.
Recommended Action The CIP software recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-COMMAND_PATH : Command connection received for undefined path ([hex])
Explanation The adapter has notified the CIP that a start subchannel command was issued by the host for an undefined path. This is an internal logic error.
Recommended Action The CIP software recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-CONN_RESULT : Connection result for device [hex][hex] expected [hex][hex]
Explanation The adapter has notified the CIP that a connection was established for a device other than the one that the CIP had just requested. This is an internal logic error.
Recommended Action The CIP software recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-0-DEV_ERR1 : Undefined device error type ([hex])
Explanation When a device error occurs, the adapter specifies the type of error so that the correct recovery action can be performed. The type specified in this message is not defined. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-0-DEV_ERR2 : Device error but no active defined device
Explanation A device error was generated, and either it occurred while status was being presented but no device was active or it occurred for an undefined device. This is a fatal internal logic error.
Recommended Action 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%CCA-0-DEV_ERR3 : Device error received for undefined path ([hex])
Explanation A device error has occurred, but the path specified in the device error message is not defined. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-DEV_ERR4 : Control Unit Busy timer wasn't started for device [hex][hex]
Explanation During a device-level error, the "control unit busy" statistic was not updated because the timer was never started.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-END_STATUS : Ending status interrupt received for [hex] CCW
Explanation The adapter has reported an ending status interrupt for a channel command word that should not have caused the CIP to be notified. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-LOGOUT : Invalid logout command modifier ([hex])
Explanation The adapter has sent a request to the CIP to perform a logout, but the command modifier in the message was not a valid value. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-REQUEST_STATUS : Request status received for undefined path ([hex])
Explanation The adapter has requested that the CIP present the status of an undefined path. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-RESET_PATH : Reset received for undefined path ([hex])
Explanation The adapter has requested the CIP to perform reset processing for an undefined path. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-RLP1 : Invalid rlp flags ([hex])
Explanation The adapter requested that the CIP reset a logical path, but the flags on the reset request were not valid. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-RLP2 : RLP received for undefined path ([hex])
Explanation The adapter requested that the CIP reset a logical path for a path that is currently undefined.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-0-SCBNRDY : Unexpected SCB not ready CCA=[hex] [hex]
Explanation The CIP has been notified that an I/O operation was attempted with a storage control block that was marked as "not ready". The specified I/O operation should never have a "not ready" storage control block. This is a fatal internal logic error.
Recommended Action 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%CCA-3-SEL_RESET1 : Invalid selective reset code ([hex])
Explanation The adapter has requested that the CIP perform a selective reset, but the request code in the message was not a valid value. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-SEL_RESET2 : Selective reset received for undefined path ([hex])
Explanation The adapter has requested the CIP to perform a selective reset on an undefined logical path. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-STATUS_NOTICE : Undefined status notice request code [hex]
Explanation The adapter has presented the CIP with notification that status was accepted by the channel, but the request code in the status message was not a valid code. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-STATUS_NOTICE2 : Control Unit Busy timer wasn't started for device [hex][hex]
Explanation During status presentation, the "control unit busy" statistic was not updated because the timer was never started.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-3-SYS_RESET : Invalid system reset code ([hex])
Explanation The adapter has requested the CIP to perform a system reset, but the request code in the message was not a valid value. This is an internal logic error.
Recommended Action The CIP has recovered, but the software developers should be notified of this problem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CCA-0-TOOMANY : Too many buffers ([dec]) required for a write operation.
Explanation The mainframe has written data to the CIP, and the number of buffers required to hold all the data being written was more than the total number of buffers allocated on the CIP for that purpose. This is a fatal error.
Recommended Action 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%CCA-3-WRAPPLUG : Wrap plug is installed on port [dec]
Explanation The wrap plug is installed on the PCA in the specified port. The PCA cannot be used unless it is connected to a channel.
Recommended Action Remove the wrap plug and connect the channel cables.
Error Message%CCA-0-WRITE_FAIL : Write of response CCA failed.
Explanation The adapter requested the CIP to perform an operation. When the CIP tried to present the response to the request, it was not able to write to the common communication area. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
CCH323 Messages
The following are Call Control for H323 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 might 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_ALLOCATE_GW : [chars]: cannot allocate gateway structure
Explanation Allocation of the CCH323 gateway instance has failed. A possible cause is the exhaustion of the system memory pool. This error can be catastrophic.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CCH323-3-CANNOT_CREATE_CCB : [chars]: cannot create the H.323 ccb Tree
Explanation An attempt to create the H.323 call control block tree has failed. A possible cause is the exhaustion of the system memory pool. This error can be catastrophic.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CCH323-3-CANNOT_CREATE_CRVHASH_TBL : [chars]: cannot create the H.323 crv hash table
Explanation An attempt to create the H.323 H.323 CRV hash table has failed. A possible cause is the exhaustion of the system memory pool. This error can be catastrophic.
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%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 might 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_H225_SEND_EVENT_FAILED : [chars]: create send internal event [chars] to H.225 state machine failed
Explanation An attempt to create and send an event to an H.225 state machine has failed. This condition can be a catastrophic error. Possible causes of the error are that the call control block is missing or that there is not enough memory for event buffers.
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%CCH323-3-CCH323_H245_SEND_EVENT_FAILED : [chars]: create and send event [chars] to H.245 state machine failed
Explanation An attempt to create and send an event to an H.245 state machine has failed. This condition can be a catastrophic error. Possible causes of the error are that the call control block is missing or that there is not enough memory for event buffers.
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%CCH323-3-CCH323_MALLOC_FAILED : [chars]: cannot allocate message buffer
Explanation Allocation of the CCH323 message buffer has failed. A possible cause is the exhaustion of the system memory pool. This error can be catastrophic.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CCH323-3-CCH323_RAS_SEND_EVENT_FAILED : [chars]: create and send event [chars] to RAS state machine failed
Explanation An attempt to create and send an event to a RAS state machine has failed. This condition can be a catastrophic error. Possible causes of the error are that the call control block is missing or that there is not enough memory for event buffers.
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%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 might 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 might 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 might 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 might 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-H225_LIBRARY_INIT_FAILED : [chars]: H.225.0 library initialization failed
Explanation H.225.0 library initialization has failed. This error can be catastrophic.
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%CCH323-3-H225_SM_INIT_FAILED : [chars]: H.225.0 State Machine integrity check failed for state [chars]
Explanation H.225 state machine integrity check has failed. This error can be catastrophic.
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%CCH323-3-INTERNAL_EVENT_QUEUE_INIT_FAILED : [chars]: Internal event queue initialization failed
Explanation Errors were found during initialization of the internal event queue. This error can be catastrophic.
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%CCH323-3-MAXIMUM_INTERNAL_EVENT_BUFFERS_EXCEED : [chars]: Exceeding limit on allocating internal event buffers
Explanation The limit for allocating internal event buffers has been exceeded. This severe error can be caused by internal loops started when events are sent between state machines.
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%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 might 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-POSSIBLE_INTERNAL_EVENT_LOOP : [chars]: Exceeding limit on servicing internal event for the same call
Explanation The maximum limit on servicing the internal event queue has been exceeded. This severe error can be caused by internal loops started when events are sent between state machines.
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%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 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.
CDMA_PDSN Messages
The following are CDMA PDSN messages.
Error Message%CDMA_PDSN-3-CMDNOTCONFIGURED : Attempt to open session without virtual-template configured
Explanation The PDSN has refused to open the session because a virtual template has not been configured.
Recommended Action Configure a virtual template by entering the cdma pdsn virtual-template command.
Error Message%CDMA_PDSN-4-CONFIG_ERROR : Master slave PDSN clustering configured or in progress.
Explanation Either the active PDSN or the standby PDSN functionality is being configured in this PDSN. The intelligent selection feature, or peer-to-peer clustering feature, cannot be configured on the same PDSN that runs either the active PDSN or the standby PDSN functionality.
Recommended Action Either do not configure the PDSN selection feature, or unconfigure either the active PDSN or the standby PDSN.
Error Message%CDMA_PDSN-3-FSDROPPAK : No session [chars]
Explanation The system cannot find a session in the FS path. The packet has been dropped. This condition indicates an internal error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CDMA_PDSN-3-GRPPROFERROR : Group Profile contains UserClass/IpTech as MobileIP
Explanation The group profile contains a User Class or IP Tech Value of "MobileIP". MSID-based access using a group profile cannot use "MobileIP" as its User Class or IP Tech Value.
Recommended Action Check and correct the group profile in the AAA server.
Error Message%CDMA_PDSN-3-GRPPROFERROR2 : Group Profile contains VPDN attributes
Explanation The group profile contains VPDN attributes. MSID-based access using a group profile cannot have VPDN attributes.
Recommended Action Check and correct the group profile in the AAA server.
Error Message%CDMA_PDSN-1-PPPNOMEMALERT : No memory to create a vaccess
Explanation An internal CDMA PDSN PPP error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CDMA_PDSN-4-PPPUNEXPWARNING : Unexpexted event [dec]
Explanation An internal error involving CDMA PDSN PPP processing has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CDMA_PDSN-3-PPPVACERR : Free Virtual Access interface failure
Explanation An internal error occurred while the virtual template was being freed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CDMA_PDSN-3-PREPAIDUNSUPPORTED : Prepaid is not supported by this image
Explanation A user profile using "Prepaid" was specified. "Prepaid" is not supported by this Cisco IOS software image.
Recommended Action Remove the configuration of "CRB_ENTITY_TYPE" from the user profile.
Error Message%CDMA_PDSN-3-PROFERROR1 : Group Profile error in case of UC/IP_Tech as NotDefined
Explanation MSID-based access was attempted using a group profile with "No User Class" or "IP Tech" with SPI in the profile. Access will be attempted without IPCP address negotiation.
Recommended Action Check and correct the group profile in the AAA server.
Error Message%CDMA_PDSN-3-PROFERROR2 : Group Profile error as profile has no REALM
Explanation MSID-based access was attempted using a group profile with no realm.
Recommended Action Check and correct the group profile in the AAA server.
Error Message%CDMA_PDSN-3-RPA11TO : A11 Registration Update re-transmission timed out at gre tunnel[dst:[IP_address]].
Explanation An RP(A10-A11) connectivity problem has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CDMA_PDSN-3-RPBADPACKET : BAD Packet : [chars]-[chars]-[dec]
Explanation An invalid packet was received from the mobile node. The format of the received packet is not included in the TR45 specifications.
Recommended Action If this message recurs consistently, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CDMA_PDSN-3-RPUNEXPECTEDMSG : Unknown [chars] Message Type = [dec]
Explanation The format of the received packet is not included in the TR45 specifications. This condition indicates an internal error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CDMA_PDSN-3-SMMAXEXCEEDED : Attempt to exceed maximum [chars] allowed ([dec])
Explanation An attempt was made to exceed the maximum configured values of the PCF or session. The PDSN has refused this attempt.
Recommended Action Increase the maximum configuration value by entering the cdma pdsn maximum pcf/session command.
Error Message%CDMA_PDSN-3-SNMPSESSION : SNMP: CDMA SESSION tree creation error
Explanation The creation of an internal structure has failed. This condition was probably caused by low available memory. SNMP reporting might not work properly.
Recommended Action Reduce other activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CDMA_PDSN-3-SNMPTREE : SNMP: CDMA PCF tree creation error
Explanation The creation of an internal structure has failed. This condition was probably caused by low available memory. SNMP reporting might not work properly.
Recommended Action Reduce other activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
CDNLD_CLIENT Messages
The following are NRP2 configuration download messages.
Error Message%CDNLD_CLIENT-3-CHECKSUM_FAIL : Checksum mismatch during configuration \n download
Explanation A checksum error was detected while the configuration file was being downloaded. The configuration file was not correctly received from the NSP.
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%CDNLD_CLIENT-6-CRASH_WR_FAIL : Failed to write crashinfo file: [chars]
Explanation The file could not be written. It is possible that the NSP log will contain more information regarding the reason for the failure.
Recommended Action Verify that the file media is present and usable and has sufficient space to hold the file.
Error Message%CDNLD_CLIENT-2-NOMEMORY : No memory available for [chars]
Explanation An operation could not be accomplished because of a low memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the memory of the router.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CDNLD_CLIENT-6-PRIVATE_RD_FAIL : Failed to read private config: [chars]
Explanation The file could not be read. The NSP log may contain more information regarding the reason for the failure.
Recommended Action Verify that the file media is present and usable and is not corrupted.
Error Message%CDNLD_CLIENT-6-PRIVATE_WR_FAIL : Failed to write private config: [chars]
Explanation The file could not be written. The NSP log may contain more information regarding the reason for the failure.
Recommended Action Verify that the file media is present and usable and has sufficient space to hold the file.
Error Message%CDNLD_CLIENT-6-STARTUP_RD_FAIL : Failed to read startup config: [chars]
Explanation The file could not be read. The NSP log may contain more information regarding the reason for the failure.
Recommended Action Verify that the file media is present and usable and is not corrupted.
Error Message%CDNLD_CLIENT-6-STARTUP_WR_FAIL : Failed to write startup config: [chars]
Explanation The file could not be written. The NSP log may contain more information regarding the reason for the failure.
Recommended Action Verify that the file media is present and usable and has sufficient space to hold the file.
CDNLD_SERVER Messages
The following are NSP configuration download messages.
Error Message%CDNLD_SERVER-6-BADCHKSUM : Bad checksum downloading: [chars]
Explanation An error has occurred during the transfer of data from the specified slot.
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%CDNLD_SERVER-6-BAD_FILE_TYPE : Config file was not ASCII text: [chars]
Explanation The NRP2 configuration file does not contain valid ASCII text.
Recommended Action Replace the existing NRP2 configuration file with a valid NRP2 configuration file.
Error Message%CDNLD_SERVER-6-CLOSE_FAILED : file close failed: "[chars]"
Explanation The file-close operation on the specified file has failed.
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%CDNLD_SERVER-6-FILERD_FAILED : file "[chars]" read failed: [chars]
Explanation The specified file could not be read. Either it does not exist or there is a problem with the file media.
Recommended Action Verify that the specified file media is present and usable and the specified file exists.
Error Message%CDNLD_SERVER-6-FILEWR_FAILED : file "[chars]" write failed: [chars]
Explanation The specified file could not be written. There may be a problem with the file media, or the media is out of space.
Recommended Action Verify that the specified file media is present and usable and has sufficient room to store the file.
Error Message%CDNLD_SERVER-6-OPEN_FAIL : file "[chars]" open failed: [chars]
Explanation The named file could not be opened. Either it does not exist, or there is a problem with the file media.
Recommended Action Verify that the specified file media is present and usable and the named file exists.
Error Message%CDNLD_SERVER-6-RENAME_FAILED : file rename failed: "[chars]" to "[chars]"
Explanation The specified file rename operation failed.
Recommended Action Verify that the specified file media is present and usable.
CDP Messages
The following are Cisco Discovery Protocol (CDP) 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.
CDSX_MODULE Messages
The following are network module messages.
Error Message%CDSX_MODULE-3-CDSX_IPC_CMD_FAIL : IPC Command (message type:[hex], opcode:[hex]) to the firmware Failed on slot([dec]) due to [chars]
Explanation An IPC message could not be sent to the firmware. The firmware is not responding or is responding too slowly. This condition was caused by a full mailbox or a lack of buffers that were available to send the message.
Recommended Action Reset the system board.
Error Message%CDSX_MODULE-3-FDLLLOOPDOWN : Controller [chars] - FDL line loopdown code detected, deactivating line loopback.
Explanation The system has detected FDL line loopdown code on the unit. Line loopback mode is being deactivated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-FDLLLOOPUP : Controller [chars] - FDL line loopup code detected, activating line loopback mode.
Explanation The system has detected FDL line loopup code on the unit. Line loopback mode is being activated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-FDLLREQFAILED : Controller [chars] - Failed to put the remote end in line loopback mode via FDL.
Explanation The T1 FDL line loopup code was sent to the remote end, but the remote end did not activate line loopback mode. This condition could be caused by a problem with the controller configuration or by a physical problem with the line.
Recommended Action Check to verify that the controllers are both operational and enabled (up).
Error Message%CDSX_MODULE-3-FDLLREQOK : Controller [chars] - Remote end is put in line loopback mode via FDL.
Explanation The T1 FDL line loopup code was sent to the remote end from the unit and the remote end has successfully activated line loopback mode.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-FDLPLOOPDOWN : Controller [chars] - FDL payload loopdown code detected, deactivating payload loopback.
Explanation The system has detected FDL payload loopdown code on the unit. The payload loopback mode is being deactivated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-FDLPLOOPUP : Controller [chars] - FDL payload loopup code detected, activating payload loopback mode.
Explanation The system has detected FDL payload loopup code on the unit. The payload loopback mode is being activated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-FDLPREQFAILED : Controller [chars] - Failed to put the remote end in payload loopback mode via FDL.
Explanation The T1 FDL payload loopup code was sent to the remote end, but the remote end did not activate payload loopback. This condition could be caused by a problem with the controller configuration or by a physical problem with the line.
Explanation Check to verify that the controllers are both operational and enabled (up).
Error Message%CDSX_MODULE-3-FDLPREQOK : Controller [chars] - Remote end is put in payload loopback mode via FDL.
Explanation The T1 FDL payload loopup code was sent to the remote end from the unit and the remote end has successfully activated the payload loopback mode.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-IBOCLOOPDOWN : Controller [chars] - IBOC loopdown code detected, deactivating line loopback.
Explanation The system has detected IBOC loopdown code on the unit. Line loopback mode is being deactivated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-IBOCLOOPUP : Controller [chars] - IBOC loopup code detected, activating line loopback mode.
Explanation The system has detected IBOC loopup code on the unit. Line loopback mode is being activated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-IBOCREQFAILED : Controller [chars] - Failed to put the remote end in line loopback mode via IBOC.
Explanation The T1 IBOC loopup code was sent to the remote end, but the remote end did not activate line loopback mode. This condition could be caused by a problem with the controller configuration or by a physical problem with the line.
Explanation Check to verify that the controllers are both operational and enabled (up).
Error Message%CDSX_MODULE-3-IBOCREQOK : Controller [chars] - Remote end is put in line loopback mode via IBOC.
Explanation The T1 IBOC loopup code was sent to the remote end from the unit and the remote end has successfully activated line loopback mode.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-T1REQCANCELLED : Controller [chars] - T1 remote loopback has been cancelled.
Explanation T1 loopdown code has been sent to the remote end from this unit. The remote end is assumed to have received the loopdown code and deactivated loopback mode. However, no test is performed to ensure that the remote end has deactivated loopback mode.
Recommended Action No action is required.
CE3 Messages
The following are CE3 port adapter 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, issue the show tech-support command, contact your Cisco technical support representative, and provide the representative with the gathered information. If possible perform an online insertion and removal. Refer to the Cisco documentation for information on how to perform an online insertion and removal for your platform.
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.
CEIPNM Messages
The following are Circuit Emulation over IP Network Module messages.
Error Message%CEIPNM-2-OIR : Unexpected card type plugged into slot [dec] \n
Explanation An OIR operation has been performed, and the card that was inserted was of an unexpected type.
Recommended Action Insert the correct type of card or reboot the system. No action is required.
Error Message%CEIPNM-2-RESET_FAIL : (sw) slot([dec]) ceipnm reset fail!\n
Explanation The firmware did not correctly boot up correctly after a network module was reset.
Recommended Action Save your router configurations, power down the router, and reboot the system. You may have to reseat the network module in the specified bay. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CEIPNM-1-UNSUPPORTED : \n[chars]\n
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%CEIPNM-5-UPDOWN : cem [dec]/[dec]/[dec], changed state to [chars]
Explanation A configurable interface has changed its state.
Recommended Action No action is required.
Error Message%CEIPNM-2-WATCH_DOG : Got WATCHDOG Interrupt from NM at slot [dec] \n
Explanation A firmware crash has been detected.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
CERF Messages
The following are Cache Error Recovery Function (CERF) messages.
Error Message%CERF-2-ABORT : [chars]
Explanation A cache error has occurred, but an attempt to recover has been aborted.
Recommended Action Enter the more nvram:cerf_report command. 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%CERF-3-RECOVER : [chars]
Explanation The system has fully recovered after a cache error has occurred.
Recommended Action Enter the more nvram:cerf_report command. 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) 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 might 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 might 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 might 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.
CES_CLIENT Messages
The following are circuit emulation service (CES) client messages.
Error Message%CES_CLIENT-4-AVAIL_PORT : No more available CES ports on Card [dec]
Explanation The system is attempting to implement the current configuration. The configuration specifies performance of CES on more ports than are available on this card. All of the CES ports that are present on this card are in use.
Recommended Action Either release some CES ports or add more CES cards.
Error Message%CES_CLIENT-3-INTERNAL_ERR : [chars]
Explanation The CES client 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 might 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.
CES_CONN Messages
The following are messages related to TDM connections in the system.
Error Message%CES_CONN-4-EXCLUSIVE : EITHER CES OR TDM connections possible from port [dec]/[dec].
Explanation The specified port can use either CES connections or TDM Drop and Insert connections but cannot use both types of connections at the same time.
Recommended Action Either remove the TDM connections to support the CES connections or remove the CES connections to support the TDM connections.
Error Message%CES_CONN-3-INVALID_PORT : An invalid ces port for port [dec]/[dec] is passed to driver in ces conn req
Explanation The assigned CES port is invalid. The invalid port was detected during the CES connection setup process for the time slots of a given port.
Recommended Action Check the connection parameters and perform the TDM connection setup and teardown process again. If this message recurs, 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%CES_CONN-4-RESRC_SHORT : Short of resources i.e ces ports to support CES conn from port [dec]/[dec]
Explanation All the CES ports are being used by other T1/E1 ports. CES cannot be performed for the specified port.
Recommended Action Perform one of the following actions to support CES on the specified port: remove CES connections on the other ports, use CES ports that are not used in other NMs, or add more CES-capable NMs.
CFG Messages
The following are messages relating to invalid Cisco 1840 configurations.
Error Message%CFG-3-CARD_NOT_SUPPORTED : Slot [dec]: [chars]
Explanation The specified line card is not recognized by the system.
Recommended Action Replace the line card with a supported line card, or upgrade the software to a Cisco IOS software image that supports this card.
Error Message%CFG-6-ECAN_NEEDS_DSP : PVDM-ECAN requires PVDM-DSP or MS-AIM.
Explanation The echo-cancellation PVDM that is present in the router will not function properly without a PVDM DSP or multiservice AIM module.
Recommended Action Add a PVDM DSP or multiservice AIM module to the system to enable echo cancellation.
Error Message%CFG-6-EXTRA_AIM : AIM-VPN in AIM slot [dec] will be ignored.
Explanation This product supports only one AIM-VPN at a time. Only the first AIM-VPN that was found will be used.
Recommended Action Remove the extra AIM.
Error Message%CFG-6-HWIC_ESW_NO_DCARD : HWIC_ESW in slot [dec] lacks ILP daughtercard.
Explanation This router has an inline power supply that can support inline-powered Ethernet on a HWIC ESW with an ILP daughter card. However, the HWIC ESW line card in the slot specified in the message does not have a daughter card and so cannot support inline-powered Ethernet.
Recommended Action Add an ILP daughter card to the HWIC ESW line card.
Error Message%CFG-6-HWIC_ESW_NO_ILP : Internal inline power supply required to support HWIC_ESW with ILP daughtercard.
Explanation This router contains at least one HWIC ESW with an ILP daughter card. This card can support inline-powered Ethernet if it contains an internal inline power supply. However, the power supply currently present on this router does not provide inline power support.
Recommended Action If you wish to use inline power, replace the power supply in your router with one that can provide inline power.
Error Message%CFG-6-ILP_DEAD : Inline Power Supply module is not working.
Explanation This router has an inline power supply module, but it is not functioning properly. Inline-powered Ethernet will not operate correctly. This condition indicates a defective inline power supply.
Recommended Action Replace the inline power supply.
Error Message%CFG-6-ILP_NO_HWIC_ESW : Inline powered ethernet requires a HWIC_ESW with ILP daughtercard.
Explanation This router contains an inline power supply that can support inline-powered Ethernet on an HWIC ESW with an ILP daughter card. However, no HWIC ESW card with an ILP is present in the router.
Recommended Action To fully utilize the router power supply, install an HWIC ESW card with an ILP daughter card.
Error Message%CFG-6-ILP_NO_PAN : Inline powered ethernet requires a PAN-HWIC with ILP daughtercard.
Explanation This router has an inline power supply that can support inline-powered Ethernet on an HWIC-4ESW or HWICD-9ESW with an inline power daughter card. However, no HWIC-4ESW or HWICD-9ESW card with inline power is present in the router.
Recommended Action Install an HWIC-4ESW or HWICD-9ESW card with an inline power daughter card to fully utilize the power supply of the router.
Error Message%CFG-6-PAN_NO_DCARD : PAN-HWIC in slot [dec] lacks ILP daughtercard.
Explanation This router has an inline power supply that can support inline-powered Ethernet on an HWIC-4ESW or HWICD-9ESW with an inline power daughter card. However, the HWIC-4ESW or HWICD-9ESW card in the slot specified in the message does not have an inline power daughter card and cannot support inline-powered Ethernet.
Recommended Action Add an inline power daughter card to the HWIC-4ESW or HWICD-9ESW.
Error Message%CFG-6-PAN_NO_ILP : Internal inline power supply required to support PAN with ILP daughtercard.
Explanation This router has at least one HWIC-4ESW or HWICD-9ESW with an inline power daughter card. This card can support inline-powered Ethernet if an internal inline power supply is present. However, the power supply currently present on this router does not provide inline power support.
Recommended Action Replace the power supply in your router with one that can provide inline power if inline power support is required.
Error Message%CFG-6-UNKNOWN_AIM : AIM module in AIM slot [dec] is not supported by this IOS image. Card info: [chars].
Explanation The AIM in the specified AIM slot is not recognized or supported by the Cisco IOS software image that is operational on the system.
Recommended Action Either replace the AIM with an AIM that is supported or upgrade to a Cisco IOS software image that supports this AIM.
Error Message%CFG-6-VIC_NEEDS_DSP : Slot [dec]: Voice requires a PVDM-DSP or MS-AIM.
Explanation At least one voice card was found in the router. The voice card will not function properly without a PVDM DSP or a multiservice AIM module.
Recommended Action Add a PVDM DSP or a multiservice AIM module to enable voice capability.
Error Message%CFG-3-WIC_NOT_ALLOWED_IN_VIC_SLOT : Slot [dec]: [chars]
Explanation The WIC that was detected is not supported in the specified slot. Slot 1 supports VICs only.
Recommended Action Move the WIC to another slot that can support it.
CHANNEL_BANK Messages
The following are Channel Bank messages.
Error Message%CHANNEL_BANK-5-UPDOWN : Channel Bank [chars] state is [chars]
Explanation The channel bank status has changed.
Recommended Action Verify that the voice ports in the channel bank are enabled (UP).
CHARLOTTE Messages
The following are Charlotte messages. Charlotte is a dual OC-3 POS port adapter that provides two OC-3 interfaces for the Cisco 7200, Cisco 7300, Cisco 7400, Cisco 7500, and Cisco 7600 router platforms.
Error Message%CHARLOTTE-1-INITFAIL : Failed to initialize port [dec].
Explanation The PA-POS-2OC3 port adapter driver failed to complete its IDB initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHARLOTTE-3-INVALIDPCI : Device reported [hex]
Explanation Hardware initialization of the PA-POS-2OC3 port adapter has failed. The PCI device contains an invalid identifier.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHARLOTTE-1-PCIINITFAIL : PCI initialization failed.
Explanation The PA-POS-2OC3 port adapter driver failed to complete its hardware initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHARLOTTE-3-UNSUPPORTED : [chars]
Explanation The PA-POS-2OC3 port adapter is not supported on this platform. The system log specifies the part of the system that requires an upgrade.
Recommended Action Upgrade your system to a platform that supports the PA-POS-2OC3 port adapter. Refer to the system log to determine what part of your system requires an upgrade.
CHKPT Messages
The following messages support the checkpoint (CHKPT) facility.
Error Message%CHKPT-4-DISABLED : Check Pointing is disabled. Client [chars] should not be calling any CPF API
Explanation The checkpointing feature has been disabled. This condition might be caused by a timing issue.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHKPT-4-DUPID : Duplicate checkpoint client ID ([dec]).
Explanation The checkpoint facility has detected a duplicate checkpoint client ID.
Recommended Action No action is required.
Error Message%CHKPT-3-ILLEGAL : ILLEGAL call to CPF API on ([chars]) by ([chars]).
Explanation A severe error involving a checkpointing operation has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHKPT-4-INVALID : Invalid checkpoint client ID ([dec]).
Explanation The checkpoint facility has detected an invalid checkpoint client ID.
Recommended Action No action is required.
Error Message%CHKPT-3-IPCPORT : Unable to create IPC port on ([chars]).
Explanation The checkpoint facility is unable to create a port for interprocess communication.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHKPT-3-IPCSESSION : Unable to open an IPC session for communicating with ([chars]). rc= [dec]
Explanation The checkpoint facility is unable to open an interprocess communication session.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHKPT-3-NOMEM : Unable allocate resource for CPF on ([chars]).
Explanation A severe error involving a checkpointing operation has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHKPT-3-RFREG : Unable to register checkpoint as client of RF.
Explanation The checkpoint facility is unable to register with the RF as a client.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHKPT-4-SENDFAILED : Checkpointing send failed client ([dec])
Explanation This warning message indicates that the checkpoint facility was unable to send checkpoint information to a client.
Recommended Action No action is necessary.
Error Message%CHKPT-3-TPPORT : Unable to create TP port on ([chars]).
Explanation A severe error involving checkpointing has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHKPT-3-TPSESSION : Unable to open an TP session for communicating with ([chars]). rc= [dec]
Explanation A severe error involving checkpointing has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHKPT-3-UNKNOWNMSG : Unknown message recieved from peer on standby for client ([dec]).
Explanation The checkpoint facility has received an unknown message from a peer. This peer is in standby mode for the client specified in the message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
CHOC12 Messages
The following are CHOC12 port adapter messages.
Error Message%CHOC12-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The CHOC12 RP driver running configuration is corrupt.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show c10k and show ipc status commands to gather data that may provide information to determine the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHOC12-3-ERROR : [chars]
Explanation This message provides general error information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHOC12-1-INITFAIL : Slot [dec]/[dec] init failure ([chars])
Explanation The CHOC12 port adapter has failed to initialize.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHOC12-4-REDINLCEVT : Redundant inactive i/f ([chars]) event: [chars], reason: [chars]
Explanation An internal redundant line card event has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHOC12-1-UNSUPPORTED : [chars]
Explanation The CHOC12 port adapter is not supported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
CHOPIN Messages
The following are Versatile Interface Processor (VIP) Multi-channel Port Adapter 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-BADMSG : Received unexpected mailbox message (id = [dec])
Explanation The mailbox for the Chopin VIP Multichannel Port Adapter has received an unexpected message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADNV : Detected invalid NVRAM size: [dec] bytes
Explanation The detected size of NVRAM is not one of the supported sizes. The NVRAM might 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-2-CHOPINFWCRASHEDINFO : [hex] [hex] [hex] [hex]
Explanation This message provides Chopin VIP Multichannel Port Adapter firmware crash 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%CHOPIN-3-CMDFAIL : [chars] Command Failed at [chars] - line [dec], arg [dec]
Explanation A Chopin VIP Multichannel Port Adapter command error has occurred.
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-CONFIGURE : Fail to configure [dec] interfaces on bay [dec], shutting down bay
Explanation The system could not configure some of the interfaces on the board in the specified bay.
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-DISCOVER : only found [dec] interfaces on bay [dec], shutting down bay
Explanation A hardware failure has occurred on the Chopin VIP Multichannel Port Adapter, or an error of mismatched type has occurred.
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-DWNLDCKSM : Failed for bay [dec], sent = [hex], received = [hex]
Explanation The checksum operation failed during a download of the internal firmware to the Chopin VIP Multichannel Port Adapter. This condition usually indicates a hardware failure.
Recommended Action Perform a power cycle. If the problem persists, the Chopin VIP Multichannel Port Adapter hardware may have failed.
Error Message%CHOPIN-1-DWNLDFAIL : Download failed
Explanation A microcode download to the Chopin VIP Multichannel 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%CHOPIN-3-ERROR : [chars]
Explanation A general error involving the Chopin VIP Multichannel Port Adapter has occurred.
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-FWFATAL : Bay [dec]: firmware needs reset due to [chars]
Explanation The Chopin VIP Multichannel Port Adapter experienced firmware problems.
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-INITFAIL : Slot [dec]: [chars]
Explanation The PRI port adapter 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-LOVEFAIL : [chars]: failed to send [chars] love letter
Explanation The Chopin VIP Multichannel Port Adapter failed to send a "love letter" (operating status or configuration message).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-MBOXRECV : Bay [dec]: fail receiving mbox reply [dec]
Explanation The Chopin VIP Multichannel Port Adapter mailbox failed to receive a mailbox reply.
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-MBOXSEND : Bay [dec]: fail sending mbox msg [dec]
Explanation The Chopin VIP Multichannel Port Adapter mailbox failed to send a mailbox message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-MBOXSENDP : Bay [dec]: fail sending mbox msg [dec] for port [dec]
Explanation The Chopin VIP Multichannel Port Adapter mailbox failed to send a mailbox message for the port specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-MBXREAD : [chars] has stale msg - mbx0:[hex], mbx1:[hex], mbx2:[hex]
Explanation The Chopin VIP Multichannel Port Adapter has not responded to a message within a specified time.
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-3-NOTCHOPIN : Device is not FREEDM - Device reported [hex]
Explanation The Chopin VIP Multichannel Port Adapter hardware has failed. A device that is not a Chopin VIP Multichannel Port Adapter has pointed at the software for the Chopin VIP Multichannel Port Adapter serial 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%CHOPIN-1-NOTCMPLT : Microcode download failed to complete
Explanation The Chopin VIP Multichannel Port Adapter hardware has failed. It could not download its operational microcode.
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-NOTPLX : Device is not PLX 9060 - Device reported [hex]
Explanation An incorrect device has been reported on the Chopin VIP Multichannel Port Adapter.
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-NOTREADY : Not ready for download.
Explanation An error has occurred on the communication path between the driver and the Chopin VIP Multichannel Port Adapter.
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.\n Putting the system in Power save mode and going to rommon.\n Please resolve cooling problem and restart system!\n
Explanation 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-3-OWNERR : serial ([dec]), Buffer ownership error, pak=[hex]
Explanation An internal buffer ownership error has occurred on the Chopin VIP Multichannel Port Adapter.
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-PANIC : Exception [dec], trace [dec]
Explanation The Chopin VIP Multichannel Port Adapter firmware has detected an illegal or unexpected CPU exception or condition. This condition may be caused by a software error or by a 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%CHOPIN-2-POTBADCMD : bad CHOPIN command [dec]
Explanation The Chopin VIP Multichannel Port Adapter received an unsupported 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.
Error Message%CHOPIN-1-STARTFAIL : [chars] channel not enabled;called from function [chars]
Explanation A software or hardware error has occurred. The Chopin VIP Multichannel Port Adapter 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-1-STOPFAIL : [chars] channel not disabled
Explanation The PRI port adapter failed to respond to a request to disable an 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%CHOPIN-3-TOOSMALL : [chars] - packet was less than two bytes
Explanation A packet that is too small (less than two bytes) was 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%CHOPIN-2-TXBADVC : [chars], vc [dec]\n
Explanation The Chopin versatile interface processor multichannel port adapter contains an invalid Tx VC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number of the affected line card, to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show tech-support and show controllers vip slot-number tech-support commands and your pertinent troubleshooting logs.
CHOPIN_MAINBOARD_ASYNC_PQII Messages
The following are Chopin Main Board Asynchronous Driver 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.
CHSTM1 Messages
The following are CHSTM1 messages.
Error Message%CHSTM1-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The running configuration for the CHSTM1 RP driver is corrupt.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show c10k and show ipc status commands to gather data that may provide information to determine the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHSTM1-3-ERROR : [chars]
Explanation This message provides general error information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CHSTM1-1-INITFAIL : Slot [dec]/[dec] init failure ([chars])
Explanation An CHSTM1 initialization failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.