-
Cisco IOS XR System Error Message Reference Guide, Release 3.5
-
Preface
-
Overview
-
Access Control List (ACL) Messages
-
Diagnostic Messages
-
Fabric Messages
-
Forwarding Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 Messages
-
Layer 2 Messages
-
Layer 3 Messages
-
Manageability (MGBL) Messages
-
Media Messages
-
Operating System (OS) Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service (QoS) Messages
-
Routing Messages
-
Security Messages
-
Services Messages
-
Simple Network Management Protocol (SNMP) Messages
-
System Database Messages
-
Feedback
Table Of Contents
High Availability (HA) Messages
High Availability (HA) Messages
This section contains all High Availability related System Error Messages. The following facility codes are represented in this module:
CHKPT_BASIC Messages
Error Message%HA-CHKPT_BASIC-7-COLD_RESTART Process has been restarted without checkpoint data due to request from sysmgr
Explanation Due to too many contiguous failed restarts, sysmgr has requested that the process be restarted without checkpoint data.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-COLD_RESTART_IGNORED Ignoring sysmgr cold restart flag
Explanation The process has failed to restart multiple times. By design, the process will continue to restart with its existing checkpoint data.
Recommended Action Analyze the restart failure and take appropriate recovery action.
Error Message%HA-CHKPT_BASIC-7-DEBUG_REGISTER Debug register failed ([hex]): [chars]
Explanation Registration of debug services failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-CHKPT_BASIC-7-DUP_KEY [chars]: User key [dec] is in use by object [hex] in table [hex]
Explanation A client of the checkpoint library attempted to create an object with a key that was already in use.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-INIT_ERROR initialization error: [chars]: [dec] ([chars])
Explanation An error was encountered during intialization of the checkpoint library. The message should indicate the error condition. This is most likely due to a coding error.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-NOT_IMPLEMENTED function not implemented yet: [chars]
Explanation Unimplemented functionality.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-REGISTRATION Error during table registration: [chars]: name: [dec] version: [dec]
Explanation An error was encountered during table registration. The message should indicate the error condition. This is most likely due to a coding error.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-SYSERR OS/System error: [chars]: [dec] ([chars])
Explanation This message signals an unrecoverable condition reported from the underlying system services. The severity of such errors cannot be determined locally by Checkpointing, so it treats them all such conditions as non-fatal, transient errors. The chkpt user must abort its immediate operation.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere.
Recommended Action Collect system log information. No action is required.
Error Message%HA-CHKPT_BASIC-7-WARNING Warning: [chars]: [chars]: [dec]
Explanation This provides information about non-error conditions which may even be expected under certain circumstances. Nevertheless, these are not considered 'desirable' conditions.
Recommended Action Collect system log information. No action is required.
CHKPT_CLI Messages
Error Message%HA-CHKPT_CLI-7-BAD_BUFFER A client library returned an empty buffer: [chars] [chars]
Explanation A NULL pointer was encountered unexpectedly.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_CLI-7-BUFFER_MISMATCH Buffer size mismatch: [dec]: [dec]
Explanation A NULL pointer was encountered unexpectedly.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_CLI-7-INVALID_ARG An invalid argument was passed: [chars]
Explanation An argument was passed with an invalid value.
Recommended Action Collect system log information.
CHKPT_HEAP Messages
Error Message%HA-CHKPT_HEAP-7-BAD_HEAPIDX heap index [hex] (seg [dec] offset [dec] segsize [dec]) cannot be mapped to segment pointer
Explanation Internally heap pointers are kept as offset indices. A given heap index was found to be outside the heap.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-BAD_HEAPPAGE Bad heap page block pointer: [chars]: [pointer]
Explanation A heap page address is misaligned or lies in some invalid range.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-BAD_HEAPPTR heap pointer cannot be mapped to segment offset: [pointer]
Explanation Internally heap pointers are kept as offset indices. A given heap pointer was found to be outside the heap.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-BAD_NCTDELETE Bad record pointer to free ([char]): [pointer]
Explanation Bad NCT record is being freed.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-CORRUPTION Checkpoint heap corruption was detected ([chars]). Process will be cold restarted.
Explanation The process crashed during checkpoint heap modification, resulting in an unrecoverable heap. Process will be started from an empty heap.
Recommended Action Collect system log information. No action is required.
Error Message%HA-CHKPT_HEAP-7-DATA_CORRUPTION Data corruption: [chars]: 0x[dec], 0x[dec], 0x[dec], 0x[dec]
Explanation Data corruption is detected in checkpointing data structures. This will generally result in a single process failure.
Recommended Action Collect system log information. No action is required.
Error Message%HA-CHKPT_HEAP-7-MUNMAP unmap and reserve failed: addr [hex] len [dec], [chars]
Explanation When attempting to free memory that is no longer in use, the checkpoint library received an error from the kernel.
Recommended Action Collect system log information and forward to technical support.
Error Message%HA-CHKPT_HEAP-7-NCT_BIGNEW NCT: requested size too large: [dec]
Explanation Higher layers of heap are requesting a size for a variable-size record that is too large.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-OBJ_NOT_FOUND Objid [hex] in table [hex] could not be found
Explanation The object could not be found in the given table when attempting to map the object ID to a memory address.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-PROC_RUNNING checkpoint segment operation failed: Process [chars] tag [chars] is running on node [chars].
Explanation A request to move or copy checkpoint data from one node to another has failed because an instance of the process is running on the destination node.
Recommended Action Determine why the process is running on the destination node.
Error Message%HA-CHKPT_HEAP-7-SEGMENT_RENAMED Checkpoint file [chars] has been renamed to [chars] for later analysis due to corruption found during restart.
Explanation A corrupted checkpoint segment has been renamed for later analysis.
Recommended Action Collect system log information. No action is required.
Error Message%HA-CHKPT_HEAP-7-TBL_OBJ_SEG_MISMATCH Tblid [hex] objid [hex] segment mismatch (tbl-seg [dec] obj-seg [dec])
Explanation When the table ID and object ID are mapped to segment numbers, they do not match. Since an object belongs to a table and therefore resides in the same segment, this indicates a coding error.
Recommended Action No action is required.
CHKPT_LIB_COMMS Messages
Error Message%HA-CHKPT_LIB_COMMS-3-SYSTEM_ERROR [chars]: [chars] failed with error [hex]
Explanation A call to a system function failed with the specified error code.
Recommended Action No action is required.
Error Message%HA-CHKPT_LIB_COMMS-6-INFO [chars]:[dec]
Explanation Internal Information messages
Recommended Action No action is required.
Error Message%HA-CHKPT_LIB_COMMS-7-DEBUG [chars]
Explanation Internal Debug Messages
Recommended Action No action is required.
CHKPT_MESSAGING Messages
Error Message%HA-CHKPT_MESSAGING-3-IDT_FAILED Checkpoint Initial Data Transfer failed at [chars] with status code [hex]
Explanation An error occurred during checkpoint Initial Data Transfer which resulted in its failure. A retry of IDT will happen automatically.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BAD_MSGLEN [chars]: message lengths invalid (msglen [dec] srcmsglen [dec] error [hex] ([chars])
Explanation The source message length is less than the message length. This is a situation which should never happen.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BAD_MSGTYPE [chars]: message type [dec] invalid; error [hex] ([chars])
Explanation The message type has the checkpoint component ID, but does not have a message type in the correct range. This is a situation which should never happen.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BAD_REQUEST [chars]: Bad request type [dec] msglen [dec]
Explanation A bad message request was received by the event handler function.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BAD_SEQNO [chars]: request type [dec] had sequence number [dec] (expected [dec])
Explanation The mirroring request had an incorrect sequence number. This indicates either an algorithm error, or data corruption on the active node or in the data transfer between nodes. Initial Data Transfer will be redone, and no data loss should occur.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BAD_TOTALSIZE [chars]: msg totalsize ([dec]) != srcmsglen ([dec] error [hex] ([chars])
Explanation The message header totalsize value must be equal to the source message length. If not, this indicates an IPC or coding error.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BUFFER_TOO_SMALL Checkpoint library message buffer must be at least [dec] bytes; [dec] bytes is too small for correct operation.
Explanation The message buffer assigned to the checkpoint library by the application is less than the minimum size for successful messaging functionality. The application should increase the size of its event manager message buffer.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-DUPLICATE_PROCESS [chars]: process name [chars] tag [chars] is already running - this should not happen: aborting
Explanation An attempt to exclusive-create on a local channel failed. This indicates that there's already a copy of this same process running, and it cannot be allowed to continue, since corruption can result.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-EVENT_MANAGER [chars]: call to [chars] failed with errno [dec]
Explanation A call to an event manager function failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-GET_MSGLEN [chars]: [chars] failed with error [hex] ([chars])
Explanation Extracting message or source message length failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-IDT_ALL_FAILED All attempts to do Initial Data Transfer to standby failed (error [hex])
Explanation Multiple attempts to transfer initial mirrored data to the standby have failed, and the attempts have been stopped.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-LWM_FAILURE [chars]: call to [chars] failed with error [hex] ([chars])
Explanation A call to a LightWeight Messaging function failed. This may be due to a server being unavailable at the time of the call.
Recommended Action Collect system log information if it appears that this message is linked with failures in functionality. Otherwise, the message can be ignored.
Error Message%HA-CHKPT_MESSAGING-7-MALLOC_FAILED [chars]: malloc of [dec] bytes failed; errno [dec]
Explanation A call to allocate memory failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-MSG_READ [chars]: msg_read (case [dec]) failed with return [dec]; status [hex] ([chars])
Explanation A msg_read call in the message handler failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-MSG_REPLY [chars]: msg_reply (reqtype [dec]) failed with errno [dec]
Explanation A msg_reply call in the message handler failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-MSG_SEND_EVENT [chars]: msg_send_event failed with return [dec]
Explanation A msg_send_event call in a checkpoint mirroring function failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-NON_CHKPT_MSG [chars]: Non-checkpoint message received: comp-id [dec]
Explanation A message request for a non-checkpoint component was received by the handler function.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-PTHREAD_FAILURE [chars]: call to [chars] failed with errno [dec]
Explanation A call to a Posix Pthreads function failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-REPLICA_NAME Replica name [chars]%s[chars] exceeded the maximum length permitted by Group Services, and has been truncated to [chars]. Replication problems may result if the truncated replica name is non-unique.
Explanation A replica name passed to the Replicator Library was truncated. This is not an issue in itself, but may cause problems further down the line, if the replica name becomes non-unique within the system.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-STANDBY_OPEN_TIMEOUT Attempts to open standby channel [chars] failed after [dec] retries - continuing
Explanation Multiple attempts to open the messasge channel to the standby node (either the application itself or the checkpoint proxy) failed due to either the proxy not running on the standby or the application itself not running on the standby. If the application should run on the standby, then it must call chkpt_init() in order for mirroring to succeed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-STANDBY_PROXY_SPAWN All attempts to spawn checkpoint proxy on the standby failed (error [hex])
Explanation Multiple attempts to spawn a copy of the checkpoint proxy for this application on the standby were done, and the attempts have been stopped.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-STBY_CAPABLE Call to sysmgr_is_standby_capable failed with error (error [hex])
Explanation The call to sysmgr_is_standby_capable failed. This may be due to the application not having a startup file, and so being unknown to sysmgr.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-SYSMGR_GET_PROC_ROLE [chars]: call to sysmgr_get_proc_role failed with status [hex] ([chars])
Explanation A call to sysmgr_get_proc_role failed with the given status.
Recommended Action Collect system log information.
CHKPT_PROXY Messages
Error Message%HA-CHKPT_PROXY-7-BAD_IPC_LENGTH IPC request type [dec] had bad length [dec] (expected [dec])
Explanation An IPC message with invalid length was received by the proxy process.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-BAD_IPC_REQUEST Bad IPC request type [dec] received with message length [dec]
Explanation An invalid IPC request type was received by the proxy process.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-DEBUG [chars]
Explanation Internal Debug Message
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-GROUP_CREATE_ERROR [chars]: a call to group_create failed with error [dec]
Explanation The proxy process uses group_create() to join the proxy control group. A call to group_create() failed with the specified error.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-IPC_ERROR [chars]: [chars] failed with error [dec]
Explanation As part of IPC operation, a call to a function failed with the specified error.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-NO_MEMORY [chars]: could not allocate [dec] bytes of memory
Explanation Memory allocation failed. This is likely to be a resource shortage rather than a coding error.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-PUTENV [chars]: a call to putenv([chars]) failed with error [dec]
Explanation The proxy process uses putenv() to communicate with the checkpoint library. A call to putenv() failed with the specified error.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-STDBY_NOPROXY Proxy not spawned for LR-plane process '[chars]' due to admin boot hold
Explanation Admin boot hold has ben set for this node (normally due to an install operation) so a chkpt_proxy has not been spawned for this process.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-SYSTEM_ERROR [chars]: [chars] failed with error [hex]
Explanation A call to a system function failed with the specified error code.
Recommended Action No action is required.
CHKPT_TDM Messages
Error Message%HA-CHKPT_TDM-7-BAD_ALIGNMENT Index not aligned: [hex]
Explanation A heap index was not word aligned.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-COLD_RESTART Cold restart: Reason: [chars]: Application [chars]: table [dec]: version [dec]
Explanation A process failed to restore state from a table in the checkpoint store.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-DUP_TABLE Duplicate table found: Application [chars], table [dec]
Explanation During registration, two copies of a table were found in the checkpoint store at the same version. This indicates corruption in the checkpoint store.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-NO_TRANSLATOR No translator found: [chars]: [chars]: [chars]
Explanation A required translator was not loaded.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-NOT_INDEXED unable to setup index structure for indexed table: [chars]: [hex]: [dec]
Explanation Errors (most likely lack of memory) prevent checkpointing from creating an index structure associated with an indexed table. This condition does not affect the functionality at all, only the performance will suffer.
Recommended Action The checkpointing software will periodically try again to set up the index structure. So, in general no action is required.
Error Message%HA-CHKPT_TDM-7-OBJ_COUNT table object count not correct: [hex]: [dec] (!= [dec])
Explanation A table's object count is not what it's supposed to be. This is an internal accounting error and does not cause any problems inside checkpointing, but it may cause applications which depend on this accounting info to mis-behave.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-OBJ_LEN Bad object length: [chars] tblname: [hex]: object size: [dec] record length: [dec]
Explanation An object save or get operation is being done with the wrong length buffer. This points to a logical bug in the client application.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-REG_MISMATCH table attributes changed upon re-register:
Explanation An application is trying to register for its table. A table with the same exists, but other attributes have changed, so the table is not allowed to be used.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-TRANSLATION_FATAL Fatal translation error: [hex]
Explanation An error occurred during data translation. The process will restart without checkpointed data.
Recommended Action No action is required.
DCL_LIB Messages
Error Message%HA-DCL_LIB-2-NULL_PTR [chars]@[dec]: Null Data Pointer Encountered Handle = [hex] Counter = [hex]
Explanation An expected data pointer was not found.
Recommended Action Collect system log information. No action is required.
Error Message%HA-DCL_LIB-4-CERR_REGISTER Registration of error strings failed with error [hex]
Explanation Error string registration failed.
Recommended Action No action is required.
Error Message%HA-DCL_LIB-4-NONFATAL_INTERNAL [chars]@[dec]: A Non-Fatal Internal Error was encountered.
Explanation A Non-Fatal condition was encountered. This is not necessarily an error, but information gathered here may help with debugging other problems elsewhere in the system.
Recommended Action Collect system log information. No action is required.
Error Message%HA-DCL_LIB-4-UNEXPECTED [chars]@[dec]: An Unexpected condition was encountered - [chars]
Explanation An unexpected condition was encountered. This is not necessarily an error, but information gathered here may help with debugging other problems elsewhere in the system.
Recommended Action Collect system log information. No action is required.
HA_FM Messages
Error Message%HA-HA_FM-4-FMSD_POLICY_APPLY Could not apply policy '[chars]': [chars]
Explanation A policy could not be applied and was un-registered. This message signaled an unsuccessful apply of the policy.
Recommended Action Remove the configuration for the policy (and commit), and then attempt to configure the registration of the same policy.
Error Message%HA-HA_FM-4-FMSD_POLICY_CONFIG_INCONSISTENT Policy '[chars]': [chars]
Explanation Some policy configuration is potentially inconsistent, and the user should follow the guidelines in the message to amend this.
Recommended Action Examine the guidelines in the message, and the fault manager configuration, to determine the potential problem. Note that this is just a warning message, not an error message, as the configuration is legal - it may be the case that the user has intentionally set this configuration.
Error Message%HA-HA_FM-4-FMSD_POLICY_UNREGREG_ERR Could not replace policy '[chars]': [chars]
Explanation A registered policy changed by the last installation update was detected. Since the update used the 'start' option, the old policy was automatically replaced by the new policy. This message signaled an unsuccessful replacement of the policy.
Recommended Action Remove the configuration for the previous policy (and commit), and then attempt to configure the registration of the new policy. The error message returned at commit time should indicate the problem with the new policy.
Error Message%HA-HA_FM-6-FMFD_WD_CPU_NOTIF CPU consumption is [chars] at [unsigned int] percent
Explanation The CPU state has changed and the new state is announced.
Recommended Action No action is required.
Error Message%HA-HA_FM-6-FMFD_WD_CPU_NOTIF_ALARM CPU consumption is [chars] at [unsigned int] percent
Explanation The CPU state has changed to or from CRITICAL state, and the new state is announced.
Recommended Action No action is required.
Error Message%HA-HA_FM-6-FMS_POLICY_EXEC Policy execution has been [chars]
Explanation The Fault Manager policy excution state has been changed to the state named in the message.
Recommended Action No action is required.
Error Message%HA-HA_FM-6-FMS_POLICY_TIMEOUT Policy '[chars]' has hit its maximum execution time of [dec].[dec] seconds, and so has been halted
Explanation The policy has exceeded its maximum execution time, and so has been halted part way through execution. If this policy is expected to take a long time to run, it may need to have 'maxrun_sec' added to the policy registration line (or its value increased if it is already specified).
Recommended Action No action is required.
Error Message%HA-HA_FM-6-FMS_RELOAD_SYSTEM Policy has requested a system reload; reloading in 5 seconds
Explanation A Fault Manager policy requested that the system be reloaded.
Recommended Action No action is required.
Error Message%HA-HA_FM-6-FMS_SYSLOG_SCAN_SIGNUP Failed to load Syslog FD DLL [chars]: [chars]. Syslog registration in Fault Manager policies will not be able to function.
Explanation The syslog_scan_signup function reported an error trying to load the specifed Syslog Fault Detector DLL library. It will not be possible for Fault Manager to be alerted of new syslog messages, and hence any scripts registered for syslog messages will not be triggered as expected.
Recommended Action Restart the syslogd process and the fm_server process. If the message still appears then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-6-FMSD_POLICY_CHANGED Registered policy '[chars]' changed by the last installation update
Explanation A registered policy was changed by the last installation update. If the update used the 'start' option, the old policy was automatically unregistered and the new policy registered. Otherwise, the old policy would remain registered and functional until the user unregisters it manually.
Recommended Action No action is required.
Error Message%HA-HA_FM-6-FMSD_POLICY_DELETED Registered policy '[chars]' deleted by the last installation update
Explanation A registered policy was deleted by the last installation update. If the update used the 'start' option, the policy was automatically unregistered. Otherwise, the policy would remain registered and functional until the user unregisters it manually.
Recommended Action No action is required.
Error Message%HA-HA_FM-6-FMSD_POLICY_REG_SUCC Policy '[chars]' registered successfully, by user [chars], with persist time [dec] and type [dec]
Explanation A new policy has been registered with Fault Manager. This message signaled a successful registration.
Recommended Action No action is required.
Error Message%HA-HA_FM-6-FMSD_POLICY_UNREG_SUCC Policy '[chars]' unregistered successfully
Explanation A registered policy changed or deleted by the last installation update was detected. Since the update used the 'start' option, the old policy was automatically unregistered. This message signaled a successful unregistration.
Recommended Action No action is required.
Error Message%HA-HA_FM-6-FMSD_POLICY_UNREGREG_SUCC Policy '[chars]' replaced successfully
Explanation A registered policy changed by the last installation update was detected. Since the update used the 'start' option, the old policy was automatically replaced by the new policy. This message signaled a successful replacement of the policy.
Recommended Action No action is required.
Error Message%HA-HA_FM-7-DEBUG_INIT_EVENT Debug initialization for the fm/[chars] event failed: [chars]
Explanation An error was returned when the Fault Manager called the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-DEBUG_REGISTER Debug registration for Fault Manager failed: [chars]
Explanation An error was returned when the Fault Manager called the debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMC_APPL_CBH_PULSE Unable to locate application publish callback entry for pulse code [dec]
Explanation The application publish callback handler was unable to validate the pulse code received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMC_APPL_CBH_SEND Unable to report that application publishing has been successfully carried out: [chars]
Explanation The application publish callback handler was unable to send a report to the Fault Manager Server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMC_CB_EVM_CREATE Unable to create the messaging infrastructure for this process: [chars]
Explanation An error was reported trying to create the messaging infrastructure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMC_CB_INIT_FMC Failed to initialize the Fault Manager context control block: [chars]
Explanation An error was reported trying to initialize the internal context control block.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMC_CB_MC_ATTACH Failed to attach to a messaging channel: [chars]
Explanation An error was reported trying to attach to a messaging channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMC_CBS_THREAD_CREATE Unable to create a posix thread: [chars]
Explanation Unable to create a posix thread to carry out Fault Manager handling.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMC_CERR_REG Unable to register error code descriptions: [chars]
Explanation The Fault Manager errors could not be registered, and so the error codes will not be decoded in messages to the user.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMC_REG_CBH_PULSE Unable to locate reg callback entry for pulse code [dec]
Explanation The registration callback handler was unable to validate the pulse code received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMC_REG_CBH_SEND Unable to report that callback handling has been successfully carried out: [chars]
Explanation The registration callback handler was unable to send a report to the Fault Manager Server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_CHKPT_INIT [chars]
Explanation Internal error. The fault detector has failed to initialize with the checkpointing server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_CHKPT_TBL_INIT [chars]
Explanation Internal error. The fault detector has failed to initialize a table with the checkpointing server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_CHKPT_TBL_ITERATE [chars]
Explanation Internal error. The fault detector has failed to iterate the checkpointing table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_DE_FETCH [chars]
Explanation Internal error. The fault detector has failed to fetch a data element from the statistics data engine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_DE_INIT [chars]
Explanation Internal error. The fault detector has failed to initialize the statistics data engine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_EA_ATTACH Could not register for asynchronous message events: [chars]
Explanation The fault detector has failed to attach an event handler for asynchronous messages.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_EI_EVENT Could not initialize event structure: [chars]
Explanation The fault detector has failed to initialize the sigevent structure to be used by the Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_EM_ATTACH Could not register for sychronous message events: [chars]
Explanation The fault detector has failed to attach an event handler for synchronous messages.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_EVM_CREATE Could not create event manager: [chars]
Explanation The fault detector has failed to create an Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_EVM_EVENT_BLOCK An error occurred while waiting for an event: [chars]
Explanation The event infrastructure will ignore this error and continue to wait for the next event. If this error is seen repeatedly, the process may not be able to function and will need to be restarted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_HIST_QERR Could not obtain a free history list entry
Explanation Internal error. The fault detector has failed to get a free history list entry.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_INV_COMPARE_OP Invalid comparison operator: [dec]
Explanation Internal error. The value comparison operator is invalid or not supported.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_INV_STATS_TYPE Invalid statistics value type: [dec]
Explanation Internal error. The statistics data type is invalid or not supported.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_INV_TM Invalid timer: type=[dec], timer=[pointer]
Explanation Internal error. The timer value is invalid or not as expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_INV_TM_TYPE Invalid timer type: [dec]
Explanation Internal error. The timer type is invalid or not supported.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_LOCAL_NODEID Could not get local nodeid: [chars]
Explanation Could not get local node identifier.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_MEM_ALLOC Not enough memory ([dec] bytes)
Explanation Allocating memory failed due to a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%HA-HA_FM-7-FMFD_MET_ENQUEUE Could not enqueue metric data: [chars]
Explanation Internal error. The system manager fault detector has failed to add a metric data entry to the list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_MET_RBLD [chars]
Explanation Internal error. The fault detector has failed to rebuild the metric list from the checkpointed records.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_MISC_ERR [chars] ([chars])
Explanation An unexpected error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_MSGSEND_EVT [chars]
Explanation The fault detector has failed to send a pulse to the fault manager to notify of an event publish.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_MSGSEND_RETRY_ERR Maximum retry number exceeded
Explanation The fault detector has exceeded its maximum number of retries to send a pulse to the fault manager to notify of an event publish.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_OE_CREATE Could not create an occurrence entry
Explanation Internal error. The fault detector has failed to create an entry for the matched occurrence list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_OE_REMOVE Could not remove an occurrence entry
Explanation Internal error. The fault detector has failed to remove an entry from the matched occurrence list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_PLTF_NODENAME Could not get local node name
Explanation The fault detector has failed to get the local node name.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_PUB_ENQUEUE [chars]
Explanation Internal error. The fault detector has failed to add a publish data entry to the list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_PUB_RBLD [chars]
Explanation Internal error. The fault detector has failed to rebuild the publish list from the checkpointed records.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_RM_ATTACH Could not attach resource manager funtions to event manager: [chars]
Explanation The fault detector has failed to attach a Resource Manager to an Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_SM_PROC_EXIT [chars]
Explanation The system manager failed to execute the default action of the terminated process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_STATS_VAL_GET_ERR [chars]
Explanation Internal error. The fault detector has failed retrieving a valid statistics value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_SYSDB_BIND [chars]
Explanation Failed to bind to SysDB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_SYSDB_GET [chars]
Explanation Failed to retrieve an item from SysDB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_SYSDB_REG_NOTIFY [chars]
Explanation Failed to register for notification of a set of items in SysDB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_THREAD_CREATE Could not create a Posix thread
Explanation The pthread_create function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_TM_ADDL_CTX Could not set additional context pointer: [chars]
Explanation The fault detector has failed to set a managed timer's additional context pointer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_TM_CRTICK_INIT [chars]
Explanation Internal error. The initialization of the cron-tick function has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_TM_LEAF_NEW Could not create a leaf timer
Explanation The fault detector has failed to create a managed leaf timer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_TM_PARENT_NEW Could not create a managed parent timer: [chars]
Explanation The fault detector has failed to create a managed parent timer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMFD_TM_TREE_NEW Could not create a managed timer tree
Explanation The fault detector has failed to create a managed timer tree.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_CHKPT_INIT Could not register the application with the checkpointing server: [chars]
Explanation Failed to register an application with the checkpointing server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_CHKPT_NULL_PTR Got a null [chars] but non-null value was expected
Explanation Failed to do further processing because we got a null data when a non-null value was expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_CHKPT_TBL_ADD Could not save a record into a checkpointing table: [chars]
Explanation Failed to save a record into the given checkpointing table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_CHKPT_TBL_INIT Failed to initialize [chars]: [chars]
Explanation Could not initialize a table with the checkpointing server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_CHKPT_TBL_RECOVER Could not recover the checkpointed [chars]: [chars]
Explanation Failed to recover a checkpointed table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_CONN_EXIST The message connection we try to set up already exists
Explanation An internal error. We tried to set up a message connection but it already exists.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_EVM_ASYNC_ATTACH Could not attach handler for Event Manager asynchronous event: [chars]
Explanation An internal error was detected when attaching a handler for an Event Manager asynchronous event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_EVM_CREATE Could not create event manager: [chars]
Explanation An internal error was detected when creating Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_EVM_EVENT_BLOCK Failed to block waiting for Event Manager events: [chars]
Explanation An internal error was detected when block waiting for Event Manager events.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_EVM_FILE_ATTACH Could not register a notification handler for a file descriptor: [chars]
Explanation An internal error was detected when trying to register a notification handler for a file descriptor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_EVM_INIT_EVENT Could not initialize Event Manager event: [chars]
Explanation An internal error was detected when initializing an Event Manager event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_EVM_TM_ATTACH Could not set up a managed timer identifier: [chars]
Explanation An internal error was detected when trying to allocate a managed timer identifier and assign to it an event handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_EVM_TM_LEAF_NEW Could not create a managed timer tree leaf: [chars]
Explanation An internal error was detected when trying to create a managed timer tree leaf for the event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_FD_SIGEVENT Error occured when a fault detector processed the pulse from the metric director: [chars]
Explanation Internal error. Error occurred when a fault detector processed the pulse from the metric director.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_FILE_OPEN Failed to open file [chars] : [chars]
Explanation Failed to open the given file due to some internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_GET_CHID Could not get message channel ID: [chars]
Explanation An internal error was detected when getting ID for a message channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_GET_NODE_NAME Could not get node name of the local host: [chars]
Explanation An internal error was detected when trying to get the node name of the local host.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_GUARD_WORD_VER [chars] guard word corrupted; [pointer]
Explanation The guard word for the specified control block does not contain what is expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_LAST_PROC Invalid last process replied: node [hex], job id [dec]
Explanation Internal error. The information of last process the metric director replied to 'show fault manager metric process' command is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_LOCAL_NODEID Could not get local nodeid: [chars]
Explanation Could not get local node identifier.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_LONG_PATHNAME Too long path name
Explanation Internal error. A path name could not be formed because it exceeded the maximum length.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_LWM_ATTACH Could not attach a connection to a message channel: [chars]
Explanation An internal error was detected when attaching a connection to a message channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_LWM_CONNECT Could not connect to the message channel [chars]: [chars]
Explanation An internal error was detected when attaching a handler for an Event Manager asynchronous event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_LWM_SEND Could not send message: [chars]
Explanation An internal error was detected when sending a message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_LWM_SEND_ASYNC Could not send a pulse to a connection: [chars]
Explanation An internal error was detected when trying to send a pulse to a connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_MEM_ALLOC Not enough memory ([dec] bytes)
Explanation Allocating memory failed due to a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%HA-HA_FM-7-FMMD_METRIC_POLL Error occurred when polling a fault detector for metric data: [chars]
Explanation Internal error. Error occurred when the metric director tried to poll a fault detector for metric data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_METRICSVC_INIT Could not initialize metric RPC service: [chars]
Explanation An internal error was detected when initializing RPC service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_PROC_EVENT_TYPE Unknown process event type [dec]
Explanation An unknown Fault Manager process event type was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_QSM_REG_NOTIF Could not register for QSM notification: [chars]
Explanation An internal error was detected when registering for QSM notification.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_SVC_REG RPC service registration for Fault Manager Metric Director failed
Explanation Fault Manager Metric Director failed to register with the RPC facility.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_SVCEVM_CREATE Could not initialize RPC server for event manager: [chars]
Explanation Initializing RPC server stub for event manager failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_SYSCALL [chars] failed: [chars]
Explanation A system call failed with the indicated error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_UNEXP_MSG_TYPE Message type is [dec] instead of the expected [chars]
Explanation A received message was of an unexpected type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_UNEXP_PROC Process metric entry with node [hex] and job id [dec] not found
Explanation Internal error. The process metric entry with the given node name and job id cannot be found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMMD_UNEXP_PULSECODE Unexpected pulse code [dec]
Explanation A received pulse was of an unexpected code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_ASYNC_ATTACH Failed to attach to handle [chars]: [chars]
Explanation The event_async_attach function reported an error trying to attach to the specified handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_ASYNC_ATTACH_FD Failed to attach to handle Fault Detector [chars] pulse code: [chars]
Explanation The event_async_attach function reported an error trying to attach to handle the Fault Detector handler pulse code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_CALLBACK_MAX_ENTRIES Maximum number of callback publish entries exceeded for [chars]; some events have been discarded
Explanation An attempt to publish an event requiring a callback failed because there is no more room in the callback publish queue for the specified process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_CHKPT_INIT Could not register the application with the checkpointing server: [chars]
Explanation Failed to register an application with the checkpointing server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_CHKPT_NULL_PTR Got a null [chars] when non-null value was expected
Explanation Failed to do further processing because we got a null data when a non-null value was expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_CHKPT_TBL_ADD Could not add to the checkpointed [chars]: [chars]
Explanation Failed to add a record to the checkpointed table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_CHKPT_TBL_INIT Failed to initialize [chars]: [chars]
Explanation Could not initialize a table with the checkpointing server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_CHKPT_TBL_RECOVER Could not recover for the checkpointed [chars]: [chars]
Explanation Failed to recover a record from the checkpointed table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_CHKPT_TBL_REMOVE Could not remove from the checkpointed [chars]: [chars]
Explanation Failed to remove a record from a checkpointed table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_CHKPT_TBL_SAVE Could not save to the checkpointed [chars]: [chars]
Explanation Failed to save a record to a checkpointed table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_EVM_CREATE Failed to create an event manager: [chars]
Explanation An error was reported trying to create this process' messaging infrastructure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_EVM_EVENT_BLOCK An error occurred while waiting for an event: [chars]
Explanation The event infrastructure will ignore this error and continue to wait for the next event. If this error is seen repeatedly, the process may not be able to function and will need to be restarted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_EVM_FILE_ATTACH Unable to do an event_file_attach for [chars]: [chars]
Explanation The event_file_attach function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_EVM_INIT_EVENT event_init_event for Fault Detector [chars] failed: [chars]
Explanation The event_init_event function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_FDC_ALLOCATE Failed to allocate Fault Detector context control block: [chars]
Explanation The get_fd function reported an error trying to allocate a Fault Detector context control block.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_FDC_OPEN Failed to open Fault Detector context control block
Explanation The open_fd function reported an error trying to open a Fault Detector context control block.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_GET_CHAN_CHAN Failed to obtain a messaging channel ID: [chars]
Explanation An error was reported trying to obtain the channel ID.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_GET_NODE_NAME Failed to retrieve the name of the local node: [chars]
Explanation An error was reported trying to obtain the node name.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_GET_NODE_STATE Failed to get the current nodes state: [chars]
Explanation The call to get the nodes current state failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_GET_PRIO Failed to get process priority: [chars]
Explanation The getprio function reported an error trying to obtain the default process priority.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_GUARD_WORD_VER [chars] guard word corrupted; [pointer]
Explanation The guard word for the specified control block does not contain what is expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_INIT_EVENT_TIMER Failed to initialize a timer event: [chars]
Explanation An error was reported trying to initialize the timer notification event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_INV_ARG_STRING Invalid argument string: [chars]
Explanation An invalid argument string was passed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_INV_ENV_STRING Invalid environment string: [chars]
Explanation An invalid environment string was passed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_KILL Unable to kill process [chars]: [chars]
Explanation The kill function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_KILL_RUN Unable to kill run process [dec] for [chars]: [chars]
Explanation The kill function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_LWM_ATTACH Failed to attach to fm message channel: [chars]
Explanation The msg_chan_attach function reported an error trying to attach to the Fault Manager server channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_LWM_ATTACH_SYNC Failed to attach to handle synchronous messages: [chars]
Explanation The event_message_attach function reported an error trying to attach to handle synchronous messages.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_LWM_CONNECT Failed to connect to fm message channel [chars]: [chars]
Explanation The msg_chan_connect function reported an error trying to connect to the specified Fault Manager server channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_LWM_DISCONNECT Failed to disconnect from fm message channel [chars]: [chars]
Explanation The msg_chan_disconnect function reported an error trying to disconnect from the specified Fault Manager server channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_LWM_SEND Failed to send a message to [chars]: [chars]
Explanation The msg_send function reported an error trying to send a message to the specified process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_LWM_SEND_ASYNC Could not send a pulse to a connection: [chars]
Explanation An internal error was detected when trying to send a pulse to a connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_LWM_SEND_EVENT Failed to send an event to [chars]: [chars]
Explanation The msg_send_event function reported an error trying to send an asynchronous message to the specified process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_MEM_ALLOC Unable to allocate [dec] bytes
Explanation The malloc function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_MEM_REALLOC Unable to reallocate [dec] bytes
Explanation The realloc function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_MISC_ERR [chars] ([chars])
Explanation An unexpected error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_NULL_SCRIPT_NAME The script name is NULL
Explanation A null script name was invalidly passed as an argument.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_OPEN Unable to open [chars]: [chars]
Explanation The open function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_OVL_GET_MODULE_PATH ovl_get_module_path failed when attempting to get the full path for a program: [chars]
Explanation The ovl_get_module_path function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_OVL_NOTIFY_REG ovl_notification_register failed when registering to handle OVL notifications: [chars]
Explanation The ovl_register_notification function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_OVL_SETUP_ENV ovl_setup_env failed when updating the environment variables during an OVL notification: [chars]
Explanation The ovl_setup_env function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_POLICY_CHECKSUM Checksum error for policy [chars] - this policy will not be run
Explanation The checksum computed for the specified policy does not match the original checksum computed when the policy was registered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_POLICY_HASH The hash computation routine reported an error: [chars]
Explanation The fm_hash_md5_fd() function reported the specified error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_QSM_REGISTER Failed to register for QSM notifications for the fault detector [chars]: [chars]
Explanation The qsm_register_notification function reported an error trying to register for QSM notifications for the named fault detector.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_REG_NODE_STATE_CHANGE Failed to register for node state changes: [chars]
Explanation The call to register for node state changes failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_SCRIPT_MAX_ENTRIES Maximum number of script publish entries exceeded; some events have been discarded
Explanation An attempt to publish an event requiring a script failed because there is no more room in the script publish queue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_SIGNAL_ATTACH Failed to attach to handle SIGCHLD: [chars]
Explanation The event_signal_attach function reported an error trying to attach to handle the SIGCHLD signal.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_SIGQUEUE Failed to queue a signal for pid [hex], signal [dec]: [chars]
Explanation The sigqueue function reported an error trying to send a notification signal to the process specified by pid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_SPAWN Unable to spawn [chars]: [chars]
Explanation The spawn function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_SYSLOG_SCAN_RESIGN Failed to unload Syslog FD DLL [chars]: [chars]
Explanation The syslog_scan_resign function reported an error trying to unload the specified Syslog Fault Detector DLL library.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_TM_LEAF_NEW Unable to create timer leaf for [chars]: [chars]
Explanation The mgd_timer_leaf_new function reported an error attempting to create a timer leaf for the timer named in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_TM_PARENT_NEW Could not create a managed parent timer: [chars]
Explanation The mgd_timer_parent_new function reported an error attempting to create the timer named in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMS_TM_TREE_NEW Could not create a managed timer tree
Explanation The mgd_timer_tree_new function reported an error attempting to create the root timer tree.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_CHKPT_INIT Could not register the application with the checkpointing server: [chars]
Explanation Failed to register an application with the checkpointing server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_CHKPT_NULL_PTR Got a null [chars] but non-null value was expected
Explanation Failed to do further processing because we got a null data when a non-null value was expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_CHKPT_TBL_ADD Could not save a record into a checkpointing table: [chars]
Explanation Failed to save a record into the given checkpointing table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_CHKPT_TBL_INIT Failed to initialize [chars]: [chars]
Explanation Could not initialize a table with the checkpointing server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_CHKPT_TBL_RECOVER Could not recover the checkpointed [chars]: [chars]
Explanation Failed to recover a checkpointed table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_CHKPT_TBL_REMOVE Could not delete a record from a checkpointing table: [chars]
Explanation Failed to delete a record from the given checkpointing table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_CHKPT_TBL_RESET Could not reset a record in a checkpointing table: [chars]
Explanation Failed to reset a record in the given checkpointing table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_COUNTER_SET Failed to set a counter: [chars]
Explanation Failed to set a Fault Manager counter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_EVENT_CREATE Failed to create an event: [chars]
Explanation Failed to create a Fault Manager event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_EVENT_REG Failed to register an event: [chars]
Explanation Failed to register a Fault Manager event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_EVENT_TYPE Unknown event type [dec]
Explanation An unknown Fault Manager event type was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_EVM_CREATE Could not create event manager: [chars]
Explanation An internal error was detected when creating Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_EVM_EVENT_BLOCK Failed to block waiting for Event Manager events: [chars]
Explanation An internal error was detected when block waiting for Event Manager events.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_FILE_OPEN Failed to open file '[chars]': [chars]
Explanation Failed to open the given file due to some internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_FM_INIT Could not initialize Fault Manager service: [chars]
Explanation An internal error was detected when initializing Fault Manager service.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_GET_NODE_NAME Failed to get the local node name: [chars]
Explanation Failed to get the local node name.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_GET_PRIO Failed to get process priority: [chars]
Explanation Internal error. A call to get process scheduling priority failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_LAST_POLICY Invalid last policy name replied '[chars]'
Explanation Internal error. The last policy name the script director replied to 'show fm policy registered' command is an invalid policy name.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_MEM_ALLOC Not enough memory ([dec] bytes)
Explanation Allocating memory failed due to a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%HA-HA_FM-7-FMSD_OVL_NOTIF_REG Could not register for Version Manager notification: [chars]
Explanation An internal error was detected when registering for Version Manager notification.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_OVL_SETUP_ENV Could not update environment variables: [chars]
Explanation Updating environment variables of the process according to system variables stored in sysdb failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_POLICY_MISSING The policy execution copy '[chars]' was not present at unregistration.
Explanation The execution copy of the indication policy was not found at the time of unregistration. Most likely, the policy was removed manually, or the policy was not synced to the standby prior to failover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_POLICY_UNREG_ERR Could not unregister policy '[chars]': [chars]
Explanation A registered policy changed or deleted by the last installation update was detected. Since the update used the 'start' option, the old policy was automatically unregistered. This message signaled an unsuccessful unregistration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_REFRESHTIMER_INIT Failed to initialize a refresh timer ([chars]): [chars]
Explanation Failed to initialize a Fault Manager refresh timer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_RESYNC_FAIL Could not re-add file [chars] to syncfs list: [chars]
Explanation On process restart or failover the script file could not be added to the syncfs list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_SVC_REG RPC service registration for Fault Manager Script Director failed
Explanation Fault Manager Script Director failed to register with the RPC facility.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_SVCEVM_CREATE Could not initialize RPC server for event manager: [chars]
Explanation Initializing RPC server stub for event manager failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_SYNC_FAIL Could not add file [chars] to syncfs list: [chars]
Explanation Failed to add a file to be backed up on the redundant node.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_SYNCLIST_FAIL Failed to remove '[chars]' from the sync list: [chars].
Explanation An error was encountered while removing the indicated execution copy of a policy from the syncfs sync list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_SYSDB_VERIFY_REG Could not register for SysDB verification: [chars]
Explanation An internal error was detected when trying to register verify function and/or apply function for SysDB tuple operations upon the given item within the given namespace.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-7-FMSD_TIMER_ARM Failed to arm a timer: [chars]
Explanation Failed to arm a Fault Manager timer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
HA_WD_LIB Messages
Error Message%HA-HA_WD_LIB-3-DEBUG_REGISTER_FAIL Call to debug_register() failed with error [dec] ([chars])
Explanation An internal error was detected when registering with the debug library.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD_LIB-7-CLIENT_MONITOR Call to remonitor evm failed: [chars]
Explanation The wdsysmon server returned an error to a client in response to a request to remonitor an event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD_LIB-7-CLIENT_UNMONITOR Call to monitor evm failed: [chars]
Explanation The wdsysmon server returned an error to a client in response to a request to stop monitoring an event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD_LIB-7-INVALID_ARG [chars]: [chars]
Explanation A wdsysmon library was called with an invalid argument.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD_LIB-7-MISSING_CTX [chars]: [unsigned int]
Explanation During a re-registration, an internal context structure was not found. This is probably a coding error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD_LIB-7-NO_MEM [chars]: not enough memory: [chars]
Explanation Allocating memory failed due to a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%HA-HA_WD_LIB-7-SVR_MEMINFO [chars]: Server failed to return memory information: [chars]
Explanation An internal error was detected when trying to communicate with wdsysmon to retrieve a node's memory information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD_LIB-7-SVR_REG [chars]: failed to register with WDSysMon server: [chars]
Explanation An internal error was detected when trying to register with WDSysMon server with an initialization message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD_LIB-7-SVR_RSC_UNREG [chars]:[chars]: failed to unregister with wdsysmon resource notification server: [chars]
Explanation An internal error was detected when trying to unregister with wdSysmon server
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD_LIB-7-SVR_UNREG [chars]: failed to unregister with WDSysMon server: [chars]
Explanation An internal error was detected when trying to unregister with WDSysMon server with a close message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD_LIB-7-SYSCALL [chars]: [chars](): [chars]
Explanation A system call failed in the wdsysmon library.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD_LIB-7-THREAD_CTX_INIT [chars]:[chars]: failed to initialize WDSysMon resource notification thread context: [chars]
Explanation An internal error was detected when trying to initialize the WDSysMon resource notification thread context
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
HA_WD Messages
Error Message%HA-HA_WD-1-ABORTING [chars], Aborting.
Explanation The system is experiencing CPU Hog, If this condition persists for 30 seconds, the node will be reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-1-CPU_HOG_5 Process [chars] pid [dec] tid [dec] prio [dec] using [dec]% is hogging CPU and will be terminated
Explanation This message is displayed
Recommended Action The command 'show watchdog trace' will display additional information about the potential CPU hog. If the hog is persistant, contact technical support. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-1-CPU_HOG_ALERT Process [chars] pid [dec] tid [dec] prio [dec] using [dec]% is the top user of CPU.
Explanation This message is displayed after the CPU hog detector trips. It shows the percentage of CPU used by the busiest thread in the top consumer of CPU.
Recommended Action The command 'show watchdog trace' will display additional information about the potential CPU hog. If the hog is persistant, contact technical support. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-1-CURRENT_STATE Persistent Hog detected for more than [dec] seconds
Explanation The system is experiencing CPU Hog, If this condition persists for 30 seconds, the node will be reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-DEBUG_REGISTER_FAIL Call to debug_register() failed with error [dec] ([chars])
Explanation An internal error was detected when registering with the debug library.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-DEVCTL [chars]: line [dec]: devctl() on file [chars] failed with error [dec] ([chars])
Explanation Failed to open procfs file or directory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-EVM_ASYNC_ATTACH [chars]: could not attach handler for Event Manager asynchronous event: [chars]
Explanation An internal error was detected when attaching a handler for an Event Manager asynchronous event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-EVM_CREATE [chars]: could not create event manager: [chars]
Explanation An internal error was detected when creating Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-EVM_EVENT_BLOCK [chars]: failed to block waiting for Event Manager events: [chars]
Explanation An internal error was detected when block waiting for Event Manager events.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-EVM_INIT_EVENT [chars]: failed to initialize a sigevent structure: [chars]
Explanation An internal error was detected when trying to initialize a sigevent structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-EVM_MSG_ATTACH [chars]: could not attach handler for Event Manager synchronous message: [chars]
Explanation An internal error was detected when attaching a handler for an Event Manager synchronous message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-EVM_THREAD_INIT [chars]: unable to initialize event manager thread: [chars]
Explanation An error occured when attempting to initialize the event manager thread.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-EVM_TM_ATTACH [chars]: could not set up a managed timer identifier: [chars]
Explanation An internal error was detected when trying to allocate a managed timer identifier and assign to it an event handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-EVM_TM_DETACH [chars]: could not set up a managed timer identifier: [chars]
Explanation An internal error was detected when trying to remove a managed timer registration from an event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-EVM_TM_LEAF_NEW [chars]: could not create a managed timer tree leaf: [chars]
Explanation An internal error was detected when trying to create a managed timer tree leaf for the event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-FD_CRIT_LIM Process [chars], pid [dec] is using [dec] file descriptors out of a max of [dec]. Critical limit ([dec]%) crossed.
Explanation A process is potentially leaking FDs. Critical limit has been crossed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-FD_INIT [chars]: failed to initialize fault detector: [chars]
Explanation An internal error was detected when initializing the fault detector.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-MSG_GET_CHAN_CHAN [chars]: could not get channel id from the channel handler: [chars]
Explanation An internal error was detected when trying to get channel id from a channel handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-NOTIF_THREAD_INIT [chars]: unable to initialize process memory notification thread: [chars]
Explanation An error occured when attempting to initialize the event manager thread.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-OPEN_PROCFS [chars]: could not open procfs file or directory [chars]: [chars]
Explanation Failed to open procfs file or directory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-PLATFORM_NODENAME [chars]: could not get local node name: [chars]
Explanation An internal error was detected when trying to get local node name through platform library.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-PLATFORM_SLOT [chars]: could not get my slot number
Explanation An internal error was detected when trying to get the slot number of local node through platform library.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-POP [chars]: unmatched stack pop operation
Explanation An unmatched stack pop operation was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-PTHRD_CREATE [chars]: could not create a POSIX thread
Explanation An internal error was detected when trying to create a POSIX thread.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-SERVICE_CREATE Failed to create thread for service [dec], name [chars]: [chars]
Explanation The system failed to create the thread that provides the indicated service. This is a fatal error for wdsysmon.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-3-WATCHER_THREAD_INIT [chars]: unable to initialize process cpu watcher thread: [chars]
Explanation An error occured when attempting to initialize the cpu watcher thread.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-4-CFG_FAILED [chars]: wd_config_init failed, error: [chars]
Explanation wd_config_init failed due to sysdb intialization problem.
Recommended Action Collect all logs, especially those from wdsysmon. Also collect output from 'show watchdog trace'. Forward the messages to technical support.
Error Message%HA-HA_WD-4-DISK_ALARM [chars]
Explanation Set: When some monitored disk's usage is above 80%. Cleared: When all monitored disks' usage are below 80%.
Recommended Action The indicated disk device may be running out of space. Determine if there are unneeded files on the disk.
Error Message%HA-HA_WD-4-FD_MAJ_LIM Process [chars], pid [dec] is using [dec] file descriptors out of a max of [dec]. Major limit ([dec]%) crossed.
Explanation A process is potentially leaking FDs. Major limit has been crossed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-4-FD_MIN_LIM Process [chars], pid [dec] is using [dec] file descriptors out of a max of [dec]. Minor Limit ([dec]%) crossed.
Explanation A process is potentially leaking FDs. Minor limit has been crossed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-4-FD_NORMAL_LIM Process [chars], pid [dec], is now using [dec] file descriptors. Status is Normal
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-4-MEM_POLL [chars]: Failed to poll for memory usage: [chars]
Explanation An error was encountered during wdsysmon's poll for system memory usage.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-4-MEMORY_ALARM Memory threshold crossed: [chars] with [unsigned int].[unsigned int]MB free
Explanation Set: Free memory on this node is below the reported threshold. Clear: Free memory is above the MINOR theshold. In both cases, the amount of free memory in megabytes is reported.
Recommended Action Investigate memory usage on this node. It may be necessary to unconfigure some applications or move them to a different node. In the case of memory leaks, technical support may need to be contacted.
Error Message%HA-HA_WD-4-MEMORY_LIMIT_EXCEEDED Process [chars][[dec]] (pid [dec]) has exceeded its memory limit: [dec] kbytes allowed, [dec] kbytes of heap and [dec] kbytes of shared memory used.
Explanation The process with the indicated name and pid has allocated more memory than its memory limit allows. The process will be restarted.
Recommended Action The system will collect data about the process before it is killed. Collect this data and forward it to technical support. Most likely, there is a memory leak in the process.
Error Message%HA-HA_WD-4-MEMORY_STATE_CHANGE New memory state: [chars]
Explanation The free memory state of this node has changed to the indicated state.
Recommended Action If the free memory state is Severe or Critical, investigate memory usage on this node. It may be necessary to unconfigure some applications or move them to a different node. In the case of memory leaks, technical support may need to be contacted.
Error Message%HA-HA_WD-4-TOP_MEMORY_USER_WARNING [dec]: Process Name: [chars][[dec]], pid: [dec][chars], Heap usage [dec] Kbytes, Shared memory usage [dec] Kbytes.
Explanation This process is one of the top memory users in the system. If the system reaches critical memory exhaustion, this process is subject to restart or termination. If the process is listed as 'Killed', then the system is in the process of recovering the resources used by the process.
Recommended Action Collect system log information. Contact technical support if the problem is not a misconfiguration.
Error Message%HA-HA_WD-4-TOP_MEMORY_USERS_WARNING Top [dec] consumers of system memory ([dec] Kbytes free):
Explanation This message is emitted when system memory usage crosses a threshold in the direction of increasing memory exhaustion. The top memory users will follow in the next messages. There may be a memory leak or misconfiguration.
Recommended Action Collect the data from the following messages and attempt to determine what is driving memory usage. Forward the messages to technical support.
Error Message%HA-HA_WD-4-TOP_SHMEM_USER_WARNING [dec]: File/Directory Name: [chars], Kbytes used: [dec].
Explanation This process is one of the top sharedmemory users in the system. If the system reaches critical memory exhaustion, this process is subject to restart or termination. If the process is listed as 'Killed', then the system is in the process of recovering the resources used by the process.
Recommended Action Collect system log information. Contact technical support if the problem is not a misconfiguration.
Error Message%HA-HA_WD-4-TOP_SHMEM_USERS_WARNING Top [dec] consumers of shared memory ([dec] Kbytes free):
Explanation This message is emitted when system memory usage crosses a threshold in the direction of increasing memory exhaustion. The top shared memory users will follow in the next messages. There may be a memory leak or misconfiguration.
Recommended Action Collect the data from the following messages and attempt to determine what is driving memory usage. Forward the messages to technical support.
Error Message%HA-HA_WD-5-NO_TIMEOUT All registered event managers on this node are sending heartbeats.
Explanation All event managers are now sending keep alive messages as expected.
Recommended Action The debugging information collected when an event manager stopped sending heartbeats should be examined and provided to technical support for analysis.
Error Message%HA-HA_WD-5-TIMEOUT Event manager from process [chars][[dec]] created by thread [dec] at [chars] is not sending heartbeats.
Explanation A timeout occurred waiting to hear from an event manager. This could happen as a result of a process being deadlocked on another event.
Recommended Action Wdsysmon has detected that an event manager is no longer sending keepalive heartbeats. The message provides information about where the event manager was created. A debug script will run and collect information about the process and the state of the router. The output will be in a directory [/disk1:|/disk0:|/bootflash:|/tmp]/wdsysmon_debug/debug.*
Error Message%HA-HA_WD-5-TIMEOUT_CANCELLED Event manager from process [chars][[dec]] created by thread [dec] at [chars] is not sending heartbeats.
Explanation An event manager has resumed sending heartbeats. This happens when a condition that caused the hang is cleared.
Recommended Action The debugging information collected when the event manager stopped sending heartbeats should be examined and provided to technical support for analysis.
Error Message%HA-HA_WD-5-TIMEOUT_EXIT Process [chars] with event manager not sending heartbeats has exited.
Explanation A process with an event manager that was not sending heartbeats has exited.
Recommended Action The debugging information collected when the event manager stopped sending heartbeats should be examined and provided to technical support for analysis.
Error Message%HA-HA_WD-6-CPU_HOG_1 CPU hog: cpu [dec]'s sched count is [dec].
Explanation Wdsysmon has detected a cpu starvation situation - potentially a high priority process spinning in a tight loop. The sched count is the number of times the wdsysmon ticker thread has been scheduled since the last time the wdsysmon watcher thread ran.
Recommended Action Check the system status, including the saved log for evidence of a high priority cpu hog.
Error Message%HA-HA_WD-6-CPU_HOG_2 CPU hog: cpu [dec]'s ticker last ran [dec].[dec] seconds ago.
Explanation Wdsysmon has detected a cpu starvation situation - potentially a high priority process spinning in a tight loop.
Recommended Action Check the system status, including the saved log for evidence of a high priority cpu hog.
Error Message%HA-HA_WD-6-CPU_HOG_3 Rolling average of scheduling times: [dec].[dec].
Explanation Wdsysmon has detected a cpu starvation situation - potentially a high priority process spinning in a tight loop. A high value for the rolling average indicates that a periodic process is not being scheduled.
Recommended Action Check the system status, including the saved log for evidence of a high priority cpu hog.
Error Message%HA-HA_WD-6-CPU_HOG_4 Process [chars] pid [dec] tid [dec] prio [dec] using [dec]% is the top user of CPU.
Explanation This message is displayed after the CPU hog detector trips. It shows the percentage of CPU used by the busiest thread in the top consumer of CPU.
Recommended Action The command 'show watchdog trace' will display additional information about the potential CPU hog. If the hog is persistant, contact technical support. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-6-DISK_UNMONITOR Alarmed disk [chars] is no longer monitored
Explanation Wdsysmon has been told to stop monitoring the indicated device, even though the disk is above 90% utilization.
Recommended Action If the disk is used for critical tasks, monitor the disk usage and take corrective action.
Error Message%HA-HA_WD-6-DISK_USAGE [chars] usage [dec]%
Explanation This message is emitted when disk usage for the indicated device crosses the 80%, 95% and 99% thresholds in either direction.
Recommended Action The indicated disk device is running out of space. Investigate disk usage.
Error Message%HA-HA_WD-6-GI_FILES_CREATED New dump files created in [chars]
Explanation Information captured by various modules and stored in bootflash during a previous reset has been moved to hard disk.
Recommended Action Examine the dump information for possible root-cause for a previous reset. Use the wd_test utility.
Error Message%HA-HA_WD-6-IN_DEP_LIST Process [chars] pid [dec] is present in Dependency List and will not be killed.
Explanation This message is emitted if the misbehaving process is one that wdsysmon depends on. It will not be terminated.
Recommended Action The command 'show watchdog trace' will display additional information about the process. Forward this information to technical support.
Error Message%HA-HA_WD-6-KNOWN_HOG Top CPU user process [chars] pid [dec] is a known hog.
Explanation This message is emitted if the top CPU user is known to use substantial CPU under some circumstances.
Recommended Action The command 'show watchdog trace' will display additional information about the potential CPU hog. If the hog is persistant, contact technical support. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-6-MEMORY_RECOVERY_DISABLED Node physical memory less than 256MB
Explanation This node is not configured with sufficient memory to enable memory recovery support.
Recommended Action Re-configure this node with more physical memory
Error Message%HA-HA_WD-6-MEMORY_RECOVERY_KILL_NON_SYSMGR Process [chars] (pid [dec]) not managed by sysmgr using [dec] kbytes of heap memory and [dec] kbytes of shared memory will be killed and not restarted.
Explanation The process with the indicated name and pid has been killed in an attempt to recover system memory. Since this process is not managed by sysmgr, it may not be restarted. The process can be manually restarted if desired, but may continue to consume large amounts of memory.
Recommended Action The system is critically short of memory. Automatic recovery will attempt to stabilize the system, but there is either a memory leak or a misconfiguration. Both require operator intervention.
Error Message%HA-HA_WD-6-MEMORY_RECOVERY_KILL_SYSMGR Process [chars][[dec]] (pid [dec]) (managed by sysmgr) using [dec] kbytes of heap memory and [dec] kbytes of shared memory will be killed and not restarted.
Explanation The sysmgr process with the indicated name and pid has been killed in an attempt to recover system memory. The process can be manually restarted if desired, but may continue to consume large amounts of memory.
Recommended Action The system is critically short of memory. Automatic recovery will attempt to stabilize the system, but there is either a memory leak or a misconfiguration. Both require operator intervention.
Error Message%HA-HA_WD-6-MEMORY_RECOVERY_RESTART Process [chars][[dec]] (pid [dec]) using [dec] kbytes of heap memory and [dec] kbytes of shared memory will be restarted.
Explanation The sysmgr process with the indicated name and pid has been restarted in an attempt to recover system memory.
Recommended Action The system is critically short of memory. Automatic recovery will attempt to stabilize the system, but there is either a memory leak or a misconfiguration. Both require operator intervention.
Error Message%HA-HA_WD-6-PROC_KILL_DISABLED [chars]: Process-terminate disabled. Pid [dec] will not be terminated
Explanation wdsysmon process-termination is disabled. A process which meets the kill criteria (either because it's in deadlock, or it's a memory or CPU hog - indicated by the first parameter [%d]) will not be terminated.
Recommended Action Collect all logs, especially those from wdsysmon. Also collect output from 'show watchdog trace'. Forward the messages to technical support.
Error Message%HA-HA_WD-6-TOP_MEMORY_USER_INFO [dec]: Process Name: [chars][[dec]], pid: [dec][chars], Heap usage: [dec] kbytes, Shared memory usage [dec] kbytes.
Explanation This process is one of the top memory users in the system. If the system reaches critical memory exhaustion, this process is subject to restart or termination. If the process is listed as 'Killed', then the system is in the process of recovering the resources used by the process.
Recommended Action Collect system log information. Contact technical support if the problem is not a misconfiguration.
Error Message%HA-HA_WD-6-TOP_MEMORY_USERS_INFO Top [dec] consumers of system memory ([dec] Kbytes free):
Explanation This message is emitted when system memory usage crosses a threshold in the direction of increasing memory exhaustion. The top memory users will follow in the next messages. There may be a memory leak or misconfiguration.
Recommended Action Collect the data from the following messages and attempt to determine what is driving memory usage. Forward the messages to technical support.
Error Message%HA-HA_WD-6-TOP_SHMEM_USER_INFO [dec]: File/Directory Name: [chars], Kbytes used: [dec].
Explanation This process is one of the top sharedmemory users in the system. If the system reaches critical memory exhaustion, this process is subject to restart or termination. If the process is listed as 'Killed', then the system is in the process of recovering the resources used by the process.
Recommended Action Collect system log information. Contact technical support if the problem is not a misconfiguration.
Error Message%HA-HA_WD-6-TOP_SHMEM_USERS_INFO Top [dec] consumers of shared memory ([dec] Kbytes free):
Explanation This message is emitted when system memory usage crosses a threshold in the direction of increasing memory exhaustion. The top shared memory users will follow in the next messages. There may be a memory leak or misconfiguration.
Recommended Action Collect the data from the following messages and attempt to determine what is driving memory usage. Forward the messages to technical support.
Error Message%HA-HA_WD-7-CLINFO_GET_DATUM [chars]: could not get an application datum associated with the channel: [chars]
Explanation An internal error was detected when trying to retrieve an application datum associated with the given channel handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-CLINFO_M_PID [chars]: could not get process id from message information: [chars]
Explanation An internal error was detected when trying to get process id from the information of a message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-CLINFO_SAVE_DATUM [chars]: could not save an application datum associated with the channel: [chars]
Explanation An internal error was detected when trying to save an application datum associated with the given channel handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-CLINFO_UNHOLD [chars]: could not decrement the hold count of the client info data: [chars]
Explanation An internal error was detected when trying to decrement the hold count of the client info data of a synchronous message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-CONTEXT_CREATE [chars]: Failed to create notification context: [chars]
Explanation During registration for memory notification, an internal error prevented the creation of an internal context structure. The calling function and detected error are displayed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-GET_EVM_CTX_BY_TIMER [chars]: could not find the event manager context by timeout timer [pointer]
Explanation An internal error was detected when trying to find the event manager context by the given timeout timer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-MSG_CHAN_CONNECT [chars]: could not connect to the message channel [chars]: [chars]
Explanation An internal error was detected when attaching a handler for an Event Manager asynchronous event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-MSG_CHAN_DISCONN [chars]: could not disconnect a message channel: [chars]
Explanation An internal error was detected when trying to disconnect a message channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-MSG_SEND [chars]: could not send the message: [chars]
Explanation An internal error was detected when trying to send a message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-MSG_SEND_EVENT [chars]: could not send the sigevent: [chars]
Explanation An internal error was detected when trying to send a sigevent to the client that last sent a message on the connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-MSG_TYPE [chars]: unknown message type [dec]
Explanation A message with an unknown type was received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-NO_MEM [chars]: not enough memory: [chars]
Explanation Allocating memory failed due to a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%HA-HA_WD-7-SCHED_GET_PRIORITY_MAX [chars]: The sched_get_priority_max() function returned an error; [chars]
Explanation The sched_get_priority_max() function returned an error which is indicated in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-SCHED_SETSCHEDULER [chars]: The sched_setscheduler() function returned an error; [chars]
Explanation The sched_setscheduler() function returned an error which is indicated in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-SYSCALL [chars]: [chars](): [chars]
Explanation A system call failed. The calling function, the failed call, and error are displayed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_WD-7-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error.
Recommended Action Collect system log information. No action is required.
HM Messages
Error Message%HA-HM-3-FPING_ERROR [chars]
Explanation HA Health Monitor Fabric ping failed
Recommended Action Shelf Manager should receive a critical alarm from HA Health Monitor for this error. The node should be reset by Shelf Manager. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HM-3-FPING_MISMATCH [chars]
Explanation HA Health Monitor Fabric ping failed. When a received ping response does not match the transmitted ping, this indicates some kind of cell corruption or cell loss in the fabric or edges of the fabric.
Recommended Action If problem persist, it indicates the bad hw in the system. Please contact TAC for fault isolation. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HM-4-ERROR_INIT [chars], reason: [chars]
Explanation HA Health Monitor failed to initialize due to internal software errors
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process hm location ' to verify that the process is up and running. If it is still non-operational, try doing 'process restart hm location ' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HM-4-FPING_INCOMPLETE HM fabric ping only completed [unsigned int] of [unsigned int] pings (ret = [hex])
Explanation HA Health Monitor Fabric ping test sequence failed to complete. If there were any errors before it got disrupted, then these are reported separately. The test will be restarted again at next HM fping interval. If there are no other errors reported, this warning is rarely a cause for concern, unless it very frequently causes only a partial set of HM fabric pings to be completed.
Recommended Action No action is required because HA Health Monitor will retry Fabric ping again
Error Message%HA-HM-4-FPING_RETRY_ERROR Fabric ping test failed for attempt: [dec], Node will be reset after [dec] retries
Explanation HA Health Monitor Fabric ping failed but will retry again
Recommended Action No action is required because HA Health Monitor will retry Fabric ping again
LRD_inv Messages
Error Message%HA-LRD_inv-3-BAG_REGISTRATION Unable to register LRd's bag structures. '[chars]'
Explanation LRd was unable to register bag structures.
Recommended Action Contact support.
Error Message%HA-LRD_inv-3-MEM_ALLOC_FAIL Failed to allocated [dec] bytes of memory: [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Contact TAC.
Error Message%HA-LRD_inv-3-MSG_CERR_REGISTER_DLL Could not register dll with error services: [chars]
Explanation The call register the dll using cerr_register_dll failed.
Recommended Action Contact TAC.
Error Message%HA-LRD_inv-3-MSG_INVENTORY_FWD Error forwarding inventory: '[chars]'
Explanation LRd was unable to read or write information needed to forward inventory in Admin space to the LR Plane.
Recommended Action Contact support.
Error Message%HA-LRD_inv-3-REDUNDANCY_STATE Unrecognized redundancy state [dec]
Explanation LRd doesn't recognize redundancy state.
Recommended Action Contact TAC.
Error Message%HA-LRD_inv-3-SYSDB_ITEM_ERROR sysdb_item_[chars]([chars]) returned '[chars]'
Explanation SysDB returned an error to LRd.
Recommended Action Contact support.
Error Message%HA-LRD_inv-4-CANT_FIND_DSC LR Daemon library could not find the dSC.
Explanation LRdlib could not find the designated Shelf Controller.
Recommended Action Collect system log information. No action is required.
Error Message%HA-LRD_inv-4-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere!
Recommended Action Collect system log information. No action is required.
Error Message%HA-LRD_inv-6-RESET_CARD_FOR_PAIRING LRd has reset the DRP '[dec]' to accomodate new pairing configuration.
Explanation The DRP pairing configuration was changed. The card entering or leaving the pair needs to be reset in order to accomodate the new configuration.
Recommended Action None.
Error Message%HA-LRD_inv-6-RESET_CARD_LR_CHANGE LRd has reset the card in slot '[dec]' because it was assigned to a new LR.
Explanation The DRP pairing configuration was changed. The card entering or leaving the pair needs to be reset in order to accomodate the new configuration.
Recommended Action None.
LRD Messages
Error Message%HA-LRD-2-EVENTATTACHFAIL event attach failure.
Explanation The LR Daemon encountered an error when registering for synchronous or asynchronous events.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%HA-LRD-2-SYSMGR_GET_NODE_STATE sysmgr get node state failure: [chars].
Explanation sysmgr_get_node_state failed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%HA-LRD-2-SYSMGR_REGISTER node role change registration with sysmgr failed: [chars].
Explanation sysmgr_register_node_state_change_evm failed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%HA-LRD-3-BAG_REGISTRATION Unable to register LRd's bag structures. '[chars]'
Explanation LRd was unable to register bag structures.
Recommended Action Contact support.
Error Message%HA-LRD-3-MEM_ALLOC_FAIL Failed to allocated [dec] bytes of memory: [chars]
Explanation The requested operation could not be accomplished because of a low memory.
Recommended Action Contact TAC.
Error Message%HA-LRD-3-MSG_CERR_REGISTER_DLL Could not register dll with error services: [chars]
Explanation The call register the dll using cerr_register_dll failed.
Recommended Action Contact support.
Error Message%HA-LRD-3-MSG_INVENTORY_FWD Error forwarding inventory: '[chars]'
Explanation LRd was unable to read or write information needed to forward inventory in Admin space to the LR Plane.
Recommended Action Contact support.
Error Message%HA-LRD-3-REDUNDANCY_STATE Unrecognized redundancy state [dec]
Explanation LRd doesn't recognize redundancy state.
Recommended Action Contact support.
Error Message%HA-LRD-3-SYSDB_ITEM_ERROR sysdb_item_[chars]([chars]) returned '[chars]'
Explanation SysDB returned an error to LRd.
Recommended Action Contact support.
Error Message%HA-LRD-4-CANT_FIND_DSC LR Daemon library could not find the dSC.
Explanation LRdlib could not find the dSC.
Recommended Action Collect system log information. No action is required.
Error Message%HA-LRD-4-HEADLESS_SDR_STATE Headless SDR condition detected, reloading local node.
Explanation Headless SDR condition was detected. The local card is being reset. This is not necessarily an error condition!
Recommended Action Make sure the dSDRSC is up.
Error Message%HA-LRD-4-SDR_PLANE_READY_TIMEOUT Signalling SDR Plane Ready for SDR [chars] ([dec]) (mgmt nodes [dec] of [dec] are NOT READY yet) -[chars]
Explanation SDR Plane ready is being signalled due to SDR plane ready timeout.
Recommended Action Contact TAC.
Error Message%HA-LRD-4-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere!
Recommended Action Collect system log information. No action is required.
Error Message%HA-LRD-4-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere!
Recommended Action Collect system log information. No action is required.
Error Message%HA-LRD-6-LATE_MGMT_NODE Management node [hex] in SDR [chars] ([dec]) is READY after SDR Plane Ready is signalled
Explanation A management node in the specified SDR came up after SDR Plane ready for that SDR was signalled.
Recommended Action Contact TAC.
PSARB Messages
Error Message%HA-PSARB-1-WRONG_SLOT Rebooting RP in slot [dec] because it conflicts with an already operational RP in slot [dec].
Explanation Card pairing requires primary/standby cards in specific slots and active RP's need to be in seperate LR's. Adjacency is defined by RP pairing rules (e.g. 0-1, 2-3, 4-5, 6-7). If it's intended to use the conflicting RP as a standby partner, please move the RP adjacent to the active. Or, if the RP is meant to be used in another logical router, please ensure it is assigned to the other LR. %d - indicates the wrong slot number the RP is inserted %d - indicates the slot number of the operational RP
Recommended Action Move standby RP card to correct slot in chassis, or assign to distinct LR.
Error Message%HA-PSARB-2-MSG_HEARTBEAT_LOST Slot [dec] heartbeat lost. Resetting card.
Explanation The active RP has lost the heartbeat of the indicated slot. This error happens after a certain number of messages are lost between the active and the indicated card. %d - indicates the slot number of the card experiencing the problem.
Recommended Action The system will automatically reset the card. If this error repeatedly occurs, try to shut down the card by configuring 'hw-module location slot shutdown' in admin mode. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-PSARB-3-INIT_ERR Process initialization failed: ([chars]%s)
Explanation The psarb process failed to initialize. This process is responsible for providing a high level of availability on the GSR router by having a pair of active and standby RPs in the system. When an active RP fails, another RP can take over the functionality of the failed RP. %s - indicates the reason for the failure. %s - the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-PSARB-3-TWO_PRIMARY_DETECTED Two primary RPs detected (message from slot [dec])
Explanation There appear to be two PRIMARY RP's in the system. This is due to messaging error when the other RP didn't receive the BID message. %d indicates the primary slot number displaying the message
Recommended Action The two primary RPs will be automatically reset.
Error Message%HA-PSARB-4-PARTNER_NOT_IN_LR This node's partner (slot [dec]) is in a different LR. The standby node will be reset.
Explanation Adjacent RPs must be in the same LR unless if they are both to be booted with an RP image. It is, however, permissable to boot a DRP in one of these slots. Adjacency is defined by RP pairing rules (e.g. 0-1, 2-3, 4-5, 6-7). %d - indicates the slot number of the partner RP
Recommended Action Do not boot RP images in adjacent slots when they are in different LRs. Adjacency is defined by RP pairing rules (e.g. 0-1, 2-3, 4-5, 6-7).
Error Message%HA-PSARB-5-IOS_RP_DETECTED Detected an RP in slot [dec] is running IOS. Configured it as IOS non-participant.
Explanation PSARB sends an mbus message to all RP running IOS on the chassis, to configure the RP as an IOS non-participant router, therefore, does not interfere with IOX running on this RP. %d - indicates the slot number of the RP that is running IOS on the chassis
Recommended Action Power up the RP that is running IOS with an IOX image. If not, shut down the RP using 'hw-module location slot shutdown' in admin mode.
Error Message%HA-PSARB-6-GO_ACTIVE Card is going active.
Explanation When an RP initially boots up, it can take the active role if no other active RP is present. Also a failure on active or a force switch over could cause the standby RP to change state to active. This message is displayed when the PRP card is going active.
Recommended Action This is an informational message only.
Error Message%HA-PSARB-6-GO_STANDBY Card is going standby.
Explanation When an RP initially boots up, it can take the standby role if an active RP is present. Also a failure on active or a force switch over causes the active RP to change state to standby. This message is displayed when the RP card is going standby.
Recommended Action This is an informational message only.
Error Message%HA-PSARB-6-ROLE_LOCKED (slot [dec]) failover prevented - card role is locked
Explanation The role of this card has been locked - failover was prevented. %d - indicates the slot number of the PRP which it's role is locked
Recommended Action No action is required.
PSARBLC Messages
Error Message%HA-PSARBLC-3-INIT_ERR Process initialization failed: ([chars]%s)
Explanation The psarb-lc process failed to initialize. This process is responsible for monitoring the arbitration messages between the primary and standby RPs and determining which slot contains the primary RP. %s - indicates the reason for the failure. %s - the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-PSARBLC-3-SELF_RESET_DLRSC_DOWN Resetting myself ([dec]), as DLRSC ([dec]) is not present anymore in my LR.
Explanation PSARB knows when a DLRSC (primary RP) in its LR is down and there is no backup DLRSC (secondary RP). PSARB then needs to reset itself as the LR is headless.
Recommended Action Bringup the DLRSC that has gone down in this LR. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REDCON_CLIENT Messages
Error Message%HA-REDCON_CLIENT-3-ERROR [chars]: [chars]: [hex]: [chars]
Explanation A redcon client API failed in the indicated function, for the specified reason.
Recommended Action Collect the function name and traceback information and forward to your next level of technical support. No action is required.
Error Message%HA-REDCON_CLIENT-7-MSG_SEND [chars]: Failed to send [chars] message to redcon: [hex]: [chars]
Explanation An attempt to send a message to the redcon server failed with the specified reason. It may be the case that redcon had been restarted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
REDCON Messages
Error Message%HA-REDCON-1-STANDBY_NOT_READY standby card is NOT ready
Explanation Redcon has determined that the standby card is NOT ready because of the failure of one or more events the prevent it from being in-sync with the active card.
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-1-STANDBY_READY standby card is ready
Explanation Redcon has determined that the standby card is ready to take over as active card if it needs to.
Recommended Action No action is required.
Error Message%HA-REDCON-3-DRIVER_INIT_FAILED initilization of the redundancy driver failed after [dec] attempts
Explanation Redcon has attempted to call the platform-specific redundancy driver initialization function, but the call failed after several attempts.
Recommended Action No action is required.
Error Message%HA-REDCON-3-UNEXPECTED_ERROR Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected error condition encountered.
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-4-FAILOVER_DISABLED Failover has been disabled by config
Explanation Redcon has notified the card failover has been disabled by the configuration.
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-4-FAILOVER_REQUESTED failover has been requested by operator, waiting to initiate
Explanation Redcon on the active card has been told to failover by request
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-4-STANDBY_NOT_READY_ALARM [chars]
Explanation Set: When the standby remains in not ready state for a prolonged period. Cleared: When the standby is removed, reset or goes ready.
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-4-STANDBY_NOT_READY_REASON JID [dec], node [chars], process [chars] set the standby not ready: [chars]
Explanation The named process has set the standby in a not ready state with the supplied reason.
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-4-STBY_ACTIVE_NOT_READY Notice to go active: Card not ready and will be reset
Explanation Redcon attempted to go active without the card ready - reset card
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-4-STBY_CONN_RETRY Connection to [chars] failed - retrying...
Explanation Redcon failed to establish a connection to redcon on the standby card.
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-4-STBY_FORCE_GO_ACTIVE Notice to go active: Not ready but forced failover has been allowed
Explanation Redcon has been forced to go active even though the card is not ready.
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-6-GO_ACTIVE this card going active
Explanation The card is going active.
Recommended Action No action is required.
Error Message%HA-REDCON-6-GO_STANDBY this card going standby
Explanation The card is going standby.
Recommended Action No action is required.
Error Message%HA-REDCON-6-STANDBY_CONNECTION_DOWN connection to standby card is DOWN
Explanation Redcon has determined that the connection to the standby card has gone down.
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-6-STANDBY_CONNECTION_UP connection to standby card is UP
Explanation Redcon has determined that the connection to the standby card has been succesfully completed.
Recommended Action No action is required.
Error Message%HA-REDCON-6-STBY_STANDBY_NOT_READY This card is standby and is NOT ready
Explanation Redcon has determined that the standby card is NOT ready because of the failure of one or more events the prevent it from being in-sync with the active card.
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-6-STBY_STANDBY_READY This card is standby and is ready
Explanation Redcon has determined that the standby card is ready to take over as active card if it needs to.
Recommended Action No action is required.
Error Message%HA-REDCON-7-FAILOVER_ENABLED Failover has been enabled by config
Explanation Redcon has notified the card failover has been enabled by the configuration.
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-7-MSG_SEND_FAILED msg_send [chars] failed [chars] [dec]
Explanation Redcon attempted to call msg_send but it failed.
Recommended Action Collect system log information. No action is required.
Error Message%HA-REDCON-7-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error.
Recommended Action Collect system log information. No action is required.
REDDRV Messages
Error Message%HA-REDDRV-2-MSG_PRIMARY_GLARE primary-primary glare (primary msg from node [hex])
Explanation There appear to be two PRIMARY RP's in the system
Recommended Action None; the node which has arbitrated for the least time will be reset.
Error Message%HA-REDDRV-3-ERROR_EXIT reddrv process exiting because [chars], error code [chars]
Explanation The DRP redundancy driver process exited for the reason mentioned in the message.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered inorder to recover. Execute 'show process reddrv location ' to verify that the process is up and running after the restart. If it is still non-operational, try doing from the admin mode 'process restart reddrv location '. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-REDDRV-3-ROLE_LOCKED (node [hex]) failover prevented - card role is locked
Explanation The role of this card has been locked - failover was prevented.
Recommended Action A failover was initiated, but could not complete because the card role is locked. Please capture the output of 'show reddrv trace' and 'show drp-reddrv trace'.
Error Message%HA-REDDRV-4-CRITERIA_CONFLICT Detected conflicting criteria comparision: [chars]
Explanation Detected conflicting criteria.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-REDDRV-4-FILE_OPEN Failed to open log file for redundancy driver: [chars]
Explanation Failed to open log file for redundancy driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-REDDRV-4-HARDWARE_ERROR Detected Hardware error: [chars].
Explanation Detected hardware error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-REDDRV-4-WD_EXPIRED Failed to punch the watchdog on time [dec] seconds [dec] nanosecs
Explanation Failed to punch the watchdog timer within one second.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.=
Error Message%HA-REDDRV-5-GO_ACTIVE Card is becoming active.
Explanation Card is becoming active.
Recommended Action No action required, just informational message.
Error Message%HA-REDDRV-5-GO_BID Card is going to bid state.
Explanation Card is going to bid state.
Recommended Action No action required, just informational message.
Error Message%HA-REDDRV-5-GO_STANDBY Card is becoming standby.
Explanation Card is becoming standby.
Recommended Action No action required, just informational message.
Error Message%HA-REDDRV-6-DELIVER_POISON_PILL Active sends poision pill packet to peer node [chars]
Explanation Active reddrv issued a poison pill packet to reset peer RP or SC
Recommended Action No action needed. This is to ensure peer RP/SC to drop out from active role
Error Message%HA-REDDRV-6-RESET_SELF No active RP detected for [dec] seconds; resetting this node
Explanation The node on which reddrv is running, resets itself on loss of heartbeat from the RP.
Recommended Action Check the RP in the system. If present, check the connectivity between RP and the node that went down.
Error Message%HA-REDDRV-6-RESET_STANDBY Active [chars] reset standby peer node [chars]
Explanation Issue hardware reset to peer standby RP or SC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.=
Error Message%HA-REDDRV-7-ASYNC_SEND Failed to send async message to redcon : [chars]
Explanation Failed to send async message to redcon.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.=
Error Message%HA-REDDRV-7-ERROR [chars] : [chars]
Explanation A general failure occured while executing a resource function. The message contains info about the cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of Redundancy Driver.
Error Message%HA-REDDRV-7-KDUMPER_MESSAGE [chars]
Explanation Reddrv has received kernel dumper message
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.=
Error Message%HA-REDDRV-7-MESSAGE_RETRY_ERROR Exhausted message retry count of messge type: [chars]
Explanation Received unexpected async error message code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.=
Error Message%HA-REDDRV-7-MISS_ACK_COUNT Missed heart beat acknowledge from standby
Explanation Received unexpected async error message code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.=
Error Message%HA-REDDRV-7-MSG_ERROR Received unexpected message of type: [dec]
Explanation Received unexpected message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.=
Error Message%HA-REDDRV-7-MSG_INVALID_MSGLEN reddrv_msg_handler got [dec] expected [dec]
Explanation reddrv_msg_handler received a message of unexpected size
Recommended Action No action required, software will take corrective action on its own.
Error Message%HA-REDDRV-7-NODE_ERROR [chars] : [chars] : [chars]
Explanation Reddrv had problem to broadcast dead node name notification.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.=
Error Message%HA-REDDRV-7-NODE_RESET Resetting node [chars] for correct active/standby arbitration
Explanation The arbitration state machine needs to be able to reset failed nodes, or other nodes on the same card as a failed node, in order to ensure correct behavior of the state machine and no mixed-role cards.
Recommended Action No action required, just informational message.
Error Message%HA-REDDRV-7-NODE_RESET_FAILED Reset of node [chars] failed with error [chars] - correct active/standby arbitration may not occur in this case
Explanation The arbitration state machine needs to be able to reset failed nodes, or other nodes on the same card as a failed node, in order to ensure correct behavior of the state machine and no mixed-role cards. If this fails, then arbitration may not occur correctly.
Recommended Action Please collect output of 'show redundancy trace', 'show logging' and 'show ltrace shelfmgr'.
Error Message%HA-REDDRV-7-OPERATION_FAIL Failed to [chars], error code [chars]
Explanation The particular operation mentioned in the message failed due to some reason. This is not a critical failure, the process can continue functioning as expected despite the failure.
Recommended Action Debug message only. No action is required.
Error Message%HA-REDDRV-7-REDCON_REREGISTER Recon registration invoked more than once
Explanation The reddrv_redcon_register function was called multiple times
Recommended Action No action required, software will automatically take corrective action.
Error Message%HA-REDDRV-7-ROLE_CHANGE Detected role change to [chars] state due to [chars]
Explanation Detected role change signal.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-REDDRV-7-SHMEM Failed to [chars] share memory region: [chars]
Explanation Failed to create, open or size share memory region.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-REDDRV-7-SW_ROLE_ERROR Detected software role error my_role: [dec] other_role: [dec]
Explanation Detected software role error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-REDDRV-7-UNEXPECTED Unexpected: [chars]: [chars]
Explanation An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere!
Recommended Action Collect system log information. No action is required.
REDSTATS Messages
Error Message%HA-REDSTATS-3-SERVICE_CREATE Failed to create thread for service [dec], name [chars]: [chars]
Explanation The system failed to create the thread that provides the indicated service. This is a fatal error for redstatsd.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-REDSTATS-7-SYSCALL [chars]: [chars](): [chars]
Explanation A system call failed. The calling function, the failed call, and error are displayed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-REDSTATS-7-UNEXPECTED Unexpected: [chars]: [hex] : [chars]
Explanation An unexpected condition encountered. This is not necessarily an error.
Recommended Action Collect system log information. No action is required.
