-
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]