-
Cisco IOS XR System Error Message Reference Guide, Release 3.2
-
Preface
-
Cisco IOS XR System Error Messages Overview
-
Access Control List (ACL) Error Messages for Cisco IOS XR
-
Fabric (FABRIC) Error Messages for Cisco IOS XR
-
Hardware Accessibility (HA) Messages for Cisco IOS XR
-
Installation (INSTALL) Messages for Cisco IOS XR
-
Internet Protocol (IP) Messages for Cisco IOS XR
-
Layer 2 (L2) Messages for Cisco IOS XR
-
Media (MEDIA) Messages on Cisco IOS XR
-
Manageability (MGBL) Messages for Cisco IOS XR
-
Operating System (OS) Messages for Cisco IOS XR
-
Packet Infrastructure (PKT_INFRA) Messages for Cisco IOS XR
-
Platform (PLATFORM) Messages for Cisco IOS XR
-
Quality of Service (QOS) Messages for Cisco IOS XR
-
Routing (ROUTING) Messages for Cisco IOS XR
-
Security (SECURITY) Messages for Cisco IOS XR
-
Simple Network Management Protocol (SNMP) Messages for Cisco IOS XR
-
System Database (SYSDB) Messages for Cisco IOS XR
-
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-2-NOT_IMPLEMENTED function not implemented yet: [chars]
Explanation Unimplemented functionality.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-3-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-3-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-3-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-3-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-3-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-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-CHKPT_BASIC-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-CHKPT_BASIC-4-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.
Error Message%HA-CHKPT_BASIC-5-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-6-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.
CHKPT_CLI Messages
Error Message%HA-CHKPT_CLI-3-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-3-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-3-INVALID_ARG An invalid argument was passed: [chars]
Explanation An argument was passed with an invalid value.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_CLI-3-MALLOC Malloc returned a null pointer.
Explanation Malloc returned a null pointer. This indicates an out of memory condition. The CLI process will exit or return.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_CLI-3-SYSERR A system call failed: [hex]
Explanation A system called returned a non-zero value for errno.
Recommended Action Collect system log information.
CHKPT_HEAP Messages
Error Message%HA-CHKPT_HEAP-2-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-2-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-3-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-3-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-3-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-3-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-3-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-3-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-3-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-3-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.
Error Message%HA-CHKPT_HEAP-4-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-6-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.
CHKPT_MESSAGING Messages
Error Message%HA-CHKPT_MESSAGING-3-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-3-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-3-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-3-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-3-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-3-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-3-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-3-FLUSH_QUEUE [chars]: flushing standby update queue failed with status [hex] - reconnecting
Explanation An attempt to flush the standby update queue of mirrored data to the standby node failed. The connection to the standby will be closed and reopened, then Initial Data Transfer will be done.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-3-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-3-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-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 reconnection to the standby node and retry of IDT will happen automatically.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-3-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-3-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-3-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-3-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-3-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-3-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-3-REQUEST_FAIL [chars]: msg handler for reqtype [dec] failed with status [hex]
Explanation The checkpoint message handler executed the request, which failed with the given status.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-3-SEND_REQUEST [chars]: sending mirroring request failed with status [hex] - reconnecting
Explanation An attempt to send a mirroring request to the standby node failed. The connection to the standby will be closed and reopened, then Initial Data Transfer will be done.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-3-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-3-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-3-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-3-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.
Error Message%HA-CHKPT_MESSAGING-4-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-4-MSG_SEND [chars]: msg_send (reqtype [dec]) failed with return [dec]; status [hex]
Explanation A msg_send call in a checkpoint mirroring function failed. The checkpoint library will resync the active and the standby automatically.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-6-IDT_BEGIN Checkpoint Initial Data Transfer to standby node is beginning
Explanation The process has connected with a peer entity on the standby node and has begun to transfer data for all mirrored checkpoint tables.
Recommended Action No action is required.
Error Message%HA-CHKPT_MESSAGING-6-IDT_DATA Checkpoint Initial Data Transfer sending [dec] bytes of data
Explanation The data transfer part of IDT is taking place.
Recommended Action No action is required.
Error Message%HA-CHKPT_MESSAGING-6-IDT_DONE Checkpoint Initial Data Transfer to standby node has finished (chunks: [dec], bytes: [dec])
Explanation The process has finished transferring initial mirrored checkpoint data to the standby node.
Recommended Action No action is required.
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.
CHKPT_PROXY Messages
Error Message%HA-CHKPT_PROXY-3-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-3-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-3-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-3-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-3-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-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.
CHKPT_TDM Messages
Error Message%HA-CHKPT_TDM-3-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-3-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-3-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.
Error Message%HA-CHKPT_TDM-4-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-4-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-4-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-4-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-4-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-4-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.
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-3-FMFD_MISC_ERR [chars]: [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-3-FMFD_RESPAWN_COUNT [chars]: could not get process respawn count: [chars]
Explanation The fault detector has failed to get the process respawn count.
Recommended Action Copy the error message exactly as it appears 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-3-FMFD_WD_CPU_ERR Could not set new system CPU state ([unsigned int])
Explanation The cpu state has changed setting the 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-3-FMMD_CHKPT_INIT [chars]: 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-3-FMMD_CHKPT_TBL_INFO_READ [chars]: could not read the existing table information: [chars]
Explanation Failed to read the existing table information using checkpointing API.
Recommended Action Copy the error message exactly as it appears 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-3-FMMD_CHKPT_TBL_INIT [chars]: 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-3-FMMD_CHKPT_TBL_RECOVER [chars]: 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-3-FMMD_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_FM-3-FMMD_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_FM-3-FMMD_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_FM-3-FMMD_GET_CHID [chars]: 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-3-FMMD_GET_NODE_NAME [chars]: 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-3-FMMD_METRICSVC_INIT [chars]: 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-3-FMMD_MSG_CHAN_ATTACH [chars]: 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-3-FMMD_MSG_SEND_ASYNC [chars]: 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-3-FMMD_QSM_REG_NOTIF [chars]: 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-3-FMMD_SVC_REG [chars]: 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-3-FMMD_SVCEVM_CREATE [chars]: 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-3-FMMD_TUPLE_PACK [chars]: could not pack sysdb tuple
Explanation Internal error. The Fault Manager Metric Director failed to pack the sysdb tuple.
Recommended Action Copy the error message exactly as it appears 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-3-FMS_MISC_ERR [chars]: [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-3-FMS_MSG_SEND_ASYNC [chars]: 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-3-FMSD_CHKPT_INIT [chars]: 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-3-FMSD_CHKPT_TBL_INFO_READ [chars]: could not read the existing table information: [chars]
Explanation Failed to read the existing table information using checkpointing API.
Recommended Action Copy the error message exactly as it appears 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-3-FMSD_CHKPT_TBL_INIT [chars]: 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-3-FMSD_CHKPT_TBL_RECOVER [chars]: 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-3-FMSD_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_FM-3-FMSD_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_FM-3-FMSD_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_FM-3-FMSD_EVM_INIT_EVENT [chars]: 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-3-FMSD_FM_INIT [chars]: 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-3-FMSD_GET_PRIO [chars]: 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-3-FMSD_OVL_NOTIF_REG [chars]: 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-3-FMSD_POLICY_UNREG_ERR [chars]: 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-3-FMSD_POLICY_UNREGREG_ERR [chars]: 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 Copy the error message exactly as it appears 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-3-FMSD_PTHRD_CREATE [chars]: failed to create POSIX thread: [chars]
Explanation An internal error occured 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_FM-3-FMSD_SVC_REG [chars]: 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-3-FMSD_SVCEVM_CREATE [chars]: 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-3-FMSD_SYSDB_BIND [chars]: could not bind to SysDB path [chars]: [chars]
Explanation An internal error was detected when trying to bind to the given SysDB path.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HA_FM-3-FMSD_SYSDB_NOTIFY_REG [chars]: could not register for SysDB notification for item [chars] under namespace [chars]: [chars]
Explanation An internal error was detected when trying to register notify function for SysDB tuple operations upon the given item within the given SysDB 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-3-FMSD_SYSDB_VERIFY_REG [chars]: could not register for SysDB verification for item [chars] under namespace [chars]: [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-4-FMS_GET_NODE_STATE [chars]: Failed to get the current nodes state: return = [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-4-FMS_REG_NODE_STATE_CHANGE [chars]: Failed to register for node state changes: return = [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-4-FMSD_RESYNC_FAIL Could not re-add file [chars] to syncfs list: Error [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-4-FMSD_SYNC_FAIL Could not add file [chars] to syncfs list: Error [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-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 Copy the error message exactly as it appears 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-FMFD_WD_CPU_NOTIF_ALARM CPU consumption is [chars] at [unsigned int] percent
Explanation The CPU state has changed and the new state is announced.
Recommended Action Copy the error message exactly as it appears 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-FMS_POLICY_EXEC [chars]: Policy execution has been [chars]
Explanation The Fault Manager policy excution state has been changed to the state named 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_FM-6-FMS_RELOAD_SYSTEM [chars]: Policy has requested a system reload; reloading in 5 seconds
Explanation A Fault Manager policy requested that the system 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_FM-6-FMSD_POLICY_CHANGED [chars]: 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 [chars]: 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_UNREG_SUCC [chars]: 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 [chars]: 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 [chars]: 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 [chars]: 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 [chars]: 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 [chars]: Unable to send response for FM_MSG_APPL_PUB_DONE [chars]
Explanation The application publish callback handler was unable to send the FM_MSG_APPL_PUB_DONE message 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_EV_CREATE [chars]: event_manager_create failed [chars]
Explanation The event_manager_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-FMC_CB_INIT_FMC [chars]: fm_init_fmc failed [chars]
Explanation The fm_init_fmc function reported an error trying to initialize the internal fm 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 [chars]: msg_chan_attach failed [chars]
Explanation The msg_chan_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-FMC_CBS_PT_CREATE [chars]: pthread_create failed [chars]
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-FMC_CERR_REG [chars]: Unable to register cerr dll: [chars]
Explanation The cerr_register_dll function could not register with the fault manager dynamically loaded 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-FMC_REG_CBH_PULSE [chars]: Unable to locate reg callback entry for pulse code [dec]
Explanation The registration callback handler was unable to validate the pulse code 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 [chars]: Unable to send response for FM_MSG_CALLBACK_DONE [chars]
Explanation The registration callback handler was unable to send the FM_MSG_CALLBACK_DONE message 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]: [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_ADD [chars]: [chars]
Explanation Internal error. The fault detector has failed to add a record to 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_CHKPT_TBL_GET [chars]: [chars]
Explanation Internal error. The fault detector has failed to retrieve data from a record in 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_CHKPT_TBL_INIT [chars]: [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]: [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_CHKPT_TBL_REMOVE [chars]: [chars]
Explanation Internal error. The fault detector has failed to remove a record from 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_CLI_REQCODE [chars]: invalid request code: [dec]
Explanation Internal error. The request code in the message from the CLI parser 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_DE_FETCH [chars]: [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]: [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 [chars]: 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 [chars]: 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 [chars]: 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_EV_BLOCK [chars]: event_block error: [chars]
Explanation The event_block 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_EVM_CREATE [chars]: 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_HIST_QERR [chars]
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_HIST_RBLD [chars]: [chars]
Explanation Internal error. The fault detector has failed to rebuild the history 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_INV_CDEVENT [chars]: invalid card event: [dec]
Explanation Internal error. The fault detector has received an invalid card event which indicates a condition which is not card insertion or removal.
Recommended Action Copy the error message exactly as it appears 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 [chars]: 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_NODEID [chars]: invalid nodeid [hex]
Explanation An invalid 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_INV_STATS_TYPE [chars]: 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 [chars]: 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 [chars]: 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 [chars]: 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_MET_ENQUEUE [chars]: 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]: [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_MSGSEND_EVT [chars]: [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 [chars]: [dec]
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_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_FM-7-FMFD_OE_CREATE [chars]: 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 [chars]: 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 [chars]: 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_PROC_ENT [chars]: [chars]: no more table entries for this process
Explanation Internal error. The fault detector has run out of memory collecting statistics for a new 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_PTHRD_CREATE [chars]: 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_PUB_ENQUEUE [chars]: [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]: [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_PUB_TM_ALLOC [chars]: could not allocate memory for event publish timer block
Explanation Internal error. The fault detector has failed to allocate memory for the event publish timer 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-FMFD_RM_ATTACH [chars]: 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]: [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]: [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]: [chars]
Explanation The sysdb_bind 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_SYSDB_IGET [chars]: [chars]
Explanation The sysdb_item_get 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_SYSDB_LIST_ERR [chars]: [chars]
Explanation Internal error. The fault detector has failed listing the interface directory 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_SYSDB_NOTREG [chars]: [chars]
Explanation The sysdb_register_notification 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 [chars]: 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]: [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 [chars]: 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 [chars]: 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 [chars]: 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-FMFD_WD_DB1_QERR [chars]
Explanation Internal error. The fault detector has failed to get a free wdsysmon 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_WD_DB2_QERR [chars]
Explanation Internal error. The fault detector has failed to get a free wdsysmon 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-FMMD_CHKPT_NULL_PTR [chars]: 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 [chars]: 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_REMOVE [chars]: 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-FMMD_CHKPT_TBL_RESET [chars]: 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-FMMD_CONN_EXIST [chars]: the message connection we try to set up already exists
Explanation An internal error. We try 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_FILE_ATTACH [chars]: 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 [chars]: 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 [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_FM-7-FMMD_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_FM-7-FMMD_FD_SIGEVENT [chars]: 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 [chars]: 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_GUARD_WORD_VER [chars]: [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_INV_NODEID [chars]: invalid nodeid [hex]
Explanation An invalid 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_LAST_PROC [chars]: 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 [chars]: 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 [chars]: 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_METRIC_POLL [chars]: 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_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_FM-7-FMMD_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_FM-7-FMMD_MSG_SEND [chars]: 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_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_FM-7-FMMD_PROC_END_TYPE [chars]: unknown process end type [dec]
Explanation An unknown Fault Manager process end 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_PROC_EVENT_TYPE [chars]: 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_SYSCALL [chars]: [chars] failed ([dec]): [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_SYSDB_BIND [chars]: Can't bind to SysDB at [chars]; [chars]
Explanation The sysdb_bind 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-FMMD_SYSDB_ITEM_CREATE [chars]: Can't create SysDB item [chars]; [chars]
Explanation The sysdb_item_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-FMMD_SYSDB_UNBIND [chars]: Can't unbind from SysDB at [chars]; [chars]
Explanation The sysdb_unbind 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-FMMD_UNEXP_MSG_TYPE [chars]: 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 [chars]: 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 [chars]: 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_APPL_PUBINFO_ENQUEUE [chars]: Failed to queue application event publish info; [chars]
Explanation The appl_pubinfo_enqueue 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_ASYNC_ATTACH [chars]: 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_ABNOR [chars]: Failed to attach to handle FM_PULSE_ABNORMAL_EXIT; [chars]
Explanation The event_async_attach function reported an error trying to attach to handle the FM_PULSE_ABNORMAL_EXIT 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_ASYNC_ATTACH_FD [chars]: 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_ASYNC_ATTACH_NOR [chars]: Failed to attach to handle FM_PULSE_NORMAL_EXIT; [chars]
Explanation The event_async_attach function reported an error trying to attach to handle the FM_PULSE_NORMAL_EXIT 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 [chars]: 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 [chars]: 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 [chars]: 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_INFO_READ [chars]: could not read the existing table information: [chars]
Explanation Failed to read the existing table information using checkpointing API.
Recommended Action Copy the error message exactly as it appears 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 [chars]: 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 [chars]: 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 [chars]: 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 [chars]: 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_EVENT_BLOCK [chars]: Error reported by event_block function; [chars]
Explanation The event_block 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_EVENT_FILE_ATTACH [chars]: 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_EVENT_INIT_EVENT [chars]: 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_EVM_CREATE [chars]: event_manager_create failed; [chars]
Explanation The event_manager_create function reported an error trying to initialize 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-FMS_FDC_ALLOCATE [chars]: 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 [chars]: 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 [chars]: msg_get_chan_chan failed; [chars]
Explanation The msg_get_chan_chan function reported an error trying to obtain the channel chid.
Recommended Action Copy the error message exactly as it appears 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 [chars]: platform_get_node_name failed; [chars]
Explanation The platform_get_node_name function reported an error 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_PRIO [chars]: 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]: [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_OVL [chars]: event_init_event failed initializing OVL sigevent; [chars]
Explanation The event_init_event function reported an error trying to initialize the OVL notification 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_FM-7-FMS_INIT_EVENT_TIMER [chars]: event_init_event failed initializing TIMER sigevent; [chars]
Explanation The event_init_event function reported an error trying to initialize the TIMER notification 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_FM-7-FMS_INV_ARG_STRING [chars]: Invalid argument string: [chars]
Explanation An invlaid argument string was passed to the specified 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-FMS_INV_ENV_STRING [chars]: Invalid environment string: [chars]
Explanation An invlaid environment string was passed to the specified 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-FMS_KILL [chars]: 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 [chars]: 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_MALLOC [chars]: Unable to allocate [chars]; [chars]
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_MSG_ATTACH_SYNC [chars]: 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_MSG_CHAN_ATTACH [chars]: 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_MSG_CHAN_CONNECT [chars]: 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_MSG_CHAN_DISCONNECT [chars]: 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_MSG_SEND [chars]: 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_MSG_SEND_EVENT [chars]: 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_NULL_SCRIPT_NAME [chars]: The script name is NULL
Explanation An invalid script name was passed as an argument into the specified function.
Recommended Action Copy the error message exactly as it appears 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 [chars]: 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 [chars]: 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 [chars]: 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 [chars]: 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 [chars]: 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 [chars]: 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 [chars]: 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_REALLOC [chars]: Unable to reallocate [chars]; [chars]
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_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 [chars]: 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 [chars]: 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 [chars]: 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_STRDUP [chars]: Failed to duplicate string [chars]; [chars]
Explanation The strdup 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_SYSDB_BIND [chars]: Can't bind to SysDB at [chars]; [chars]
Explanation The sysdb_bind 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_SYSDB_ITEM_CREATE [chars]: Can't create SysDB item [chars]; [chars]
Explanation The sysdb_item_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-FMS_SYSDB_ITEM_DELETE [chars]: Can't delete SysDB item [chars]; [chars]
Explanation The sysdb_item_delete 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_SYSDB_ITEM_GET [chars]: Can't get SysDB item [chars]; [chars]
Explanation The sysdb_item_get 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_SYSDB_ITEM_SET [chars]: Can't set SysDB item [chars]; [chars]
Explanation The sysdb_item_set 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_SYSDB_UNBIND [chars]: Can't unbind from SysDB at [chars]; [chars]
Explanation The sysdb_unbind 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 [chars]: Failed to unload Syslog FD DLL [chars]; return code=[dec]
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_SYSLOG_SCAN_SIGNUP [chars]: Failed to load Syslog FD DLL [chars]; return code=[dec]
Explanation The syslog_scan_signup function reported an error trying to load 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_SYSMGR_RELOAD_FM [chars]: Failed to load Sysmgr FD DLL [chars]; return code=[dec]
Explanation The sysmgr_reload_fm_detector function reported an error trying to load the specified Sysmgr 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 [chars]: 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 [chars]: 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 [chars]: 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-FMS_WDSYSMON_RELOAD_FM [chars]: Failed to load WDSysMon FD DLL [chars]; return code=[dec]
Explanation The wd_reload_fm_detector function reported an error trying to load the specified WDSysMon 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-FMSD_CHKPT_NULL_PTR [chars]: 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 [chars]: 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_REMOVE [chars]: 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 [chars]: 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 [chars]: 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 [chars]: 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 [chars]: 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 [chars]: unknown event type [dec]
Explanation An unknown Fault Manager even 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_FILE_OPEN [chars]: 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_GET_NODE_NAME [chars]: 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_LAST_POLICY [chars]: 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_LONG_PATHNAME [chars]: 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-FMSD_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_FM-7-FMSD_OVL_SETUP_ENV [chars]: 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_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_TIMER_ARM [chars]: 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-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_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-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 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-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-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 [chars]
Explanation The router has changed state
No action is required.
HM Messages
Error Message%HA-HM-1-REG_PM_ERROR [chars], ([dec], [chars])
Explanation HA Health Monitor Fault handler connection 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-HM-3-ERROR_INIT [chars], ([dec], [chars])
Explanation HA Health Monitor init 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-HM-3-ERROR_INIT_EVM [chars]
Explanation HA Health Monitor init 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-HM-3-FAB_SVR_ERROR [chars]
Explanation HA Health Monitor error related to fabric 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-HM-3-FPING_ERROR [chars]
Explanation HA Health Monitor Fabric ping 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-HM-3-FPING_RETRY_ERROR Fabric ping test failed for attempt: [dec], Node will be reset after [dec] retries
Explanation HA Health Monitor Fabric ping 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-HM-3-SYSDB_ERROR [chars], ([dec], [chars])
Explanation HA Health Monitor sysdb 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-HM-3-TIMER_ERROR [chars], ([dec])
Explanation HA Health Monitor timer 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-HM-3-TIMER_INIT_ERROR [chars]
Explanation HA Health Monitor timer 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.
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-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-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_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 support.
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 support.
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-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-MSG_MALLOC Couldn't malloc [dec] bytes: [chars]
Explanation The requested memory is not available
Recommended Action Contact support.
Error Message%HA-LRD_inv-3-MSG_MALLOC Couldn't malloc [dec] bytes: [chars]
Explanation The requested memory is not available
Recommended Action Contact support.
Error Message%HA-LRD_inv-3-MSG_MALLOC Couldn't malloc [dec] bytes: [chars]
Explanation The requested memory is not available
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 support.
Error Message%HA-LRD_inv-3-REDUNDANCY_STATE Unrecognized redundancy state [dec]
Explanation LRd doesn't recognize redundancy state.
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 support.
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-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 dSC.
Recommended Action Collect system log information. No action is required.
Error Message%HA-LRD_inv-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_inv-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_inv-4-INVENTORY_LATE Waited [dec] seconds and inventory still looks incomplete. Proceeding as if complete. ([hex])
Explanation The system will wait some time for inventory to appear before continuing with boot. At that time it will mark inventory complete even if some slots might still be missing. This is in order to prevent a problematic slot or glitch in system boot to paralyze the entire system. In most cases, the system missed the timing window by a small amount and there is no serious problem, but it may also be the case that there is a serious problem in the system.
Recommended Action Contact support.
Error Message%HA-LRD_inv-4-INVENTORY_LATE Waited [dec] seconds and inventory still looks incomplete. Proceeding as if complete. ([hex])
Explanation The system will wait some time for inventory to appear before continuing with boot. At that time it will mark inventory complete even if some slots might still be missing. This is in order to prevent a problematic slot or glitch in system boot to paralyze the entire system. In most cases, the system missed the timing window by a small amount and there is no serious problem, but it may also be the case that there is a serious problem in the system.
Recommended Action Contact support.
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-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-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_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-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-MSG_MALLOC Couldn't malloc [dec] bytes: [chars]
Explanation The requested memory is not available
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-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.
PSARB Messages
Error Message%HA-PSARB-2-MSG_HEARTBEAT_LOST Slot [dec] heartbeat lost. Resetting slot.
Explanation psarb has lost the heartbeat of the indicated slot.
Recommended Action No action is required.
Error Message%HA-PSARB-2-MSG_PRIMARY_GLARE primary-primary glare (primary msg from slot [dec])
Explanation There appear to be two PRIMARY RP's in the system
Recommended Action None, the cards involved in the glare will be reset.
Error Message%HA-PSARB-2-WRONG_SLOT Rebooting RP in slot [dec] because it conflicts with an already operational RP in slot [dec]. If you intend to use the conflicting RP as a standby partner, please move the RP to slot [dec]. Or, if the RP is meant to be used in another logical router, please ensure it is assigned to the other LR.
Explanation Card pairing requires primary/standby cards in specific slots and active RP's need to be in seperate LR's.
Recommended Action Move standby RP card to correct slot in chassis, or assign to distinct LR.
Error Message%HA-PSARB-3-FAILED_LR_CONNECT Could not connect to LRd for [dec] seconds. Retrying...
Explanation PSARB needs to be informed when a card is added or removed from the Logical Router. PSARB has been unable to connect to LRd so it can not determine whether a card has been added or removed..
Recommended Action Do not attempt to configure Logical Routers while this is happening. Something is wrong with the infrastructure that should be investigated.
Error Message%HA-PSARB-3-FAILED_LR_EVENT Could not extract the '[chars]' for Inventory Event. ([chars])
Explanation PSARB needs to be informed when a card is added or removed from a Logical Router. PSARB has received an event from LRd that it could not interpret.
Recommended Action If LRs were not just reconfigured you may ignore this error. If an LR was recently added to the system or a slot was moved from or into this LR then restarting PSARB on all the RPs should fix this situation. This is a bug and should be reported.
Error Message%HA-PSARB-3-FAILED_TO_RESET_SLOT Encountered error ([dec], '[chars]') attempting to reset LC in slot [dec].
Explanation PSARB resets all linecards on initial boot. One of the LC reset attempts failed.
Recommended Action The LC that failed to reset is in a suspect state. Manually reboot it if it appears to be having problems.
Error Message%HA-PSARB-3-FAILED_TO_RESET_THRU_SYSLDR_API Failed to reset card in slot [dec] using [chars]. Calling [chars] as an equivalent workaround.
Explanation PSARB may reset cards under certain circumstances. One of the reset attempts failed. PSARB will try again to reset the card using the workaround specified in the message.
Recommended Action No action is required.
Error Message%HA-PSARB-3-MSG_CALL_FAIL [chars] call to [chars] failed, err = [dec]
Explanation Internal error - software bug
Recommended Action Contact support.
Error Message%HA-PSARB-3-MSG_CANT_CREATE_CHANNEL unable to create channel, errno [dec] [chars]
Explanation Unable to create required channel; low resources?
Recommended Action Contact support.
Error Message%HA-PSARB-3-MSG_CANT_CREATE_LRD_THREAD unable to pthread_create lrd thread, errno [dec] [chars]
Explanation Unable to create thread; low resources?
Recommended Action Contact support.
Error Message%HA-PSARB-3-MSG_CANT_CREATE_RESMGR_THREAD unable to pthread_create resmgr_start thread, errno [dec] [chars]
Explanation Unable to create thread; low resources?
Recommended Action Contact support.
Error Message%HA-PSARB-3-MSG_CANT_GET_NODEID unable to get nodeid, retrying...
Explanation Unable to detect MBUS slot number, MBUS driver failure?
Recommended Action Contact support.
Error Message%HA-PSARB-3-MSG_CANT_RESMGR_PATHNAME_ATTACH unable to resmgr_pathname_attach, errno [dec] [chars]
Explanation Unable to bind name; low resources?
Recommended Action Contact support.
Error Message%HA-PSARB-3-MSG_FAILED_TO_MBUS_SEND_MESSAGE (slot [dec]): failed to mbus_send_message, errno [dec] ([chars])
Explanation A failure was encountered when sending a message to the MBUS driver.
Recommended Action If this error persists, then there is (most likely) a hardware problem with the MBUS; contact a service representative.
Error Message%HA-PSARB-3-MSG_FAILED_TO_OPEN_MBUS (slot [dec]): failed to open MBUS at [chars], errno [dec] ([chars])
Explanation The MBUS driver isn't available at this point.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%HA-PSARB-3-MSG_FAILED_TO_SELECT_MBUS_PARMS (slot [dec]): failed to select MBUS parms, errno [dec] ([chars])
Explanation The MBUS driver didn't accept a standard request.
Recommended Action If this problem persists, contact a service representative.
Error Message%HA-PSARB-3-MSG_FTRUNCATE_FAILED unable to ftruncate shared memory object [chars], errno [dec] [chars]
Explanation Unable to ftruncate shared memory object; possible coding bug
Recommended Action Contact support.
Error Message%HA-PSARB-3-MSG_INVALID_MSG (slot [dec]): invalid msg [hex]
Explanation A message was received from the MBUS that had the PSARB module ID in it, but with an unknown type.
Recommended Action Software version mismatch, or possible hardware fault on the MBUS, contact service representative.
Error Message%HA-PSARB-3-MSG_INVALID_STATE (slot [dec]): invalid state [hex]
Explanation Internal variable has been set to a value that should never occur.
Recommended Action This should never happen; contact service rep.
Error Message%HA-PSARB-3-MSG_MMAP_FAILED unable to mmap shared memory object [chars], errno [dec] [chars]
Explanation Unable to mmap shared memory object; possible coding bug
Recommended Action Contact support.
Error Message%HA-PSARB-3-MSG_SEM_INIT_FAILED (slot [dec]) unable to initialize a semaphore, errno [dec] [chars]
Explanation Unable to initialize a semaphore; low resources?
Recommended Action Contact support.
Error Message%HA-PSARB-3-MSG_SEM_WAIT_FAILED (slot [dec]) unable to wait on a semaphore, errno [dec] [chars]
Explanation Unable to wait on a semaphore; bad initialization?
Recommended Action Contact support.
Error Message%HA-PSARB-3-MSG_SHMEM_OPEN_FAILED unable to create shared memory object [chars], errno [dec] [chars]
Explanation Unable to create shared memory object; low resources?
Recommended Action Contact support.
Error Message%HA-PSARB-3-MSG_UNEXPECTED_TERMINATION Unexpected termination of [chars]
Explanation The PSARB module should never exit; if this message occurrs, it indicates that the module is about to exit. This is a 'should never happen' case.
Recommended Action No action is required.
Error Message%HA-PSARB-3-MSG_USAGE usage: [chars] [-t timebase(msec, default 100ms)] &
Explanation Incorrect command line arguments were given to the module
Recommended Action Contact support.
Error Message%HA-PSARB-3-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).
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-3-SYSDB_BIND Unable to bind to sysdb. Error was: [chars]
Explanation Unable to bind to sysdb.
Recommended Action Contact support.
Error Message%HA-PSARB-3-SYSDB_ITEM_SET Unable to set item [chars] in sysdb. Error was: [chars]
Explanation Unable to set item in sysdb.
Recommended Action Contact support.
Error Message%HA-PSARB-4-IOS_RP_DETECTED Detected an RP on 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.
Recommended Action Shut down the RP that is running IOS using 'mtool power' or physical OIR.
Error Message%HA-PSARB-4-POSIX [chars]: function [chars] failed with error [dec] ([chars])
Explanation A Posix function call failed.
Recommended Action No action is required.
Error Message%HA-PSARB-5-MSG_STARTING Starting [chars]
Explanation Normal startup information indicating that the PSARB module is starting.
Recommended Action No action is required.
Error Message%HA-PSARB-6-MSG_INVALID_CLINFO [chars]: unknown clinfo: [hex]
Explanation A function received a message of unexpected size
Recommended Action No action is required.
Error Message%HA-PSARB-6-MSG_INVALID_LRD_NOTIFY psarb was not able to handle an lrd notification: [dec]
Explanation psarb_msg_handler received a message of unexpected size
Recommended Action No action is required.
Error Message%HA-PSARB-6-MSG_INVALID_MSGLEN psarb_msg_handler got [dec] expected [dec]
Explanation psarb_msg_handler received a message of unexpected size
Recommended Action No action is required.
Error Message%HA-PSARB-6-MSG_INVALID_PAIRING [chars]: Invalid lrd pairing attempted: [dec] with [dec]
Explanation An attempt was made to assign an invalid partner to the indicated slot
Recommended Action No action is required.
Error Message%HA-PSARB-6-MSG_REDCON_REREGISTER psarb_redcon_register called more than once
Explanation The psarb_redcon_register function was called multiple times
Recommended Action Contact support.
Error Message%HA-PSARB-6-MSG_SOFTWARE_VERSION (slot [dec]) software version [dec]
Explanation Normal startup information indicating the MBUS slot number that the RP card is in, and the software version number that will be broadcast by this node in its bid to become primary.
Recommended Action No action is required.
Error Message%HA-PSARB-6-MSG_TRANSIT_TO_BID (slot [dec]) transit to bid state
Explanation This particular RP has entered a bid to become PRIMARY.
Recommended Action No action is required.
Error Message%HA-PSARB-6-MSG_TRANSIT_TO_FAILOVER (slot [dec]) transit to failover state
Explanation This particular RP has entered been told to be a non-participant, and give up.
Recommended Action No action is required.
Error Message%HA-PSARB-6-MSG_TRANSIT_TO_PRIMARY (slot [dec]) transit to primary state
Explanation This particular RP has succeeded in its bid to become PRIMARY.
Recommended Action No action is required.
Error Message%HA-PSARB-6-MSG_TRANSIT_TO_STANDBY (slot [dec]) transit to standby state
Explanation This particular RP has failed in its bid to become PRIMARY, and is now operating as a STANDBY unit.
Recommended Action No action is required.
Error Message%HA-PSARB-6-RESET_OLD_ACTIVE Resetting old active partner card in slot [dec]
Explanation When going active from standby, the old active card in our partner slot is reset.
Recommended Action No action is required.
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.
Recommended Action No action is required.
Error Message%HA-PSARB-7-GO_ACTIVE Card is going active.
Explanation Card is going active.
Recommended Action No action is required.
Error Message%HA-PSARB-7-GO_BID Card is going to bid state.
Explanation Card is going to bid state.
Recommended Action No action is required.
Error Message%HA-PSARB-7-GO_STANDBY Card is going standby.
Explanation Card is going standby.
Recommended Action No action is required.
Error Message%HA-PSARB-7-RESET_ALL_LC_CARDS RP going active; resetting all linecards in chassis
Explanation Due to critical state on the active RP, all LCs are initialized to the same state as the active RP.
Recommended Action No action is required.
PSARBLC Messages
Error Message%HA-PSARBLC-3-FAILED_LR_CONNECT Could not connect to LRd for [dec] seconds. Retrying...
Explanation PSARB needs to be informed when a card is added or removed from the Logical Router. PSARB has been unable to connect to LRd so it can not determine whether a card has been added or removed..
Recommended Action Do not attempt to configure Logical Routers while this is happening. Something is wrong with the infrastructure that should be investigated.
Error Message%HA-PSARBLC-3-FAILED_LR_EVENT Could not extract the '[chars]' for Inventory Event. ([chars])
Explanation PSARB needs to be informed when a card is added or removed from a Logical Router. PSARB has received an event from LRd that it could not interpret.
Recommended Action If LRs were not just reconfigured you may ignore this error. If an LR was recently added to the system or a slot was moved from or into this LR then restarting PSARB on all the RPs should fix this situation. This is a bug and should be reported.
Error Message%HA-PSARBLC-3-FAILED_TO_RESET_SLOT Encountered error ([dec], '[chars]') attempting to reset LC in slot [dec].
Explanation PSARB resets the Line Card (LC) when the corresponding LR becomes headless (meaning DLRSC goes down). The LC reset failed. The LC is running headless. Future system install operations may fail.
Recommended Action From the owner LR, reload the LC using 'admin hw-module location reload'.
Error Message%HA-PSARBLC-3-FAILED_TO_RESET_THRU_SYSLDR_API Failed to reset card in slot [dec] using [chars]. Calling [chars] as an equivalent workaround.
Explanation PSARB resets self LC when the corresponding LR becomes headless (meaning DLRSC goes down). One of the LC reset attempts failed. PSARB will try again to reset the LC.
Recommended Action No action is required.
Error Message%HA-PSARBLC-3-MSG_CALL_FAIL [chars] call to [chars] failed, err = [dec]
Explanation Internal error - software bug
Recommended Action Contact support.
Error Message%HA-PSARBLC-3-MSG_FTRUNCATE_FAILED unable to ftruncate shared memory object [chars], errno [dec] [chars]
Explanation Unable to ftruncate shared memory object; possible coding bug
Recommended Action Contact support.
Error Message%HA-PSARBLC-3-MSG_MMAP_FAILED unable to mmap shared memory object [chars], errno [dec] [chars]
Explanation Unable to mmap shared memory object; possible coding bug
Recommended Action Contact support.
Error Message%HA-PSARBLC-3-MSG_MUTEX_INIT_FAILED unable to initialize mutex object, errno [dec] ([chars])
Explanation Unable to initialize mutex object
Recommended Action Contact support.
Error Message%HA-PSARBLC-3-MSG_SHMEM_OPEN_FAILED unable to create shared memory object [chars], errno [dec] [chars]
Explanation Unable to create shared memory object; low resources?
Recommended Action Contact support.
Error Message%HA-PSARBLC-3-MSG_UNEXPECTED_TERMINATION Unexpected termination of [chars]
Explanation The PSARB module should never exit; if this message occurrs, it indicates that the module is about to exit. This is a 'should never happen' case.
Recommended Action No action is required.
Error Message%HA-PSARBLC-3-MSG_USAGE usage: [chars] [-t timebase(msec, default 100ms)] &
Explanation Incorrect command line arguments were given to the module
Recommended Action Contact support.
Error Message%HA-PSARBLC-3-PTHREAD_CREATE_FAILED unable to create new thread, errno [dec] ([chars])
Explanation Unable to create timeout thread in arbitration listener
Recommended Action Contact support.
Error Message%HA-PSARBLC-3-UNKNOWN_MSG_TYPE psarb listener: unknown msg type: [dec]
Explanation unknown msg type
Recommended Action Contact support.
Error Message%HA-PSARBLC-4-MSG_RP_SLOT slot [dec]: [chars]
Explanation RP slot position (Debug message)
Recommended Action --
Error Message%HA-PSARBLC-4-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.
Error Message%HA-PSARBLC-6-MSG_INVALID_PAIRING [chars]: Invalid lrd pairing attempted: [dec] with [dec]
Explanation An attempt was made to assign an invalid partner to the indicatedf slot
Recommended Action No action is required.
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-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 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-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-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-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_HEARTBEAT_LOST Node [hex] heartbeat lost - resetting that node.
Explanation reddrv has lost the heartbeat of the indicated node.
Recommended Action No action is required.
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-2-WRONG_NODE Standby RP booted in wrong node relative to primary RP. Move card to node [hex].
Explanation Card pairing requires primary/standby cards in specific nodes.
Recommended Action Move standby RP card to correct node in chassis.
Error Message%HA-REDDRV-3-ASYNC_ATTACH_FAIL Failed to attach handler for async events: [chars]
Explanation Failed to attach handler for async 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-REDDRV-3-ETHERNET_GET_MY_MAC [chars]: eth_server_get_my_macaddr failed with return [dec]
Explanation Getting local MAC address from the control ethernet server failed.
Recommended Action None.
Error Message%HA-REDDRV-3-ETHERNET_OPEN [chars]: eth_server_open failed with return [dec] - retrying
Explanation Open of the control ethernet server failed.
Recommended Action None.
Error Message%HA-REDDRV-3-ETHERNET_READ [chars]: eth_server_read failed with return [dec]
Explanation Read of a heartbeat/arbitration message on the control ethernet failed.
Recommended Action Contact support.
Error Message%HA-REDDRV-3-ETHERNET_WRITE [chars]: eth_server_write to MAC address [chars] failed with return [dec]
Explanation Transmission of a heartbeat/arbitration message on the control ethernet failed.
Recommended Action Contact support.
Error Message%HA-REDDRV-3-EVM_CREATE_FAIL Failed to create event manager: [chars]
Explanation Failed to create 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-REDDRV-3-FAILED_TO_RESET_SLOT Encountered error ([dec], '[chars]') attempting to reset LC in slot [dec].
Explanation reddrv resets all linecards on initial boot. One of the LC reset attempts failed.
Recommended Action The LC that failed to reset is in a suspect state. Manually reboot it if it appears to be having problems.
Error Message%HA-REDDRV-3-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-3-IPC_CREATE Failed to create peer-to-peer communication channel: [chars]
Explanation Failed to create peer-to-peer communication 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-REDDRV-3-MMAP_FAIL Failed to map registers to process space: [chars]
Explanation Failed to mmap REDDRV registers.
Recommended Action Copy the error message exactly as it appears 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-MSG_ATTACH_FAIL Failed to attach handler for sync events: [chars]
Explanation Failed to attach handler for sync 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-REDDRV-3-MSG_CALL_FAIL [chars] call to [chars] failed, err = [dec]
Explanation Internal error - software bug
Recommended Action Contact support.
Error Message%HA-REDDRV-3-MSG_CANT_CREATE_CHANNEL unable to create channel, errno [dec] [chars]
Explanation Unable to create required channel; low resources?
Recommended Action Contact support.
Error Message%HA-REDDRV-3-MSG_CANT_CREATE_THREAD unable to pthread_create [chars] thread, errno [dec] ([chars])
Explanation Unable to create thread; low resources?
Recommended Action Contact support.
Error Message%HA-REDDRV-3-MSG_CANT_GET_NODEID unable to get nodeid, retrying...
Explanation Unable to use platform APIs to determine node ID.
Recommended Action Contact support.
Error Message%HA-REDDRV-3-MSG_CANT_RESMGR_PATHNAME_ATTACH unable to resmgr_pathname_attach, errno [dec] [chars]
Explanation Unable to bind name; low resources?
Recommended Action Contact support.
Error Message%HA-REDDRV-3-MSG_CHAN_CREATE Failed to connect to message channel: [chars]
Explanation Failed to attach handler for sync 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-REDDRV-3-MSG_FTRUNCATE_FAILED unable to ftruncate shared memory object [chars], errno [dec] [chars]
Explanation Unable to ftruncate shared memory object; possible coding bug
Recommended Action Contact support.
Error Message%HA-REDDRV-3-MSG_INVALID_CLINFO [chars]: unknown clinfo: [hex]
Explanation A function received a message of unexpected size
Recommended Action No action is required.
Error Message%HA-REDDRV-3-MSG_INVALID_LRD_NOTIFY reddrv was not able to handle an lrd notification: [dec]
Explanation reddrv_msg_handler received a message of unexpected size
Recommended Action No action is required.
Error Message%HA-REDDRV-3-MSG_INVALID_MSGLEN reddrv_msg_handler got [dec] expected [dec]
Explanation reddrv_msg_handler received a message of unexpected size
Recommended Action No action is required.
Error Message%HA-REDDRV-3-MSG_INVALID_PAIRING [chars]: Invalid lrd pairing attempted: [dec] with [dec]
Explanation An attempt was made to assign an invalid partner to the indicated slot
Recommended Action No action is required.
Error Message%HA-REDDRV-3-MSG_MMAP_FAILED unable to mmap shared memory object [chars], errno [dec] [chars]
Explanation Unable to mmap shared memory object; possible coding bug
Recommended Action Contact support.
Error Message%HA-REDDRV-3-MSG_REDCON_REREGISTER reddrv_redcon_register called more than once
Explanation The reddrv_redcon_register function was called multiple times
Recommended Action Contact support.
Error Message%HA-REDDRV-3-MSG_SEM_INIT_FAILED (node [hex]) unable to initialize a semaphore, errno [dec] [chars]
Explanation Unable to initialize a semaphore; low resources?
Recommended Action Contact support.
Error Message%HA-REDDRV-3-MSG_SEM_WAIT_FAILED (node [hex]) unable to wait on a semaphore, errno [dec] [chars]
Explanation Unable to wait on a semaphore; bad initialization?
Recommended Action Contact support.
Error Message%HA-REDDRV-3-MSG_SHMEM_OPEN_FAILED unable to create shared memory object [chars], errno [dec] [chars]
Explanation Unable to create shared memory object; low resources?
Recommended Action Contact support.
Error Message%HA-REDDRV-3-MSG_TRANSIT_TO_BID (slot [dec]) transit to bid state
Explanation This particular RP has entered a bid to become PRIMARY.
Recommended Action No action is required.
Error Message%HA-REDDRV-3-MSG_TRANSIT_TO_FAILOVER (node [hex]) transit to failover state
Explanation This particular RP has entered been told to be a non-participant, and give up.
Recommended Action No action is required.
Error Message%HA-REDDRV-3-MSG_TRANSIT_TO_PRIMARY (node [hex]) transit to primary state
Explanation This particular RP has succeeded in its bid to become PRIMARY.
Recommended Action No action is required.
Error Message%HA-REDDRV-3-MSG_TRANSIT_TO_STANDBY (node [hex]) transit to standby state
Explanation This particular RP has failed in its bid to become PRIMARY, and is now operating as a STANDBY unit.
Recommended Action No action is required.
Error Message%HA-REDDRV-3-MSG_UNEXPECTED_TERMINATION Unexpected termination of [chars]
Explanation The reddrv module should never exit; if this message occurrs, it indicates that the module is about to exit. This is a 'should never happen' case.
Recommended Action No action is required.
Error Message%HA-REDDRV-3-MSG_USAGE usage: [chars] [-t timebase(msec, default 200ms)] &
Explanation Incorrect command line arguments were given to the module
Recommended Action Contact support.
Error Message%HA-REDDRV-3-NODEID_TO_MACADDR [chars]: call to convert node [hex] to MAC address failed with error [hex]
Explanation Conversion of node IDs to MAC addresses is required to be able to do a unicast on the control ethernet for arbitration heartbeats.
Recommended Action Contact support.
Error Message%HA-REDDRV-3-NOT_POSSIBLE_DSC This node is not a dSC candidate
Explanation reddrv has determined that this node is not a candidate to be dSC. This means that it is not part of the Owner LR. This also means that the box will not function unless another RP is booted as dSC. This condition is caused by the ROMMON variable 'is_owner_rp' being set to 0.
Recommended Action No action is required.
Error Message%HA-REDDRV-3-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).
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-REDDRV-3-RESET_ALL_LC_CARDS RP going active; resetting all linecards in chassis
Explanation Due to critical state on the active RP, all LCs are initialized to the same state as the active RP.
Recommended Action No action is required.
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 No action is required.
Error Message%HA-REDDRV-3-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-3-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-3-SYSDB_BIND Unable to bind to sysdb: [chars]
Explanation Unable to bind to sysdb.
Recommended Action Contact support.
Error Message%HA-REDDRV-3-SYSDB_ITEM_SET Unable to set item [chars] in sysdb. Error was: [chars]
Explanation Unable to set item in sysdb.
Recommended Action Contact support.
Error Message%HA-REDDRV-3-THREAD_CREATE_FAIL Failed to create [chars] thread
Explanation Failed to create threads.
Recommended Action Copy the error message exactly as it appears 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-ASYNC_MSG_ERROR Received unexpected async error message of code: [dec]
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-4-ASYNC_SEND Failed to send async message to redcon errno : [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-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-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-4-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-4-MSG_ERROR Received unexpected message of code: [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-4-MSG_SEND Failed to send message to reddrv
Explanation Failed to send message to reddrv.
Recommended Action Copy the error message exactly as it appears 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-POSIX [chars]: function [chars] failed with error [dec] ([chars])
Explanation A Posix function call failed.
Recommended Action No action is required.
Error Message%HA-REDDRV-4-RESET_CALL_FAIL [chars]: a call to reset node [hex] failed
Explanation The arbitration state machine needs to be able to reset failed nodes, or other nodes on the same card as a failed node, and the reset call failed.
Recommended Action None.
Error Message%HA-REDDRV-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-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 is required.
Error Message%HA-REDDRV-5-GO_BID Card is going to bid state.
Explanation Card is going to bid state.
Recommended Action No action is required.
Error Message%HA-REDDRV-5-GO_STANDBY Card is becoming standby.
Explanation Card is becoming standby.
Recommended Action No action is required.
Error Message%HA-REDDRV-5-MSG_STARTING Starting [chars]
Explanation Normal startup information indicating that the reddrv module is starting.
Recommended Action No action is required.
Error Message%HA-REDDRV-5-NODE_RESET [chars]: resetting node [hex] 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 None.
Error Message%HA-REDDRV-6-RESET_SELF [chars]: 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 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-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.
