GEN_PROXY through HFSLIB
GEN_PROXY
| %GEN_PROXY-3-IPC_UNHANDLED : failure | |
|---|---|
| Explanation | An unknown message type: %d was received by the Generic Client Proxy. |
| Recommended Action | LOG_STD_ACTION |
| %GEN_PROXY-3-REPLY_MSG : wrong version [dec] | |
|---|---|
| Explanation | An incorrect SBS message was received by the Generic Client Proxy. |
| Recommended Action | LOG_STD_ACTION |
| %GEN_PROXY-3-STACK_ALLOC_FAILED : Stack allocation for reply failed reply_size [hex] | |
|---|---|
| Explanation | Stack space could not be allocated for reply. |
| Recommended Action | LOG_STD_ACTION |
| %GEN_PROXY-3-GPM_ALLOC_FAILED : GPM allocation for reply failed pak_size [hex] reply_size [hex] | |
|---|---|
| Explanation | GPM could not be allocated for reply. |
| Recommended Action | LOG_STD_ACTION |
| %GEN_PROXY-3-IPC_SEND_FAILED : IPC send reply failed [chars] | |
|---|---|
| Explanation | GEN proxy failed to send of reply to IPC msg. |
| Recommended Action | LOG_STD_ACTION |
GLBP
| %GLBP-4-BADAUTH : Bad authentication received from [chars], group [dec] | |
|---|---|
| Explanation | Two routers participating in a Gateway Load Balancing Protocol group disagree on the valid authentication string. |
| Recommended Action | Use the glbp authentication interface command to repair the GLBP authentication discrepancy between the local system and the one whose IP address is reported. |
| %GLBP-3-MISCONFIG : Cannot add MAC address [enet] to interface [chars] - not supported | |
|---|---|
| Explanation | A software or hardware error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %GLBP-6-STATECHANGE : [chars] Grp [int] state [chars] -> [chars] | |
|---|---|
| Explanation | The GLBP gateway has changed state |
| Recommended Action | No action is required. |
| %GLBP-6-FWDSTATECHANGE : [chars] Grp [int] Fwd [int] state [chars] -> [chars] | |
|---|---|
| Explanation | The GLBP forwarder has changed state |
| Recommended Action | No action is required. |
| %GLBP-4-DUPADDR : Duplicate address [chars] on [chars], sourced by [enet] | |
|---|---|
| Explanation | The IP address in a GLBP message received on the interface is the same as the router's own IP address. This may be because of misconfiugration, or because of a malfunctioning switch |
| Recommended Action | Check the configurations on all the GLBP routers, and make sure that any switches you have are functioning properly. |
| %GLBP-4-DUPVIP1 : [chars] Grp [dec] address [chars] is already assigned to [chars] group [dec] | |
|---|---|
| Explanation | The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to a different GLBP group. |
| Recommended Action | Check the configuration on all GLBP routers. |
| %GLBP-4-DUPVIP2 : [chars] Grp [dec] address [chars] is already assigned on this interface | |
|---|---|
| Explanation | The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to this interface. |
| Recommended Action | Check the configuration on all GLBP routers. |
| %GLBP-4-DUPVIP3 : [chars] Grp [dec] address [chars] is already assigned to, or overlaps with, an address on another interface or application | |
|---|---|
| Explanation | The GLBP virtual IP address contained in the Hello message cannot be learnt as it is already assigned to, or overlaps with, an address on another interface or application. |
| Recommended Action | Check the configuration on all GLBP routers. |
| %GLBP-4-BADVIP : [chars] Grp [dec] address [chars] is in the wrong subnet for this interface | |
|---|---|
| Explanation | The GLBP virtual IP address contained in the Hello message cannot be learnt as it is not within a subnet configured on the interface. |
| Recommended Action | Check the configuration on all GLBP routers and ensure that the virtual IP address is within a configured subnet. |
| %GLBP-4-DIFFVIP1 : [chars] Grp [dec] active routers virtual IP address [chars] is different to the locally configured address [chars] | |
|---|---|
| Explanation | The GLBP virtual IP address contained in the Hello message from the Active router is different to that configured locally. |
| Recommended Action | Check the configuration on all GLBP routers. |
GRIP
| %GRIP-3-BADPATHS : Invalid number of paths ([dec]) for %q | |
|---|---|
| Explanation | An internal inconsistency was detected in the XNS routing table structure. |
| Recommended Action | Note the parameters associated with this message and call your technical support representative for assistance. |
| %GRIP-2-BADROUTE : Error [chars] route - null table | |
|---|---|
| Explanation | A hardware or software error occurred. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
HA
| %HA-6-TOOBIG : Running config too big, config sync failed | |
|---|---|
| Explanation | The running config was too big to be synced |
| Recommended Action | No action is required. |
| %HA-6-SWITCHOVER : Route Processor switched from standby to being active | |
|---|---|
| Explanation | This RP switched to become the active RP |
| Recommended Action | No action is required. |
HAL_GENMEM
| %HAL_GENMEM-3-HAL_MISMATCHED_GENMEM : VADDR:[int] LINE: [dec] | |
|---|---|
| Explanation | Mismatched genmem. |
| Recommended Action | LOG_STD_ACTION |
HAL_PACKET
| %HAL_PACKET-3-HAL_GATHER_ASYNC_WAIT_TIMEOUT : seqnum=[int] pak-type=[int] | |
|---|---|
| Explanation | Packet Hardware Transmit Error |
| Recommended Action | LOG_STD_ACTION |
HA_EM
| %HA_EM-7-FMCMN_PTHREAD_MUTEX_LOCK : [chars]: Error locking mutex [chars]; [chars] | |
|---|---|
| Explanation | The pthread_mutex_lock function reported an error while attempting to lock the specified mutex. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMCMN_PTHREAD_MUTEX_UNLOCK : [chars]: Error unlocking mutex [chars]; [chars] | |
|---|---|
| Explanation | The pthread_mutex_unlock function reported an error while attempting to unlock the specified mutex. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFDCMN_DM_CREATE : [chars]: could not create dispatch manager: [chars] | |
|---|---|
| Explanation | The event detector has failed to create an dispatch manager. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFDCMN_EA_ATTACH : [chars]: 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 message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFDCMN_INV_TM : [chars]: invalid timer: type=[dec], timer=[IPV6 address] | |
|---|---|
| Explanation | Internal error. The timer value is invalid or not as expected. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFDCMN_INV_TM_TYPE : [chars]: invalid timer type: [dec] | |
|---|---|
| Explanation | Internal error. The timer type is invalid or not supported. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFDCMN_MSGSEND_EVT : [chars]: error returned from event_send_pulse; [chars] | |
|---|---|
| Explanation | The event detector has failed to send a pulse to itself to notify of a pending message send event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFDCMN_PUB_RBLD : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to rebuild the publish list from the checkpointed records. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFDCMN_XDM_DISPATCH_FAIL : [chars]: XOS Dispatch Manager dispatch error: [dec] | |
|---|---|
| Explanation | XOS Dispatch Manager reports an error when dispatching an event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFDCMN_XDM_WAIT_FAIL : [chars]: XOS Dispatch Manager wait error: [dec] | |
|---|---|
| Explanation | XOS Dispatch Manager reports an error when waiting for an event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_ADD_PARSER : [chars]: Unable to add [chars] event detector command; | |
|---|---|
| Explanation | The Event detector failed to add command. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_CHKPT_INIT : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to initialize with the checkpointing server. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_CHKPT_TBL_ADD : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to add a record to the checkpointing table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_CHKPT_TBL_INIT : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to initialize a table with the checkpointing server. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_CHKPT_TBL_ITERATE : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to iterate the checkpointing table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_CHKPT_TBL_REMOVE : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to remove a record from the checkpointing table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_COND_WAIT : [chars]: conditional wait error: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to do pthread conditional wait. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_CONNECTION_FAIL : Could not connect to [chars] : [chars] | |
|---|---|
| Explanation | Could not connect to event detector on the remote node. Node may be invalid or not available or the process may not be available to accept the connection. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_DE_FETCH : [chars]: [chars][[dec]] | |
|---|---|
| Explanation | Internal error. The event detector has failed to fetch a data elementfrom the statistics data engine. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_DE_INIT : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to initialize the statistics data engine. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_DM_CREATE : [chars]: could not create dispatch manager: [chars] | |
|---|---|
| Explanation | The event detector has failed to create an dispatch manager. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_EA_ATTACH : [chars]: 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 message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMFD_EMPTY_QUEUE : [chars]: The [chars] event detector I/O queue empty. | |
|---|---|
| Explanation | The I/O queue is empty at this point, and should not be. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_ENQUEUE_FAIL : [chars]: Unable to enqueue [chars]; | |
|---|---|
| Explanation | The enqueue function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_EV_BLOCK : [chars]: [chars] | |
|---|---|
| Explanation | The event_block function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_EVM_CREATE : Could not create event manager: [chars] | |
|---|---|
| Explanation | The event detector has failed to create an Event Manager. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_HIST_QERR : [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to get a free history listentry. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_HIST_RBLD : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to rebuild the history list from the checkpointed records. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_INV_COMPARE_OP : [chars]: invalid comparison operator: [dec] | |
|---|---|
| Explanation | Internal error. The value comparison operator is invalid or notsupported. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_INV_STATS_TYPE : [chars]: invalid statistics value type: [dec] | |
|---|---|
| Explanation | Internal error. The statistics data type is invalid or not supported. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_INV_TM : [chars]: invalid timer: type=[dec], timer=[IPV6 address] | |
|---|---|
| Explanation | Internal error. The timer value is invalid or not as expected. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_INV_TM_TYPE : [chars]: invalid timer type: [dec] | |
|---|---|
| Explanation | Internal error. The timer type is invalid or not supported. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_LOCAL_NODEID : Could not get local nodeid: [chars] | |
|---|---|
| Explanation | Could not get local node identifier. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_MALLOC : [chars]: Unable to allocate [chars]; [chars] | |
|---|---|
| Explanation | The malloc function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_MET_ENQUEUE : [chars]: could not enqueue metric data: [chars] | |
|---|---|
| Explanation | Internal error. The system manager event detector has failed to add a metric data entry to the list. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_MET_RBLD : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to rebuild the metriclist from the checkpointed records. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_MISC_ERR : [chars]: [chars] | |
|---|---|
| Explanation | An unexpected error occurred. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_MSGSEND_EVT : [chars]: error returned from event_send_pulse; [chars] | |
|---|---|
| Explanation | The event detector has failed to send a pulse to itself to notify of a pending message send event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_MSGSEND_RETRY_ERR : [chars]: [dec] | |
|---|---|
| Explanation | The event detector has exceeded its maximum number of retries to send apulse to the embedded event manager to notify of an event publish. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_NO_CLOCK : [chars]: unable to read clock using clock_gettime: [chars] | |
|---|---|
| Explanation | The clock_gettime function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_NO_MEM : [chars]: not enough memory: [chars] | |
|---|---|
| Explanation | Allocating memory failed due to a low-memory condition. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_OE_CREATE : [chars]: could not create an occurrence entry | |
|---|---|
| Explanation | Internal error. The event detector has failed to create an entry for thematched occurrence list. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_OE_REMOVE : [chars]: could not remove an occurrence entry | |
|---|---|
| Explanation | Internal error. The event detector has failed to remove an entry for thematched occurrence list. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMFD_OID_UNAVAIL : [chars]: The following oid has become unavailable: [chars] | |
|---|---|
| Explanation | The registered oid is no longer available in the system. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_OPEN_CONF : [chars]: could not open event detector config file: [chars] | |
|---|---|
| Explanation | The event detector has failed to open the config file for event detector type information. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_PTHRD_CREATE : [chars]: could not create a Posix thread | |
|---|---|
| Explanation | The pthread_create function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_PUB_RBLD : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed to rebuild the publish list from the checkpointed records. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_PUB_TM_ALLOC : [chars]: Unable to allocate memory for event publish timer block | |
|---|---|
| Explanation | Internal error. The event detector has failed to allocate memoryfor the event publish timer block. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMFD_QUEUE_INIT : [chars]: Unable to initialize queue; | |
|---|---|
| Explanation | The queue initialization function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_RESOURCE_MONITOR_REGISTER_FAIL : [chars]: resource_monitor_register failed; return code = [dec] | |
|---|---|
| Explanation | The resource_monitor_register function reported an error trying toregister for RMI notifications. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_RM_ATTACH : [chars]: could not attach resource manager funtions to event manager: [chars] | |
|---|---|
| Explanation | The event detector has failed to attach a Resource Manager to an Event Manager. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SM_PROC_EXIT : [chars]: [chars] | |
|---|---|
| Explanation | The system manager failed to execute the default action of the terminated process. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_ADDR_ILLEGAL : [chars]: Illegal SNMP address type | |
|---|---|
| Explanation | The SNMP address is illegal. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_ADDR_IPV6 : [chars]: SNMP IPV6 address is not supported | |
|---|---|
| Explanation | The IPV6 address is not supported. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_BUILD_PDU_FAILED : [chars]: SNMP build pdu failed | |
|---|---|
| Explanation | The SNMP pdu build has failed. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_COMM_FAIL : [chars]: Unable to create SNMP octet community string; string = [chars] | |
|---|---|
| Explanation | The community string was not able to build into a SNMP octet string |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_COMMUNICATE_FAIL : [chars]: [chars] [chars] | |
|---|---|
| Explanation | Unable to communicate with SNMPD process |
| Recommended Action | Check whether SNMP is configured on this Router. |
| %HA_EM-7-FMFD_SNMP_ERRCODE : [chars]: [chars] | |
|---|---|
| Explanation | The SNMP error code. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_MAKE_PDU_FAILED : [chars]: SNMP make pdu failed | |
|---|---|
| Explanation | The SNMP pdu make has failed. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMFD_SNMP_MIB_OBJ_REP_FAIL : [chars]: SNMP MIB object info replace failed [dec] | |
|---|---|
| Explanation | The SNMP MIB object info replace function has failed. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_MSG_FAIL : [chars]: Unable to create a SNMP message; community = [chars] | |
|---|---|
| Explanation | The SNMP message failed to be created |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMFD_SNMP_NO_OBJECT_VALUE : [chars]: SNMP MIB object value not provided | |
|---|---|
| Explanation | The SNMP MIB object value is not provided for substitution. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMFD_SNMP_OBJECT_UNKNOWN_RESPONSE_CODE : [chars]: Unknown SNMP object response code [dec] | |
|---|---|
| Explanation | The SNMP MIB object response code is unknown. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_OID_INVALID : [chars]: Invalid SNMP oid length [dec] | |
|---|---|
| Explanation | The SNMP oid has invalid length |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_OID_MAKE_FAIL : [chars]: Unable to build an oid string into a SNMP oid; oid = [chars] | |
|---|---|
| Explanation | The oid string was not able to build into a SNMP oid |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_REQ_FAILED : [chars]: SNMP request failed | |
|---|---|
| Explanation | The SNMP request has failed. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_RESP_CANCEL : [chars]: SNMP response cancelled | |
|---|---|
| Explanation | The SNMP response has been cancelled. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_RESP_ERROR : [chars]: SNMP response error; error_status = [dec] | |
|---|---|
| Explanation | The SNMP response has error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_RESP_Q_EMPTY : [chars]: SNMP proxy exec got event, but queue is empty | |
|---|---|
| Explanation | The SNMP proxy got event but the queue is empty. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_RESP_TIMEOUT : [chars]: SNMP response has timed out | |
|---|---|
| Explanation | The SNMP response has timed out. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_UNKNOWN_TYPE : [chars]: Unknown SNMP operation or response type [dec] | |
|---|---|
| Explanation | The operation or response type is unknown. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SNMP_VARBIND_FAIL : [chars]: Unable to create a SNMP varbind | |
|---|---|
| Explanation | The oid failed to make into a SNMP varbind |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_STATS_VAL_GET_ERR : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The event detector has failed retrieving a valid statistics value. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SYSDB_BIND : [chars]: [chars] | |
|---|---|
| Explanation | Failed to bind to SysDB. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SYSDB_GET : [chars]: [chars] | |
|---|---|
| Explanation | Failed to retrieve an item from SysDB. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_SYSDB_REG_NOTIFY : [chars]: [chars] | |
|---|---|
| Explanation | Failed to register for notification of a set of items in SysDB. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_TM_CRTICK_INIT : [chars]: [chars] | |
|---|---|
| Explanation | Internal error. The initialization of the cron-tick function has failed. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_TM_LEAF_NEW : [chars]: could not create a leaf timer | |
|---|---|
| Explanation | Internal error. The event detector has failed to create a managedleaf timer. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMFD_TTY_NUM : [chars]: Error occurred while fetching TTY number. | |
|---|---|
| Explanation | The Embedded Event Manager failed to fetch a TTY number. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_XDM_DISPATCH_FAIL : [chars]: XOS Dispatch Manager dispatch error: [dec] | |
|---|---|
| Explanation | XOS Dispatch Manager reports an error when dispatching an event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMFD_XDM_WAIT_FAIL : [chars]: XOS Dispatch Manager wait error: [dec] | |
|---|---|
| Explanation | XOS Dispatch Manager reports an error when waiting for an event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMC_APPL_CBH_PULSE : [chars]: Unable to locate application publish callback entry for pulse code [dec] | |
|---|---|
| Explanation | The application publish callback handler was unable to validate the pulse code received. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMC_APPL_CBH_SEND : [chars]: Unable to send response for FH_MSG_CALLBACK_DONE [chars] | |
|---|---|
| Explanation | The registration callback handler was unable to send the FH_MSG_CALLBACK_DONE message to the Embedded Event Manager Server. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMC_CB_CLOSE : [chars]: fh_close failed [chars] | |
|---|---|
| Explanation | The fh_close function reported an error trying to initialize the internal callback connection. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMC_CB_EV_CREATE : [chars]: event_manager_create failed [chars] | |
|---|---|
| Explanation | The event_manager_create function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMC_CBH_PROCESS_CREATE : [chars]: callback handler process create failed for eid: [dec] | |
|---|---|
| Explanation | The process_create function reported an error trying to create thecallback handler process. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMC_CB_INIT : [chars]:[dec] (thread:[dec]) fh_init failed [chars] | |
|---|---|
| Explanation | The fh_init function reported an error trying to initialize the internal callback connection. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMC_CBS_PT_CREATE : [chars]: pthread_create failed [chars] | |
|---|---|
| Explanation | The pthread_create function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMC_ENQUEUE_FAIL : [chars]: Unable to enqueue [chars]; | |
|---|---|
| Explanation | The enqueue function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMC_FH_INIT : [chars]: fh_init failed : [dec] | |
|---|---|
| Explanation | The fh_init function reported an error trying to initialize EEM fora callback process. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMC_INV_REPLY : [chars]: Application client library unable to handle message receive. | |
|---|---|
| Explanation | The API received a msg reply when it was not in a state to acceptsuch messages. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMC_MALLOC : [chars]: Unable to allocate [chars]; | |
|---|---|
| Explanation | The malloc function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMC_REG_CBH_PULSE : [chars]: Unable to locate reg callback entry for pulse code [dec] | |
|---|---|
| Explanation | The registration callback handler was unable to validate the pulse codereceived. |
| Recommended Action | The pthread_create function reported an error. |
| %HA_EM-7-FMC_REG_CBH_SEND : [chars]: Unable to send response for FH_MSG_CALLBACK_DONE [chars] [dec] | |
|---|---|
| Explanation | The registration callback handler was unable to send theFH_MSG_CALLBACK_DONE message to the Embedded Event Manager Server. |
| Recommended Action | The pthread_create function reported an error. |
| %HA_EM-7-FMC_XDM_DISPATCH_FAIL : [chars]: XOS Dispatch Manager dispatch error: [dec] | |
|---|---|
| Explanation | XOS Dispatch Manager reports an error when dispatching an event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMC_XDM_WAIT_FAIL : [chars]: XOS Dispatch Manager wait error: [dec] | |
|---|---|
| Explanation | XOS Dispatch Manager reports an error when waiting for an event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_ACTION : [chars]: Error occurred while performing action: [chars]. | |
|---|---|
| Explanation | The Embedded Event Manager Policy Director failed to perform anaction for the registered event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_ACTION_INFO : [chars]: Error occurred while fetching action information: [dec]. | |
|---|---|
| Explanation | The Embedded Event Manager Policy Director failed to gather actioninformation registered for the event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_ACTION_NOTRACK : [chars]: unable to set state for tracking object number [int]; object does not exist or is not a stub-object. | |
|---|---|
| Explanation | The Embedded Event Manager applet attempted to set the state ofa tracking object that does not exist. |
| Recommended Action | Only set the state of tracking objects that have already been configured in the system. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_CHECKSUM_MISMATCH : [chars]: file checksum mismatch | |
|---|---|
| Explanation | The checksum value of an installed policy does not match the valueprovided by the installation manager. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_CHKPT_INIT : [chars]: could not register the application with the checkpointing server: [chars] | |
|---|---|
| Explanation | Failed to register an application with the checkpointing server. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_CHKPT_ITERATE_END : [chars]: call to chkpt_iterate_end returned unexpected failure. | |
|---|---|
| Explanation | Failed to register an application with the checkpointing server. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_CHKPT_NULL_PTR : [chars]: Got a null [chars] but non-null value was expected | |
|---|---|
| Explanation | Failed to do further processing because we got a null data when a non-null value was expected. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_CHKPT_TBL_ADD : [chars]: could not save a record into a checkpointing table: [chars] | |
|---|---|
| Explanation | Failed to save a record into the given checkpointing table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_CHKPT_TBL_INFO_READ : [chars]: could not read the existing table information: [chars] | |
|---|---|
| Explanation | Failed to read the existing table information using checkpointing API. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_CHKPT_TBL_INIT : [chars]: failed to initialize [chars]: [chars] | |
|---|---|
| Explanation | Could not initialize a table with the checkpointing server. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_CHKPT_TBL_RECOVER : [chars]: could not recover the checkpointed [chars]: [chars] | |
|---|---|
| Explanation | Failed to recover a checkpointed table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_CHKPT_TBL_REMOVE : [chars]: could not delete a record from a checkpointing table: [chars] | |
|---|---|
| Explanation | Failed to delete a record from the given checkpointing table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_CHKPT_TBL_RESET : [chars]: could not reset a record in a checkpointing table: [chars] | |
|---|---|
| Explanation | Failed to reset a record in the given checkpointing table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_CLI_CONNECT : Unable to establish CLI session: [chars] | |
|---|---|
| Explanation | Unable to establish CLI session. |
| Recommended Action | |
| %HA_EM-3-FMPD_CLI_DISCONNECT : Error disconnecting from CLI session: [chars] | |
|---|---|
| Explanation | An error occurred while disconnecting from the CLI session. |
| Recommended Action | |
| %HA_EM-3-FMPD_CLI_NOTTY : Error attempting to access an unopened CLI session: [chars] | |
|---|---|
| Explanation | An error occurred attempting to access an unopened CLI session: %s |
| Recommended Action | |
| %HA_EM-3-FMPD_CLI_READ : Unable to read CLI response: [chars] | |
|---|---|
| Explanation | Unable to read CLI response. |
| Recommended Action | |
| %HA_EM-3-FMPD_CLI_WRITE : Unable to send CLI command: [chars] | |
|---|---|
| Explanation | Unable to send CLI command. |
| Recommended Action | |
| %HA_EM-6-FMPD_CONTEXT_RETRIEVE : Failed to retrieve context for key [chars]: [chars] | |
|---|---|
| Explanation | Failed to context retrieve variable information for event. |
| Recommended Action | Ensure context information with the given key is saved. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-6-FMPD_CONTEXT_SAVE : Failed to save variable context for key [chars]: [chars] | |
|---|---|
| Explanation | Failed to context save variable information for event. |
| Recommended Action | Ensure context information with the same key is not already saved. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMPD_DIRECTORY_NOT_EXIST : User policy directory [chars] could not be found on [chars] | |
|---|---|
| Explanation | A policy directory could not be found. Cold start on this location may result in startup configuration failure. |
| Recommended Action | Create the directory on this location. |
| %HA_EM-6-FMPD_DIVIDE_ZERO : Invalid operand in arithmetic division, cannot divide by zero | |
|---|---|
| Explanation | Arithmetic division does not allow divide by zero. |
| Recommended Action | Ensure denominator provided to division action is non-zero. |
| %HA_EM-4-FMPD_DSIG_TYPE_CHANGE : Cisco Signature not found or invalid. [chars] has been registered as a user policy. | |
|---|---|
| Explanation | Cisco Signature not found or invalid. |
| Recommended Action | Sign with Cisco signature. |
| %HA_EM-6-FMPD_EEM_CONFIG : [chars]: [chars] | |
|---|---|
| Explanation | The Embedded Event Manager reports an error on Event Managerconfiguration |
| Recommended Action | Check the EEM applet or policy configuration |
| %HA_EM-6-FMPD_EEM_LOG_MSG : [chars] | |
|---|---|
| Explanation | The Embedded Event Manager reports errors when registering a TCL policy. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_ERROR : Error executing applet [chars] statement [chars] | |
|---|---|
| Explanation | The Embedded Event Manager policy director found an error whenprocessing an applet. |
| Recommended Action | Check syntax of applet statement. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMPD_EVENT_CREATE : [chars]: failed to create an event: [chars] | |
|---|---|
| Explanation | Failed to create an Embedded Event Manager event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMPD_EVENT_REG : [chars]: failed to register an event: [chars] | |
|---|---|
| Explanation | Failed to register an Embedded Event Manager event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_EVENT_TYPE : [chars]: unknown event type [dec] | |
|---|---|
| Explanation | An unknown Embedded Event Manager even type was detected. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_EVM_CREATE : [chars]: could not create event manager: [chars] | |
|---|---|
| Explanation | An internal error was detected when creating Event Manager. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_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 message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_EXECUTE_CALLBACK : [chars]: failed to execute callback | |
|---|---|
| Explanation | Failed to execute callback routine. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_FH_INIT : [chars]: could not initialize Embedded Event Manager service: [chars] | |
|---|---|
| Explanation | An internal error was detected when initializing Embedded Event Managerservice. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_FILE_CLOSE : [chars]: failed to close fd [chars] : [chars] | |
|---|---|
| Explanation | Failed to close the given file descriptor due to some internal error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_FILE_DELETE : [chars]: failed to delete file: [chars] : [chars] | |
|---|---|
| Explanation | Failed to delete the given file. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_FILE_OPEN : [chars]: failed to open file [chars] : [chars] | |
|---|---|
| Explanation | Failed to open the given file due to some internal error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_FILE_READ : [chars]: failed to read from fd [chars] : [chars] | |
|---|---|
| Explanation | Failed to read from the given file descriptor due to some internal error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_FILE_WRITE : [chars]: failed to write to fd [chars] : [chars] | |
|---|---|
| Explanation | Failed to write to the given file descriptor due to some internal error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_FORMAT_TIME : [chars]: error attemting to format time string | |
|---|---|
| Explanation | Format time failure. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_GET_PRIO : [chars]: failed to get process priority: [chars] | |
|---|---|
| Explanation | Internal error. A call to get process scheduling priority failed. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMPD_IPC_GET_PAK : [chars]: failed to allocate an IPC buffer | |
|---|---|
| Explanation | Embedded Event Manager failed to allocate a buffer from IPC. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_IPC_PORT_CREATE : [chars]: failed to create an IPC port: [chars] | |
|---|---|
| Explanation | Embedded Event Manager failed to create an IPC port. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_IPC_PORT_OPEN : [chars]: failed to open an IPC port: [chars] | |
|---|---|
| Explanation | Embedded Event Manager failed to open an IPC port. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_IPC_PORT_REGISTER : [chars]: failed to register an IPC port: [chars] | |
|---|---|
| Explanation | Embedded Event Manager failed to register an IPC port. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMPD_IPC_SEND_MSG : [chars]: failed to send an IPC message: [chars] | |
|---|---|
| Explanation | Embedded Event Manager failed to send a message through IPC. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_LAST_POLICY : [chars]: invalid last policy name replied [chars] | |
|---|---|
| Explanation | Internal error. The last policy name the script director repliedto show fm policy registered command is an invalid policy name. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_MEM_ALLOC : Not enough memory ([dec] bytes) | |
|---|---|
| Explanation | Allocating memory failed due to a low-memory condition. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMPD_NO_ACTION : No action configured for applet [chars] | |
|---|---|
| Explanation | No action has been configured for this applet. |
| Recommended Action | Configure at least one action for this applet. |
| %HA_EM-7-FMPD_NO_CLOCK : [chars]: unable to read clock using clock_gettime: [chars] | |
|---|---|
| Explanation | The clock_gettime function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_NOEID : [chars]: No such event id found. | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_NOESID : [chars]: No such event spec id found. | |
|---|---|
| Explanation | The Embedded Event Manager Policy Director could not find the eventfor the event spec. ID. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMPD_NO_EVENT : No event configured for applet [chars] | |
|---|---|
| Explanation | No event has been configured for this applet. |
| Recommended Action | Configure an event for this applet. |
| %HA_EM-7-FMPD_NO_MEM : [chars]: not enough memory: [chars] | |
|---|---|
| Explanation | Allocating memory failed due to a low-memory condition. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_NO_PROC : [chars]: Failed to create process | |
|---|---|
| Explanation | The process create function reports an error |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMPD_NOTAGNAME : [chars]: No tag [chars] found corresponding to this event publish. | |
|---|---|
| Explanation | The Embedded Event Manager policy director could not associate the tagname with a published event. |
| Recommended Action | Only use tagnames in the action info type event reqinfo command which correspond to the published event. |
| %HA_EM-6-FMPD_OPERAND_INVALID : Invalid operand in action, expected value within range %ld to %ld, received: [chars] | |
|---|---|
| Explanation | Arithmetic actions only accept valid long integer values. |
| Recommended Action | Ensure value provided to action is long integer. |
| %HA_EM-3-FMPD_OVL_NOTIF_REG : [chars]: could not register for Version Manager notification: [chars] | |
|---|---|
| Explanation | An internal error was detected when registering for Version Manager notification. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_OVL_SETUP_ENV : [chars]: [chars] | |
|---|---|
| Explanation | Updating environment variables of the process according to system variables stored in sysdb failed. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMPD_POLICY_APPLY : Could not apply policy '[chars]': [chars] | |
|---|---|
| Explanation | A policy could not be applied. This message signaled an unsuccessful apply of the policy. |
| Recommended Action | Remove the configuration for the policy (and commit), and then attempt to configure the registration of the same policy. |
| %HA_EM-6-FMPD_POLICY_CHANGED : [chars]: registered policy [chars] changed by the last installation update | |
|---|---|
| Explanation | A registered policy was changed by the last installation update. If the update used the start option, the old policy was automatically unregistered and the new policy registered. Otherwise, the old policy would remain registered and functional until the user unregisters it manually. |
| Recommended Action | None. |
| %HA_EM-4-FMPD_POLICY_CONFIG_INCONSISTENT : Policy '[chars]': [chars] | |
|---|---|
| Explanation | Some policy configuration is potentially inconsistent, and the user should follow the guidelines in the message to amend this. |
| Recommended Action | Examine the guidelines in the message, and the event manager configuration,to determine the potential problem. Note that this is just a warning message, not an error message, as the configuration is legal - it may be the case that the user has intentionally set this configuration. |
| %HA_EM-6-FMPD_POLICY_DELETED : [chars]: registered policy [chars] deleted by the last installation update | |
|---|---|
| Explanation | A registered policy was deleted by the last installation update. If the update used the start option, the policy was automatically unregistered. Otherwise, the policy would remain registered and functional until the user unregisters it manually. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_POLICY_HASH : [chars]: The hash computation routine reported an error; [chars] | |
|---|---|
| Explanation | The policy dir checksum function reported the specified error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMPD_POLICY_NOT_EXIST : Policy file [chars] could not be found on [chars] | |
|---|---|
| Explanation | A policy file could not be found. Cold start on this location may result in startup |
| Recommended Action | Copy the policy file to this location. |
| %HA_EM-6-FMPD_POLICY_REG_SUCC : [chars]: Policy '[chars]' registered successfully, by user [chars], with persist time [dec] and type [dec] | |
|---|---|
| Explanation | A new policy has been registered with Embedded Event Manager. This message signaled a successful registration. |
| Recommended Action | None. |
| %HA_EM-7-FMPD_POLICY_TBL_REMOVE : [chars]: could not delete a record from a checkpointing table: [chars] | |
|---|---|
| Explanation | Failed to delete a record from the given checkpointing table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMPD_POLICY_TUPLE_UNPACK : Failed to unpack_tuple to get username (Err: [dec]) for [chars] | |
|---|---|
| Explanation | Failed to unpack sysdb tuple to get the username for the scripts. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_POLICY_UNREG_ERR : [chars]: could not unregister policy [chars]: [chars] | |
|---|---|
| Explanation | A registered policy changed or deleted by the last installation update was detected. Since the update used the start option, the old policy was automatically unregistered. This message signaled an unsuccessful unregistration. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_POLICY_UNREGREG_ERR : [chars]: could not replace policy [chars]: [chars] | |
|---|---|
| Explanation | A registered policy changed by the last installation update was detected. Since the update used the start option, the old policy was automatically replaced by the new policy. This message signaled an unsuccessful replacement of the policy. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-6-FMPD_POLICY_UNREGREG_SUCC : [chars]: policy [chars] replaced successfully | |
|---|---|
| Explanation | A registered policy changed by the last installation update was detected. Since the update used the start option, the old policy was automatically replaced by the new policy. This message signaled a successful replacement of the policy. |
| Recommended Action | None. |
| %HA_EM-6-FMPD_POLICY_UNREG_SUCC : [chars]: policy [chars] unregistered successfully | |
|---|---|
| Explanation | A registered policy changed or deleted by the last installation update was detected. Since the update used the start option, the old policy was automatically unregistered. This message signaled a successful unregistration. |
| Recommended Action | None. |
| %HA_EM-3-FMPD_PROCESS_XML : [chars]: error processing xml buffer | |
|---|---|
| Explanation | An error occurred processing the event publish information xml buffer. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_QUEUE_INIT : [chars]: could not initialize queue | |
|---|---|
| Explanation | An internal error was detected when initializing Embedded Event Managerqueue. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_REFRESHTIMER_INIT : Failed to initialize a refresh timer ([chars]): [chars] | |
|---|---|
| Explanation | Failed to initialize a Embedded Event Manager refresh timer. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-6-FMPD_REGCOMP : Error compiling regular expression: [chars] | |
|---|---|
| Explanation | An error was encountered when compiling the given regular expression. |
| Recommended Action | Check syntax of regular expression pattern. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_REQINFO : [chars]: Error attempting to fetch event information: [chars]. | |
|---|---|
| Explanation | The Embedded Event Manager Policy Director failed to receive event infofor a callback. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_SET_INFO : [chars]: Error occurred while fetching variable information: [dec]. | |
|---|---|
| Explanation | The Embedded Event Manager Policy Director was unable to set thevariable with the requested information. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_SHM_OPEN : [chars]: ERROR opening shared mem IDB | |
|---|---|
| Explanation | An internal error was detected when attempting to open the IDB shared memory area |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_SMTP : Error occurred when sending mail to SMTP server: [chars] : [chars] | |
|---|---|
| Explanation | An unexpected error occurred when sending mail to SMTP server. |
| Recommended Action | |
| %HA_EM-3-FMPD_SMTP_SEND : Unable to send notification using all SMTP servers | |
|---|---|
| Explanation | An unexpected error occurred when sending mail to all SMTP servers. |
| Recommended Action | |
| %HA_EM-6-FMPD_SNMP_DUP_OID : [chars]: duplicate oid | |
|---|---|
| Explanation | The oid is a duplicate |
| Recommended Action | Check the EEM applet or policy configuration |
| %HA_EM-6-FMPD_SNMP_NO_VAR : [chars]: No variable [chars] | |
|---|---|
| Explanation | The variable is not defined. |
| Recommended Action | Check the EEM applet or policy configuration |
| %HA_EM-6-FMPD_SNMP_TRAPVAR_ADD : [chars]: Error adding trapvar to queue [chars] | |
|---|---|
| Explanation | The trap variable was not added to the queue. |
| Recommended Action | Check the EEM applet or policy configuration |
| %HA_EM-6-FMPD_SNMP_VARS_EXCEEDED : [chars]: number of values exceeded [dec] | |
|---|---|
| Explanation | The number of values per variable exceeded the maximum |
| Recommended Action | Check the EEM applet or policy configuration |
| %HA_EM-7-FMPD_SWITCH_FAIL : [chars]: The system is unable to switch to standby processor. Switchover cancelled. | |
|---|---|
| Explanation | Switchovers must occur when STANDBY is available and ready. |
| Recommended Action | None Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-6-FMPD_SWITCH_HARDWARE : [chars]: Policy has requested a hardware switchover | |
|---|---|
| Explanation | An Embedded Event Manager policy requested that a hardware switchoveroccur. |
| Recommended Action | None |
| %HA_EM-7-FMPD_SYSDB_VERIFY_REG : Could not register for SysDB verification: [chars] | |
|---|---|
| Explanation | An internal error was detected when trying to register verify function and/or apply function for SysDB tuple operations upon the given item within the given namespace. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_THREAD_POOL : [chars]: [chars] | |
|---|---|
| Explanation | An internal error was detected while initialization of threadpool. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_UNKNOWN_ENV : [chars]: could not find environment variable: [chars] | |
|---|---|
| Explanation | The Embedded Event Manager policy director could not find the environmentvariable specified in the action message. |
| Recommended Action | Only use well known Embedded Event Manager environment variables. If the message continues to occur, copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMPD_UNKNOWNTYPE : [chars]: Unknown event type found in applet. | |
|---|---|
| Explanation | The Embedded Event Manager applet had an unknown event type. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-6-FMPD_UPDATE_POLICY_COPY : Policy update has copied [dec] bytes from [chars] to [chars] | |
|---|---|
| Explanation | An EEM policy has been copied as a result of an event manager update command |
| Recommended Action | |
| %HA_EM-6-FMPD_UPDATE_POLICY_REGISTER : Policy update has successfully re-registered policy [chars] | |
|---|---|
| Explanation | An EEM policy has been successfully re-registered as a result of an event manager update command |
| Recommended Action | |
| %HA_EM-6-FMPD_UPDATE_POLICY_REGISTER_FAIL : Policy update has failed to register policy [chars] [chars] | |
|---|---|
| Explanation | An EEM policy has failed to be registered as a result of an event manager update command |
| Recommended Action | |
| %HA_EM-6-FMPD_UPDATE_POLICY_UNREGISTER_FAIL : Policy update has failed to unregister policy [chars] [chars] | |
|---|---|
| Explanation | An EEM policy has failed to be unregistered as a result of an event manager update command |
| Recommended Action | |
| %HA_EM-3-FMPD_WRONGTYPE : [chars]: Published event type does not match event spec. | |
|---|---|
| Explanation | The Embedded Event Manager Policy Director detected a mis-match in eventtype between the published event and the event spec. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_XDM_DISPATCH_FAIL : [chars]: XOS Dispatch Manager dispatch error: [dec] | |
|---|---|
| Explanation | XOS Dispatch Manager reports an error when dispatching an event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMPD_XDM_WAIT_FAIL : [chars]: XOS Dispatch Manager wait error: [dec] | |
|---|---|
| Explanation | XOS Dispatch Manager reports an error when waiting for an event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-ACTION_ADD_PARSER : [chars]: Unable to add action [chars] command; | |
|---|---|
| Explanation | Failed to add action command. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-ACTION_CNS_AGENT_UNAVAIL : [chars]: CNS Event Agent not available: [dec] | |
|---|---|
| Explanation | The CNS Event Agent is currently not available. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-ACTION_CNS_CLEAR_RESTART : [chars]: Unable to clear restart callback; | |
|---|---|
| Explanation | The CNS Action process failed to clear restart callback. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-ACTION_CNS_OPEN_FAIL : [chars]: Unable to open connection to CNS Event Agent: [dec] | |
|---|---|
| Explanation | The CNS Action process failed to open CNS handle to Event Agent. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-ACTION_CNS_SET_RESTART : [chars]: Unable to set restart callback; | |
|---|---|
| Explanation | The CNS Action process failed to set the restart callback. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-ACTION_ENQUEUE_FAIL : [chars]: Unable to enqueue [chars]; | |
|---|---|
| Explanation | The enqueue function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-ACTION_WB_CREATE : [chars]: create_watched_boolean failed: [chars] | |
|---|---|
| Explanation | The create_watched_boolean function reported an error trying to createthe watched boolean. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-ACTION_WB_DELETE : [chars]: delete_watched_boolean failed: [chars] | |
|---|---|
| Explanation | The delete_watched_boolean function reported an error trying to delete the watched boolean. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_ASYNC_ATTACH_CHKPT : [chars]: Failed to attach to handle chkpt asynchronous events; [chars] | |
|---|---|
| Explanation | The event_pulse_attach_event function reported an error trying to attach the chkpt pulse handler. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_ASYNC_ATTACH_DEFAULT : [chars]: Failed to attach to handle default asychronous events; [chars] | |
|---|---|
| Explanation | The event_pulse_attach_event function reported an error trying to attach the default pulse handler. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_CHKPT_INIT : [chars]: could not register the application with the checkpointing server: [chars] | |
|---|---|
| Explanation | Failed to register an application with the checkpointing server. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_CHKPT_ITERATE_END : [chars]: call to chkpt_iterate_end returned unexpected failure. | |
|---|---|
| Explanation | Unexpected error when iterating over a checkpointing table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_CHKPT_NULL_PTR : [chars]: Got a null [chars] when non-null value was expected | |
|---|---|
| Explanation | Failed to do further processing because we got a null data when a non-null value was expected. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_CHKPT_TBL_ADD : [chars]: could not add to the checkpointed [chars]: [chars] | |
|---|---|
| Explanation | Failed to add a record to the checkpointed table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_CHKPT_TBL_INFO_READ : [chars]: could not read the existing table information: [chars] | |
|---|---|
| Explanation | Failed to read the existing table information using checkpointing API. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_CHKPT_TBL_INIT : [chars]: failed to initialize [chars]: [chars] | |
|---|---|
| Explanation | Could not initialize a table with the checkpointing server. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_CHKPT_TBL_RECOVER : [chars]: could not recover for the checkpointed [chars]: [chars] | |
|---|---|
| Explanation | Failed to recover a record from the checkpointed table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_CHKPT_TBL_REMOVE : [chars]: could not remove from the checkpointed [chars]: [chars] | |
|---|---|
| Explanation | Failed to remove a record from a checkpointed table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_CHKPT_TBL_SAVE : [chars]: could not save to the checkpointed [chars]: [chars] | |
|---|---|
| Explanation | Failed to save a record to a checkpointed table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_CHKPT_TBL_UNREG : [chars]: could not unregister the checkpointed table [chars]: [chars] | |
|---|---|
| Explanation | Failed to unregister a checkpointed table. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMS_CNS_FAIL : [chars]: Failed to perform CNS action: [chars] | |
|---|---|
| Explanation | The Embedded Event Manager failed attempting to send a CNS message. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_CREATE_THREAD_POOL : [chars]: Error reported by create_thread_pool function; [chars] | |
|---|---|
| Explanation | The create_thread_pool function reported an error while attempting to create the thread pool. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMS_EMPTY_QUEUE : [chars]: The I/O queue empty. | |
|---|---|
| Explanation | The I/O queue is empty at this point, and should not be. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMS_ENQUEUE_FAIL : [chars]: The Unable to enqueue packet onto queue. | |
|---|---|
| Explanation | The queue is not in a state to handle enqueues. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_EVM_CREATE : [chars]: event_manager_create failed; [chars] | |
|---|---|
| Explanation | The event_manager_create function reported an error trying to initialize the event manager. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_EVM_EVENT_BLOCK : An error occurred while waiting for an event: [chars] | |
|---|---|
| Explanation | The event infrastructure will ignore this error and continue to wait for the next event. If this error is seen repeatedly, the process may not be able to function and will need to be restarted. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_FDC_ALLOCATE : [chars]: Failed to allocate Event Detector context control block; [chars] | |
|---|---|
| Explanation | The get_fd function reported an error trying to allocate a Event Detectorcontext control block. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_FDC_OPEN : [chars]: Failed to open Event Detector context control block | |
|---|---|
| Explanation | The open_fd function reported an error trying to open a Event Detectorcontext control block. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_GET_NODE_NAME : [chars]: platform_get_node_name failed; [chars] | |
|---|---|
| Explanation | The platform_get_node_name function reported an error trying to obtain the node name. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_GET_NODE_STATE : Failed to get the current nodes state: [chars] | |
|---|---|
| Explanation | The call to get the nodes current state failed. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_GET_PRIO : [chars]: Failed to get process priority; [chars] | |
|---|---|
| Explanation | The getprio function reported an error trying to obtain the default process priority. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_GUARD_WORD_VER : [chars]: [chars] guard word corrupted; [IPV6 address] | |
|---|---|
| Explanation | The guard word for the specified control block does not contain what isexpected. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_INV_ARG_STRING : [chars]: Invalid argument string: [chars] | |
|---|---|
| Explanation | An invalid argument string was passed to the specified function. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_INV_ENV_STRING : [chars]: Invalid environment string: [chars] | |
|---|---|
| Explanation | An invalid environment string was passed to the specified function. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_KILL : [chars]: Unable to kill process [chars]; [chars] | |
|---|---|
| Explanation | The kill function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_KILL_RUN : [chars]: Unable to kill run process [dec] for [chars]; [chars] | |
|---|---|
| Explanation | The kill function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-6-FMS_LAST_POLICY : [chars]: Cannot change a class [chars] [chars] to priority LAST. LAST is for default policies only | |
|---|---|
| Explanation | Embedded Event Manager Scheduler Command can only change a default policy to priority LAST. |
| Recommended Action | The command is applicable to default policies only. |
| %HA_EM-7-FMS_MALLOC : [chars]: Unable to allocate [chars]; [chars] | |
|---|---|
| Explanation | The malloc function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_MISC_ERR : [chars] ([chars]) | |
|---|---|
| Explanation | An unexpected error occurred. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-6-FMS_MODIFY_LAST_POLICY : [chars]: Cannot modify a LAST policy to class [chars]. LAST policies are for class default only. | |
|---|---|
| Explanation | Embedded Event Manager LAST policy is for default class only. |
| Recommended Action | The command is applicable to default policies only. |
| %HA_EM-6-FMS_MODIFY_POLICY : [chars]: unable to modify the policy to class [chars]: scheduling rule unavailable. | |
|---|---|
| Explanation | There is no scheduler rule configured to service this event class. |
| Recommended Action | Please configure a scheduler rule before modifying the event. |
| %HA_EM-7-FMS_NO_CLOCK : [chars]: unable to read clock using clock_gettime: [chars] | |
|---|---|
| Explanation | The clock_gettime function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-4-FMS_NO_SCHED_THREAD : No threads are configured to service event class [chars] | |
|---|---|
| Explanation | The Embedded Event Manager has no scheduler threads to service this event class. |
| Recommended Action | Track ED is not available in this image Configure threads for the event class using the 'event manager scheduler' command. |
| %HA_EM-3-FMS_NO_TRACK : keyword in the correlate statement is not supported in this image. | |
|---|---|
| Explanation | The Embedded Event Manager Track ED is not supported in this image. |
| Recommended Action | Track ED is not available in this image |
| %HA_EM-7-FMS_NULL_SCRIPT_NAME : [chars]: The script name is NULL | |
|---|---|
| Explanation | An invalid script name was passed as an argument into the specifiedfunction. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMS_OPEN : [chars]: Unable to open [chars]; [chars] | |
|---|---|
| Explanation | The open function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_OVL_NOTIFY_REG : [chars]: ovl_notification_register failed when registering to handle OVL notifications; [chars] | |
|---|---|
| Explanation | The ovl_register_notification function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_OVL_SETUP_ENV : [chars]: [chars] | |
|---|---|
| Explanation | Updating environment variables of the process according to system variables stored in sysdb failed. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMS_POLICY_CHECKSUM : [chars]: Checksum error for policy [chars] - this policy will not be run | |
|---|---|
| Explanation | The checksum computed for the specified policy does not match the original checksum computed when the policy was registered. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_POLICY_EXEC : [chars]: Policy execution [chars] | |
|---|---|
| Explanation | The Embedded Event Manager policy excution state has been changed to thestate named in the message. |
| Recommended Action | |
| %HA_EM-3-FMS_POLICY_HASH : [chars]: The hash computation routine reported an error; [chars] | |
|---|---|
| Explanation | The fh_hash_md5_fd() function reported the specified error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-3-FMS_POLICY_LOOKUP_FAIL : [chars]: Failed to look up in the table the registration specification for policy [chars]. | |
|---|---|
| Explanation | A table lookup for the registration specification for the policy failed. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_POLICY_MAX_ENTRIES : [chars]: Class [chars]: Maximum number of [dec] [chars] publish entries exceeded; some events have been discarded | |
|---|---|
| Explanation | An attempt to publish an event failed because there is no more room in the publish queue |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative |
| %HA_EM-6-FMS_POLICY_TIMEOUT : Policy '[chars]' has hit its maximum execution time of [dec].%9.9ld seconds, and so has been halted | |
|---|---|
| Explanation | The policy has exceeded its maximum execution time, and so has been halted part way through execution.If this policy is expected to take a long time to run, it may need to have 'maxrun_sec' added to the policy registration line (or its value increased if it is already specified). |
| Recommended Action | *NONE* |
| %HA_EM-3-FMS_QUEUE_INIT : [chars]: The Unable to initialize queue. | |
|---|---|
| Explanation | The queue cannot be initialized.An attempt to publish an event failed because there is no more roomin the publish queue. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative.Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_REALLOC_FAIL : [chars]: Unable to reallocate [chars]; [chars] | |
|---|---|
| Explanation | The realloc function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_REG_NODE_STATE_CHANGE : Failed to register for node state changes: [chars] | |
|---|---|
| Explanation | The call to register for node state changes failed. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-6-FMS_RELOAD_SYSTEM : [chars]: Policy has requested a system reload; | |
|---|---|
| Explanation | An Embedded Event Manager policy requested that the system be reloaded. |
| Recommended Action | |
| %HA_EM-6-FMS_RUNNING_POLICY : [chars]: cannot [chars] a running policy with jobid [dec]. | |
|---|---|
| Explanation | Embedded Event Manager Scheduler Command cannot change a running policy. |
| Recommended Action | The command is not applicable to a running policy. |
| %HA_EM-7-FMS_SPAWN : [chars]: Unable to spawn [chars]; [chars] | |
|---|---|
| Explanation | The spawn function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_STRDUP : [chars]: Failed to duplicate string [chars]; [chars] | |
|---|---|
| Explanation | The strdup function reported an error. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_SWITCH_FAIL : [chars]: The system is unable to switch to standby processor. Switchover cancelled. | |
|---|---|
| Explanation | Switchovers must occur when STANDBY is available and ready. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-6-FMS_SWITCH_HARDWARE : [chars]: Policy has requested a hardware switchover | |
|---|---|
| Explanation | An Embedded Event Manager policy requested that a hardware switchoveroccur. |
| Recommended Action | |
| %HA_EM-3-FMS_SWITCH_NOT_RF_ACTIVE : [chars]: This processor is not in ACTIVE state (state = [dec]). Switchover must be performed on ACTIVE processor. | |
|---|---|
| Explanation | Switchovers must occur on ACTIVE unit, not STANDBY unit. |
| Recommended Action | |
| %HA_EM-7-FMS_SYSLOG_SCAN_RESIGN : [chars]: Failed to unload Syslog FD DLL [chars]; return code=[dec] | |
|---|---|
| Explanation | The syslog_scan_resign function reported an error trying to unload the specified Syslog Event Detector DLL library. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_SYSLOG_SCAN_SIGNUP : [chars]: Failed to load Syslog FD DLL [chars]; return code=[dec] | |
|---|---|
| Explanation | The syslog_scan_signup function reported an error trying to load the specified Syslog Event Detector DLL library. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_SYSMGR_RELOAD_FM : [chars]: Failed to load Sysmgr FD DLL [chars]; return code=[dec] | |
|---|---|
| Explanation | The sysmgr_reload_fh_detector function reported an error trying to load the specified Sysmgr Event Detector DLL library. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_THREADPOOL_MAX : Maximum number ([dec]) of callback events exceeded for [chars]; There is no available thread in the threadpool to service the event. | |
|---|---|
| Explanation | An attempt to schedule an event requiring a callback failed because there is no available thread in the threadpool. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_THREAD_POOL_START : [chars]: Error reported by thread_pool_start function; [chars] | |
|---|---|
| Explanation | The thread_pool_start function reported an error while attempting to start the thread pool. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_WB_CREATE : [chars]: create_watched_boolean failed; [chars] | |
|---|---|
| Explanation | The create_watched_boolean function reported an error trying to createthe watched boolean. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_WDSYSMON_RELOAD_FM : [chars]: Failed to load WDSysMon FD DLL [chars]; return code=[dec] | |
|---|---|
| Explanation | The wd_reload_fh_detector function reported an error trying to load the specified WDSysMon Event Detector DLL library. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_WQ_CREATE : [chars]: create_watched_queue failed; [chars] | |
|---|---|
| Explanation | The create_watched_queue function reported an error trying to createthe watched queue. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_XDM_DISPATCH_FAIL : [chars]: XOS Dispatch Manager dispatch error: [dec] | |
|---|---|
| Explanation | XOS Dispatch Manager reports an error when dispatching an event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_XDM_WAIT_FAIL : [chars]: XOS Dispatch Manager wait error: [dec] | |
|---|---|
| Explanation | XOS Dispatch Manager reports an error when waiting for an event. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
| %HA_EM-7-FMS_XOS_DM_EXECUTE : [chars]: Failed to attach a handler to process child process exit; [chars] | |
|---|---|
| Explanation | The xos_dm_execute function reported an error trying to attach the handler to process child process exit. |
| Recommended Action | Copy the message exactly as it appears, and report it your technical support representative. |
HA_PROXY
| %HA_PROXY-3-PROXY_IPC_PAK_ALLOC_FAILED : | |
|---|---|
| Explanation | Allocation of IPC packet failed. |
| Recommended Action | LOG_STD_ACTION |
| %HA_PROXY-2-HA_SESSION_ALLOC_FAILED : [chars]: unable to allocate entry for [chars] binding | |
|---|---|
| Explanation | HA could not allocate a control block to manage the service |
| Recommended Action | LOG_STD_ACTION |
| %HA_PROXY-2-HA_FIND_SERVICE_FAILED : [chars]: unable to find [chars] service | |
|---|---|
| Explanation | HA could not find the specified service |
| Recommended Action | LOG_STD_ACTION |
| %HA_PROXY-3-HA_DUP_SERVICE_NAME : [chars]: Duplicate service name: [chars] on bind | |
|---|---|
| Explanation | Duplicate service name on ha service bind |
| Recommended Action | LOG_STD_ACTION |
| %HA_PROXY-3-HA_DUP_SERVICE_INDEX : [chars]: Duplicate service index: [dec] on bind | |
|---|---|
| Explanation | Duplicate service index on ha service bind |
| Recommended Action | LOG_STD_ACTION |
| %HA_PROXY-3-HA_INVALID_REQUEST : [chars]: Unknown request: [dec] | |
|---|---|
| Explanation | HA control services received unknown request |
| Recommended Action | LOG_STD_ACTION |
| %HA_PROXY-3-HA_MALFORMED_PKT : Malformed packet bad [chars] [hex], MSGDEF_LIMIT_MEDIUM | |
|---|---|
| Explanation | HA Sync packet was malformed, may not have been fully processed |
| Recommended Action | LOG_STD_ACTION |
| %HA_PROXY-4-HA_UNKNOWN_SERVICE : Sync msg for unknown service [hex] rg [hex], MSGDEF_LIMIT_MEDIUM | |
|---|---|
| Explanation | HA Sync received a message for an unknown service |
| Recommended Action | LOG_STD_ACTION |
| %HA_PROXY-4-HA_PKT_ERROR : Error processing HA sync pkt, rg [hex], MSGDEF_LIMIT_MEDIUM | |
|---|---|
| Explanation | HA Sync packet was dropped while processing |
| Recommended Action | LOG_STD_ACTION |
HDLC
| %HDLC-1-ISSU_NOMEMORY : msgtxt_nomemory | |
|---|---|
| Explanation | The requested operation could not be accomplished because of a low memory condition. |
| Recommended Action | Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. |
| %HDLC-4-ISSU_SENDFAILED : HDLC ISSU: send message failed, rc = [dec] | |
|---|---|
| Explanation | The sending of a message has failed. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %HDLC-4-ISSU_INCOMPATIBLE : hdlc-issu-compat: returned FALSE | |
|---|---|
| Explanation | The compatibility checking has failed |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %HDLC-4-ISSU_XFORM : [chars]: failed, rc=[chars] | |
|---|---|
| Explanation | The transform has failed. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). Issue the show tech-support command to gather data that may help identify the nature of the error. If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
HFSLIB
| %HFSLIB-3-HFSOPEN : Problem accessing the udev generated file: [chars] | |
|---|---|
| Explanation | No explanation. |
| Recommended Action | No action is required. |
| %HFSLIB-3-HFSINOFAILED : Inotify failed to initialize : [chars] | |
|---|---|
| Explanation | This error occurs when the inotify sub-system is misbehaving |
| Recommended Action | No action is required. |
| %HFSLIB-3-HFSINOWATCH : Inotify failed to add a watch: [chars] | |
|---|---|
| Explanation | This error occurs when the inotify sub-system is misbehaving |
| Recommended Action | No action is required. |
Feedback