-
Cisco IOS Release 12.4 System Messages, Volume 1 of 2
-
System Messages Overview
-
AAA through ASPP
-
AT through BGP
-
BIT through C6KPWR
-
C6MSFC through CHOPIN_MAINBOARD_ASYNC_PQII
-
CI through COT
-
CPAD through DBUS
-
DCV through DSCREDCLK
-
DSI through ENT
-
ENV_MON through FR_FRAG
-
FR_LMI through GSR_ENV
-
GSRIPC through IF
-
IFINDEX through ISA
-
ISDN through LCCOREDUMP
-
LCINFO through MBRI
-
Volume 1 Glossary
-
Table Of Contents
GSRIPC Messages
The following are Internet router interprocess communication (IPC) service routines messages.
Error Message%GSRIPC-3-PORT : port ([chars]) already exists
Explanation The port to be created already exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GSRIPC-3-REXEC : [chars]
Explanation The remote execution open port has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GSRIPC-3-SYSCALL : For port ([chars]): [chars] fails (cause: [chars])
Explanation The IPC kernel system call has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
GT64010 Messages
The following are GT64010 DMA controller driver messages.
Error Message%GT64010-3-DMA : Interrupt error, c=[hex], m=[hex], rc=[hex]
Explanation An unexpected interrupt has been registered from a DMA engine that was not initialized by the software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT64010-1-DMASTALL : DMA interrupt stalled, restarted engine [dec]
Explanation The driver timed out while waiting for completion of a DMA task. The DMA engine has been restarted.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT64010-3-NOCHANNEL : Referencing unused DMA channel [dec]
Explanation An access to an uninitialized DMA engine has been attempted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT64010-3-TIMER : Interrupt error, c=[hex], m=[hex], rc=[hex]
Explanation An unexpected timer interrupt was received from a timer element that had not been initialized by the software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT64010-3-TIMERINSTALL : Attempt to install already installed timer [dec]
Explanation An attempt was made to initialize a timer element that is already in use.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
GT64011 Messages
The following are CMCC channel port adapter GT64011 messages.
Error Message%GT64011-2-ERROR_INT : GT64011 Error (cause=[hex])
Explanation An unexpected GT64011 error interrupt has occurred.
Recommended Action Ensure all port adapters are properly seated. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT64011-2-ERROR_REGS : GT64011: Bus Error = [hex], Address Decode Error = [hex]
Explanation An unexpected GT64011 error interrupt has occurred.
Recommended Action Ensure all port adapters are properly seated. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT64011-2-UNKNOWN_ID : GT64011 Unknown Device or Vendor ID ([hex])
Explanation The GT64011 was found to have an incompatible device or vendor ID.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
GT64120 Messages
The following are GT64120 DMA controller driver messages.
Error Message%GT64120-3-ID_ERROR : System controller has unexpected vendor id [hex] (expected [hex]) or unexpected device id [hex] (expected [hex])
Explanation The system controller has detected an unexpected vendor or device identification number. The system controller could be faulty or it could have a wrong hardware version. The system might not operate as expected.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
GT96K_FE Messages
The following are messages related to Cisco 3700 series and Cisco 3631 system controller.
Error Message%GT96K_FE-2-CIU_BE : FE - interface: [chars] CIU arbiter configured incorrectly
Explanation The CIU arbiter is configured for big-endian mode, and this image expects it to be configured for little-endian.
Recommended Action Update your Cisco IOS image to the latest version. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-2-CIU_LE : FE - interface: [chars] CIU arbiter configured incorrectly
Explanation The CIU arbiter is configured for little-endian mode, but the image expects the mode to be configured for big-endian.
Recommended Action Update the Cisco IOS software image to the latest version in your release train. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%GT96K_FE-3-EXCESSCOLL : FE - interface: [chars] excessive collisions
Explanation An excessively high collision count has been recorded on this interface.
Recommended Action Monitor the condition for improvement. Degradation could indicate a faulty transmission line or interface. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-3-INIT_ERR : FE - initialization error, [chars]
Explanation An error occurred during system initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-2-LATECOLL : FE - interface: [chars] late collision
Explanation An illegal collision has occurred. This condition is a fatal network error.
Recommended Action If the interface is not usable, reset it. You might have to reboot the system. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-2-NOIDB : FE - interface: unable to allocate IDB control block
Explanation The system did not allocate the memory IDB control block during system initialization.
Recommended Action A system reboot might be necessary to correct the problem. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-5-NOISL : Configure ISL
Explanation An attempt was made to configure ISL on an interface that does not implement ISL.
Recommended Action No action is required. The system should correct itself.
Error Message%GT96K_FE-2-NOMEM : FE - interface: [chars] unable to allocate [dec] bytes of memory
Explanation The system did not allocate memory during initialization.
Recommended Action A system reboot might be necessary. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-2-NOPOOL : FE - interface: [chars] unable to allocate memory pool
Explanation The system did not allocate the memory pool during initialization.
Recommended Action A system reboot might be necessary. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-4-OWNERR : FE - interface: [chars]: OWNERR; tx ring count: [dec], tx pak count: [dec], tx tail: [dec], pak: [hex]
Explanation A packet descriptor ownership error has occurred.
Recommended Action No action is required. The system should correct itself.
Error Message%GT96K_FE-4-SHADOWERR : FE - interface: [chars]: SHADOW_ERR; tx ring count: [dec], tx pak count: [dec], tx tail: [dec], pak: [hex], shad-pak: [hex], shad-mp: [hex]
Explanation A transmit descriptor shadow ring error has occurred.
Recommended Action No action is required. The system should correct itself.
Error Message%GT96K_FE-3-SPURIDON : FE - interface: [chars] spurious IDON interrupt
Explanation A spurious "SMI done" interrupt has occurred.
Recommended Action Monitor the interface for improvement. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-3-SPURINT : FE - interface [chars] spurious interrupt
Explanation A spurious interrupt has occured.
Recommended Action Monitor the interface for improvement. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-4-TOOBIG : FE - interface: [chars]: size [dec]: pak size
Explanation The packet-size limit has been exceeded.
Recommended Action No action is required. The system should correct itself.
Error Message%GT96K_FE-4-TOOMANYPART : FE - count: [dec]: protocol [dec]: descriptor count
Explanation A scattered packet contained too many particles for a Tx ring.
Recommended Action No action is required. The system should correct itself.
Error Message%GT96K_FE-3-TXH_RSRCERR : FE - interface [chars] Tx high resource error interrupt
Explanation A transmit resource error interrupt has occurred on the high-priority descriptor ring.
Recommended Action Monitor the interface for improvement. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-3-TXL_RSRCERR : FE - interface [chars] Tx low resource error interrupt
Explanation A transmit resource error interrupt has occurred on the low-priority descriptor ring.
Recommended Action Monitor the interface for improvement. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-3-TX_UNDERRUN : FE - interface [chars] Tx underrun interrupt
Explanation A transmit underrun interrupt has occurred.
Recommended Action Monitor the interface for improvement. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FE-3-UNDERFLO : FE - interface: [chars] underflow
Explanation A Tx underflow condition has occurred. Part of the packet data was not available while transmission in progress. This condition can cause possible memory access delays.
Recommended Action No action is required. The system should correct itself.
GT96K_FEWAN Messages
The following are messages related to Cisco 3700 series and Cisco 3631 system controller.
Error Message%GT96K_FEWAN-3-BSCHUNT : BSC HUNT cmd for int [dec]/[dec] failed
Explanation An internal error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-4-DCD_CHANGE : Unexpected DCD transition interrupt on wic [dec] port [dec] occured
Explanation An unexpected event has been detected by the software. This should be a transient condition.
Recommended Action The system should recover. No action is required.
Error Message%GT96K_FEWAN-1-DISCOVER : NM slot [dec]: only [dec] PCI dev found
Explanation Some of the interface controller devices on the GT96K_FEWAN network module did not properly initialize.
Recommended Action Power down, reinsert the port module, and reboot.
Error Message%GT96K_FEWAN-3-GT96K : GT96K chip init slot [dec] failed
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-1-INITFAIL : NM slot [dec]: PCI dev [dec] init failed
Explanation A PCI device on the GT96K_FEWAN network module did not successfully complete its hardware initialization.
Recommended Action Power down the system, reinsert the port module, and reboot. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-3-INVALID_TXRX : NM slot [dec], WIC card [dec] doesn't support different tx speed ([dec]) and rx speed ([dec])
Explanation The software does not support different Tx and Rx speed.
Recommended Action Configure the Tx speed and Rx speed to be equivalent.
Error Message%GT96K_FEWAN-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%GT96K_FEWAN-3-OWNERR : Buffer owner ship error on int [chars], pak=[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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-2-SCCFAIL : Init of SCC[dec] for int [dec]/[dec] failed to do [chars]
Explanation The software failed to initialize or restart an SCC of a serial interface on the GT96K_FEWAN.
Recommended Action Clear the serial interface. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-3-SCCRESET : SCC reset for int [dec]/[dec] at [chars] failed
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-3-SMIBUSY : GT96K FE SMI is busy; cannot do PHY register access [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-3-SPI_OP_FAILED : NM base addr - [hex], WIC slot - [dec], SPI op failed
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-5-TOOBIG : On int [chars], tx pak is [dec] bytes
Explanation A packet greater than the assigned MTU of this serial interface was queued for transmission.
Recommended Action The system should recover. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-5-TOOSMALL : On int [dec]/[dec], tx pak size is [dec] bytes
Explanation A small packet (less than 2 bytes) was queued for transmission. The interface cannot process a packet of less than two bytes for transmission.
Recommended Action The system should recover. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-3-TXCOMPNOTIFY : On int [dec]/[dec], tx_comp_notify vector is not set
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-3-UFHANDLE : UnderFlow handling on int [dec]/[dec] failed.
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_FEWAN-5-UNDERFLOW : Transmit underflow on int [chars]
Explanation While a frame was being transmitted, the local buffer of the GT96K controller chip received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%GT96K_FEWAN-1-UNKNOWN_WIC : NM slot [dec], wic card has an unknown id [hex]
Explanation The software does not recognize the type of WIC that is plugged into the port module.
Recommended Action Check the part number on the WIC to verify that it is supported in the CiscoIOS release that is operating on the router. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
GT96K_TDM Messages
The following are Cisco 37xx, Cisco 2691, and Cisco 3631 TDM subsystem messages.
Error Message%GT96K_TDM-1-ETM_FAIL : ETM Failed BIST
Explanation The ETM has failed a built-in self-test.
Recommended Action Remove the ETM module. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GT96K_TDM-1-INITFAIL : C3700 TDM Initialization Failed
Explanation The platform TDM hardware for the Cisco 3700 series Multiservice Access Routers could not be initialized.
Recommended Action Attempt to power down and reboot the system. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
GTP Messages
The following are GPRS Tunnel Protocol messages.
Error Message%GTP-2-GSNSERVICEUPDOWN : GSN service [chars] changed state to [chars]
Explanation The SGSN service has started or has been shutdown.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-0-GTPv1PACKETPARSINGERROR : GSN: [IP_address], TEID: [hex], APN: [chars], Reason: [chars]
Explanation A PDP context activation failed at the packet parsing state for one of the following reasons:
1.
The mandatory IE is missing in the PDP.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%GTP-2-GTPv1PDPACTIVATIONFAIL : GTP PDP activation/update failed, GSN: [IP_address], TEID: [hex], Reason: [chars]
Explanation A PDP context activation or update has failed.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%GTP-3-INCOMPLETECONFIG : APN: [chars], Reason: [chars]
Explanation A required configuration is missing.
Recommended Action Ensure that the missing commands are configured.
Error Message%GTP-0-NORESOURCE : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [chars]
Explanation Available resources have become exhausted. GGSN service cannot continue because of one or more of the following reasons:
1.
2.
3.
Recommended Action For reason 1, check to see whether you can increase the number of PDPs that can be processed by GGSN. For any of the other reasons, if the problem recurs, copy the message exactly as it appears on the console or in the system log. Enter the show gprs gtp status command. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%GTP-0-PACKETPARSINGERROR : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [chars]
Explanation A PDP context activation has failed at the packet parsing state. The reason code indicates the probable cause.
a.
b.
a.
b.
c.
d.
e.
f.
g.
h.
i.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-6-PDP_PURGED : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [chars]
Explanation The PDP context has been purged because of a PDP-context idle timeout.
Recommended Action This is an informational message. No action is required.
Error Message%GTP-2-PDPACTIVATIONFAIL : GTP PDP activation/update failed, GSN: [IP_address], TID: [hex][hex], Reason: [chars]
Explanation A PDP context activation has failed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%GTP-4-RECOVERYIEDIFF : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [chars]
Explanation The GGSN has received a PDP update request with a different recovery information element in the same path.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
GUIDO Messages
The following are GUIDO network module messages.
Error Message%GUIDO-1-DAUGHTER_CARD_DETECTED : NM-HD in slot [dec]: VIC card is inserted in subslot [dec], id [hex].
Explanation The software has detected that a VIC was inserted in the NM-HD port module.
Recommended Action No action is required.
Error Message%GUIDO-1-DAUGHTER_CARD_FAILED : NM-HD in slot [dec]: VIC card in subslot [dec] initialization failed.
Explanation The VIC that is plugged into the NM-HD port module could not be initialized.
Recommended Action Check the part number on the VIC to see if it is supported in the version of Cisco IOS operational on the router. Ensure that the VIC is not damaged. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%GUIDO-1-DAUGHTER_CARD_UNKNOWN : NM-HD in slot [dec]: VIC card in subslot [dec] has an unkown id of [hex].
Explanation The software did not recognize the type of VIC that is plugged into the NM-HD port module.
Recommended Action Check the part number on the VIC to see if it is supported in the version of Cisco IOS that is operational on the router. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%GUIDO-1-NO_DAUGHTER_CARD : NM-HD in slot [dec]: no VIC card is inserted in the NM-HD.
Explanation The software did not detect the presence of a VIC in the NM-HD port module.
Recommended Action Ensure that a VIC has been inserted properly into the NM-HD. If the VIC is inserted properly in the NM-HD port module, check the part number on the VIC to see if it is supported in the version of Cisco IOS software that is operational on the router. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%GUIDO-1-NOPCIMEMORY : NM-HD in slot [dec]: No PCI memory available
Explanation The system is experiencing memory exhaustion in the PCI or packet memory. This condition is probably due to heavy traffic congestion, but could also be due to a software error.
Recommended Action Review the configuration for performance bottlenecks. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
HA Messages
The following are high availability system messages.
Error Message%HA-2-CCB_PLAYBACK_ERROR : CCB playback failed.
Explanation This message provides critical error information regarding a high availability system status or condition.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-2-CCB_RECORD_ERROR : CCB record failed.
Explanation This message provides critical error information regarding a high availability system status or condition.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-4-CONFIG_NOT_LOCKED : Unable to lock the configuration session.
Explanation The configuration session could not be locked. Simultaneous configuration sessions can corrupt the configuration.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-2-CUTOVER_ERROR : [chars]
Explanation A critical failure occurred during cutover of the standby high availability system to the active high availability system. The active system has relinquished system control and the standby system has failed to properly take over as the active.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-2-CUTOVER_NOTICE : [chars]
Explanation This message provides information regarding the state of a cutover from the standby high availability system to the active high availability system. The active system has relinquished system control and the standby system is taking over as the active system.
Recommended Action If the message is due to a failure condition, copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-3-ERROR : [chars]
Explanation An error involving the high availability system has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-5-HA_IOS_VERSION : Active IOS version differs from standby IOS version
Explanation A mismatch has occurred between the active high availability system and the standby high availability system.
Recommended Action No action is required.
Error Message%HA-5-HA_VERSION : Active HA version ([int].[int]) differs from standby HA version ([int].[int])
Explanation A mismatch has occurred between the versions of the active high availability system and the standby high availability system.
Recommended Action No action is required.
Error Message%HA-5-HWMOD_IMG_NOTICE : [chars] hw-module slot [dec] image [chars] : [chars]
Explanation This message provides information regarding a high availability system hardware module configuration status, condition, or event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-4-INCOMPATIBLE : Incompatible RP ([chars]) in slot [dec] - Peer RP being held in reset state
Explanation The peer Route Processor is not compatible with the active Route Processor and will be held in reset state.
Recommended Action Remove the peer Route Processor and replace it with one that is the same type as the active Route Processor so that it will boot as the standby Route Processor.
Error Message%HA-2-INIT_ERROR : [chars]
Explanation An error involving the status or condition of the high availability system has occurred. A failure occurred while the high availability system was being initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-2-IPC_ERROR : [chars] [chars]
Explanation This message provides information regarding the status or condition of a high availability system interprocess communication. An interprocess communication failure has occurred between the active system and the standby system.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-2-MAX_NO_QUIESCE : [dec] linecard(s) not quiesced exceeds limit of [dec], all slots will be reloaded.
Explanation An error has occurred with the line cards of a high availability system during system cutover. The line cards did not quiesce properly. Because of the current configuration, the number of errors that have been detected requires that the system perform a full reload of all of the line cards.
Recommended Action If you removed the active RSP via an OIR operation or have legacy IPs installed, this message indicates normal system operation and no action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-5-MODE : Operating mode is [chars], [chars]mode is [chars].
Explanation This message provides information regarding the operating mode of the high availability system.
Recommended Action Ensure that both the active system and standby systems are correctly configured and operational.
Error Message%HA-2-NO_QUIESCE : Slot [dec] did not quiesce, it will be disabled and then reloaded.
Explanation A high availability system line card error has occurred during system cutover. The line card did not quiesce properly.
Recommended Action If the line card in the slot contains a legacy IP, this message indicates normal system operation and no action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-5-NOTICE : [chars]
Explanation This message provides information regarding status, condition, or event for the high availability system.
Recommended Action No action is required.
Error Message%HA-3-RF_EVENT_FAILED : RF event not processed till [dec] milliseconds. Code = [dec]
Explanation The event message that was sent to the redundancy facility was delayed in processing. The delay time is specified in the message text.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-5-RF_RELOAD_NOTICE : Unable to reload the standby. [chars]
Explanation The active RSP was unable to reload the standby system because of the reason indicated in the message. This may be because the standby system is unplugged, because a redundancy forced switchover process is in progress, or because the reload function has been incorrectly called from the standby system to the active system
Recommended Action If the message says "Standby (slave) is unplugged", verify that the standby system is properly seated in the chassis. If the message says "Switchover is in progress", it means that currently a switchover is in progress, and no action is required. If the message says "Standby cannot reload the Active", enter the show logging and show tech-support commands and open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-3-SYNC_ERROR : [chars]
Explanation A high availability system synchronization status, condition, or event has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-5-SYNC_NOTICE : [chars]
Explanation A high availability system synchronization status, condition, or event has occurred.
Recommended Action No action is required.
Error Message%HA-5-SYNC_RETRY : Reloading standby and retrying sync operation (retry [dec]).
Explanation A high availability system synchronization status, condition, or event has occurred. The synchronization operation will be retried.
Recommended Action No action is required.
Error Message%HA-5-SYNC_RETRY_FAIL : Maximum sync retries exceeded. Reloading standby and cancelling sync.
Explanation A high availability system synchronization status, condition, or event has occurred. The synchronization operation has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA-4-WARNING : [chars]
Explanation A high availability system status, condition, or event has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Check both the active system and standby system for any messages. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
HA_CLIENT Messages
The following are high availability client messages.
Error Message%HA_CLIENT-3-BS_TO_STBY_FAILED : The [chars] HA client's Bulk Sync phase was unsuccessful
Explanation The nominated HA client encountered an unspecified failure during its bulk-sync phase on the active unit. Because of this condition, the standby unit is now out of synchronization. This condition should not normally happen and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-4-CF_NOT_BUNDLED : CF failed to go into bundled mode for the [chars] HA client (rc [int])
Explanation The CF did not allow the specified HA client to use the CF bundled mode. The client continues to operate using the CF unbundled mode.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-3-CF_REG_FAILED : CF registration for the [chars] HA client failed with return code [int]
Explanation The specified HA client has failed to register properly with the CF. This failure should not occur and indicates a software problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-3-CLIENT_INIT_FAILED : Initialisation of the [chars] HA client failed (required field(s) missing)
Explanation The HA client utilities code could not initialize the specified client because some fields required by the utilities code were not provided by the client. This failure should not occur and indicates a software problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-3-CP_TO_STBY_FAILED : Delivery of a checkpointing (CP) message from the [chars] HA client failed
Explanation The CF passed information to the nominated HA client on the active unit that indicated a problem with a checkpoint message. One of the checkpointing messages either could not be sent to or did not reach the standby unit. As a result, the standby unit is now out of synchronization. This failure should not normally occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-3-IF_INDEX_ADD_FAILURE : Unable to add an interface index to a table: [chars] (rc=[dec])
Explanation The interface index could not be added to a table. This condition should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-4-IF_INDEX_LOOKUP_FAILURE : Unable to find an interface index: (rc=[dec]) [chars]
Explanation The interface index could not be found. This is a rare, but possible situation, which should be able to correct itself.
Recommended Action No action is required.
Error Message%HA_CLIENT-3-NO_BS_PROCESS : The [chars] HA client failed to create a Bulk Sync process (rc [int])
Explanation The nominated HA client could not create a Cisco IOS process needed to perform a bulk synchronization. As a result, the client's bulk synchronization did not occur and the standby unit is now out of synchronization. This failure should not occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-3-NO_CF_BUFFER : The [chars] HA client failed to get a buffer (len=[int]) from CF (rc=[dec]); checkpointing failed
Explanation The nominated HA client failed to get a buffer from the CF to store checkpointing data. This condition means that the client was unable to send the data to the standby unit and that the standby unit is now out-of-sync. This condition should not normally occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-3-NO_RF_BUFFER : The [chars] HA client failed to get a buffer (len=[int]) from RF
Explanation The nominated HA client failed to get a buffer from the RF to send an RF message to the peer unit. This condition means that the client was unable to send the message to its peer. This error condition should not normally occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-3-PROTO_VER_INCOMPAT : The HA client '[chars]' is incompatible with the peer
Explanation The named HA client cannot communicate with the client on the peer unit. These units cannot be used in a warm or hot standby environment.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-4-RESOURCE_RECOVERY_LIST_FAILURE : Failed to create [chars] resource recovery list
Explanation The specified resource recovery list could not be created. This message means that resource recovery cannot be performed at switchover; some of the relevant resources are left unusable. This error should not normally occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-3-RF_MSG_NOT_SENT : Delivery of an RF message from the [chars] HA client failed (rc=[int])
Explanation The RF told the nominated HA client that the RF could not send a message to the peer unit. This error should not normally occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-3-RF_REG_FAILED : RF registration for the [chars] HA client failed with return code [int]
Explanation The specified HA client failed to register properly with the RF. This error should not occur and indicates a software problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_CLIENT-3-VALIDITY_CHECK_FAILURE : The HA client detected a validity check failure: [chars]
Explanation The HA client performed a validity check. This check failed and can indicate a serious problem. A reload might be required to recover from this error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
HA_EM Messages
The following are Embedded Event Manager messages.
Error Message%HA_EM-7-ACTION_ADD_PARSER : [chars]: Unable to add action [chars] command;
Explanation Failed to add action command.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-7-ACTION_CNS_AGENT_UNAVAIL : [chars]: CNS Event Agent not available: [dec]
Explanation The CNS event agent is currently not available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-ACTION_CNS_CLEAR_RESTART : [chars]: Unable to clear restart callback;
Explanation The CNS action process failed to clear and restart the callback routine.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-ACTION_CNS_OPEN_FAIL : [chars]: Unable to open connection to CNS Event Agent: [dec]
Explanation The CNS action process failed to open a CNS handle to the event agent.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-ACTION_CNS_SET_RESTART : [chars]: Unable to set restart callback;
Explanation The CNS action process failed to set and restart the callback routine.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-ACTION_ENQUEUE_FAIL : [chars]: Unable to enqueue [chars];
Explanation The enqueue function reported an error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-6-ACTION_SYSLOG : [chars]\n
Explanation An logging action has occurred for the embedded event manager system.
Recommended Action No action is required.
Error Message%HA_EM-7-ACTION_WB_CREATE : [chars]: create_watched_boolean failed: [chars]
Explanation The create_watched_boolean function reported an error trying to create the watched boolean.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-7-ACTION_WB_DELETE : [chars]: delete_watched_boolean failed: [chars]
Explanation The delete_watched_boolean function reported an error trying to delete the watched boolean.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-7-FM_ACTION_ADD_PARSER : [chars]: Unable to add action [chars] command;
Explanation An action command could not be added.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FM_ACTION_ENQUEUE_FAIL : [chars]: Unable to enqueue [chars];
Explanation The enqueue function reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FM_ACTION_WB_CREATE : [chars]: create_watched_boolean failed: [chars]
Explanation The "create_watched_boolean" function reported an error while a watched Boolean operator was being created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMAD_ACTION : [chars]: Error occurred while performing action: [chars].
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMAD_ACTION_INFO : [chars]: Error occurred while fetching action information: [dec].
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-4-FMAD_EVENT_CREATE : [chars]: failed to create an event: [chars]
Explanation An embedded event manager event could not be created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-4-FMAD_EVENT_REG : [chars]: failed to register an event: [chars]
Explanation An embedded event manager event could not be registered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMAD_EVENT_TYPE : [chars]: unknown event type [dec]
Explanation An unknown embedded event manager event type was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMAD_EXECUTE_CALLBACK : [chars]: failed to execute callback
Explanation The callback routine could not be executed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMAD_FH_INIT : [chars]: could not initialize Embedded Event Manager service: [chars]
Explanation An internal error was detected while the embedded event manager service was being initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMAD_LAST_POLICY : [chars]: invalid last policy name replied [chars]
Explanation An internal error has occurred. The last policy name to which the script director replied was invalid.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-4-FMAD_NO_ACTION : No action configured for applet [chars]
Explanation No action has been configured for the applet specified in the message.
Recommended Action Configure at least one action for this applet.
Error Message%HA_EM-3-FMAD_NOESID : [chars]: No such event spec id found.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-4-FMAD_NO_EVENT : No event configured for applet [chars]
Explanation No event has been configured for the applet specified in the message.
Recommended Action Configure an event for this applet.
Error Message%HA_EM-7-FMAD_NO_MEM : [chars]: not enough memory
Explanation Memory could not be allocated because of a low-memory condition.
Recommended Action Reduce other activity to reduce memory demands. If conditions warrant, upgrade to a larger memory configuration. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMAD_QUEUE_INIT : [chars]: could not initialize queue
Explanation An internal error was detected while the embedded event manager queue was being initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMAD_REQINFO : [chars]: Error attempting to fetch event information: [dec].
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMAD_UNKNOWN_ENV : [chars]: could not find environment variable: [chars]
Explanation The embedded event manager applet director could not find the environment variable specified in the message text.
Recommended Action Only use well-known embedded event manager environment variables. If the message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMAD_UNKNOWNTYPE : [chars]: Unknown event type found in applet.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMAD_WRONGTYPE : [chars]: Published event type does not match event spec.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMC_CBH_PROCESS_CREATE : [chars]: callback handler process create failed for eid: [dec]
Explanation The "process_create" function could not create the callback handler process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMC_ENQUEUE_FAIL : [chars]: Unable to enqueue [chars];
Explanation The enqueue function has reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMC_FH_INIT : [chars]: fh_init failed : [dec]
Explanation The "fh_init" function could not initialize EEM for a callback process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMC_INV_REPLY : [chars]: Application client library unable to handle message receive.
Explanation The API received a message reply when it was not in a state to accept such messages.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMC_MALLOC : [chars]: Unable to allocate [chars];
Explanation The memory allocation function reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMC_REG_CBH_PULSE : [chars]: Unable to locate reg callback entry for pulse code [dec]
Explanation The registration callback handler was unable to validate the pulse code that was received. The "pthread_create" function has reported an error.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMC_REG_CBH_SEND : [chars]: Unable to send response for FH_MSG_CALLBACK_DONE [chars]
Explanation The registration callback handler was unable to send a "FH_MSG_CALLBACK_DONE" message to the embedded event manager server. The "pthread_create" function has reported an error.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_ADD_PARSER : [chars]: Unable to add [chars] event detector command;
Explanation The event detector failed to add a command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_DE_FETCH : [chars]: [chars][[dec]]
Explanation An internal error has occurred. The event detector has failed to fetch a data element from the statistics data engine.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMFD_EMPTY_QUEUE : [chars]: The [chars] event detector I/O queue empty.
Explanation The I/O queue has been detected as being empty. It should not be empty at this point.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_ENQUEUE_FAIL : [chars]: Unable to enqueue [chars];
Explanation The enqueue function has reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_HIST_QERR : [chars]
Explanation An internal error has occurred. The event detector has failed to obtain a free history list entry.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_INV_COMPARE_OP : [chars]: invalid comparison operator: [dec]
Explanation An internal error has occurred. The value comparison operator is invalid or is not supported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_INV_STATS_TYPE : [chars]: invalid statistics value type: [dec]
Explanation An internal error has occurred. The statistics data type is invalid or is not supported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_INV_TM : [chars]: invalid timer: type=[dec], timer=[p]
Explanation An internal error has occurred. The timer value is invalid or is not as expected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_INV_TM_TYPE : [chars]: invalid timer type: [dec]
Explanation An internal error has occurred. The timer type is invalid or is not supported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_MALLOC : [chars]: Unable to allocate [chars]; [chars]
Explanation The memory allocation function has reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_MET_RBLD : [chars]: [chars]
Explanation An internal error has occurred. The event detector has failed to rebuild the metric list from the checkpointed records.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_MSGSEND_RETRY_ERR : [chars]: [dec]
Explanation The event detector has exceeded its maximum number of retries to send a pulse to the embedded event manager for notification of an event-publishing operation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_OE_CREATE : [chars]: could not create an occurrence entry
Explanation An internal error has occurred. The event detector has failed to create an entry for the matched occurrence list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_OE_REMOVE : [chars]: could not remove an occurrence entry
Explanation An internal error has occurred. The event detector has failed to remove an entry for the matched occurrence list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMFD_OID_UNAVAIL : [chars]: The following oid has become unavailable: [chars]
Explanation The registered OID is no longer available in the system.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_PLTF_NODENAME : [chars]: could not get local node name
Explanation The event detector has failed to retrieve the local node name.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_PROC_ENT : [chars]: [chars]: no more table entries for this process
Explanation An internal error has occurred. The event detector exhausted the available memory while it was collecting statistics for a new process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_PUB_TM_ALLOC : [chars]: Unable to allocate memory for event publish timer block
Explanation There was an internal error. The event detector has failed to allocate memory for the event publish timer block.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMFD_QUEUE_INIT : [chars]: Unable to initialize queue;
Explanation The queue initialization function has reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMFD_TM_LEAF_NEW : [chars]: could not create a leaf timer
Explanation There was an internal error. The event detector has failed to create a managed leaf timer.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMFD_TTY_NUM : [chars]: Error occurred while fetching TTY number.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMPD_ACTION : [chars]: Error occurred while performing action: [chars].
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMPD_ACTION_INFO : [chars]: Error occurred while fetching action information: [dec].
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMPD_CLI_CONNECT : Unable to establish CLI session: [chars]
Explanation Unable to establish CLI session.
Recommended Action Not available.
Error Message%HA_EM-3-FMPD_CLI_DISCONNECT : Error disconnecting from CLI session: [chars]
Explanation An error has occurred while disconnecting from the CLI session.
Recommended Action Not available.
Error Message%HA_EM-3-FMPD_CLI_READ : Unable to read CLI response: [chars]
Explanation Unable to read CLI response.
Recommended Action Not available.
Error Message%HA_EM-3-FMPD_CLI_WRITE : Unable to send CLI command: [chars]
Explanation Unable to send CLI command.
Recommended Action Not available.
Error Message%HA_EM-4-FMPD_EVENT_CREATE : [chars]: failed to create an event: [chars]
Explanation Failed to create an Embedded Event Manager event.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-4-FMPD_EVENT_REG : [chars]: failed to register an event: [chars]
Explanation Failed to register an Embedded Event Manager event.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-7-FMPD_EVENT_TYPE : [chars]: unknown event type [dec]
Explanation An unknown Embedded Event Manager event type was detected.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMPD_EXECUTE_CALLBACK : [chars]: failed to execute callback
Explanation A callback routine has failed to execute.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMPD_FH_INIT : [chars]: could not initialize Embedded Event Manager service: [chars]
Explanation An internal error was detected when initializing the Embedded Event Manager service.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-7-FMPD_FORMAT_TIME : [chars]: error attemting to format time string
Explanation Format time failure.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-7-FMPD_LAST_POLICY : [chars]: invalid last policy name replied [chars]
Explanation There was an internal error. The last policy name that the script director replied to was invalid.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-4-FMPD_NO_ACTION : No action configured for applet [chars]
Explanation No action has been configured for this applet.
Recommended Action Configure at least one action for this applet.
Error Message%HA_EM-3-FMPD_NOESID : [chars]: No such event spec id found.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-4-FMPD_NO_EVENT : No event configured for applet [chars]
Explanation No event has been configured for this applet.
Recommended Action Configure an event for this applet.
Error Message%HA_EM-7-FMPD_NO_MEM : [chars]: not enough memory: [chars]
Explanation Allocating memory has failed due to a low-memory condition.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMPD_QUEUE_INIT : [chars]: could not initialize queue
Explanation An internal error was detected when initializing the Embedded Event Manager queue.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMPD_REQINFO : [chars]: Error attempting to fetch event information: [chars].
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMPD_SET_INFO : [chars]: Error occurred while fetching variable information: [dec].
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMPD_SMTP_CHK_REPLY : Reply code unexpected from SMTP server: [chars]
Explanation An unexpected reply code was received from the connected SMTP server.
Recommended Action Not available.
Error Message%HA_EM-3-FMPD_SMTP_CONNECT : Unable to connect to SMTP server: [chars]
Explanation Unable to connect to the SMTP server.
Recommended Action Not available.
Error Message%HA_EM-3-FMPD_SMTP_DISCONNECT : Unable to disconnect from SMTP server: [chars]
Explanation Unable to disconnect from the connected SMTP server.
Recommended Action Not available.
Error Message%HA_EM-3-FMPD_SMTP_READ : Unable to read from SMTP server: [chars]
Explanation Unable to read from the connected SMTP server.
Recommended Action Not available.
Error Message%HA_EM-3-FMPD_SMTP_WRITE : Unable to write to SMTP server: [chars]
Explanation Unable to write to the connected SMTP server.
Recommended Action Not available.
Error Message%HA_EM-3-FMPD_UNKNOWN_ENV : [chars]: could not find environment variable: [chars]
Explanation The embedded event manager applet director could not find the environment variable specified in the action message.
Recommended Action Use only well known embedded event manager environment variables. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMPD_UNKNOWNTYPE : [chars]: Unknown event type found in applet.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMPD_WRONGTYPE : [chars]: Published event type does not match event spec.
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-7-FMS_APPLET_EXEC : [chars]: Applet execution has been [chars]
Explanation The applet execution state for the embedded event manager has been changed to the state named in the message.
Recommended Action No action is required.
Error Message%HA_EM-7-FMS_CALLBACK_MAX_ENTRIES : Maximum number of callback publish entries exceeded for [chars]; some events \n have been discarded
Explanation An attempt to publish an event requiring a callback has failed because there is no room in the callback publish queue for the specified process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMS_CNS_FAIL : [chars]: Failed to perform CNS action: [chars]
Explanation The embedded event manager failed to send a CNS message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMS_EMPTY_QUEUE : [chars]: The I/O queue empty.
Explanation The I/O queue has been detected as being empty. It should not be empty at this point.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-3-FMS_ENQUEUE_FAIL : [chars]: The Unable to enqueue packet onto queue.
Explanation The queue is not in a state to enqueue packets.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMS_FDC_ALLOCATE : [chars]: Failed to allocate Event Detector context control block; [chars]
Explanation The "get_fd" function reported an error while an event detector context control block was being allocated.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMS_FDC_OPEN : [chars]: Failed to open Event Detector context control block
Explanation The "open_fd" function reported an error while an event detector context control block was being opened.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMS_GUARD_WORD_VER : [chars]: [chars] guard word corrupted;[p]
Explanation The guard word for the specified control block contained information that was not expected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMS_INV_ARG_STRING : [chars]: Invalid argument string: [chars]
Explanation An invalid argument string was passed to the specified function.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-7-FMS_MALLOC : [chars]: Unable to allocate [chars]; [chars]
Explanation The memory allocation function has reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMS_NULL_SCRIPT_NAME : [chars]: The script name is NULL
Explanation An invalid script name was passed as an argument into the specified function.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMS_OPEN : [chars]: Unable to open [chars]; [chars]
Explanation The open function reported an error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-7-FMS_POLICY_EXEC : [chars]: Policy execution [chars]
Explanation The Embedded Event Manager policy execution state has been changed to the state named in the message.
Recommended Action No Action is required.
Error Message%HA_EM-3-FMS_POLICY_LOOKUP_FAIL : [chars]: Failed to look up in the table the registration specification for policy [chars].
Explanation A table lookup for the registration specification for the policy has failed.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-7-FMS_POLICY_MAX_ENTRIES : [chars]: Maximum number of script publish entries exceeded; some events have been discarded
Explanation An attempt to publish an event requiring a script has failed because there is no more room in the script publish queue.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-3-FMS_QUEUE_INIT : [chars]: The Unable to initialize queue.
Explanation The queue cannot be initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMS_REALLOC_FAIL : [chars]: Unable to reallocate [chars]; [chars]
Explanation The realloc function reported an error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-6-FMS_RELOAD_SYSTEM : [chars]: Policy has requested a system reload;
Explanation An embedded event manager policy has requested that the system be reloaded.
Recommended Action No action is required.
Error Message%HA_EM-7-FMS_STRDUP : [chars]: Failed to duplicate string [chars]; [chars]
Explanation The strdup function reported an error.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%HA_EM-7-FMS_SWITCH_FAIL : [chars]: The system is unable to switch to standby processor. Switchover cancelled.
Explanation Switchovers must occur when a standby processor is available and ready.
Recommended Action Ensure that a standby processor is available and ready.
Error Message%HA_EM-6-FMS_SWITCH_HARDWARE : [chars]: Policy has requested a hardware switchover
Explanation A hardware switchover has been requested.
Recommended Action No action is required.
Error Message%HA_EM-3-FMS_SWITCH_NOT_RF_ACTIVE : [chars]: This processor is not in ACTIVE state (state = [dec]). Switchover must be performed on ACTIVE processor.
Explanation Switchovers must occur on the active unit, not the standby unit.
Recommended Action Ensure that the switchover occur on a unit that is designated as an active unit and not a standby unit.
Error Message%HA_EM-7-FMS_SWITCH_STANDBY_UNAVAIL : [chars]: The STANDBY processor is not available. Switchover cancelled.
Explanation A switchover was requested for a standby unit that was not available. The switchover has been canceled.
Recommended Action Perform the switchover when the standby unit is available and ready.
Error Message%HA_EM-7-FMS_WB_CREATE : [chars]: create_watched_boolean failed; [chars]
Explanation The "create_watched_boolean" function reported an error while the watched Boolean operator was being created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HA_EM-7-FMS_WQ_CREATE : [chars]: create_watched_queue failed; [chars]
Explanation The "create_watched_queue" function reported an error while the watched queue was being created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
HAL Messages
The following are Halcyon messages.
Error Message%HAL-3-BADMSG : Received unexpected mailbox message (id = [dec])
Explanation An unexpected message has been received from the HAL firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-1-CONFIGURE : Failed to configure [dec] interfaces in bay [dec], shutting down bay
Explanation The HAL hardware failed. Some components on the board failed to initialize.
Recommended Action Replace the HAL port adapter.
Error Message%HAL-1-DISCOVER : Found [dec] interfaces in bay [dec], shutting down bay
Explanation The HAL hardware failed. Some components on the board failed to initialize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-1-DWNLDFAIL : Microcode to slot [dec]
Explanation An attempt to download firmware into the HAL port adapter has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-3-ERROR : [chars]
Explanation This message is a general error information message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-2-HALFWCRASHED : HAL F/W crashed in bay [dec]: [hex] - reset
Explanation The HAL firmware did not update the software watchdog.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-2-HALFWCRASHEDINFO : [hex] [hex] [hex] [hex]
Explanation This message provides information about a HAL firmware crash.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-3-HALNOACC : [chars] - Accumulator is not available
Explanation An invalid Tx accumulator has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-1-INITFAIL : Slot [dec] firmware init ([chars])
Explanation This message indicates a HAL firmware initialization failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-1-INITFAILP : [chars] init failed at [chars]
Explanation This message indicates a HAL initialization failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-3-LOVEFAIL : [chars]: failed to send [chars] love letter
Explanation A "love letter" (operating status or configuration message) was not sent to RSP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-3-MBOXRECV : Failed to receive reply [dec] from bay [dec] firmware
Explanation A message was not received from the HAL firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-3-MBOXSEND : Failed to send msg [dec] to bay [dec] firmware
Explanation A message was not sent to the HAL firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-3-MBOXSENDM : Failed to send msg [chars] to bay [dec] firmware
Explanation The specified message was not sent to the HAL firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-3-MBOXSENDP : Failed to send msg [dec] to [chars] driver firmware
Explanation A port- related message was not sent to the HAL firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-3-NOTMXT : Slot [dec] device ID seen as [hex], expected [hex] (Mueslix)
Explanation The system failed to detect the HDLC controller on the HAL.
Recommended Action Replace the HAL port adapter.
Error Message%HAL-3-NOTPLX : Slot [dec] device ID seen as [hex], expected [hex] (PLX9060)
Explanation The PLX 9060 was not detected on the HAL.
Recommended Action Replace the HAL port adapter.
Error Message%HAL-1-NOTREADY : Slot [dec] for microcode download
Explanation An error was detected on the communication path between the VIP and the HAL.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-2-NOVC : [chars]: packet received for unknown VC [dec]
Explanation The virtual channel encapsulation is corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-3-OWNERR : [chars] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The HAL driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-1-RESTARTFAIL : [chars] could not be reset by [chars]
Explanation The restart failed to reset the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-1-STARTFAIL : [chars] could not be enabled by [chars]
Explanation The restart failed to enable the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-1-STOPFAIL : [chars] could not be disabled by [chars]
Explanation The shutdown failed to disable the interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAL-1-UNSUPPORTED : \n[chars]
Explanation A HAL port adapter with a revision number earlier than Revision 3 has been detected. This port adapter predates the router platform in which it has been installed, and is not a supported combination.
Recommended Action Upgrade to a HAL port adapter that is Revision 3 or later.
HAWKEYE Messages
The following are Token Ring protocol control information (PCI) port adapter messages.
Error Message%HAWKEYE-3-ADPCHK : Interface [chars], adapter check error
Explanation The Token Ring interface has encountered an unrecoverable error condition while it was operating and connected to the ring. The interface automatically shuts itself down.
Recommended Action Issue the clear interface token command to restart the interface. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAWKEYE-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay
Explanation The Token Ring device driver was unable to communicate with all of the interfaces expected to be on the port adapter module. This condition could indicate that one or more of the interfaces is not functioning. This message can occur during Cisco IOS software initialization or after an OIR of a Token Ring port adapter or module.
Recommended Action Reseat the port adapter or module in the slot. If necessary, install it in another slot. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAWKEYE-3-INITFAIL : [chars] failed to initialize - [chars]
Explanation The Token Ring interface has encountered an error while attempting to open a connection to the ring. The specific error that occurred is described in the last half of the error message as one of the following:
–
–
–
Recommended Action Reset the interface using the clear interface token command in EXEC mode. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAWKEYE-1-NOPCIMEMORY : PCI memory unavailable for [chars]
Explanation The device driver for the specified interface was unable to allocate the necessary amount of shared memory between the driver and the interface hardware. This condition can occur if the system contains less than the recommended minimum amount of SRAM for the current interface combination. Because shared memory blocks are required for the interface to function, the specified interface is inoperable until the memory shortage is corrected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HAWKEYE-1-OLDREV : HAWKEYE(bay [dec]), Port adapter requires Rev 2 CPU, shutting down bay
Explanation The device driver has detected an NPE150 CPU version earlier than Revision 2. The Token Ring device driver requires capabilities of an NPE150 Revision 2 or later CPU. This message is specific to Cisco 7200 series routers.
Recommended Action Upgrade the Cisco 7200 router processor to an NPE150 Revision 2 or later.
HD Messages
The following are HD64570 serial controller messages.
Error Message%HD-1-BADLOOPCABLE : Loopback not supported for a 4T DTE/X.21, port [dec] in slot [dec]
Explanation Loopback mode is not allowed when using an X.21 DTE cable on a Quad serial NIM port.
Recommended Action Do not enable loopback mode, or use a different cable type.
Error Message%HD-1-BADPORTADAPTER : 4T Port Adapter fault on port [dec] in slot [dec]
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HD-1-BADRING : Bad [chars] ring size
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HD-5-LINEFLAP : Unit [dec] excessive modem control changes
Explanation Too many modem control interrupts have been received. The port was disabled to prevent excessive use of the CPU.
Recommended Action Check the cable on the serial port.
HDLC32 Messages
The following are PAS HDLC32 messages.
Error Message%HDLC32-1-NOPCIMEMORY : HDLC32 in slot [dec]: No PCI memory available
Explanation The system is experiencing memory exhaustion in the PCI or packet memory. This condition is probably due to heavy traffic congestion but it could also be due to a software error.
Recommended Action Review the configuration for performance bottlenecks. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
HDV Messages
The following are High Density Voice (HDV) driver messages.
Error Message%HDV-3-DISCOVER : HDV in slot [dec]: the HDV failed to initialize properly.
Explanation An initialization action has failed for the HDV. This failure can be caused by a lack of system resources, a missing VIC, an improper VIC installed in the port module, or defective HDV hardware.
Recommended Action Power down the router. Check that a supported VIC is properly installed in the HDV port module. Reinsert the VIC, and then reinsert the port module and reboot the router. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HDV-2-FATAL_ERROR : HDV in slot [dec]: An unrecoverable error occurred.
Explanation The HDV card has experienced an internal unrecoverable error. This error can be caused by an internal firmware error or defective HDV hardware.
Recommended Action Power down, reinsert the network module, and reboot the router. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HDV-3-FW_START : HDV in slot [dec]: the firmware on the port module did start properly.
Explanation The firmware on the card did not start after a reset. This condition is usually caused by a defective HDV module or improperly seated HDV module.
Recommended Action Power down, reinsert the HDV port module, and reboot the router. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HDV-3-HW_START : HDV in slot [dec]: the port module did not reset and start up properly.
Explanation The hardware on the card did not start after a reset. This condition is usually caused by a defective HDV module or improperly seated HDV module.
Recommended Action Power down, reinsert the HDV port module, and reboot the router. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HDV-3-IDB_CREATE : Error creating an idb for VoIP fastswitching in slot [dec].
Explanation The HDV driver failed to create an IDB for VoIP fast switching.
Recommended Action Power down and reboot the system. If this message recurs, the Cisco IOS software image is most likely missing a required subsystem. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HDV-3-INCORRECT_PMID : HDV in slot [dec]: Incorrect [dec] PM-ID device not supported.
Explanation An interface controller device did not have the correct port module ID.
Recommended Action Ensure that the HDV port module is inserted properly. If necessary, power down the router and reinsert the HDV port module. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HDV-3-INVALID_PCI_ID : HDV in slot [dec]: reports an invalid device id of [hex].
Explanation The HDV port module hardware mighty be defective or improperly seated.
Recommended Action Power down, reinsert the network module, and reboot the router. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HDV-1-NO_DAUGHTER_CARD : HDV in slot [dec]: no VIC card is inserted in the HDV.
Explanation The software did not detect the presence of a VIC inserted in the HDV port module.
Recommended Action Check that there is a VIC inserted properly into the HDV. If the VIC is inserted properly, check the part number on the VIC to see if it is supported by the version of Cisco IOS software that running on the router. For further assistance, contact your Cisco technical support representative.
Error Message%HDV-1-NOPCIMEMORY : HDV in slot [dec]: No PCI memory available.
Explanation The system has exhausted its memory in the PCI or packet memory. This condition is probably due to heavy traffic congestion but could also indicate a software error.
Recommended Action Review the system configuration for performance bottlenecks. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HDV-4-SWVER_NOSUPPORT : HDV at slot [dec]: not supported on this version of IOS software.
Explanation This version of Cisco IOS software does not support the HDV card.
Recommended Action Load a version of Cisco IOS software that supports this card.
Error Message%HDV-1-TOOBIG : HDV in slot [dec]: packet size ([dec]) too big.
Explanation A packet greater than the 256-byte maximum has been received on this interface.
Recommended Action The system should recover. No action is required. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HDV-1-UNKNOWN_VIC : HDV in slot [dec]: VIC daughter card has an unknown id of [hex]
Explanation The software did not recognize the type of VIC that is plugged into the HDV port module.
Recommended Action Check the part number on the VIC to see if it is supported in the version of Cisco IOS software running on the router. For further assistance, contact your Cisco technical support representative.
Error Message%HDV-1-UNSUPPORTED_VIC : HDV in slot [dec]: VIC daughter card ([chars]/[hex]) is unsupported
Explanation The type of VIC that is plugged into the HDV is not supported.
Recommended Action Replace the VIC in the specified HDV slot with a type that is supported by the version of Cisco IOS software that is running on the router, or change the version of Cisco IOS software to support this type of VIC.
HDV2 Messages
The following are HDV2 network module messages.
Error Message%HDV2-1-DAUGHTER_CARD_DETECTED : HDV2 in slot [dec]: VIC card is inserted in subslot [dec], '[chars]'.
Explanation The software has detected the presence of a VIC inserted in the HDV2 port module.
Recommended Action No action is required.
Error Message%HDV2-1-DAUGHTER_CARD_FAILED : HDV2 in slot [dec]: VIC card in subslot [dec] initialization failed.
Explanation The VIC that has been plugged into the HDV2 port module could not be initialized.
Recommended Action Check the part number on the VIC to see if it is supported in the version of Cisco IOS software that is operational on the router. Ensure that the VIC is not damaged. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HDV2-1-DAUGHTER_CARD_UNKNOWN : HDV2 in slot [dec]: VIC card in subslot [dec] has an unkown id of [hex].
Explanation The software did not recognize the type of VIC that was plugged into the HDV2 port module.
Recommended Action Check the part number on the VIC to see if it is supported in the version of Cisco IOS software that is operational on the router. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HDV2-1-NO_DAUGHTER_CARD : HDV2 in slot [dec]: no VIC card is inserted in the HDV2.
Explanation The software did not detect the presence of a VIC that was inserted in the HDV2 port module.
Recommended Action Check that there is a VIC inserted properly into the HDV2. If there is a VIC properly inserted into the HDV2, check the part number on the VIC to see if it is supported in the version of Cisco IOS software that is operational on the router. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HDV2-1-NOPCIMEMORY : HDV2 in slot [dec]: No PCI memory available
Explanation The system is experiencing memory exhaustion in the PCI or packet memory. This condition is probably due to heavy traffic congestion, but could also indicate a software error.
Recommended Action Review the configuration for performance bottlenecks. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
HDX Messages
The following are messages related to half-duplex (HDX) finite state machines (FSM).
Error Message%HDX-3-BADFSM : On int [chars], unexpected state [dec], event [dec]
Explanation An invalid state or event pair has been detected in the Rx or Tx half-duplex state machine.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
HEALTH_MONITOR Messages
The following are health monitor messages.
Error Message%HEALTH_MONITOR-2-HM_RELOAD : Health Monitor is forcing a reload due to : [chars]
Explanation The health monitor is attempting to recover from a fatal error by reloading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-2-INIT_FAILURE : Init failure: [chars]
Explanation A problem occurred in the health monitor during initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-INVALID_ACTION : Invalid action
Explanation The health monitor detected an invalid action.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-INVALID_ARG_NUM : Invalid argument number [[dec]], arg num list [chars]=
Explanation An invalid argument number was passed during this event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-INVALID_CONDITION : Invalid [chars] condition
Explanation The condition specified in the message is not valid and is ignored.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-INVALID_PARAMETERS : A call to Health Monitor [chars] made with invalid parameters
Explanation A call to the health monitor contains one or more invalid parameters.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-INVALID_SEVERITY : Invalid event severity [hex]
Explanation The health monitor received an event that contained an invalid event severity. The event was not processed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-2-NO_FREE_EVENT_BUFFERS : Event pool depleted: [chars]
Explanation The event pool has been depleted. There are no free buffers to process events.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-NO_FREE_RULE_IDS : No more Rule IDs available
Explanation No more rule IDs can be allocated. The effect of this state is that health monitor rules can no longer be created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-NULL_ACTION_ROUTINE : NULL action routine invoked
Explanation The health monitor attempted to invoke an action that has a null value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-PRE_INIT_CALL : Health Monitor routine called prior to initialisation
Explanation The health monitor component was called before initialization. This error could result in the loss of vital information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-VAR_RULE_LIST_CREATE_FAILED : Variable ([chars]) rule list create failed
Explanation The health monitor could not create a rule list to be associated with a variable in the variable database.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-VAR_RULE_LIST_INSERT_FAILED : Variable ([chars]) rule list insert failed
Explanation The HM could not insert a rule into the rule list associated with a variable in the variable database.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-VAR_RULE_LIST_NOT_FOUND : Variable ([chars]) rule list not found
Explanation The rule list associated with a variable in the variable database cannot be found.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-VARIABLE_CREATE_FAILED : [chars] variable ([chars]) creation failed: [chars]
Explanation The request to create a variable in the variable database has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-VARIABLE_DBASE_CREATE_FAILED : Variable database create failed
Explanation The system failed to create the linked list used as the variable database. No variables can be created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-VARIABLE_DELETE_FAILED : [chars] variable ([chars]) deletion failed: [chars]
Explanation The request to delete a variable from the variable database has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-VARIABLE_READ_FAILED : Variable ([chars]) read failed: [chars]
Explanation The request to read from a variable in the variable database has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HEALTH_MONITOR-3-VARIABLE_WRITE_FAILED : Variable ([chars]) write failed: [chars]
Explanation The request to write to a variable in the variable database has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
HEARTBEAT Messages
The following are heartbeat messages.
Error Message%HEARTBEAT-6-NOT_HEARD : Heartbeat messages have not been heard for [dec] seconds
Explanation Heartbeats have not been heard for a significant amount of time. It is likely that a timeout will occur soon that will 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] [int]] [[chars] [int]] [[chars] [int]]
Explanation Heartbeats have not been sent for a significant amount of time. It is likely that a timeout will occur soon that will reset the system.
Recommended Action No action is required.
Error Message%HEARTBEAT-3-TIMED_OUT : Heartbeat messages have failed, resetting system
Explanation Heartbeat messages have failed and the system is no longer operational.
Recommended Action No action is required.
HHM Messages
The following are Cisco AS5400 health monitor messages.
Error Message%HHM-3-INTFWEDGE : [chars] [chars]
Explanation The interface hold queues have reached their limit and are stuck. Packets cannot be transmitted in or out of this interface.
Recommended Action Collect the interface-related information and reset the interface. Clear the counters of the interface to retransmit the packets. If the problem 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HHM-1-PROCFAIL : [chars]
Explanation During system initialization, the system was unable to create the periodic check process for the Cisco AS5400 health monitor because of a low-memory condition. The router memory has been exhausted or the memory may be fragmented. This condition may be caused by the current system configuration, the network environment, or a software error.
Recommended Action Check the minimum memory requirements for your system configuration. If a memory problem is suspected, reduce other activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.If your system meets the minimum memory requirements, this message is most likely caused by a software failure. If the problem persists, copy the error message text exactly as it appears on the console or in the system log. Enter the show tech-support, show log, show process memory and show memory summary commands. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
HIFN79XX Messages
The following are Hifn 79xx (a hardware accelerator for IP Security) driver-specific messages.
Error Message%HIFN79XX-1-ALIGN : Alignment failure on packet buffer: [hex]
Explanation A software error has occurred. The Hifn 79xx driver has detected that the buffer is not correctly aligned.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-3-CMD_ERR : Hifn 79XX command returned error: ([hex])
Explanation The Hifn 79xx driver has returned an error code while processing a command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-1-ERROR : [chars]
Explanation An error has occurred in the Hifn79xx driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-1-HIFN79XX_PROC_ALIGN : Hifn 79XX Command Processor alignment error: ([chars]=[hex])
Explanation A Hifn 79xx driver command processor alignment error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-3-HIFN79XX_PROC_ERR : Hifn 79XX Command Processor error: ([chars])
Explanation A Hifn 79xx command processor error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-1-HIFN79XX_PROC_INIT : Hifn 79XX Command Processor initialization failed: ([chars])
Explanation The Hifn 79xx driver command processor initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-1-INITFAIL : [chars]
Explanation The Hifn 79xx driver failed to initialize at the point specified in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-1-NOMEMORY : [chars] creation failed
Explanation The Hifn 79xx driver could not allocate memory for the specified data structure.
Recommended Action Consider adding more memory. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-3-NVRAMFAIL : Hifn 79XX could not read its own NVRAM configuration: ([dec])
Explanation A Hifn 79xx driver NVRAM error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-1-OWNER : [chars] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The Hifn 79xx driver detected that the buffer ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-1-PKTENGREQCOUNT_ERROR : Hifn79xx PktEngReqCount = [dec] is not valid.
Explanation The Hifn79xx packet-engine request for a count-range is from zero to four. The value specified in the error message is out of the range of zero to four.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-1-PKTENGREQCOUNT_ERROR1 : Hifn79xx PktEngReqCount = [dec] is not valid.
Explanation The Hifn79xx packet engine request count should be less than four. The value specified in the error message is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-1-PKTENGRESULT_ERROR : Hifn79xx PktEngEntry->Result.destinationCount = [hex] and the result_len [hex] don't match
Explanation The Hifn79xx packet engine failed during a length-check operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-1-PKTENGRET_ERROR : Hifn79xx PktEng Return Value = [hex], [chars].
Explanation This message provides a Hifn79xx packet-engine return-code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-6-SHUTDOWN : [chars] shutting down
Explanation The specified Hifn 79xx driver is shutting down. It may have been physically removed.
Recommended Action This is an informational message only and occurs in normal operation. No action is required.
Error Message%HIFN79XX-1-TOOBIG : [chars] received a packet with size [dec].
Explanation The Hifn79xx driver has received a packet that exceeds the MTU.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HIFN79XX-1-TOOLKIT_ERROR : hifn79xxUnitId = [dec], exceptionInformation = [dec].
Explanation The Hifn79xx toolkit has reported an unexpected internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
HMM_ASYNC Messages
The following are hex modem network module asynchronous driver messages.
Error Message%HMM_ASYNC-3-CARD_FAILED_DOWNLOAD : Unable to download firmware image to digital modem card in slot [dec].
Explanation An attempt to bring up the processor on the digital modem card has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-HMM_HARDWARE_EXCEPTION : HMM: Digital Modem Card [dec] hardware exception : [chars]
Explanation An intermittent or permanent hardware failure may have occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-MODEM_FAILED_DIAGS : Digital modem [dec]/[dec] on Simm [dec] failed power on diagnostics.
Explanation The digital modem has failed to pass power on diagnostics and will not be used.
Recommended Action If the remaining SIMMs passed the diagnostics, remove or replace the defective SIMM before continuing. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-MODEM_MAILBOX_IS_FULL : HMM Modem [dec]/[dec] Mailbox is Full, command [hex] not sent.
Explanation An error has occurred during an attempt to deliver commands to the modem module. This failure might be temporary. If this message repeats every 30 seconds, it can indicate a failed modem module.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-MODEM_STOPPED_PROCESSING_MAIL : HMM Modem [dec]/[dec] failed to accept a new command.
Explanation The modem has failed to accept a new command. This failure might be temporary, or the modem can remain unusable until a system reset is performed.
Recommended Action Reset the modem by issuing the clear modem slot/port command. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-NOMEMORY : No memory for [chars] of unit [dec]
Explanation The router does not have enough memory to perform the requested function.
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-4-NO_MODEMS_PRESENT : HMM Digital Modem Card [dec] contains no active modems.
Explanation There are no modems installed on the network module.
Recommended Action Ensure that the network module contains properly installed MICA-6DM SIMMs.
Error Message%HMM_ASYNC-3-NORAWRXPOOL : Unable to create pool for [dec] raw Rx mode buffers
Explanation The router does not have enough I/O memory for the buffers.
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-NORAWTXPOOL : Unable to creaet pool [dec] raw Tx mode buffers
Explanation The router does not have enough I/O memory for the buffers.
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-NOTTYCREATE : Unable to create TTY structure for line [dec]
Explanation The system was unable to create a tty line control block for the specified line. This condition might have occurred because there is not enough memory in the router.
Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-SIMM_FAILED_DOWNLOAD : Unable to download modem firmware image to Simm [dec] in slot [dec].
Explanation The modem firmware has failed to load into the SIMM.
Recommended Action If the firmware has successfully loaded into remaining SIMMs, remove or replace the defective SIMM before continuing. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-SIMM_RUNTIME_ERROR : Simm [dec] in slot [dec] has halted due to a Runtime Error.
Explanation The portware running on the SIMM was halted because of a runtime error. The six modems contained on the SIMM have been marked "bad" and are no longer usable until the system is reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log along with the output of the show modem and show modem log commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-TDM_SYNTHESIS_ERROR : HMM Digital Modem Card [dec] experienced a TDM Synthesis Error.
Explanation The digital modem card has failed to send or receive PCM data in time to avoid data loss. This condition can cause the modems to speed shift, retrain, or hang up.
Recommended Action Verify that the DS1 interfaces share a common clock source. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-UNKNOWN_MESSAGE : Received unknown message [hex] at mail offset [dec] from modem [dec]/[dec].
Explanation An unidentified message has been received from the modem. This condition is a symptom of running an incompatible version of modem firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HMM_ASYNC-3-UNKNOWNPLATFORM : Unknown Platform type to support HMM Network Module
Explanation The network module is not compatible with the current platform into which it is plugged.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
HOOD Messages
The following are LAN controller 100VG-AnyLAN interface messages.
Error Message%HOOD-3-BADUNIT : Bad unit number [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HOOD-5-CABLEERR : Unit [dec], HP100VG, cable error. Training failed
Explanation A 100VG cable or hub is faulty.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HOOD-5-COLL : Unit [dec], excessive collisions
Explanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged.
Recommended Action If the transceiver appears to be properly terminated, repair or replace the router.
Error Message%HOOD-5-LOSTCARR : Unit [dec], lost carrier. Transceiver problem?
Explanation An Ethernet transceiver is unplugged or defective.
Recommended Action Repair or replace the controller.
Error Message%HOOD-5-NOCABLE : Unit [dec], HP100VG, no tone detected. Check cable, hub
Explanation A 100VG cable is defective.
Recommended Action If this message recurs and either the cable or the hub appears to function, repair or replace the router module.
HP100VG Messages
The following are 100VG-AnyLAN port adapter driver messages.
Error Message%HP100VG-1-ACCESS : [chars] access to network denied
Explanation Access to the network is denied because of an incompatible configuration.
Recommended Action Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration.
Error Message%HP100VG-5-CABLEERR : [chars] training failed
Explanation A 100VG cable or hub is faulty.
Recommended Action Repair or replace the cable or hub. If either the cable or the hub appear to function, repair or replace the VG PA interface module.
Error Message%HP100VG-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay
Explanation No VG interface was detected.
Recommended Action Ensure that the 100VG PA is properly seated in the slot. Otherwise, repair or replace the 100VG PA interface module.
Error Message%HP100VG-1-DUPMAC : On [chars] LAN segment
Explanation Two VG devices on the same LAN segment have the same MAC address.
Recommended Action Check the router configuration to ensure that no duplicate MAC address is configured.
Error Message%HP100VG-1-LANCNF : [chars] configuration not compatible with the network
Explanation The configuration of the router module is not compatible with the network.
Recommended Action Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration.
Error Message%HP100VG-5-LOSTCARR : [chars] cable/hub problem?
Explanation The VG controller has detected that a link to the hub is down because of a cable, hub or VG controller problem.
Recommended Action Repair or replace the cable or hub. If either the cable or the hub appear to be functioning, repair or replace the VG PA interface module.
Error Message%HP100VG-5-NOCABLE : [chars] cable fault; tone not detected
Explanation A 100VG cable is faulty.
Recommended Action Repair or replace the cable. If the cable appears to be functioning, repair or replace the VG PA interface module.
Error Message%HP100VG-3-NOCAM : [chars] hardware CAM device not found
Explanation The hardware CAM could not be found on the PA module.
Recommended Action Repair or replace the 100VG PA interface module.
Error Message%HP100VG-3-NOTHP100VG : Bay [dec] device ID seen as [hex], expected [hex]
Explanation The 100VG PCI device could not be found.
Recommended Action Ensure that the 100VG PA device is properly seated in the slot. Otherwise, repair or replace the 100VG PA interface module.
Error Message%HP100VG-3-OWNERR : [chars] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The HP100VG driver detected that the buffer ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HP100VG-1-TRAINFAIL : [chars] unable to login to the hub
Explanation An attempt to log in to the hub has failed.
Recommended Action Take action based on the error messages that follow this message.
HPI Messages
The following are HPI messages.
Error Message%HPI-3-CODEC_NOT_LOADED : channel:[chars] DSP ID:[hex], command failed as codec not loaded [dec]
Explanation A message was sent to the DSP without a codec being loaded. This condition can result in failure of the DSP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HPI-3-FAILED_START : channel:[chars] DSP ID:[hex], failed mode [dec] for service [dec]
Explanation DSP services could not be started.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HPI-4-INVALID_CODEC_LOAD : channel:[chars] DSP ID:[hex], invalid hpi mode [dec] for loading codec [dec]
Explanation An attempt was made to load the codec while the DSP is in an invalid mode. This condition can result in failure of the DSP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HPI-4-INVALID_ECAN_TYPE : [chars] ECAN is not available in voice-card [dec], [chars] ECAN will be used
Explanation All voice cards that are participating in DSPFARM must have the same echo canceller type.
Recommended Action Ensure that all voice cards that are participating in DSPFARM have the same echo canceller type configured.
Error Message%HPI-3-INVALID_PAYLOAD : wrong payload size, channel:[chars] DSP ID:[hex], failed mode [dec] for service [dec]
Explanation DSP services could not be started.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HPI-4-NO_CLOSE : channel:[chars] DSP ID:[hex]
Explanation An attempt was made to release a DSP without sending a "close" message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
HSRP Messages
The following are Hot Standby Router Protocol (HSRP) messages.
Error Message%HSRP-4-BADAUTH : Bad authentication from [IP_address], group [dec], remote state [chars]
Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Use the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is being reported.
Error Message%HSRP-4-BADAUTH2 : Bad authentication from [IP_address]
Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Enter the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported.
Error Message%HSRP-4-DIFFVIP1 : [chars] Grp [dec] active routers virtual IP address [IP_address] is different to the locally configured address [IP_address]
Explanation The HSRP virtual IP address contained in the hello message from the active router is different from the locally configured IP address.
Recommended Action Check the configuration on all HSRP routers.
Error Message%HSRP-4-DUPADDR : Duplicate address [IP_address] on [chars], sourced by [enet]
Explanation The IP address in an HSRP message received on the interface is the same as the IP address of the router. This condition may be caused by a misconfiguration or a malfunctioning switch.
Recommended Action Check the configurations on all the HSRP routers and ensure that any switches you have are functioning properly.
Error Message%HSRP-4-DUPVIP1 : [chars] Grp [dec] address [IP_address] is
already assigned to [chars] group [dec]Explanation The HSRP virtual IP address contained in the hello message cannot be learned because it is already assigned to a different HSRP group.
Recommended Action Check the configuration on all HSRP routers.
Error Message%HSRP-4-DUPVIP2 : [chars] Grp [dec] address [IP_address] is
already assigned on this interfaceExplanation The HSRP virtual IP address contained in the hello message cannot be learned because it is already assigned to this interface.
Recommended Action Check the configuration on all HSRP routers.
Error Message%HSRP-4-DUPVIP3 : [chars] Grp [dec] address [IP_address] is
already assigned to, or overlaps with, an address on
another interface or applicationExplanation The HSRP virtual IP address contained in the hello message cannot be learned because it is already assigned to, or overlaps with, an address on another interface or application.
Recommended Action Check the configuration on all HSRP routers.
Error Message%HSRP-3-MISCONFIG : Attempt to change [chars] MAC address to [enet] when DECNET already running
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HSRP-3-NOSOCKET : Unable to open socket
Explanation The system was unable to initialize an IP connection for the hot standby protocol.
Recommended Action Make sure that there is at least one interface is configured to run IP.
Error Message%HSRP-6-STATECHANGE : [chars] Grp [dec] state [chars] -> [chars]
Explanation The router has changed state.
Recommended Action No action is required.
HTSP Messages
The following are analog voice hardware adaptation layer software messages.
Error Message%HTSP-3-CAPABILITYMISMATCH : voice port [chars]: call connection id [[hex] [hex] [hex] [hex]]
Explanation The capabilities between the two call legs did not match. The capabilities are negotiated between call legs for codec, VAD, and fax rates.
Recommended Action Check that the dial peer configuration is appropriate for the interface in question. Also check that the configuration on the interface is correct.
Error Message%HTSP-3-DSPALARM : voice port [chars]: status=[hex] message=[hex] text=[chars]
Explanation The DSP has reported a fatal error. All calls on the DSP were dropped, and a DSP reload was attempted.
Recommended Action Verify that the DSP reloaded properly by attempting to place a call on the specified voice port. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HTSP-3-NOEVENT : no free event structure available from [chars] for DSP message
Explanation No event structures were remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Check that the voice port for which the event was reported is still operational. If it is not still operational, clear the voice port.
Error Message%HTSP-3-TRUNKNOTSUPPORTED : voice port [chars]: Ground Start trunking not supported
Explanation The specified voice port does not support the connection trunk command when ground start signaling is configured. Trunking mode on this voice is supported when loop-start signaling is used.
Recommended Action Shut down the voice port, remove the connection trunk or signal ground-start command from the voice port configuration, and restart (unshut) the voice port.
Error Message%HTSP-5-UPDOWN : Trunk port(channel) [[chars]] is [chars]
Explanation The trunk port:channel has changed state.
Recommended Action No action is required.
HTTP Messages
The following are HTTP messages.
Error Message%HTTP-3-INIT_FAIL : HTTP Process Init failed.
Explanation Initialization of the HTTP subsystem has failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%HTTP-3-OUTOF_MEM : HTTP out of memory.
Explanation An error occurred during initialization of the HTTP process. The HTTP process could not create crucial internal data structures that are required for operation of the HTTP subsystem. The most likely reason for this condition is exhaustion of system memory.
Recommended Action Reduce other system activity to ease memory demands. if conditions warrant, upgrade to a larger memory configuration.
Error Message%HTTP-3-PROC_NOCREAT : Unable to create HTTP process.
Explanation An error occurred during initialization of the HTTP process. The HTTP process that processes all HTTP requests and responses could not be created.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%HTTP-6-SERVER_SETUP_FAILED : Server setup failed
Explanation Setup of the HTTP or HTTPS server to listen on the specified port number has failed.
Recommended Action Disable the server, verify that the port number is correct, and enable the server. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
HTTPC Messages
The following are HTTP Client messages.
Error Message%HTTPC-6-CLOSE_SRV_CONNECT : The connection to server [IP_address] appears to be hung and will be closed.
Explanation Messages are being backed up in the write queue of the HTTP client in the connection with the specified server. The connection is assumed to have failed, and the HTTP client is closing the connection.
Recommended Action Check with the specified server for a possible connection error.
Error Message%HTTPC-3-CONNECT_NULL : NULL connection structure for fd([dec]) - closing socket.
Explanation The HTTP client is receiving a read event from the socket, but the client cannot locate the connection structure for the file descriptor. If this condition is detected continuously in a loop, it indicates a problem with the socket code. Since the socket should be closed immediately after the read event, the HTTP client should not be receiving any additional read events.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HTTPC-3-COOKIE_MEM : HTTP Client runs out of allowable memory to store cookies.
Explanation The total memory allocated for storing cookies has run out. All cookies received from the HTTP server will be dropped. Users may no longer be able to interact with a session-based origin server until memory is freed up.
Recommended Action Users may want to try their requests at a later time or contact the system administrator to increase the maximum RAM that is allowed for saving HTTP cookies.
Error Message%HTTPC-3-RECEIVE_SOCK_READ_EVENT_WHILE_DISABLED : Received socket read event while read interest is disabled callID([dec]) fd([dec]) - closing socket.
Explanation The HTTP client is receiving a read event from the socket while the read interest is being disabled. This condition indicates a problem between the HTTP client and the socket interface.
Recommended Action Record the error and report it to the system administrator.
HUB Messages
The following are Cisco Ethernet hub messages.
Error Message%HUB-1-BADHUB : Invalid hub type [dec] and number [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HUB-1-BADUNIT : Bad port number [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HUB-1-NOMEMORY : Unit [dec], no memory for [chars]
Explanation The system has detected that there is not enough memory for the hub initialization.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%HUB-1-READERR : Read op [dec] not allowed
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%HUB-1-WRITEERR : Write op [dec] not allowed
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, contact your Cisco technical support representative, and provide the representative with the gathered information.
HW_VPN Messages
The following are Encryption Advanced Interface Module (EAIM) messages. EAIM is a hardware accelerator for IPSec encryption services.
Error MessageExplanation The POST has reported an incorrect memory size.
Recommended Action Replace the EAIM.
Error Message%HW_VPN-1-BADTYPE : This Encryption AIM type not supported on this router platform
Explanation An EAIM that is not supported on this router platform has been installed. Different EAIMs are supported by each router platform.
Recommended Action Remove the EAIM and install an EAIM that is compatible with this router.
Error Message%HW_VPN-1-BUSY : Encryption AIM busy
Explanation The EAIM cannot perform the requested command because it is busy executing another command.
Recommended Action Wait until the current command has completed. If the current command does not complete in a reasonable amount of time, the EAIM is defective. Replace the EAIM.
Error Message%HW_VPN-1-CMDERR : [chars]: Command [hex] failed with status [hex]
Explanation The EAIM has responded that the current requested command contains an error, and the command has failed. The details of the failure depend upon the circumstances, but it is likely that the EAIM is defective and should be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. The EAIM will most likely need to be replaced.
Error Message%HW_VPN-1-CMDTIMEOUT : [chars]: Timeout on reply to command to Encryption AIM
Explanation The EAIM has not responded to the current requested command in a reasonable amount of time. The EAIM is faulty and should be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. The EAIM will most likely need to be replaced.
Error Message%HW_VPN-1-DEVID : EAIM: Invalid PCI device ID: [int]
Explanation The identity of the EAIM device on the router bus is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. The EAIM will need to be replaced.
Error Message%HW_VPN-1-DEVINIT : EAIM: Device Initialization failure
Explanation The EAIM has failed to respond properly to an initialization attempt.
Recommended Action Replace the EAIM.
Error Message%HW_VPN-6-DISABLED : [chars]: disabled
Explanation The EAIM has been disabled.
Recommended Action Replace the EAIM.
Error Message%HW_VPN-1-ELMERREV : AIM in slot [int] not supported by this HW revision.
Explanation The revision level of the C2600 PLD does not support EAIM. The PLD needs to be upgraded to a later version of software.
Recommended Action Upgrade the PLD software to a later version that supports EAIM.
Error Message%HW_VPN-1-HELLOERR : [chars]: VPN_HW responded incorrectly to hello: received [hex] expected [hex]
Explanation A command was sent to the Encryption AIM, and it was expected to echo back the data that was sent to it. Instead of receiving the expected data, the data specified in the error message was received instead.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. The EAIM will most likely need to be replaced.
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 may occur during the normal operation of the system, or it may occur during the transition to a new session key for a security association. In such cases, it may be ignored. However, if it happens frequently, or is associated with traffic disruption, make a note of the status value and contact your Cisco technical support representative. The EAIM will most likely need to be replaced.
Error Message%HW_VPN-1-INITFAIL : EAIM: Initialization failed at [chars]
Explanation The EAIM device did not reset properly. This condition is indicative of a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. The EAIM will need to be replaced.
Error Message%HW_VPN-1-LPRXERR : [chars]: Command Error IPSEC cmd=[chars][[hex]] Uproc cmd=[chars][[dec]] status=[chars][[hex]]
Explanation An error has occurred during the execution of a key management command by the EAIM.
Recommended Action The EAIM may require replacement. Make a note of the status value, and contact your Cisco technical support representative.
Error Message%HW_VPN-1-NOHW : Encryption AIM not present in system
Explanation The user entered a command that involves an EAIM, but no EAIM is present in the system.
Recommended Action Do not enter EAIM commands unless an EAIM is present. If an EAIM is installed, replace the EAIM.
Error Message%HW_VPN-1-POSTFAIL : [chars]: Power On Self Test failed, failed test = [chars]
Explanation The VPN module failed the power-on self-test.
Recommended Action Replace the VPN module.
Error Message%HW_VPN-6-STARTUP : [chars]: starting up
Explanation The specified EAIM has initialized successfully.
Recommended Action This is an informational message only. No action is required.
Error Message%HW_VPN-1-UNEXPCMD : [chars]: Invalid command reply: expected [hex] received [hex]
Explanation A command was sent to the Encryption AIM, and its reply contained an unexpected reply code. The details of the failure depend upon the circumstances, but in all likelihood the Encryption AIM is faulty and should be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. The EAIM will most likely need to be replaced.
HWCONF Messages
The following are HW conference register/unregister messages.
Error Message%HWCONF-6-REGISTER : hwconf-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has registered.
Explanation Configed hwconf has registered.
Recommended Action No action is required.
Error Message%HWCONF-6-REGISTER_NEW : hwconf-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has registered.
Explanation A hwconf has registered. The hwconf is not yet in current running configuration.
Recommended Action No action is required.
Error Message%HWCONF-6-UNREGISTER_ABNORMAL : hwconf-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has unregistered abnormally.
Explanation A hwconf has unregistered without sending an unregister message.
Recommended Action No action is required.
Error Message%HWCONF-6-UNREGISTER_NORMAL : hwconf-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has unregistered normally.
Explanation A hwconf has successfully unregistered.
Recommended Action No action is required.
HWECAN Messages
The following are HWECAN echo canceller messages.
Error Message%HWECAN-5-DEVICE : HWECAN Device [dec] in slot [dec] [chars] [dec], changed state to [chars]
Explanation The HWECAN individual device has changed state.
Recommended Action No action is required.
Error Message%HWECAN-5-INITFAILURE : HWECAN in slot [dec] [chars] [dec], Initialization Failed: [chars]
Explanation Initialization of the HWECAN echo canceller has failed.
Recommended Action Retry the operation. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWECAN-5-INSUFFICIENT : Insufficient EC channel resource to allocate for slot [dec] port [dec] ts [dec]
Explanation A free HWECAN channel is not available for allocation to the voice channel.
Recommended Action Change the tail-length configuration to get more ECAN channels. Specify fewer time slots for voice configuration. Install or replace additional HWECAN resources to allow more complex configurations.
Error Message%HWECAN-5-NACK : HWECAN in slot [dec] [chars] [dec] NACKed the Command/Query [hex]
Explanation The command or the query is not understood by the HWECAN device.
Recommended Action Retry the query or command. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWECAN-5-NOMSGPOOL : HWECAN in slot [dec] [chars] [dec], Failed to get [chars] Msg buffer Pool
Explanation A buffer pool for Tx or Rx message communication could not be allocated.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWECAN-5-TIMEOUT : HWECAN in slot [dec] [chars] [dec] failed to return response for Command/Query [hex]
Explanation A response to the previous command was not received in a timely manner.
Recommended Action Check the status of the HWECAN echo canceller and replace it, if required.
Error Message%HWECAN-5-UPDOWN : HWECAN in slot [dec] [chars] [dec], changed state to [chars] with [dec] Channels
Explanation The HWECAN has changed state.
Recommended Action No action is required.
HWIC_1GE_SFP Messages
The following are Gigabit Ethernet High-speed WAN Interface Card (HWIC) messages.
Error Message%HWIC_1GE_SFP-3-BAD_CLOCK : PL3 clock is missing at FPGA
Explanation An attempt by MAC to acquire clocks on the system bus has failed. This condition indicates a hardware problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_1GE_SFP-3-DUPLICATE_SN : SFP in interface [chars] has the same serial number as another SFP
Explanation The serial number of the SFP matches that of another interface on the system. Cisco SFPs are assigned unique serial numbers.
Recommended Action Verify that the SFP was obtained from Cisco or a supported vendor.
Error Message%HWIC_1GE_SFP-3-ID_MISMATCH : SFP in interface [chars] failed identification check
Explanation The system was unable to verify the identity of the SFP.
Recommended Action Verify that the SFP was obtained from Cisco or from a supported vendor. Use the Cisco Software Advisor tool to check if the Cisco IOS software that is running on the system supports the SFP. If the SFP is newer, a system software upgrade might be required.
Error Message%HWIC_1GE_SFP-3-INVALID_FPGA_VER : Incorrect FPGA version. Expected [hex] Read [hex]\n
Explanation One or more of the following errors have occurred:
–
–
–
Recommended Action Attempt to reload the router. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_1GE_SFP-1-NOMEMORY : HWIC_1GE_SFP [dec]: Memory allocation failure; could not allocate [chars]
Explanation An attempt to allocate memory for the specified HWIC-1GE-SFP has failed.
Recommended Action Additional RAM may be required in order to execute this image. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_1GE_SFP-3-SFP_BAD_CC : Interface [chars] SFP [chars] ID fields check sum failed.
Explanation The specified SFP ID fields failed a checksum operation.
Recommended Action Reinsert or replace the SFP.
Error Message%HWIC_1GE_SFP-6-SFP_IN : Interface [chars] [chars] SFP has been inserted.
Explanation An HWIC-1GE-SFP interface SFP has been inserted.
Recommended Action No action is required.
Error Message%HWIC_1GE_SFP-4-SFP_INTERR : Interface [chars] internal error occurred in setup for SFP
Explanation The system could not allocate resources, or had some other problem, while the specified SFP interface was being set up.
Recommended Action Reload the system. If the problem 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_1GE_SFP-6-SFP_OUT : Interface [chars] SFP has been removed.
Explanation An HWIC-1GE-SFP interface SFP has been removed.
Recommended Action No action is required.
Error Message%HWIC_1GE_SFP-6-STARTUP : [chars] initialized
Explanation The specified HWIC-1GE-SFP has initialized successfully.
Recommended Action No action is required.
Error Message%HWIC_1GE_SFP-3-UNRECOGNIZED_VENDOR : SFP in interface [chars] is manufactured by an unrecognized vendor
Explanation The system was unable to match the SFP manufacturer with one on the known list of Cisco SFP vendors.
Recommended Action Verify that the SFP was obtained from Cisco or a supported vendor. Use the Software Advisor tool to check if the Cisco IOS software running on the system supports the SFP. If the SFP is newer, a system software upgrade might be required.
Error Message%HWIC_1GE_SFP-3-VN_DATA_CRC_ERROR : SFP in interface [chars] has bad crc
Explanation The SFP does not contain a valid CRC in the EEPROM data.
Recommended Action Reinsert or replace the SFP.
HWIC_CELL Messages
The following are Cellular High-Speed WAN Interface Card driver messages.
Error Message%HWIC_CELL-1-FPGA_DNLD_FAIL : FPGA download failed for NM slot [dec] HWIC slot [dec][chars]
Explanation The firmware/FPGA download failed for the specified device.
Recommended Action If this message recurs, provide the following:
LOG_STD_SH_CMD_ACTION
The output of the show cellular <xxx> and show tech support commands.Error Message%HWIC_CELL-1-MGMT_ERROR : Error response received from modem [dec]
Explanation The host has received an error from the modem.
Recommended Action LOG_STD_ACTION.
HWIC_HOST Messages
The following are High-speed WAN Interface Card (HWIC) host driver library messages.
Error Message%HWIC_HOST-1-BAD_HWIC_INT : HWIC_HOST: Invalid Interrupt Table [dec]
Explanation The interrupt table number is not supported by the HWIC library. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-BAD_HWIC_INTERFACE_NUM : HWIC_HOST: Invalid Interface Number [dec]
Explanation The HWIC Library API function does not recognize this interface. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-BAD_HWIC_SLOT : HWIC_HOST: Invalid HWIC slot [dec]
Explanation The HWIC slot is not supported on this platform. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-BAD_IDB : HWIC_HOST: Invalid Interface Descriptor Block [hex]
Explanation The IDB that was passed to an HWIC host driver library API is of a null value or contains invalid null pointers. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-DMA_ERROR : HWIC_HOST: Host termination logic experienced a DMA error for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered an HWIC read or write error for the interface described by the IDB. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-REG_RW_ERROR : HWIC_HOST: Host termination logic experienced an HWIC read/write error for Interface Descriptor Bl \nock [hex]
Explanation The host termination logic has encountered an HWIC read or write error for the interface specified by the IDB. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-REG_RW_TIMEOUT_ERROR : HWIC_HOST: Host termination logic experienced an HWIC read/write timeout error for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered a timeout error during an HWIC read or write operation for the interface specified by the IDB. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-RXCLK_MISSING_ERROR : HWIC_HOST: The HWIC Receive Clock signal was not detected for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered a fatal error. The logic could not detect the HWIC receive clock for the interface specified by the IDB. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-RX_CRC_ERROR : HWIC_HOST: Host termination logic experienced an HWIC CRC error for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered an HWIC CRC error for the interface specified by the IDB. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-RX_DONE_ERROR : HWIC_HOST: Improper DONE bit setting in Receive Ring for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered a invalid setting for a Done bit in the buffer descriptor for the interface specified by the IDB. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-RX_FORMAT_ERROR : HWIC_HOST: Host termination logic experienced an HWIC Format error for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered an HWIC format error for the interface specified by the IDB. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-RX_OVERRUN_ERROR : HWIC_HOST: Host termination logic experienced a Receive FIFO overrun for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered a FIFO overrun during a receive operation for the interface specified by the IDB. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-TX_DONE_ERROR : HWIC_HOST: Improper DONE bit setting in Transmit Ring for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered a invalid setting for a Done bit in the buffer descriptor for the interface specified by the IDB. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%HWIC_HOST-1-TX_FIRST_LAST_ERROR : HWIC_HOST: Improper First/Last sequence in Transmit Ring for Interface Descriptor Block [hex]
Explanation The host termination logic has encountered an invalid first or last sequence in the buffer descriptor for the interface specified by the IDB. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
HWIC_SERIAL Messages
The following are High-speed WAN Interface Card (HWIC) serial device driver messages.
Error Message%HWIC_SERIAL-3-BSCHUNT : BSC HUNT cmd for int [dec]/[dec] failed
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%HWIC_SERIAL-4-DCD_CHANGE : Unexpected DCD transition interrupt on wic [dec] port [dec] occured
Explanation Unexpected event has been detected by the software. This should just be a transient condition.
Recommended Action The System should recover. No action is required.
Error Message%HWIC_SERIAL-1-DISCOVER : NM slot [dec]: only [dec] PCI dev found
Explanation Some of the interface controller devices on HWIC_SERIAL NM did not initialize properly.
Recommended Action Power down, reinsert the port module, and reboot.If this message recurs, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%HWIC_SERIAL-1-FPGA_DNLD_FAIL : FPGA download failed for NM slot [dec] HWIC slot [dec]
Explanation The firmware/FPGA download has failed for this module.
Recommended Action Check the part number on the WIC card to verify that it is supported
in the IOS release operational on the router.Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HWIC_SERIAL-4-FREQ_OUT_OF_RANGE : [chars] Frequency not in Range.
Explanation Frequency in not in range.
Recommended Action ensure that the DCE side is up and providing clock. No action is required.
Error Message%HWIC_SERIAL-3-INVALID_CABLE : [chars]: Cable connected is not supported on this interface.
Explanation The HWIC-16A supports only octal RS232 RJ45 cables. All other cables are invalid.
Recommended Action Connect the proper cable.
Error Message%HWIC_SERIAL-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. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HWIC_SERIAL-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. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HWIC_SERIAL-3-INVALID_TXRX : NM slot [dec], WIC card [dec] doesn't support different tx speed ([dec]) and rx speed ([dec])
Explanation The software does not support different TX and RX speeds.
Recommended Action Configure the TX speed and the RX speed to be equivalent.
Error Message%HWIC_SERIAL-4-MISMATCH_FREQ : [chars] Mismatch between configured and measured Freq.
Explanation There was a mismatch between the configured and the measured frequency.
Recommended Action Re-configure the clock rate network on the serial interface.
Error Message%HWIC_SERIAL-3-NOMEMORY : No memory for [char