-
Cisco IOS XR System Error Message Reference Guide, Release 3.8
-
Preface
-
Overview
-
Access Control List (ACL) Messages
-
Application Infrastructure Messages
-
Diagnostic Messages
-
Fabric Messages
-
Forwarding Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 Messages
-
Layer 2 Messages
-
Layer 3 Messages
-
License Messages
-
Media Messages
-
Manageability (MGBL) Messages
-
Operating System (OS) Messages
-
Platform Messages
-
Quality of Service (QoS) Messages
-
Routing Messages
-
Security Messages
-
Services Messages
-
Simple Network Management Protocol (SNMP) Messages
-
System Database Messages
-
Index
-
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:
CDM_CLI Messages
Error Message%HA-CDM_CLI-3-MUTEX_COUNT Mutex(0x[pointer]) locked already is being locked again, count equals [dec]
Explanation A mutex is being locked more than once in the same thread.
Recommended Action Collect coredump and dll info for the process printing the msg.
Error Message%HA-CDM_CLI-7-BAD_BUFFER A client library returned an empty buffer: [chars] [chars]
Explanation A NULL pointer was encountered unexpectedly.
Recommended Action Collect system log information.
Error Message%HA-CDM_CLI-7-BUFFER_MISMATCH Buffer size mismatch: [dec]: [dec]
Explanation A NULL pointer was encountered unexpectedly.
Recommended Action Collect system log information.
Error Message%HA-CDM_CLI-7-INVALID_ARG An invalid argument was passed: [chars]
Explanation An argument was passed with an invalid value.
Recommended Action Collect system log information.
CDM_MEMMGR_HEAP Messages
Error Message%HA-CDM_MEMMGR_HEAP-7-BAD_HEAPIDX heap index [hex] (seg [dec] offset [dec] segsize [dec]) cannot be mapped to segment pointer
Explanation Internally heap pointers are kept as offset indices. A given heap index was found to be outside the heap.
Recommended Action No action is required.
Error Message%HA-CDM_MEMMGR_HEAP-7-BAD_HEAPPAGE Bad heap page block pointer: [chars]: [pointer]
Explanation A heap page address is misaligned or lies in some invalid range.
Recommended Action No action is required.
Error Message%HA-CDM_MEMMGR_HEAP-7-BAD_HEAPPTR heap pointer cannot be mapped to segment offset: [pointer]
Explanation Internally heap pointers are kept as offset indices. A given heap pointer was found to be outside the heap.
Recommended Action No action is required.
Error Message%HA-CDM_MEMMGR_HEAP-7-BAD_NCTDELETE Bad record pointer to free ([char]): [pointer]
Explanation Bad NCT record is being freed.
Recommended Action No action is required.
Error Message%HA-CDM_MEMMGR_HEAP-7-CORRUPTION CDM heap corruption was detected ([chars]). Process will be cold restarted.
Explanation The process crashed during CDM 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-CDM_MEMMGR_HEAP-7-DATA_CORRUPTION Data corruption: [chars]: 0x[dec], 0x[dec], 0x[dec], 0x[dec]
Explanation Data corruption is detected in CDM data structures. This will generally result in a single process failure.
Recommended Action Collect system log information. No action is required.
Error Message%HA-CDM_MEMMGR_HEAP-7-MUNMAP unmap and reserve failed: addr [hex] len [dec], [chars]
Explanation When attempting to free memory that is no longer in use, the CDM library received an error from the kernel.
Recommended Action Collect system log information and forward to technical support.
Error Message%HA-CDM_MEMMGR_HEAP-7-NCT_BIGNEW NCT: requested size too large: [dec]
Explanation Higher layers of heap are requesting a size for a variable-size record that is too large.
Recommended Action No action is required.
Error Message%HA-CDM_MEMMGR_HEAP-7-OBJ_NOT_FOUND Objid [hex] in table [hex] could not be found
Explanation The object could not be found in the given table when attempting to map the object ID to a memory address.
Recommended Action No action is required.
Error Message%HA-CDM_MEMMGR_HEAP-7-PROC_RUNNING CDM segment operation failed: Process [chars] tag [chars] is running on node [chars].
Explanation A request to move or copy CDM 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-CDM_MEMMGR_HEAP-7-SEGMENT_RENAMED CDM file [chars] has been renamed to [chars] for later analysis due to corruption found during restart.
Explanation A corrupted CDM segment has been renamed for later analysis.
Recommended Action Collect system log information. No action is required.
Error Message%HA-CDM_MEMMGR_HEAP-7-TBL_OBJ_SEG_MISMATCH Tblid [hex] objid [hex] segment mismatch (tbl-seg [dec] obj-seg [dec])
Explanation When the table ID and object ID are mapped to segment numbers, they do not match. Since an object belongs to a table and therefore resides in the same segment, this indicates a coding error.
Recommended Action No action is required.
CDM_MEMMGR_UTIL Messages
Error Message%HA-CDM_MEMMGR_UTIL-3-ASSERT_MSG [chars].[dec]: hit assert condition. 'val1 equals [hex]' expected to be [chars] 'val2 equals [hex]'
Explanation cdm hit an internal assert.
Recommended Action Contact support.
Error Message%HA-CDM_MEMMGR_UTIL-7-COLD_RESTART Process has been restarted without CDM data due to request from sysmgr
Explanation Due to too many contiguous failed restarts, sysmgr has requested that the process be restarted without CDM data.
Recommended Action No action is required.
Error Message%HA-CDM_MEMMGR_UTIL-7-COLD_RESTART_IGNORED Ignoring sysmgr cold restart flag
Explanation The process has failed to restart multiple times. By design, the process will continue to restart with its existing CDM data.
Recommended Action Analyze the restart failure and take appropriate recovery action.
Error Message%HA-CDM_MEMMGR_UTIL-7-DEBUG_REGISTER Debug register failed ([hex]): [chars]
Explanation Registration of debug services failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-CDM_MEMMGR_UTIL-7-DUP_KEY [chars]: User key [dec] is in use by object [hex] in table [hex]
Explanation A client of the CDM library attempted to create an object with a key that was already in use.
Recommended Action No action is required.
Error Message%HA-CDM_MEMMGR_UTIL-7-INIT_ERROR initialization error: [chars]: [dec] ([chars])
Explanation An error was encountered during intialization of the CDM 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-CDM_MEMMGR_UTIL-7-NOT_IMPLEMENTED function not implemented yet: [chars]
Explanation Unimplemented functionality.
Recommended Action No action is required.
Error Message%HA-CDM_MEMMGR_UTIL-7-REGISTRATION Error during table registration: [chars]: name: [dec] version: [dec]
Explanation An error was encountered during table registration. The message should indicate the error condition. This is most likely due to a coding error.
Recommended Action No action is required.
Error Message%HA-CDM_MEMMGR_UTIL-7-SYSERR OS/System error: [chars]: [dec] ([chars])
Explanation This message signals an unrecoverable condition reported from the underlying system services. The severity of such errors cannot be determined locally by CDM, so it treats them all such conditions as non-fatal, transient errors. The CDM user must abort its immediate operation.
Recommended Action No action is required.
Error Message%HA-CDM_MEMMGR_UTIL-7-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere.
Recommended Action Collect system log information. No action is required.
Error Message%HA-CDM_MEMMGR_UTIL-7-WARNING Warning: [chars]: [chars]: [dec]
Explanation This provides information about non-error conditions which may even be expected under certain circumstances. Nevertheless, these are not considered 'desirable' conditions.
Recommended Action Collect system log information. No action is required.
CDM_TDM Messages
Error Message%HA-CDM_TDM-7-BAD_ALIGNMENT Index not aligned: [hex]
Explanation A heap index was not word aligned.
Recommended Action No action is required.
Error Message%HA-CDM_TDM-7-COLD_RESTART Cold restart: Reason: [chars]: Application [chars]: table [dec]: version [dec]
Explanation A process failed to restore state from a table in the CDM store.
Recommended Action No action is required.
Error Message%HA-CDM_TDM-7-DUP_TABLE Duplicate table found: Application [chars], table [dec]
Explanation During registration, two copies of a table were found in the CDM store at the same version. This indicates corruption in the CDM store.
Recommended Action No action is required.
Error Message%HA-CDM_TDM-7-NO_TRANSLATOR No translator found: [chars]: [chars]: [chars]
Explanation A required translator was not loaded.
Recommended Action No action is required.
Error Message%HA-CDM_TDM-7-NOT_INDEXED unable to setup index structure for indexed table: [chars]: [hex]: [dec]
Explanation Errors (most likely lack of memory) prevent CDM 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 CDM software will periodically try again to set up the index structure. So, in general no action is required.
Error Message%HA-CDM_TDM-7-OBJ_COUNT table object count not correct: [hex]: [dec] (! equals [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 CDM, but it may cause applications which depend on this accounting info to mis-behave.
Recommended Action No action is required.
Error Message%HA-CDM_TDM-7-OBJ_LEN Bad object length: [chars] tblname: [hex]: object size: [dec] record length: [dec]
Explanation An object save or get operation is being done with the wrong length buffer. This points to a logical bug in the client application.
Recommended Action No action is required.
Error Message%HA-CDM_TDM-7-REG_MISMATCH table attributes changed upon re-register: [hex], [hex]
Explanation An application is trying to register for its table. A table with the same name, version exists, but other attributes have changed, so the table is not allowed to be used.
Recommended Action No action is required.
Error Message%HA-CDM_TDM-7-TRANSLATION_FATAL Fatal translation error: [hex]
Explanation An error occurred during data translation. The process will restart without CDM data.
Recommended Action No action is required.
CHKPT_BASIC Messages
Error Message%HA-CHKPT_BASIC-7-COLD_RESTART Process has been restarted without checkpoint data due to request from sysmgr
Explanation Due to too many contiguous failed restarts, sysmgr has requested that the process be restarted without checkpoint data.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-COLD_RESTART_IGNORED Ignoring sysmgr cold restart flag
Explanation The process has failed to restart multiple times. By design, the process will continue to restart with its existing checkpoint data.
Recommended Action Analyze the restart failure and take appropriate recovery action.
Error Message%HA-CHKPT_BASIC-7-DEBUG_REGISTER Debug register failed ([hex]): [chars]
Explanation Registration of debug services failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-CHKPT_BASIC-7-DUP_KEY [chars]: User key [dec] is in use by object [hex] in table [hex]
Explanation A client of the checkpoint library attempted to create an object with a key that was already in use.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-INCONSISTENT_VERSIONS Inconsistent versioning information: [chars]: native_version: [dec], storage_version: [dec], VS_version: [dec]
Explanation An invalid combination of version numbers was encountered during table registration or table versioning. This is most likely due to a coding error.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-INIT_ERROR initialization error: [chars]: [dec] ([chars])
Explanation An error was encountered during intialization of the checkpoint library. The message should indicate the error condition. This is most likely due to a coding error.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-NOT_IMPLEMENTED function not implemented yet: [chars]
Explanation Unimplemented functionality.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-REGISTRATION Error during table registration: [chars]: name: [dec] version: [dec]
Explanation An error was encountered during table registration. The message should indicate the error condition. This is most likely due to a coding error.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-SYSERR OS/System error: [chars]: [dec] ([chars])
Explanation This message signals an unrecoverable condition reported from the underlying system services. The severity of such errors cannot be determined locally by Checkpointing, so it treats them all such conditions as non-fatal, transient errors. The chkpt user must abort its immediate operation.
Recommended Action No action is required.
Error Message%HA-CHKPT_BASIC-7-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere.
Recommended Action Collect system log information. No action is required.
Error Message%HA-CHKPT_BASIC-7-WARNING Warning: [chars]: [chars]: [dec]
Explanation This provides information about non-error conditions which may even be expected under certain circumstances. Nevertheless, these are not considered 'desirable' conditions.
Recommended Action Collect system log information. No action is required.
CHKPT_CLI Messages
Error Message%HA-CHKPT_CLI-7-BAD_BUFFER A client library returned an empty buffer: [chars] [chars]
Explanation A NULL pointer was encountered unexpectedly.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_CLI-7-BUFFER_MISMATCH Buffer size mismatch: [dec]: [dec]
Explanation A NULL pointer was encountered unexpectedly.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_CLI-7-INVALID_ARG An invalid argument was passed: [chars]
Explanation An argument was passed with an invalid value.
Recommended Action Collect system log information.
CHKPT_HEAP Messages
Error Message%HA-CHKPT_HEAP-7-BAD_HEAPIDX heap index [hex] (seg [dec] offset [dec] segsize [dec]) cannot be mapped to segment pointer
Explanation Internally heap pointers are kept as offset indices. A given heap index was found to be outside the heap.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-BAD_HEAPPAGE Bad heap page block pointer: [chars]: [pointer]
Explanation A heap page address is misaligned or lies in some invalid range.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-BAD_HEAPPTR heap pointer cannot be mapped to segment offset: [pointer]
Explanation Internally heap pointers are kept as offset indices. A given heap pointer was found to be outside the heap.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-BAD_NCTDELETE Bad record pointer to free ([char]): [pointer]
Explanation Bad NCT record is being freed.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-CORRUPTION Checkpoint heap corruption was detected ([chars]). Process will be cold restarted.
Explanation The process crashed during checkpoint heap modification, resulting in an unrecoverable heap. Process will be started from an empty heap.
Recommended Action Collect system log information. No action is required.
Error Message%HA-CHKPT_HEAP-7-DATA_CORRUPTION Data corruption: [chars]: 0x[dec], 0x[dec], 0x[dec], 0x[dec]
Explanation Data corruption is detected in checkpointing data structures. This will generally result in a single process failure.
Recommended Action Collect system log information. No action is required.
Error Message%HA-CHKPT_HEAP-7-MUNMAP unmap and reserve failed: addr [hex] len [dec], [chars]
Explanation When attempting to free memory that is no longer in use, the checkpoint library received an error from the kernel.
Recommended Action Collect system log information and forward to technical support.
Error Message%HA-CHKPT_HEAP-7-NCT_BIGNEW NCT: requested size too large: [dec]
Explanation Higher layers of heap are requesting a size for a variable-size record that is too large.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-OBJ_NOT_FOUND Objid [hex] in table [hex] could not be found
Explanation The object could not be found in the given table when attempting to map the object ID to a memory address.
Recommended Action No action is required.
Error Message%HA-CHKPT_HEAP-7-PROC_RUNNING checkpoint segment operation failed: Process [chars] tag [chars] is running on node [chars].
Explanation A request to move or copy checkpoint data from one node to another has failed because an instance of the process is running on the destination node.
Recommended Action Determine why the process is running on the destination node.
Error Message%HA-CHKPT_HEAP-7-SEGMENT_RENAMED Checkpoint file [chars] has been renamed to [chars] for later analysis due to corruption found during restart.
Explanation A corrupted checkpoint segment has been renamed for later analysis.
Recommended Action Collect system log information. No action is required.
Error Message%HA-CHKPT_HEAP-7-TBL_OBJ_SEG_MISMATCH Tblid [hex] objid [hex] segment mismatch (tbl-seg [dec] obj-seg [dec])
Explanation When the table ID and object ID are mapped to segment numbers, they do not match. Since an object belongs to a table and therefore resides in the same segment, this indicates a coding error.
Recommended Action No action is required.
CHKPT_LIB_COMMS Messages
Error Message%HA-CHKPT_LIB_COMMS-3-SYSTEM_ERROR [chars]: [chars] failed with error [hex]
Explanation A call to a system function failed with the specified error code.
Recommended Action No action is required.
Error Message%HA-CHKPT_LIB_COMMS-6-INFO [chars]:[dec]
Explanation Internal Information messages
Recommended Action No action is required.
Error Message%HA-CHKPT_LIB_COMMS-7-DEBUG [chars]
Explanation Internal Debug Messages
Recommended Action No action is required.
CHKPT_MESSAGING Messages
Error Message%HA-CHKPT_MESSAGING-3-COMMS_INIT_FAIL Chkpt was unable to asynchronously initialise the Replicator Library (error [hex] - [chars]). The client process will be restarted in order to attempt to recover.
Explanation Lib/replicator returned a non-retryable error after the asynchronous retry thread was spawned. There is no way to return an error to the client process, so the library will force an exit to try again. A voluntary core dump should accompany this message to allow further debugging.
Recommended Action Collect system log information and copy core file for offline analysis. Communications debug (e.g. 'show tech gsp') may also be useful.
Error Message%HA-CHKPT_MESSAGING-3-IDT_FAILED Checkpoint Initial Data Transfer failed at [chars] with status code [hex]
Explanation An error occurred during checkpoint Initial Data Transfer which resulted in its failure. A retry of IDT will happen automatically.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BAD_MSGLEN [chars]: message lengths invalid (msglen [dec] srcmsglen [dec] error [hex] ([chars])
Explanation The source message length is less than the message length. This is a situation which should never happen.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BAD_MSGTYPE [chars]: message type [dec] invalid; error [hex] ([chars])
Explanation The message type has the checkpoint component ID, but does not have a message type in the correct range. This is a situation which should never happen.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BAD_REQUEST [chars]: Bad request type [dec] msglen [dec]
Explanation A bad message request was received by the event handler function.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BAD_SEQNO [chars]: request type [dec] had sequence number [dec] (expected [dec])
Explanation The mirroring request had an incorrect sequence number. This indicates either an algorithm error, or data corruption on the active node or in the data transfer between nodes. Initial Data Transfer will be redone, and no data loss should occur.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BAD_TOTALSIZE [chars]: msg totalsize ([dec]) ! equals srcmsglen ([dec] error [hex] ([chars])
Explanation The message header totalsize value must be equal to the source message length. If not, this indicates an IPC or coding error.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-BUFFER_TOO_SMALL Checkpoint library message buffer must be at least [dec] bytes; [dec] bytes is too small for correct operation.
Explanation The message buffer assigned to the checkpoint library by the application is less than the minimum size for successful messaging functionality. The application should increase the size of its event manager message buffer.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-DUPLICATE_PROCESS [chars]: process name [chars] tag [chars] is already running - this should not happen: aborting
Explanation An attempt to exclusive-create on a local channel failed. This indicates that there's already a copy of this same process running, and it cannot be allowed to continue, since corruption can result.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-EVENT_MANAGER [chars]: call to [chars] failed with errno [dec]
Explanation A call to an event manager function failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-GET_MSGLEN [chars]: [chars] failed with error [hex] ([chars])
Explanation Extracting message or source message length failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-IDT_ALL_FAILED All attempts to do Initial Data Transfer to standby failed (error [hex])
Explanation Multiple attempts to transfer initial mirrored data to the standby have failed, and the attempts have been stopped.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-LWM_FAILURE [chars]: call to [chars] failed with error [hex] ([chars])
Explanation A call to a LightWeight Messaging function failed. This may be due to a server being unavailable at the time of the call.
Recommended Action Collect system log information if it appears that this message is linked with failures in functionality. Otherwise, the message can be ignored.
Error Message%HA-CHKPT_MESSAGING-7-MALLOC_FAILED [chars]: malloc of [dec] bytes failed; errno [dec]
Explanation A call to allocate memory failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-MSG_READ [chars]: msg_read (case [dec]) failed with return [dec]; status [hex] ([chars])
Explanation A msg_read call in the message handler failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-MSG_REPLY [chars]: msg_reply (reqtype [dec]) failed with errno [dec]
Explanation A msg_reply call in the message handler failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-MSG_SEND_EVENT [chars]: msg_send_event failed with return [dec]
Explanation A msg_send_event call in a checkpoint mirroring function failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-NON_CHKPT_MSG [chars]: Non-checkpoint message received: comp-id [dec]
Explanation A message request for a non-checkpoint component was received by the handler function.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-PTHREAD_FAILURE [chars]: call to [chars] failed with errno [dec]
Explanation A call to a Posix Pthreads function failed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-REPLICA_NAME Replica name [chars]%s[chars] exceeded the maximum length permitted by Group Services, and has been truncated to [chars]. Replication problems may result if the truncated replica name is non-unique.
Explanation A replica name passed to the Replicator Library was truncated. This is not an issue in itself, but may cause problems further down the line, if the replica name becomes non-unique within the system.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-STANDBY_OPEN_TIMEOUT Attempts to open standby channel [chars] failed after [dec] retries - continuing
Explanation Multiple attempts to open the messasge channel to the standby node (either the application itself or the checkpoint proxy) failed due to either the proxy not running on the standby or the application itself not running on the standby. If the application should run on the standby, then it must call chkpt_init() in order for mirroring to succeed.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-STANDBY_PROXY_SPAWN All attempts to spawn checkpoint proxy on the standby failed (error [hex])
Explanation Multiple attempts to spawn a copy of the checkpoint proxy for this application on the standby were done, and the attempts have been stopped.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-STBY_CAPABLE Call to sysmgr_is_standby_capable failed with error (error [hex])
Explanation The call to sysmgr_is_standby_capable failed. This may be due to the application not having a startup file, and so being unknown to sysmgr.
Recommended Action Collect system log information.
Error Message%HA-CHKPT_MESSAGING-7-SYSMGR_GET_PROC_ROLE [chars]: call to sysmgr_get_proc_role failed with status [hex] ([chars])
Explanation A call to sysmgr_get_proc_role failed with the given status.
Recommended Action Collect system log information.
CHKPT_PROXY Messages
Error Message%HA-CHKPT_PROXY-7-BAD_IPC_LENGTH IPC request type [dec] had bad length [dec] (expected [dec])
Explanation An IPC message with invalid length was received by the proxy process.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-BAD_IPC_REQUEST Bad IPC request type [dec] received with message length [dec]
Explanation An invalid IPC request type was received by the proxy process.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-DEBUG [chars]
Explanation Internal Debug Message
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-GROUP_CREATE_ERROR [chars]: a call to group_create failed with error [dec]
Explanation The proxy process uses group_create() to join the proxy control group. A call to group_create() failed with the specified error.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-IPC_ERROR [chars]: [chars] failed with error [dec]
Explanation As part of IPC operation, a call to a function failed with the specified error.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-NO_MEMORY [chars]: could not allocate [dec] bytes of memory
Explanation Memory allocation failed. This is likely to be a resource shortage rather than a coding error.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-PUTENV [chars]: a call to putenv([chars]) failed with error [dec]
Explanation The proxy process uses putenv() to communicate with the checkpoint library. A call to putenv() failed with the specified error.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-STDBY_NOPROXY Proxy not spawned for LR-plane process '[chars]' due to admin boot hold
Explanation Admin boot hold has ben set for this node (normally due to an install operation) so a chkpt_proxy has not been spawned for this process.
Recommended Action No action is required.
Error Message%HA-CHKPT_PROXY-7-SYSTEM_ERROR [chars]: [chars] failed with error [hex]
Explanation A call to a system function failed with the specified error code.
Recommended Action No action is required.
CHKPT_TDM Messages
Error Message%HA-CHKPT_TDM-4-OOS Checkpoint data on active and standby nodes is out-of-sync: Reason: [chars]: Application [chars]: table [dec]: native version [dec], storage version [dec], VS version [dec]
Explanation A process failed to restore state from a table in the checkpoint store.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-BAD_ALIGNMENT Index not aligned: [hex]
Explanation A heap index was not word aligned.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-COLD_RESTART Cold restart: Reason: [chars]: Application [chars]: table [dec]: native version [dec], storage version [dec], VS version [dec]
Explanation A process failed to restore state from a table in the checkpoint store.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-DUP_TABLE Duplicate table found: Application [chars], table [dec]
Explanation During registration, two copies of a table were found in the checkpoint store at the same version. This indicates corruption in the checkpoint store.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-NATIVE_VERSION Application passed an invalid native version during a checkpoint table versioning operation. Table: [unsigned int], New version: [dec], Heap version: [dec]
Explanation While attempting to version a checkpoint table, an application using checkpoint attempted to pass a native version that was inconsistent with the native version recorded in the checkpoint heap.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-NO_TRANSLATOR No translator found: [chars] : [chars] : [chars]
Explanation A required translator was not loaded.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-NOT_INDEXED unable to setup index structure for indexed table: [chars]: [hex]: [dec]
Explanation Errors (most likely lack of memory) prevent checkpointing from creating an index structure associated with an indexed table. This condition does not affect the functionality at all, only the performance will suffer.
Recommended Action The checkpointing software will periodically try again to set up the index structure. So, in general no action is required.
Error Message%HA-CHKPT_TDM-7-OBJ_COUNT table object count not correct: [hex]: [dec] (! equals [dec])
Explanation A table's object count is not what it's supposed to be. This is an internal accounting error and does not cause any problems inside checkpointing, but it may cause applications which depend on this accounting info to mis-behave.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-OBJ_LEN Bad object length: [chars] tblname: [hex]: object size: [dec] record length: [dec]
Explanation An object save or get operation is being done with the wrong length buffer. This points to a logical bug in the client application.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-REG_MISMATCH table attributes changed upon re-registration: name [unsigned int], version [dec], new attributes: [unsigned int],[unsigned int],[unsigned int], existing attributes: [unsigned int],[unsigned int],[unsigned int]
Explanation An application is trying to register for its table. A table with the same name and version exists, but other attributes have changed, so the table is not allowed to be used.
Recommended Action No action is required.
Error Message%HA-CHKPT_TDM-7-TRANSLATION_FATAL Fatal translation error: [hex]
Explanation An error occurred during data translation. The process will restart without checkpointed data.
Recommended Action No action is required.
DCL_LIB Messages
Error Message%HA-DCL_LIB-2-NULL_PTR [chars]@[dec]: Null Data Pointer Encountered Handle equals [hex] Counter equals [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_SS Messages
Error Message%HA-HA_SS-7-DEBUG MSG1[[chars]] ID[[dec]] MSG2[[chars]]
Explanation Debug message
Recommended Action No action is required.
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.
HM Messages
Error Message%HA-HM-3-FPING_ERROR [chars]
Explanation HA Health Monitor Fabric ping failed
Recommended Action Shelf Manager should receive a critical alarm from HA Health Monitor for this error. The node should be reset by Shelf Manager. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HM-3-FPING_MISMATCH [chars]
Explanation HA Health Monitor Fabric ping failed. When a received ping response does not match the transmitted ping, this indicates some kind of cell corruption or cell loss in the fabric or edges of the fabric.
Recommended Action If problem persist, it indicates the bad hw in the system. Please contact TAC for fault isolation. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HM-4-ERROR_INIT [chars], reason: [chars]
Explanation HA Health Monitor failed to initialize due to internal software errors
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process hm location ' to verify that the process is up and running. If it is still non-operational, try doing 'process restart hm location ' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-HM-4-FPING_INCOMPLETE HM fabric ping only completed [unsigned int] of [unsigned int] pings (ret equals [hex])
Explanation HA Health Monitor Fabric ping test sequence failed to complete. If there were any errors before it got disrupted, then these are reported separately. The test will be restarted again at next HM fping interval. If there are no other errors reported, this warning is rarely a cause for concern, unless it very frequently causes only a partial set of HM fabric pings to be completed.
Recommended Action No action is required because HA Health Monitor will retry Fabric ping again
Error Message%HA-HM-4-FPING_RETRY_ERROR Fabric ping test failed for attempt: [dec], Node will be reset after [dec] retries
Explanation HA Health Monitor Fabric ping failed but will retry again
Recommended Action No action is required because HA Health Monitor will retry Fabric ping again
IRM_CHKPT Messages
Error Message%HA-IRM_CHKPT-7-INIT_ERROR initialization error: [chars]: [dec] ([chars])
Explanation An error was encountered during intialization of the checkpoint library. The message should indicate the error condition. This is most likely due to a coding error.
Recommended Action No action is required.
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-BAG_REGISTRATION Unable to register LRd's bag structures. '[chars]'
Explanation LRd was unable to register bag structures.
Recommended Action Contact support.
Error Message%HA-LRD_inv-3-MEM_ALLOC_FAIL Failed to allocated [dec] bytes of memory: [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Contact TAC.
Error Message%HA-LRD_inv-3-MEM_ALLOC_FAIL Failed to allocated [dec] bytes of memory: [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Contact TAC.
Error Message%HA-LRD_inv-3-MEM_ALLOC_FAIL Failed to allocated [dec] bytes of memory: [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Contact TAC.
Error Message%HA-LRD_inv-3-MEM_ALLOC_FAIL Failed to allocated [dec] bytes of memory: [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Contact TAC.
Error Message%HA-LRD_inv-3-MSG_CERR_REGISTER_DLL Could not register dll with error services: [chars]
Explanation The call register the dll using cerr_register_dll failed.
Recommended Action Contact 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 TAC.
Error Message%HA-LRD_inv-3-MSG_CERR_REGISTER_DLL Could not register dll with error services: [chars]
Explanation The call register the dll using cerr_register_dll failed.
Recommended Action Contact 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_INVENTORY_FWD Error forwarding inventory: '[chars]'
Explanation LRd was unable to read or write information needed to forward inventory in Admin space to the LR Plane.
Recommended Action Contact support.
Error Message%HA-LRD_inv-3-REDUNDANCY_STATE Unrecognized redundancy state [dec]
Explanation LRd doesn't recognize redundancy state.
Recommended Action Contact 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 TAC.
Error Message%HA-LRD_inv-3-SYSDB_ITEM_ERROR sysdb_item_[chars]([chars]) returned '[chars]'
Explanation SysDB returned an error to LRd.
Recommended Action Contact support.
Error Message%HA-LRD_inv-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 designated Shelf Controller.
Recommended Action Collect system log information. No action is required.
Error Message%HA-LRD_inv-4-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere!
Recommended Action Collect system log information. No action is required.
Error Message%HA-LRD_inv-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-NON_DRP_PRIMARY WARNING: A node with unknown type or a non RP/DRP node [chars] is used as primary for SDR
Explanation This is an informational message output during SDR configuration commit time only if a non-RP or non-DRP node is being assigned as primary to the SDR. Please note that if the node is not in IOX-RUN state, it's node type will not be determined.
Recommended Action Verify the card type in the slot being configured as primary for the SDR. If not a DRP or RP card, please replace with valid card type.
Error Message%HA-LRD_inv-6-NON_DRP_PRIMARY WARNING: A node with unknown type or a non RP/DRP node [chars] is used as primary for SDR
Explanation This is an informational message output during SDR configuration commit time only if a non-RP or non-DRP node is being assigned as primary to the SDR. Please note that if the node is not in IOX-RUN state, it's node type will not be determined.
Recommended Action Verify the card type in the slot being configured as primary for the SDR. If not a DRP or RP card, please replace with valid card type.
Error Message%HA-LRD_inv-6-NON_DRP_PRIMARY WARNING: A node with unknown type or a non RP/DRP node [chars] is used as primary for SDR
Explanation This is an informational message output during SDR configuration commit time only if a non-RP or non-DRP node is being assigned as primary to the SDR. Please note that if the node is not in IOX-RUN state, it's node type will not be determined.
Recommended Action Verify the card type in the slot being configured as primary for the SDR. If not a DRP or RP card, please replace with valid card type.
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_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-UNPAIRED_DRP WARNING: A unpaired DRP node [chars] is being added as primary to SDR
Explanation This is an informational message output during SDR configuration commit time only if an unpaired DRP node is being assigned to an SDR.
Recommended Action *none*
Error Message%HA-LRD_inv-6-UNPAIRED_DRP WARNING: A unpaired DRP node [chars] is being added as primary to SDR
Explanation This is an informational message output during SDR configuration commit time only if an unpaired DRP node is being assigned to an SDR.
Recommended Action *none*
Error Message%HA-LRD_inv-6-UNPAIRED_DRP WARNING: A unpaired DRP node [chars] is being added as primary to SDR
Explanation This is an informational message output during SDR configuration commit time only if an unpaired DRP node is being assigned to an SDR.
Recommended Action *none*
LRD Messages
Error Message%HA-LRD-2-EVENTATTACHFAIL event attach failure.
Explanation The LR Daemon encountered an error when registering for synchronous or asynchronous events.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%HA-LRD-2-SYSMGR_GET_NODE_STATE sysmgr get node state failure: [chars].
Explanation sysmgr_get_node_state failed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%HA-LRD-2-SYSMGR_REGISTER node role change registration with sysmgr failed: [chars].
Explanation sysmgr_register_node_state_change_evm failed.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%HA-LRD-3-BAG_REGISTRATION Unable to register LRd's bag structures. '[chars]'
Explanation LRd was unable to register bag structures.
Recommended Action Contact support.
Error Message%HA-LRD-3-MEM_ALLOC_FAIL Failed to allocated [dec] bytes of memory: [chars]
Explanation The requested operation could not be accomplished because of a low memory.
Recommended Action Contact TAC.
Error Message%HA-LRD-3-MSG_CERR_REGISTER_DLL Could not register dll with error services: [chars]
Explanation The call register the dll using cerr_register_dll failed.
Recommended Action Contact support.
Error Message%HA-LRD-3-MSG_INVENTORY_FWD Error forwarding inventory: '[chars]'
Explanation LRd was unable to read or write information needed to forward inventory in Admin space to the LR Plane.
Recommended Action Contact support.
Error Message%HA-LRD-3-REDUNDANCY_STATE Unrecognized redundancy state [dec]
Explanation LRd doesn't recognize redundancy state.
Recommended Action Contact support.
Error Message%HA-LRD-3-SYSDB_ITEM_ERROR sysdb_item_[chars]([chars]) returned '[chars]'
Explanation SysDB returned an error to LRd.
Recommended Action Contact support.
Error Message%HA-LRD-4-CANT_FIND_DSC LR Daemon library could not find the dSC.
Explanation LRdlib could not find the dSC.
Recommended Action Collect system log information. No action is required.
Error Message%HA-LRD-4-HEADLESS_SDR_STATE Headless SDR condition detected, reloading local node.
Explanation Headless SDR condition was detected. The local card is being reset. This is not necessarily an error condition!
Recommended Action Make sure the dSDRSC is up.
Error Message%HA-LRD-4-SDR_PLANE_READY_TIMEOUT Signalling SDR Plane Ready for SDR [chars] ([dec]) (mgmt nodes [dec] of [dec] are NOT READY yet) -[chars]
Explanation SDR Plane ready is being signalled due to SDR plane ready timeout.
Recommended Action Contact TAC.
Error Message%HA-LRD-4-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere!
Recommended Action Collect system log information. No action is required.
Error Message%HA-LRD-4-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere!
Recommended Action Collect system log information. No action is required.
Error Message%HA-LRD-6-LATE_MGMT_NODE Management node [hex] in SDR [chars] ([dec]) is READY after SDR Plane Ready is signalled
Explanation A management node in the specified SDR came up after SDR Plane ready for that SDR was signalled.
Recommended Action Contact TAC.
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.
REDSTATS Messages
Error Message%HA-REDSTATS-3-SERVICE_CREATE Failed to create thread for service [dec], name [chars]: [chars]
Explanation The system failed to create the thread that provides the indicated service. This is a fatal error for redstatsd.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-REDSTATS-7-SYSCALL [chars]: [chars](): [chars]
Explanation A system call failed. The calling function, the failed call, and error are displayed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-REDSTATS-7-UNEXPECTED Unexpected: [chars]: [hex] : [chars]
Explanation An unexpected condition encountered. This is not necessarily an error.
Recommended Action Collect system log information. No action is required.
WD_STAT_PUB Messages
Error Message%HA-WD_STAT_PUB-3-SHM_EDM_ERR [chars]: [chars], ([unsigned int])
Explanation A shared memory for statistics area might be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-WD_STAT_PUB-3-SHM_ERR [chars]: [chars], version: [unsigned int], magic: [hex]
Explanation A shared memory for statistics area might be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-WD_STAT_PUB-3-SHMEM [chars]: Error. initializing shared memory. ([chars])
Explanation Failed to initialize the shared memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%HA-WD_STAT_PUB-7-SYSCALL [chars]: [chars](): [chars]
Explanation A system call failed. Error reason will be displayed on the console.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
