Cisco IOS XR System Error Message Reference Guide, Release 4.3.x
High Availability (HA) Messages
Downloads: This chapterpdf (PDF - 697.0KB) The complete bookPDF (PDF - 19.88MB) | Feedback

High Availability (HA) Messages

Table Of Contents

High Availability (HA) Messages

CDM_CLI Messages

CDM_MEMMGR_HEAP Messages

CDM_MEMMGR_UTIL Messages

CDM_TDM Messages

CHKPT_BASIC Messages

CHKPT_CLI Messages

CHKPT_CLIENT Messages

CHKPT_HEAP Messages

CHKPT_LIB_COMMS Messages

CHKPT_MESSAGING Messages

CHKPT_PROXY Messages

CHKPT_TDM Messages

DCL_LIB Messages

ENF_BROKER Messages

HA_EM Messages

HA_SS Messages

HA_WD_LIB Messages

HA_WD Messages

HM Messages

IRM_CHKPT Messages

LRD_inv Messages

LRD Messages

REDCON_CLIENT Messages

REDCON Messages

REDSTATS Messages

RMF_CLIENT Messages

WD_STAT_PUB Messages


High Availability (HA) Messages


This section contains all High Availability related System Error Messages.

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 0x%zx (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: %zd

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]: 0x%zx

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: 0x%zx

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]: [hex]

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_CLIENT Messages

Error Message     
 
    
    
   

%HA-CHKPT_CLIENT-3-CONFLICT_ISSU_FLAG Conflicting ISSU flag specified for process [chars] jid [dec] component [dec]. Existing shared memory reuse flag is [dec] and new flag is [dec].

Explanation    When chkpt is used by multiple DLLs from within the same process context, they all need to specify same value for shared memory reuse flag.

Recommended Action    Save the above error message. Note down the component ID from the above error message and open a DDTS against that component and attach this error message.

Error Message     
 
    
    
   

%HA-CHKPT_CLIENT-3-DLL_NOT_PROVIDED Mirroring enabled for this client but translator DLL not provided.

Explanation    Every chkpt client that requires mirroring should provide call back DLL to handle the endian neutral transformation. If DLL is not provided, check pointed records might get corrupted in mixed endian mode RP.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%HA-CHKPT_CLIENT-7-CALLBACK_NOT_REQUIRED Checkpoint client has not registered translator DLL with chkpt. Chkpt assumes that the endianess is handled by the client appropriately.

Explanation    Some clients wishes to store their records in NBO format. In such cases, there is no need to register callback DLL with chkpt since no X86 transformation is needed in such cases.

Recommended Action    No action is required.

CHKPT_HEAP Messages

Error Message     
 
    
    
   

%HA-CHKPT_HEAP-7-BAD_HEAPIDX heap index 0x%zx (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 0x[pointer] len %zd, [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: %zd

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 0x%zx in table 0x%zx 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 0x%zx objid 0x%zx 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 %zd

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 (%zd 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-IDT_DIFF_NODE_TYPE IDT received from different endian node type. Endian transformation needed.

Explanation    Just debug information to know that active RP is of different endian type.

Recommended Action    None.

Error Message     
 
    
    
   

%HA-CHKPT_MESSAGING-7-IDT_XFORM_COMPLETED Endian transformation of IDT portion of data completed.

Explanation    --

Recommended Action    None.

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 %zd 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]:[dec]: Non-checkpoint message received: comp-id [dec] req type [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.

Error Message     
 
    
    
   

%HA-CHKPT_MESSAGING-7-X86_XFORM_AFTER After conversion:[chars]

Explanation    To print the values after conversion.

Recommended Action    X

Error Message     
 
    
    
   

%HA-CHKPT_MESSAGING-7-X86_XFORM_BEFORE Before conversion:[chars]

Explanation    To print the values before conversion.

Recommended Action    X

Error Message     
 
    
    
   

%HA-CHKPT_MESSAGING-7-X86_XFORM_DBG [chars]:[dec] - [chars]

Explanation    For UT

Recommended Action    X

CHKPT_PROXY Messages

Error Message     
 
    
    
   

%HA-CHKPT_PROXY-7-BAD_IPC_LENGTH IPC request type [dec] had bad length %zd (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 %zd

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: 0x%zx

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 0x[pointer] Counter equals 0x[pointer]

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.

ENF_BROKER Messages

Error Message     
 
    
    
   

%HA-ENF_BROKER-3-INITIALIZATION_FAILURE Failure during initialization. A call to [chars] failed. Error: [chars]

Explanation    The Enf Broker process wasn't able to startup up due the indicated failure during initialization. A restart of the process will be attempted. If the process cannot be successfully started after several attempts, enf service will be unavailable.

Recommended Action    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-ENF_BROKER-7-CLIENT_CONN_FAILURE Unable to create a client connection object.

Explanation    The Enf Broker process was unable to create a client connection info object for saving the client information (most likely lack of memory). This condition does not impact the functionality, but may result in degradation in performance of this feature.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

HA_EM Messages

Error Message     
 
    
    
   

%HA-HA_EM-7-EEMED_EA_ATTACH Could not register for asynchronous message events: [chars]

Explanation    The event 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_EM-7-EEMED_EA_ATTACH Could not register for asynchronous message events: [chars]

Explanation    The event 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_EM-7-EEMED_EI_EVENT Could not initialize event structure: [chars]

Explanation    The event 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_EM-7-EEMED_EI_EVENT Could not initialize event structure: [chars]

Explanation    The event 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_EM-7-EEMED_EM_ATTACH Could not register for sychronous message events: [chars]

Explanation    The event 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_EM-7-EEMED_EM_ATTACH Could not register for sychronous message events: [chars]

Explanation    The event 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_EM-7-EEMED_EVM_CREATE Could not create event manager: [chars]

Explanation    The event 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_EM-7-EEMED_EVM_CREATE Could not create event manager: [chars]

Explanation    The event 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_EM-7-EEMED_EVM_EVENT_BLOCK An error occurred while waiting for an event: [chars]

Explanation    The event infrastructure will ignore this error and continue to wait for the next event. If this error is seen repeatedly, the process may not be able to function and will need to be restarted.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_EM-7-EEMED_EVM_EVENT_BLOCK An error occurred while waiting for an event: [chars]

Explanation    The event infrastructure will ignore this error and continue to wait for the next event. If this error is seen repeatedly, the process may not be able to function and will need to be restarted.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_EM-7-EEMS_FILE_OPEN Failed to open file [chars] : [chars]

Explanation    Failed to open the given file due to some internal error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_EM-7-EEMS_GET_CHAN_CHAN Failed to obtain a messaging channel ID: [chars]

Explanation    An error was reported trying to obtain the channel ID.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_EM-7-EEMS_GUARD_WORD_VER [chars] guard word corrupted; [pointer]

Explanation    The guard word for the specified control block does not contain what is expected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_EM-7-EEMS_MEM_ALLOC Not enough memory ([dec] bytes)

Explanation    Allocating memory failed due to a low-memory condition.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%HA-HA_EM-7-FMS_ASYNC_ATTACH_FD [chars]: Failed to attach to handle Event Detector [chars] pulse code; [chars]

Explanation    The event_pulse_attach_event function reported an error trying to attach to handle the Event 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_EM-7-FMS_EVM_FILE_ATTACH Unable to do an event_file_attach for [chars]: [chars]

Explanation    The event_file_attach function reported an error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_EM-7-FMS_EVM_INIT_EVENT event_init_event for Embedded Event 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_EM-7-FMS_LWM_ATTACH Failed to attach to eem message channel: [chars]

Explanation    The msg_chan_attach function reported an error trying to attach to the Embedded Event 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_EM-7-FMS_LWM_ATTACH_SYNC Failed to attach to handle synchronous messages: [chars]

Explanation    The event_message_attach function reported an error trying to attach to handle synchronous messages.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_EM-7-FMS_LWM_CONNECT Failed to connect to eem message channel [chars]: [chars]

Explanation    The msg_chan_connect function reported an error trying to connect to the specified Embedded Event 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_EM-7-FMS_LWM_DISCONNECT Failed to disconnect from eem message channel [chars]: [chars]

Explanation    The msg_chan_disconnect function reported an error trying to disconnect from the specified Embedded Event 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_EM-7-FMS_LWM_SEND Failed to send a message to [chars]: [chars]

Explanation    The msg_send function reported an error trying to send a message to the specified process.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_EM-7-FMS_LWM_SEND_ASYNC Could not send a pulse to a connection: [chars]

Explanation    An internal error was detected when trying to send a pulse to a connection.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_EM-7-FMS_LWM_SEND_EVENT Failed to send an event to [chars]: [chars]

Explanation    The msg_send_event function reported an error trying to send an asynchronous message to the specified process.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_EM-7-FMS_QSM_REG_NOTIF Could not register for QSM notification: [chars]

Explanation    An internal error was detected when registering for QSM notification.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

HA_WD Messages

Error Message     
 
    
    
   

%HA-HA_WD-1-ABORTING [chars], Aborting.

Explanation    The system is experiencing CPU Hog, If this condition persists for 30 seconds, the node will be reloaded.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-1-CPU_HOG_5 Process [chars] pid [dec] tid [dec] prio [dec] using [dec]% is hogging CPU and will be terminated

Explanation    This message is displayed

Recommended Action    The command 'show watchdog trace' will display additional information about the potential CPU hog. If the hog is persistant, contact technical support. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-1-CPU_HOG_ALERT Process [chars] pid [dec] tid [dec] prio [dec] using [dec]% is the top user of CPU.

Explanation    This message is displayed after the CPU hog detector trips. It shows the percentage of CPU used by the busiest thread in the top consumer of CPU.

Recommended Action    The command 'show watchdog trace' will display additional information about the potential CPU hog. If the hog is persistant, contact technical support. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-1-CURRENT_STATE Persistent Hog detected for more than [dec] seconds

Explanation    The system is experiencing CPU Hog, If this condition persists for 30 seconds, the node will be reloaded.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-1-DISK_ALERT A monitored device [chars] is above [dec]% utilization. Current utilization equals [dec]. Please remove unwanted user files and configuration rollback points.

Explanation    When some monitored disk's usage is above 99%.

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-2-DISK_CRIT A monitored device [chars] is above [dec]% utilization. Current utilization equals [dec]. Please remove unwanted user files and configuration rollback points.

Explanation    When some monitored disk's usage is above 95%.

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-3-DEBUG_REGISTER_FAIL Call to debug_register() failed with error [dec] ([chars])

Explanation    An internal error was detected when registering with the debug library.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-DEVCTL [chars]: line [dec]: devctl() on file [chars] failed with error [dec] ([chars])

Explanation    Failed to open procfs file or directory.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-EVM_ASYNC_ATTACH [chars]: could not attach handler for Event Manager asynchronous event: [chars]

Explanation    An internal error was detected when attaching a handler for an Event Manager asynchronous event.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-EVM_CREATE [chars]: could not create event manager: [chars]

Explanation    An internal error was detected when creating Event Manager.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-EVM_EVENT_BLOCK [chars]: failed to block waiting for Event Manager events: [chars]

Explanation    An internal error was detected when block waiting for Event Manager events.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-EVM_INIT_EVENT [chars]: failed to initialize a sigevent structure: [chars]

Explanation    An internal error was detected when trying to initialize a sigevent structure.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-EVM_MSG_ATTACH [chars]: could not attach handler for Event Manager synchronous message: [chars]

Explanation    An internal error was detected when attaching a handler for an Event Manager synchronous message.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-EVM_THREAD_INIT [chars]: unable to initialize event manager thread: [chars]

Explanation    An error occured when attempting to initialize the event manager thread.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-EVM_TM_ATTACH [chars]: could not set up a managed timer identifier: [chars]

Explanation    An internal error was detected when trying to allocate a managed timer identifier and assign to it an event handler.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-EVM_TM_DETACH [chars]: could not set up a managed timer identifier: [chars]

Explanation    An internal error was detected when trying to remove a managed timer registration from an event manager.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-EVM_TM_LEAF_NEW [chars]: could not create a managed timer tree leaf: [chars]

Explanation    An internal error was detected when trying to create a managed timer tree leaf for the event manager.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-FD_CRIT_LIM Process [chars], pid [dec] is using [dec] file descriptors out of a max of [dec]. Critical limit ([dec]%) crossed.

Explanation    A process is potentially leaking FDs. Critical limit has been crossed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-FD_INIT [chars]: failed to initialize fault detector: [chars]

Explanation    An internal error was detected when initializing the fault detector.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-3-FREE_MEM_ADDR Unable to get address of free memory variable from kernel.

Explanation    Wdsysmon was not able to get access to free memory information from kernel.

Recommended Action    Copy the error message exactly as it appears on the 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-HELPER_INIT_FAIL Failed to init helper lib. [chars]: [chars]

Explanation    The system failed to initialize helper library. 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-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] [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-DISK_WARN A monitored device [chars] is above [dec]% utilization. Current utilization equals [dec]. Please remove unwanted user files and configuration rollback points.

Explanation    When some monitored disk's usage is above 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-DSC_REG_FAILED [chars]: Failed to register for DSC event with sysmgr, error: [chars]

Explanation    sysmgr_register_lr_event failed to register for DSC notification event

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-FD_MAJ_LIM Process [chars], pid [dec] is using [dec] file descriptors out of a max of [dec]. Major limit ([dec]%) crossed.

Explanation    A process is potentially leaking FDs. Major limit has been crossed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-4-FD_MIN_LIM Process [chars], pid [dec] is using [dec] file descriptors out of a max of [dec]. Minor Limit ([dec]%) crossed.

Explanation    A process is potentially leaking FDs. Minor limit has been crossed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-4-FD_NORMAL_LIM Process [chars], pid [dec], is now using [dec] file descriptors. Status is Normal

Explanation    --

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-4-MEM_POLL [chars]: Failed to poll for memory usage: [chars]

Explanation    An error was encountered during wdsysmon's poll for system memory usage.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-4-MEMORY_ALARM Memory threshold crossed: [chars] with [unsigned int].[unsigned int]MB free

Explanation    Set: Free memory on this node is below the reported threshold. Clear: Free memory is above the MINOR theshold. In both cases, the amount of free memory in megabytes is reported.

Recommended Action    Investigate memory usage on this node. It may be necessary to unconfigure some applications or move them to a different node. In the case of memory leaks, technical support may need to be contacted.

Error Message     
 
    
    
   

%HA-HA_WD-4-MEMORY_LIMIT_EXCEEDED Process [chars][[dec]] (pid [dec]) has exceeded its memory limit:[dec] kbytes of heap allowed, [dec] kbytes of heap used. (Info:[dec] kbytes of virtual shared memory used).

Explanation    The process with the indicated name and pid has allocated more memory than its memory limit allows. The process will be restarted.

Recommended Action    The system will collect data about the process before it is killed. Collect this data and forward it to technical support. Most likely, there is a memory leak in the process.

Error Message     
 
    
    
   

%HA-HA_WD-4-MEMORY_STATE_CHANGE New memory state: [chars]

Explanation    The free memory state of this node has changed to the indicated state.

Recommended Action    If the free memory state is Severe or Critical, investigate memory usage on this node. It may be necessary to unconfigure some applications or move them to a different node. In the case of memory leaks, technical support may need to be contacted.

Error Message     
 
    
    
   

%HA-HA_WD-4-TOP_MEMORY_USER_WARNING [dec]: Process Name: [chars][[dec]], pid: [dec][chars], Heap usage [dec] Kbytes, Virtual Shared memory usage: [dec] Kbytes.

Explanation    This process is one of the top memory users in the system. If the system reaches critical memory exhaustion, this process is subject to restart or termination. If the process is listed as 'Killed', then the system is in the process of recovering the resources used by the process.

Recommended Action    Collect system log information. Contact technical support if the problem is not a misconfiguration.

Error Message     
 
    
    
   

%HA-HA_WD-4-TOP_MEMORY_USERS_WARNING Top [dec] consumers of system memory ([dec] Kbytes free):

Explanation    This message is emitted when system memory usage crosses a threshold in the direction of increasing memory exhaustion. The top memory users will follow in the next messages. There may be a memory leak or misconfiguration.

Recommended Action    Collect the data from the following messages and attempt to determine what is driving memory usage. Forward the messages to technical support.

Error Message     
 
    
    
   

%HA-HA_WD-4-TOP_SHMEM_USER_WARNING [dec]: File/Directory Name: [chars], Kbytes used: [dec].

Explanation    This process is one of the top sharedmemory users in the system. If the system reaches critical memory exhaustion, this process is subject to restart or termination. If the process is listed as 'Killed', then the system is in the process of recovering the resources used by the process.

Recommended Action    Collect system log information. Contact technical support if the problem is not a misconfiguration.

Error Message     
 
    
    
   

%HA-HA_WD-4-TOP_SHMEM_USERS_WARNING Top [dec] consumers of shared memory ([dec] Kbytes free):

Explanation    This message is emitted when system memory usage crosses a threshold in the direction of increasing memory exhaustion. The top shared memory users will follow in the next messages. There may be a memory leak or misconfiguration.

Recommended Action    Collect the data from the following messages and attempt to determine what is driving memory usage. Forward the messages to technical support.

Error Message     
 
    
    
   

%HA-HA_WD-5-NO_TIMEOUT All registered event managers on this node are sending heartbeats.

Explanation    All event managers are now sending keep alive messages as expected.

Recommended Action    The debugging information collected when an event manager stopped sending heartbeats should be examined and provided to technical support for analysis.

Error Message     
 
    
    
   

%HA-HA_WD-5-TIMEOUT Event manager from process [chars][[dec]] created by thread [dec] at [chars] is not sending heartbeats.

Explanation    A timeout occurred waiting to hear from an event manager. This could happen as a result of a process being deadlocked on another event.

Recommended Action    Wdsysmon has detected that an event manager is no longer sending keepalive heartbeats. The message provides information about where the event manager was created. A debug script will run and collect information about the process and the state of the router. The output will be in a directory [/disk1:|/disk0:|/bootflash:|/tmp]/wdsysmon_debug/debug.*

Error Message     
 
    
    
   

%HA-HA_WD-5-TIMEOUT_CANCELLED Event manager from process [chars][[dec]] created by thread [dec] at [chars] is not sending heartbeats.

Explanation    An event manager has resumed sending heartbeats. This happens when a condition that caused the hang is cleared.

Recommended Action    The debugging information collected when the event manager stopped sending heartbeats should be examined and provided to technical support for analysis.

Error Message     
 
    
    
   

%HA-HA_WD-5-TIMEOUT_EXIT Process [chars] with event manager not sending heartbeats has exited.

Explanation    A process with an event manager that was not sending heartbeats has exited.

Recommended Action    The debugging information collected when the event manager stopped sending heartbeats should be examined and provided to technical support for analysis.

Error Message     
 
    
    
   

%HA-HA_WD-6-CPU_HOG_1 CPU hog: cpu [dec]'s sched count is [dec].

Explanation    Wdsysmon has detected a cpu starvation situation - potentially a high priority process spinning in a tight loop. The sched count is the number of times the wdsysmon ticker thread has been scheduled since the last time the wdsysmon watcher thread ran.

Recommended Action    Check the system status, including the saved log for evidence of a high priority cpu hog.

Error Message     
 
    
    
   

%HA-HA_WD-6-CPU_HOG_2 CPU hog: cpu [dec]'s ticker last ran [dec].[dec] seconds ago.

Explanation    Wdsysmon has detected a cpu starvation situation - potentially a high priority process spinning in a tight loop.

Recommended Action    Check the system status, including the saved log for evidence of a high priority cpu hog.

Error Message     
 
    
    
   

%HA-HA_WD-6-CPU_HOG_3 Rolling average of scheduling times: [dec].[dec].

Explanation    Wdsysmon has detected a cpu starvation situation - potentially a high priority process spinning in a tight loop. A high value for the rolling average indicates that a periodic process is not being scheduled.

Recommended Action    Check the system status, including the saved log for evidence of a high priority cpu hog.

Error Message     
 
    
    
   

%HA-HA_WD-6-CPU_HOG_4 Process [chars] pid [dec] tid [dec] prio [dec] using [dec]% is the top user of CPU.

Explanation    This message is displayed after the CPU hog detector trips. It shows the percentage of CPU used by the busiest thread in the top consumer of CPU.

Recommended Action    The command 'show watchdog trace' will display additional information about the potential CPU hog. If the hog is persistant, contact technical support. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-6-DISK_NORMAL Device [chars] usage [dec].

Explanation    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-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-GI_FILES_CREATED New dump files created in [chars]

Explanation    Information captured by various modules and stored in bootflash during a previous reset has been moved to hard disk.

Recommended Action    Examine the dump information for possible root-cause for a previous reset. Use the wd_test utility.

Error Message     
 
    
    
   

%HA-HA_WD-6-IN_DEP_LIST Process [chars] pid [dec] is present in Dependency List and will not be killed.

Explanation    This message is emitted if the misbehaving process is one that wdsysmon depends on. It will not be terminated.

Recommended Action    The command 'show watchdog trace' will display additional information about the process. Forward this information to technical support.

Error Message     
 
    
    
   

%HA-HA_WD-6-KNOWN_HOG Top CPU user process [chars] pid [dec] is a known hog.

Explanation    This message is emitted if the top CPU user is known to use substantial CPU under some circumstances.

Recommended Action    The command 'show watchdog trace' will display additional information about the potential CPU hog. If the hog is persistant, contact technical support. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-6-MEMORY_RECOVERY_DISABLED Node physical memory 256MB

Explanation    This node is not configured with sufficient memory to enable memory recovery support.

Recommended Action    Re-configure this node with more physical memory

Error Message     
 
    
    
   

%HA-HA_WD-6-MEMORY_RECOVERY_KILL_NON_SYSMGR Process [chars] (pid [dec]) not managed by sysmgr using [dec] kbytes of heap memory will be killed and not restarted.(Info:[dec] kbytes of virtual shared memory).

Explanation    The process with the indicated name and pid has been killed in an attempt to recover system memory. Since this process is not managed by sysmgr, it may not be restarted. The process can be manually restarted if desired, but may continue to consume large amounts of memory.

Recommended Action    The system is critically short of memory. Automatic recovery will attempt to stabilize the system, but there is either a memory leak or a misconfiguration. Both require operator intervention.

Error Message     
 
    
    
   

%HA-HA_WD-6-MEMORY_RECOVERY_KILL_SYSMGR Process [chars][[dec]] (pid [dec]) (managed by sysmgr) using [dec] kbytes of heap memory will be killed and not restarted.(Info:[dec] kbytes of virtual shared memory).

Explanation    The sysmgr process with the indicated name and pid has been killed in an attempt to recover system memory. The process can be manually restarted if desired, but may continue to consume large amounts of memory.

Recommended Action    The system is critically short of memory. Automatic recovery will attempt to stabilize the system, but there is either a memory leak or a misconfiguration. Both require operator intervention.

Error Message     
 
    
    
   

%HA-HA_WD-6-MEMORY_RECOVERY_RESTART Process [chars][[dec]] (pid [dec]) using [dec] kbytes of heap memory will be restarted. (Info:[dec] kbytes of virtual shared memory).

Explanation    The sysmgr process with the indicated name and pid has been restarted in an attempt to recover system memory.

Recommended Action    The system is critically short of memory. Automatic recovery will attempt to stabilize the system, but there is either a memory leak or a misconfiguration. Both require operator intervention.

Error Message     
 
    
    
   

%HA-HA_WD-6-PROC_KILL_DISABLED [chars]: Process-terminate disabled. Pid [dec] will not be terminated

Explanation    wdsysmon process-termination is disabled. A process which meets the kill criteria (either because it's in deadlock, or it's a memory or CPU hog - indicated by the first parameter [%d]) will not be terminated.

Recommended Action    Collect all logs, especially those from wdsysmon. Also collect output from 'show watchdog trace'. Forward the messages to technical support.

Error Message     
 
    
    
   

%HA-HA_WD-6-TOP_MEMORY_USER_INFO [dec]: Process Name: [chars][[dec]], pid: [dec][chars], Heap usage: [dec] kbytes, Virtual Shared memory usage: [dec] kbytes.

Explanation    This process is one of the top memory users in the system. If the system reaches critical memory exhaustion, this process is subject to restart or termination. If the process is listed as 'Killed', then the system is in the process of recovering the resources used by the process.

Recommended Action    Collect system log information. Contact technical support if the problem is not a misconfiguration.

Error Message     
 
    
    
   

%HA-HA_WD-6-TOP_MEMORY_USERS_INFO Top [dec] consumers of system memory ([dec] Kbytes free):

Explanation    This message is emitted when system memory usage crosses a threshold in the direction of increasing memory exhaustion. The top memory users will follow in the next messages. There may be a memory leak or misconfiguration.

Recommended Action    Collect the data from the following messages and attempt to determine what is driving memory usage. Forward the messages to technical support.

Error Message     
 
    
    
   

%HA-HA_WD-6-TOP_SHMEM_USER_INFO [dec]: File/Directory Name: [chars], Kbytes used: [dec].

Explanation    This process is one of the top sharedmemory users in the system. If the system reaches critical memory exhaustion, this process is subject to restart or termination. If the process is listed as 'Killed', then the system is in the process of recovering the resources used by the process.

Recommended Action    Collect system log information. Contact technical support if the problem is not a misconfiguration.

Error Message     
 
    
    
   

%HA-HA_WD-6-TOP_SHMEM_USERS_INFO Top [dec] consumers of shared memory ([dec] Kbytes free):

Explanation    This message is emitted when system memory usage crosses a threshold in the direction of increasing memory exhaustion. The top shared memory users will follow in the next messages. There may be a memory leak or misconfiguration.

Recommended Action    Collect the data from the following messages and attempt to determine what is driving memory usage. Forward the messages to technical support.

Error Message     
 
    
    
   

%HA-HA_WD-7-CISCOSHMEM [chars]: [chars]

Explanation    Mapping to shared memory provided by cisco_wrapper 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_WD-7-CLINFO_GET_DATUM [chars]: could not get an application datum associated with the channel: [chars]

Explanation    An internal error was detected when trying to retrieve an application datum associated with the given channel handler.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-CLINFO_M_PID [chars]: could not get process id from message information: [chars]

Explanation    An internal error was detected when trying to get process id from the information of a message.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-CLINFO_SAVE_DATUM [chars]: could not save an application datum associated with the channel: [chars]

Explanation    An internal error was detected when trying to save an application datum associated with the given channel handler.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-CLINFO_UNHOLD [chars]: could not decrement the hold count of the client info data: [chars]

Explanation    An internal error was detected when trying to decrement the hold count of the client info data of a synchronous message.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-CONTEXT_CREATE [chars]: Failed to create notification context: [chars]

Explanation    During registration for memory notification, an internal error prevented the creation of an internal context structure. The calling function and detected error are displayed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-GET_EVM_CTX_BY_TIMER [chars]: could not find the event manager context by timeout timer [pointer]

Explanation    An internal error was detected when trying to find the event manager context by the given timeout timer.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-MSG_CHAN_CONNECT [chars]: could not connect to the message channel [chars]: [chars]

Explanation    An internal error was detected when attaching a handler for an Event Manager asynchronous event.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-MSG_CHAN_DISCONN [chars]: could not disconnect a message channel: [chars]

Explanation    An internal error was detected when trying to disconnect a message channel.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-MSG_SEND [chars]: could not send the message: [chars]

Explanation    An internal error was detected when trying to send a message.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-MSG_SEND_EVENT [chars]: could not send the sigevent: [chars]

Explanation    An internal error was detected when trying to send a sigevent to the client that last sent a message on the connection.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-MSG_TYPE [chars]: unknown message type [dec]

Explanation    A message with an unknown type was received.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-NO_MEM [chars]: not enough memory: [chars]

Explanation    Allocating memory failed due to a low-memory condition.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%HA-HA_WD-7-SCHED_GET_PRIORITY_MAX [chars]: The sched_get_priority_max() function returned an error; [chars]

Explanation    The sched_get_priority_max() function returned an error which is indicated in the message.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-SCHED_SETSCHEDULER [chars]: The sched_setscheduler() function returned an error; [chars]

Explanation    The sched_setscheduler() function returned an error which is indicated in the message.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-SYSCALL [chars]: [chars](): [chars]

Explanation    A system call failed. The calling function, the failed call, and error are displayed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HA_WD-7-UNEXPECTED Unexpected: [chars]: [chars]: [hex]

Explanation    An unexpected condition encountered. This is not necessarily an error.

Recommended Action    Collect system log information. No action is required.

HM Messages

Error Message     
 
    
    
   

%HA-HM-3-FPING_ERROR [chars]

Explanation    HA Health Monitor Fabric ping failed

Recommended Action    Shelf Manager should receive a critical alarm from HA Health Monitor for this error. The node should be reset by Shelf Manager. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HM-3-FPING_MISMATCH [chars]

Explanation    HA Health Monitor Fabric ping failed. When a received ping response does not match the transmitted ping, this indicates some kind of cell corruption or cell loss in the fabric or edges of the fabric.

Recommended Action    If problem persist, it indicates the bad hw in the system. Please contact TAC for fault isolation. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HM-4-ERROR_INIT [chars], reason: [chars]

Explanation    HA Health Monitor failed to initialize due to internal software errors

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process hm location ' to verify that the process is up and running. If it is still non-operational, try doing 'process restart hm location ' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%HA-HM-4-FPING_INCOMPLETE HM fabric ping only completed [unsigned int] of [unsigned int] pings (ret 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    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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 allocate %zd 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    Collect the console log, perform the reovery action describes below.

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 registers the dll using cerr_register_dll 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-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    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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 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 against on LRD, but may help with debugging other problems elsewhere!

Recommended Action    Collect system log information.

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-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    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

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    Debug message only. No action is required.

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 allocate %zd 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_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_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-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-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-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.

REDCON Messages

Error Message     
 
    
    
   

%HA-REDCON-1-BACKUP_NOT_READY backup process groups between [chars] and [chars] are NOT ready

Explanation    RMF has determined that the backup process groups are NOT ready because of the failure of one or more events the prevent it from being in-sync with the primary process groups.

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-REDCON-1-BACKUP_READY backup process groups between [chars] and [chars] are ready

Explanation    RMF has determined that the backup process groups on the specified card are ready to take over as primary if it needs to.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%HA-REDCON-1-STANDBY_NOT_READY standby card is NOT ready

Explanation    Redcon has determined that the standby card is NOT ready because of the failure of one or more events the prevent it from being in-sync with the active card.

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-REDCON-1-STANDBY_NOT_READY standby card is NOT ready

Explanation    RMF has determined that the standby card is NOT ready because of the failure of one or more events the prevent it from being in-sync with the active card.

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-REDCON-1-STANDBY_READY standby card is ready

Explanation    Redcon has determined that the standby card is ready to take over as active card if it needs to.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%HA-REDCON-1-STANDBY_READY standby card is ready

Explanation    RMF has determined that the standby card is ready to take over as active card if it needs to.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%HA-REDCON-3-DRIVER_INIT_FAILED initilization of the redundancy driver failed after [dec] attempts

Explanation    RMF 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-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-PCDS_INIT_FAILED Redcon unable to register with PCDS infrastructure.

Explanation    An unexpected error condition encountered.

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-REDCON-3-PCDS_INIT_FAILED RMF unable to register with PCDS infrastructure.

Explanation    An unexpected error condition encountered.

Recommended Action    Collect system log information. 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-BACKUP_NOT_READY_ALARM [chars]

Explanation    Set: When the backup process groups remain in not ready state for a prolonged period. Cleared: When the card where the backup process groups are located is removed, reset or goes ready.

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-REDCON-4-BACKUP_NOT_READY_REASON JID [dec], node [chars], group [chars], process [chars] set the backup not ready: [chars]

Explanation    The named process has set the backup process group in a not ready state with the supplied reason.

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-REDCON-4-CONN_RETRY Connection to [chars] failed - retrying...

Explanation    RMF failed to establish a connection to RMF on the another card.

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-FAILOVER_REQUESTED failover has been requested by operator, waiting to initiate

Explanation    RMF 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-SRP_NR_CLIENT_UNREG client not registered to set SRP not ready : [chars]

Explanation    An unexpected error condition encountered.

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-REDCON-4-SRP_NR_REASON_UNREG client ([unsigned int],[chars]) is using unregistered reason string to set SRP not ready: [chars]

Explanation    An unexpected error condition encountered.

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_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_NOT_READY_REASON JID [dec], node [chars], process [chars] set the standby not ready: [chars]

Explanation    The named process has set the standby in a not ready state with the supplied reason.

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-REDCON-4-STBY_ACTIVE_NOT_READY Notice to go active: Card not ready and will be reset

Explanation    RMF 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_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    RMF 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-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-5-INIT_FAILED Failed to initialize [chars]: [hex]:[chars].

Explanation    RMF failed to initialize a module.

Recommended Action    Collect system log information No action is required.

Error Message     
 
    
    
   

%HA-REDCON-6-BACKUP_CONNECTION_DOWN connection to backup process group location [chars] is DOWN

Explanation    RMF has determined that the connection to the backup process groups location has gone down.

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-REDCON-6-BACKUP_CONNECTION_UP connection to backup process group location [chars] is UP

Explanation    RMF has determined that the connection to the backup process groups location has been succesfully completed.

Recommended Action    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_ACTIVE this card going active

Explanation    The card is going active.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%HA-REDCON-6-GO_BACKUP this card has process groups going backup

Explanation    The card has process groupss going to backup state.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%HA-REDCON-6-GO_PRIMARY this card has process groups going primary

Explanation    The card has process groups going to primary state.

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-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_DOWN connection to standby card is DOWN

Explanation    RMF 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    RMF has determined that the connection to the standby card has been succesfully completed.

Recommended Action    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_BACKUP_NOT_READY This card is standby and its backup process groups are NOT ready

Explanation    RMF has determined that the standby card has backup process groups which are NOT ready because of the failure of one or more events the prevent it from being in-sync primary process groups.

Recommended Action    Collect system log information. No action is required.

Error Message     
 
    
    
   

%HA-REDCON-6-STBY_BACKUP_READY This card is standby and its backup process groups are ready

Explanation    RMF has determined that the standby card is ready to take over as primary if it needs to.

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    RMF 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-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.

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.

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.

RMF_CLIENT Messages

Error Message     
 
    
    
   

%HA-RMF_CLIENT-3-ERROR [chars]: [chars]: [hex]: [chars]

Explanation    A rmf 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-RMF_CLIENT-7-MSG_SEND [chars]: Failed to send [chars] message to rmf: [hex]: [chars]

Explanation    An attempt to send a message to the rmf server failed with the specified reason. It may be the case that rmf 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.

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.