Table Of Contents

GTP Messages

GUIDO Messages

HA Messages

HA_CLIENT Messages

HA_EM Messages

HDLC32 Messages

HDV2 Messages

HDX Messages

HEALTH_MONITOR Messages

HEARTBEAT Messages

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 been started or has shut down.

Recommended Action    If this change was intended, no action is required. 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-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. The mandatory IE contains an invalid range of values.

3. The mandatory IE is out of sequence.

4. The message format is invalid.

5. The optional IE present in the packet contains an invalid range of values.

6. The GGSN node does not support the GTP version that was received.

7. A noncharging message exists in the charging path.

8. A charging message exists in the GTP path.

9. The system received an unknown GTP message.

10. The GTP message that was received is too short to contain all expected information from the IE.

11. A unexpected message was seen.

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. The number of pending signaling messages has reached its limit.

2. The system has run out of memory. Insufficient memory is available in the GGSN.

3. A permanent system failure has occured.

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 failed at the packet parsing state for one of the following reasons:

1. A mandatory IE is missing from the PDP.

2. A mandatory IE contains an invalid value range.

3. The mandatory IEs are not in sequence.

4. The message has an invalid format.

5. The optional IE present in the packet has an invalid value range.

6. The GGSN node does not support the GTP version that was recieved.

7. A noncharging message was received in the charging path.

8. A charging message was received in the GTP path.

9. An unknown GTP message was received.

10. The GTP message that was received is too short to contain all expected information IEs.

11. An unexpected message was seen.

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-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 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-6-PDP_PURGED : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [chars]

Explanation    A PDP context has been purged because of a PDP context idle timeout.

Recommended Action    This is an informational message only. No action is required.

Error Message     

%GTP-4-RECOVERYIEDIFF : GSN: [IP_address], TID: [hex][hex], APN: [chars], Reason: [chars]

Explanation    GGSN has recieved a PDP update request in the same path that contains a different Recovery Information Element.

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.

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.

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.

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 half-duplex (HDX) finite state machines (FSM) messages.

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.