Downloads |
Table Of Contents
System Error Messages for 12.1 T
How to Read System Error Messages
System Error Messages for 12.1 T
This chapter lists and describes the system error messages for Cisco IOS Release 12.1 T, up to and including 12.1(5)T. The system software sends these error messages to the console (and, optionally, to a logging server on another system) during operation. Not all system error messages indicate problems with your system; some are purely informational, while others may help diagnose problems with communications lines, internal hardware, or the system software.
This chapter lists only error messages for Cisco IOS Release 12.1 T that are not documented in the Cisco IOS Release 12.1 Cisco IOS Software System Error Messages manual. For additional system error messages, refer to the Cisco IOS Software System Error Messages manual.
How to Read System Error Messages
The messages are organized according to the particular system facility that produces the messages. The facility sections appear in alphabetical order, and within each facility section, messages are listed alphabetically by mnemonic. Each error message is followed by an explanation and a recommended action.
System error messages begin with a percent sign (%) and are structured as follows:
%FACILITY-SEVERITY-MNEMONIC: Message-textFACILITY is a code consisting of two or more uppercase letters that indicates the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. lists the system facilities codes.
SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. lists the severity levels.
MNEMONIC is a code that uniquely identifies the error message.
Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets (e). A decimal number, for example, is represented as [dec]. lists the representations of variable fields and the type of information in them.
The following is a sample system error message:
%LINK-2-BADVCALL: Interface [chars], undefined entry pointSome error messages also indicate the card and slot reporting the error. These error messages begin with a percent sign (%) and are structured as follows:
%CARD-SEVERITY-MSG:SLOT %FACILITY-SEVERITY-MNEMONIC: Message-textCARD is a code that describes the type of card reporting the error. VIP and FEIP are possible card types.
MSG is a mnemonic that indicates this is a message. It is always shown as MSG.
SLOT indicates the slot number of the card reporting the error. It is shown as SLOT followed by a numeral. (For example, SLOT5.)
Note
The prepended portion of the error message (%CARD-SEVERITY-MSG:SLOT) is not shown in the error message listings in this manual.
Error message severity levels correspond to the keywords assigned by the logging global configuration commands that define where and at what level these messages appear. The default is to log messages to the console at the debugging level (7). For more information, see the system configuration chapter and descriptions of the logging command in the appropriate Cisco IOS configuration guide and command reference publications.
Error Messages
This section lists error messages alphabetically by facility and mnemonic.
Error Message%AAAA-4-DNISGPUNDEF: Warning: DNIS group [chars] is not defined.Explanation The Dialed Number Identification Service (DNIS) group was used without having first been defined.
Recommended Action Define the DNIS group before using it.
Error Message%AAAA-3-DROPACCTLOWMEM: accounting record dropped due to low memory: [chars]-[chars] [chars] [chars], 10*ONESECExplanation An accounting record has been dropped because of a low memory condition.
Recommended Action Disable the periodic accounting feature if it is on. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%AAAA-3-DROPACCTSNDFAIL: accounting record dropped, send to server failed: [chars]-[chars] [chars] [chars], 10*ONESECExplanation An attempt to send an accounting record to the specified server has failed.
Recommended Action Ensure that the TACACS+ or RADIUS server is operational. Next, ensure that the network access server (NAS) is configured properly. Finally, ensure that the NAS can communicate with the server.
Error Message%ACLMERGE-3-CUDDERROR: A CUDD Library error was detected in [chars]Explanation An error was detected by the CUDD library, and the access control list (ACL) merge has failed. The failed ACL merge could cause more traffic to be switched by the software, resulting in lower performance for the interface for which the (ACL) merge had failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information, along with the ACL configuration of this device.
Error Message%ACLMERGE-3-CUDDWARN: A CUDD Library warning message for interest in this event in [chars]Explanation A CUDD library warning message for the specified event has been received.
Recommended Action This is a debug message only. No action is required.
Error Message%ALIGN-3-SPURIOUS: Spurious memory access made at 0x[hex] reading 0x[hex]Explanation An error was identified and temporarily corrected within a software component of the router.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALIGN-3-TRACEX: [chars]Explanation This tracing message provides information about a memory optimization error that involves the Reduced Instruction-Set Computer (RISC) processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALPS-6-CIRCUIT_ASCU_REJECT: Circuit [chars] received a Circuit Open Confirm with a list of rejected ascusExplanation An Airline Protocol Support (ALPS) circuit has sent a Circuit Open Request message and has received a Circuit Open Confirm reply with a list of rejected agent-sent control units (ASCUs).
Recommended Action No action is required.
Error Message%AMD79C971_FE-5-FAILED_SUSPEND: Failed to suspend the amd79c971 chipExplanation An attempt to suspend the AMD Am79C971 chip has filed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AMDP2_FE-6-EXCESSCOLL: [chars] TDR=[dec], TRC=[dec], MSGDEF_LIMIT_SLOWExplanation Ethernet or Fast Ethernet is experiencing multiple collisions. This condition may occur under heavy traffic loads.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-3-TOOMANYPART: Bad packet with [dec] particles, pak=0x[hex]Explanation The software has detected an invalid packet.
Recommended Action Try a later version of the software. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AS5400-1-DFC_ERR: DFC [dec]: Detected PCI [chars] Error, CSR=[hex]Explanation A protocol control information (PCI) error has been detected on the dial feature card (DFC). This error was caused by a hardware failure. The Cisco IOS software will power down this DFC and clean up the associated system data structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AS5400-3-HW_ERROR: NULLExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AS5400-1-OLD_FIRMWARE: [chars]Explanation The specified component should have the latest hardware revision. If the hardware revision is not the latest, it must be updated to the version specified in this message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AS5400-1-UNKNOWN_DFC_INT: Unknown DFC interrupt: DFC slot no [dec], interrupt [dec]Explanation An unknown dial feature card (DFC) interrupt has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AS5400-1-UNKNOWN_INT: Unknown interrupt: interrupt [dec]Explanation The system has detected an unknown interruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ATM-5-UPDOWN: Changing VC [dec]/[dec] VC-state to [chars]Explanation The ATM virtual circuit (VC) has been created, removed, activated, or deactivated.
Recommended Action No action is required if the status change was intended; otherwise, the cause of the status change should be researched. To deactivate or activate the VC, use the shut cli command or the no shut cli command.
Error Message%BGP-3-BGP_INCONSISTENT: [int] Inconsistent [chars], MSGDEF_LIMIT_SLOWExplanation An inconsistency exists in the specified data structures.
Recommended Action The occurrence of data structure inconsistencies is a rare situation and is the result of an internal problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BGP-3-MARTIAN_IP: [int] Martian prefix [chars] in [chars], MSGDEF_LIMIT_SLOWExplanation A nonregistered or ill-formed prefix was found in the Border Gateway Protocol (BGP) message. This error indicates that there is some problem involving the remote router.
Recommended Action Inspect the remote router for problems.
Error Message%BGP-3-NOTIFICATION: [chars] neighbor [IP_address] [dec]/[dec] ([chars]) [dec] bytes [chars]Explanation An error condition in the Border Gateway Protocol (BGP) session has been detected. A notification has been sent or received, and the session will be reset. This message appears only if the log-neighbor-changes command has been configured for the BGP process.
Recommended Action This message represents an error in the session, and its origin should be investigated. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BGP-4-VPNV4NH_IF: Nexthop [IP_address] may not be reachable from neigbor [IP_address] - not a loopbackExplanation A Virtual Private Network Version 4 (VPNv4) route is being sent to this internal BGP (IBGP) neighbor, and the next hop is one of the directly connected physical interfaces. The label for the next-hop address may have been removed in the Multiprotocol Label Switching (MPLS) cloud one hop too soon. Since the P routers do not have Virtual Private Network (VPN) information, they do not know where to forward packets that have the Border Gateway Protocol (BGP) label. This problem could break connectivity between VPN sites.
Recommended Action Use loopback interfaces as the next hop for VPNv4 internal BGP (IBGP) neighbors.
Error Message%BGP-4-VPNV4NH_MASK: Nexthop [IP_address] may not be reachable from neigbor [IP_address] - not /32 maskExplanation A Virtual Private Network Version 4 (VPNv4) route is being sent to the specified internal BGP (IBGP) neighbor, and the next-hop address is a loopback that does not have the IP host mask /32. OSPF is being used on this loopback, and the OSPF network type of this interface is LOOPBACK. OSPF advertises this address as a host route with the IP host mask /32, regardless of what mask is configured. Because this configuration conflicts with Tag Distribution Protocol (TDP), which uses configured masks, the TDP neighbors may not receive a tag for this route. This problem can break connectivity between sites that belong to the same VPN.
Recommended Action Configure the loopback that is used as the next hop with the IP host mask /32.
Error Message%BIT-4-OUTOFRANGE: bit [dec] is not in the expected range of [dec] to [dec]Explanation An invalid request has been detected by the bitlist subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C1700-3-NOCONFIG: Could not download startup configuration from the tftp server.\nExplanation The startup configuration could not be downloaded from the TFTP server. The specified file might not be available, or the server might be unreachable.
Recommended Action Check the file name and availability on the server. Check to see if the network is up and the TFTP server can be reached.
Error Message%C1700-3-TDMMODIFUNKNOWN: TDM Module does not support WAN Interface module [hex] in slot [dec]Explanation The WAN interface card was not recognized by the time-division multiplexing (TDM) module. The internal connections that are required for this WAN interface card to function have not been configured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700-5-WRITEMEM: NVRAM configuration is not supported.\nExplanation The startup configuration could not be stored in NVRAM. It is stored in the SBC.
Recommended Action The startup configuration is automatically saved by the management application. It can also be saved by copying the running configuration to a server using FTP.
Error Message%C4GWY_DSPRM-5-DSPFAIL: DSP [dec] is in the failed stateExplanation The Digital Signal Processor (DSP) has entered the FAILED state because of alarm indications.
Recommended Action Replace the DSP resource.
Error Message%C4GWY_DSPRM-5-DSPNOTPRESENT: DSP [dec] is not presentExplanation All four hardware Digital Signal Processor (DSP) SIMMs were unavailable.
Recommended Action Reinstall all four hardware DSP SIMMs.
Error Message%C4GWY_DSPRM-3-INSUFFICIENT: Insufficient DSP resources for timeslot [dec] on port [chars]Explanation The configuration requires more Digital Signal Processor (DSP) resources than are available.
Recommended Action Change the configuration to specify fewer used time slots. Install additional DSP resources to allow for more complex configurations.
Error Message%C4GWY_DSPRM-5-KEEPALIVE: DSP [dec] in slot [chars], NOT RESPONDING - auto restart([dec] times)Explanation The Digital Signal Processor (DSP) has failed the background keepalive test.
Recommended Action No action is required.
Error Message%C4GWY_DSPRM-5-SETCODEC: Configured codec [dec] is not supported with this dsp image.Explanation The codec negotiation has failed.
Recommended Action No action is required.
Error Message%C4GWY_DSPRM-5-UPDOWN: DSP [dec], changed state to [chars]Explanation The Digital Signal Processor (DSP) resource has changed state.
Recommended Action No action is required.
Error Message%C6KENV-4-CLOCKFAILED: clock [dec] failedExplanation The indicated clock has failed. The system will continue to operate using the redundant clock.
Recommended Action Replace the failed clock.
Error Message%C6KENV-0-CLOCKMAJFAILED: too many clocks failed to continue system operationExplanation The system requires at least one clock to operate. Because there are no are operational clocks, no packets can be forwarded.
Recommended Action Replace the clocks, backplane, or chassis.
Error Message%C6KENV-2-CLOCKMAJRECOVERED: enough clocks operational to continue system operationExplanation The system can continue to operate using the recovered clock.
Recommended Action No action is required.
Error Message%C6KENV-4-CLOCKOK: clock [dec] operationalExplanation A previously failed clock has declared itself operational.
Recommended Action No action is required.
Error Message%C6KENV-4-FANTRAYFAILED: fan tray failedExplanation One or more fans in the system fan tray have failed. Although this is a minor problem, the system components may overheat and be shut down.
Recommended Action Replace the failed fan as soon as possible.
Error Message%C6KENV-4-FANTRAYOK: fan tray OKExplanation All fans in the system fan tray are operating.
Recommended Action No action is required.
Error Message%C6KENV-2-MAJORTEMPALARM: [chars] has exceeded allowed operating temperature range.Explanation Because the temperature of a component has exceeded the allowable range, the component will be powered off. For shared components, you must power off the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6KENV-4-MAJORTEMPALARMRECOVER: [chars] has returned to allowed operating temperature range.Explanation Because the specified component has returned to a temperature within the allowed range, the scheduled shutdown has been canceled, and the system will continue to operate.
Recommended Action No action is required.
Error Message%C6KENV-4-MINORTEMPALARM: [chars] has exceeded normal operating temperature range.Explanation This message may indicate a developing temperature problem for the component, and also a problem for other components in the system.
Recommended Action Inspect the indicated component closely to determine why it is operating out of the normal operating temperature range, and whether it will eventually exceed the allowed operating temperature range.
Error Message%C6KENV-4-MINORTEMPALARMRECOVER: [chars] has returned to normal operating temperature range.Explanation This message indicates a resolved temperature problem for the specified component.
Recommended Action No action is required.
Error Message%C6KENV-4-PSFANFAILED: the fan in power supply [dec] has failedExplanation The fan in the specified power supply has failed. The failed fan may cause the power supply to overheat and be shut down.
Recommended Action Replace the fan in the power supply as soon as possible.
Error Message%C6KENV-4-PSFANOK: the fan in power supply [dec] is OKExplanation The fan in the specified power supply is operating.
Recommended Action No action is required.
Error Message%C6KENV-2-SHUTDOWN: shutdown [chars] now because of [chars].Explanation The indicated component has been shut down.
Recommended Action Replace the component as soon as possible.
Error Message%C6KENV-2-SHUTDOWN_CANCELLED: shutdown for [chars] cancelledExplanation The problem that caused the shutdown to be scheduled has been resolved, and the shutdown has been canceled.
Recommended Action No action is required.
Error Message%C6KENV-1-SHUTDOWN_DISABLED: need to shutdown [chars] now but shutdown action is disabled!Explanation A shutdown action that had been set by a user has been disabled, and the system could not shut down the specified component.
Recommended Action Manually shut down or remove the indicated component immediately.
Error Message%C6KENV-2-SHUTDOWN_SCHEDULED: shutdown for [chars] scheduled in [dec] secondsExplanation A major alarm condition will be corrected by shutting down the affected component.
Recommended Action Replace the component as soon as possible.
Error Message%C6KENV-4-VTTFAILED: VTT [dec] failedExplanation The specified voltage termination (VTT) or the chassis has failed.
Recommended Action Replace the specified VTT or the chassis as soon as possible.
Error Message%C6KENV-0-VTTMAJFAILED: Too many VTT failures to continue system operationExplanation The Cisco Catalyst 6000 backplane data bus cannot operate without the proper termination that is normally provided by the voltage termination (VTTs).
Recommended Action Replace the failed VTTs.
Error Message%C6KENV-2-VTTMAJRECOVERED: enough VTTs operational to continue system operationExplanation Although there are some failed voltage terminations (VTTs), the system is operating.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C6KENV-4-VTTOK: VTT [dec] operationalExplanation The specified voltage termination (VTT) is operational.
Recommended Action No action is required.
Error Message%C6KPWR-4-COULDNOTREPOWER: wanted to re-power FRU (slot [dec]) but could not.Explanation An attempt to restart the module in the specified slot has failed.
Recommended Action The process for recovery of the module will depend upon the indicated reason. If you need assistance, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C6KPWR-4-DISABLED: power to module in slot [dec] set [chars]Explanation The module in the specified slot was powered off for the indicated reason.
Recommended Action The process for recovery of the module will depend upon the indicated reason. If you need assistance, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C6KPWR-4-ENABLED: power to module in slot [dec] set onExplanation The module in the indicated slot has been powered up.
Recommended Action No action is required.
Error Message%C6MSFC-4-BADFLASH: Unsupported flash type in the bootflash - [chars].Explanation The flash chips in the Flash SIMM are not supported by the platform.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message%C6MSFC-3-CHASSIS: Unknown chassis model.Explanation The data stored in the CPU IDPROM is corrupt or incomplete.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message%C6MSFC-4-MACBLKSIZE: Unknown MAC address block size.Explanation The data stored in the CPU IDPROM is corrupt or incomplete.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message%C6SUP-3-NOVLANMAC: Can't allocate MAC address for VLAN interface [int]Explanation The MAC address allocation failed because the number of VLAN interfaces exceeds the number of VLAN interfaces provided for by the chassis.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CALL_MGMT-4-CALL_DISC: [chars]Explanation The specific message text is supplied by the Call Management software. This message 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CALLPROG-3-API_INIT: api front init failed for [chars]Explanation The Call Progress Notification support structures could not be initialized for the indicated Application Programming Interfaces (APIs) because the system does not have sufficient memory.
Recommended Action 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 has failed to retrieve a free element from the front-end queue. The platform requires additional free elements in order to function properly.
Recommended Action Stop using the Call Progress Notification applications. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CALLRECORD-6-MICA_TERSE_CALL_FAILED_REC: [chars]Explanation A Terse MICA Call Failed Record has been received.
Recommended Action No action is required.
Error Message%CALLRECORD-6-MICA_TERSE_CALL_REC: [chars]Explanation A Terse MICA Call Failed Record has been received.
Recommended Action No action is required.
Error Message%CALLTRKR-3-CALL_REC_ERROR: [chars]Explanation A generated record has exceeded the capability of the system log.
Recommended Action No action is required.
Error Message%CALLTRKR-6-CALL_RECORD: [chars]Explanation Terse Call Tracker Call Record has been received.
Recommended Action No action is required.
Error Message%CALLTRKR-6-MODEM_CALL_REC: [chars]Explanation A Modem Verbose Call Tracker Call Record has been received.
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 been received.
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 been received.
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 been received.
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 memory could be allocated for the task.
Recommended Action Disable Call Tracker by entering the no calltracker enable command. Enter the show memory command to find out where the memory has been allocated.
Error Message%CALLTRKR-3-PRINT_BUFFER: calltrkr cli print buffer [chars]Explanation The Call Tracker CLI (command-line interface) internal print buffer has overflowed.
Recommended Action Stop entering calltracker show commands. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CALLTRKR-3-PROC: can't spawn [chars]Explanation The Call Tracker process could not be spawned.
Recommended Action Disable Call Tracker by entering the no calltracker enable command. Then reenable it. If the error persists, contact your Cisco technical support representative.
Error Message%CALLTRKR-3-TBL_INIT: Init of CT's [chars] table failed; CT unusableExplanation The Call Tracker record table could not be initialized.
Recommended Action Disable Call Tracker by entering the no calltracker enable command. Then reenable it. If the error persists, contact your Cisco technical support representative.
Error Message%CARRIER-2-CT3_8PRI_MIX: Cannot mix 8PRI and CT3 DFC in chassis, do not power up invalid card in slot [dec]Explanation The user has placed 8PRI and CT3 dial feature cards (DFCs) in the same chassis. You cannot mix 8PRI and CT3 DFC card types in the same chassis.
Recommended Action Remove the extra 8PRI or CT3 DFC card.
Error Message%CARRIER-3-DFC_INIT_ALREADY: DFC is already initialized - DFC [dec]Explanation The dial feature card (DFC) has already been 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, call 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 The dial feature card (DFC) initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-DFC_POWER_INT: DFC Power Changed - DFC [dec]Explanation The dial feature card (DFC) power is fluctuating.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-INVALID_DFC: Invalid DFC - DFC [dec] type [dec]Explanation The dial feature card (DFC) has an invalid board ID or type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-NO_DFC: DFC is not present - DFC [dec]Explanation The dial feature card (DFC) is not present in the carrier card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 The dial feature card (DFC) carrier platform initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-POWER_DFC: DFC Power-On Failed - DFC [dec]Explanation The dial feature card (DFC) power-on has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-3-RESET_DFC: DFC Reset Failed - DFC [dec]Explanation During the online insertion and removal (OIR) process, the dial feature card (DFC) reset failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-2-T1_E1_MIX: Cannot mix T1 and E1 8PRI DFC cards in chassis, do not power up invalid card in slot [dec]\nExplanation The user has put T1 and E1 8PRI dial feature card (DFC) cards in the same chassis.
Recommended Action Remove the extra T1 or E1 8PRI DFC card.
Error Message%CARRIER-2-THREE_NP108_NOT_PRESENT: 3 NP108s were not found on Tetryl card, [dec] detected.Explanation Fewer than three NP108s have been found on a tetryl card. A tetryl card requires three NP108s.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CARRIER-2-TOOMANY_8PRI: Too many 8PRI DFC cards, do not power up invalid card in slot [dec]Explanation The user has placed too many 8PRI dial feature cards (DFCs) in the chassis.
Recommended Action Remove the extra 8PRI DFC cards.
Error Message%CARRIER-2-TOOMANY_CT3: Too many CT3 DFC cards, do not power up invalid card in slot [dec]Explanation The user has placed too many CT3 dial feature cards (DFCs) in the chassis.
Recommended Action Remove the extra CT3 DFC cards. If the problem persists, also check the 8PRI DFC cards.
Error Message%CASA-4-WARNING: Unexpected condition: [chars]Explanation An unexpected condition was detected by the system while it was performing a Content Aware Services Architecture (CASA) operation.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CBUS-4-FIXBADTXVC: Detected and fixed bad tx vc encap on [chars], bad vc [dec], fixed vc [dec], ONEMINExplanation A transmit packet on a channelized serial interface does not have a virtual circuit (VC) number encapsulation.
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-3-TXVCENCAPFAIL: Detected bad tx vc encap on [chars], vc [dec]. Board encap failed [hex], [hex], [hex], ONEMINExplanation Board encapsulation has failed on a transmit packet on a channelized serial interface that does not have the required virtual circuit (VC) number encapsulation.
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%CCH323-2-E164_LENGTH_IS_NOT_SUPPORTED: [chars]: E164 address length [dec] is not supportedExplanation An E164 address with a length that is not supported has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADADDR: chopin_little_endian_addr: Attempted conversion of invalid address ([hex])Explanation A software error occurred while the software was trying to determine protocol control information (PCI) device addressing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADADDR2: chopin_big_endian_addr: Attempted conversion of invalid address ([hex])Explanation A software error occurred while the software was trying to determine protocol control information (PCI) device addressing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADBAYDEV: get_pci_dev_num: Invalid bay ([dec]) or device number offset ([dec])Explanation A software error occurred while the software was trying to determine protocol control information (PCI) device addressing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADDEVNO: pas_get_device_subunit: Invalid PCI device number: [dec]Explanation A software error occurred while the software was trying to determine protocol control information (PCI) device addressing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADNV: Detected invalid NVRAM size: [dec] bytesExplanation The detected size of NVRAM is not one of the supported sizes. The NVRAM may be defective.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADPA: Invalid Port Adaptor type ([dec]) reported for mainboardExplanation The virtual port adapter type derived from the mainboard type is not one of the supported types. It is possible that the mainboard is of a new mainboard type and that the software release you are 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, call 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 protocol control information (PCI) bus configuration read cycle has failed. The mainboard must be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-BADPCIWR: PCI Configuration Write Cycle Failed for bus [dec], Device [dec], function [dec], register [dec]Explanation A protocol control information (PCI) bus configuration write cycle has failed. The mainboard must be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-INITFAIL: CHOPIN (bay [dec]), Init Failed at [chars] - line [dec] arg [hex]Explanation The port adapter has failed to complete hardware initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-NOMAC: Can't allocate MAC address for interface [int]/[int]Explanation An attempt to allocate a MAC address for the specified interface has failed because all the 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-6-NOTDMBP: No TDM backplane is supported on slot [dec].Explanation The DS0 inter slot cannot be cross-connected without the time-division multiplexing (TDM) backplane.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-6-NOTSUPPORT: Voice PA is not supported in this platform.Explanation The specified port adapter is not supported on this platform.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 errorExplanation The password protection feature has failed to erase the configuration because of an internal error.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-1-OVERTEMP: System detected OVERTEMPERATURE condition. Putting the system in Power save mode and going to rommon. Please resolve cooling problem and restart systemExplanation The environmental monitor has detected a high-temperature condition.
Recommended Action Ensure 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 the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-6-RXDFILLFAIL: CHOPIN (bay [dec]), Data rx ring refill failed: rxd_fill_fail=[dec]Explanation The port adapter has failed to refill the data RX ring.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-6-RXVFILLFAIL: CHOPIN (bay [dec]), Voice rx ring refill failed: rxv_fill_fail=[dec]Explanation The port adapter has failed to refill the voice RX ring.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-1-STARTFAIL: [chars] channel not enabledExplanation A software or hardware error has occurred. The serial interface for the port adapter is not responding to commands used to initialize it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-TDMFAIL: CHOPIN-TDM, access failed at [chars] - line [dec], arg1=[dec],arg2=[dec]Explanation The port adapter has failed to access the time-division multiplexing (TDM) switch.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-TSBUSY: CHOPIN (bay [dec]), TDM timeslot is busy: ST=[dec]/TS=[dec]Explanation The port adapter has failed to grant a cross-connect setup request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-TSNONBUSY: CHOPIN (bay [dec]), TDM timeslot is non busy: ST=[dec]/TS=[dec]Explanation The port adapter has failed to grant a cross-connect teardown request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-5-TXVFULL: CHOPIN (bay [dec]), Voice tx ring is full: dma_done=[dec], last_dma_done=[dec]Explanation The voice TX ring of the port adapter is full.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN-3-UNEXPEVENT: CHOPIN (bay [dec]), received an unexpected event=[hex]Explanation The port adapter has received an unexpected event from firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CHOPIN_MAINBOARD_ASYNC_PQII-3-NOMEMORY: No memory for [chars] of unit [dec]Explanation The router does not have enough memory to perform the specified function.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CMAPP-6-PROCESS_CREATION_FAILED: Cannot create Call Manager Application process\nExplanation The Call Manager Application process could not be created.
Recommended Action Ensure that there is adequate free memory.
Error Message%CCH323-2-E164_LENGTH_IS_NOT_SUPPORTED: [chars]: E164 address length [dec] is not supportedExplanation An E164 address with a length that is not supported has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CMCC-3-IPCBUFFAIL: Unable to obtain IPC resourcesExplanation The interprocess communication (IPC) service used by the TN3270 server on the Cisco Mainframe Channel Connection (CMCC) interfaces has failed to obtain a buffer.
Recommended Action The CMCC will not load properly. Try the reload command again. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CMCC-3-IPCDNSFAIL: DNS lookup failed - [chars]Explanation The interprocess communication (IPC) service used by the TN3270 server on the Cisco Mainframe Channel Connection (CMCC) interfaces has experienced a Domain Name System (DNS) lookup failure.
Recommended Action Ensure that the proper revisions of code have been selected.
Error Message%CMCC-4-IPCDNSNOIPADDR: DNS lookup failed - the DNS server has no entry for hostname [chars]Explanation The InterProcess Communication (IPC) service used by the TN3270 Server on the Cisco Mainframe Channel Connection (CMCC) interfaces has experienced a DNS lookup failure.
Recommended Action Ensure that the DNS server entries are current.
Error Message%CMCC-5-IPCDNSQUERYTIMEDOUT: DNS lookup failed - query to DNS server [IP_address] timed outExplanation The interprocess communication (IPC) service used by the TN3270 server on the Cisco Mainframe Channel Connection (CMCC) interfaces has experienced a Domain Name System (DNS) lookup failure.
Recommended Action Check the status of the DNS server.
Error Message%CMCC-5-IPCDNSSERVERUNREACHABLE: DNS lookup failed - DNS server [IP_address] is unreachableExplanation The interprocess communication (IPC) service used by the TN3270 server on the Cisco Mainframe Channel Connection (CMCC) interfaces has experienced a Domain Name System (DNS) lookup failure.
Recommended Action Check for available routes to the Domain Name System (DNS) servers.
Error Message%CMCC-3-IPCINITFAIL: Unable to initialize IPC [chars] servicesExplanation The interprocess communication (IPC) service used by the TN3270 server on the Cisco Mainframe Channel Connection (CMCC) interfaces has failed to initialize.
Recommended Action The CMCC will not load properly. The router must be reloaded to resolve the problem.
Error Message%CMCC-3-IPCINVALID: Invalid IPC request ([dec]) received from ([hex])Explanation The interprocess communication (IPC) service used by the TN3270 server on the Cisco Mainframe Channel Connection (CMCC) interfaces has received an invalid message.
Recommended Action Ensure that the proper revisions of code have been selected.
Error Message%CM_MONITOR-5-DNS_KILL: Terminating DNS processExplanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CM_MONITOR-5-DNS_RESP: Sending DNS response to [int] (request was for [int])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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CM_MONITOR-5-DNS_START: Starting DNS processExplanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CRYPTO-3-CERTCHECK: Certificates with invalid status have been detected!!!Explanation A check of the certificates saved in the memory against the certificate revocation list (CRL) revealed that some certificates were detected as having invalid status.
Recommended Action Check the status, and contact the certification authority (CA) administrator. Enrollment may be required.
Error Message%CRYPTO-6-CERTPENDING: Enter manual authentication ...Explanation The certification authority (CA) server has attempted to process a manual authentication to the router.
Recommended Action Follow a manual authentication procedure.
Error Message%CRYPTO-3-GETCACERT: Failed to find CA cert in memory.Explanation The certification authority (CA) certificate was not located in memory.
Recommended Action Check the status and contact the CA administrator.
Error Message%CRYPTO-3-GETCARACERT: Failed to receive RA/CA certificates.Explanation A failure was encountered when certification authority (CA) or registration authority (RA) certificates were parsed and processed.
Recommended Action Check the status and contact the CA administrator.
Error Message%CRYPTO-6-GETCERTINITIAL: Certificate enrollment failed in manual modeExplanation The current certificate enrollment has failed in manual mode.
Recommended Action Contact the certification authority (CA) administrator.
Error Message%CRYPTO-3-GETCRL: Query the Certificate Revocation List from CA failedExplanation The attempt to query the certificate revocation list from the certification authority (CA) server has failed. Several reasons are possible.
Recommended Action Contact the CA administrator.
Error Message%CRYPTO-3-IKEINIT: [chars]Explanation An Internet Key Exchange (IKE) initialization error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CRYPTO-6-IKE_TED_BAD_REPLY: Received TED reply that did not correspond to a TED probe, MSGDEF_LIMIT_GLACIALExplanation The received Tunnel Endpoint Discovery (TED) reply does not match the TED probe that is currently outstanding. This error might be a one-time occurrence caused by delay of the TED reply. This error might also be caused by ill-formed packets that were sent by the peer. Ill-formed packets sent by the peer may be a hostile event.
Recommended Action If the problem occurs more than once, contact the administrator of the peer.
Error Message%CRYPTO-4-IKMP_NO_SA: IKE message from %15i has no SA and is not an initialization offerExplanation Internet Key Exchange (IKE) maintains state for a communication in the form of security associations. No security association exists for this packet, and it is not an initial offer from the peer to establish one. This situation could signify a denial-of-service attack.
Recommended Action Contact the remote peer and the administrator of the remote peer.
Error Message%CRYPTO-6-ISAKMP_MANUAL_DELETE: IKE SA manually deleted. Do 'clear crypto sa peer [IP_address]' to manually clear IPSec SA's covered by this IKE SA.Explanation The Internet Key Exchange (IKE) security association (SA) was deleted by a user command. However, keepalives for this connection are enabled, and IP Security (IPSec) Source-Actives (SAs) that have been covered by this IKE SA still exist. Since this IKE SA is now deleted, these IPSec SAs have no IKE SA supporting them.
Recommended Action Use the parser command to manually delete the IP Security (IPSec) Source-Actives (SAs).
Error Message%CRYPTO-6-RANDOM: A pseudo-random number was generated twice in succession, 10*ONESECExplanation A pseudorandom number generator produced the same number twice in succession.
Recommended Action Under normal circumstances, it is not a problem if a pseudorandom number generator occasionally produces the same number twice in succession. If this message occurs frequently, manually reload the system. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your Cisco technical support representative.
Error Message%CRYPTO-0-SELF_TEST_FAILURE: Encryption self-test failed ([chars])Explanation One of the encryption self-tests has failed. The encryption engine is not operable in this state.
Recommended Action If the failure persists, contact Cisco to obtain a replacement Cisco IOS image.
Error Message%CRYPTO-3-SOCKETSELECT: Failed to select the socketExplanation A socket selection has caused a failure.
Recommended Action Check the TCP or socket debugging message.
Error Message%CTRC-3-NOBUFFS: No buffers available to [chars]Explanation (Cisco IOS Release 12.1(3)T message) Cisco Transaction Connection (CTRC) failed to allocate a buffer while performing the operation described in the message text. The buffer pool does not contain enough items to fulfill the allocation request. The failed buffer allocation request occurs most commonly when a public buffer pool runs out of elements.
Recommended Action Determine which pool has run out of buffers by entering the show buffers command. Adjust the pool size using the buffers configuration command.
Error Message%CTRC-3-NOBUFFS: No buffers available to [chars], MSGDEF_LIMIT_FASTExplanation Cisco Transaction Connection (CTRC) failed to allocate a buffer while performing the operation described in the message text. The buffer pool does not contain enough items to fulfill the allocation request. The failed buffer allocation request occurs most commonly when a public buffer pool runs out of elements.
Recommended Action Determine which pool has run out of buffers by entering the show buffers command. Adjust the pool size using the buffers configuration command.
Error Message%CWAN_ATM-3-BADMAC: Broadcast MAC on [chars] subnetExplanation A packet with an unexpected MAC address from the backplane has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_ATM-3-MCAST_VC_ERR: Multiple IP Multicast addrs assigned to VC [hex]Explanation A multicast MPT virtual circuit was already in use and had been assigned to another multicast group.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_ATM-3-NONDATAVC: Ethernet data frame received on non-data VCExplanation A data packet for a control virtual circuit has been received from the backplane.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC-4-BUSSTALL: Constellation BUS Stall detectedExplanation A stall has been detected on the Constellation bus. The stall may have been caused by some online insertion and removal (OIR) activity on the bus.
Recommended Action No action is required.
Error Message%CWANLC-3-IPCALLOCFAIL: Failed to allocate IPC buffer [chars]Explanation The line card has failed to allocate a buffer for communication with the Multilayer Switch Feature Card (MSFC) Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC-3-IPCPORTFAIL: Failed to open IPC port '[chars]' [chars]Explanation The line card has failed to open a port for communication with the Route Processor Multilayer of the Switch Feature Card (MSFC).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC-3-IPCSENDFAIL: Failed to send IPC message [chars]Explanation The line card has failed to send a message to the Multilayer Switch Feature Card (MSFC) Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC-4-LOGMSGTOOBIG: Logger message length exceeds max, [int] bytesExplanation The line card has attempted to send a large message to the Multilayer Switch Feature Card (MSFC) Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC-3-LONGSTALL: Long bus stall ([int] ms), check for improperly seated cardsExplanation This message indicates that a stall was detected, but the backplane stall was longer than expected.
Recommended Action Ensure that all cards are firmly seated. A recurring problem may indicate a hardware failure.
Error Message%CWANLC-2-PCIERROR: Fatal PCI Error [chars] seen on PCI Bus [dec]Explanation A fatal protocol control information (PCI) error has been detected on the PCI bus. This PCI error is probably caused by a hardware problem.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC_ATM-3-CMDERR: ([dec]/[dec]) Interface ([chars]): [chars] IPC command fails (cause: [hex])Explanation The ATM Route Processor (RP) driver has experienced an IPC command error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC_ATM-3-EVENT: ([dec]/[dec]) Interface ([chars]): unknown IPC event ([int]) from linecardExplanation The ATM Route Processor (RP) driver has received an unknown event from the line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC_ATM-4-HIRATE: ([dec]/[dec]) Interface ([chars]): SAR limits VBR VC PCR to [dec] kbps, opening UBR VC insteadExplanation The segmentation and reassembly (SAR) limits the VBR VC PCR to one-half of the bandwidth of the link.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC_ATM-3-INIT: ATM driver ([int]/[int]) initialization [chars].Explanation The ATM Route Processor (RP) driver has experienced a software initialization error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC_ATM-4-UNSUP: ([dec]/[dec]) Interface ([chars]): unsupported feature: [chars]Explanation This feature is not supported by the ATM Route Processor (RP).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWANLC_ATM-3-VCENCTYPE: ([dec]/[dec]) VC:[int] unknown VC encapsulation type ([int])Explanation The ATM Route Processor (RP) driver has experienced an unknown VC encapsulation software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-BAD_IFCOMTYPE: Bad ifcom message type=[int]Explanation A line card has forwarded a message that the Draco software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-BOOTFAIL: The CWAN-LC in slot [int]/[int] failed to bootExplanation The line card that was booting either has reset or has failed.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-6-CARDRELOAD: Card reloaded on slot [int]/[int]Explanation A Find Master System Control Protocol (SCP) message has been recovered on the Route Processor (RP). The line card was either inserted or reset from the Network Management Processor (NMP). The inserted interface will be shut down until it is configured by the user or, if an interface of the same type was previously configured, it will be restored to its previous state.
Recommended Action No action is required.
Error Message%CWAN_RP-3-ERROR: NULLExplanation This message provides information about the specified software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-FOREVER: cmd [int] to [chars] (slot [int]/[int]) took [int] usecs, done [hex]Explanation A call control block (CCB) command from Draco to a line card took longer than expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-HV_ALLOCFAIL: Draco failed to allocate a VLAN for a WAN interface, status=[int]Explanation The Network Management Processor (NMP) has returned a failure for the VLAN allocation request.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-6-IMAGE_UPGRADE: Bootflash image upgrade [chars] for slot [int]/[int][chars]Explanation The bootflash image on the Constellation WAN (CWAN) line card has been automatically upgraded.
Recommended Action No action is required.
Error Message%CWAN_RP-3-IPCALLOCFAIL: Failed to allocate IPC buffer [chars]Explanation The Draco software has failed to allocate a buffer for communication with a line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-IPCPORTFAIL: Failed to open IPC port '[chars]' [chars]Explanation The Draco software has failed to open a port for communication with a line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-IPCSENDFAIL: Failed to send IPC message [chars]Explanation The Draco software has failed to send a message to a line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-KEEPFAIL: The CWAN-LC in slot [int]/[int] is not responding to keepalivesExplanation The line card either has been reset or has failed.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-LC_CRASHINFO: The CWAN_LC in slot [int]/[int] copied [chars] on to RP bootflashExplanation The line card has failed.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-LCLOG_BADSEV: Linecard [int]/[int] invalid message severity [int]Explanation The line card has forwarded a logger message with invalid severity that the Multilayer Switch Feature Card (MSFC) Route Processor cannot process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-4-LCLOG_TOOLONG: Linecard [int]/[int] message too long, [int] bytesExplanation The line card has forwarded a logger message that is too long for the Multilayer Switch Feature Card (MSFC) Route Processor Multilayer Switch Feature Card (MSFC) to process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-6-LC_PRESENT: [chars] in slot [int]Explanation A Constellation WAN (CWAN) line card has been detected by the hardware.
Recommended Action No action is required.
Error Message%CWAN_RP-6-QUIESCE_FAIL: Quiesce failed for slot [int]/[int]Explanation The Draco software has failed to contact the Constellation WAN (CWAN) line card during the specified failure, and the line card will be reset.
Recommended Action No action is required.
Error Message%CWAN_RP-3-RESET_FAIL: The CWAN-LC in slot [int] failed even after several resetsExplanation The specified line card has failed.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWAN_RP-3-SCPALLOCFAIL: Failed to allocate SCP packet [chars]Explanation The Draco software has failed to allocate a packet for communication with other slots in the chassis.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-BAD_IFCOMTYPE: Bad ifcom message type=[int]Explanation The Multilayer Switch Feature Card (MSFC) Route Processor has forwarded a message that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-BADMALUCMD: Unsupported MALU command [dec], arg=[hex], pascb=[hex]Explanation The Multilayer Switch Feature Card (MSFC) Route Processor has forwarded a command that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-BADMALUCMD2: CWPA([int]): Unsupported MALU cmd/arg0=[hex][hex], arg1arg2=[hex][hex], pascb=[hex]Explanation The Multilayer Switch Feature Card (MSFC) Route Processor has forwarded a command that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-CMDNOPASCB: PASCB Null for command [dec], arg=[hex]Explanation The Multilayer Switch Feature Card (MSFC) Route Processor passed down a command that the software was unprepared to handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-IPCALLOCFAIL: Failed to allocate IPC buffer [chars]Explanation The line card has failed to allocate a buffer for communication with the Multilayer Switch Feature Card (MSFC) Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-IPCSENDFAIL: Failed to send IPC message [chars]Explanation The line card has failed to send a message to the Multilayer Switch Feature Card (MSFC) Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-LVLTRTOOBIG: Loveletter length exceeds max, [int] bytesExplanation The line card has attempted to send a large message that exceeded the maximum allowed length to the Multilayer Switch Feature Card (MSFC) Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWPA-3-NODISPATCH: Dispatch vector Null, cmd=[dec], dintf=[dec]Explanation No command dispatch vector has been found for the specified interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-BAD_IFCOMTYPE: Bad ifcom message type=[int]Explanation The Multilayer Switch Feature Card (MSFC) Route Processor has forwarded a message that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-BADINT: Attempted to access HWIDB for port [int]Explanation The line card has attempted to access an HWIDB value that is associated with a port that does not exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-BADINTCREATE: Attempted to install HWIDB for port [int]Explanation The line card has failed to install an HWIDB value because the associated port number was out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-BADMALUCMD: Unsupported MALU command [dec], arg=[hex], pascb=[hex]Explanation The Multilayer Switch Feature Card (MSFC) Route Processor has forwarded a command that the software was not prepared to handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-BADMALUCMD2: Unsupported MALU cmd/arg0=[hex][hex], arg1arg2=[hex][hex], hwidb=[chars]Explanation The Multilayer Switch Feature Card (MSFC) Route Processor has forwarded a command that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-CMDNOINT: HWIDB Null for command [dec], arg=[hex]Explanation The Multilayer Switch Feature Card (MSFC) Route Processor has forwarded a command that the software could not process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-IPCALLOCFAIL: Failed to allocate IPC buffer [chars]Explanation The line card has failed to allocate a buffer for communication with the Multilayer Switch Feature Card (MSFC) Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-IPCSENDFAIL: Failed to send IPC message [chars]Explanation The line card has failed to send a message to the Multilayer Switch Feature Card (MSFC) Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-LVLTRTOOBIG: Loveletter length exceeds max, [int] bytesExplanation The line card has attempted to send a large message that exceeds the maximum allowed length to the Multilayer Switch Feature Card (MSFC) Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-NODISPATCH: Dispatch vector Null, cmd=[dec], dintf=[dec]Explanation No command dispatch vector has been found for the specified interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-3-VAERROR: Error on Van Allen [dec]Explanation An error has been detected on one of the Constellation Switching Bus ASICs that are located on the line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC-2-VAFATAL: Fatal Error on Van Allen [dec]Explanation A fatal error has been detected one of the Constellation Switching Bus ASICs.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%CWTLC_ATM-3-CMD_ACK: ATM (port [dec]): Cmd ack problem: [chars]Explanation An error has occurred during an attempted communication with segmentation and reassembly (SAR).
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DBUS-3-PERMANENT_WEDGED: Line card in slot [dec] is permanently wedgedExplanation Two successive attempts to restart and analyze the line card have failed.
Recommended Action Reinstall the line card. This condition could be caused by bad VIP hardware. If the condition persists, 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/cgi-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%DFC-1-DFC_BAD_DFC_TYPE: DFC in slot [dec] has incorrect board id of [dec]Explanation A dial feature card (DFC) board does not have a correct board ID.
Recommended Action Ensure that the board cookie was correctly programmed, or try a new board.
Error Message%DFC-1-DFC_OLD_HW_REV: DFC in slot [dec] has old hw rev [dec].[dec] when should be [dec].[dec]Explanation A dial feature card (DFC) board does not have the latest hardware revision. If the hardware version is not the latest, the board must be updated to the version indicated in the error message output.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DFC-1-DFC_OLD_TULUM_VERSION: DFC in slot [dec] has old Tulum version [dec] when should be [dec]Explanation A dial feature card (DFC) board does not have the latest Tulum version.
Recommended Action Update the Tulum version on the DFC board.
Error Message%DFC_CARRIER-1-CARRIER_OLD_HW_REV: DFC Carrier in slot [dec] has old hw revision [dec].[dec] when hw revision should be [dec].[dec].Explanation A dial feature card (DFC) carrier card does not have the latest revision.
Recommended Action If the hardware version is not the latest, update the DFC carrier card with the latest revision as specified in the error message output.
Error Message%DIRECTOR-6-DNSNORSP: answer type [chars] host [chars] cli [IP_address] id# [dec] noneExplanation This is an informational Domain Name System (DNS) reply logging message.
Recommended Action No action is required.
Error Message%DIRECTOR-6-DNSQUERY: query type [chars] host [chars] cli [IP_address] id# [dec]Explanation This is an informational Domain Name System (DNS) reply logging message.
Recommended Action No action is required.
Error Message%DIRECTOR-6-DNSRESPN: answer type [chars] host [chars] cli [IP_address] id# [dec] svr [IP_address]Explanation This Domain Name System (DNS) reply logging message indicates that a server has been found.
Recommended Action No action is required.
Error Message%DIRECTOR-3-NOTCONF: Metric [chars] referenced but not foundExplanation This is an informational Domain Name System (DNS) reply logging message.
Recommended Action No action is required.
Error Message%DIRECTOR-6-SVRNSELCT: no answer for (host [chars] cli [IP_address] type [chars] id# [dec]) [chars]Explanation This is an informational Domain Name System (DNS) reply logging message.
Recommended Action No action is required.
Error Message%DIRECTOR-6-SVRSELECT: select [IP_address] (host [chars] cli [IP_address] type [chars] id# [dec]) [chars]Explanation This Domain Name System (DNS) logging message provides information about the report server selection process.
Recommended Action No action is required.
Error Message%DIRECTOR-5-SVRUPDOWN: server [IP_address] (on port [dec]) has gone [chars]Explanation The remote server has gone up or down.
Recommended Action No action is required.
Error Message%DIRECTOR-3-URLELSEWHERE: URL is elsewhere ('[chars]'), Code [dec] - [chars]Explanation The HTTP return code indicates that the specified page is not actually on this server.
Recommended Action Check the URL that had been configured. Check the configured HTTP server.
Error Message%DIRECTOR-3-URLSVRERR: Server error ('[chars]'), Code [dec] - [chars]Explanation The HTTP return code indicates that a server failure error has occurred.
Recommended Action Check the URL that had been configured. Check the configured HTTP server.
Error Message%DMA-1-DRQ_EMPTY_PAK: Empty packet is being sent to backplane. particle_ptr=[hex]Explanation The drq_io has received a packet that has a particle count of zero. A coding error has occurred that will jeopardize system performance.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. If possible, also provide the output of the show command on the reporting Versatile Interface Processor (VIP).
Error Message%DNET-4-DUPENTRY: Duplicate DECnet Accounting List Entry for nodes [dec].[dec] - [dec].[dec]Explanation A synchronization problem occurred when a new DECnet accounting list entry was being added, and a duplicate entry has been found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show decnet accounting command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show decnet accounting command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DNET-3-NOMEMORY: Insufficient memory for DECnet accounting entryExplanation The traffic information for a particular pair of DECnet nodes cannot be recorded because of a low memory condition.
Error Message Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.%DSCC4-3-ANALYZE_DEVICE_FAILURE: [chars]Explanation A DSCC4 analyze device has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSCC4-3-GENERIC: [chars]Explanation A generic error message has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSCC4-1-INITFAIL: DSCC4([dec]/[dec]), SCC[dec] init failedExplanation The software has failed to initialize or restart the Signaling Connection Control (SCC) of a serial interface.
Recommended Action Clear the serial interface. If the message recurs, call your Cisco technical support representative for assistance.
Error Message%DSCC4-3-INVALID_CLOCKRATE: DSCC4([dec]/[dec]), invalid clock rate (index [dec]) requestedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSCC4-3-NOMEMORY: No memory for [chars] of unit [dec]Explanation The router does not have enough memory to perform the specified function.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%DSCC4-3-OWNERR: DSCC4([dec]/[dec]), Buffer ownership error, pak=0x[hex]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSCC4-3-TOOBIG: DSCC4([dec]/[dec]), packet (size [dec]) too bigExplanation A packet larger than the assigned assigned maximum transmission unit (MTU) of this serial interface has been queued up for transmission. The system should recover.
Recommended Action No action is required. If the message recurs, it may indicate an error related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSCC4-3-TOOSMALL: DSCC4([dec]/[dec]), packet (size [dec]) was less than 2 bytesExplanation A small packet (less than 2 bytes) was queued up for transmission. The interface cannot handle such small packets for transmission. The system should recover.
Recommended Action No action is required. If the message recurs, it may indicate an error related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSCC4-3-UNKNOWN_SCCS: DSCC4, Incorrect SCC numberExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSC_ENV-4-MANUALBOOT: Setting config-register to 0x0 will prevent the feature boards from booting when router shelf is rebootedExplanation The dial shelf controller cannot be booted manually.
Recommended Action Set the configuration register to 0x2 to enable the automatic boot feature.
Error Message%DSC_REDUNDANCY-3-TDMSPLITCONFLICT: Tdm Split conflict detected, my tdm [dec], other rs [dec]Explanation Another router is connected to the dial shelf, and it is claiming ownership of the backplane time slots that this router requires. This problem is probably caused by online insertion and removal (OIR) activity involving the moving of trunk cards from one half of the split to the other.
Recommended Action Resolve the ownership conflict by reloading the router whose time-division multiplexing (TDM) number is greater than the trunk capacity for that router. In some cases it may be necessary to reset both routers.
Error Message%DSIPPF-3-DSIP_SEND_FAILURE: Failed to send DSIP message - number of failures [dec]Explanation The Nitro Interconnect Protocol encountered an error when it was sending a message, and the message has been discarded after three unsuccessful resends.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-BADCB: Unexpected DSIP data callback for modemExplanation An unexpected software event has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-FLOW_CONTROL: DS-RS flow control has got out of sync, connection has too many particles free. slot:[dec] ttynum:[dec] parts_avail:[dec]Explanation (Cisco IOS Release 12.1(5)T message) The flow control accounting on the DS has gotten out of synchronization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-FLOWCONTROLACCOUNT: DS-RS flow control has got out of sync, connection has too many particles free. slot:[dec] ttynum:[dec] parts_avail:[dec]Explanation The flow control accounting on the DS has gotten out of synchronization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-LOWPARTICLES: Not enough particles - modem number:[dec] particles needed:[dec] available:[dec]; CTS [chars]Explanation A breakdown of flow control between the RS and the DS has occurred. The RS has sent more particles than are available for this connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-LOW_PARTICLES: Not enough particles - modem number:[dec] particles needed:[dec] available:[dec]; CTS [chars]Explanation A breakdown of flow control between RS and DS has occurred, and RS has sent more particles than are permitted for this connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-NORXPAK: Static receive paktype unavailableExplanation A software structure was found in an unexpected state during the run time for the indicated modem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-OUTPUT_DROP: Output drop - modem number:[dec] refunded [dec]; particle count [dec], pool size [dec], queue size [dec]Explanation (Cisco IOS Release 12.1(5)T message) The system was unable to allocate particles for sending traffic to the modem module, indicating a breakdown of flow control between RS and DS.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-OUTPUTDROP: Output drop - modem number:[dec] refunded [dec]; particle count [dec], pool size [dec], queue size [dec]Explanation The system was temporarily unable to allocate particles for sending traffic to the modem module. This problem indicates a breakdown of flow control between the RS and the DS.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPDD-1-DSPFWFAILURE: DSPDD internal firmware error[[chars]:[dec]Explanation The router or access server has detected an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPDD-1-INTERNALERROR: DSPDD internal error[[chars]:[dec]Explanation The router or access server has detected an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPDD-1-NOBUFFERS: IOS buffer pool unavailable [[chars]:[dec]]Explanation The router or access server could not allocate internal resources.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPRM-5-DSPFAIL: DSP [dec] in slot [chars], is in the failed stateExplanation The Digital Signal Processor (DSP) entered the FAILED state because of alarm indications.
Recommended Action Replace the DSP resource.
Error Message%DSPRM-5-KEEPALIVE: DSP [dec] in slot [chars], NOT RESPONDING - auto restart([dec] times)Explanation The Digital Signal Processor (DSP) has failed the background keepalive test.
Recommended Action No action is required.
Error Message%DSPRM-5-UPDOWN: DSP [dec] in slot [chars], changed state to [chars]Explanation The Digital Signal Processor (DSP) resource has changed state.
Recommended Action No action is required.
Error Message%DS_TDM-3-ASSERT_FAIL: Slot [dec]: Assertion failed: file `[chars]', line [dec]Explanation An internal sanity check has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-ATTACH_ERR: Slot [dec]: tried but failed to set COMBO_SELECT bit on [chars] FB; cannot attach to backplaneExplanation The time-division multiplexing (TDM) subsystem could not configure the feature board (FB) to attach to the backplane in the manner desired. The FB is defective.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-BAD_CONN: Slot [dec]: unrecognized TDM connect message received ([dec]) on [chars] feature boardExplanation An unrecognized time-division multiplexing (TDM) connect message has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-BAD_DISCONN: Slot [dec]: unrecognized TDM disconnect message received ([dec]) on [chars] feature boardExplanation An unrecognized time-division multiplexing (TDM) disconnect message has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-BAD_DSIP: Slot [dec]: unrecognized DSIP message received ([dec]) on [chars] feature boardExplanation An unrecognized Dial Shelf Interconnect Protocol (DSIP) message has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-BAD_MAPPING: Slot [dec]: Legacy FB ([chars]), with static port-to-DS0 mapping, was passed dynamic mapping infoExplanation A software error has caused dynamic port-to-DS0 mapping information to be passed to a statically mapped feature board (FB).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-BAD_S4_POWER_UP: Slot [dec]: [chars] powered-up with one or more incorrect default settings ([chars])Explanation The specified S4 ASIC did not power up with some of the default settings expected by the software; therefore, the time-division multiplexing (TDM) data integrity could have been compromised.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-CONN_FAILED: Slot [dec]: handling of sub-msg ([dec]/[int]/[int]/[int]/[int]/[int]) [int] of [int] failed; processing of rest of DSIP msg abortedExplanation The processing of a submessage encapsulated within a Dial Shelf Interconnect Protocol (DSIP) TDM_CONNECT message has failed. Any remaining submessages in the DSIP message have not been processed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-CONV_CLOSE: Slot [dec]: open MT8986 (addr: [hex]) connection failed - STo[dec], CHo[dec]Explanation (Cisco IOS Release 12.1(3)T message) An attempt to disable a rate-converted connection has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-CONV_CLOSE: Slot [dec]: open MT8986 (addr: 0x[hex]) connection failed - STo[dec], CHo[dec]Explanation An attempt to disable a rate-converted connection has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-CONV_OPEN: Slot [dec]: open MT8986 (addr: 0x[hex]) [chars] connection failed - STi[dec], CHi[dec], STo[dec], CHo[dec]Explanation An attempt to establish a rate-converted connection has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-CONV_OPEN: Slot [dec]: open MT8986 (addr: [hex]) [chars] connection failed - STi[dec], CHi[dec], STo[dec], CHo[dec]Explanation (Cisco IOS Release 12.1(3)T message) An attempt to establish a rate-converted connection has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-DISC_FAILED: Slot [dec]: handling of sub-msg ([dec]/[int]/[int]/[int]/[int]/[int]) [int] of [int] failed; processing of rest of DSIP msg abortedExplanation The processing of a submessage encapsulated within a Dial Shelf Interconnect Protocol (DSIP) TDM_CONNECT message has failed. Any remaining submessages in the DSIP message have not been not processed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-DISC_FOR_NO_CONN: Slot [dec]: got disc msg for non-existent conn: [chars]-st[int]-ts[int]/gts>[int]><[int]</[chars]-st[int]-ts[int]Explanation The feature board (FB) has received a request to disconnect an unrecognized connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-NO_RECOMB_BUS_DS0: Slot [dec]: no free Recombination bus DS0s left; connection not madeExplanation The time-division multiplexing (TDM) Mezzanine card of the Raiko-based feature board (FB) does not have any free recombination bus DS0s.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-RECOMB_BUS_TS_BAD_USE: Slot [dec]: convention broken for Mezz's Recomb. bus t'slots: [chars]-st[int]-ts[int]/gts>[int]><[int]</[chars]-st[int]-ts[int]Explanation The usage convention has been broken for recombination bus time slots. The broken usage convention is a time-division multiplexing (TDM) error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-S4_INT: Slot [dec]: [chars] generated interrupt [chars]Explanation The S4 ASIC has generated the specified interrupt message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-TDM_CLOSE: Slot [dec]: close MT90820 (addr: [hex]) connection failed - STo[dec], CHo[dec]Explanation An attempt to disable a digitally switched connection has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-TDM_OPEN: Slot [dec]: open MT90820 (addr: [hex]) connection failed - STi[dec], CHi[dec], STo[dec], CHo[dec]Explanation An attempt to establish a digitally switched connection has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-UNEXPECTED_INT: Slot [dec]: got unexpected interrupt from masked-out source '[chars]'Explanation Although it had been masked out, an interrupt has been received from the specified source.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-UNSUPPORTED_MEZZ_VER: Slot [dec]: the detected version ([int]) of Mezzanine card is not supported by this software imageExplanation The software does not support the Mezzanine card that is currently installed on the Raiko card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-VERIFY_DISCONN: Slot [dec]: [chars] failed to veryify disconnect: sto = [dec], ch_out = [dec]Explanation An attempt to verify a time-division multiplexing (TDM) hardware component has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-VERIFY_HILOWMEM: Slot [dec]: [chars] failed to veryify himem, or lowmem: sto = [dec], ch_out = [dec], sti = [dec], ch_in = [dec]Explanation An attempt to verify a time-division multiplexing (TDM) hardware component has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-VERIFY_IMS: Slot [dec]: [chars] failed to veryify IMS: [hex]Explanation An attempt to verify a time-division multiplexing (TDM) hardware component has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX0-5-RBSLINEDBUSYOUT: RBS of slot [dec] controller [dec] timeslot [dec] is dynamic busyoutExplanation Robbed-Bit Signalling (RBS) has been dynamically busied out on the specified time slot and controller.
Recommended Action No action is required.
Error Message%DSX0-5-RBSLINESBUSYOUT: RBS of slot [dec] controller [dec] timeslot [dec] is static busyoutExplanation Robbed-Bit Signalling (RBS) has been statically busied out on the specified time slot and controller.
Recommended Action No action is required.
Error Message%DSX0-5-RBSLINEUNBUSYOUT: RBS of slot [dec] controller [dec] timeslot [dec] is unbusyoutExplanation Robbed-Bit Signalling (RBS) has been restored from a busied out condition on the specified time slot and controller.
Recommended Action No action is required.
Error Message%DSX1-3-FIRMWARE_RESTART: T1/E1 Firmware in slot [dec] restartedExplanation T1/E1 firmware has been restarted. All the active calls on the T1/E1 lines will be disconnected, and the controllers will come back up within a few seconds.
Recommended Action No action is required.
Error Message%DSX1-1-FIRMWARE_RESTART_FAILED: Trunk Firmware in slot [dec] reset failedExplanation The trunk could not be restarted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX1-1-FIRMWARE_RUNNING: T1/E1 Firmware in slot [dec] is runningExplanation T1/E1 firmware is now running after recovering from a critical error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX1-1-FIRMWARE_STOPPED: T1/E1 Firmware in slot [dec] is not runningExplanation The T1/E1 firmware has experienced a critical error and has stopped running. The access server must be reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DTP-5-ILGLCFG: Illegal config(on,isl--on,dot1q) on [chars]Explanation The two ports on the specified link are set to the ON mode, but one port is set to 802.1Q encapsulation, while the other port is set to Inter-Switch Link (ISL) encapsulation. When both ports on a link are set to the ON mode, their encapsulation types must match.
Recommended Action Configure both ports on the link to have the same encapsulation type.
Error Message%DTP-4-MEM_UNAVAIL: Memory was not available to perform the trunk negotiation actionExplanation There is not enough memory to negotiate trunks.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%DTP-5-NONTRUNKPORTON: Port [chars] has become non-trunkExplanation The specified port has changed its status from trunk port to access port.
Recommended Action No action is required.
Error Message%DTP-4-TMRERR: An internal timer error occurred when trunking on interface [chars]Explanation There may be some instances in which a timer that is used by the trunking protocol expires at an unexpected time. The problem is corrected internally.
Recommended Action There are no likely long-term problems associated with the timer expiration. However, if further problems involving trunking are seen, it is recommended that you reload the device.
Error Message%DTP-5-TRUNKPORTCHG: Port [chars] has changed from [chars] trunk to [chars] trunkExplanation The specified trunk port has changed the encapsulation type it uses.
Recommended Action No action is required.
Error Message%DTP-5-TRUNKPORTON: Port [chars] has become [chars] trunkExplanation The specified port has changed from being an access port to a trunk port, using the specified encapsulation.
Recommended Action No action is required.
Error Message%DTP-4-UNKN_ERR: An unknown operational error occurredExplanation The device could not negotiate the trunks an internal operation that has generated an error.
Recommended Action Reload the device.
Error Message%E1T1_MODULE-3-BERTBUSY: Controller [chars] - BERT hardware in use, command refusedExplanation The current task requires bit error rate tester (BERT) hardware resources that are currently occupied with other tasks.
Recommended Action The BERT chip could be in use by either of the following tasks: sending V.54 loopup or loopdown code to the remote end or running a BERT test. Determine if either of the tasks is in progress on this controller.
Error Message%E1T1_MODULE-3-FDLLLOOPDOWN: Controller [chars] - FDL line loopdown code detected, deactivating line loopback.Explanation The system has detected Facility Data Link (FDL) line loopdown code on the unit, and it is deactivating the line loopback.
Recommended Action No action is required.
%E1T1_MODULE-3-FDLPREQOK: Controller [chars] - Remote end is put in payload loopback mode via FDL.Explanation The T1 Facility Data Link (FDL) payload loopup code was sent to the remote end from the unit, and the remote end has activated the payload loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-IBOCLOOPDOWN: Controller [chars] - IBOC loopdown code detected, deactivating line loopback.Explanation The system has detected inband bit-oriented code (IBOC) loopdown code on the unit, and is it deactivating the line loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-IBOCLOOPUP: Controller [chars] - IBOC loopup code detected, activating line loopback mode.Explanation The system has detected inband bit-oriented code (IBOC) loopup code on the unit, and it is activating the line loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-IBOCREQFAILED: Controller [chars] - Failed to put the remote end in line loopback mode via IBOC.Explanation The T1 inband bit-oriented code (IBOC) loopup code was sent to the remote end, but the remote end did not activate the line loopback. The remote end may not have activated the payload loopback because of a controller configuration or line problem.
Recommended Action Ensure that both controllers are up.
Error Message%E1T1_MODULE-3-IBOCREQOK: Controller [chars] - Remote end is put in line loopback mode via IBOC.Explanation The T1 inband bit-oriented code (IBOC) loopup code was sent to the remote end from the unit, and the remote end has activated the line loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-T1REQCANCELLED: Controller [chars] - T1 remote loopback has been cancelled.Explanation T1 loopdown code has been sent to the remote end from the specified unit. The remote end is assumed to have received the loopdown code and deactivated the loopback mode. However, no test has been performed to ensure that the remote end has deactivated the loopback mode.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-V54REQFAILED: Unit [chars] - Failed to put the remote end in V.54 payload loopback modeExplanation The V.54 loopup code was sent to the remote end, but the remote end did not activate loopback. This error could be caused by a controller configuration mismatch or line problem.
Recommended Action Check the time slots and speed setting on both ends for the channel group in question, and ensure that V.54 detection is enabled on the remote end.
Error Message%EC-5-BUNDLE: Interface [chars] joined port-channel [chars]Explanation The specified interface has joined the port channel bundle.
Recommended Action No action is required.
Error Message%EC-5-CANNOT_BUNDLE1: Port-channel [chars] is admin-down, port [chars] will remain stand-alone.Explanation The port channel is administratively down.
Recommended Action Reconfigure the port channel to form a bundle.
Error Message%EC-5-CANNOT_BUNDLE2: [chars] is not compatible with [chars] and will be suspended ([chars])Explanation The specified port has different port attributes from those of the port channel or ports within the port channel.
Recommended Action To join this port to the bundle, change its port attributes to match the port attributes of the port channel.
Error Message%EC-5-L3DONTBNDL1: [chars] suspended: PAgP not enabled on the remote port.Explanation Port Aggregation Protocol (PAgP) is enabled on the Layer 3 interface, but the remote partner port does not have PAgP enabled. In this mode, the port is placed in a suspended state.
Recommended Action Enable PAgP on the remote partner port.
Error Message%EC-5-L3DONTBNDL2: [chars] suspended: incompatible partner port with [chars]Explanation The partner port has been configured with a global configuration (GC) that is different from the GCs on the other ports in the bundle.
Recommended Action For a port to join a bundle, the local GC and the partner GC should match the GC on the other ports in the bundle. Ensure that the partner GCs for all the ports in the group are same.
Error Message%EC-5-L3PORTDOWN: Shutting down [chars] as it's port-channelis admin-downExplanation The administrative state of the Layer 3 port is ruled by the administrative state of its aggregation port. If the administrative state of the aggregation port is down, the administrative state of the Layer 3 port will be forced to go down.
Recommended Action Change the administrative state of the aggregation port to up.
Error Message%EC-5-L3STAYDOWN: [chars] will remain down as it's port-channel[chars] is admin-downExplanation The administrative state of the Layer 3 port is ruled by the administrative state of its aggregation port. If the administrative state of the aggregation port is down, the administrative state of the Layer 3 port will be forced to go down.
Recommended Action Change the administrative state of the aggregation port to up.
Error Message%EC-4-NOMEM: Not enough memory available for [chars]Explanation The Port Aggregation Protocol (PAgP) Shim/EtherChannel (EC) could not obtain the amount of memory it needed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%EC-5-NOPAGP: Invalid EC mode, PAgP not enabledExplanation The EtherChannel (EC) mode could not be set to the mode requested because the Port Aggregation Protocol (PAgP) had not been included in the software image.
Recommended Action Get an image that includes PAgP or set the EC mode to on.
Error Message%EC-5-UNBUNDLE: Interface [chars] left the port-channel [chars]Explanation The interface has been disconnected from the bundle.
Recommended Action No action is required.
Error Message%EC-5-UNSUITABLE: [chars] will not join any port-channel,unsuitable attributes configuredExplanation An attempt was made to configure Port-fast, VLAN Membership Policy Server (VMPS), and Dest-SPAN for Etherchannel. Port-fast, VMPS, and Dest-SPAN cannot be configured for Etherchannel.
Recommended Action Undo the attempted configuration.
Error Message%EVENT-3-INSERT_FAILURE: Failed to insert [chars]Explanation The event process has failed to insert the newly created row in its linked list data structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EVENT-3-NULL_ELEMENT: Null pointer in the watched queue for [chars] testExplanation The process was interrupted by a null element.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EVENT-3-NULL_STRUCT: Null pointer to the [chars] structureExplanation The process was interrupted by an element that contained a null pointer to the test structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FALLBACK-4-CACHE_OVERFLOW: Cache has overflowed.Explanation The fallback cache has overflowed and has dumped a fourth of the entries.
Recommended Action Increase the fallback cache size.
Error Message%FALLBACK-3-INTERNAL_ERROR: [chars]: Internal error.Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FALLBACK-3-MALLOC_FAIL: [chars]: Memory allocation failed.Explanation A memory allocation has failed, possibly because the system memory pool is exhausted.
Recommended Action Allocate more system memory.
Error Message%FALLBACK-3-NO_RTP_PORT: No available RTP ports.Explanation No available voice Real-Time Transport Protocol (RTP) ports were found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FALLBACK-3-NO_STATS: [chars]: No stats were returned.\nExplanation No statistics were returned with the probe.
Recommended Action No action is required.
Error Message%FALLBACK-3-PROBE_FAILURE: A probe error to [IP_address] occurred - [chars]Explanation A probe error has occurred. The responder on the remote router may not have been enabled, or there may not have been any machine on the specified IP address.
Recommended Action Check the destination router.
Error Message%FALLBACK-3-RTR_CREATE_FAIL: [chars]: Creation of probe failed. Return code [dec]Explanation A response time reporter (RTR) probe could not be created. Not having an RTR probe can cause inaccurate Calculated Planning Impairment Factor (ICPIF) values and also can cause Voice over IP (VoIP) calls to be hairpinned when they should not be hairpinned.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FALLBACK-3-RTR_START_FAIL: [chars]: probe could not be started. Return code [dec]Explanation A response time reporter (RTR) probe could not be started. Not having an RTR probe can cause lost or inaccurate Calculated Planning Impairment Factor (ICPIF) values and can cause VoIP calls to be hairpinned when they should not be hairpinned.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FALLBACK-3-RTR_STATS_FAIL: [chars]: Could not retrive statistics from the probe. Return code [dec] \nExplanation Response time reporter (RTR) statistics could not be retrieved from the probe. The absence of RTR statistics can result in inaccurate Calculated Planning Impairment Factor (ICPIF) values and can cause Voice over IP (VoIP) calls to be hairpinned when they should not be hairpinned.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FALLBACK-5-TEST_PROBE_ALREADY_RUNNING: A test probe is already running.Explanation An attempt to run a test probe was made when a test prob was already in progress. Only one test probe may run at a time.
Recommended Action Wait until the first test probe has finished before initiating a second test probe.
Error Message%FASTBLK-4-CREATE_ERR: Fastblk pool creation error: [chars]Explanation A software error occurred during an operation to create a Fast Block memory pool.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FASTBLK-4-DEALLOC_ERR: Fastblk deallocation error: [chars]Explanation A software error occurred during an operation to allocate Fast Block memory.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FASTBLK-4-GROW_ERR: Fastblk pool growth error: [chars]Explanation A software error occurred during an operation to grow the Fast Block memory pool.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FASTBLK-4-QUEUE_ERR: Fastblk queue error: [chars]Explanation A software error occurred during the operation to queue the Fast Block memory.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FASTBLK-4-SHRINK_ERR: Fastblk pool shrink error: [chars]Explanation A software error occurred during the operation to reduce the Fast Block memory pool.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FASTBLK-4-WARNING: Unexpected condition: [chars]Explanation An unexpected condition was detected during a Fast Block memory operation.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FB_COREDUMP-3-NOMEMORY: No Memory or buffer for [chars] to be send to [dec]Explanation There was not enough memory for the router shelf to send any command or acknowledgment to the feature boards.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-BSCHUNT: BSC HUNT cmd for int [dec]/[dec] failedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-1-DISCOVER: NM slot [dec]: only [dec] PCI dev foundExplanation Some of the interface controller devices on the Fast Ethernet Combination Port Module network module did not initialize properly.
Recommended Action Power down, reinsert the port module, and reboot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-DSCC4: DSCC4 chip init slot [dec] failedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-1-INITFAIL: NM slot [dec]: PCI dev [dec] init failedExplanation A protocol control information (PCI) device on the Fast Ethernet Combination Port Module device driver network module has failed to successfully initialize the hardware.
Recommended Action Power down, reinsert the port module, and reboot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-INVALID_CLOCKRATE: Unsupported clock rate req on int [dec]/[dec] - index [dec]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-INVALID_SCC: Config req for invalid SCC via int [dec]/[dec]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-NOMEMORY: No memory for [chars] of unit [dec]Explanation The router does not have enough memory to perform the specified function.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%FECPM-3-OWNERR: Buffer owner ship error on int [dec]/[dec], pak=0x[hex]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-2-SCCFAIL: Init of SCC[dec] for int [dec]/[dec] failed to do [chars]Explanation The software has failed to initialize or restart a Signaling Connection Control (SCC) of a serial interface on the Fast Ethernet Combination Port Module device driver network module.
Recommended Action Clear the serial interface. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-SCCRESET: SCC reset for int [dec]/[dec] at [chars] failedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-SPI_OP_FAILED: NM base addr - 0x[hex], WIC slot - [dec], SPI op failedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-5-TOOBIG: On int [dec]/[dec], tx pak is [dec] bytesExplanation A packet greater than the assigned maximum transmission unit (MTU) of this serial interface was queued up for transmission. The system should recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-5-TOOSMALL: On int [dec]/[dec], tx pak size is [dec] bytesExplanation A small packet (fewer than 2 bytes) was queued up for transmission. The interface cannot send packets that are smaller than 2 bytes. The system should recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-TXCOMPNOTIFY: On int [dec]/[dec], tx_comp_notify vector is not setExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-3-UFHANDLE: UnderFlow handling on int [dec]/[dec] failedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FECPM-5-UNDERFLOW: Transmit underflow on int [dec]/[dec]Explanation While sending a frame, the local buffer of the serial controller chip received insufficient data because data could not be transferred to the chip fast enough to keep pace with the output rate of the chip. Normally, this system problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%FECPM-1-UNKNOWN_WIC: NM slot [dec], wic card has an unknown id [hex]Explanation The software does not recognize the type of WAN interface card (WIC) that is plugged into the port module.
Recommended Action Check the part number on the WIC card to verify that it is supported in the Cisco IOS release that is operational on the router. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FIB-3-FIBLOADBALINITFAIL: Error initializing [chars] load sharing algorithm ([chars]). Default load sharing algorithm restored.Explanation The initialization of the Forwarding Information Base (FIB) load-sharing algorithm has failed because of the specified condition. The default algorithm for this platform and image has been restored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FIB-3-FIBPENDINGLIST: Error queueing interface [chars] to CEF pending event list.Explanation An attempt to queue an interface to the Cisco Express Forwarding (CEF) pending event list has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FIB-3-FIBSBINIT: Error initializing [chars] subblock data structure. [chars]Explanation The initialization of the specified Cisco Express Forwarding (CEF) subblock data structure could not be accomplished.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FIB-3-MAXPATHS_EXCEEDED: Max paths is [dec], [dec] attempted. Address was [IP_address], mask was [IP_address]Explanation An internal software error has occurred. An attempt was made to set up more than the supported number of routing paths. Cisco Express Forwarding (CEF) switching has been disabled on this slot.
Recommended Action Investigate why the number of routing paths has been exceeded.
Error Message%FIB-3-POLICY_NULL_ROUTEMAP: Empty or missing policy routemap found on [chars]Explanation The expected policy route map was empty or missing.
Recommended Action Investigate why an empty route map was associated with this slot.
Error Message%FLASH-3-DEVERR: Error accessing the device : Device number = [dec] Error number = [dec]Explanation An error was detected while the device was being accessed.
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/cgi-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%FLASH-4-SIMM: System Flash Simms unequal. Simm1: [dec]M, Simm2: [dec]MExplanation The system has detected an unsupported Flash configuration.
Recommended Action Replace the Flash SIMMs with SIMMs of equal sizes, or remove the SIMM from the second system Flash slot.
Error Message%FM-4-ACL_CONFLICT: Interface [chars] configured ACLs conflict in [chars] direction(s)Explanation The routed access control lists (ACLs) that were configured for this interface conflict with the VLAN access control lists (VACLs) on this interface. The traffic on this interface may not comply with either the routed ACLs or VACLs.
Recommended Action To remove the interface conflict, redefine or remove the configuration for either the VACLs or the routed ACLs.
Error Message%FM-2-ACL_FAILURE: Interface [chars] traffic will not comply with ACLs in [chars] direction(s)Explanation There are too many configured access control lists (ACLs) to fit into the hardware Ternary Content Addressable Memory (TCAM). TCAM resource contention prevents the ACLs from being applied on traffic for this interface.
Recommended Action Use the mls tcam priority command to prioritize interfaces for hardware switching. If possible, share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.
Error Message%FM-2-BAD_MESSAGE: Error in internal messaging - bad result [dec]Explanation A software error may have affected the programming of access control lists (ACLs) into the Ternary Content Addressable Memory (TCAM).
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FM-2-BAD_TLV: Error in internal messaging - bad tlv [dec]Explanation A software error may have affected the programming of access control lists (ACLs) into the Ternary Content Addressable Memory (TCAM).
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FM-4-RACL_REDUCED: Interface [chars] routed traffic will be software switched in [chars] direction(s)Explanation There are too many configured access control lists (ACLs) to fit into the hardware Ternary Content Addressable Memory (TCAM). TCAM resource contention has prevented the ACLs from being applied in the TCAM for this interface. The traffic on this interface will be rerouted so that the ACLs can be applied.
Recommended Action Use the mls tcam priority command to prioritize the interfaces for hardware switching. If possible, share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.
Error Message%FM-2-SEQUENCE: Error in internal messaging - lost message (i/f [chars], dir [chars], type [dec])Explanation A software error may have a ffected the programming of the access control lists (ACLs) into the Ternary Content Addressable Memory (TCAM).
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FM-2-TCAM_BAD_LOU: Bad TCAM LOU operation in ACLExplanation The access control lists (ACLs) could not be programmed into the Ternary Content Addressable Memory (TCAM) because of a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FM-4-TCAM_CAPMAP: Interface [chars] hardware TCAM LOU usage capability exceededExplanation The hardware Ternary Content Addressable Memory (TCAM) does not have the capacity to handle the number of logical operations that are used with the configured access control lists (ACLs) on this specific interface. The hardware TCAM can only handle up to 9 logical operations per interface and up to 64 logical operations in total.
Recommended Action Reduce the number of logical operations used in the ACLs.
Error Message%FM-4-TCAM_ENTRY: Hardware TCAM entry capacity exceededExplanation The hardware Ternary Content Addressable Memory (TCAM) does not have the capacity to handle all the configured access control lists (ACLs).
Recommended Action Use the mls tcam priority command to prioritize the interfaces for hardware switching. If possible, share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.
Error Message%FM-2-TCAM_ERROR: TCAM programming error [dec]Explanation The programming of access control lists (ACLs) into the Ternary Content Addressable Memory (TCAM) has failed because of a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FM-4-TCAM_LABEL: Hardware TCAM label capacity exceededExplanation The hardware Ternary Content Addressable Memory (TCAM) does not have the capacity to handle the number of interfaces that are configured with access control lists (ACLs). The hardware TCAM can handle only 500 interfaces that are configured with ACLs.
Recommended Action Use the mls tcam priority command to prioritize the interfaces for hardware switching. Remove the configuration of ACLs from some of the interfaces.
Error Message%FM-4-TCAM_LOU: Hardware TCAM LOU capacity exceededExplanation The hardware Ternary Content Addressable Memory (TCAM) does not have the capacity to handle the number of logical operations that are being used with the configured access control lists (ACLs). The hardware Ternary Content Addressable Memory (TCAM) can only handle up to 9 logical operations per interface and up to 64 logical operations in total.
Recommended Action Reduce the number of logical operations used in the ACLs.
Error Message%FM-2-TCAM_MEMORY: NMP processor memory lowExplanation An attempt to program the access control lists (ACLs) into the Ternary Content Addressable Memory (TCAM) has failed because of inadequate memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may 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, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FM-2-VACL_FAILURE: Interface [chars] traffic will not comply with VACLs in [chars] direction(s)Explanation There are too many configured access control lists (ACLs) to fit into the hardware Ternary Content Addressable Memory (TCAM). The specified VLAN access control lists (VACLs) will not be applied on traffic for this interface because of TCAM resource contention.
Recommended Action Use the mls tcam priority command to prioritize the interfaces for hardware switching. If possible, share the same ACLs across multiple interfaces in order to reduce TCAM resource contention.
Error Message%FR-3-FRTSZEROCIR: FRTS: attempt to configure zero CIRExplanation It it not possible to configure a zero committed information rate (CIR). Configuring a zero CIR would prevent data transmission on the virtual circuit (VC).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FS_IPHC-4-IPC_NO_CHUNK: IPC Chunk pool empty, RSP msg junkedExplanation The IP compression private memory pool for interprocess communication (IPC) messages has been exhausted.
Recommended Action If this message occurs regularly, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FS_IPHC-2-LC_CONTEXT_INIT_FAIL: Failed to initialise or allocate memory for TX/RX contextsExplanation The IP compression context tables have not been created because of a lack of memory resources. The line card cannot allocate memory for an IP header compression context.
Recommended Action Reduce the number of contexts that are configured on all interfaces on the affected line card by using the ip rtp compression-connections interface configuration.
Error Message%FS_IPHC-3-LC_INVALID_MSG: Received IPC message of unknown typeExplanation The IP compression on the line card has received an unknown message from the Route Processor.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FS_IPHC-4-LC_NOIPCBUFFER: Unable to malloc IPC msg buffer on line card. Send Message failed.Explanation The line card did not have enough memory in its private memory pool to send IPHC information to the Route Processor.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FS_IPHC-2-LC_PROC_INIT: Line Card Failed to initialise distributed IP Hdr Comp ProcessExplanation The IP compression process was not created on the line card, possibly because of a lack of memory resources.
Recommended Action Check the memory allocation on the line card and either upgrade the line card memory or reduce the feature burden in the interface configurations for the line card.
Error Message%FS_IPHC-3-MSG_TOO_LARGE: Received IPC message to large to handleExplanation The IP compression has received an interprocess communication (IPC) message of a size larger than expected.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%FS_IPHC-4-RP_IPCSENDFAIL: RP unable to send IPHC msg to Line CardExplanation The Route Processor was unable to send an IP header compression configuration message to a line card interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. If possible, also provide the output of the debug ip rtp header and debug ip tcp header commands for the period during which this message had appeared.
Error Message%FS_IPHC-2-RP_NOLCINFO: Unable to malloc state table for Line CardExplanation An internal data structure is missing because of a lack of memory resources.
Recommended Action The Route Processor is dangerously low on memory resources. Free up memory by removing an unwanted feature configuration, or upgrade the memory on the Route Processor.
Error Message%FS_IPHC-3-SEQ_ERROR: Received out of sequence IPC messageExplanation IP compression has received an out-of-sequence interprocess communication (IPC) message.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GPRSFLTMG-4-MOBILITYERROR: GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [dec], [chars]Explanation A failure involving a mobility station has occurred. The following reasons are possible:
•
•
•
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GPRSFLTMG-6-PDP_PURGED: GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [dec], [chars]Explanation The policy decision point (PDP) context has been purged because of a PDP context idle timeout.
Recommended Action No action is necessary.
Error Message%GPRSFLTMG-4-RECOVERYIEDIFF: GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [dec], [chars]Explanation The Cisco Gateway GPRS Support Node (GGSN) has received policy decision point (PDP) update requests with different recovery information elements in the same path.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GPRSMIB-4-FRAGMENT_ERROR: fragmentation error (s_uid = [hex]) receivedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GPRSMIB-4-INVALIDMSG: Invalid GPRSMIB message (msg_type [hex]) receivedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GRP-3-DEVERR: [chars] [dec] [chars] [dec]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-2-APNINVALID: APN name requested ([chars]) is not valid for the GSN node from [int]Explanation An access point name (APN) lookup has failed.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-2-CGWUPDOWN: Charging Gateway [int] changed state to [chars]Explanation The primary or secondary charging gateway has changed its state from up to down or from down to up.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-6-EXTIPADDRALLOCFAIL: ip address allocation failed from external source. APN: [chars] TID: [hex] Reason: [chars]Explanation The Gateway GPRS Support Node (GGSN) has failed to allocate the dynamic IP address.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-2-GSNPATHFAIL: Path to GSN peer [int] failedExplanation No echo message was received from the GSN peer, and the path has timed out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-2-GSNSERVICEUPDOWN: GSN service [chars] changed state to [chars]Explanation The Gateway GPRS Support Node (GGSN) or Serving GPRS Service Node (SGSN) service has started or has shut down.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-6-INTIPADDRALLOCFAIL: ip address allocation failed from internal local pool. APN: [chars] TID: [hex] Reason: [chars]Explanation The Gateway GPRS Support Node (GGSN) has failed to allocate a dynamic IP address from the local pool.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-6-INVALIDIE: Invalid information element (type [dec]) for message type 0x[hex] from [int]Explanation The system has received a GPRS Tunneling Protocol (GTP) packet with an invalid message format.
Recommended Action Determine why the source of the packet is not generating a correct message.
Error Message%GTP-6-INVALIDLFN: Invalid GTP header (lfn bit): [char]Explanation The system has received a GPRS Tunneling Protocol (GTP) packet with an invalid header element.
Recommended Action Determine why the source of the packet is not generating a correct header.
Error Message%GTP-6-INVALIDTID: Invalid GTP header (TID): [hex] from [int]Explanation The system has received a GPRS Tunneling Protocol (GTP) packet with an invalid or unknown Terminal Identifier (TID).
Recommended Action Determine why the source of the packet is not generating a correct header.
Error Message%GTP-2-MSGTOOSHORT: GTP message is too short for the message type, msgtype: [dec], len: [dec], from [ipaddr]Explanation The GPRS Tunneling Protocol (GTP) message received is too short to contain all expected information elements.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-2-NORESOURCE: System resources exhausted: ([chars])Explanation The system resources are exhausted.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-2-PDPACTIVATIONFAIL: GTP PDP activation/update failed, GSN: [int], TID: [hex], Reason: [chars]Explanation A PDP context activation has failed.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-6-PDUPURGED: PDP context purged, TID: ([hex])Explanation A PDP "context idle" timeout has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-2-PROCESSDOWN: GTP Process creation failedExplanation The system cannot start the GPRS Tunneling Protocol (GTP) process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-2-SOCKETSENDFAILED: GTP send failed, errno [dec]Explanation The system cannot send a GPRS Tunneling Protocol (GTP) message using this socket.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-2-UNEXPECTEDMSG: Unexpected GTP signalling message (type 0x[hex]) received from [int]Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-2-UNKNOWNMSG: Unknown GTP message (type 0x[hex]) received from [int]Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-2-VERSIONNOTSUPPORT: GTP Version is not supported, source GSN [int], version received: ([dec]), version supported: ([dec])Explanation The GPRS Tunneling Protocol (GTP) version received is not supported.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HDX-3-BADFSM: On int [dec]/[dec], unexpected state [dec], event [dec]Explanation An unexpected state and event pair was detected in the RX/TX half-duplex state machine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HEARTBEAT-6-NOT_HEARD: Heartbeat messages have not been heard for [dec] secondsExplanation Heartbeat messages have not been heard for a significant amount of time. It is likely that a timeout will soon occur and reset the system.
Recommended Action No action is required.
Error Message%HEARTBEAT-2-NOT_RUNNING: Heartbeat messages have not been sent for [dec] seconds [[chars]] [[chars] [time-stamp]] [[chars] [time-stamp]] [[chars] [time-stamp]]Explanation Heartbeat messages have not been heard for a significant amount of time. It is likely that a timeout will soon occur and reset the system.
Recommended Action No action is required.
Error Message%HEARTBEAT-3-TIMED_OUT: Heartbeat messages have failed, resetting systemExplanation Heartbeat messages have failed and the system is no longer operational.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HW_VPN-1-BADMEMSIZE: [chars]: Invalid Amount of RAM for PA ID, memsize = [hex]Explanation The power-on self test (POST) has reported an invalid memory size.
Recommended Action The encryption Advanced Interface Module (EAIM) must be replaced.
Error Message%HW_VPN-1-BADTYPE: This Encryption AIM type not supported on this router platformExplanation The encryption Advanced Interface Module (EAIM) designed for one particular type of router platform (for example, Cisco 2600) has been installed on another router platform (for example, Cisco 3620). This type of Encryption AIM is not supported by this router platform.
Recommended Action The encryption AIM must be removed and one compatible with your router platform must be installed in its place.
Error Message%HW_VPN-1-BUSY: Encryption AIM busyExplanation You have entered a command that involves an encryption Advanced Interface Module (EAIM), but the encryption AIM is busy executing another command.
Recommended Action Wait until the present command has finished executing. If execution of the present command does not seem to end within a reasonable amount of time, the encryption AIM may be defective and may require replacement.
Error Message%HW_VPN-1-CMDERR: [chars]: Command [hex] failed with status [hex]Explanation A command was sent to the encryption Advanced Interface Module (EAIM), and it responded that the command had failed. The details of the command failure depend upon the circumstances, but the encryption AIM could be defective and could require replacement.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HW_VPN-1-CMDTIMEOUT: [chars]: Timeout on reply to command to Encryption AIMExplanation A command has been sent to the encryption Advanced Interface Module (EAIM), and a reply to the command has not been received within a reasonable amount of time. The encryption AIM is defective and must be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HW_VPN-1-DEVID: EAIM: Invalid PCI device ID: [int]Explanation The encryption Advanced Interface Module (EAIM) device has improperly identified itself on the router bus. The EAIM may be defective and may require replacement.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HW_VPN-1-DEVINIT: EAIM: Device Initialization failureExplanation The encryption Advanced Interface Module (EAIM) has failed to respond properly to initialization attempts.
Recommended Action The EAIM must be replaced.
Error Message%HW_VPN-6-DISABLED: [chars]: disabledExplanation The encryption Advanced Interface Module (EAIM) has been disabled.
Recommended Action The EAIM must be replaced.
Error Message%HW_VPN-1-ELMERREV: AIM in slot [int] not supported by this HW revision.Explanation The revision level of the C2600 programmable logic device (PLD) does not support encryption Advanced Interface Module (EAIM).
Recommended Action The C2600 PLD must be reprogrammed to a later revision. Refer to CCO Release Notes for the C2600 and Encryption AIM for an explanation of how to reprogram the PLD.
Error Message%HW_VPN-1-HELLOERR: [chars]: EAIM responded incorrectly to hello: received [hex] expected [hex]Explanation A command was sent to the encryption Advanced Interface Module (EAIM). The EAIM was expected to echo back the data that was sent to it. Instead the EAIM sent back the data specified in this error message. The EAIM may be defective and require replacement.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HW_VPN-1-HPRXERR: [chars]: Packet Encryption/Decryption error, status=[int]Explanation An unexpected error occurred during the encryption or decryption of a packet.
Recommended Action This message can occur occasionally during normal operation of the system. It may occur during the transition to a new session key for a security association. In such cases, this error message can be ignored. However, if this message recurs frequently, or it is associated with traffic disruption, make a note of the status value and contact a Cisco representative. The encryption Advanced Interface Module (EAIM) may be defective and require a replacement.
Error Message%HW_VPN-1-INITFAIL: EAIM: Initialization failed at [chars]Explanation The encryption Advanced Interface Module (EAIM) would not reset properly, indicating a hardware failure. The EAIM will need to be replaced.
Recommended Action Replace the EAIM.
Error Message%HW_VPN-1-LPRXERR: [chars]: Key management error, cmd=[hex] status=[hex]Explanation An unexpected error occurred during the execution of a key management command by the encryption Advanced Interface Module (EAIM).
Recommended Action Make a note of the status value and contact a Cisco technical support representative. The EAIM may require replacement.
Error Message%HW_VPN-6-MULTDEV: Cannot support more than one Encryption AIMsExplanation A second encryption Advanced Interface Module (EAIM) was discovered to be present in the system. The encryption AIM software supports only a single Encryption AIM. All other installed encryption AIMs will be ignored.
Recommended Action Remove all but one of the encryption AIMs installed in your system.
Error Message%HW_VPN-1-NOHW: Encryption AIM not present in systemExplanation You have entered a command that involves an encryption Advanced Interface Module (EAIM), but no encryption AIM is present in the system.
Recommended Action Do not enter encryption AIM commands unless an encryption AIM is present. If only one encryption AIM has been installed, it is defective and must be replaced.
Error Message%HW_VPN-1-POSTFAIL: [chars]: Power On Self Test failed, alert status = [hex]Explanation The power-on self test (POST) for the encryption Advanced Interface Module (EAIM) has failed.
Recommended Action The EAIM must be replaced.
Error Message%HW_VPN-6-STARTUP: [chars]: starting upExplanation The specified encryption Advanced Interface Module (EAIM) has initialized successfully.
Recommended Action No action is required.
Error Message%HW_VPN-1-UNEXPCMD: [chars]: Invalid command reply: expected [hex] received 0x[chars]Explanation A command was sent to the encryption Advanced Interface Module (EAIM), and the replay message contained an unexpected reply code. The details of this failure depend upon the circumstances, but it is highly possible that the encryption AIM is defective and must be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%I82543-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bayExplanation A possible hardware error has caused too few Gigabit Ethernet (GE) interfaces to be discovered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%I82543-3-ERRINT: [chars], error interrupt, csr_STATUS=[hex]Explanation The Intel 82543 Ethernet/Fast Ethernet/Gigabit Ethernet (GE) controller has signaled an error condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%I82543-1-INITFAIL: I82543([dec]/[dec]), initialization failed, bad base address([hex])Error Message%I82543-1-INITFAIL_NOMEM: [chars], initialization failed, no buffer memoryExplanation The Ethernet port initialization has failed because of insufficient memory.
Recommended Action Upgrade the port adapter with a larger memory model. If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%I82543-5-LOSTCARR: [chars] cable/transceiver problem?Explanation The Ethernet port has detected a link failure, meaning that it is no longer receiving signals from the LAN. This error can be caused by disconnected Ethernet cabling, a transceiver (GBIC) failure, or a shutdown of the remote end.
Recommended Action Check your Ethernet wiring and port adapter. If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%I82543-2-NOISL: Interface [chars] does not support ISLExplanation The Inter-Switch Link (ISL) is not supported on the hardware of the specified interface.
Recommended Action No action is required.
Error Message%I82543-3-NOTI82543: PA bay [int], device number [int]: unknown device ([hex])Explanation The port adapter does not contain an Intel 82543 controller chip.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%I82543-3-TOOBIG: [chars], packet too big ([dec]), from [enet]Explanation The interface has detected a packet larger than the maximum size allowed by the assigned maximum transmission unit (MTU).
Recommended Action Check the MTU setting of the other station.
Error Message%ICC-4-COMM: Communication failure occurred while [chars]Explanation A communication failure has occurred between the specified card and another card in the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ICC-4-CONSISTENCY: Internal consistency check: [chars]Explanation An internal inconsistency was found in some Interface Controller Card (ICC) data structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ICC-4-HEARTBEAT: Card [dec] failed to respond to heartbeatExplanation A communication failure has occurred between the primary and the specified line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ICC-2-NOMEM: No memory available for [chars]Explanation The Interface Controller Card (ICC) subsystem could not obtain as much memory as it needed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%INTERFACE_API-3-NODESTROYSUBBLOCK: The [chars] subblock named [chars] was not removedExplanation A software error has occurred. The specified Interface Descriptor Block (IDB) subblocks cannot be removed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IP-3-STCKYARPOVR: Attempt to overwrite Sticky ARP entry: [IP_address], hw: [enet] by hw: [enet]\nExplanation Multiple stations have been configured with the same IP address in the private VLAN. It is possible that a user has attempted to duplicate some IP addresses.
Recommended Action Change the IP address of one of the two systems.
Error Message%IP-4-UNICASTRPF: IP unicast reverse-path check disabled on [chars]Explanation The IP Verify Unicast Reverse-Path feature was disabled because Cisco express forwarding (CEF) has been disabled, either through configuration or because of an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPA-3-INVMBXCMD: [chars]: invalid mailbox command: [hex]Explanation A subsystem has attempted to register a mailbox command that is out of range.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPA-3-NEVER: bay [[chars]] mailbox response timed out after ([int] + [int]) usecs, mbx=[hex]Explanation A mailbox command sent from the channel port adapter driver to the channel port adapter did not finish within the expected time limit. The mailbox command error has caused the channel port adapter driver to reset the port adapter and reload the microcode to it.
Recommended Action The reset and reload should have resolved the problem. If the problem recurs, try the microcode reload operation again. If the error still recurs, record the output from the following commands:
•
•
•
•
Provide this information to your Cisco technical support representative.
Error Message%IPA-3-PORTCONN: bay [[int]] failed to establish [chars] connection ([hex])Explanation An attempt to establish the console or debugger connection with the channel port adapter has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPA-3-PORTIOKILL: Port IO [chars] process terminating.Explanation The specified process has been terminated unexpectedly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPA-3-UKNMBXCMD: [chars]: unknown mailbox command: [hex] [hex] [hex] [hex]Explanation The channel port adapter has sent a mailbox command that the driver did not expect. This error may occur if there is a version mismatch between the system image and the microcode image.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-3-LOWBUFF: The main IPC message header cache below application reserve count ([dec])., MSGDEF_LIMIT_SLOWExplanation The main IPC message header cache has fallen below the application reserve count.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status 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 ipc status command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-2-NO_ACK_HANDLER: No handler for ACK with data.Explanation A preview function appended data to an ACK message at the sender, but there is no corresponding ACK handler at the receiver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-2-NOACKRECEIVER: Got an ACK with data, couldn't find receiver.Explanation A preview function has inserted data into an ACK, but there is no corresponding ACK receiver.
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 output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPC-2-PRECLOSE: IPC port pre-closure overflow : [hex] : [hex]Explanation An application attempted to close an interprocess communication (IPC) port while pending messages were in the retransmit queue, and the IPC defer table overflowed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC_RPM-3-ECC: WARNING: ECC Single Bit Error CorrectionExplanation An Error-Correcting Code (ECC) single-bit error has been detected and corrected.
Recommended Action Enter the debug rpm ecc command to look at the total number of ECC errors that have occurred since the system was booted. Enter the debug rpm ecc count command to determine the number of ECC errors that will cause a switchover.
Error Message%IPFAST-4-INVALFAIL: Error invalidating IP fast cache due to memory shortageExplanation This debugging message appears when a memory shortage has occurred. The memory shortage could cause incorrect switching decisions.
Recommended Action Upgrade the router memory. If the problem persists, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPFAST-2-IPCACHEINIT: Error initializing IP fast cache structuresExplanation A programming error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_C54X-3-HOST_XMIT_BLOCKED: Host is unable to transmit packets to DSP [dec]Explanation The Cisco IOS software is unable to communicate with one of the digital signal processors (DSPs).
Recommended Action Reload the Cisco IOS software image running on the host. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_C54X-3-INSUFICIENT_SPMMS: [dec] SPMM Modules to support this configurationExplanation There are not enough SPMMs to support this configuration. Certain configurations require more than 1 SPMM module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IPM_DSPRM-3-ERROR_DSP_BOOTLDR_DNLD: Boot loader dwonload failed for dsp [dec] in dsp group [dec]Explanation The digital signal processor (DSP) boot loader firmware download is not successful.
Recommended Action Remove or replace the DSP module.
Error Message%IPM_DSPRM-3-ERROR_DSP_FW_DNLD: BAD restart indication received from dsp [dec] in dsp group [dec]Explanation The digital signal processor (DSP) firmware download has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPM_DSPRM-3-ERROR_DSP_INIT: BAD init config response received from dsp [dec] in dsp group [dec]Explanation The initial configuration in the digital signal processor (DSP) firmware has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPM_DSPRM-3-ERROR_DSP_OPERATION: ALARM indication received from dsp [dec] in dsp group [dec]Explanation The digital signal processor (DSP) has failed and has sent an alarm.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPM_DSPRM-3-ERROR_NO_DSP_RESOURCES: Insufficient DSP resources [chars]Explanation The digital signal processor (DSP) resources are not available to open a voice channel or to run a voice codec.
Recommended Action Check the DSP resource usage to see if the number of active calls has exceeded the limits.
Error Message%IPM_DSPRM-3-ERROR_PORT_NOT_FOUND: Port [dec]/[dec] not found in any DSP groupExplanation The T1 port has not been added to any digital signal processor (DSP) group.
Recommended Action Check to see if the time-division multiplexing (TDM) clock has been configured for this port.
Error Message%IPX-3-BADRDBDATA: Inconsistency in the [chars] LSP Linkage data structure detected.Explanation An internal inconsistency has been detected in a data area used by NetWare Link-Services Protocol (NLSP) to link link-state packets (LSPs) in the relational database (RDB) or source route relational database (SRDB) internal routing table structure.
Recommended Action Copy and save this message. If NLSP is not running, there may be a software or hardware problem that is corrupting the memory. If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ISA-6-INFO: [chars]Explanation This is an informational message from Integrated Services Adapter (ISA) indicating normal operation.
Recommended Action No action is required.
Error Message%ISDN-2-ISDN_GENERAL_TRACEBACK: [chars]:[dec]Explanation A debug traceback condition has occurred.
Recommended Action No action is required.
Error Message%ISDN-3-ISDN_RESOURCE_UNAVAILABLE: [chars]: Resource not available, at [chars]:[dec]Explanation The specified hardware resources could not be allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ISDN-4-RLM_STATUS_CHANGE: ISDN SC [chars]: Status Changed to: [chars]Explanation The ISDN has been notified by the Redundant Link Manager (RLM) component of a status change in the RLM link.
Recommended Action No action is required.
Error Message%IVR-3-BAD_IVR_VERSION: Script requires version [dec].[dec], image supports [dec].[dec]Explanation The Integrated Voice Response (IVR) script requires a more recent version of IVR infrastructure.
Recommended Action Upgrade the version of Cisco IOS software, or use a more recent IVR script.
Error Message%IVR-3-NOSCRIPT: Could not load IVR script [chars] errno=[dec]=[chars]Explanation The interactive voice response (IVR) script could not be loaded.
Recommended Action Ensure that the script exists on the server, and ensure that it is readable.
Error Message%L2R-4-DROP_PAK: l2r uid [dec] drop packet (type [hex]) from/to uid [dec] when [chars]Explanation A packet was dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L2R-4-FRAGMENT_ERROR: fragmentation error (s_uid = [hex]) receivedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L2R-4-INVALIDMSG: Invalid L2R message (msg_type [hex]) received from UID [dec] at line [dec]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L3_MGR-3-FLUSH: L3 MGR flush error: [chars]Explanation The Layer 3 manager has encountered a flush error.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L3_MGR-3-ICC_ASYNC: L3 MGR aysnc request failed: [chars]Explanation The Layer 3 manager has received a null request failure message.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L3_MGR-3-L2_FLUSH_ENTRY: L3 MGR install l2 flush entry: [chars]Explanation The Layer 3 manager has received a "failed status" message.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L3_MGR-3-NULL_SVI: L3 MGR svi allocation error: [chars]Explanation The Layer 3 manager cannot allocate a switched virtual circuit (SVI).
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L3_MGR-3-NULL_VLAN: L3 MGR vlan allocation error: [chars]Explanation The L3 Manager cannot allocate VLAN.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L3_MGR-3-REQ_SEND: L3 MGR SEND error : [chars]Explanation The Layer 3 manager has failed to send out the specified request.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L3_MGR-3-RSP_RCVD: L3 MGR RCVD error: [chars]Explanation The Layer 3 manager has received an error packet.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L3_MGR-3-SW_SHORTCUT: L3 MGR install sw shortcut: [chars]Explanation The Layer 3 manager has received a bad status message.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LAPP_OFF-2-INTERNAL_ERROR: Internal software error, [chars]Explanation An internal software error has occurred.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LAPP_OFF-4-LAPP_OFF_BAD_MESSAGE: LAPP_OFF- Bad message receivedExplanation An unexpected message has been received.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LAPP_OFF-6-LAPP_OFF_CAUSE_ABNORMAL: Call abortedExplanation A call has been aborted.
Recommended Action No action is required.
Error Message%LAPP_OFF-6-LAPP_OFF_CAUSE_NORMAL: Normal call clearingExplanation A normal call clearing has occurred.
Recommended Action No action is required.
Error Message%LAPP_OFF-6-LAPP_OFF_HANDOFF: T.37 Fax off-ramp call initiatedExplanation A fax offramp call has been initiated.
Recommended Action No action is required.
Error Message%LAPP_OFF-2-LAPP_OFF_INTERNAL_ERROR: Internal software error, [chars], cid=[dec]Explanation An internal software error has occurred.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LAPP_OFF-4-LAPP_OFF_NO_SMTP: mmsp- Can't connect to the SMTP serverExplanation An attempt to create a connection to the specified Simple Mail Transfer Protocol (SMTP) server has failed.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LAPP_OFF-4-LAPP_OFF_NO_SMTP_SEND: FAXMAIL- Could not send data to the SMTP serverExplanation A connection to the Simple Mail Transfer Protocol (SMTP) server has been created, but no data can be sent.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LAPP_OFF-1-NOMEMORY: Unit [dec], no memory for [chars]Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%LAPP_OFF-4-SMTP_NOT_CONNECTED: SMTP- failed [chars], [dec]Explanation An attempt to connect to a remote mail server has failed.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LAPP_OFF-6-SMTP_OPEN: SMTP- opening [chars], [dec]Explanation A connection is being attempted.
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_AUTH_FAILED: User authentication failedExplanation A user authentication has failed.
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_DMSP_DISCONNECTED: Document Media Service (DMSP) disconnectedExplanation The Document Media Service has been disconnected.
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_FMSP_DISCONNECTED: Fax protocol (FMSP) disconnectedExplanation The Fax MSP (FMSP) has been disconnected.
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_INTERNAL: Internal error occurredExplanation An internal software error has occurred.
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_NO_ESMTP_CONNECT: ESMTP client did not connect or lost connection to remote serverExplanation The ESMPT client did not connect to or has lost its connection to the remote server.
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_NO_MEMORY: No memory availableExplanation A memory shortage has occurred.
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_NORMAL: Normal call clearingExplanation A normal call clearing operation has occurred.
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_VTSP_DISCONNECTED: Telephony interface (VTSP) disconnectedExplanation The telephony interface has been disconnected.
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_HANDOFF: T.37 Fax on-ramp call initiatedExplanation A fax onramp call has been initiated.
Recommended Action No action is required.
Error Message%LAT-3-BADDATA: Tty%t, Data pointer does not correspond to current packetExplanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LAT-3-BUFFULL: Tty%t, data buffer full with count [dec]Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LAT-3-NOSYNC: Tty%t, Output data ptrs out of sync with byte countExplanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LAT-3-REUSE: Tty%t, Attempt to re-use slot array, empty = [dec], fill = [dec]Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LPD-3-MANYLF: Line %t, packet has too many newlines to convertExplanation An internal buffer did not have enough room to add all the necessary carriage returns to a packet of Line printer daemon (LPD) data destined for a printer configured with the newline-convert command. This message is unlikely to occur with a file that contains valid data.
Recommended Action Check the file being printed to see whether it contains valid, printable data.
Error Message%MCAST-6-GC_LIMIT_EXCEEDED: IGMP snooping was trying to allocate more Layer 2 entries than what allowed ([dec])Explanation The allocation of Layer 2 entries have been limited in order to conserve system resources.
Recommended Action To set the limit of Layer 2 entries, enter the ip igmp snooping l2-entry-limit max-entries configuration command.
Caution
Error Message%MCAST-6-IGMP_CGMP_MODE: IGMP snooping now is running in IGMP_CGMP mode on vlan [dec]Explanation Internet Group Management Protocol (IGMP) snooping has detected a switch or a router that uses the Cisco Group Management Protocol (CGMP) protocol. As a result, IGMP is now running in IGMP_CGMP mode so that other devices that use CGMP protocol can function.
Recommended Action No action is required.
Error Message%MCAST-6-IGMP_ONLY_MODE: IGMP snooping now is running in IGMP_ONLY mode on vlan [dec]Explanation Internet Group Management Protocol (IGMP) snooping is now running on a network where there are no devices that use the Cisco Group Management Protocol (CGMP) protocol. Since IGMP snooping does not have to support the CGMP protocol, it is running in IGMP_ONLY mode.
Recommended Action No action is required.
Error Message%MGCP-2-INTERNAL_CRITICAL: [chars], MGCP_COMPLAIN_IVLExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MGCP-3-INTERNAL_ERROR: [chars], MGCP_COMPLAIN_IVLExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MGCP-4-INTERNAL_WARNING: [chars], MGCP_COMPLAIN_IVLExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MGCP_APP-6-EVT_NODE_ALLOC_FAILED: Failed to allocate memory for event node\nExplanation A memory allocation for the event node has failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MGCP_APP-6-GEN_INIT_NO_IP_INTF_FAILED: Suspended initialization of MGCP services. No IP interface up yet\nExplanation The initialization of Media Gateway Control Protocol (MGCP) services has been suspended. No IP interface has been brought up yet.
Recommended Action Ensure that there is at least one interface configured with an IP address.
Error Message%MICA-3-CRASH: Runtime error on MICA module [dec] Hex [dec]Explanation A software error has occurred on the modem firmware that is running on the specified modem module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MICA-3-INBANDNAK: Inband NAK from modem ([dec]/[dec]): opcode = 0x[hex]Explanation An in-band message that had been sent to the specified modem has been rejected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MICA-3-INBANDNAK: Inband NAK from modem [dec] -- payload 0x[hex][hex][hex][hex][hex][hex] 0x[hex][hex]Explanation An in-band message that had been sent to the specified modem has been rejected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MICA-3-INBAND_UNKNOWN_OPCODE: Inband message with unknown opcode received from modem [dec] -- payload [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]Explanation An in-band message with an unknown operation code has been received from the specified modem.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MICA-3-INVALID_PARAM: Mica sent invalid stack address or length, MICA module [dec], addr 0x[hex], length [dec]Explanation A run-time error has occurred on the modem ISDN channel aggregation (MICA) modem module. The MICA module has sent an invalid stack address or length.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MICA-3-NOMEMORY: Failed To Allocate Memory for MICA modem mgmtExplanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MICA-3-UNKNINBAND: Unknown inband msg from modem ([dec]/[dec]): opcode = 0x[hex]Explanation An unknown in-band message has been received from the specified modem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%MODEM-3-MODEM_INFO_CREATE_FAIL: Unable to create modem infos for slot [dec]Explanation During online insertion and removal (OIR) of the specified board, the modem information could not be created because of a lack of memory.
Recommended Action Save the output of the show memory command, showing the amount of processor and I/O memory usage only, along with the output of the show version command. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MODEMCALLRECORD-3-PM_CALL_RECORD_ERROR: [chars]Explanation An Exceeded Syslog Capability Record message has been received.
Recommended Action No action is required.
Error Message%MODEMCALLRECORD-3-PM_NO_CALL_RECORD_BUF: [chars]Explanation A buffer to build the modem call record could not be allocated.
Recommended Action No action is required.
Error Message%MODEMCALLRECORD-6-PM_TERSE_CALL_FAILED_RECORD: [chars]Explanation A Terse Modem Call Failed Record message has been received.
Recommended Action No action is required.
Error Message%MODEM_HIST-7-CONTROL: [chars]: Control Reply: [hex][hex]Explanation A reply to a control message has been received.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-CSM_IC_CALLED_NUM: [chars]: ISDN incoming called number: [chars]Explanation This tracing message shows the number of the ISDN line that is receiving a call.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-CSM_IC_CALLING_NUM: [chars]: ISDN incoming caller number: [chars]Explanation This tracing message shows the number of an incoming ISDN caller.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-CSM_OC_CALLED_NUM: [chars]: ISDN outgoing called number: [chars]Explanation This tracing message shows a dialed ISDN number.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-3-DC_EVT_POLL: [chars]: DC session response: [chars]Explanation This trace log event provides information for a direct-connect (DC) session response event.
Recommended Action No action is required.
Error Message%MODEM_HIST-3-DC_SESSION: [chars]: DC Session received replyExplanation This trace log event confirms that the direct-connect (DC) session has received a reply.
Recommended Action No action is required.
Error Message%MODEM_HIST-7-MICA_DEBUG_EVT: [chars]: [chars]:Explanation This tracing message provides information about a host debug event that was reported by the specified modem ISDN channel aggregation (MICA) modem.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_DYNAMIC_EVT: [chars]: [chars]: [chars]Explanation This tracing message provides information about a dynamic event that was reported by the specified modem ISDN channel aggregation (MICA) modem.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_END_CONN_EVT: [chars]: [chars]: [chars]Explanation This tracing message provides information about an end connection event that was reported by the specified modem ISDN channel aggregation (MICA) modem.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_LEAD_EVT: [chars]: [chars]:[chars], [chars], [chars], [chars]Explanation This tracing message provides information about a lead event that was reported by the specified modem ISDN channel aggregation (MICA) modem.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_OOS_EVT: [chars]: [chars] [chars] Cause: [chars]Explanation This tracing message provides information about an out-of-service event that was reported by the specified modem ISDN channel aggregation (MICA) modem.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_STARTUP_EVT: [chars]: [chars] [chars]. [chars] Modem firmware = [dec].[dec].[dec].[dec]Explanation This tracing message confirms the successful startup of the specified modem ISDN channel aggregation (MICA) modem.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_STATE_EVT: [chars]: [chars] [chars] State: [chars]Explanation This tracing message provides information about a state event that was reported by the specified modem ISDN channel aggregation (MICA) modem.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_STATIC_EVT: [chars]: [chars]: [chars]Explanation This tracing message provides information about a static event that was reported by the specified modem ISDN channel aggregation (MICA) modem.
Recommended Action This is a debug message only. No action is required.
Error Message%MODEM_HIST-7-MICA_STATUS_EVT: [chars]: [chars]: [chars]. [chars] Modem firmware = [dec].[dec].[dec].[dec]Explanation This tracing message provides information about a status event that was reported by the specified modem ISDN channel aggregation (MICA) modem.
Recommended Action This is a debug message only. No a
