-
Cisco IOS XR System Error Message Reference Guide, Release 3.2
-
Preface
-
Cisco IOS XR System Error Messages Overview
-
Access Control List (ACL) Error Messages for Cisco IOS XR
-
Fabric (FABRIC) Error Messages for Cisco IOS XR
-
Hardware Accessibility (HA) Messages for Cisco IOS XR
-
Installation (INSTALL) Messages for Cisco IOS XR
-
Internet Protocol (IP) Messages for Cisco IOS XR
-
Layer 2 (L2) Messages for Cisco IOS XR
-
Media (MEDIA) Messages on Cisco IOS XR
-
Manageability (MGBL) Messages for Cisco IOS XR
-
Operating System (OS) Messages for Cisco IOS XR
-
Packet Infrastructure (PKT_INFRA) Messages for Cisco IOS XR
-
Platform (PLATFORM) Messages for Cisco IOS XR
-
Quality of Service (QOS) Messages for Cisco IOS XR
-
Routing (ROUTING) Messages for Cisco IOS XR
-
Security (SECURITY) Messages for Cisco IOS XR
-
Simple Network Management Protocol (SNMP) Messages for Cisco IOS XR
-
System Database (SYSDB) Messages for Cisco IOS XR
-
Feedback
Table Of Contents
Operating System (OS) Messages
Operating System (OS) Messages
This section contains all Operating System(OS) and OS infrastructure related System Error Messages. The following facility codes are represented in this module:
action Messages
Error Message%OS-action-3-BISTATE_MSG State has changed
Explanation This is a test message for action-bistate 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%OS-action-3-NONE_MSG Invoking action 'none' message
Explanation This is a test message for action-none 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%OS-action-3-PEG1MSG Invoking action 'peg' message
Explanation This is a test message for action-peg 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%OS-action-3-PEG2MSG Invoking action 'peg' message
Explanation This is a test message for action-peg 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%OS-action-3-RESET_MSG Invoking action 'reset' message
Explanation This is a test message for action-reset 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%OS-action-3-RESTART_MSG Invoking action 'restart' message
Explanation This is a test message for action-restart 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%OS-action-3-TESTMSG Invoking a test message [chars]
Explanation This is a test message for ios error message
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ALARM_TEST Messages
Error Message%OS-ALARM_TEST-3-ALARM_GENERATE [chars] alarm generated [[unsigned int] [chars] alarms generated so far]: [chars]
Explanation Autogenerated alarm
Recommended Action No action is required.
ATC_CACHE Messages
Error Message%OS-ATC_CACHE-3-ERROR Operation [chars] failed : [chars]
Explanation The specified operation 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%OS-ATC_CACHE-6-INFO [chars] [chars]
Explanation Information pertaining to the attractor cache process operation
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ATC_LIB Messages
Error Message%OS-ATC_LIB-3-CLASS_CACHE_CREATE_FAIL Unable to create class cache entry for class [chars]
Explanation The specified operation 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%OS-ATC_LIB-3-ERROR Operation [chars] failed : [chars]
Explanation The specified operation 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%OS-ATC_LIB-6-INFO [chars] [chars]
Explanation Information pertaining to the attractor cache library operation
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ATTRACTOR Messages
Error Message%OS-ATTRACTOR-3-ERROR Operation [chars] failed : [chars]
Explanation The specified operation 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%OS-ATTRACTOR-6-INFO [chars] [chars]
Explanation Information associated with current attractor process 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.
AVPAIR Messages
Error Message%OS-AVPAIR-6-ADD_FAIL [chars]: avpair_add failure on avlist [hex].
Explanation avpair_add failed while unpacking the Posix message into avlist
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-AVPAIR-6-BUFFER_TOO_SMALL [chars]: need [dec] bytes, only have [dec] in buffer, msg dropped.
Explanation avpair API fails because the buffer is too small.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-AVPAIR-6-ERR_BAD_AVLIST [chars]: Attempt to use uninitialized avlist [hex].
Explanation An illegal attempt to use an uninitialized avpair list
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-AVPAIR-6-ERR_BAD_LIST [chars]: Attempt to re-initialize list [chars] failed
Explanation An illegal attempt to reinitialize an avpair list
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
BAG Messages
Error Message%OS-BAG-7-BYTECODE Unknown bytecode character '[char]'
Explanation The bytecode is not recognised, the bag may be corrupt.
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%OS-BAG-7-DISCRIM Union switch type didn't match the discriminant [dec]
Explanation No matching type found (and no default supplied) when interpretting discriminant in bag definition. The operation was aborted.
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%OS-BAG-7-DLL Error accessing bag DLL [chars]: [chars]
Explanation There was a problem accessing the named dll, either to open, close or access a symbol. The operation was aborted.
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%OS-BAG-7-GENERAL [chars]
Explanation An operation failed. The explanation is in the error message.
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%OS-BAG-7-LOCK Failed to obtain mutex: [chars]
Explanation Mutex could not be locked. The operation was aborted.
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%OS-BAG-7-PARAMS Bad parameter passed to function
Explanation Invalid parameter (NULL pointer) passed to function. The operation was aborted.
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%OS-BAG-7-PATHNAME SysDB pathname too long
Explanation The string being dealt with exceeded the defined maximum for a path in SysDB. The operation was aborted.
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%OS-BAG-7-RANGE An integer value did not fall within the range specified for its type.
Explanation A value found while decoding a bag does not not fall within the range specified in the bag file.
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%OS-BAG-7-SYSDB Error accessing [chars] in SysDB: [chars]
Explanation There was a problem accessing the named item. This could be an temporary problem caused by an outage in the connection to the server. The connection will be restored, but the operation itself was aborted.
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%OS-BAG-7-VERSION [chars] version conflict: got [dec], expecting [dec] ([chars])
Explanation Version mismtach in bag.
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%OS-BAG-7-XDR XDR operation failed
Explanation An operation interpretting the XDR from a bag failed. This could be a bytecode error, a data mismatch or memory exhaustion.
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.
BANNER Messages
Error Message%OS-BANNER-3-CERR_REGISTER_FAILED Error code registration failed: [chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-BANNER-3-CONFIG_INIT_FAILED Banner config initialization failed: [chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-BANNER-3-EVENT_BLOCK_ERROR Event block dispatch error: [chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-BANNER-3-EVENT_MGR_CREATE_FAILED [chars]: event manager creation failed: [chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-BANNER-3-SYSMGR_CALL System manager call [chars] failed: [chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-BANNER-7-SYSDB_BIND_FAILURE Failed to bind to sysdb path [chars]: [chars]
Explanation Error binding to sysdb path
Recommended Action Copy the message exactly as it appears, andreport it your technical support representative.
Error Message%OS-BANNER-7-SYSDB_REGISTRATION_FAILURE Failed to register for sysdb path [chars]: [chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-BANNER-7-SYSDB_UNREGISTRATION_FAILURE Failed to unregister for sysdb path [chars]: [chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-BANNER-7-UNKNOWNCARD The cardtype [dec] is unknown to us
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
BCDL Messages
Error Message%OS-BCDL-3-MSG_AGENT_USAGE usage: [chars] -p producer_base_name [-t r]
Explanation Incorrect command line arguments were given to the module
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_BASE_NAME The plug-in base name: [chars] is longer than [dec] bytes
Explanation The name could not be used.
Recommended Action Contact support.
Error Message%OS-BCDL-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%OS-BCDL-3-MSG_CONTROL_USAGE usage: [chars]
Explanation Incorrect command line arguments were given to the module
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_DEBUG_INIT Unable to initialize debug capabilities: [chars] failed: [chars]
Explanation The program cannot initialize its debug capabilities.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_DEBUG_INIT Unable to initialize debug capabilities: [chars] failed: [chars]
Explanation The program cannot initialize its debug capabilities.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_DEBUG_SERVICES debug services function [chars] failed
Explanation A call to a debug services interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_DEBUG_SERVICES debug services function [chars] failed
Explanation A call to a debug services interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_DLL_OPEN The plug-in dll: [chars] could not be loaded: [chars]
Explanation The interface library is not availble.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_DLSYM The plug-in dll symbol [chars] could not be found: [chars]
Explanation The interface library is not availble.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_DOUBLE_AGENT Found duplicate agent for BCDL group [chars]: node [hex], jid [dec]
Explanation A BCDL agent for the group is already running.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_EVENT event manager function [chars] failed, error [dec]: [chars]
Explanation A call to a event manager interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_EVENT_MANAGER event manager function [chars] failed: [chars]
Explanation A call to an event manager interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_GENERIC_FUNC function [chars] failed: [chars]
Explanation A call to some function interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_GENERIC_FUNC function [chars] failed: [chars]
Explanation A call to some function interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_GROUP group services function [chars] failed for gid [dec], error [dec]: [chars]
Explanation A call to a group services interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_GROUP group services function [chars] failed for gid [dec], error [dec]: [chars]
Explanation A call to a group services interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_GROUP_CREATE group_create failed for group [chars], error [dec]: [chars]
Explanation A call to a group services interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_GROUP_CREATE_LWG group_create_lwg failed for group [chars], parent gid [dec], error [dec]: [chars]
Explanation A call to a group services interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_GROUP_MBRSET Memberset contains [dec] mbrs: (gid/nid/pid) [chars]
Explanation Displaying the memberset details of a failed _memberset call.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_GROUP_MBRSET Memberset contains [dec] mbrs: (gid/nid/pid) [chars]
Explanation Displaying the memberset details of a failed _memberset call.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_GROUP_NODESET Nodeset contains [dec] mbrs: (nid) [chars]
Explanation Displaying the memberset details of a failed _nodeset call.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_GROUP_NODESET Nodeset call: gid [dec], nid [dec]
Explanation Displaying the memberset details of a failed _nodeset call.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_HB_MISS group [chars]: no heartbeats received in last [dec] seconds
Explanation The bcdl client library detected that it should have received a heartbeat from the agent, but didn't
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_HB_SEQ group [chars]: seq in heartbeat from agent [dec], my seq [dec]
Explanation The bcdl client library detected that it has missed some messages and is re-establishing the connection to the agent.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_INSTALLMGR An error was returned from install mgr function [chars]: [chars]
Explanation A call to an install manager function failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_IPV4_RIB ipv4 rib function [chars] failed: [chars]
Explanation A call to an ipv4 rib interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_LOST group [chars]: lost [dec] messages
Explanation The bcdl client library detected that it should have received some number of messages, but didn't see them.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_LRD lrd function [chars] failed: [chars]
Explanation A call to an lrd api failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_LWM LWM function [chars] failed, error [dec]: [chars]
Explanation A call to a LWM interface failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_MALLOC Couldn't malloc [dec] bytes: [chars]
Explanation The requested memory is not available
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_MALLOC Couldn't malloc [dec] bytes: [chars]
Explanation The requested memory is not available
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_PTHREAD Pthread operation [chars] [hex] failed: [chars]
Explanation The mutex lock/unlock failed
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_PTHREAD Pthread operation [chars] [hex] failed: [chars]
Explanation The mutex lock/unlock failed
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_READ_FAILED read error: [chars]
Explanation A read from the producer returned an error.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_RINFO Unable to use group services function [chars] for type [dec]: error [dec]: [chars], grp has [dec] mbrs
Explanation A call to a group services rinfo function failed.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_SEQ_ERR seq error group [chars]: expect [dec] actual [dec]
Explanation The bcdl client library received a message out of sequence.
Recommended Action Contact support.
Error Message%OS-BCDL-3-MSG_TABLE_FUNC Attempt to [chars] table id [dec] for sg [dec] failed: [chars]
Explanation A call to the producer (rib) table function failed. Routes may not be being downloaded correctly.
Recommended Action Contact support.
Error Message%OS-BCDL-7-MSG_CRIT_NORM Bad bytes critical ([dec]) or normal ([dec]), using default [dec] and [dec]
Explanation The bcdl_agent_start api was used incorrectly.
Recommended Action Contact support.
Error Message%OS-BCDL-7-MSG_STALL_RESET Hit max of [dec] messages queued - initiating reset of this consumer
Explanation The consumer is not servicing the incoming message queue.
Recommended Action Contact support.
BLWM Messages
Error Message%OS-BLWM-4-BATCH_CONFIG_REPLY_FAILED Failed to send batch-configuration reply to client, errno [dec]
Explanation A BLWM-enabled server failed to send a reply about batch configuration to the client. The client might have restarted and this could be a transient error. Wait for the client to restart and reestablish connection with the server.
Recommended Action No action is required.
Error Message%OS-BLWM-4-BATCHED_REPLY_FAILED Failed to send a batch of replies to client, errno [dec]
Explanation A BLWM-enabled server encountered a failure while sending batched replies to the client. The client might have restarted. Wait for the client to restart and reconnect to server to resume the processing.
Recommended Action No action is required.
Error Message%OS-BLWM-4-PULSED_FLUSH_FAILED Pulsed flush of batched requests failed, Reason: [chars]
Explanation A BLWM-enabled client failed to flush the batched LWM requests. This is most likely because the server process restarted. Wait for client to reestablish connection with server and flush the batched requests again.
Recommended Action No action is required.
Error Message%OS-BLWM-4-REPLY_PROCESSING_ERRORS An error ocurred while processing the batched replies, error: [chars]
Explanation A failure occurred while processing the batched replies received from the server. This is most likely an internal error.
Recommended Action No action is required.
Error Message%OS-BLWM-4-RESTART_PROCESSING_ERRORS An error ocurred during restart handling, error: [chars]
Explanation A failure occurred while processing the requests/replies from the previous life after a restart. A best-effort attempt is made to process the requests/replies from the previous life. if this attempt fails, this error message is printed and the state is reset for normal BLWM operation.
Recommended Action No action is required.
Error Message%OS-BLWM-4-SHMEM_FAILURE Failed to acquire/access shared memory, error: [chars]
Explanation A failure occurred while initializing or accessing the shared memory buffer used to assemble the responses. This is most likely an internal error.
Recommended Action No action is required.
Error Message%OS-BLWM-4-TIMED_FLUSH_FAILED Timed flush of batched requests failed, Reason: [chars]
Explanation A BLWM-enabled client failed to flush the batched LWM requests. This is most likely because the server process restarted. Wait for client to reestablish connection with server and flush the batched requests again.
Recommended Action No action is required.
Error Message%OS-BLWM-4-WARNING [chars] rc = [dec]
Explanation For displaying blwm debugging information.
Recommended Action No action is required.
BTREE Messages
Error Message%OS-BTREE-3-INTERNAL [chars]: rc [hex]
Explanation The btree library has either failed a function that expected to succeed, or has got into an inconsistent state.
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%OS-BTREE-3-LOCKING Failed to [chars] [chars]. Error [dec]
Explanation The btree library has either failed to aquire or release a lock.
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%OS-BTREE-3-MEMORY Failed to malloc [unsigned int] bytes
Explanation The btree library has failed to aquire the required amount of memory.
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.
CHUNK Messages
Error Message%OS-CHUNK-2-BADELESIZE Chunk element size is more than 64k for [chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-CHUNK-2-BADREFCOUNT Bad chunk reference count ([dec]), chunk [pointer] data [pointer].
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%OS-CHUNK-2-BOUNDS Attempted to exceed freelist chunk bounds, chunk [hex], data [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-CHUNK-2-DESTROY_NOTEMPTY Attempted to destroy chunk with siblings, chunk [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OS-CHUNK-2-FREE Attempted to free nonchunk memory, chunk [pointer], data [pointer]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OS-CHUNK-2-INVFREE Attempted to free already freed chunk memory, chunk [hex], data [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OS-CHUNK-2-LOCK Attempted to lock unlockable chunk data, chunk [hex] data [hex]
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%OS-CHUNK-2-NEG_FREE_COUNT Negative free counter on chunk [chars]
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%OS-CHUNK-2-NOSIBLING Could not find the sibling to allocate memory from. Chunk [chars], total free [dec] inuse [dec].
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-CHUNK-2-NULLCHUNK NULL chunk pointer argument
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-CHUNK-2-PARTIAL Attempted to destroy partially full chunk, chunk [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OS-CHUNK-2-SIB_INDEX Error noticed in the sibling of the chunk [chars] Chunk index : [dec], Chunk real max : [dec]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-CHUNK-3-CREATE Chunk named [chars] not created because [chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-CHUNK-3-INIT Error initializing chunk [chars], mutex error, [chars]
Explanation The chunk's mutex could not be initialized.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%OS-CHUNK-3-PRIVMEM_SIZE Private pool size ([dec]) smaller than request ([dec])
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
DEBUG_CERR Messages
Error Message%OS-DEBUG_CERR-7-REGISTER [chars]: could not register the debug specific structured error messages: [chars]
Explanation The debug library was unable to register its debug specific condition codes. Condition messages from the debug library are likely to be degraded.
Recommended Action Check to see if sufficient memory resources remain for normal operations. Add memory if necessary. Verify the installation of the debug library. Re-load if required.
deflate Messages
Error Message%OS-deflate-3-ERROR [chars] [chars] [chars]
Explanation Error in uncompressing
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
DISTRIB_LIB Messages
Error Message%OS-DISTRIB_LIB-3-ASYNC_HANDLER_FAILED [chars]: error attaching async handler: [chars]
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%OS-DISTRIB_LIB-3-BAD_MSG_TYPE [chars]: bad message type [dec]
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%OS-DISTRIB_LIB-3-BAD_REPLY [chars]-I-replying to a non-block sync msg
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%OS-DISTRIB_LIB-3-CONNECT_FAILED [chars]: ### failed to connect to [chars], [chars]
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%OS-DISTRIB_LIB-3-CONNECT_GSP_FAILED [chars]: error connecting to GSP: [chars]
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%OS-DISTRIB_LIB-3-CREATE_GROUP_ERR [chars]:[dec] [chars]
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%OS-DISTRIB_LIB-3-DEF_SYNC_HANDLER_FAILED [chars]: error attaching lib's default sync handler: [chars]
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%OS-DISTRIB_LIB-3-EVENT_ASYNC_ATTACH_FAILED [chars]: error async attach all failed: [chars]
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%OS-DISTRIB_LIB-3-EVENT_FILE_ATTACH_FAILED [chars]: event_file_attach call failed: [chars]
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%OS-DISTRIB_LIB-3-FUNCTION_ERR [chars]:[dec] [chars]
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%OS-DISTRIB_LIB-3-GSP_FAILURE [chars] GSP failure connection lost...
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%OS-DISTRIB_LIB-3-GSP_MSG_RCV_FAILURE [chars]: error retrieving msg from GSP: [chars]
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%OS-DISTRIB_LIB-3-GSP_TRACE_BACK [chars] : [chars] [hex]
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%OS-DISTRIB_LIB-3-INIT_MEM_MANAGER_FAILED [chars]: error initializing lib memory manager
Explanation Error initializing lib memory 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%OS-DISTRIB_LIB-3-MALLOC_FAILED [chars]:[dec] malloc failed
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%OS-DISTRIB_LIB-3-MSG_CHAN_DISCONNECT_FAIL [chars]: msg_chan_disconnect failed [chars]
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%OS-DISTRIB_LIB-3-MSG_GET_CONN_FAILED [chars]: msg_get_conn call failed: [chars]
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%OS-DISTRIB_LIB-3-MSG_SEND_ERR [chars] msg_send error ERRNO: [dec]::[chars]
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%OS-DISTRIB_LIB-3-MUNMAP_FAILED [chars]: munmap of size [dec] at addr [hex] failed. Error [chars]
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%OS-DISTRIB_LIB-3-MUTEX_OP_FAILED [chars]: Mutex op [chars] failed on mutex [chars]: [chars]
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%OS-DISTRIB_LIB-3-NO_PRIV_MSG_HANDLER [chars]: no private msg handler!
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%OS-DISTRIB_LIB-3-REG_ERROR [chars]-E-[chars]
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%OS-DISTRIB_LIB-3-SBM_MODE_ENTER_ERR [chars]: error sending sbm mode enter: [chars]
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%OS-DISTRIB_LIB-3-SYNC_RESP_ERR [chars] error sending SYNC_RESPONSE: [chars]
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%OS-DISTRIB_LIB-6-BAD_SEQ_CHAN [chars]: Sequencer channel for [chars] does not exist.
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%OS-DISTRIB_LIB-6-GROUP_SEQ_INFO [chars][[dec]]-setting lib seq for gid : [dec] to nidx
Explanation Just more information.
Recommended Action 'No action is required.'
Error Message%OS-DISTRIB_LIB-6-GSP_TRACE_HDR [chars] : Previous accesses (line number): [chars]
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%OS-DISTRIB_LIB-6-MEM_TRACE_BLOCK [chars] -Traceback= [hex] [hex] [hex] [hex] [hex]
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.'
DUMPER_MARK Messages
Error Message%OS-DUMPER_MARK-4-NO_SLOT The array is filled, no slot found for inserting [hex] dropping request
Explanation A new request for marking segment came, but the marker reference array is already filled. Dropping this request.
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%OS-DUMPER_MARK-7-NOT_FOUND The given entry [hex] not found, dropping request
Explanation The request for a page to be unmarked came, but no such marking was found in the reference array.
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.
DUMPER_SNAP Messages
Error Message%OS-DUMPER_SNAP-3-INSANE Coredump request rate exceeds sanity threshold - restarting process
Explanation The process explicitly configured a threshold of how many non-invasive voluntary coredump requests should be permitted before deeming the process insane. This has been exceeded, and so the process is being restarted.
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%OS-DUMPER_SNAP-4-DUMP Process [dec] requested voluntary [chars] dump of itself
Explanation A non-invasive voluntary coredump requested by the process. Process might be experiancing a condition which needs investigation. This core file will help analysing the issue.
Recommended Action This should not occur in normal conditions, please provide the coredump to TAC.
Error Message%OS-DUMPER_SNAP-4-NODUMP Problem with voluntary core dump requested by [dec] when [chars]: [chars]
Explanation A non-invasive voluntary coredump was requested by the process, and was within the configured rate-limit, but a problem occured that prevented the coredump from being created.
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%OS-DUMPER_SNAP-6-DUMP_OK Voluntary core dump requested by process [dec] completed
Explanation A non-invasive voluntary coredump requested by the process completed successfully. Process might be experiancing a condition which needs investigation. This core file will help analysing the issue.
Recommended Action This should not occur in normal conditions, please provide the coredump to TAC.
Error Message%OS-DUMPER_SNAP-6-LIMITED Coredump request would exceed configured rate-limit
Explanation A non-invasive voluntary coredump was requested by the process, but was declined since this would exceed the configured rate-limit.
Recommended Action None, this is benign.
DUMPER Messages
Error Message%OS-DUMPER-1-BAD_CHANNEL [chars]: can't create channel
Explanation Channel creation failed for the dumper 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%OS-DUMPER-1-BAD_PATHNAME_ATTACH [chars]: can't attach resmgr funcs '[chars]'
Explanation Failed to attach pathname to the 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%OS-DUMPER-1-CLOSE_PROBLEM [chars] failed. Error: [chars]
Explanation Possibly the server died.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-1-CONNECT_FAILED errmsg_connect_attach chid [dec] : [chars]
Explanation Connect attach 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%OS-DUMPER-1-DEBUG_INIT_FAILURE Dumper debug initialization error
Explanation Dumper debug initialization 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%OS-DUMPER-1-EVENT_BLOCK_ERROR event_block error -- [chars]
Explanation Error during event block
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-1-EVENT_MGR_CREATE_FAILED [chars]: can't create event manager. [chars]
Explanation Failed to create event manager for the 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%OS-DUMPER-1-PROC_OPEN_FAILED Fail to open process, pid = [dec]. Error = [chars]
Explanation Could not open the process file system
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-1-QSM_ADD_SERVICE_DIRECTORY Dumper qsm add service directory error
Explanation Dumper initialization 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%OS-DUMPER-1-SYSDB_APPLY_FAILURE Failure in verification apply handler for [chars]. [chars]
Explanation Error in apply 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%OS-DUMPER-1-SYSDB_INIT_FAILURE Dumper configuration initialization error
Explanation Dumper configuration initialization 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%OS-DUMPER-1-SYSDB_NOTIFY_FAILURE Failure in notification handler for [chars]. [chars]
Explanation Error in notify 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%OS-DUMPER-1-SYSDB_REGISTRATION_FAILURE Sysdb registration for [chars] failed. Error: [chars]
Explanation Sysdb registration failure
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-1-UNKNOWNCARD Dumper unknown card
Explanation Platfrom card type unknown to dumper.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-DUMPER-3-BAD_CORE_SIZE Bad core file size, Expecting: [dec], Collected: [dec]
Explanation Could not collect the entire core file data
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-BAD_DEBUG_INIT_THREAD Could not start the debug init thread: [chars]
Explanation Could not start a 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%OS-DUMPER-3-BAD_THREAD [chars]: [chars] failed: [chars]
Explanation Could not start a 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%OS-DUMPER-3-DEBUG_INIT_FAILED [chars]
Explanation Debug init 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%OS-DUMPER-3-DEVCTL_FAILED Devctl Code: [dec] failed. Error: [chars]
Explanation A devctl 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%OS-DUMPER-3-DUMP_FAILURE Core dump failed: [chars]
Explanation Could be any number of reasons. Check for other error 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%OS-DUMPER-3-DUMP_INFO_PROBLEM Dump Info [chars] failure. Error: [chars]
Explanation Something went wrong with the dump information storage scheme
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-DUMP_TIMEDOUT The core dump timedout, core file may be incomplete or corrupted, [chars] failed: [chars]
Explanation An internal time out on core dump.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-ERROR [chars]: Unexpected error: [chars]
Explanation Encountered an unexpected 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%OS-DUMPER-3-FAIL_DEBUG_REG [chars]: Can't connect to configuration, [chars]
Explanation DUMPER debugging service register to sysdb failed.
Recommended Action Check the existence of the Sysdb service. The system is supposed to re-register if the Sysdb service is available.
Error Message%OS-DUMPER-3-FAIL_PRE_FLAGS [chars]: Sysdb debug - fetching pre defined flags failed
Explanation NVRAM debugging service fetching pre defined flags from sysdb failed.
Recommended Action Check the existence of the Sysdb service. The system is supposed to re-register if the Sysdb service is available.
Error Message%OS-DUMPER-3-GET_FSLIST_FAILED [chars]: unable to read platform dependent filesystem
Explanation Most probably some problem with the file systems data file
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-GET_MAPINFO_FAILED devctl DCMD_PROC_MAPINFO failed, Error: [chars]
Explanation A devctl 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%OS-DUMPER-3-GET_PAGEDATA_FAILED devctl DCMD_PROC_PAGEDATA failed, Error: [chars]
Explanation A devctl 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%OS-DUMPER-3-GET_PROC_TIDSTATUS_FAILED devctl DCMD_PROC_TIDSTATUS failed
Explanation A devctl 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%OS-DUMPER-3-GET_PROCINFO_FAILED devctl DCMD_PROC_INFO failed. Error: [chars]
Explanation A devctl 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%OS-DUMPER-3-INVALID_PATH [chars] not a valid path or not supported
Explanation most probably tried to configure an unsupported path e.g. rcp.
Recommended Action 'Configure a valid path'
Error Message%OS-DUMPER-3-ITERATOR_FAILURE [chars] [chars]
Explanation Iteration over sysdb tuples failure
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-KERNEL_INFO_MMAP_FAILURE Could not map kernel dumper information. [chars]
Explanation Space might not have been allocated for storing kernel dump 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%OS-DUMPER-3-KERNEL_INVALID_PATH Valid paths are only /bootflash: and tftp:
Explanation kernel core can only be dumped to bootflash or tftp
Recommended Action 'Configure a valid path'
Error Message%OS-DUMPER-3-LRD_ERROR [chars]: Unable to determine node specific role from LRD. Error: [chars]
Explanation Could not determine node status. Dumper will work in all respect except the behavior regarding dumper configuration may not be appropriate. Check that all nodes in the LR/system are properly booted. dumper process can be restarted as an workaround if this message is seen.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-LSEEK_FAILED Seek to [hex] for fd [dec] failed. Error: [chars]
Explanation Most probably some problem with the file system
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-MALLOC_FAILED Malloc failed
Explanation Memory running low
Recommended Action Reboot the router
Error Message%OS-DUMPER-3-MMAP_FAILED Map of file descriptor [dec] for size [dec] Offset [hex] failed: [chars]
Explanation Something wrong
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-MSGERROR_FAILED Failed to reply to client. Error: [chars]
Explanation Could not reply to client
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-MSGREPLY_FAILED Failed to reply to client. Error: [chars]
Explanation Could not reply to client
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-MUNMAP_FAILED Unmap for size [dec] at Address [hex] failed: [chars]
Explanation Something wrong
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-OPEN_FAILED Open of path [chars] failed. Error: [chars]
Explanation Could not open a file
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-PROCESS_NAME_FAILED No process name information available, using pid as name instead: [chars]
Explanation Something wrong
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-PTHREAD_MUTEX_FAILED mutex operation [chars] failed for [chars] mutex: [chars]
Explanation A internal mutex operation has failed. This is a bug.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-PTHREAD_TIMEDJOIN_FAILED thread timed join operation failed: [chars]
Explanation A internal timed thread join operation has failed. This is a bug.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-READ_FAILED Read of size [dec] from fd [dec] failed. Error: [chars]
Explanation Most probably some problem with the file system
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-REGISTRATION_FAILURE Couldn't register [chars]%s with sysdb. Error [chars]
Explanation Could not register with sysdb
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-REMOVE_LOWMEM Removing dump [chars] as we are in low memory condition
Explanation Memory running low
Recommended Action Reboot the router
Error Message%OS-DUMPER-3-REPLY_OS Reply to OS failed. Error: [chars]
Explanation Could not reply to OS
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-STACK_PREALLOCATE_ERROR Could not pre-allocate stack
Explanation Failed to memory map buffer to be used as stack for a critical 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%OS-DUMPER-3-SYSDB_BAD_ITEM Bad item : [chars]. [chars]
Explanation Unexpected or bad item under config for dumper
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-DUMPER-3-SYSDB_BAD_ITEM_TYPE Bad item type for [chars]
Explanation Unexpected item type in dumper config
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-DUMPER-3-SYSDB_BIND_FAILURE [chars]: Unable to bind to [chars]. Error: [chars]
Explanation Could not connect to sysdb
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-SYSDB_CALL Failed call : [chars]. Error [chars]
Explanation Unexpected failure for sysdb call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-DUMPER-3-SYSDB_UNBIND_FAILURE Unable to unbind from [chars]. Error: [chars]
Explanation Could not disconnect to sysdb
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-SYSMGR_CALL Failed call : [chars]. Error [chars]
Explanation Unexpected failure for sysdb call.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-DUMPER-3-TIMER_PROBLEM Timer [chars] failure. Error: [chars]
Explanation Something went wrong with the 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%OS-DUMPER-3-TRACE_BACK_FAILED Stack trace back failed
Explanation Could not figure out trace back
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-UNLINK_FAILED Unlink of [chars] failed. Error: [chars]
Explanation Could not delete a file
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-3-WRITE_FAILED Write of size [dec] to fd [dec] failed. Error: [chars]
Explanation Most probably some problem with the file system
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-4-CORE_INFO Core for pid = [dec] ([chars]) requested by [chars]@[chars]
Explanation Debug core info
Recommended Action No action is required.
Error Message%OS-DUMPER-4-CRASH_INFO Crashed pid = [dec] ([chars])
Explanation Debug crash info
Recommended Action No action is required.
Error Message%OS-DUMPER-4-ITEM_GET_FAILURE [chars]: Could not get [chars] [chars]
Explanation Could not get sysdb item.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-4-ITEM_SET_FAILURE [chars]: Could not set [chars] [chars]
Explanation Could not set sysdb item.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-4-SHOW_REGISTERS_FAILED show registers call failed
Explanation Could not get the registers context for the process being dumped. This could happen if a core dump is explicitly requested of a running or suspended process using dumpcore command. If not it is a bug.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-4-SIGNALCORE_INFO Core for pid = [dec] ([chars]) as signal [dec] sent by [chars]@[chars]
Explanation Debug core info
Recommended Action No action is required.
Error Message%OS-DUMPER-4-UNKNOWNCORE_INFO Core for pid = [dec] ([chars]) requested by Unknown
Explanation Debug core info
Recommended Action No action is required.
Error Message%OS-DUMPER-5-CORE_FILE_NAME Core for process [chars] at [chars]
Explanation Name of the core file
Recommended Action No action is required.
Error Message%OS-DUMPER-5-CORE_TRANSFER_STATUS Transfer of Core file from [chars] to [chars] [chars]
Explanation Status of the core dump transfer to persistent location.
Recommended Action No action is required.
Error Message%OS-DUMPER-5-DUMP_SUCCESS Core dump success
Explanation Core dump succeded
Recommended Action No action is required.
Error Message%OS-DUMPER-5-PATH_REMOVED [chars] path for core file has been removed
Explanation Configured path for core file has been removed
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-6-BAD_PATH Choice [dec] either not configured or bad path. Trying next choice.
Explanation Could be any number of reasons. Check for other error 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%OS-DUMPER-6-BOOT_DEVICE_FAILURE Failed to get boot device for local node:[chars]
Explanation Failed to determine the boot device for a RP
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-6-CORE_DUMP_OFF Core for process [chars] turned off
Explanation The core for the process has turned off delibrately
Recommended Action No action is required.
Error Message%OS-DUMPER-6-CORE_FILE_NAME_UNAVAIL Could not get core file name for crash
Explanation The core dump file name for this crash is invalid.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-6-CORRUPT_CONTEXT Dumper context information is corrupted, throwing it away
Explanation Looks like the core context infomation dumper stores is corrupted. The conext is being reset, all existing context infomation will be lost.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-6-FALLBACK_CHOICE Fall back choice: [chars]
Explanation Could be any number of reasons. Check for other error 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%OS-DUMPER-6-FALLBACK_CHOICE_BOOT_DEV Fallback choice is on boot device of local or remote node.
Explanation The fallback choice is on the boot device for either the local node or the remote node. This device would be skipped as dump device choice to prevent dumper filling it up with core dumps.
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-6-FB_CHOICE_STATUS_FAIL Failed to get status of the fallback device:[chars]
Explanation Failed to get status about the fallback device option specified.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-6-LOCAL_BOOT_DEVICE_FAIL Cannot determine the local boot device
Explanation Failed to determine the local boot device for checking the validity of dumper fallback options.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-6-NODE_NAME_FAIL Failed to get the local nodes internal node name
Explanation Failed to get the local node name from 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%OS-DUMPER-6-ONLY_CONTEXT Displaying just the context information as Core for process [chars] turned off
Explanation The core for the process has turned off delibrately
Recommended Action No action is required.
Error Message%OS-DUMPER-6-OPEN_TEXT_DUMP_FAIL Failed to open the text dump file [chars], errno:[dec]
Explanation The text dump file could not be opened.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-6-READ_TEXT_DUMP_FAIL Failed to read from text dump file:[chars]. Error:[chars]
Explanation Failed to read from the text dump file.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-6-REMOTE_DEVICE_FAIL Failed to get the remote device for the fallback path
Explanation Failed to get teh remote device to which the fallback option is linked.
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-6-REMOVE_OLDEST Removing dump [chars] as we can have only limited number of cores in fallback path
Explanation Memory limitation.
Recommended Action None
Error Message%OS-DUMPER-6-SKIP_FALLBACK_CHOICE Fallback choice is not a valid dumping area. Skipping it
Explanation The fallback choice is not a valid choice for core dumps.
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-6-SPARSE_CORE_DUMP Sparse core dump as [chars]
Explanation The core for the process is sparse dump
Recommended Action No action is required.
Error Message%OS-DUMPER-6-USAGE Usage: [chars] [-h]
Explanation Usage information.
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-6-WORKER_THREAD_BUSY Too many dump request simultaneously
Explanation Too many processes crashes or dump request simultaneously
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-6-WRITE_TEXT_DUMP_FAIL Failed to write to text dump file:[chars]. Error:[chars]
Explanation Failed to write to the text dump file.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-7-BUS_ADRALN Address alignment @ address [hex]
Explanation Signal info
Recommended Action No action is required.
Error Message%OS-DUMPER-7-BUS_ADRERR Accessed BadAddr [hex] at PC [hex]
Explanation Signal info
Recommended Action No action is required.
Error Message%OS-DUMPER-7-CORE_FILE_OPEN_FAILED Dump to path [chars] fails. Error: [chars]
Explanation Could not open a file to dump core.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-7-DLL_INFO [chars] [hex] [hex] [hex] [hex] [dec]
Explanation Dll information for the process being dumped
Recommended Action No action is required.
Error Message%OS-DUMPER-7-DLL_INFO_HEAD DLL path Text addr. Text size Data addr. Data size Version
Explanation Heading for dll info being printed
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-7-DUMP_REQUEST Dump request for process [chars] dump attribute [hex]
Explanation The information message for debug use.
Recommended Action No action is required.
Error Message%OS-DUMPER-7-FLT_STACK Failed to map stack @ PC [hex]
Explanation Signal info
Recommended Action No action is required.
Error Message%OS-DUMPER-7-INSTALL_PKG [chars] V [chars][[chars]] [chars] at [chars] [chars]
Explanation Active installed packages
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-7-INSTALL_PKG_SHOW_FAILED active installed packages show failed: [chars]
Explanation Install manager might have died
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-7-MKDIR_FAILED mkdir for path [chars] failed, error: [chars]
Explanation Something wrong
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-7-NO_FREE_SPACE_INFO No space information available
Explanation Something wrong
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-DUMPER-7-REGISTERS_INFO [chars]
Explanation This is the register contents at the time of the crash for the crashed process.
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-7-SIGBUS_INFO Thread [dec] received SIGBUS
Explanation Signal info
Recommended Action No action is required.
Error Message%OS-DUMPER-7-SIGEMT Thread [dec] received Mutex deadlock signal
Explanation Signal info
Recommended Action No action is required.
Error Message%OS-DUMPER-7-SIGILL Thread [dec] received SIGILL, accessed BadAddr [hex] at PC [hex] : [chars]
Explanation Signal info
Recommended Action No action is required.
Error Message%OS-DUMPER-7-SIGNAL_NUMBER Thread [dec] received SIGNAL [dec], si code [dec], si errno [dec]
Explanation Signal info
Recommended Action No action is required.
Error Message%OS-DUMPER-7-SIGSEGV Thread [dec] received SIGSEGV
Explanation Signal info
Recommended Action No action is required.
Error Message%OS-DUMPER-7-TRACE_BACK #[dec] [hex]
Explanation Trace back
Recommended Action 'No action is required.'
EVM Messages
Error Message%OS-EVM-1-CORRUPT_MLIST [chars]: attached-message list corrupted -- [[dec],[dec]] overlaps [[dec],[dec]]
Explanation An Event Manager list of attached messages was found to be corrupt.
Recommended Action This is an internal error and should be reported to TAC. A memory dump should be taken (to assist TAC) and the application should be restarted.
Error Message%OS-EVM-1-FLAGS [chars]: invalid event manager flags -- [hex]
Explanation An Event Manager call was made with an invalid flag argument.
Recommended Action This is an internal error and should be reported to TAC. The application process making the call has corrupted data or some other internal error. The application should be restarted; if that fails, the router should be rebooted.
Error Message%OS-EVM-1-HANDLE [chars]: invalid event manager handle -- [hex]
Explanation An Event Manager call was made with an invalid event manager handle.
Recommended Action This is an internal error and should be reported to TAC. The application process making the call has corrupted data or some other internal error. The application should be restarted; if that fails, the router should be rebooted.
Error Message%OS-EVM-1-QSM [chars]: call to qsm_add_service([chars], [chars]) failed -- [chars]
Explanation A call to the QSM API failed. The server was not able to advertise itself.
Recommended Action This is an internal error and should be reported to TAC. The application process making the call has corrupted data or some other internal error. The application should be restarted; if that fails, the router should be rebooted.
Error Message%OS-EVM-1-SIGPATCH [chars]: unexpected signal [dec] received
Explanation The Event Manager signal handler should never be invoked directly.
Recommended Action This is an internal error and should be reported to TAC.
Error Message%OS-EVM-1-TIMEOUT [chars]: timeout call failed, handle [hex]
Explanation An Event Manager blocking call was made with an invalid timeout specification.
Recommended Action This is an internal error and should be reported to TAC. The application process making the call has corrupted data or some other internal error. The application should be restarted; if that fails, the router should be rebooted.
Error Message%OS-EVM-4-FATTACH [chars]: event_file_attach failure for fd [dec], cond [dec]: [chars].
Explanation An ionotify call to request file-state notification failed.
Recommended Action This is an internal error and should be reported to TAC. The server process for the failed fd has died or there is a connectivity failure. If it can be determined which server failed, it and the application with the ionotify error should be restarted. If that fails, the router should be rebooted.
Error Message%OS-EVM-4-RMCONTEXT [chars]: could not allocate memory for Resource Manager context
Explanation The Event Manager could not allocate memory to construct a Resource Manager context when delivering an RM message.
Recommended Action Either some process is using too much memory or there is not enough physical memory available in the router. Determine if an application is misbehaving by checking the amount of memory allocated to each application and noting whether one is unusually large. If there are no misbehaving applications, memory should be added to the router.
Error Message%OS-EVM-4-SIGACTION [chars]: could not install signal handler for signal [dec] [chars]
Explanation The Event Manager signal thread must install a signal handler for each signal that it is watching.
Recommended Action This is an internal error and should be reported to TAC.
Error Message%OS-EVM-4-SIGHEAP [chars]: could not allocate memory to deliver signal [dec] [attempt [dec] of [dec]]
Explanation The Event Manager signal thread could not allocate memory needed to deliver a signal message to the Event Manager message channel. The Event Manager will try to work around the problem by sending itself the same signal a few times.
Recommended Action Either some process is using too much memory or there is not enough physical memory available in the router. Determine if an application is misbehaving by checking the amount of memory allocated to each application and noting whether one is unusually large. If there are no misbehaving applications, memory should be added to the router.
Error Message%OS-EVM-7-EVMDESTROY Attempt to destroy EVM: [pointer] (registered for disconnect events) will be ignored
Explanation A call to the destroy the EVM was ignored, since there were other EVMs around.
Recommended Action This is an internal error and should be reported to TAC. The application process is making a call to event_manager_destroy while it still had other EVMs. Destroying the EVM will result in the process not receiving notifications when its clients go away.
Error Message%OS-EVM-7-HEAP [chars]: could not allocate from heap
Explanation An Event Manager library function was not able to obtain HEAP memory space.
Recommended Action Either some process is using too much memory or there is not enough physical memory available in the router. Determine if an application is misbehaving by checking the amount of memory allocated to each application and noting whether one is unusually large. If there are no misbehaving applications, memory should be added to the router.
FILECOPY_LIB Messages
Error Message%OS-FILECOPY_LIB-3-BAGDECODE An attempt to decode a filecopy bag failed when [chars]
Explanation An attempt to decode a filecopy bag failed. This may be due to like low memory. You may need to free some resources from other processes if the system is running low on memory - if freeing up resources does not fix the problem, please contact your customer support representative and file a bug against the infra-filecopy-srv component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-FILECOPY_LIB-3-BAGENCODE An attempt to encode a filecopy bag failed when [chars]
Explanation An attempt to encode a filecopy bag failed. This may be due to like low memory. You may need to free some resources from other processes if the system is running low on memory - if freeing up resources does not fix the problem, please contact your customer support representative and file a bug against the infra-filecopy-srv component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-FILECOPY_LIB-3-NOMEM Insufficient memory to [chars]
Explanation No memory to perform bag operations.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-FILECOPY_LIB-3-NULLARGS Null parameter passed to function when [chars]
Explanation A NULL parameter was passed to a function expecting non-NULL parameters. This will result in the operation being performed failing. If this error occurs, please capture any contextual information from the CLI, and email it to your customer support representative. A bug should be filed against the infra-filecopy-srv component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-FILECOPY_LIB-3-SYSDBFAIL A sysdb operation failed when [chars]
Explanation An attempt to retrieve (or set) a sysdb item or list failed. This could be a transient problem that may be fixed by restarting the filecopy_process - note well that restarting this process could result in loss of data. If restarting the process does not solve this problem, please capture any contextual information from the CLI, contact your customer support representative and file a bug against the infra-filecopy-srv component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FILECOPY Messages
Error Message%OS-FILECOPY-3-BAGREGFAILED Failed to register filecopy bags during startup of filecopy_process
Explanation The filecopy_process was unable register its bags during startup. This will result in the filecopy_process being terminated. The problem may be due to a transient condition like low memory. Try restarting the filecopy_process - you may do this by creating a new ccCopyEntry row in the CISCO-CONFIG_COPY-MIB. If the problem persists after a few tries, please open a bug and include the release number for the infra/filecopy/server component, the logged error message containing the traceback and a copy of the running-configuration at the time of the 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%OS-FILECOPY-3-EVMCREATE Could not create event manager for the filecopy_process
Explanation The filecopy_process was unable to create an event manager. The filecopy_process will shut down since it cannot receive any events. Try restarting the process - if the error continues, contact customer support with the error message and associated 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.
Error Message%OS-FILECOPY-3-NOMEM Insufficient memory to [chars]
Explanation No memory to perform edm or bag operations.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-FILECOPY-3-SIGATTACH Could not attach a handler function for the signal [chars]
Explanation The filecopy_process was unable attach a handler for a signal. This could affect cleanup of open connections or allocated resources during shutdown, which could affect the filecopy_process' ability to restart in the future. The filecopy_process will attempt to shutdown in the hope that this problem is transient, and that a future attempt to start it will succeed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-FILECOPY-3-SYSDBBIND Could not bind with SysDB
Explanation The filecopy_process was unable to bind with sysdb. This means the process will be unable to communicate with its clients. Hence the filecopy_process will shut itself down.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-FILECOPY-4-DEBUGINIT Could not register for debug notifications
Explanation The filecopy_process was unable to register for debug notifications. If you have turned on debugging for this process, it will have no effect. However, the rest of the filecopy_process functionality should still be available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-FILECOPY-4-NOTIFFAIL Failed to send a filecopy notification - [chars]
Explanation The filecopy process failed to send a notification to its clients about a state-transition for a copy request. Users may find the reported duration of a copy operation to be quite large as a result, depending on how long it takes for a client to poll the filecopy_process to see if a state change occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-FILECOPY-4-SYSDBUNBIND Could not unbind with SysDB
Explanation The filecopy_process was unable to unbind from sysdb when shutting down. This may result in a failure to re-register with sysdb when the process is restarted later.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FSM Messages
Error Message%OS-FSM-4-ANOMALY [chars]
Explanation A SW exception occurred in FSM 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.
GSP_NOTIF Messages
Error Message%OS-GSP_NOTIF-3-msg_failed Failure in [chars] at Line [dec]. Function [chars] returned Error [chars]
Explanation The internal communication channel is broken.
Recommended Action Must restart the process.
gsp Messages
Error Message%OS-gsp-3-BAD_GRP_DELETE [chars]: sgrp-grp for group [dec] ([chars]) still exists after group is deleted
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%OS-gsp-3-CONDVAR_OP_FAILED [chars]:[dec] condvar op [chars] failed [chars]
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%OS-gsp-3-ERROR gsp error [chars].
Explanation --
Recommended Action 'No action is required.'
Error Message%OS-gsp-3-FILE_OP_FAILED [chars]: File op [chars] failed. : [chars]
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%OS-gsp-3-GET_MEM_FAILED [chars]:[dec] gs_get_mem or malloc failed (other [dec])
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%OS-gsp-3-INCORRECT_RSI Inconsistent node-id received, expect:[hex], got [hex]:[dec] for group [dec]
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%OS-gsp-3-LTRACE_INIT Ltrace init for file [chars] failed [chars]
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%OS-gsp-3-MSG_ENQUEUE_ERROR Process [chars] (pid [dec]) not picking up messages, [dec] msgs dropped. [dec] msgs pending
Explanation --
Recommended Action 'No action is required.'
Error Message%OS-gsp-3-MUTEX_OP_FAILED [chars]: Mutex op [chars] failed on mutex [chars] ([chars]) : [chars]
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%OS-gsp-3-PTHREAD_OP_FAILED [chars]:[dec] pthread op [chars] failed [chars]
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%OS-gsp-3-TRACEBACK gsp traceback [chars]
Explanation --
Recommended Action 'No action is required.'
Error Message%OS-gsp-3-UPDATE_ADDR Can not add node [hex] to group [chars](gid [dec]), error [dec]
Explanation --
Recommended Action 'No action is required.'
Error Message%OS-gsp-7-FUNC_ERROR Function [chars] returned error: [chars]
Explanation --
Recommended Action 'No action is required.'
Error Message%OS-gsp-7-MSG_ENQUEUE_WARN Process [chars] (pid [dec]) not picking up messages, [dec] msgs pending
Explanation --
Recommended Action 'No action is required.'
Error Message%OS-gsp-7-RCV_OWN_MSG Received own mcast on gid [dec]
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.'
INFRA_CERR Messages
Error Message%OS-INFRA_CERR-7-CORRUPT [chars]: corrupted data structured detected at line [dec]
Explanation The infrastructure library detected a corrupt data structure while performing internal checks.
Recommended Action Run diagnostics to determine if this is a result of a hardware problem. If the problem reoccurs, a memory dump should be taken to assist TAC.
Error Message%OS-INFRA_CERR-7-NOMEM [chars]: could not allocate memory ([dec] bytes requested): [chars]
Explanation The infrastructure library was unable to allocate memory from the system for an internal data structure.
Recommended Action Check to see if sufficient memory resources remain for normal operations. Add memory if necessary. Verify the installation of the infrastructure library. Re-load if required.
Error Message%OS-INFRA_CERR-7-PTHREADKEY [chars]: could not create thread key: [chars]
Explanation The infrastructure library was unable to obtain a thread key for thread private data storage.
Recommended Action Check to see if sufficient memory resources remain for normal operations. Add memory if necessary.
Error Message%OS-INFRA_CERR-7-REGISTER [chars]: could not register the infrastructure specific structured error messages: [chars]
Explanation The infrastructure library was unable to register its infrastructure specific condition codes. Condition messages from the infrastructure library are likely to be degraded.
Recommended Action Check to see if sufficient memory resources remain for normal operations. Add memory if necessary. Verify the installation of the infrastructure library. Re-load if required.
Error Message%OS-INFRA_CERR-7-SETSPECIFIC [chars]: could not set threadspecific data pointer for key [hex]: [chars]
Explanation The infrastructure library was unable to set a threadspecific data pointer for thread private data storage.
Recommended Action Check to see if sufficient memory resources remain for normal operations. Add memory if necessary.
INIT Messages
Error Message%OS-INIT-4-INSTALL_TIMEOUT installation still not done after [dec] seconds, wait continuing
Explanation The pakage installation sync did not complete in time. This could indicate that the node is hung and may require a reset.
Recommended Action Collect system log information. No action is required.
Error Message%OS-INIT-7-INSTALL_READY total time [dec].[dec] seconds
Explanation The pakage installation software is now ready. This is not an error.
Recommended Action No action is required.
Error Message%OS-INIT-7-INSTALL_THRESHOLD_EXCEEDED package install time threshold of [dec] seconds has been exceeded, continuing
Explanation An unexpected condition encountered. This is not necessarily an error.
Recommended Action Collect system log information. No action is required.
Error Message%OS-INIT-7-MBI_STARTED total time [dec].[dec] seconds
Explanation The MBI processes have all been started. This is not an error.
Recommended Action No action is required.
Error Message%OS-INIT-7-MBI_THRESHOLD_EXCEEDED MBI bootup exceeded threshold of [dec] seconds, continuing
Explanation An unexpected condition encountered. This is not necessarily an error.
Recommended Action Collect system log information. No action is required.
KD_MBUS Messages
Error Message%OS-KD_MBUS-1-EVENT_MGR_CREATE_FAILED [chars]: can't create event manager. [chars]
Explanation Failed to create event manager for the 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%OS-KD_MBUS-1-FLASH_FULL No space in bootflash to write. Size of data: [dec], Data: [chars]
Explanation Bootflash is full
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-KD_MBUS-3-COMPRESS_INIT_FAILED Compress initialization failed. Probably low memory
Explanation Could not initalize data structure for compression
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-KD_MBUS-3-CORE_FILE_OPEN_FAILED Could not open [chars]. Error: [chars]
Explanation Open of file failed
Recommended Action Check if valid file location and filename
Error Message%OS-KD_MBUS-3-DEBUG_INIT_FAILED [chars]
Explanation Debug init 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%OS-KD_MBUS-3-FAIL_DEBUG_REG [chars]: Can't connect to configuration, [chars]
Explanation DUMPER debugging service register to sysdb failed.
Recommended Action Check the existence of the Sysdb service. The system is supposed to re-register if the Sysdb service is available.
Error Message%OS-KD_MBUS-3-SYSDB_BIND_FAILURE Unable to bind to [chars]. Error: [chars]
Explanation Could not connect to sysdb
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-KD_MBUS-3-SYSDB_GET_FAILURE Unable to get item [chars]. Error: [chars]
Explanation Item possible not in sysdb
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-KD_MBUS-3-WRITE_FAILED Write of size [dec] to fd [dec] failed. Error: [chars]
Explanation Most probably some problem with the file system
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-KD_MBUS-4-SYSDB_SET_FAILURE Could not set [chars]. [chars]
Explanation Could not set sysdb item.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-KD_MBUS-6-CORE_DUMP_NOT_CONFIGURED Core dump failed since dump location not configured
Explanation Core dump location needs to be configured before dumping
Recommended Action Configure core dump location using exception kernel command
LGROUP Messages
Error Message%OS-LGROUP-3-ERROR [chars]: Operation [chars] failed : [chars]
Explanation The specified operation 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.
LIBSYSMGR Messages
Error Message%OS-LIBSYSMGR-3-ERR Unsupported API [chars] called by process [chars]
Explanation The call is not supported during MBI boot.
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%OS-LIBSYSMGR-3-INST_ERR [chars]: software upgrade error ([dec], [dec])
Explanation Inconsistent file count between given and in the file list.
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%OS-LIBSYSMGR-3-INTERNAL [chars]: sysmgr function [chars]() failed: [chars]
Explanation The client library has failed a sysmgr function.
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%OS-LIBSYSMGR-3-NOMEM [chars]: failed to malloc [unsigned int] bytes
Explanation The client library has failed to allocate the required amount of memory.
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%OS-LIBSYSMGR-3-PARSE [chars]: parse error: [chars]
Explanation An error was encountered whilst parsing the argument vector for a spawn script operation.
Recommended Action No action is required.
Error Message%OS-LIBSYSMGR-3-SYSCALL [chars]: [chars]() failed: [chars]
Explanation The client library has failed a system call.
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%OS-LIBSYSMGR-6-INFO [chars]: Node restart requested by pid [dec]
Explanation Informational only.
Recommended Action No action is required.
Error Message%OS-LIBSYSMGR-6-SCRIPT_TIMEOUT Script [chars] exceeded allotted time of [dec] sec and was killed.
Explanation Script exceeded allotted time.
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.
LTRACE_SDT_SHOW Messages
Error Message%OS-LTRACE_SDT_SHOW-4-EXTEND_FAIL Extending the trace string data to [dec] traces ran out of memory
Explanation The show decode helper library attempted to extend its database of decode trace string data and was unable to do so. Any trace using this string may not be printable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LTRACE_SDT_SHOW-4-GROUP_CALLOC Unable to get space for group header data
Explanation The show decode helper library isolates string trace data into group keyed by trace name and nodeid. The library was unable to obtain memory for one of this group items. Because of this, the library will not be able to print out data from the given trace name/node grouping.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LTRACE_SDT_SHOW-4-NODE_PRINT Unable to decode nodeid because [chars]
Explanation The show helper was unable to decode a text name for the node id a given trace block containing string data came from. As a result of this, the given trace will not be printable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LTRACE_SDT_SHOW-4-STR_CALLOC Unable to get string data for trace [dec] of length [dec]
Explanation The show decode helper library breaks up string data for mesasages into single trace buffers and reassembles them. There was not enough memory to create the string space to hold the data. Any trace using this string may not be printable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LTRACE_SDT_SHOW-4-STR_SEQ Sequence of string data on trace [dec] was [dec] instead of the expected [dec]
Explanation The show decode helper library breaks up string data for mesasages into single trace buffers and reassembles them. While putting the trace data back together, the sequence received was not the expected next sequence. Any trace using this string may not be printable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LTRACE_SDT_SHOW-4-TRACE_FIND The message decode locate for '[chars]' failed because:[chars]
Explanation The show decode helper library isolates string and trace data to a given trace name and node. The attempt to find this in the lookup tree failed for the above reason. Any trace using this string may not be printable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LTRACE_SDT_SHOW-4-TRACE_INSERT The message decode insert for '[chars]' failed because:[chars]
Explanation The show decode helper library isolates string and trace data to a given trace name and node. The attempt to insert this into the lookup tree failed for the above reason. Any trace using this string may not be printable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LTRACE_SDT Messages
Error Message%OS-LTRACE_SDT-4-BTREE_FIND [chars]: The message storage optimization failed in btree lookup for '[chars]':[chars]
Explanation The internal message storage space optimizer failed to lookup the string being stored. This is not a critical, since the string will still be stored, however it does possibly indicate a lower level memory corruption or other problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LTRACE_SDT-4-BTREE_INSERT [chars]: The message storage optimization failed in btree insert for '[chars]':[chars]
Explanation The internal message storage space optimizer failed to insert the string being stored. This is not a critical, since the string will still be stored, however it does possibly indicate a lower level memory corruption or other problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LTRACE Messages
Error Message%OS-LTRACE-3-ERROR [chars] failed: [chars]
Explanation Required functionality failed or returned an error
Recommended Action Contact support.
Error Message%OS-LTRACE-7-DEBUG [chars] [chars] [chars]
Explanation Internal debugging message.
Recommended Action Informational only.
LWMESS Messages
Error Message%OS-LWMESS-7-CORRUPT_CLI [chars]: Corrupted channel list for [chars]. Memory lost
Explanation A corrupt memory area was discovered in an internal data structure
Recommended Action This is an internal error and should be reported to TAC. Try re-starting the offending application. If that does not work, a memory dump should be taken (to assist TAC) and the router should be rebooted.
Error Message%OS-LWMESS-7-CORRUPT_CLI_SKIP [chars]: Corrupted channel list for [chars]. Iteration Skipped.
Explanation A corrupt memory area was discovered in an internal data structure. A function that was searching the open connection list was not able to process all open connections.
Recommended Action This is an internal error and should be reported to TAC. Try re-starting the offending application. If that does not work, a memory dump should be taken (to assist TAC) and the router should be rebooted.
Error Message%OS-LWMESS-7-INVALID_MSG_ERROR_CODE Invalid msg_error errcode: [dec]
Explanation The msg_error error codes are limited to errno values. Any error values with high bits set (such as -1) are invalid.
Recommended Action Report this message to TAC.
Error Message%OS-LWMESS-7-LOCK_CONN [chars]: Could not lock conn_list for [chars]: [chars]
Explanation The mutex for the channel connection list could not be held
Recommended Action This is an internal error and should be reported to TAC. Try re-starting the offending application. If that does not work, a memory dump should be taken (to assist TAC) and the router should be rebooted.
Error Message%OS-LWMESS-7-UNLOCK_CONN [chars]: Could not unlock conn_list for [chars]: [chars]
Explanation The mutex for the channel connection list could not be released
Recommended Action This is an internal error and should be reported to TAC. Try re-starting the offending application. If that does not work, a memory dump should be taken (to assist TAC) and the router should be rebooted.
MEMLOG Messages
Error Message%OS-MEMLOG-3-ERRCHECK Invalid error check value: [hex]
Explanation An unexpected value was found in the error check.
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%OS-MEMLOG-3-FREE A NULL pointer was passed to free
Explanation An attempt was made to free a null pointer
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%OS-MEMLOG-3-HEADER Invalid [chars] value in header: [hex]
Explanation An unexpected value was found in the header. This might indicate a buffer overflow
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%OS-MEMLOG-3-MALLOC Memory allocation failed
Explanation A call to malloc failed.
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%OS-MEMLOG-3-MEMALIGN Attempt to use unsupported function: memalign()
Explanation This function is not supported.
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%OS-MEMLOG-3-SIGERR Received unknown signal value [unsigned int]
Explanation An unexpected signal value was received.
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%OS-MEMLOG-3-TOOBIG Attempt to allocate more than 16MB using [chars]()
Explanation A process attempted to malloc more than the maximum size of 16MB
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.
MEMPOOL_EDM Messages
Error Message%OS-MEMPOOL_EDM-1-EVENT_BLOCK_ERROR event_block error -- [chars]
Explanation Error during event block
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-MEMPOOL_EDM-1-SYSDB_REGISTRATION_FAILURE Sysdb registration for [chars] failed. Error: [chars]
Explanation Sysdb registration failure
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-MEMPOOL_EDM-3-EVENT_MGR_CREATE_FAILED Can't create event manager. [chars]
Explanation Failed to create event manager for the 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%OS-MEMPOOL_EDM-3-MALLOC_FAILED Malloc failed
Explanation Memory running low
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%OS-MEMPOOL_EDM-3-SYSDB_BIND_FAILURE Unable to bind to [chars]. Error: [chars]
Explanation Could not connect to sysdb
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
MGII_API Messages
Error Message%OS-MGII_API-2-INFRA_FAIL [chars]: [chars] failed rc=[chars]([dec])
Explanation An error occurred while processing an infrastructure service request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-MGII_API-3-ASYNC_ERR Asynchronous error: [chars]
Explanation 'An unhandled asynchromous error occurred in the MGII API'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-MGII_API-7-ASYNC_WAR Warning: [chars]
Explanation 'A recoverable error condition occurred in the MGII API'
Recommended Action No action is required.
NRS_LIB Messages
Error Message%OS-NRS_LIB-3-ASYNC_HANDLER_FAILED [chars]: error attaching async handler: [chars]
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%OS-NRS_LIB-3-ASYNC_INIT_FAILED [chars]: async_nrs_init failed with Error : [dec]
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%OS-NRS_LIB-3-BAD_GROUP [chars]: no such group, gid [dec]
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%OS-NRS_LIB-3-BAD_MSG_TYPE [chars]: bad message type [dec]
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%OS-NRS_LIB-3-BAD_REPLY [chars]-I-replying to a non-block sync msg
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%OS-NRS_LIB-3-CONNECT_FAILED [chars]: ### failed to connect to [chars]
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%OS-NRS_LIB-3-CONNECT_GSP_FAILED [chars]: error connecting to GSP: [chars]
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%OS-NRS_LIB-3-DEF_SYNC_HANDLER_FAILED [chars]: error attaching lib's default sync handler: [chars]
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%OS-NRS_LIB-3-ERROR [chars]: error: [hex]([chars])
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%OS-NRS_LIB-3-EVENT_ASYNC_ATTACH_FAILED [chars]: error async attach all failed: [chars]
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%OS-NRS_LIB-3-EVENT_FILE_ATTACH_FAILED [chars]: event_file_attach call failed: [chars]
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%OS-NRS_LIB-3-GSP_FAILURE [chars]-E-GSP failure connection lost...
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%OS-NRS_LIB-3-GSP_MSG_RCV_FAILURE [chars]: error retrieving msg from GSP: [chars]
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%OS-NRS_LIB-3-MALLOC_FAILED [chars]: malloc failed
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%OS-NRS_LIB-3-MEMORY Failed to malloc [unsigned int] bytes
Explanation The client library has failed to aquire the required amount of memory.
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%OS-NRS_LIB-3-MSG_CHAN_DISCONNECT_FAIL [chars]: msg_chan_disconnect failed [chars]
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%OS-NRS_LIB-3-MSG_GET_CONN_FAILED [chars]: msg_get_conn call failed: [chars]
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%OS-NRS_LIB-3-MSG_SEND_ERR [chars] msg_send error ERRNO: [dec]::[chars]
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%OS-NRS_LIB-3-MUTEX_OP_FAILED [chars]: Mutex op [chars] failed on mutex [chars]: [chars]
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%OS-NRS_LIB-3-NO_PRIV_MSG_HANDLER [chars]: no private msg handler!
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%OS-NRS_LIB-3-PTHREAD [chars] : failed with Error [dec]
Explanation pthread_XXX call has failed
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%OS-NRS_LIB-3-REG_ERROR [chars]-E-[chars]
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%OS-NRS_LIB-3-SEND_FAILED [chars]: failed to [chars]: [hex]([chars])
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%OS-NRS_LIB-3-SYNC_RESP_ERR [chars] error sending SYNC_RESPONSE: [chars]
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.'
nrs Messages
Error Message%OS-nrs-2-USAGE Incorrect arguments: Usage: [chars] [svr_threads]
Explanation Incorrect command line parameters were passed to the nrs server, and so it failed to start.
Recommended Action Check the startup arguments passed to nrs server. A default configuration will be used if no parameters are passed. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-nrs-3-CHKPT_ATTR_CREATE checkpoint create failed for attr [dec], handle [hex], err [hex]
Explanation chkpt_create api failed
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%OS-nrs-3-CHKPT_ATTR_SAVE checkpoint save failed for attr [hex], handle [hex], err [hex]
Explanation chkpt_save api failed
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%OS-nrs-3-CHKPT_CREATE checkpoint create failed for [chars], handle [hex], name [chars], err [hex]
Explanation chkpt_create api failed
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%OS-nrs-3-CHKPT_DEBUG saved class [chars], handle [hex] to checkpoint table
Explanation chkpt_iterate_* api failed
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%OS-nrs-3-CHKPT_DELETE_BYKEY checkpoint delete failed for table [chars], handle [hex], err [hex]
Explanation chkpt_delete_bykey api failed
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%OS-nrs-3-CHKPT_ITERATE chkpt_iterate_[chars] failed for table [hex], err [hex]
Explanation chkpt_iterate_* api failed
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%OS-nrs-3-CHKPT_ITERATE_NEXT chkpt_iterate_next failed for table [hex], after [dec] iterations, err [hex]
Explanation chkpt_iterate_* api failed
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%OS-nrs-3-CHKPT_REGISTER checkpoint register failed for table [dec], err [hex], [chars]
Explanation chkpt_register api failed
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%OS-nrs-3-CHKPT_RESTORE_ATTR Failed to restore attr, attr [hex], handle [hex] from checkpoint table, err [hex], [chars]
Explanation nrs_chm_chkpt_create_attr api failed
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%OS-nrs-3-CHKPT_RESTORE_CLASS Failed to restore class [chars], handle [hex] from checkpoint table, err [hex], [chars]
Explanation nrs_chm_chkpt_create_class api failed
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%OS-nrs-3-CHKPT_RESTORE_DATA Failed to restore data [chars], handle [hex] from checkpoint table, err [hex], [chars]
Explanation nrs_chm_chkpt_create_data api failed
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%OS-nrs-3-CHKPT_RESTORE_DEBUG restoring from chkpt class [chars], handle [hex], index [hex] to checkpoint table
Explanation chkpt_iterate_* api failed
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%OS-nrs-3-CHKPT_RESTORE_DEBUG_SUCCESS restored from chkpt class [chars], handle [hex], index [hex] to checkpoint table
Explanation chkpt_iterate_* api failed
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%OS-nrs-3-CHKPT_RESTORE_SET Failed to restore set, exp [chars], handle [hex] from checkpoint table, err [hex], [chars]
Explanation nrs_chm_chkpt_create_set api failed
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%OS-nrs-3-CHKPT_SAVE checkpoint save failed for [chars], handle [hex], name [chars], err [hex]
Explanation chkpt_save api failed
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%OS-nrs-3-CHKPT_UNREGISTER checkpoint unregister failed for table [chars], class [chars], err [hex]
Explanation chkpt_unregister api failed
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%OS-nrs-3-ENS_PUBLISH ens_publish call failed [chars]
Explanation ens_publish call has failed.
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%OS-nrs-3-ENS_WRITE ens_write call failed [chars]
Explanation ens_write call has failed.
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%OS-nrs-3-INTERNAL [chars]: rc [hex], [chars]
Explanation The server has either failed a function that expected to succeed, or has got into an inconsistent state.
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%OS-nrs-3-LOCKING Failed to [chars] [chars]. Error [dec]
Explanation The server has either failed to aquire or release a lock.
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%OS-nrs-3-LTRACE_INIT Ltrace init for file [chars] failed [chars]
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%OS-nrs-3-MEMORY Failed to malloc [unsigned int] bytes
Explanation The server has failed to acquire the required amount of memory.
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%OS-nrs-3-NULLARG A NULL pointer was passed as a fn parameter
Explanation A NULL pointer was passed as a fn parameter
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%OS-nrs-3-REGCOMP regcomp failed - error [hex], regex [chars]
Explanation The server has either failed a function that expected to succeed, or has got into an inconsistent state.
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%OS-nrs-3-REGISTER_EXTERNAL_PUBLISH_DIFF_ID trying to create or get data [chars] handle [hex] of class [chars] with previous id [hex] and new id [hex]
Explanation try to register a data with diff id
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%OS-nrs-3-REPLY Failed to send reply to client pid [unsigned int] tid [unsigned int]: rc [hex]
Explanation The server failed to reply to a client request.
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.
NRSUTILS Messages
Error Message%OS-NRSUTILS-3-INTERNAL [chars]: rc [hex]
Explanation The client library has either failed a function that expected to succeed, or has got into an inconsistent state.
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%OS-NRSUTILS-3-MEMORY Failed to malloc [unsigned int] bytes
Explanation The nrs common library has failed to aquire the required amount of memory.
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%OS-NRSUTILS-3-NULLARG A NULL pointer was passed as a fn parameter
Explanation A NULL pointer was passed as a fn parameter
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.
PLACED_LIB Messages
Error Message%OS-PLACED_LIB-2-VECTOR_OVERFLOW Overflow in message vector ([dec] entries used, [dec] available)
Explanation A client was unable to send a message to PlaceD due to encountering an internal error condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_LIB-4-STARTUP_POLICY System placement policy found in [chars]. Policy should be moved to a .placement file.
Explanation PlaceD discovered system placement policy specified in an unsupported format; the policy will not be honored. The system should continue to function correctly, though process placement decisions may be sub-optimal.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLACED_MAIN Messages
Error Message%OS-PLACED_MAIN-2-CHKPT Failed to initialize checkpoint library: [chars]
Explanation PlaceD was unable to initialize the checkpoint library for saving its internal state, and therefore failed to initialize.
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%OS-PLACED_MAIN-2-CLASSES Failed to initialize classes: [chars]
Explanation PlaceD was unable to set up its object classes, and therefore failed to initialize.
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%OS-PLACED_MAIN-2-DLRSC Failed to determine whether running on dLRSC: [chars]
Explanation PlaceD was unable to determine whether it was running on the dLRSC, and therefore failed to initialize.
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%OS-PLACED_MAIN-2-DLRSC_REG Failed to register for dLRSC notifications: [chars]
Explanation PlaceD failed to register for dLRSC change events, and therefore failed to initialize.
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%OS-PLACED_MAIN-2-EVENT_HANDLER Failed to attach event handler to event manager: [chars]
Explanation PlaceD was unable register an event handling for processing received messages, and therefore failed to initialize.
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%OS-PLACED_MAIN-2-EVENT_MGR Failed to create an event manager for channel '[chars]': [chars]
Explanation PlaceD was unable to create an event manager for receiving messages, and therefore failed to initialize.
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%OS-PLACED_MAIN-2-PROC_READY Failed to signal end of initialization: [chars]
Explanation PlaceD was unable to inform SysMgr that it had completed its initialization.
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%OS-PLACED_MAIN-2-QSM_CHAN Failed to publish QSM channel '[chars]' (rendezvous '[chars]'): [chars]
Explanation PlaceD was unable to publish a channel for receiving messages, and therefore failed to initialize.
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%OS-PLACED_MAIN-2-QSM_RENDEZ Failed to get rendezvous name: [chars]
Explanation PlaceD was unable to get a rendezvous name for publishing the message channel, and therefore failed to initialize.
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%OS-PLACED_MAIN-2-SYSDB Failed to do a [chars] with SysDB at '[chars]': [chars]
Explanation PlaceD was unable to perform a critical SysDB operation, and therefore failed to initialize.
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%OS-PLACED_MAIN-2-SYSDB_VRFN_INIT Failed to initialize SysDB verification functions handle: [chars]
Explanation PlaceD was unable to initialize its SysDB verification functions handle, and therefore failed to initialize.
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%OS-PLACED_MAIN-2-TRACE_BUFFERS Failed to initialize trace buffers: [chars]
Explanation PlaceD was unable to set up its trace buffers, and therefore failed to initialize. This almost certainly means there was insufficient memory available for placed to function correctly.
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%OS-PLACED_MAIN-3-BACKUP_DLRSC Unable to determine new backup dLRSC: [chars]
Explanation PlaceD was notified that the backup dLRSC has changed, but was unable to determine the new location. This means that it is unable to direct its checkpoint updates to that location, and so the system may be in an unstable state if the currently active dLRSC fails.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-3-BACKUP_DLRSC_REG Failed to register for backup dLRSC notifications: [chars]
Explanation PlaceD failed to register for backup dLRSC change events, and therefore will not be able to mirror its checkpoint data to the backup location.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-3-CHKPT_TARGET Unable to set checkpoint target to location [chars]: [chars]
Explanation PlaceD tried to direct its remote checkpoint updates to the specified location (the backup dLRSC) but encountered an error. This may mean that the system will be in an unstable state if the currently active dLRSC fails.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-3-DLRSC_NOT Failed to get event type from dLRSC notification: [chars]
Explanation PlaceD couldn't get the event type from a dLRSC notification it received, and therefore may no longer be aware whether or not it is running on the dLRSC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-3-INIT_COMPLETE Unable to record that initialization is complete: [chars]
Explanation PlaceD encountered a problem when recording the fact that it has successfully initialized for the first time since this logical router powered up. This means that problems may be encountered when PlaceD restarts, such as after a dLRSC migration.
Recommended Action In the short term this alone does not indicate that the system will operate incorrectly. It is however diagnostic of some underlying problem, and it is possible that the system will operate incorrectly after the placement daemon is forced to restart. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-4-DBG_ON Failed to switch on debugging flag '[chars]': [chars]
Explanation PlaceD was unable to switch on one of its debugging flags whilst initializing, but ignored the error and continued.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-4-DBG_REG Failed to register for debug notification: [chars]
Explanation PlaceD was unable to register for notification of its debugging flag settings. PlaceD ignored the error and continued.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-4-EVENT_BLOCK Error waiting for message - ignoring: [chars]
Explanation An error occured whilst PlaceD was waiting for a messages, PlaceD ignored the error and continued to wait for more messages.
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%OS-PLACED_MAIN-4-UNEXPECTED_REQ Ignoring request type [dec] to non-active PlaceD instance
Explanation An inactive PlaceD instance received a request. Only the instance on the currently active dLRSC should receive any requests.
Recommended Action If this is during a dLRSC migration then it is probably benign, provided no other ill effects are seen. Otherwise it probably indicates a problem in the underlying infrastructure, such as QSM. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-4-UNKNOWN_MSG Ignoring unrecognized message (comp ID: [dec], msg no: [dec])
Explanation PlaceD did not recognise a message it received, and therefore ignored it.
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%OS-PLACED_MAIN-4-UNKNOWN_REQ Ignoring unrecognized request ([dec])
Explanation PlaceD did not recognise a request it received, and therefore ignored it.
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%OS-PLACED_MAIN-6-DLRSC_CHANGED The active dLRSC has changed, so the previously active placed is transitioning to inactive state
Explanation The active dLRSC changed, so the process placement daemon running on the previously active dLRSC has changed to inactive state, so that the instance on the newly active dLRSC can take over without problems.
Recommended Action This indicates an unusual situation, but if there are no other indications of system problems then this is probably benign.
Error Message%OS-PLACED_MAIN-6-DUMP_CORE PlaceD is performing a voluntary core dump because an unexpected situation has arisen. This is not a crash, but does indicate there was a problem.
Explanation The placement daemon has encountered an unexpected internal situation. If there are no further signs of a problem then it is reasonably safe to assume that the system has recovered.
Recommended Action Please check with your support representative, and if possible provide the core file for further examination.
PLACED_NODES Messages
Error Message%OS-PLACED_NODES-2-NO_NODES Empty or badly damaged LR inventory - assuming only [chars]%s[chars] present as a fallback strategy
Explanation There were no RP or DRP cards reported in the inventory for process placement. This is an error (the process placement daemon must be running on one such card if nothing else) and will have a very detrimental effect on process placement. The system will limp on as best it can, assuming the only RP/DRP in the LR is that on which the process placement daemon is itself running, and should the inventory problem be resolved then the system will then adjust accordingly automatically.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-2-NODEID Failed to obtain ID of current location: [chars]
Explanation PlaceD was unable to determine the ID of the location at which it was running, and therefore failed to initialize.
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%OS-PLACED_NODES-3-ACTIVE_LIST Failed to get active-standby [chars] list: [chars]
Explanation PlaceD couldn't get the list of active-standby RP or DRP pairs, and therefore may not be able to determine which location from a pair is active.
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%OS-PLACED_NODES-3-LR_INVEN Failed to get [chars] from the LR inventory: [chars]
Explanation PlaceD couldn't retrieve the specified information from the LR inventory it received, and therefore may not have sufficient location information to place processes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-3-LR_NOT Failed to get [chars] from LR notification: [chars]
Explanation PlaceD couldn't retrieve the specified information from an LR notification it received, and therefore may no longer have up-to-date location 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%OS-PLACED_NODES-3-LR_REG Failed to register for LR notifications: [chars]
Explanation PlaceD couldn't register for LR notifications, and may therefore be unable to maintain up-to-date location 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%OS-PLACED_NODES-3-MEMORY Insufficient memory for object representing location [chars] (partner [chars]), location will not be used for placement
Explanation An object to represent the location could not be created (probably due to insufficient memory). PlaceD will not be able to place processes at the location.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%OS-PLACED_NODES-4-LR_INVEN_ENTRY Failed to get [chars] from the LR inventory entry [dec]: [chars]
Explanation PlaceD couldn't retrieve the specified information from an entry in the LR inventory, and therefore ignored the entry.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-4-LR_INVEN_NODETYPE Ignoring entry [dec] in the LR inventory entry since location is of unknown type ([dec])
Explanation PlaceD didn't recognise the location type in an entry in the LR inventory, and therefore ignored the entry.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-4-PARTIAL Received partial list of locationss, placement will initially use this subset
Explanation PlaceD received a partial list of locations at boottime. Initially, these locations will be used for placing processes. Other nodes will be used later when they become available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-5-NOT_RUNNING LR inventory indicated that state of location [chars] was [dec], using state [dec] (RUNNING) instead
Explanation The LR inventory showed that the location at which PlaceD was running was not in the running state. PlaceD assumed this was erroneous.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLACED_PLACE Messages
Error Message%OS-PLACED_PLACE-2-TIMER Unable to create [chars] timer
Explanation PlaceD was unable to create a necessary timer, and therefore failed to initialize.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%OS-PLACED_PLACE-2-TIMER_GROUP Unable to create [chars] timer group
Explanation PlaceD was unable to create the group for storing a timer, and therefore failed to initialize.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%OS-PLACED_PLACE-3-ALGO Placement algorithm failed: [chars]
Explanation An error occured in the algorithm used by PlaceD to determine the optimal placement.
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%OS-PLACED_PLACE-3-ALGO_RERUN Unable to determine optimal placement after running algorithm [unsigned int] times
Explanation PlaceD was unable to place one or more processes on any of the available nodes in the system.
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%OS-PLACED_PLACE-4-CANT_START Unable to start program [chars]%s[chars] since there is insufficient cpu or memory capacity
Explanation Starting the new program would overflow the watermarks for the cpu or memory capacity currently available.
Recommended Action Options include adding or unpairing a DRP, deconfiguring some features, or increasing the watermarks configured by placement { cpu | memory } maximum. One can also specify particularly important or disposable processes via configuring large or small existence affinities if so desired.
Error Message%OS-PLACED_PLACE-4-KILLING Killing program [chars]%s[chars] since there is insufficient cpu or memory capacity for all configured processes
Explanation There is insufficient cpu or memory capacity for all configured placeable processes.
Recommended Action Options include adding or unpairing a DRP, deconfiguring some features, or increasing the watermarks configured by placement { cpu | memory } maximum. One can also specify particularly important or disposable processes via configuring large or small existence affinities if so desired.
Error Message%OS-PLACED_PLACE-4-LISTEN Unable to listen for multicast messages: [chars] ([chars])
Explanation PlaceD is unable to register to receive multicast messages. This means that the location which emitted the message will not be able to keep its local copy of the current placement, persisted to non-volatile storage, up to date.
Recommended Action If this is a transient issue then the router will recover. Also, restarting the PlaceD instance that emitted this message will cause it to re-register to receive these updates. If the issue persists: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PLACE-4-LOOKUP_PERSIST Unable to [chars] when looking up persisted placement for [chars]%s[chars]: [chars] ([chars])
Explanation PlaceD hit a problem when looking up the persisted location for a process. This means that it may not be placed on the same location as it was assigned before the most recent reload of the router or LR.
Recommended Action This should not be a service-affecting incident. If this is because the card on which the process was previously placed has been removed, taken administratively down, or been assigned to a different logical router, then this is entirely expected and benign. Otherwise: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PLACE-5-RESTARTING Program [chars]%s[chars] has now been started (was previously unable to run due to insufficient cpu or memory capacity)
Explanation The program was previously prevented from running due to insufficient cpu or memory, but that situation no longer applies and so the program has now been started.
Recommended Action Options to prevent the original inability to run include adding or unpairing a DRP, deconfiguring some features, or increasing the watermarks configured by placement { cpu | memory } maximum. One can also specify particularly important or disposable processes via configuring large or small existence affinities if so desired.
Error Message%OS-PLACED_PLACE-5-SYSDB Unable to [chars] with SysDB at [chars]: [chars]
Explanation PlaceD was unable to register with SysDB for receiving 'placement persist now' actions. This facility will be unavailable.
Recommended Action This is non-critical, and in the absence of other errors, simply means that one facility (triggering persisting of placements by the user) is inoperable.
Error Message%OS-PLACED_PLACE-5-WRITE_PERSIST Unable to [chars] when writing persistent placement: [chars] ([chars])
Explanation The current placement was being persisted to non- volatile storage, but a problem occured. If this condition persists then it is possible that the placement of processes across the available RPs and DRPs will be different after the next router/LR reload.
Recommended Action The write operation will be automatically re-tried later, so if this is a transitory condition then the system will recover completely without intervention. If this is a persistent problem then: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLACED_PROGS Messages
Error Message%OS-PLACED_PROGS-2-CHKPT_REG Failed to register checkpoint table: [chars]
Explanation PlaceD was unable to register a table for checkpointing its program information, and therefore failed to initialize.
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%OS-PLACED_PROGS-2-RECOVER_STATE Failed to recreate state for [chars]%s[chars] when attempting [chars]: [chars]
Explanation PlaceD was unable to recreate its internal representation for the specified program, either from its checkpoint data or from information from SysMgr, and therefore failed to intialize.
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%OS-PLACED_PROGS-2-TIMER_GROUP Unable to create timer group
Explanation PlaceD was unable to create the group for storing program timers, and therefore failed to initialize.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%OS-PLACED_PROGS-3-CHKPT_MIGRATE Failed to migrate checkpoint data for process '[chars]%s[chars]' from location [chars] to [chars]: [chars]
Explanation Whilst moving a process to a new location, PlaceD was unable to migrate the checkpointed data belonging to the process. No checkpointed data was therefore available to the process when it started at the new location.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-3-CHKPT_WRITE Failed to update checkpoint record for process '[chars]': [chars]
Explanation PlaceD was unable to update the checkpointed information for the specified process. PlaceD will fail to recover, or will recover out of date, information for the process if it is 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%OS-PLACED_PROGS-3-CLASS_INFO Failed to get all program info from SysMgr: [chars]
Explanation PlaceD was unable to get information from System Manager about all program classes and will now be in an indeterminate 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%OS-PLACED_PROGS-3-IPPH Failed to service an is-program-placed-here request: [chars]
Explanation PlaceD was asked about the location of a process, but was unable to service the request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-3-JID Failed to get job ID for process '[chars]%s[chars]' at location [chars]: [chars]
Explanation PlaceD was unable to get the Job ID for a 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%OS-PLACED_PROGS-3-KILL_MAN The attempt to kill process '[chars]%s[chars]' (job ID [dec]) at location [chars] failed, it should be killed manually
Explanation PlaceD attempted to kill a process, but it is still running
Recommended Action Attempt to kill the process manually. 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%OS-PLACED_PROGS-3-KILL_PROC Failed to kill process '[chars]%s[chars]' (job ID [dec]) at location [chars]: [chars]
Explanation PlaceD was unable to kill a process. PlaceD's view of the system state will now be incorrect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-3-KILL_UNKNOWN Attempted to kill process '[chars]%s[chars]' (job ID [dec]) at location [chars], but failed to determine whether it is dead
Explanation PlaceD attempted to kill a process, but is unable to determine whether the attempt was successful.
Recommended Action Determine whether the process is still running, if so, attempt to kill it manually. 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%OS-PLACED_PROGS-3-PARSE Failed to parse keyword '[chars]' in file [chars]:[dec] ([chars])
Explanation Whilst getting the system placement policy, an error occured whilst processing the specified file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-3-START_PROC Failed to start process '[chars]%s[chars]' at location [chars]: [chars]
Explanation PlaceD was unable to start a process. PlaceD's view of the system state will now be incorrect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-3-SYSMGR_TARGET Failed to set SysMgr target location to [chars]: [chars]
Explanation PlaceD was unable to set the target location in order to communicate with the appropriate System Manager instance.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-3-SYSTEM_POLICY Failed to read system placement policy. Process placement decisions will be sub-optimal. [chars]
Explanation PlaceD was unable to read the system placement policy and thus has no built-in policy to use when placing processes. The results of process placement decisions made by PlaceD will be sub-optimal.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-3-UPDATE_CLASS Failed to get updated info for '[chars]' from SysMgr: [chars]
Explanation PlaceD was unable to update information from System Manager about the program or program class specified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-4-CANT_SUSPEND Unable to suspend the request to start the process '[chars]%s[chars]' from location [chars]: [chars]
Explanation This is an out-of-memory message. PlaceD received a request to start the specified process on the specified location, and wanted to suspend the request. This is because PlaceD has a better location in mind, but is keeping the present location as a backup in case that card gets into trouble. However, there was insufficient resources for PlaceD to effect the suspension.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *SUPPORT*
Error Message%OS-PLACED_PROGS-4-CHKPT_DELETE Failed to delete the checkpoint data for process '[chars]%s[chars]' at location [chars]: [chars]
Explanation PlaceD was unable to delete the checkpoint segment for an application, eg before starting it from cold on that location.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-4-NOT_PLACEABLE Ignoring info from SysMgr about non-placeable process '[chars]'
Explanation PlaceD received information from System Manager about a program or program class that is not placeable, and therefore ignored the 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%OS-PLACED_PROGS-4-PROG_TYPE Ignoring unknown program type ([dec]) for '[chars]'
Explanation PlaceD did not recognise the program type received from System Manager, and therefore ignored the program 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%OS-PLACED_PROGS-4-TIMEOUT Ignoring timeout event for unknown program
Explanation A timeout event occurred, but PlaceD was unable to determine which program the event was for, and therefore ignored it.
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%OS-PLACED_PROGS-4-UNEXPECTED_NODE A message was received from the unknown location [chars]
Explanation A message was received from a location not known to be an RP or DRP in the current LR.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-4-UNKNOWN_PROC Unable to place '[chars]%s[chars]' since this is an unknown program type
Explanation PlaceD was asked to place a program whose name does not appear in the list of placeable processes and their properties.
Recommended Action This indicates that placed is receiving inconsistent or incomplete information from sysmgr. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-4-UNREC_PROG Ignoring request to remove unrecognized process '[chars]%s[chars]'
Explanation PlaceD did not recognise the process it was asked to remove, and therefore ingnored the request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-6-COLD_START The process '[chars]%s[chars]' is being restarted on the new location [chars] [chars] from cold, without its checkpoint data
Explanation The process is being replaced without its checkpoint data, eg if the node it was previously running on has failed. This may impact the router's operation.
Recommended Action If every RP and DRP has a standby, then this situation should not occur unless there is a double-failure of both active and standby cards simultaneously. If this message occurs in any other situation: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-6-REMOVING_ENTITY '[chars]%s[chars]' appears to no longer be configured, and will not be started again until reconfigured.
Explanation PlaceD was unable to start a process because it is purely configuration-driven and there is no configuration present. PlaceD will no longer attempt to keep the process running.
Recommended Action If the process has indeed been deconfigured (possibly a long time before this message appeared), then this is entirely benign. Otherwise: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROGS-6-START_PROC_NODE Process '[chars]%s[chars]' will be started at the location pair [chars] [chars] only when one of the locations completes booting
Explanation PlaceD was unable to start the specified process (and possibly other processes as well) because the specified locations are not running. The locations may still be in the process of booting. When one of the locations completes booting the process will be started.
Recommended Action If the locations are still in the process of booting then this is benign; the process will be started normally as part of the boot process. If the boot process takes too long, an alternative location for the process will automatically be chosen.
Error Message%OS-PLACED_PROGS-6-START_PROC_TIMEOUT Process '[chars]%s[chars]' cannot be started at the location pair [chars] [chars]; an alternative location will be selected
Explanation PlaceD was unable to start the specified process (and possibly other processes as well) at the the specified locations because they are taking too long to finish booting. An attempt will be made to start the process at an alternative location.
Recommended Action If the specified location pair does not boot successfully: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLACED_PROPS Messages
Error Message%OS-PLACED_PROPS-2-INIT Failed to initialize the Properties module: [chars]
Explanation PlaceD was unable to perform one of the steps required to initialize its Properties module.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%OS-PLACED_PROPS-3-BAD_CONFIG Refusing to apply some placement policy that would be rejected by placed's config verifier
Explanation Some placement policy is being ignored, since entering it normally would cause it to be rejected. This situation can occur only in rare situations, such as leaving placement policy configured for a program after that program's package has been de-activated from all locations.
Recommended Action If the situation is something like that in the explanation, then this message is correctly warning that the 'dead' policy is no longer acted upon. Otherwise: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROPS-3-NODETYPE Unknown location-type ([dec]) in location-type affinity (process '[chars]')
Explanation Whilst determining the optimal placement for the specified process, PlaceD encountered an affinity containing an unrecognized location-type, and therefore ignored the affinity.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROPS-3-REV_AFF Failed to apply program affinity from '[chars]' to '[chars]': affinity in reverse direction already configured
Explanation PlaceD attempted to set up an affinity from the first program class to the second, but discovered that an affinity from the second to the first already existed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PROPS-4-MAX_AFF Reached maximum limit on number of affinities ([dec]) for '[chars]', ignoring remaining affinities
Explanation Whilst determining the optimal placement, PlaceD reached the limit on the number of affinities allowed per process, and therefore ignored any further affinities.
Recommended Action Remove configured affinities that apply to this process until the number is equal to or below the given limit.
Error Message%OS-PLACED_PROPS-4-SUSPECT_NODE The affinity for program [chars] to location [chars] will be ignored until an RP or DRP is inserted at that location
Explanation The operator configured an affinity between a program and a location-set that includes a location not currently occupied by an RP or DRP. This part of the affinity policy will be ignored until an RP or DRP is inserted there. The policy applying to a given program (or program instance) can be inspected via the 'show placement policy program [instance ]' command.
Recommended Action Correct the configuration if this is an error, or insert an RP or DRP for the configuration to have any effect.
PMHAC Messages
Error Message%OS-PMHAC-2-CON_FAIL Internal SW.connection to [chars] failed and could not be retried (code=[dec])
Explanation Failed closing a internal sw connection using event_conn_error(). The process will abort.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PMHAC-2-FATAL PM HA Client DLL had a fatal error, reason=[chars]
Explanation The Platform Manager HA DLL encountered a fatal error and will cause the process to exit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PMHAC-3-CON_CLOSE Internal SW.connection to [chars] failed and retry also failed (code=[dec])
Explanation Failed closing a internal sw connection using event_conn_error() after failing a msg_send from Platform Manager to another component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PMHAC-3-ERROR PM HA Client DLL error=[chars]
Explanation The Platform Manager HA DLL encountered an internal software 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%OS-PMHAC-3-ERROR2 PM HA CLIENT DLL error, reason=[chars], errno=[dec]
Explanation The Platform Manager fault reporting DLL encountered an internal software 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%OS-PMHAC-4-BAD_DEVICEID Internal SW error, device_id [dec] is not recognized
Explanation As part of regular operation, software attempted to register to an unrecognized device ID to get fault information. Nothing should go wrong as a result of this 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%OS-PMHAC-4-NOMEM_RETRY PM HA CLient DLL: out of memory ([chars]) Will retry.
Explanation PM HA Memory Allocation Error. DLL will retry.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%OS-PMHAC-4-WARNING PM HA Client DLL warning, reason=[chars]
Explanation The Platform Manager HA DLL encountered an internal software warning.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PMHAD Messages
Error Message%OS-PMHAD-2-FATAL PM HA Driver DLL fatal error, reason=[chars]
Explanation The Platform Manager fault reporting DLL encountered a fatal error and will cause the process to exit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PMHAD-2-FATAL2 PM HA Driver DLL fatal error, reason=[chars], errno=[dec]
Explanation The Platform Manager fault reporting DLL encountered a fatal error and will cause the process to exit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PMHAD-3-ERROR PM HA Driver DLL error, reason=[chars]
Explanation The Platform Manager HA DLL encountered an internal software 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%OS-PMHAD-3-ERROR2 PM HA Driver DLL error, reason=[chars], errno=[dec]
Explanation The Platform Manager HA DLL encountered an internal software 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%OS-PMHAD-4-BAD_DEVICEID Internal SW error, device_id [dec] is not recognized
Explanation As part of regular operation, the device driver was registering with a fault reporting API. But the device is unrecognized by the API. Nothing should go wrong as a result of this 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%OS-PMHAD-4-INCONSISTENT_DEV SW error, driver registered using different ID ([chars] then [chars]).
Explanation As part of regular operation, the device driver was registering with a fault reporting API. The request was rejected because the driver did not register using the same device 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%OS-PMHAD-4-INSTANCE_OUT_OF_RANGE SW error, device [chars]: instance [dec] is out of range.
Explanation As part of regular operation, the device driver was registering with a fault reporting API. The request was rejected because the API does not support the number of device instance asked for by the driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PMHAD-4-WARNING PM HA Driver DLL warning, reason=[chars]
Explanation The Platform Manager HA DLL encountered an internal software warning.
Recommended Action No action is required.
PROCFIND Messages
Error Message%OS-PROCFIND-2-EVENT_MGR Failed to create an event manager: [chars]
Explanation Procfind was unable to create an event manager for receiving messages, and therefore failed to initialize.
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%OS-PROCFIND-2-MEMORY Failed to allocate memory for [chars]
Explanation Insufficient resources were available to allocate memory for the specified item. Procfind may not be able to continue running.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%OS-PROCFIND-2-NODEID Failed to get node ID of current node: [chars]
Explanation Procfind was unable to determine the ID of the node on which it was running, and therefore failed to initialize.
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%OS-PROCFIND-2-SYSDB_BIND Failed to bind to SysDB at '[chars]': [chars]
Explanation Procfind was unable to bind to the SysDB server, and therefore failed to initialize.
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%OS-PROCFIND-2-SYSDB_EDM_INIT Failed to initialize SysDB EDM functions handle: [chars]
Explanation Procfind was unable to initialize its SysDB EDM functions handle, and therefore failed to initialize.
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%OS-PROCFIND-2-SYSDB_EDM_REG Failed to register with SysDB as an EDM at '[chars]': [chars]
Explanation Procfind was unable to register with the SysDB server for as an EDM, and therefore failed to initialize.
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%OS-PROCFIND-3-PROC_INFO Failed to retrieve info for process [dec]: [chars]
Explanation Procfind was unable to read the information for the specified process, and will therefore return incomplete results.
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%OS-PROCFIND-3-PROC_OPEN Failed to open process [dec]: [chars]
Explanation Procfind was unable to open the specified process, and will therefore return incomplete results.
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%OS-PROCFIND-4-EVENT_BLOCK Error waiting for message - ignoring: [chars]
Explanation An error occured whilst Procfind was waiting for messages, Procfind ignored the error and continued to wait for more messages.
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%OS-PROCFIND-4-NODETYPE Running on unknown nodetype, assuming it is a linecard
Explanation Procfind was did not recognise the node type on which it was running, and therefore assumed it was a linecard.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PROCFIND-4-READY Failed to signal end of initialization to SysMgr: [chars]
Explanation Procfind was unable to inform System Manager that it has finished initializing and is ready to service request. Procfind ignored the error and continued normally.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PUF Messages
Error Message%OS-PUF-4-MCAST_MSG Problem processing incoming multicast message: [chars]
Explanation An incoming multicast message was received, supposedly containing data that should be persisted to non-volatile storage on the receiving location, but this persisting operation could not complete because of a problem.
Recommended Action This is unlikely to be immediately threatening to the router's health, but could cause misbehavior if the router is reloaded. 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.
QAD_LIB Messages
Error Message%OS-QAD_LIB-3-ERROR Operation [chars] failed : [chars]
Explanation The specified operation 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%OS-QAD_LIB-6-INFO Condition [chars] : [chars]
Explanation The specified condition has occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
QAD_QUEUE_MODEL Messages
Error Message%OS-QAD_QUEUE_MODEL-3-ERROR Operation [chars] failed : [chars]
Explanation The specified operation 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.
QAD_SERVER Messages
Error Message%OS-QAD_SERVER-3-ERROR Operation [chars] failed : [chars]
Explanation The specified operation 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.
QNET_LC Messages
Error Message%OS-QNET_LC-2-BASE_BAD_CHAIN_TYPE [chars]:[dec]:[chars]: Invalid attempt to build chain (type [dec])
Explanation qnetbase_builder_func() called with bad chain type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-2-BASE_CONTROL_FUNC_ERR [chars]:[dec]:[chars]: Base Control function erroneously called!
Explanation qnetbase_control_func() wrongly called.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-2-CAPS_BAD_CHAIN_TYPE [chars]:[dec]:[chars]: Invalid attempt to build chain (type [dec])
Explanation qnetcaps_builder_func() called with wrong chain type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-2-CAPS_CONTROL_FUNC_ERR [chars]:[dec]:[chars]: Caps Control function erroneously called!
Explanation qnetcaps_control_func() has been called, which should never happen.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-2-DUPLICATE_BMA_PAK [chars]: Cannot duplicate BMA packet (rc=[dec] dropping Qnet packet.
Explanation pak_netio_duplicate() 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%OS-QNET_LC-2-ENCAPS_FUNC_ERR [chars]:[dec]:[chars]: Qnet encapsulation node erroneously called!
Explanation qnetcaps_encaps() has been called, which should never happen.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-2-LOST_QNET_CONN Lost connection to Qnet process; dropping packets.
Explanation netio_dll_packet_input_NEW() to Qnet failed and Qnet connection is closed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET_LC-2-PAK_INPUT_FAIL [chars]:[dec]:[chars]: packet_input returned non-zero result code ([dec])
Explanation netio_dll_packet_input_NEW() to Qnet 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%OS-QNET_LC-2-UINT32_GET [chars]:[dec] failed to get destination slot. error [dec]
Explanation pak_netio_uint32_get() 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.
QNET Messages
Error Message%OS-QNET-0-EMG [chars]
Explanation An EMERGENCY level message was emitted by QNET.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET-1-ALT [chars]
Explanation An ALERT level message was emitted by QNET.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET-2-CRT [chars]
Explanation A CRITICAL level message was emitted by QNET.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET-3-ERR [chars]
Explanation An ERROR level message was emitted by QNET.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET-4-DUMPER_SNAP_DUMP Process [dec] requested voluntary [chars] dump of itself
Explanation A non-invasive voluntary coredump requested by the process. Process might be experiancing a condition which needs investigation. This core file will help analysing the issue.
Recommended Action This should not occur in normal conditions, please provide the coredump to TAC.
Error Message%OS-QNET-4-DUMPER_SNAP_NODUMP Problem with voluntary core dump requested by [dec] when [chars]: [chars]
Explanation A non-invasive voluntary coredump was requested by the process, but a problem occured that prevented the coredump from being created.
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%OS-QNET-4-SIO_Q_PROD q_produce for QNET tx failed, rc = [dec]
Explanation could not send pkt to fabric driver.
Recommended Action This should not occur in normal conditions
Error Message%OS-QNET-4-WRN [chars]
Explanation A WARNING level message was emitted by QNET.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QNET-5-NOT [chars]
Explanation A NOTICE level message was emitted by QNET.
Recommended Action No action is required.
Error Message%OS-QNET-6-DUMPER_SNAP_DUMP_OK Voluntary core dump requested by process [dec] completed
Explanation A non-invasive voluntary coredump requested by the process completed successfully. Process might be experiancing a condition which needs investigation. This core file will help analysing the issue.
Recommended Action This should not occur in normal conditions, please provide the coredump to TAC.
Error Message%OS-QNET-6-INF [chars]
Explanation An INFO level message was emitted by QNET.
Recommended Action No action is required.
Error Message%OS-QNET-7-DEB [chars]
Explanation A DEBUG level message was emitted by QNET.
Recommended Action Debug message only. No action is required.
QSM Messages
Error Message%OS-QSM-2-ADD_SYMLINKS_DIR Unable to add directory link [chars]: [chars]
Explanation A error occured while processing a QSM configuration file. This could be due to a problem with the installed media or file system damage. QSM will continue startup-up, but some system functionality may be impared.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-2-ADD_SYMLINKS_FILE Unable to add link [chars]-[chars]: [chars]
Explanation A error occured while processing a QSM configuration file. This could be due to a problem with the installed media or file system damage. QSM will continue startup-up, but some system functionality may be impared.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-2-DEBUG_KEY_CREATE Could not create key. rc: [dec], qsm_lock_key: [dec]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-2-DEBUG_SPECIFIC_ALLOC Could not alloc space for thread specific lock data: [chars]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-2-DEBUG_SPECIFIC_SET Could not set thread specific for lock data: [chars]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-2-INITIALIZATION_FAILURE Unable to initialize [chars]: [chars]
Explanation The QSM process wasn't able to startup up due the indicated failure during initialization. A restart of the process will be attempted. If the process can not be sucessfully started after several attempts, the board will probably be unusable.
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%OS-QSM-2-INVALID_PLATFORM_TYPE Platform_get_type returned an unknown node type: [dec]
Explanation The QSM process wasn't able to startup up due the indicated failure during initialization. A restart of the process will be attempted. If the process can not be sucessfully started after several attempts, the board will probably be unusable.
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%OS-QSM-2-INVALID_SYMLINKS_FILE Invalid line in symlinks file: [chars]
Explanation A startup configuration file for QSM contained an invalid line. This could be due to a problem with the installed media or file system damage. QSM will continue startup-up, but some system functionality may be impared.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-2-LOCATE_SYMLINKS_FILE Unable to locate symlinks file at etcpath [chars]: [chars]
Explanation An expected startup configuration file for QSM could not be found. This could be due to an install problem or due to data being deleted from the installation file system. QSM will continue startup-up, but some system functionality may be impared.
Recommended Action Your installed file system is missing a file. Perform a re-install to refresh the missing file. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-2-LOCK_HELD Unexpected lock held at [chars]: [dec]. Last taken at [chars]: [dec]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-2-OPEN_SYMLINKS_FILE Unable to open symlinks file [chars]: [chars]
Explanation An expected startup configuration file for QSM could not be opened. This could be due to a problem with the installed media or file system damage. QSM will continue startup-up, but some system functionality may be impared.
Recommended Action Your installed file system may be corrupted. Perform a format and re-install to fix it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-ADMIN_ADD (transition message) Detected admin plane add for [chars]. class: [hex], svctype: [hex], msgflags: [hex]
Explanation Development debug message
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-3-BAD_DBDUMP_MESSAGE An database dump message from another node could not be processed ([chars]): [chars]
Explanation The indicated error occured while processing a dbdump from another node.
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%OS-QSM-3-BAD_MESSAGE An unexpected message from another node could not be processed ([chars]): [dec]
Explanation An invalid message type was received from another node.
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%OS-QSM-3-BAD_UPDATE_MESSAGE An update message from another node could not be processed ([chars]): [chars]
Explanation The indicated error occured while processing an update from another node.
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%OS-QSM-3-CERR_REGISTER Unable to register the QSM error messages: [chars]
Explanation The QSM error number/messages table could not be registered with the cerrno system. Error translations will not be available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_CANT_OPEN Unable to open QSM checkpoint file [chars]: [chars]
Explanation The checkpoint file could not be opened. A restart of QSM is likely to have incomplete data.
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%OS-QSM-3-CHECKPOINT_CANT_RELOAD Unable to re-load QSM link [chars]-[chars]: [chars]
Explanation A link found in the checkpoint file could not be created in the QSM database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_CANT_RELOAD_NOTIFY Unable to re-load QSM notification for [chars]: [chars]
Explanation A link found in the checkpoint file could not be created in the QSM database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_CANT_RENAME Unable to rename checkpoint file [chars]-[chars]: [chars]
Explanation The checkpoint temporary file could not be renamed. A restart of QSM is likely to have incomplete data.
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%OS-QSM-3-CHECKPOINT_CANT_SEEK Unable to seek to the end of the QSM checkpoint file [chars]: [chars]
Explanation The checkpoint file could not be appended to. A restart of QSM is likely to have incomplete data.
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%OS-QSM-3-CHECKPOINT_CANT_TRUNCATE Unable to truncate QSM checkpoint file [chars]: [chars]
Explanation The QSM checkpoint file could not be truncated -- prior to being overwritten with updated data. A restart of QSM is likely to have incomplete data.
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%OS-QSM-3-CHECKPOINT_CANT_WRITE Unable to write to QSM checkpoint file [chars]: [chars]
Explanation A link could not be written to the QSM checkpoint file. A restart of QSM is likely to have incomplete data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-CHECKPOINT_FORMAT Insufficient buffer size to format QSM checkpoint record. Have [dec], need [dec]
Explanation A QSM checkpoint record could not be placed in the checkpoint file due to insufficient buffer space.
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%OS-QSM-3-CHECKPOINT_LOCK_FAILURE Checkpoint lock failure: [chars]
Explanation The lock that protects the QSM checkpoint database could not be taken. The checkpoint database could become corrupted -- causing a restart of QSM to have incomplete data.
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%OS-QSM-3-CHECKPOINT_NOSPACE Unable to allocate space for the checkpoint buffer
Explanation A QSM checkpoint record could not be placed in the checkpoint file due to insufficient heap space.
Recommended Action This indicates a low memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%OS-QSM-3-LINK_BAD_MODE A Link database entry had an unexpected mode: 0o%o
Explanation The mode data (MOG) for a link entry had an unexpected value. This could indicate a memory corruption problem.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_CREATE_FAILURE Unable to create link database entry '[chars]' ([chars]): [chars]
Explanation An entry could not be placed in the links database. The full error message should indicate where the failure occured and why.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_DELETE_FAILURE_INUM Unable to delete link database entry: [dec]
Explanation A link could not be deleted from the links database. This could indicate either a code problem or a memory corruption problem.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_DELETE_FAILURE_PATH Unable to delete link database entry: [chars]
Explanation An entry could not be deleted from the links database. The full error message should indicate where the failure occured and why.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_FREE_ZERO_INUM The QSM links database was requested to free a inode with a zero inumber
Explanation A internal error occured. A small amount of memory has been lost. QSM can be restarted to recover the lost 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%OS-QSM-3-LINK_INVALID_CUR_INDEX Invalid cur index in [chars]. CUR: [dec], path: [chars], inum: [dec]
Explanation A internal error has occured. The QSM directory scrub routine has been aborted. This should not cause any instability unless this message is repeated many times.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_LOCK_FAILURE A lock failure occured in the links database ([chars]): [chars]
Explanation An expected database lock was not held. This could indicate a memory corruption problem.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LINK_WRONG_RESULT link delete returned wrong link entry. path [chars], result: [hex], delete_result: [hex]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-3-LOCK_FAILURE A lock failure occured ([chars]): [chars]
Explanation The indicated error occurred while attempting to hold or release a lock.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-LOCK_FAILURE_LOCKTEST [chars]: [dec]. A lock failure occured ([chars]): [chars]
Explanation The indicated error occurred while attempting to hold or release a lock.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-NO_MEMORY Unable to obtain [dec] bytes of memory while: [chars]
Explanation QSM could not obtain system meory while performing the indicated operation.
Recommended Action This indicates a low memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%OS-QSM-3-NON_ADMIN_ADD (transition message) Detected NON admin plane add for [chars]. class: [hex], svctype: [hex], msgflags: [hex]
Explanation Development debug message
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-3-NOTIFY_LOCK_FAILURE A lock failure occured in the notification database ([chars]): [chars]
Explanation An expected database lock was not held. This could indicate a memory corruption problem.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-NOTIFY_WRITE_FAILED Notification checkpoint record could not be written: [chars]
Explanation A notification record could not be written to the QSM notification checkpoint file. A restart of QSM is likely to have incomplete data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-3-SEND_DATABASE_MESSAGE Unable to send a database message ([chars]): [chars]
Explanation A database update or dump mesage could not be sent to the other nodes.
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%OS-QSM-7-BAD_LWM_MSG Bad LWM Message received from pid [dec]. ([chars]): [chars]
Explanation An error was received while processing a request from a local process. There could be a version mis-match or corruption in the client process. The error message should provide some clue to the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-7-BAD_LWM_VERSION A QSM message was received, but it had the wrong version number. Received: [hex], Expected: [hex].
Explanation An error was received while processing a request from a local process. There could be a version mis-match or corruption in the client process. The error message should provide some clue to the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-7-LINK_BAD_THREAD_INUM A link was not threaded correctly in the links database ([chars]). thread: [dec]. inum: [dec]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LINK_BAD_THREAD_PATH A link was not threaded correctly in the links database ([chars]). thread: [dec]. path: [chars]
Explanation This is a debug message that is not compiled into a customer version of the code.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LINK_LOST_EMPTY_DIRECTORY An empty directory was to be deleted but inode [dec] could not be found: [chars]
Explanation An empty directory was to be automatically purged from the QSM database. When the directory was searched for, it could not be found.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LOCK_NOTFOUND A lock list did not have an expected lock at [chars]: [dec]
Explanation The lock list was corrupted.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LOCK_WRONG_COUNT A lock list had an incorrect count at [chars]: [dec]. ([dec] vs [dec])
Explanation The lock list was corrupted.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LOCKORDER_FAILURE A lock ordering failure occured ([chars]) at [chars]:[dec]. ([dec] vs [dec]).
Explanation A lock was taken in an invalid sequence.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-LOCKORDER_UPGRADE A lock upgrade (read to write) attempt was made at [chars]:[dec]. The lock was first taken at [chars]:[dec]
Explanation An invalid upgrade was made of a lock.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-NODE_DELETE_FAILURE A node was only partially deleted. thread [dec], node: [chars]
Explanation Internal memory corruption occured in the QSM nodes database.
Recommended Action Take a dump of the process and restart it. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-QSM-7-NODE_LOOKUP_FAILURE A node could not be found in the QSM nodes database: [chars]
Explanation An attempt to use a QSM link was made -- but the remote node that exported the link to the local node was not in the local nodes database. This could be a harmless timing condition.
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%OS-QSM-7-NON_LOCAL A QSM message was received from a non-local process
Explanation A process on another node contacted the local QSM server. The local server refused the request.
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%OS-QSM-7-NOTIFY_REGISTER_FAILED notification register of [chars] failed: [chars]
Explanation A application requested database notification could not be placed in the QSM notification database. An error will be returned to the client process.
Recommended Action Debug message only. No action is required.
Error Message%OS-QSM-7-NOTIFY_UNREGISTER_FAILED notification register of [dec] failed: [chars]
Explanation A application requested database un-notification could not be removed from the QSM notification database. An error will be returned to the client process.
Recommended Action Debug message only. No action is required.
QUEUE Messages
Error Message%OS-QUEUE-2-LINKED Bad [chars] of [hex] in queue [hex]
Explanation The router is running short on memory.
Recommended Action It may be necessary to free some memory by exiting a program. If this message recurs, call your technical support representative for assistance.
Error Message%OS-QUEUE-2-NOTQ [chars] didn't find [hex] in queue [hex]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
Error Message%OS-QUEUE-2-QCOUNT Bad [chars] [hex] count [dec]
Explanation An internal software error occurred.
Recommended Action If any of these messages recur, call your technical support representative for assistance.
RDS Messages
Error Message%OS-RDS-2-ASSERT_MSG [chars].[dec]: hit assert condition. 'val1=[hex]' expected to be [chars] 'val2=[hex]'
Explanation rds hit an internal assert.
Recommended Action Contact support.
Error Message%OS-RDS-3-ALLOC_FAILURE_MSG couldnt alloc for [chars], len=[dec], errno=[dec]
Explanation This is a generic error msg for memory allocation failure.
Recommended Action Contact support.
Error Message%OS-RDS-3-BAD_READ ens_[chars] returned len=[dec] for DH_ENTRY: [hex], expected=[dec]
Explanation ens_read returned bad len.
Recommended Action Contact support.
Error Message%OS-RDS-3-BAD_SEQNUM UNEXPECTED rdr_dh_seqnum=[dec] rhdr.seq_num=[dec] for DH=[hex], dlen=[dec], rdr_data=[pointer]
Explanation ens_read returned data with bad seqnum.
Recommended Action Contact support.
Error Message%OS-RDS-3-ENS_BULK_REGISTER [chars]: ens_bulk_register failed, rc=[hex], errno=[dec]
Explanation ens_bulk_register failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-ENS_PRODUCER_RELEASE ens_producer_release for DH=[hex] failed, errno=[dec]
Explanation ens_producer_release failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-ENS_PUBLISH [chars]: ens_publish for DH=[hex] failed, errno=[dec]
Explanation ens_publish failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-ENS_REGISTER_CLASS [chars]: ens_register_class for replica_name=[chars] ch=[hex] failed, rc=[hex], errno=[dec]
Explanation ens_bulk_register failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-GROUP_CREATE group_create for [chars]/[chars] failed, errno=[dec]
Explanation Group create failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-LOCK_FAILURE [chars] failed, errno=[dec]
Explanation Lock/Unlock operation failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-NRS_CREATE_CLASS [chars]: nrs_create_class for [chars] failed, errno=[dec]
Explanation nrs_create_class failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-NRS_REGISTER_BULK [chars]: nrs_register_bulk for CH=[hex] failed, rc=[dec] errno=[dec]
Explanation nrs_register_bulk failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-NRS_SEARCH [chars]: nrs_search for [chars] failed, rc=[dec] errno=[dec]
Explanation nrs_search failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-PENDING_WRITE [chars]: couldnt create pending msg for CH=[hex], DH=[hex], errno=[dec]
Explanation couldnt create pending msg for the incoming write.
Recommended Action Contact support.
Error Message%OS-RDS-3-READ_FAILED ens_[chars] DH_ENTRY=[hex] ([chars]), for exp_len=[dec] got=[dec] rc=[dec] errno=[dec]
Explanation ens_read API failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-SYNC_CREATE TID=[dec]: gs_sync_create failed for tag [hex], err [dec]
Explanation Ticket create failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-SYNC_RELEASE_FAILED TID=[dec]: Ticket Release failed rp=[pointer] tick=[hex] curr=[dec] hi=[dec] currturn=[hex] next=[hex] waitcnt=[dec] rc=[dec] errno=[dec]
Explanation Ticket request timed out.
Recommended Action Contact support.
Error Message%OS-RDS-3-SYNC_REQUEST TID=[dec]: Ticket Request failed for ticket [hex], rp [pointer], err [dec]
Explanation Ticket request failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-SYNC_REQUEST_TIMED_OUT TID=[dec]: Tick Req Timed out rp=[pointer] tick=[hex] curr=[dec] hi=[dec] currturn=[hex] next=[hex] waitcnt=[dec] rc=[dec] errno=[dec], RETRYING...
Explanation Ticket request timed out.
Recommended Action Contact support.
Error Message%OS-RDS-3-SYNC_REQUEST_UNEXPECTED TID=[dec]: Tick Req unknown failure, rp=[pointer] tick=[hex] curr=[dec] hi=[dec] currturn=[hex] next=[hex] waitcnt=[dec] rc=[dec] errno=[dec]
Explanation Ticket request failed with unknown error.
Recommended Action Contact support.
Error Message%OS-RDS-3-WRITE_TIMEDOUT rds_write DHDL=[hex]([chars]), req=[dec], resp=[dec], #wtrs=[dec]: [chars], errno=[dec], retries=[dec]
Explanation rds_write request timed out.
Recommended Action Contact support.
Error Message%OS-RDS-4-AVL_TREE_LOOKUP Lookup of identifier=[hex] in TREE=[pointer] failed
Explanation avl tree lookup failed.
Recommended Action Contact support.
Error Message%OS-RDS-4-BAD_RDSTYPE TID=[dec]: [chars]: Wrong replica type passed, expected=[dec]..
Explanation passed in replica_id is wrong.
Recommended Action Contact support.
Error Message%OS-RDS-4-COND_TIMED_WAIT TID=[dec]: Unexpected error=[dec] from pthread_cond_timedwait cmd=[dec]
Explanation pthread_cond_timedwait failed.
Recommended Action Contact support.
Error Message%OS-RDS-4-DUPLICATE_TICKET_NOTIF TID=[dec]: [dec]: Duplicate Tick Notif (Dropping it) rp=[pointer] tick=[hex] curr=[dec] hi=[dec] currturn=[hex] next=[hex] TickCurr=[dec] TickHi=[dec] state=[hex]
Explanation Got a ticket notification, for an already active ticket.
Recommended Action Contact support.
Error Message%OS-RDS-4-GENERIC_FAILURE_MSG [chars][dec]
Explanation This is a generic error msg.
Recommended Action Contact support.
Error Message%OS-RDS-4-GROUP_SEND_RINFO [chars]: group_send_rinfo failed GID=[hex], errno=[dec], rc=[dec], #resp=[dec], pattern=[chars]
Explanation group_send_rinfo failed.
Recommended Action Contact support.
Error Message%OS-RDS-4-GSM_FAIL GSM for [chars] Failed for Handle=[hex], to (g:[hex]/n:[hex]/p:[dec]), errno=[dec]
Explanation group_send_memberset failed.
Recommended Action Contact support.
Error Message%OS-RDS-4-NRS_DECODE [chars], Datahandle=[hex], errno=[dec]
Explanation An internal NRS function failed.
Recommended Action Contact support.
Error Message%OS-RDS-7-GET_DH_ENTRY [chars].[dec]: No entry for Datahandle=[hex], rp=[pointer] vec=[pointer] errno=[dec]
Explanation Could find datahandle entry in the vector for replica
Recommended Action Contact support.
Error Message%OS-RDS-7-GET_REPLICA [chars].[dec]: [chars] for CH=[hex], errno=[dec], rds_type=[dec]
Explanation Couldnt get the replica entry
Recommended Action Contact support.
Error Message%OS-RDS-7-INVALID_ARGS function [chars] was passed invalid args
Explanation a function was invoked with invalid arguments
Recommended Action Contact support.
Error Message%OS-RDS-7-INVALID_RHDR function [chars] was passed invalid rhdr=[pointer]
Explanation a function was invoked with invalid rhdr msg
Recommended Action Contact support.
Error Message%OS-RDS-7-NO_PREQ_ENTRY [chars].[dec]: [chars] rp=[pointer] nptr=[pointer] from sender=g:[dec]/n:[dec]/p:[dec]
Explanation Couldnt find pending request entry in the pending list.
Recommended Action Contact support.
Error Message%OS-RDS-7-QUERY_PEERS_TIMED_OUT TID=[dec] Couldnt cmd=[dec] for GID=[hex] CHDL=[hex]([hex]) #to_resp=[dec] req=[dec] got=[dec] state=[hex], expstate=[hex] preq_id=[dec] rds_type=[dec]
Explanation Ticket request timed out.
Recommended Action Contact support.
Error Message%OS-RDS-7-WRONG_PLANE [chars]: Wrong plane [dec] for [chars] failed..
Explanation ens_bulk_register failed.
Recommended Action Contact support.
REGEXP Messages
Error Message%OS-REGEXP-6-ENOMEM % Out of memory
Explanation *NONE*
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%OS-REGEXP-6-INTERNAL % Internal error
Explanation *NONE*
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-REGEXP-6-INVALID % invalid regexp: [chars]
Explanation *NONE*
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-REGEXP-6-REGERROR % [chars]
Explanation *NONE*
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
RSVDPMEM Messages
Error Message%OS-RSVDPMEM-3-BAD_DATAFILE_VALUES Values from [chars] are invalid. data=[chars]. start=[dec], end=[dec].
Explanation Reserve Physmem encountered a severe error and is not able to recover from the error. Details are provided with the error message. Call support with this error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RSVDPMEM-3-BAD_RETURN_VALUES Did not set return values correctly. start=[dec], end=[dec], base_addr=[hex], mem_size=[dec], mem_physical_start=[hex], mem_physical_size=[dec].
Explanation Reserve Physmem encountered a severe error and is not able to recover from the error. Details are provided with the error message. Call support with this error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RSVDPMEM-3-INVALID_PARAMS Invalid parameters passed to function. [chars] is NULL
Explanation Reserve Physmem encountered a severe error and is not able to recover from the error. Details are provided with the error message. Call support with this error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RSVDPMEM-3-MEMUTIL_FIND_FAIL memutil_find_reserved_mem returned invalid memory reservation - mem_physical_start=[hex], mem_physical_size=[hex].
Explanation Reserve Physmem encountered a severe error and is not able to recover from the error. Details are provided with the error message. Call support with this error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RSVDPMEM-3-NO_MATCHING_STRING Failed to find any line in [chars] containing string: [chars]
Explanation Reserve Physmem encountered a severe error and is not able to recover from the error. Details are provided with the error message. Call support with this error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RSVDPMEM-3-OPEN_FAIL Open of [chars] failed. Error [chars]
Explanation Reserve Physmem encountered a severe error and is not able to recover from the error. Details are provided with the error message. Call support with this error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RSVDPMEM-3-SSCANF_FAIL sscanf function failed to match required number of parameters. Matched [dec], error: [chars]. data=[chars].
Explanation Reserve Physmem encountered a severe error and is not able to recover from the error. Details are provided with the error message. Call support with this error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
RT_CHECK_LIB Messages
Error Message%OS-RT_CHECK_LIB-3-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%OS-RT_CHECK_LIB-3-DEBUG_SERVICES debug services function [chars] failed
Explanation A call to a debug services interface failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK_LIB-3-EVENT_MANAGER event manager function [chars] failed: [chars]
Explanation A call to an event manager interface failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK_LIB-3-GSP_CONN [chars]: error connecting with Group Services: [chars]
Explanation A call to group_join() failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK_LIB-3-GSP_LOOKUP [chars]: error group lookup with Group Services: [chars]
Explanation A call to group_lookup() failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK_LIB-3-GSP_NOTIFY [chars]: error group set notify with Group Services: [chars]
Explanation A call to group_set_notify() failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK_LIB-3-GSP_SEND [chars]: error sending with Group Services: [chars]
Explanation A call to group_send() failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK_LIB-3-MGD_TIMER mgd timer function [chars] failed
Explanation A call to a mgd timer interface failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK_LIB-3-PTHREAD Pthread operation [chars] [hex] failed: [chars]
Explanation A pthread operation failed
Recommended Action Contact support.
RT_CHECK Messages
Error Message%OS-RT_CHECK-3-BCDL_REQ BCDL [chars] request failure, error [dec]: [chars]
Explanation A call to a BCDL interface failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK-3-CHAN_CONN [chars] msg chan connect failed: [chars], error [dec]: [chars]
Explanation A call to a LWM API failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK-3-DEBUG_SERVICES debug services function [chars] failed
Explanation A call to a debug services interface failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK-3-EDM_DATALIST_ADD_FAILED Failed to add an external data manager datalist for [chars]
Explanation A process has requested information through SysDB, probably as the result of executing a show command. The attempt to add an item to an external data manager datalist has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RT_CHECK-3-EDM_DATALIST_CREATE_FAILED Failed to create external data manager datalist for [chars]
Explanation A process has requested information through SysDB, probably as the result of executing a show command. The creation of the external data manager datalist has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RT_CHECK-3-EDM_ENCODE_FAILED Failed to encode [chars] data in external data manager
Explanation A process has requested information through SysDB, probably as the result of executing a show command. The data requested could not be encoded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RT_CHECK-3-EDM_LIST_ADD_FAILED Failed to add to an external data manager list for [chars]
Explanation A process has requested information through SysDB, probably as the result of executing a show command. The attempt to add an item to an external data manager list has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RT_CHECK-3-EDM_LIST_CREATE_FAILED Failed to create external data manager list for [chars]
Explanation A process has requested information through SysDB, probably as the result of executing a show command. The creation of the external data manager list has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RT_CHECK-3-EDM_REGISTER_FAILED Failed to register its external data manager: [chars]
Explanation The process failed when attempting to register its external data manager with SysDB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RT_CHECK-3-EVENT_MANAGER event manager function [chars] failed: [chars]
Explanation A call to an event manager interface failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK-3-GROUP group services function [chars] failed, error [dec]: [chars]
Explanation A call to a group services interface failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK-3-MEMORY Memory allocation error.
Explanation Malloc or calloc returned a null pointer. This indicates an out of memory condition. The rt_check process will exit or return.
Recommended Action Collect system log information.
Error Message%OS-RT_CHECK-3-MGD_TIMER mgd timer function [chars] failed
Explanation A call to a mgd timer interface failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK-3-PTHREAD pthread function [chars] failed
Explanation A call to a pthread interface failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK-3-PTHREAD_MUTEX Pthread operation [chars] [hex] failed: [chars]
Explanation The mutex lock/unlock failed
Recommended Action Contact support.
Error Message%OS-RT_CHECK-3-SYSDB [chars]
Explanation A call to a sysdb interface failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK-3-TIMER_INIT timer init failed
Explanation A call to the rt_check timer init routine failed.
Recommended Action Contact support.
Error Message%OS-RT_CHECK-3-TRM_INIT Failed to initialize TRM client library: [chars]
Explanation Failed to initialize TRM global client 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%OS-RT_CHECK-3-TRM_VRF_ID Failed to get TRM vrf id from vrf tag: [chars]
Explanation The TRM failed to translate a vrf tag into a vrf 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%OS-RT_CHECK-3-USAGE usage: [chars] [-m] [-u]
Explanation Incorrect command line arguments were given to the module
Recommended Action Contact support.
Error Message%OS-RT_CHECK-6-EDM_BAG_REGISTRATION_FAILED Failed to register its external data manager data blocks: [chars]
Explanation The process failed while attempting to register its external data manager data blocks with SysDB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SHMWIN_SVR Messages
Error Message%OS-SHMWIN_SVR-3-EVM_ERROR [chars], Error: [chars]
Explanation Failed in some event management functions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SHMWIN_SVR-3-LWM_ERROR [chars], Error: [chars]
Explanation Failed to execute some LWM library functions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SHMWIN_SVR-3-MAIN_INIT Initialization in main failed, Error: [chars]
Explanation One of the functions called during initialization of the process 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%OS-SHMWIN_SVR-3-MMAP_FAIL Failed to mmap [chars]
Explanation mmap of the shared memory required to store servers tree nodes 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%OS-SHMWIN_SVR-3-MSG_ERROR Received a bad message, [chars]
Explanation The message received by the server had inconsistent values.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SHMWIN_SVR-3-NO_MEMORY Failed in allocating memory
Explanation Not enough memory available in the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SHMWIN_SVR-3-PLATFORM_FILE [chars], Error: [chars]
Explanation Problem opening/reading from the platform shmwin file.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SHMWIN_SVR-3-QSM_ERROR Failed to publish QSM namespace, [chars]
Explanation The server failed in advertising its namespace through QSM
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SHMWIN_SVR-3-SHM_ERROR [chars] [chars], Error: [chars]
Explanation There was a problem with the shared memory file allocation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SHMWIN_SVR-3-SVR_ERR [chars]
Explanation An error has occurred in a server operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SHMWIN_SVR-6-SHARED_MUTEX_REVIVED The shmwin control mutex was revived by shmwin_svr
Explanation A participant process crashed while holding the shared shmwin control mutex and the shmwin_svr revived the mutex.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SHMWIN Messages
Error Message%OS-SHMWIN-2-ERROR_ENCOUNTERED SHMWIN: Error encountered: [chars]
Explanation SHMWIN hit an error, which is described by the description printed
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SHMWIN-2-SHARED_PAGE_ERROR SHMWIN: Shared page related error encountered: [chars]: failed with [chars]
Explanation SHMWIN hit an error related to the shared page.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SHMWIN-3-ALLOC_ARENA_FAILED SHMWIN: Failed to allocate new arena from the server : [chars]
Explanation SHMWIN failed to allocate the arena's virtual range from the 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%OS-SHMWIN-3-FREE_ARENA_FAILED SHMWIN: Failed to free VM at address [hex] back to the server : [chars]
Explanation SHMWIN failed to free the arena's virtual range back to the 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%OS-SHMWIN-3-FSTAT_FAILED SHMWIN: fstat call for [chars] failed, error: [chars][[dec]]
Explanation SHMWIN encountered an error condition, a fstat call 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%OS-SHMWIN-3-FTRUNCATE_FAILED SHMWIN: [chars]: ftruncate for [chars] to size [dec] failed, error: [chars][[dec]]
Explanation SHMWIN encountered an error condition, the ftruncate 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%OS-SHMWIN-3-MMAP_FAILED SHMWIN: [chars]: mmap at pid [dec] address [hex] size [dec] failed, error: [chars][[dec]]
Explanation SHMWIN encountered an error condition, the mmap 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%OS-SHMWIN-3-MUNMAP_FAILED SHMWIN: [chars]: munmap at pid [dec] address [hex] size [dec] failed, error: [chars][[dec]]
Explanation SHMWIN encountered an error condition, the munmap 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%OS-SHMWIN-3-MUTEXOP_FAILED SHMWIN: [chars] failed, error: [chars][[dec]]
Explanation SHMWIN encountered an error condition, the a mutex operation 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%OS-SHMWIN-3-OPEN_FAILED SHMWIN: shm open for [chars] failed, error: [chars][[dec]]
Explanation SHMWIN encountered an error condition, the shm open 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%OS-SHMWIN-6-FILE_EXISTS SHMWIN: [chars]: shmwin found file [chars] of size [dec] existing when not expecting, trying to continue
Explanation SHMWIN encountered an error condition, the file was existing already.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SYSMGR Messages
Error Message%OS-SYSMGR-0-EMERGENCY [chars]
Explanation The system is unusable.
Recommended Action Contact support.
Error Message%OS-SYSMGR-1-ALERT [chars]
Explanation Action must be taken immediately.
Recommended Action Contact support.
Error Message%OS-SYSMGR-2-CRITICAL [chars]
Explanation Critical conditions are present.
Recommended Action Contact support.
Error Message%OS-SYSMGR-2-MANAGED_REBOOT reboot to be managed by process ([chars]) reason ([chars])
Explanation A critical process ran into trouble and will reboot the node.
Recommended Action Contact support.
Error Message%OS-SYSMGR-2-REBOOT reboot required, process ([chars]) reason ([chars])
Explanation A critical process ran into trouble.
Recommended Action Contact support.
Error Message%OS-SYSMGR-3-ERROR [chars]
Explanation A function call returned an unexpcted error
Recommended Action Contact support.
Error Message%OS-SYSMGR-3-FUNCTION [chars]: call to [chars] failed: [chars]
Explanation A function call returned an unexpcted error
Recommended Action Contact support.
Error Message%OS-SYSMGR-3-UNEXPECTED [chars]
Explanation A function call returned an unexpcted error
Recommended Action Contact support.
Error Message%OS-SYSMGR-4-CHECK_LOG [chars]
Explanation Check specified log for important information
Recommended Action Contact support.
Error Message%OS-SYSMGR-4-MANDATORY_OFF mandatory state off for all processes by request
Explanation Check specified log for important information
Recommended Action None
Error Message%OS-SYSMGR-4-MANDATORY_ON mandatory state on for all processes by request
Explanation Check specified log for important information
Recommended Action None
Error Message%OS-SYSMGR-4-MANDATORY_REBOOT_ABORTED mandatory reboot aborted by request
Explanation Check specified log for important information
Recommended Action None
Error Message%OS-SYSMGR-4-MANDATORY_REBOOT_ENABLE mandatory reboot option enabled by request
Explanation Check specified log for important information
Recommended Action None
Error Message%OS-SYSMGR-4-MANDATORY_REBOOT_OVERRIDE mandatory reboot option overridden by request
Explanation Check specified log for important information
Recommended Action None
Error Message%OS-SYSMGR-4-PROC_CRASH_JID User [chars] ([chars]) requested a crash of process with jobid [dec]
Explanation For high availability demonstration, processes may be intentionally crashed by sending them a fatal signal.
Recommended Action None
Error Message%OS-SYSMGR-4-PROC_CRASH_NAME User [chars] ([chars]) requested a crash of process [chars]
Explanation For high availability demonstration, processes may be intentionally crashed by sending them a fatal signal.
Recommended Action None
Error Message%OS-SYSMGR-4-WARNING [chars]
Explanation Warning conditions are present.
Recommended Action Contact support.
Error Message%OS-SYSMGR-5-NOTICE [chars]
Explanation A normal but significant event has occurred.
Recommended Action none
Error Message%OS-SYSMGR-6-INFO [chars]
Explanation An informational message only
Recommended Action none
Error Message%OS-SYSMGR-7-DEBUG [chars]
Explanation An informational message only
Recommended Action Contact support.
Error Message%OS-SYSMGR-7-FUNCTION_PATH [chars]: [chars] [chars] failed: [chars]
Explanation A function call returned an unexpcted error
Recommended Action Contact support.
Error Message%OS-SYSMGR-7-INSTALL_FINISHED software installation is finished
Explanation software installation has finished.
Recommended Action None
Error Message%OS-SYSMGR-7-INSTALL_NOTIFICATION notification of software installation received
Explanation A notification to begin processing a software installation has been received.
Recommended Action None
TIMER Messages
Error Message%OS-TIMER-3-MGDTIMER [chars]%s, timer = [hex]
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, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-TIMER-3-NO_CHILD Parent has no child, this may be a freed/stopped parent
Explanation All parents in a managed timer tree should have at least one child.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-TIMER-3-TIMERNEG Cannot start timer ([hex]) with negative offset ([dec]).
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-TIMER-3-TWCHUNKALLOC Couldn't allocate a chunk for timer wheel
Explanation There wasn't enough resources to allocate a chunk in timer wheels.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-TIMER-3-TWCHUNKFREE Couldn't free chunk for timer wheel
Explanation Resources were not able to be deallocated in timer wheels.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-TIMER-3-TWEVMERROR EVM error [dec] in timer wheels.
Explanation EVM 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%OS-TIMER-3-TWMUTEXLOCKERROR Error acquiring mutex for timer wheel; [chars]
Explanation A software error occurred acquiring a mutex.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-TIMER-3-TWMUTEXUNLOCKERROR Error releasing mutex for timer wheel; [chars]
Explanation A software error occurred releasing a mutex.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-TIMER-3-TWNOMEM Couldn't allocate memory for timer wheel
Explanation Not enough resources to allocate a system structure in timer wheels.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-TIMER-3-TWOSERROR OS error [dec] in timer wheels.
Explanation OS call 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%OS-TIMER-3-TWTIMERALLOC Timer wheels Couldn't allocate OS timer for timer wheel ([dec])
Explanation Could get access to OS timer resources.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-TIMER-3-TWTIMERERROR OS timer error [dec] in timer wheels
Explanation Couldn't manipulate OS 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.
TZ Messages
Error Message%OS-TZ-2-INTERNAL [chars]: [chars]
Explanation Serious problem occured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-TZ-3-LRD LRd error: [chars]
Explanation Unable to query LR status
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-TZ-3-SYSDB [chars]: [chars]
Explanation One of the sysdb APIs 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.
