-
Cisco IOS XR System Error Message Reference Guide, Release 3.8
-
Preface
-
Overview
-
Access Control List (ACL) Messages
-
Application Infrastructure Messages
-
Diagnostic Messages
-
Fabric Messages
-
Forwarding Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 Messages
-
Layer 2 Messages
-
Layer 3 Messages
-
License Messages
-
Media Messages
-
Manageability (MGBL) Messages
-
Operating System (OS) Messages
-
Platform Messages
-
Quality of Service (QoS) Messages
-
Routing Messages
-
Security Messages
-
Services Messages
-
Simple Network Management Protocol (SNMP) Messages
-
System Database Messages
-
Index
-
Feedback
Table Of Contents
Operating System (OS) Messages
PLATFORM_LPTS_COM_IFIB Messages
PLATFORM_LPTS_COM_NETIO 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:
•
PLATFORM_LPTS_COM_IFIB Messages
•
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.
ALLOCATOR Messages
Error Message%OS-ALLOCATOR-3-LTRACE_INIT_FAILED ltrace_init failed with retcode [dec], ([chars])
Explanation Ltrace initialization 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-ALLOCATOR-7-LOCKING Failed to [chars] [chars]. Error [dec] ([chars])
Explanation The allocator module has either failed to acquire 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-ALLOCATOR-7-MEMORY Failed to malloc [unsigned int] bytes
Explanation The allocator module 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-ALLOCATOR-7-NULL A NULL argument was passed into an allocator API where a non-NULL value was expected.
Explanation A client passed a NULL value into an allocator API, or an internal error caused a NULL value to be unexpectedly passed through to an internal API.
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-ALLOCATOR-7-SIZE_MISMATCH Mismatch between block size discovered in pool memory ([unsigned int]) and block size specified by client ([unsigned int])
Explanation The block size in the memory passed into the allocator module does not match that passed in by the caller on initialisation.
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.
ARBMGR Messages
Error Message%OS-ARBMGR-4-INIT_ERROR Unexpected init error: [chars]: [chars]: [hex]
Explanation An unexpected init error condition encountered.
Recommended Action Collect system log information. No action is required.
Error Message%OS-ARBMGR-4-MBI_BOOT_HOLD MBI Boot Hold delay of [dec] seconds done to allow other RP to become active due to multiple ungraceful resets on this RP.
Explanation An MBI boot hold has been introduced to allow the other RP to boot first to give it the opportunity to become the active RP. This is because this RP has had multiple ungraceful resets in the last two hours which could be preventing the router from being stable.
Recommended Action Collect system log information.
Error Message%OS-ARBMGR-7-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error.
Recommended Action Collect system log information. No action is required.
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.
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.
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.
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_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_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_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_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_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_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_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_TABLE_REF_COUNT Table id [hex] not found in subgroup [dec] to merge from subgroup [dec]
Explanation Any table has to be part of the subgroup 0.
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 Group [chars] 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 equals [dec]
Explanation For displaying blwm debugging information.
Recommended Action No action is required.
CDS_CONSUMER_LIB Messages
Error Message%OS-CDS_CONSUMER_LIB-3-NULL_CONSUMER [dec]: Consumer has not registered yet, tag equals [hex]
Explanation cds lib has got a message to process, but consumer has not yet registered. please collect cds consumer ltrace.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
CDS_PRODUCER_LIB Messages
Error Message%OS-CDS_PRODUCER_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-CDS_PRODUCER_LIB-3-SEND_FAILED [chars]: ### failed to send LWM message ret [dec] 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.'
cds_proxy Messages
Error Message%OS-cds_proxy-2-USAGE Incorrect arguments: Usage: [chars] [svr_threads]
Explanation Incorrect command line parameters were passed to the cds proxy, 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-cds_proxy-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-cds_proxy-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-cds_proxy-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.
cds_svr Messages
Error Message%OS-cds_svr-2-USAGE Incorrect arguments: Usage: [chars] [svr_threads]
Explanation Incorrect command line parameters were passed to the cds proxy, 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-cds_svr-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-cds_svr-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.
CDSUTILS Messages
Error Message%OS-CDSUTILS-7-INTERNAL_ERROR Encountered internal error: [chars]: [dec]:[hex]:[hex]
Explanation The CDS module has encountered internal error.
Recommended Action None
Error Message%OS-CDSUTILS-7-INVALID_ARG Invalid argument passed: [chars]: [dec]:[hex]:[hex]
Explanation CDS module was passed invalid arguments.
Recommended Action None
CERR_LIB Messages
Error Message%OS-CERR_LIB-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-CERR_LIB-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-CERR_LIB-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-CERR_LIB-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.
CERR_SVR Messages
Error Message%OS-CERR_SVR-7-EVENT Unrecoverable error in event loop. Error: [chars]
Explanation An error (other than EINTR) occured in the event loop. The process must exit.
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-CERR_SVR-7-INIT Failure during intialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the Cerrno Server process
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-CERR_SVR-7-INSTALL Error updating Cerrno DLL Lookup table during Install Event. Error: [chars]
Explanation An error has occurred updating the reference table for cerrno error messages. Some cerrno messages may be incorrect or undecodable.
Recommended Action A successful restart of the Cerrno Server will result in future messages being decodable.
Error Message%OS-CERR_SVR-7-SYSMGR Failure communicating readiness to SysMgr. Error: [chars]
Explanation The process was initialized successfully but was unable to inform System Manager of the success.
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-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.
Error Message%OS-CHUNK-7-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-7-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-7-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-7-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-7-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-7-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-7-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-7-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-7-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-7-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-7-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-7-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.
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_CANCEL_TYPE [chars]: bad cancel 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_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-COND_OP_FAILED [chars]: Cond op [chars] failed on conditional variable [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_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_BLOCK_ERR [chars]: rc [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-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_failed Failed to notify node state when [chars]: [chars]
Explanation The internal communication channel among pctl threads is broken.
Recommended Action Must restart the process.
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-INCORRECT_GROUP_ID Can not rejoin group [chars], group id changed from [dec] to [dec], restarting
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-RELEASE_TICKET_FAILURE [chars]: release ticket failure ret: [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-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-3-WRONG_TICKET_TYPE [chars]: wrong ticket 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-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 equals [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-3-CORE_FILE_TOO_SMALL Too small size [dec] for [chars]
Explanation Core dump file resulted in illegally small size
Recommended Action 'Copy the error message exactly as it appears on 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-DLOPEN_FAILED dll loading [dec] failures: [chars] is [chars]
Explanation Dumper startup failed because loading some of dlls failed. Most likely cause is memory running low.
Recommended Action No action is required.
Error Message%OS-DUMPER-3-GET_MAPPING_INFO_FAILED Core dump failed for [chars] in getting map info. Error: [chars]
Explanation Core dump failed because getting map info failed.
Recommended Action No action is required.
Error Message%OS-DUMPER-3-MAP_INFO_FAILED Core dump for [chars] failed due to process information not available
Explanation Core dump failed because the process information is not available.
Recommended Action Possible Work Around: If there was dumper malloc failure, try following command for failed process. 'show proc failed_process_name | include COPY' If it would produce something like following output, core: other_option COPY then dumper COPY option is enabled for this process and it temporary consume a lot of memory, so it might be one of the cause of the memory shortage problem. If that is the case, then specifing following command for failed process will reduce the temporal memory usage of the process, thus it might work around the problem. 'proc failed_process_name core other_option'
Error Message%OS-DUMPER-3-PATH_FAILED Core dump for [chars] failed due to lack of working dump path choice
Explanation Core dump failed because there is no working dump path.
Recommended Action No action is required.
Error Message%OS-DUMPER-3-SELECT_SEGMENTS_FAILED Core dump for [chars] failed in selecting process segments
Explanation Core dump failed because selecting process segments in sparse mode failed.
Recommended Action No action is required.
Error Message%OS-DUMPER-3-SET_RLIMIT_FAIL Failed to set resource limit data. soft limit: [hex] hard limit: [hex] Error([dec]): [chars]
Explanation Failed to set resource limit dat
Recommended Action 'Copy the error message exactly as it appears on 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_SIZE_INVALID Stack size [dec] [chars] at [chars]:[dec]
Explanation Stack size of target process 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-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-WRONG_COMP_MAGIC_NUMBER Wrong file magic number [hex] [hex] [hex] for [chars]
Explanation Core dump file compression header is broken.
Recommended Action 'Copy the error message exactly as it appears on 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-BUS_OBJERR Accessed BadAddr [hex] at PC [hex] code [dec] fltno [dec]
Explanation Signal info
Recommended Action No action is required.
Error Message%OS-DUMPER-4-CORE_INFO Core for pid equals [dec] ([chars]) requested by [chars]@[chars]
Explanation Debug core info
Recommended Action No action is required.
Error Message%OS-DUMPER-4-CORE_PAGE_LOST [chars] core COPY option enabled but free memory:[unsigned long int] is not enough for the next segment:0x[pointer](size [unsigned long int]) and succeeding ones. Use 'exception memory-threshold percentage_in_total_memory' to change the minimum free memory threshold.
Explanation Not enough free memory to continue COPY option core dump, which allocate local memory for each meory segent.
Recommended Action No action is required.
Error Message%OS-DUMPER-4-CRASH_INFO Crashed pid equals [dec] ([chars])
Explanation Debug crash info
Recommended Action No action is required.
Error Message%OS-DUMPER-4-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-4-ERR_MEM_ALIGN Memory addr:[hex] not aligned :[chars] at [dec]
Explanation Core dump failed because the pending segment flush failed.
Recommended Action No action is required.
Error Message%OS-DUMPER-4-ERR_MEM_ALLOC Malloc (size:[dec]) failed :[chars] at [dec]
Explanation Memory running low
Recommended Action Reboot the router
Error Message%OS-DUMPER-4-ERR_PATHMGR_SYMLINK Pathmgr symlink failed [chars] [chars] . Error: [chars] errno [hex]
Explanation Pathmgr symlink 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-4-ERR_QSM_ADD_SERVICE QSM publish dumper path failed [chars] [chars] . Error: [chars] errno [hex]
Explanation QSM publish dumper path 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-4-ERR_SP_INVAL Stack Pointer:[hex] is corrupted Base [hex], Top [hex]:[chars] at [dec]
Explanation Core dump failed because the stack pointer is corrupted.
Recommended Action No action is required.
Error Message%OS-DUMPER-4-ERR_SYSDB_APPLY 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-4-ERR_SYSDB_BIND [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-4-ERR_SYSDB_GET [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-ERR_SYSDB_NOTIFY 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-4-ERR_SYSDB_REG_NOTIFY Sysdb notifier registration for [chars] failed. Error: [chars]
Explanation Sysdb notifier 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-4-ERR_SYSDB_REG_VERIFY Sysdb verifier registration for [chars] failed. Error: [chars]
Explanation Sysdb verifier 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-4-ERR_SYSDB_SET [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-ERR_SYSDB_UNBIND 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-4-ERR_SYSMGR_REG_LREVT Sysmgr LR evt registration failed. Error: [chars] errno [hex]
Explanation Sysmgr LR event 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-4-ERR_SYSMGR_REG_REDST Sysmgr redundancy state registration failed. Error: [chars] errno [hex]
Explanation Sysmgr redundancy state 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-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 equals [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 equals [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] on [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] on [chars] [chars]
Explanation Status of the core dump transfer to persistent location.
Recommended Action No action is required.
Error Message%OS-DUMPER-5-DUMP_FAILURE Core dump failed: [chars] [chars] [unsigned long int]
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-5-DUMP_SUCCESS Core dump success
Explanation Core dump succeded
Recommended Action No action is required.
Error Message%OS-DUMPER-5-LTRACE_INIT Dumper ltrace init failure. Error([dec]): [chars]
Explanation Failed to initialize dumper ltrace buffer
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-5-TIMEOUT dumper will be restarted due to watchdog timeout
Explanation dumper restarted due to watchdog timeout.
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-5-TMP_PATH_FULL [chars]
Explanation /tmp/dumper is not available because it is full of files still being transferred.
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-6-BAD_PATH Choice [dec]([chars]) either not configured or bad path [chars] at [dec]. Trying next choice.
Explanation Could be any number of reasons. Check for other error messages.
Recommended Action No action is required.
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 'No action is required.'
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 'No action is required.'
Error Message%OS-DUMPER-6-CORE_MD5 [chars] [chars] size:[unsigned long int] md5:[chars]
Explanation Keep core file md5 information to identify later file corruption.
Recommended Action 'No action is required.'
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 No action is required.
Error Message%OS-DUMPER-6-DEFAULT_PATH_TMP [chars]
Explanation Notify that the default path has been set to /tmp/dumper
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-6-ERR_SYSMGR_CORE_OPTIONS Failed to get process core options from sysmgr. Error([dec]): [chars]. Default options will be used.
Explanation Dumper failed to get process core option values from sysmgr. Typically because a non sysmgr managed process crashed, or rarely because sysmgr was being down or being very busy.
Recommended Action No action is required.
Error Message%OS-DUMPER-6-FALLBACK_CHOICE Fall back choice: [chars]%s[chars]
Explanation Could be any number of reasons. Check for other error messages.
Recommended Action No action is required.
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-GET_PROC_CISCO devctl DCMD_PROC_CISCO failed with size:[dec]. 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-6-GET_PROC_CURTHREAD_FAILED devctl DCMD_PROC_CURTHREAD failed for [chars] with tid:[dec]. 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-6-GET_PROC_GETGREG_FAILED devctl DCMD_PROC_GETGREG failed for [chars]. 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-6-GET_PROC_TIDSTATUS_FAILED devctl DCMD_PROC_TIDSTATUS failed for [chars]. 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-6-GET_PROCINFO_FAILED devctl DCMD_PROC_INFO failed for [chars]. 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-6-MSGREPLY_CONFIRMED Reply to client is confirmed
Explanation Reply to client could have been missing, so did reply at the end.
Recommended Action No action is required.
Error Message%OS-DUMPER-6-NO_SP_INFO No sub processor information on this card.
Explanation No sub processor information found on this card. Display the local node information instead.
Recommended Action 'No action is required.'
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 'No action is required.'
Error Message%OS-DUMPER-6-NODEID_FAIL Failed to get the local nodeid.
Explanation Failed to get the local nodeid from platform library.
Recommended Action 'No action is required.'
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-PENDING_SEGMENT_FLUSH_FAILED Core dump failed in pending segment flush
Explanation Core dump failed because the pending segment flush failed.
Recommended Action No action is required.
Error Message%OS-DUMPER-6-POPULATE_FILTERS_FAILED Core dump failed in populating filters
Explanation Core dump failed because populating filters for the process mapinfo failed.
Recommended Action No action is required.
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 '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 No action is required.
Error Message%OS-DUMPER-6-SAVE_SEGINFO_FAILED Core dump failed at [dec] in saving segment info
Explanation Core dump failed because the saving segment info failed.
Recommended Action No action is required.
Error Message%OS-DUMPER-6-SCAN_DLLDATA_FAILED Core dump failed at [dec] in scanning the dll data
Explanation Core dump failed because scanning the dll data failed.
Recommended Action No action is required.
Error Message%OS-DUMPER-6-SCAN_PROCDATA_FAILED Core dump failed in scanning the process data
Explanation Core dump failed because scanning the process data failed.
Recommended Action No action is required.
Error Message%OS-DUMPER-6-SCAN_REGISTERS_FAILED Core dump failed in scanning regisers
Explanation Core dump failed because scanning registers for the process failed.
Recommended Action No action is required.
Error Message%OS-DUMPER-6-SCAN_STACK_FAILED Core dump failed in scanning stack
Explanation Core dump failed because scanning stack for the process failed.
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-TREEWALK_FAILED Core dump failed in sparse tree walk
Explanation Core dump failed because the sparse tree processing failed.
Recommended Action No action is required.
Error Message%OS-DUMPER-6-UNLINK_CORE_FAILED Unlink of [chars] failed. Error: [chars]
Explanation Could not delete a file
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 No action is required.
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 'No action is required.'
Error Message%OS-DUMPER-7-BAD_CORE_SIZE Bad core file size, Expecting: [dec], Collected: [dec]
Explanation Could not collect the entire core file data
Recommended Action No action is required.
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-CLOSE_PROBLEM [chars]:[dec] [chars] failed. Error: [chars]
Explanation Possibly the server died.
Recommended Action No action is required.
Error Message%OS-DUMPER-7-CORE_CONFLICT [chars] core dump is cancelled. The same name core is still being transferred from /tmp
Explanation This happens when a process requests repeating core dump, and the next core dump is requested while the previous core was temporary dump'ed to /tmp, and still being transferred from /tmp.
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 No action is required.
Error Message%OS-DUMPER-7-DEBUG_INIT_FAILED [chars]
Explanation Debug init failed
Recommended Action No action is required.
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_ATTRIBUTE Dump request with attribute [hex] for process [chars]
Explanation The information message for debug use.
Recommended Action No action is required.
Error Message%OS-DUMPER-7-DUMP_CORE_FAILURE Core dump failed: Could not create core
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-7-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-7-DUMP_REQUEST Dump request for process [chars]
Explanation The information message for debug use.
Recommended Action No action is required.
Error Message%OS-DUMPER-7-ERR_EVM_CREATE [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-7-ERR_EVM_EVENT_BLOCK 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-7-ERR_EVM_FILE_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-7-ERR_SYSDB_DATALIST Failed call : [chars]. Error [chars]
Explanation Unexpected failure for sysdb datalist.
Recommended Action No action is required.
Error Message%OS-DUMPER-7-ERR_SYSDB_ITEM Bad item : [chars]. [chars]
Explanation Unexpected or bad item under config for dumper
Recommended Action No action is required.
Error Message%OS-DUMPER-7-ERR_SYSDB_ITEM_TYPE Bad item type for [chars]
Explanation Unexpected item type in dumper config
Recommended Action No action is required.
Error Message%OS-DUMPER-7-ERR_THREAD_ATTRIBUTE [chars]: [chars] failed: [chars]
Explanation Could not attribute a thread. 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-7-ERR_THREAD_COND [chars]: [chars] failed: [chars]
Explanation Could not cond_wait a thread. 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-7-ERR_THREAD_CREATE [chars]:[dec] [chars]: [chars] failed: [chars]
Explanation Could not create a thread. 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-7-ERR_THREAD_JOIN 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-7-ERR_THREAD_MUTEX_INIT mutex operation [chars] failed for mutex_init 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-7-ERR_THREAD_MUTEX_LOCK [chars]:[dec] mutex operation [chars] failed for loc_mutex 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-7-ERR_THREAD_MUTEX_UNLOCK [chars]:[dec] mutex operation [chars] failed for unlock_mutex 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-7-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-7-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-7-FLT_STACK Failed to map stack @ PC [hex]
Explanation Signal info
Recommended Action No action is required.
Error Message%OS-DUMPER-7-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-7-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-7-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-7-INSTALL_PKG [chars] V [chars][[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-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-7-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-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-MMAP_FAILED [chars]:[dec] 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-7-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-7-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-7-MUNMAP_FAILED Unmap for size [dec] at Address 0x[pointer] 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-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-OPEN_FAILED Open of path [chars] failed at [chars]:[dec]. 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-7-PROC_OPEN_FAILED Fail to open process, pid equals [dec]. Error equals [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-7-PROC_PAGES Process memory pages [dec]
Explanation The total memory page number of dumper target process
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-7-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-7-READ_FAILED Read of size [dec] to fd [dec] at offset [hex] failed, read [dec] Error: [chars]
Explanation Most probably some problem with the procfs 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-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-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-7-SEEK_FAILED lseek to vaddr [hex] with fd [dec] failed. Error: [chars]
Explanation Most probably some problem with the procfs 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-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-SYSMGR_CALL Failed call : [chars]. Error [chars]
Explanation Unexpected failure for sysmgr 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-7-TRACE_BACK #[dec] [hex]
Explanation Trace back
Recommended Action 'No action is required.'
Error Message%OS-DUMPER-7-TRACE_BACK_ERROR [chars]
Explanation Some error happened in trace back 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-DUMPER-7-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-7-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-7-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-7-WRITE_FAILED Write of size [dec] to fd [dec] failed. Written [dec]. 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.
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-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-3-MUTEX_LOCK mutex lock error: ([chars]:[dec])
Explanation An Event Manager library function was not able to lock mutex.
Recommended Action Contact support.
Error Message%OS-EVM-3-MUTEX_UNLOCK mutex unlock error: ([chars]:[dec])
Explanation An Event Manager library function was not able to unlock mutex.
Recommended Action Contact support.
Error Message%OS-EVM-4-EMPTY_PATH registering empty path name without specifying _RESMGR_FLAG_FTYPEONLY flag, flags equals [hex]
Explanation A server process has registered empty path name with the path manager without specifying _RESMGR_FLAG_FTYPEONLY flag. This may lead to undesired behaviour like receiving requests intended for some other server process (when the other server process is restarted).
Recommended Action This is an internal error and should be reported to TAC. The application process making the call might have passed incorrect path name.
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-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-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_C12000 Messages
Error Message%OS-GSP_C12000-7-info [chars]
Explanation --
Recommended Action 'No action is required.'
GSP_NOTIF Messages
Error Message%OS-GSP_NOTIF-3-msg_failed Failure to notify node state when [chars]: [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-CLIENT_LOCK_ERROR [chars]:[dec] Error in client locking of client id [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-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-ENS_INVALIDATE_HANDLE_FAILED [chars]:[dec] detect application error from mid [dec]:[dec]%d and [dec]:[dec]:[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-gsp-3-ENS_MULTIPLE_PUBLISHERS_ERROR [chars]:[dec] ENS detects error in jid [dec], hdl [hex]:[dec], local-producer [dec]:[dec]:[dec], new-producer [dec]:[dec]:[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-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, taking [unsigned int] bytes
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-node_insert_fail Can't insert node [hex] to node state map
Explanation --
Recommended Action 'No action is required.'
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-3-WRONG_FLOW [chars]: wrong flow zone info
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-6-INFO [chars].
Explanation --
Recommended Action 'No action is required.'
Error Message%OS-gsp-7-DEBUG [chars].
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, taking [unsigned int] bytes
Explanation --
Recommended Action 'No action is required.'
Error Message%OS-gsp-7-MSG_NOTIF_WARN Process [chars] (pid [dec]) not handling message notification [dec] msgs pending head value [hex] retry cnt [dec]
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.'
Error Message%OS-gsp-7-send_mcast_failed [chars] returned error: [chars] for node [hex] state [dec] with seq [dec]
Explanation --
Recommended Action 'No action is required.'
INIT Messages
Error Message%OS-INIT-2-MBI_BOOT_HOLD_TIMEOUT mbi boot hold was not released after [dec] seconds, resetting node
Explanation An application set the MBI boot hold and it was not released within the specified timeout. This could indicate that the node is having problems and will be reset.
Recommended Action Collect system log information. No action is required.
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.
ISIS_MIB Messages
Error Message%OS-ISIS_MIB-3-ERR_ALLOC A general allocation failed
Explanation An allocation has failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%OS-ISIS_MIB-3-ERR_BAG_DECODE Failed to decode a trap event bag: [chars] ([hex])
Explanation The agent was unable to decode the bag representing a trap event.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%OS-ISIS_MIB-3-ERR_INIT [chars] : [chars] ([hex])
Explanation Initialization failed
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Enable 'debug snmp isis', restart the process snmpd and cause the isis mib to be loaded.
Error Message%OS-ISIS_MIB-3-ERR_MAKE_VAR_BIND Allocation failed for Var OID [chars] ID [dec] SNMP type [dec] value [hex]
Explanation An allocation has failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
ITAL_SHM Messages
Error Message%OS-ITAL_SHM-3-ERR_RESOURCE [chars] failed: [chars]
Explanation Some error occurred in operations related to resource allocation. The text of the message displays the failed operation and the related error code. The system will try to re-aquire the resource.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-ITAL_SHM-7-ERR_GENERAL [chars] failed: [chars]
Explanation Some error occurred in operations related to Shared Memory area. The text of the message displays the failed operation and the related error code. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-ITAL_SHM-7-ERR_INIT ITAL initialization failed: [chars]
Explanation Initialization of ITAL failed. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-ITAL_SHM-7-ERR_INIT_DEBUG ITAL debug init failed: [chars] ([chars])
Explanation Initialization of ITAL failed. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ITAL Messages
Error Message%OS-ITAL-2-ERR_INIT ITAL lib not fully initialized: [chars], error code [chars]
Explanation ITAL Initialization failed. The message displays the failed operation and the error code
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-ITAL-2-ERR_THREAD_LOCK An attempt to lock ITAL dbase failed for [chars] dbase, caller [chars] holder [chars]
Explanation An effort to lock database failed. The function which tried to lock as well as the function holding the lock are given in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-ITAL-2-ERR_THREAD_UNLOCK An attempt to unlock ITAL dbase failed for [chars] dbase
Explanation An effort to unlock database failed. The function which tried to unlock is given in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-ITAL-3-ERR_DEBUG_INIT [chars] : [chars]
Explanation Some error occurred in interactions with debug infrastructure. The text of the message displays the failed operation and the related error code. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-ITAL-3-ERR_IF_NOTIF Invalid interface notification ([chars]) received: IfName equals [chars], IfHandle equals [hex]
Explanation An invalid interface notification was received from one of the servers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-ITAL-3-ERR_MEM_ALLOC Memory allocation ([unsigned int] bytes) failed for [chars]
Explanation A memory allocation operation failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%OS-ITAL-5-ERR_UNSUPPORTED [chars]
Explanation Some client requires unsupported ITAL functionality.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-ITAL-7-ERR_GENERAL [chars]: [chars]
Explanation Certain operation failed due to unexpected error. The message displays the reasons.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-ITAL-7-ERR_REG [chars], reason: [chars]
Explanation Registration operation with a certain server failed. The message displays the reasons.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-ITAL-7-ERR_RETRY [chars], Retry Count equals [dec]
Explanation Retry count exceeded the limit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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-ALREADY_CALLED API [chars] already been called
Explanation The specified API has already been called.
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-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-INVALID_ARG [chars]: Invalid value [[dec]] for argument [[chars]] passed
Explanation An application called the API with invalid value.
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.
LPTS_LIB Messages
Error Message%OS-LPTS_LIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_LIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_LIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_MRT Messages
Error Message%OS-LPTS_MRT-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_MRT-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_MRT-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_PA_FF_CL Messages
Error Message%OS-LPTS_PA_FF_CL-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when calling the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PA_FF_CL-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when calling debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_PA_FF Messages
Error Message%OS-LPTS_PA_FF-3-CLIENT_NOT_FOUND [chars]: The client structure associated with this client was not found
Explanation An internal error was detected when trying find the internal client structure for a given 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-LPTS_PA_FF-3-EVENT_BLOCK [chars]: failed to block waiting for Event Manager events: [chars]
Explanation An internal error was detected when block waiting for Event Manager events.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PA_FF-3-EVENT_INIT_EVENT [chars]: could not initialize event structure: [chars]
Explanation An internal error was detected when initializing a sigevent structure using event_init_event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PA_FF-3-EVENT_UPDATE_FAIL Failure in the PA-FF update module: [chars] ([chars])
Explanation An error was detected when initializing the event queue between two infrastructure module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PA_FF-3-EVM_ASYNC_ATTACH [chars]: could not attach handler for Event Manager asynchronous event: [chars]
Explanation An internal error was detected when attaching a handler for an Event Manager asynchronous event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PA_FF-3-EVM_CREATE [chars]: could not create event manager: [chars]
Explanation An internal error was detected when creating Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PA_FF-3-GET_NODEID [chars]: Can't get my own nodeid: [chars]
Explanation A call to platform_get_my_nodeid faild.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PA_FF-3-INIT [chars]: initialization for PA Flow Forwarder I/O thread failed: [chars]
Explanation An internal error was detected when initializing PA Flow Forwarder I/O 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-LPTS_PA_FF-3-LRD_FAIL [chars]: error from lrd function [chars]: [chars]
Explanation An internal error was detected when using a logical router daemon 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-LPTS_PA_FF-3-MALLOC [chars]: malloc [dec] bytes failed: [chars]
Explanation An attempt to allocate meory 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-LPTS_PA_FF-3-MSG_ATTACH_SYNC [chars]: failed to attach handler for Event Manager synchronous event: [chars]
Explanation An internal error was detected when attaching a handler for an Event Manager synchronous event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PA_FF-3-MSG_CLINFO_GET_DATUM [chars]: msg_clinfo_get_datum failed: [chars]
Explanation An internal error was detected when accessing a client info structure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PA_FF-3-MSG_SEND_EVENT [chars]: msg_send_event failed: [chars]
Explanation An internal error was detected when sending an Event Manager synchronous event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PA_FF-3-TIMER_CREATE [chars]: could create the timer: [chars]
Explanation An internal error was detected when creating a timer using timer_create.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PA_FF-3-TIMER_SETTIME [chars]: could arm the timer: [chars]
Explanation An internal error was detected when arming a timer using timer_settime.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_PIFIB Messages
Error Message%OS-LPTS_PIFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PIFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PIFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS_PREIFIB Messages
Error Message%OS-LPTS_PREIFIB-3-BACKEND_EDM [chars]: EDM backend function [chars] failed: [chars]
Explanation An internal EDM backend function 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-LPTS_PREIFIB-3-BAG [chars]: Bag function [chars] failed: [chars]
Explanation An internal bag function 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-LPTS_PREIFIB-3-BATCHING [chars]: Error [chars] during batching '[chars]' from hardware pre-ifib
Explanation Hardware pre-ifib returned an error during a batching 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-LPTS_PREIFIB-3-BLC_UPDATE [chars]: BLC '[chars]' failed for interface handle: [hex]
Explanation Bundle (vlan) interface update to local bundle (vlan) database 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-LPTS_PREIFIB-3-DATAPATH_CMD [chars]: Pre-IFIB datapath control command [chars] failed: [chars]
Explanation The given Pre-IFIB datapath control command returns 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-LPTS_PREIFIB-3-EDM_UNREG [chars]: failed to unregister EDM: [chars]
Explanation An internal error was detected when trying to unregister EDM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-ENTRY_UPDATE [chars]: Error [chars] while updating entry with '[chars]' [hex]
Explanation Error during entry delete or update.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-EVENT_BLOCK [chars]: failed to block waiting for Event Manager events: [chars]
Explanation An internal error was detected when block waiting for Event Manager events.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-EVENT_CONN_CREATE [chars]: could not create event connection: [chars]
Explanation An internal error was detected when trying to create event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-EVENT_CONN_NOTIFY [chars]: could not set notify handler for connection open/close/error: [chars]
Explanation An internal error was detected when trying to set notify handler for connection opens, closes and errors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-EVENT_CONN_OPEN_ALL [chars]: could not open all event connections of this event manager: [chars]
Explanation An internal error was detected when trying to open all event connections of one event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-EVM_CREATE [chars]: could not create event manager: [chars]
Explanation An internal error was detected when creating Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-EVM_TM_ATTACH [chars]: could not set up a managed timer identifier: [chars]
Explanation An internal error was detected when trying to allocate a managed timer identifier and assign to it an event handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-EVM_TM_LEAF_NEW [chars]: could not create a managed timer tree leaf: [chars]
Explanation An internal error was detected when trying to create a managed timer tree leaf for the event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-HW_RETRY [chars]: Error [chars] during hardware retry to update entry in TCAM
Explanation Hardware pre-ifib returned an error during a update retry 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-LPTS_PREIFIB-3-IIR_QUERY [chars]: Error [chars] during POS bundle member query from IIR for ifhandle [hex]
Explanation Hardware pre-ifib returned an error during a batching 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-LPTS_PREIFIB-3-IM_CAPS_DATAPATH_CONTROL [chars]: the datapath control function for the capsulation failed: [chars]
Explanation An internal error was detected when calling datapath control function for the capsulation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-INVALID_ARGS [chars]: Invalid arguments: [chars]
Explanation The given argument 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-LPTS_PREIFIB-3-INVALID_FLOW_TYPE [chars]: Invalid flowtype [dec]
Explanation The flow type information is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-IPSEC_FVRF Failure occurred in IPSEC FRVF client API: [chars]. reason: [chars]
Explanation An errror detetcetd in one of the IPSEC-FVRF client APIs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-LRD_FAIL [chars]: error from lrd function [chars]: [chars]
Explanation An internal error was detected when using a logical router daemon 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-LPTS_PREIFIB-3-LTRACE_INIT [chars]: Initialization of lightweight tracing buffer '[chars]' failed: [chars]
Explanation Lightweight tracing initialization 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-LPTS_PREIFIB-3-MSG_CHAN_GLOBAL [chars]: failed to publish global directory channel: [chars]
Explanation An internal error was detected when publishing a global directory channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-NOMEM [chars]: Not enough memory
Explanation Memory low condition is detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-PA_FF_OPEN [chars]: failed to connect to the Port Arbitrator as a Flow Forwarder: [chars]
Explanation An internal error was detected when trying to connect to the Port Arbitrator as a Flow Forwarder.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-PA_FF_RESET [chars]: Reset of BCDL group in LPTS PA/FF library failed: [chars]
Explanation An internal error was detected when trying to reset the BCDL group for the LPTS Port Arbitrator/Flow Forwarder.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-PA_UPDATE [chars]: Error [chars] during '[chars]' from PA
Explanation Update from PA 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-LPTS_PREIFIB-3-PARSE_INFLOW_CONFIG [chars]: could not read input flow config file: [chars]
Explanation An internal error was detected when trying to parse the input flow configuration 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-LPTS_PREIFIB-3-PFI_IFH_BIND [chars]: Failed to connect to PFI Interface Handle Server: [chars]
Explanation Failed to connect to PFI Interface Handle 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-LPTS_PREIFIB-3-PIFIBM_INIT [chars]: failed to initialize Pre-IFIB Mgr: [chars]
Explanation An internal error was detected when trying to initialize the Pre-IFIB Mgr.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-REASS_LIST [chars]: Corrupted reassembly server list received: num_nodes [dec]
Explanation The list of reassembly servers is 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-LPTS_PREIFIB-3-SYSDB [chars]: Sysdb function [chars] failed: [chars]
Explanation An internal sysdb function 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-LPTS_PREIFIB-3-SYSMGR_PROC_READY [chars]: failed to notify sysmgr that we are ready: [chars]
Explanation An internal error was detected when trying to notify sysmgr that we are ready.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-3-VRF_UPDATE [chars]: VRF '[chars]' failed for VRF id: [hex]
Explanation VRF update to attached VRFs database on LC 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-LPTS_PREIFIB-6-NETIO_DOWN Pre-IFIB can't establish connection to NetIO in [dec]:[dec]
Explanation Pre-IFIB process can't establish connection to NetIO.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-6-NETIO_UP Pre-IFIB establish connection to NetIO after [dec]:[dec]
Explanation Pre-IFIB process established connection to NetIO.
Recommended Action No action is required.
Error Message%OS-LPTS_PREIFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS_PREIFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LPTS Messages
Error Message%OS-LPTS-3-ERR_BAD_LISTENER_TAG bad listner tag detected on the packet, dropping packet
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-LPTS-3-ERR_BAG_ENCODE [chars]: SysDB Bag encoding failed: [chars]
Explanation An internal error was detected when trying to encode a SysDB Bag.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_BAG_REG [chars]: SysDB Bag registration failed: [chars]
Explanation An internal error was detected when trying to register a SysDB Bag definition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_DATAPATH_INPUT_LEN datapath control input buffer len error: length equals ([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-LPTS-3-ERR_DEBUG_REG [chars]: debug register failed: [chars]
Explanation An internal error was detected when trying to register for changes to debug tuples.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_ECM_CREATE [chars]: couldn't create event connection manager: [chars]
Explanation An internal error was detected when trying to create event connection 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-LPTS-3-ERR_ECM_OPEN [chars]: couldn't open event connection: [chars]
Explanation An internal error was detected when trying to open event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_EDM_DATALIST_ADD [chars]: adding datalist as a SysDB EDM failed: [chars]
Explanation An internal error was detected when trying to add an item to SysDB data 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-LPTS-3-ERR_EDM_DATALIST_CREATE [chars]: adding datalist as a SysDB EDM failed: [chars]
Explanation An internal error was detected when trying to create a SysDB data 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-LPTS-3-ERR_EDM_REG [chars]: registering as a SysDB EDM failed: [chars]
Explanation An internal error was detected when trying to register as a SysDB EDM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_EVM_CREATE [chars]: couldn't create event manager: [chars]
Explanation An internal error was detected when trying to create event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_FINT_MEDIA_REG Couldn't set control mapping for lpts media on fint
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-LPTS-3-ERR_HSSD [chars]: [chars] 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-LPTS-3-ERR_HSSD_GET_DATA [chars]: retrieving data from HSSD failed: [chars]
Explanation An internal error was detected when trying to read data from the packet HSSD area.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_IFIB [chars]: [chars] 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-LPTS-3-ERR_IFIB_RES_ALLOC Couldn't allocate platform-specific IFIB result structure: [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-LPTS-3-ERR_IFIB_RES_SET failed to set platform-specific IFIB result fields: [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-LPTS-3-ERR_IFIB_SET_KEY [chars]: lpts_netio_ifib_set_key() 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-LPTS-3-ERR_INFO_GENERAL [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-LPTS-3-ERR_INVALID_ARGS [chars]: invalid args
Explanation Detected invalid arguments.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_MALLOC [chars]: malloc failure
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-LPTS-3-ERR_NETIO_DEBUG_INIT lpts netio debugging failed to initialize
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-LPTS-3-ERR_NETWORK_START_FAIL Unable to get packet network start. Dropping packet
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-LPTS-3-ERR_NULL_FINT_IDB NULL fint idb.. dropping packet
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-LPTS-3-ERR_NULL_TRANSPORT_CALLBACK [chars]: Null transport callback
Explanation Detected a NULL transport callback function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_PA_CLOSE [chars]: couldn't close the client connection with PA: [chars]
Explanation An internal error was detected when trying to close the client connection with PA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_PA_CONN [chars]: couldn't establish connection with PA: [chars]
Explanation An internal error was detected when trying to connection to PA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_PAK_DUP couldn't duplicate packet (deliver failed), error equals [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-LPTS-3-ERR_PAK_NETIO_MUTEX_LOCK [chars]: pak_netio_mutex_lock() 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-LPTS-3-ERR_PAK_NETIO_MUTEX_UNLOCK [chars]: pak_netio_mutex_unlock() 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-LPTS-3-ERR_PAK_NETIO_RETURN_BUFFER [chars]: pak_netio_return_buffer() 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-LPTS-3-ERR_PAK_NETIO_UINT8_GET [chars]: pak_netio_uint8_get() 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-LPTS-3-ERR_PLATFORM_GET_MY_NODEID [chars]: couldn't get my node ID: [chars]
Explanation An internal error was detected when trying to get the node ID for the node on which the caller is running.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_PREPARE_EGRESS_BUFFHDR [chars]: failed to process egress buffer header of packet [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-LPTS-3-ERR_PROCESS_INGRESS_BUFFHDR [chars]: failed to process ingress buffer header of packet [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-LPTS-3-ERR_PUNT_FAIL punt to [chars] failed, dropping packet: [chars]
Explanation One of the possible cause for this message could be denial-of-service attack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_SYSDB_CONN_TO_COID [chars]: converting SysDB connection ID to file descriptor failed: [chars]
Explanation An internal error was detected when trying to convert a SysDB connection ID to a file descriptor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-3-ERR_SYSDB_NS_NODE_TO_STR [chars]: converting node ID to SysDB string failed: [chars]
Explanation An internal error was detected when trying to convert a node ID to a string format that SysDB expects.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-LPTS-6-INFO_INTERNAL_TABLE LPTS tables changed in middle of walk. Show command incomplete.
Explanation During processing of a show command, the internal LPTS data structures changed in such a way as to make completion of the show command impossible.
Recommended Action Retry the command.
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_SYNC Messages
Error Message%OS-LTRACE_SYNC-3-EXTERNAL_API_ERROR [chars] failed: [chars]
Explanation Common external API returned an error
Recommended Action Contact support.
Error Message%OS-LTRACE_SYNC-3-FILE_BAD_MAGIC file [chars] has bad magic number [hex], should be [hex]
Explanation The file has wrong magic number.
Recommended Action Contact support.
Error Message%OS-LTRACE_SYNC-3-MEMORY_UNMAP_ERROR memory unmapping for [chars] failed. size:[dec]. Error([dec]): [chars]
Explanation Memory unmapping for the file failed.
Recommended Action Contact support.
Error Message%OS-LTRACE_SYNC-3-PTHREAD_API_ERROR [chars] failed. Error([dec]): [chars]
Explanation Pthread API returned an error
Recommended Action Contact support.
Error Message%OS-LTRACE_SYNC-3-RWLOCK_ERROR [chars] for [chars] failed. Error([dec]): [chars]
Explanation Read-write lock failed.
Recommended Action Contact support.
Error Message%OS-LTRACE_SYNC-4-FILE_SIZE_CHANGE The size of file [chars] couldn't be changed to [dec]. Error([dec]): [chars]
Explanation The operation to change the file size failed.
Recommended Action Contact support.
Error Message%OS-LTRACE_SYNC-4-LTRACE_INIT_ERROR ltrace initialization failed. Error([dec]): [chars]
Explanation ltrace initialization for ltrace synchronization server failed.
Recommended Action Contact support.
Error Message%OS-LTRACE_SYNC-4-MEMORY_MAP_ERROR memory mapping for [chars] failed. size:[dec] protection:[hex] flags:[hex] fd:0x[dec] off:[dec] Error([dec]): [chars]
Explanation Memory mapping for the file failed.
Recommended Action Contact support.
Error Message%OS-LTRACE_SYNC-4-SHMEM_ERROR ltrace shmem [chars] failed for [chars]. flags:[hex] mode:%o Error([dec]): [chars]
Explanation Shared memory operation failed.
Recommended Action Contact support.
Error Message%OS-LTRACE_SYNC-6-FILE_TOO_SHORT file [chars] is too short. size:[dec] version:[dec]
Explanation The file is read when it's being written, or version mismatch between the file and the reader.
Recommended Action Informational only. Indicates upgraded software accessed older version file before it's updated.
Error Message%OS-LTRACE_SYNC-6-FILE_WRONG_VERSION file [chars] has wrong version [dec], should be [dec]
Explanation The file has wrong version.
Recommended Action Informational only.
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.
Error Message%OS-LTRACE-7-STRING_SCALE scaling down string buffer [chars] (len:[dec]) by [dec]
Explanation Internal debugging message.
Recommended Action Informational only. Indicates card has less system memory
Error Message%OS-LTRACE-7-WRAP_SCALE scaling down wrap buffer [chars] (len:[dec]) by [dec]
Explanation Internal debugging message.
Recommended Action Informational only. Indicates card has less system memory
LWMESS Messages
Error Message%OS-LWMESS-7-CORRUPT_CLI [chars]: Corrupted channel list for [chars]. Memory lost, chan equals [pointer], infop equals [pointer], connectp equals [pointer] magic equals [hex] guard equals [hex]
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. Take a memory dump and try re-starting the offending application.
Error Message%OS-LWMESS-7-CORRUPT_CLI_SKIP [chars]: Corrupted channel list for [chars]. Iteration Skipped, chan equals [pointer], infop equals [pointer], connectp equals [pointer] magic equals [hex] guard equals [hex]
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. Take a memory dump and try re-starting the offending application.
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-3-INFRA_FAIL [chars] failed: [chars]
Explanation An error occurred while processing an infrastructure service request. This should happen mostly due to resource exhaustion.
Recommended Action Do the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
MPLS_VPN_MIB Messages
Error Message%OS-MPLS_VPN_MIB-3-ERR_DLL_LOAD Cannot load DLL: [chars]
Explanation Cannot load DLL 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-MPLS_VPN_MIB-3-ERR_DLL_SYMBOL_ERROR Cannot find symbol [chars] in DLL [chars]
Explanation Cannot find DLL symbol 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-MPLS_VPN_MIB-3-ERR_INIT [chars] : [chars]
Explanation Initialization failed
Recommended Action Enable 'debug mpls vpn init' and restart the process mpls_vpn_mib.
NCD Messages
Error Message%OS-NCD-3-INIT_ERR [chars]%s
Explanation An software error occurred during the initialization of the NCD process.
Recommended Action NCD will attempt to recover from this situation by restarting. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise, take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-NCD-3-PAK_CSUM_ERR Checksum failed on received packet; Pak:0x[pointer] Length:[dec] Offset:[dec] Computed Checksum:[unsigned int]
Explanation A checksum error was detected for a packet by NCD.
Recommended Action The clients of NCD will attempt to recover from this situation by retransmitting the packets. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise, take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
NQC Messages
Error Message%OS-NQC-3-PAK_CSUM_ERR Checksum failed on received packet; Pak:0x[pointer] Length:[dec] Offset:[dec] Computed Checksum:[unsigned int]
Explanation A checksum error was detected for a packet by NCD.
Recommended Action The clients of NCD will attempt to recover from this situation by retransmitting the packets. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise, take the following action. Copy the error message exactly as 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_LIB Messages
Error Message%OS-NRS_LIB-7-ERROR [chars]: info [hex]([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-7-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.'
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-INIT NRS Server restarting due to error [hex] in intialisation
Explanation An NRS Server hit an error from which it could not recover during initialisation and is restarting to continue normal operation.
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-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.
Error Message%OS-nrs-3-SHUTDOWN NRS Server restarting due to error during operation. Error [hex], [chars]
Explanation An NRS Server hit an error from which it could not recover and is restarting to continue normal operation.
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-7-EDM_INTERNAL [chars]: rc [hex], [chars]
Explanation The server's EDM 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-7-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.'
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.
OBFLINFRA_CLI Messages
Error Message%OS-OBFLINFRA_CLI-3-NO_MEMORY Failed in allocating memory with size:[dec]
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-OBFLINFRA_CLI-7-FAIL_TO_GET_SDD Fail to get sdd information, file size: [dec]
Explanation Fail to get sdd 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-OBFLINFRA_CLI-7-FILE_GARBAGE Garbage [dec] bytes at the end
Explanation File has garbage bytes at the end.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_CLI-7-invalid_historical_file_format Invalid historical file format. [chars]. field id: [dec]. Abort printing file contents.
Explanation Invalid historical file format.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_CLI-7-INVALID_RECORD_TYPE Invalid record type, type: [dec]
Explanation Invalid record 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-OBFLINFRA_CLI-7-JID_GET_ERROR process's JobID can not be obtained
Explanation process's JobID can not be obtained
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-OBFLINFRA_CLI-7-STRING_LENGTH_TOO_LONG The string([chars]) is longer than buffer length([dec]).
Explanation The string length is too long.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_CLI-7-SYMBOL_NOT_FOUND process(JobID:[dec]) notified symbol:[chars] but it is not found in dll:[chars]. Error:[chars]
Explanation A symbol notified from a process is not found
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-OBFLINFRA_CLI-7-UNABLE_TO_GET_NODENAME Unable to get the nodename of this card, file name: [chars]
Explanation Unable to get the nodename of this card
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
OBFLINFRA_CLIENT Messages
Error Message%OS-OBFLINFRA_CLIENT-7-APPLICATION_ERROR Failed to execute application function([chars]: [chars]), client_id:[dec], descriptor:[dec], error([dec]): [chars]
Explanation Failed to execute some application 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-OBFLINFRA_CLIENT-7-APPLICATION_REGIST_ERROR Failed to execute application registration function([chars]), nodeid:[hex], error([dec]): [chars]
Explanation Failed to execute application registration function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_CLIENT-7-ID_INVALID Invalid client_id [dec] is returned for feature:[chars] target_node:[hex].
Explanation Invalid client_id is 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-OBFLINFRA_CLIENT-7-JID_GET_ERROR process's JobID can not be obtained
Explanation process's JobID can not be obtained
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-OBFLINFRA_CLIENT-7-NO_MEMORY Failed in allocating memory with size:[dec]
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-OBFLINFRA_CLIENT-7-NODEID_FAILURE Failed to get nodeid for [chars]. Error([dec]): [chars]
Explanation Failed to get nodeid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_CLIENT-7-NUM_OF_SENSORS_OVERFLOW Cannot set more sensor ID than number of sensors([dec]).
Explanation Cannot set more sensor ID than number of sensors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_CLIENT-7-SENSOR_NOT_FOUND Sensor([dec]) is not found
Explanation No sensor found
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_CLIENT-7-TOO_LONG_FEATURE_NAME feature [chars] is too long name
Explanation Too long feature name is 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.
OBFLINFRA_DRIVER Messages
Error Message%OS-OBFLINFRA_DRIVER-3-JID_GET_ERROR process's JobID can not be obtained
Explanation process's JobID can not be obtained
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-OBFLINFRA_DRIVER-7-NODEID_FAILURE [chars] of nodeid for [chars] failed. Error([dec]): [chars]
Explanation An error happened for a nodeid 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-OBFLINFRA_DRIVER-7-TOO_LONG_DEVICE_NAME device [chars] is too long name
Explanation Too long device name is 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.
OBFLINFRA_INT Messages
Error Message%OS-OBFLINFRA_INT-3-EVM_ERROR [chars], Error([dec]): [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-OBFLINFRA_INT-3-INVALID_RECORD_MAGIC_NUM Invalid record magic number: [hex]. [hex] is expected. Abort reading the file contents.
Explanation Invalid magic number
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-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-OBFLINFRA_INT-3-NO_MEMORY Failed to allocate memory with size:[dec] at [chars]:[dec]
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-OBFLINFRA_INT-3-NO_PLATFORM_DATA_FILE platform data file:[chars] doesn't exist
Explanation The platform data file doesn't exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-3-NO_SERVER_FOUND no destination OBFL manager found
Explanation Destination OBFL manager path is not found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-3-NODEID_FAILURE [chars] of nodeid for [chars] failed. Error([dec]): [chars]
Explanation An error happened for a nodeid 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-OBFLINFRA_INT-3-NODEID_GET_FAILURE nodeid for [chars] can not be obtained
Explanation Self nodeid can not be obtained.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-3-PLATFORM_DATA_FILE_ERROR platform data file:[chars] scan failed. Error([dec]): [chars]
Explanation An error happened while reading the platform 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-OBFLINFRA_INT-3-PTHREAD_ERROR [chars] failed. Error([dec]): [chars] : [chars]:[dec]
Explanation Failed in a pthread function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-3-RECORD_TOO_SHORT Too short record size:[dec] for [chars] record. The file contents might be corrupted.
Explanation A feature record is too short.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-3-RECORD_TYPE_MISMATCH Type mismatch for [chars] record. Record_type:[dec] My_type:[dec].
Explanation A feature record has different type with current software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-3-RECORD_VERSION_MISMATCH Version mismatch for [chars] record. Record_version:[dec] My_version:[dec].
Explanation A feature record has different version format with current software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-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-OBFLINFRA_INT-4-JID_GET_ERROR process's JobID can not be obtained
Explanation process's JobID can not be obtained
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-OBFLINFRA_INT-4-MSG_RESEND_ERROR [chars] [chars]. Error([dec]): [chars]
Explanation Failed in re-sending a message after onboard logging server process resart.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-4-UNSUPPORTED_API Unsupported API [chars] called by process [chars]
Explanation The call is not supported by OBFL infra.
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-OBFLINFRA_INT-5-MSG_CKSUM_DATA_ERROR Received a corrupted message data with cksum:[hex] Calculated cksum:[hex] length:[dec] type:[dec]
Explanation The message received by an application had a wrong cksum value. The message data could be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-5-MSG_CKSUM_HDR_ERROR Received a corrupted message header with cksum:[hex] Calculated cksum:[hex] length(corrupted?):[dec] type(corrupted?):[dec]
Explanation The message received by an application had a wrong cksum value. The message data could be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-5-MSG_REPLY_ERROR Received message has wrong reply data:0x[pointer] data_len:[dec] actual_data_len:[dec]
Explanation The message received by an application had a wrong reply data. The message data could be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-6-EXIT process terminated with code:[dec] at [chars]:[dec]
Explanation An OBFL process 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-OBFLINFRA_INT-7-BUFFER_GARBAGE Garbage [dec] bytes at the end of a buffer for [chars]
Explanation A buffer has garbage bytes at the end.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-7-DEBUG_CONNECT [chars]:[dec] server:[chars]
Explanation debug print before msg_chan_connect
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-7-DEBUG_QSM [chars]:[dec] server:[chars]
Explanation debug print before qsm_stat
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-7-DEBUG_SENDV [chars]:[dec] conn:[pointer] target_node:[pointer]
Explanation debug print before msg_sendv
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-7-FILE_ERROR [chars] [chars]. Error([dec]): [chars]
Explanation An error happened in a file 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-OBFLINFRA_INT-7-RECORD_TOO_LONG Too long record size:[dec] for [chars] record. The file contents might be corrupted.
Explanation A feature record is too long.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-7-SLOT_DECODE_FAILURE decoding of rack:[hex] and slot:[hex] for [chars] failed. Error([dec]): [chars]
Explanation An error happened for a nodeid decoding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLINFRA_INT-7-TOO_LONG_NAME [chars] [chars] is too long name
Explanation Too long name is 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.
OBFLMGR Messages
Error Message%OS-OBFLMGR-3-CHECKSUM_ERROR checksum for [chars] is wrong. Original:[hex] Calculated:[hex] offset:[dec]. The contents of [chars] could be corrupted.
Explanation A checksum of a record is wrong. The file could be corrupted. The file should be saved to other place for later debugging, and then it should be removed to recover current situation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-ENV_STATIC_DATA_ERROR Failed to [chars] env static data record. Error([dec]): [chars]
Explanation An environment record data processing 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-OBFLMGR-3-EVENT_CONN_CREATION_ERROR Failed to create event connection. Error: [chars]
Explanation Failed to create event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-EVENT_CONN_NOTIFY_ERROR Failed to attach a handler for an event connection. Error: [chars]
Explanation Failed to attach a handler for an event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-EVENT_CONN_OPEN_ERROR Failed to open an event connection. Error: [chars]
Explanation Failed to open an event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-EVM_ERROR [chars], Error([dec]): [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-OBFLMGR-3-FILE_SIZE_GET_FAILURE file size for [chars] can not be obtained from platform DB
Explanation An OBFL file size can not be obtained from platform DB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-FILELIMIT_TOO_SMALL A file's max limit is too small for [chars], or internal parameters might be corrupted. cur_data_size:[dec] file_size_limit:[dec].
Explanation A file's max limit is too small, or internal parameter might be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-HISTGROUP_TOO_LARGE Too large historical group for [chars], or internal parameters might be corrupted. cur_data_size:[dec] writing_group_size:[dec] file_size_limit:[dec].
Explanation A historical group is too large, or internal parameter might be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-LWM_ERROR [chars], Error([dec]): [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-OBFLMGR-3-MSG_VER_MISMATCH Msg:[chars] version:[dec] mismatch from jid:[dec]. Correct version:[dec].
Explanation A msg from an application has different version format with current software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-MUTEX_RESET_ERROR Mutex reset error. Exit and restart the process
Explanation Failed to reset a corrupted mutex. Restart 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-OBFLMGR-3-NO_FINAL_CLEAR_RECORD A file [chars] doesn't have its final clear record after compressed records, or internal parameters might be corrupted. cur_data_size:[dec] file_size_limit:[dec].
Explanation A file don't have its final clear record which is necessary for coalescing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-RECORD_LENGTH_UNMATCH A record length:[dec] and the LWM msg_length:[dec] doesn't match for [chars] feature
Explanation The message received by an application had inconsistent record length.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-RECORD_TOO_SHORT Too short record size:[dec] for [chars] record at offset:[dec]. The file contents might be corrupted.
Explanation A feature record is too short.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-RECORD_VERSION_MISMATCH Version mismatch for [chars] record at offset:[dec]. Record_version:[dec] My_version:[dec].
Explanation A feature record has different version format with current software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-REDUNDANCY_INIT_ERROR [chars], Error([dec]): [chars]
Explanation Failed to init redundancy state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-SM_CALLBACK_ERROR [chars] [chars] failed. Error([dec]): [chars]
Explanation Failure in self management callback routine.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-SYMBOL_NOT_FOUND process(JobID:[dec]) notified symbol:[chars] for owner:[chars], but it is not found. Error:[chars]
Explanation A dll notified from a client is not found
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-OBFLMGR-3-SYSDB_BIND_ERROR Sysdb bind failed for [chars] [chars]. Error([dec]): [chars]
Explanation Sysdb bind 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-OBFLMGR-3-SYSDB_EDM_INIT_ERROR Falied edm initialization. Error: [chars]
Explanation Falied edm initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-SYSDB_REG_EDM_ERROR sysdb registration edm error. Error: [chars]
Explanation Registration fail for sysdb edm.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-SYSDB_REG_NOTIFY_ERROR sysdb registration (notification) error, [chars] [chars], [chars]
Explanation Registration fail for sysdb notification
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-SYSDB_REG_VERIFY_ERROR sysdb registration (verification) error, [chars] [chars], [chars]
Explanation Registration fail for sysdb verification
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-3-UNLOAD_DLL_FAILED previous DLL:[chars] notified from process(JobID:[dec]) for FEATURE:[chars] can not be unloaded. Error:[chars]
Explanation An old DLL can not be unloaded
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-OBFLMGR-4-CLI_MSG_ERROR Received a bad message with value:[dec]: [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-OBFLMGR-4-CLIENTID_ERROR client_id:[dec] specified from process(JobID:[dec]) caused an error:[chars]
Explanation Specified client ID caused an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-4-DEVCTL_ERROR Failed to get ReloadReason. Return:[dec], result:[dec].
Explanation devctl 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-OBFLMGR-4-DEVICE_CREATED_AND_DISABLED device:[chars] on node:[chars] is disabled by user configuration
Explanation A device is disabled for logging onboard by user configuration.
Recommended Action No action is required.
Error Message%OS-OBFLMGR-4-DEVICE_DEACTIVATED device:[chars](nodeid:[hex]) is deactivated for onboard logging due to [dec] times write error to file:[chars]. The last Error([dec]): [chars]
Explanation The device on the node is deactivated for onboard logging.
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-OBFLMGR-4-DEVICE_DISABLED device:[chars] on node:[chars] is disabled by user configuration
Explanation A device is disabled for logging onboard by user configuration.
Recommended Action No action is required.
Error Message%OS-OBFLMGR-4-FEATURE_DEACTIVATED feature:[chars] on device:[chars](nodeid:[hex]) failed to get platform information from [chars], and is deactivated
Explanation A feature is deactivated because it couldn't get platform information from a new platform library.
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-OBFLMGR-4-FILE_ERROR file:[chars](fp:[pointer], fd:[dec]) [chars] failing. [dec] retry so far. Error([dec]): [chars]
Explanation Failed to open/close an OBFL 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-OBFLMGR-4-FILE_OPEN_ERROR [chars] can not be opened. Error([dec]): [chars]
Explanation File open 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-OBFLMGR-4-FILE_WRITE_ERROR Tried to write [dec] bytes to file: [chars](total size [dec]). Error([dec]): [chars]
Explanation File write 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-OBFLMGR-4-QUEUE_CLEAR_ERROR queue clear error. elems:[dec] first:[pointer] last:[pointer]
Explanation failed to clear internal queue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-4-UNSUPPORTED_FEATURE Unsupported FEATURE: [chars] called by a process(JobID:[dec])
Explanation The feature is not supported by OBFL.
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-OBFLMGR-4-UPTIME_RR_NOT_SET ResetReason is not set.
Explanation ResetReason is not yet set.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-5-CORRUPTED_MSG Received a corrupted message for [chars] with value:[dec]: [chars]
Explanation The message received by an application 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-OBFLMGR-5-MSG_CKSUM_ERROR Received a corrupted message with cksum:[hex] Calculated cksum:[hex] length(corrupted?):[dec] type(corrupted?):[dec]
Explanation The message received by an application had a wrong cksum value. The message data could be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-6-DEVICE_ACTIVATED device:[chars](nodeid:[hex]) is activated for onboard logging.
Explanation The device on the node is activated for onboard logging.
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-OBFLMGR-6-DEVICE_ENABLED device:[chars] on node:[chars] is enabled by user configuration
Explanation A device is enabled for logging onboard by user configuration.
Recommended Action No action is required.
Error Message%OS-OBFLMGR-6-FEATURE_ACTIVATED feature:[chars] on device:[chars](nodeid:[hex]) is activated
Explanation A deactivated feature is activated.
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-OBFLMGR-7-COALESCE_ERROR Coalescing failed for feature:[chars] device:[chars](node:[hex]) because [chars].
Explanation Coalescing failed on a device. Records for the device will be discarded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-COALESCER_NOT_FOUND process(JobID:[dec]) notified coalescer:[chars] for FEATURE:[chars], but it is not found
Explanation A coalesce function name notified from a client is not found
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-OBFLMGR-7-DEVICE_INACTIVE device on the node(ID:[hex]) is not active
Explanation The device on the node is not 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-OBFLMGR-7-DEVICE_NOT_READY no device ready for feature:[chars] from process(JobID:[dec]). target_node:[hex] client_id:[dec] device:[pointer].
Explanation no device ready yet for notified feature
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-DEVICE_NOT_REGISTERED device:[chars] notified from process(JobID:[dec]) is not registered
Explanation Caller's device is not yet registered
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-DEVICE_UNAVAILABLE device [chars] on nodeid:[hex] is not accessible on the filesystem. Error([dec]): [chars]
Explanation A device specified from a driver is not accessible.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-ENV_STATE_UNKNOWN Unknown environment state:[dec] of node:[hex]
Explanation An environment record has an unknown 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-OBFLMGR-7-ERRMSG_HIST_FULL Syslog histrical file buffer reached the limit. Current size:[dec]. limit:[dec]. Subsequent syslog historical records will be discarded.
Explanation Syslog historical file reached the limit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-JID_GET_ERROR process's JobID can not be obtained
Explanation process's JobID can not be obtained
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-OBFLMGR-7-MAGIC_NUM_INVALID Invalid magic number:[hex] for [chars] record. [hex] is expected. The file contents might be corrupted.
Explanation A feature record has an invalid magic number.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-META_OPER_WRITE_ERROR Failed to write [chars] meta oper record to the file:[chars]. Error([dec]): [chars]
Explanation An OBFL internal record type write 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-OBFLMGR-7-MSG_ERROR Received a bad message with value:[dec]: [chars]
Explanation The message received by an application 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-OBFLMGR-7-NO_MEMORY Failed to allocate memory with size:[dec] at [chars]:[dec]
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-OBFLMGR-7-NODEID_DECODE_FAILURE decoding of nodeid:[hex] for [chars] failed. Error([dec]): [chars]
Explanation An error happened for a nodeid decoding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-NODEID_FAILURE [chars] of nodeid for [chars] failed. Error([dec]): [chars]
Explanation An error happened for a nodeid 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-OBFLMGR-7-QUEUE_LIMIT_OVER The queue:[pointer] for device:[chars] entry_num:[dec] and the max limit:[dec]. The new request for [chars] will be discarded.
Explanation The destination queue is full. New enqueue request will be discarded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-RACK_DECODE_FAILURE decoding of rack:[hex] for [chars] failed. Error([dec]): [chars]
Explanation An error happened for a rackid decoding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-RECORD_TOO_LONG Too long record size:[dec] for [chars] record. The file contents might be corrupted.
Explanation A feature record is too long.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-RECORD_TYPE_UNKNOWN Unknown record type:[dec] for [chars] record. The file contents might be corrupted.
Explanation A feature record has an unknown record 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-OBFLMGR-7-REDUNDANCY_STANDBY logging to node:[hex] is denied because this node:[hex] is redundancy standby state.
Explanation Node is redundancy standby state, so can't log to other node.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-SLOT_DECODE_FAILURE decoding of rack_type:[hex] and slot:[hex] for [chars] failed. Error([dec]): [chars]
Explanation An error happened for a slot fields decoding.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-SYSDB_TUPLE_ERROR [chars] sysdb tuple, [chars] at [chars]:[dec]
Explanation Invalid sysdb tuple
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-UNREGISTERED_FEATURE Unregistered FEATURE:[chars] called by a process(JobID:[dec])
Explanation The specified feature is not yet registered for OBFL manager.
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-OBFLMGR-7-UPTIME_CONT_TOO_LARGE Too large continuous record, or internal parameters might be corrupted. length:[dec].
Explanation A continuous record too large, or internal parameter might be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-UPTIME_HIST_INVALID_TASKID Invalid block_and_task_id:[hex]. The file contents might be corrupted.
Explanation This record has invalid block_and_task_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-OBFLMGR-7-UPTIME_HIST_TOO_LARGE Too large historic uptime record([chars]), or internal parameters might be corrupted. length:[dec] offset_ehud:[dec].
Explanation A historic uptime record too large, or internal parameter might be corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-OBFLMGR-7-UPTIME_RECORD_NOT_FOUND Uptime record([chars]) is not found.
Explanation Uptime record is not found
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.
PA Messages
Error Message%OS-PA-2-CTX_CREATE [chars]: Can't create VRF context structures. VRF '[chars]' ([hex]) error [chars] ([unsigned int])
Explanation PA Can't create VFR context structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PA-2-IFIB_LIMIT IFIB entries threshold exceeded in LPTS - [chars]
Explanation The number of IFIB entires in lpts has exceeded the threshold limit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PA-2-INFRA_FAIL [chars]: [chars] failed rc equals [dec]
Explanation There was a ENA infra call failure resulting in a failure to provide some infrastructure service.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%OS-PA-2-RSI_ERROR RSI [chars] failed error [chars] ([unsigned int])
Explanation RSI 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-PA-2-RSI_UNKNOWN_EVENT Unknown event from RSI event [unsigned int]
Explanation RSI sent unknown event
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PA-3-ECM_SETRETRY_FAIL Error setting linear connection retry mechanism : [chars]
Explanation Failed to set linear connection retry mechanism in Port Arbitrator 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-PA-3-ERR_ADD_SLICE [chars]: Assign of slice [chars] to node [hex] failed. ([chars])
Explanation The PA failed to assign an IFIB slice.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PA-3-ERR_BACKEND [chars]: [chars] failed
Explanation Sysdb backend api 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-PA-3-ERR_BAG [chars]: [chars] failed: [chars]
Explanation Bag api 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-PA-3-ERR_FM_MSG_TIMEOUT [chars]: [chars] update of slice [chars] to node [hex] timed out.
Explanation The PA failed to receive a response to an IFIB table update or an IFIB slice assignment update 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-PA-3-ERR_LOCK [chars] line [dec]: error: [chars]
Explanation An attempt to lock a mutex 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-PA-3-ERR_PIFIB_MSG_TIMEOUT [chars]: Pre-IFIB update for slice [chars] timed out.
Explanation The PA failed to receive a response to a critical Pre-IFIB update.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PA-3-ERR_SYSDB [chars]: [chars] failed
[chars]Explanation Sysdb api 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-PA-3-ERR_UNLOCK [chars] line [dec]: error: [chars]
Explanation An attempt to lock a mutex 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-PA-3-EVENT_REGISTRATION_FAILED PA failed to connect to the event manager: [chars]
Explanation The PA process failed while attempting to connect to an event manager channel for the indicated subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PA-6-INFO_GENERAL [chars]: [chars]
Explanation The PA encountered some problem in genric nature or plain information.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
PCDS Messages
Error Message%OS-PCDS-3-ERROR [chars] failed: [chars]
Explanation Required functionality failed or returned an error
Recommended Action Contact support.
Error Message%OS-PCDS-7-DEBUG [chars] [chars] [chars]
Explanation Internal debugging message.
Recommended Action Informational only.
PLACED_LIB Messages
Error Message%OS-PLACED_LIB-7-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.
Error Message%OS-PLACED_LIB-7-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.
PLACED_MAIN Messages
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. Reason: [chars]
Explanation The process 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.
Error Message%OS-PLACED_MAIN-7-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-7-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-7-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-7-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-7-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-7-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-7-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-7-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 None - PlaceD should restart and recover by itself. If the message recurs: Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-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-7-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-7-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 None - PlaceD should restart and recover by itself. If the message recurs: Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_MAIN-7-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-7-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-7-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-7-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-7-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-7-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-7-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-7-SIGNALS Failed to set up signal mask: [chars]
Explanation One of the OS calls to set up the thread signal mask failed, and therefore PlaceD couldn't initialise.
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-7-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-7-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-7-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-7-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-7-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-7-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.
PLACED_NODES Messages
Error Message%OS-PLACED_NODES-3-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-7-DOWNGRADING_NODE System call to node [chars] indicated that node is not yet booted. Downgrading state to [unsigned int]
Explanation An error encountered while querying a remote node indicated that the target location was not in the running state. PlaceD has downgraded the node accordingly.
Recommended Action Copy the error message exactly as it appears on 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-7-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-7-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-7-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-7-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-7-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-7-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-7-NO_INVENTORY The LR inventory is empty or not available (despite waiting for over a minute for it) - error '[chars]'. PlaceD cannot function without this information, so will restart and attempt to wait for the information again.
Explanation Placement requires a complete knowledge of the LR inventory in order to function as expected. The LR inventory is currently not fully populated, so PlaceD is restarting in order to give the LR inventory time to finish initialising. If this message continues to appear, this indicates that the LR information is not able to complete, and that this will be affecting the ability of the system to function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_NODES-7-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-7-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-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. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, 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. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, 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-REOP_ABORTED Re-optimization of the placement aborted due to [chars]. Placement has been partially re-optimized. Running the command again will complete the re-optimization
Explanation The re-optimization of the placement was aborted because PlaceD had to respond to a change in the router environment.
Recommended Action Run the 'placement reoptimize' command again to complete the re-optimization.
Error Message%OS-PLACED_PLACE-5-RESTARTING Program [chars]%s[chars] has now been started (was previously unable to run)
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. This message may also result from problems in retrieving the node inventory for the router.
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. If a node inventory problem is suspected: Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, call your Cisco technical support representative and provide the representative with the gathered information.
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.
Error Message%OS-PLACED_PLACE-6-REOP_COMPLETE Re-optimization of the placement complete. Use 'show placement' to view the new placement
Explanation The re-optimization of the placement has completed.
Recommended Action Use the 'show placement' command to view the newly re-optimized placement.
Error Message%OS-PLACED_PLACE-6-REOP_START Re-optimization of the placement requested. You will be notified on completion
Explanation A re-optimization of the placement has started. The most optimal location of each program will be re-calculated by ignoring any affinity of the default program to the current location. Any resulting migrations will be rate limited accoring to the slow migration interval configured for each program.
Recommended Action Wait for the notification that the re-optimization has completed before adding or removing cards from the router, adding new configuration, or starting a new re-optimization.
Error Message%OS-PLACED_PLACE-7-AFFINITY_ITERATOR Unable to obtain affinity iterator for [chars]
Explanation PlaceD was unable to obtain an iterator for all the affinities.
Recommended Action This is non-critical, and in the absence of other errors, simply means that one facility (triggering reoptimisation of placements by the user) is inoperable.
Error Message%OS-PLACED_PLACE-7-ALGO_INIT Unable to create placement algorithm
Explanation PlaceD was unable to create the placement algorithm object, 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-7-CHKPT_INIT Failed to initialize checkpoint store: [chars]
Explanation PlaceD was unable to initialize the checkpoint store for the placement package, 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_PLACE-7-CHKPT_UPDATE Failed to update checkpoint record for re-optimization status: [chars]
Explanation PlaceD was unable to update the checkpointed information indicating whether a placement re-optimization is in progress.
Recommended Action This should not be a service-affecting incident. However, PlaceD may no longer be able to correctly report the completion of re-optimization events. Copy the error message exactly as it appears on 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-7-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. Issue the show tech-support placement command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support placement output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLACED_PLACE-7-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-7-TIMER Unable to [chars] persistence timer
Explanation PlaceD was unable to create the persistence 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*
PLACED_PROGS Messages
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-PROC_STATE Unable to determine process placement information for process '[chars]%s[chars]' at location [chars]: [chars]
Explanation PlaceD was unable to respond accurately to a placement request from SysMgr on a remote node.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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-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-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-4-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-4-RMPROC_INCORRECT_NODE Ignoring request from '[chars]' to remove process '[chars]%s[chars]'
Explanation Request to remove the process came from a node on which the process is not currently running. PlaceD will ignore this 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-4-START_PROC_MIGRATE Process '[chars]%s[chars]' cannot be migrated to the location pair [chars] [chars] because the pair is no longer up
Explanation PlaceD was unable to migrate the specified process to the specified locations because they are no longer up. If necessary, an alternative location will be selected for the process.
Recommended Action If the specified location pair is still up: Copy the error message exactly as it appears on 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-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-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 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.
Error Message%OS-PLACED_PROGS-7-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-7-CLASS_INFO Failed to get all program info from SysMgr at location [chars]: [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-7-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-7-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-7-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-7-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-7-PLPROC Failed to service a place-processes request from cfgmgr: [chars]
Explanation PlaceD was asked by cfgmgr about the location of a list of processes, 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-7-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-7-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-7-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-7-TIMEOUT Ignoring timeout event with unknown [chars]
Explanation A timeout event occurred, but PlaceD was unable to determine which program or node 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-7-TIMERS Unable to initialize request timers
Explanation PlaceD was unable to initialize the request 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-7-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-7-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.
PLACED_PROPS Messages
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-5-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-5-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-5-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 program [instance 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.
Error Message%OS-PLACED_PROPS-7-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-7-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.
PLATFORM_LPTS_COM_IFIB Messages
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-CONFIG_MISSING_FLOW [chars]: Flow type '[chars]' not configured
Explanation error in IFIB flow handling configuration. The named flow type was not explicitly configured and will have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-CONFIG_MISSING_FLOW [chars]: Flow type '[chars]' not configured
Explanation error in IFIB flow handling configuration. The named flow type was not explicitly configured and will have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-CONFIG_MISSING_PARAMETER [chars]: Missing parameter after '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-CONFIG_MISSING_PARAMETER [chars]: Missing parameter after '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-CONFIG_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-CONFIG_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-CONFIG_UNKNOWN_PARAMETER [chars]: Unknown parameter '[chars]' after '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-CONFIG_UNKNOWN_PARAMETER [chars]: Unknown parameter '[chars]' after '[chars]' in flow '[chars]'
Explanation Syntax error in IFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-ERR_MEM_ALLOC Failed to allocate memory
Explanation The system failed to allocate memory. It's likely that the system is running low in memory.
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-PLATFORM_LPTS_COM_IFIB-3-ERR_MEM_ALLOC Failed to allocate memory
Explanation The system failed to allocate memory. It's likely that the system is running low in memory.
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-PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG [chars]: Missing configuration for IFIB flow handling
Explanation No configuration for IFIB flow handling was found. Default characteristics will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG [chars]: Missing configuration for IFIB flow handling
Explanation No configuration for IFIB flow handling was found. Default characteristics will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG_MEMORY [chars]: Insufficient memory for IFIB flow handling configuration
Explanation Insufficient memory was available for storing the IFIB flow handling configuration. Default characteristics will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-3-NO_CONFIG_MEMORY [chars]: Insufficient memory for IFIB flow handling configuration
Explanation Insufficient memory was available for storing the IFIB flow handling configuration. Default characteristics will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when calling debug_cleanup() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when calling debug_cleanup() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when calling the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when calling the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when calling debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when calling debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
Error Message%OS-PLATFORM_LPTS_COM_IFIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
PLATFORM_LPTS_COM_NETIO Messages
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when calling debug_cleanup() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when calling the debug_init_event() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when calling debug_register() function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_COM_NETIO-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLATFORM_LPTS_LIB Messages
Error Message%OS-PLATFORM_LPTS_LIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
Error Message%OS-PLATFORM_LPTS_LIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
Error Message%OS-PLATFORM_LPTS_LIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
PLATFORM_LPTS_PIFIB Messages
Error Message%OS-PLATFORM_LPTS_PIFIB-3-BACKEND_EDM [chars]: EDM backend function [chars] failed: [chars]
Explanation An internal EDM backend function 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-PLATFORM_LPTS_PIFIB-3-BAG [chars]: Bag function [chars] failed: [chars]
Explanation An internal bag function 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-PLATFORM_LPTS_PIFIB-3-CHKPT_INIT [chars]: Checkpoint Initialization function [chars] failed: [chars]
Explanation An internal Checkpoint function 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-PLATFORM_LPTS_PIFIB-3-CONFIG_FLOW_MEMORY [chars]: Insufficient memory for flow configuration
Explanation There is insufficient memory for the flow configuration. All flows will be assigned default characteristics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-CONFIG_MISSING_FLOW [chars]: Flow type '[chars]' not configured
Explanation error in PIFIB flow handling configuration. The named flow type was not explicitly configured and will have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-CONFIG_MISSING_PARAMETER [chars]: Missing parameter after '[chars]' in flow '[chars]'
Explanation Syntax error in PIFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_MEMORY [chars]: Insufficient memory for policer configuration
Explanation There is insufficient memory for the policer configuration. All flows will be assigned default characteristics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_PARAMETER_INVALID [chars]: Invalid parameter '[chars]' after '[chars]' in policer '[dec]' definition
Explanation There is an invalid parameter after a keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_PARAMETER_MISSING [chars]: Missing parameter after '[chars]' in policer '[dec]' definition
Explanation There is a missing required parameter after a keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-CONFIG_POLICER_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in policer '[dec]' definition
Explanation There is an unknown keyword in a policer definition. The policer may be assigned default characterstics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-CONFIG_UNDEFINED_POLICER [chars]: flow '[chars]' references undefined policer '[dec]'
Explanation An input flow definition references an undefined policer. The flow will be configured to use policer 0.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-CONFIG_UNKNOWN_KEYWORD [chars]: Unknown keyword '[chars]' in flow '[chars]'
Explanation Syntax error in PIFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-CONFIG_UNKNOWN_PARAMETER [chars]: Unknown parameter '[chars]' in flow '[chars]'
Explanation Syntax error in PIFIB flow handling configuration. The named flow type may have default characteristics applied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-ERR_IFH_UIDB_INDEX Failed to find uidb index for interface handle [hex]
Explanation Failed to find uidb index for an given interface handle. It is likely to be caused by a programming bug or a programming problem happened in the past.
Recommended Action Run the command 'show uidb index' to verify whether the uidb index is created for the interface. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-ERR_IFH_UIDB_INDEX Failed to find uidb index for interface handle [hex]
Explanation Failed to find uidb index for an given interface handle. It is likely to be caused by a programming bug or a programming problem happened in the past.
Recommended Action Run the command 'show uidb index' to verify whether the uidb index is created for the interface. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-ERR_IFH_UIDB_INDEX Failed to find uidb index for interface handle [hex]
Explanation Failed to find uidb index for an given interface handle. It is likely to be caused by a programming bug or a programming problem happened in the past.
Recommended Action Run the command 'show uidb index' to verify whether the uidb index is created for the interface. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-ERR_IPV6_COMPRESS Failed to perform IPV6 compress, tm_rc equals [hex], prefix_len equals [hex]
Explanation The IPv6 compression fail under fatal error condition.
Recommended Action When this issue happens, it will trigger an automatic restart.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-ERR_MEM_ALLOC Failed to allocate memory
Explanation The system failed to allocate memory. It's likely that the system is running low in memory.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-3-ERR_MEM_ALLOC Failed to allocate memory
Explanation The system failed to allocate memory. It's likely that the system is running low in memory.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-3-ERR_MEM_ALLOC Failed to allocate memory
Explanation The system failed to allocate memory. It's likely that the system is running low in memory.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-3-ERR_NOTIF_Q_FULL The queue for notifications from [chars] is full
Explanation Too many notifications have been sent to the component. The queue to hold the notification has overflowed.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-3-ERR_NOTIF_Q_FULL The queue for notifications from [chars] is full
Explanation Too many notifications have been sent to the component. The queue to hold the notification has overflowed.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-3-ERR_NOTIF_Q_FULL The queue for notifications from [chars] is full
Explanation Too many notifications have been sent to the component. The queue to hold the notification has overflowed.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-3-EVENT_CONN_CREATE [chars]: could not create event connection: [chars]
Explanation An internal error was detected when trying to create event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-EVENT_CONN_OPEN [chars]: could not open event connection: [chars]
Explanation An internal error was detected when trying to open event connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-FM_ADD_FEAT2GRP [chars]: fm add feat to group failed for ISIS [chars]
Explanation An internal fm add feature to group function 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-PLATFORM_LPTS_PIFIB-3-FM_ADD_IFH2GRP [chars]: fm add ifh to group failed for ISIS [chars]
Explanation An internal fm add ifh to group function 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-PLATFORM_LPTS_PIFIB-3-FM_CREATE_GROUP [chars]: fm create group failed: [chars]
Explanation An internal fm create group function 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-PLATFORM_LPTS_PIFIB-3-FM_FEAT_PROCESSING [chars]: fm feature registration failed: [chars]
Explanation An internal fm feature registration function 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-PLATFORM_LPTS_PIFIB-3-FM_REGISTER [chars]: fm_register failed: [chars]
Explanation An internal fm_register function 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-PLATFORM_LPTS_PIFIB-3-HFA_REGISTER [chars]: hfa_register failed: [chars]
Explanation An internal hfa_register function 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-PLATFORM_LPTS_PIFIB-3-LTRACE_INIT [chars]: ltrace_init2 failed: [chars]
Explanation An internal ltrace_init2 function 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-PLATFORM_LPTS_PIFIB-3-MSG_ATTACH [chars]: Event Mgr function [chars] failed: [chars]
Explanation An internal Event Manager function 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-PLATFORM_LPTS_PIFIB-3-NO_CONFIG [chars]: Missing configuration for PIFIB flow handling
Explanation No configuration for PIFIB flow handling was found. Default characteristics will be used for all packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-3-SHOW_EDM_CLOSE [chars]: Cleanup for EDM failed: [chars]
Explanation Cleanup for EDM 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-PLATFORM_LPTS_PIFIB-3-SHOW_EDM_INIT [chars]: Initialization for show EDM failed: [chars]
Explanation Initialization for show EDM 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-PLATFORM_LPTS_PIFIB-3-SYSDB [chars]: Sysdb function [chars] failed: [chars]
Explanation An internal sysdb function 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-PLATFORM_LPTS_PIFIB-3-TCAM_FMT_TO_HFA_MAP [chars]: vmr_builder_program_tcam_fmt_from_hfa_map failed: [chars]
Explanation An tcam format to hfa mapping function 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-PLATFORM_LPTS_PIFIB-5-ERR_MSTATS_ALLOC Failed to allocate HW counters.
Explanation It failed to allocate HW counters. It may be because of running out of HW counters or encountering internal error.
Recommended Action Disable the numbers of non crucial services which use HW counters.
Error Message%OS-PLATFORM_LPTS_PIFIB-5-ERR_MSTATS_ALLOC Failed to allocate HW counters.
Explanation It failed to allocate HW counters. It may be because of running out of HW counters or encountering internal error.
Recommended Action Disable the numbers of non crucial services which use HW counters.
Error Message%OS-PLATFORM_LPTS_PIFIB-5-ERR_PRM_STATS_ALLOC Failed to allocate HW counters.
Explanation It failed to allocate HW counters. It may be because of running out of HW counters or encountering internal error.
Recommended Action Disable the numbers of non crucial services which use HW counters.
Error Message%OS-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_INVALID_REG_NAME Found the Pre-IFIB region with unrecognized name: [chars]
Explanation A Pre-IFIB region with unrecognized name is found in the TCAM. It is likely caused by a programming bug or a programming problem happened in the past.
Recommended Action Check the status of TCAM Manger because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_INVALID_REG_NAME Found the Pre-IFIB region with unrecognized name: [chars]
Explanation A Pre-IFIB region with unrecognized name is found in the TCAM. It is likely caused by a programming bug or a programming problem happened in the past.
Recommended Action Check the status of TCAM Manger because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_INVALID_REG_NAME Found the Pre-IFIB region with unrecognized name: [chars]
Explanation A Pre-IFIB region with unrecognized name is found in the TCAM. It is likely caused by a programming bug or a programming problem happened in the past.
Recommended Action Check the status of TCAM Manger because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_OVERFLOW Does not have enough space for the Pre-IFIB entry in TCAM region [chars]
Explanation TCAM space is not enough for all Pre-IFIB entries in the particular TCAM region. All control packets which do not have matching Pre-IFIB entries in TCAM will use SW path to forward to destinations.
Recommended Action Disable the numbers of services configured for the system.
Error Message%OS-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_OVERFLOW Does not have enough space for the Pre-IFIB entry in TCAM region [chars]
Explanation TCAM space is not enough for all Pre-IFIB entries in the particular TCAM region. All control packets which do not have matching Pre-IFIB entries in TCAM will use SW path to forward to destinations.
Recommended Action Disable the numbers of services configured for the system.
Error Message%OS-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_OVERFLOW Does not have enough space for the Pre-IFIB entry in TCAM region [chars]
Explanation TCAM space is not enough for all Pre-IFIB entries in the particular TCAM region. All control packets which do not have matching Pre-IFIB entries in TCAM will use SW path to forward to destinations.
Recommended Action Disable the numbers of services configured for the system.
Error Message%OS-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_PREFIX_COMPRESS Failed to have IPv6 prefix compressed
Explanation IPv6 prefix compression failed because the line card has run out of internal resources for compressing a preifx. It shouldn't have any major impact on the system service. The in-bound (destined to the system) packets can still reach destinations through SW path.
Recommended Action Try either change the prefix length or change the prefix value of IPv6 addressses used in the system if possible.
Error Message%OS-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_PREFIX_COMPRESS Failed to have IPv6 prefix compressed
Explanation IPv6 prefix compression failed because the line card has run out of internal resources for compressing a preifx. It shouldn't have any major impact on the system service. The in-bound (destined to the system) packets can still reach destinations through SW path.
Recommended Action Try either change the prefix length or change the prefix value of IPv6 addressses used in the system if possible.
Error Message%OS-PLATFORM_LPTS_PIFIB-5-ERR_TCAM_PREFIX_COMPRESS Failed to have IPv6 prefix compressed
Explanation IPv6 prefix compression failed because the line card has run out of internal resources for compressing a preifx. It shouldn't have any major impact on the system service. The in-bound (destined to the system) packets can still reach destinations through SW path.
Recommended Action Try either change the prefix length or change the prefix value of IPv6 addressses used in the system if possible.
Error Message%OS-PLATFORM_LPTS_PIFIB-7-DEBUG_CLEANUP [chars]: Debug cleanup failed: [chars]
Explanation An error was returned when cleaning up debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-7-DEBUG_INIT_EVENT [chars]: Debug initialization for the lpts/[chars] event failed: [chars]
Explanation An error was returned when initializing debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-7-DEBUG_REGISTER [chars]: Debug registration failed: [chars]
Explanation An error was returned when registering debug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-PLATFORM_LPTS_PIFIB-7-ERR_CONN_INIT Failed to connect to [chars]: [chars]
Explanation An internal error was detected when trying to connect to the respective component.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of the respective component because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_CONN_INIT Failed to connect to [chars]: [chars]
Explanation An internal error was detected when trying to connect to the respective component.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of the respective component because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_CONN_INIT Failed to connect to [chars]: [chars]
Explanation An internal error was detected when trying to connect to the respective component.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of the respective component because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
Error Message%OS-PLATFORM_LPTS_PIFIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
Error Message%OS-PLATFORM_LPTS_PIFIB-7-ERR_DEBUG_INIT [chars]: [chars]
Explanation An error was returned when initializing debug. The facility to debug the component may not work.
Recommended Action Debug message only. No action is required.
Error Message%OS-PLATFORM_LPTS_PIFIB-7-ERR_EVM_INIT [chars]: [chars]
Explanation An internal error was detected when trying to set up event connection.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_EVM_INIT [chars]: [chars]
Explanation An internal error was detected when trying to set up event connection.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_EVM_INIT [chars]: [chars]
Explanation An internal error was detected when trying to set up event connection.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_ATTACH Could not set up a timer object: [chars]
Explanation An internal error was detected when trying to allocate a timer object.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_ATTACH Could not set up a timer object: [chars]
Explanation An internal error was detected when trying to allocate a timer object.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_ATTACH Could not set up a timer object: [chars]
Explanation An internal error was detected when trying to allocate a timer object.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_LEAF_NEW Could not create a timer tree leaf objct: [chars]
Explanation An internal error was detected when trying to create a timer tree leaf object.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_LEAF_NEW Could not create a timer tree leaf objct: [chars]
Explanation An internal error was detected when trying to create a timer tree leaf object.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_EVM_TM_LEAF_NEW Could not create a timer tree leaf objct: [chars]
Explanation An internal error was detected when trying to create a timer tree leaf object.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_INIT_POLICERS Failed to initialize the flow policer [dec]: [chars]
Explanation It failed to program a flow policer during initialization.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_INIT_POLICERS Failed to initialize the flow policer [dec]: [chars]
Explanation It failed to program a flow policer during initialization.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_INIT_POLICERS Failed to initialize the flow policer [dec]: [chars]
Explanation It failed to program a flow policer during initialization.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_LTRACE_INIT Failed to initialize the ltrace buffer
Explanation An internal error was detected when trying to initalize a ltrace buffer.
Recommended Action When this issue happens, it will not able to use ltrace buffer for debugging. 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-PLATFORM_LPTS_PIFIB-7-ERR_LTRACE_INIT Failed to initialize the ltrace buffer
Explanation An internal error was detected when trying to initalize a ltrace buffer.
Recommended Action When this issue happens, it will not able to use ltrace buffer for debugging. 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-PLATFORM_LPTS_PIFIB-7-ERR_LTRACE_INIT Failed to initialize the ltrace buffer
Explanation An internal error was detected when trying to initalize a ltrace buffer.
Recommended Action When this issue happens, it will not able to use ltrace buffer for debugging. 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-PLATFORM_LPTS_PIFIB-7-ERR_MIPC_INIT Failed to initialize with Metro IPC Server: [chars]
Explanation An internal error was detected when trying to initialize with Metro IPC server.
Recommended Action Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_MIPC_INIT Failed to initialize with Metro IPC Server: [chars]
Explanation An internal error was detected when trying to initialize with Metro IPC server.
Recommended Action Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_MIPC_INIT Failed to initialize with Metro IPC Server: [chars]
Explanation An internal error was detected when trying to initialize with Metro IPC server.
Recommended Action Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_MIPC_NOTIF_ACK Failed to acknowledge a MIPC notification: [chars]
Explanation It is an internal error which the system failed to acknowledge a MIPC Server notification.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_MIPC_NOTIF_ACK Failed to acknowledge a MIPC notification: [chars]
Explanation It is an internal error which the system failed to acknowledge a MIPC Server notification.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_MIPC_NOTIF_ACK Failed to acknowledge a MIPC notification: [chars]
Explanation It is an internal error which the system failed to acknowledge a MIPC Server notification.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_MSTATS_INIT Failed to initialize stats table: [chars]
Explanation An internal error was detected when trying to initialize a statistic counter table.
Recommended Action Check the status of Metro Stats Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_MSTATS_INIT Failed to initialize stats table: [chars]
Explanation An internal error was detected when trying to initialize a statistic counter table.
Recommended Action Check the status of Metro Stats Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_NOTIF_HANDLE Failed to handle [chars] notification: [chars]
Explanation An internal error was detected when trying to handle a notification from the respective component.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_NOTIF_HANDLE Failed to handle [chars] notification: [chars]
Explanation An internal error was detected when trying to handle a notification from the respective component.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_NOTIF_HANDLE Failed to handle [chars] notification: [chars]
Explanation An internal error was detected when trying to handle a notification from the respective component.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_PRM_STATS_INIT Failed to initialize stats table: [chars]
Explanation An internal error was detected when trying to initialize a statistic counter table.
Recommended Action Check the status of Metro Stats Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_PROGRAM_ERRORED_POLICER Failed to reprogram the flow policer [dec]: [chars]
Explanation An internal error was detected when trying to program the flow policer.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_PROGRAM_ERRORED_POLICER Failed to reprogram the flow policer [dec]: [chars]
Explanation An internal error was detected when trying to program the flow policer.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_PROGRAM_ERRORED_POLICER Failed to reprogram the flow policer [dec]: [chars]
Explanation An internal error was detected when trying to program the flow policer.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_REPROGRAM_POLICERS Failed to program the flow policer [dec]: [chars]
Explanation It failed to reprogram a flow policer when it had received a request to reprogram all flow policers to HW.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_REPROGRAM_POLICERS Failed to program the flow policer [dec]: [chars]
Explanation It failed to reprogram a flow policer when it had received a request to reprogram all flow policers to HW.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_REPROGRAM_POLICERS Failed to program the flow policer [dec]: [chars]
Explanation It failed to reprogram a flow policer when it had received a request to reprogram all flow policers to HW.
Recommended Action When this issue happens, it will trigger an automatic restart. Check the status of Metro IPC Server because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_SYSDB_DATALIST_CREATE Sysdb datalist function failed to create an object handle: [chars]
Explanation An internal sysdb function failed.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_SYSDB_DATALIST_CREATE Sysdb datalist function failed to create an object handle: [chars]
Explanation An internal sysdb function failed.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_SYSDB_DATALIST_CREATE Sysdb datalist function failed to create an object handle: [chars]
Explanation An internal sysdb function failed.
Recommended Action When this issue happens, it will trigger an automatic restart. 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-PLATFORM_LPTS_PIFIB-7-ERR_TCAM_INIT Failed to initialize TCAM regions: [chars]
Explanation An internal error was detected when trying to initialize TCAM regions.
Recommended Action Check the status of TCAM Manger because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_TCAM_INIT Failed to initialize TCAM regions: [chars]
Explanation An internal error was detected when trying to initialize TCAM regions.
Recommended Action Check the status of TCAM Manger because this issue is likely related to it. 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-PLATFORM_LPTS_PIFIB-7-ERR_TCAM_INIT Failed to initialize TCAM regions: [chars]
Explanation An internal error was detected when trying to initialize TCAM regions.
Recommended Action Check the status of TCAM Manger because this issue is likely related to it. 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.
PMHAC Messages
Error Message%OS-PMHAC-7-ERR_DLL_INIT PM HA Client DLL failed to initialize debugging services, reason [chars]
Explanation The Platform Manager HA DLL encountered an internal software error. The debugging services could not be initialized. This problem should rarely happen. Restarting the Platform Manager HA process might recover the problem
Recommended Action There is no action required because the client process should handle this error.
PMHAD Messages
Error Message%OS-PMHAD-3-ERR_NOMEM [chars]
Explanation The Platform Manager HA Driver DLL was unable to add any new fault record due to lack of memory. This condition will cause the DLL to exit.
Recommended Action Add more memory to the card specified in the System Message. If the this message recurs after a memory upgrade, copy the System Message text exactly as it appears on the console or in the system log, and contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OS-PMHAD-4-ERR_NOMEM_WARNING [chars]
Explanation The Platform Manager HA Driver DLL was unable to add one new fault record due to lack of memory, but it is still running.
Recommended Action Add more memory to the card specified in the System Message. If the this message recurs after a memory upgrade, copy the System Message text exactly as it appears on the console or in the system log, and contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%OS-PMHAD-7-ERR_DLL_INIT [chars], reason [chars]
Explanation The Platform Manager HA Driver DLL encountered an internal software error. The debugging services could not be initialized. This problem should rarely happen. Restarting the Platform Manager HA process might recover the problem
Recommended Action There is no action required because the client process should handle this error.
Error Message%OS-PMHAD-7-ERR_INIT [chars], reason: [chars]
Explanation The Platform Manager HA Driver DLL was unable to initialize due to internal software resource issues.
Recommended Action The Platform Manager HA Driver DLL will exit and the client process should handle the error accordingly. Please exam the output of show logging to see if similar issue had occured.
PROCFIND Messages
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-6-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-6-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-6-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-6-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.
Error Message%OS-PROCFIND-7-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-7-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-7-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-7-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-7-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-7-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.
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-7-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-7-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-7-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-7-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-7-DUPLICATE_BMA_PAK [chars]: Cannot duplicate BMA packet (rc equals [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-7-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-7-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-7-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-7-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-2-FATAL Fatal: [chars]
Explanation some fatal error has happended.
Recommended Action This should not occur in normal conditions
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-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.
Error Message%OS-QNET-7-SIO_Q_PROD q_produce for QNET tx failed, rc equals [dec]
Explanation could not send pkt to fabric driver.
Recommended Action This should not occur in normal conditions
QSM Messages
Error Message%OS-QSM-3-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-3-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-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-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-3-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-3-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-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]): [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-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-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-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-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-ADMIN_ADD (transition message) Detected admin plane add for [chars]. class: [hex], svctype: [hex], msgflags: [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-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-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-7-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-7-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-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_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-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-7-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-7-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-7-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-IDT_FAILED IDT for replica [chars] (all handles) FAILED
Explanation IDT for the specified replica has totally failed and the process will do a voluntary dump to recover.
Recommended Action If this message is seen for a particular process on a particular node continously then contact support
Error Message%OS-RDS-3-ALLOC_FAILURE_MSG couldnt alloc for [chars], len equals [dec], errno equals [dec]
Explanation This is a generic error msg for memory allocation failure.
Recommended Action Contact support.
Error Message%OS-RDS-3-ASSERT_MSG [chars].[dec]: hit assert condition. 'val1 equals [hex]' expected to be [chars] 'val2 equals [hex]'
Explanation rds hit an internal assert.
Recommended Action Contact support.
Error Message%OS-RDS-3-BAD_READ ens_[chars] returned len equals [dec] for DH_ENTRY: [hex], expected equals [dec]
Explanation ens_read returned bad len.
Recommended Action Contact support.
Error Message%OS-RDS-3-BAD_SEQNUM UNEXPECTED rdr_dh_seqnum equals [dec] rhdr.seq_num equals [dec] for DH equals [hex], dlen equals [dec], rdr_data equals [pointer]
Explanation ens_read returned data with bad seqnum.
Recommended Action Contact support.
Error Message%OS-RDS-3-ENS_BULK_REGISTER [dec]: ens_bulk_register failed, rc equals [hex], errno equals [dec]
Explanation ens_bulk_register failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-ENS_PRODUCER_RELEASE ens_producer_release for DH equals [hex] failed, errno equals [dec]
Explanation ens_producer_release failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-ENS_PUBLISH [chars]: ens_publish for DH equals [hex] failed, errno equals [dec]
Explanation ens_publish failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-ENS_REGISTER_CLASS [chars]: ens_register_class for replica_name equals [chars] ch equals [hex] failed, rc equals [hex], errno equals [dec]
Explanation ens_bulk_register failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-GROUP_CREATE group_create for [chars]/[chars] failed, errno equals [dec]
Explanation Group create failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-LOCK_FAILURE [chars] failed, errno equals [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 equals [dec]
Explanation nrs_create_class failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-NRS_REGISTER_BULK [chars]: nrs_register_bulk for CH equals [hex] failed, rc equals [dec] errno equals [dec]
Explanation nrs_register_bulk failed.
Recommended Action Contact support.
Error Message%OS-RDS-3-PENDING_MSG [chars]: couldnt create pending msg for CH equals [hex], DH equals [hex], errno equals [dec]
Explanation couldnt create pending msg for the incoming write/publish.
Recommended Action Contact support.
Error Message%OS-RDS-3-SEARCH_HDLS_FAILED [chars]:[dec] nrs_search for replica_name [chars] returned NULL after 50 retries
Explanation nrs_search for the specified replica did not yield any data handles.
Recommended Action If this message is seen for a particular process on a particular node more than 5 times then contact support.
Error Message%OS-RDS-3-SNAP_DUMP [chars]: handle equals [hex] memory ptr equals 0x[pointer]
Explanation rds hit an internal error.
Recommended Action Contact support.
Error Message%OS-RDS-3-SYNC_CREATE TID equals [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 equals [dec]: Ticket Release failed rp equals [pointer] tick equals [hex] curr equals [dec] hi equals [dec] currturn equals [hex] next equals [hex] waitcnt equals [dec] rc equals [dec] errno equals [dec]
Explanation Ticket request timed out.
Recommended Action Contact support.
Error Message%OS-RDS-3-SYNC_REQUEST TID equals [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 equals [dec]: Tick Req Timed out rp equals [pointer] tick equals [hex] curr equals [dec] hi equals [dec] currturn equals [hex] next equals [hex] waitcnt equals [dec] rc equals [dec] errno equals [dec], RETRYING...
Explanation Ticket request timed out.
Recommended Action Contact support.
Error Message%OS-RDS-3-SYNC_REQUEST_UNEXPECTED TID equals [dec]: Tick Req unknown failure, rp equals [pointer] tick equals [hex] curr equals [dec] hi equals [dec] currturn equals [hex] next equals [hex] waitcnt equals [dec] rc equals [dec] errno equals [dec]
Explanation Ticket request failed with unknown error.
Recommended Action Contact support.
Error Message%OS-RDS-3-WRITE_TIMEDOUT rds_write DHDL equals [hex]([chars]), req equals [dec], resp equals [dec], #wtrs equals [dec]: [chars], errno equals [dec], retries equals [dec]
Explanation rds_write request timed out.
Recommended Action Contact support.
Error Message%OS-RDS-4-COND_TIMED_WAIT TID equals [dec]: Unexpected error equals [dec] from pthread_cond_timedwait cmd equals [dec]
Explanation pthread_cond_timedwait failed.
Recommended Action Contact support.
Error Message%OS-RDS-4-RING_LOOKUP Lookup of identifier equals [hex] index equals [hex] in RING equals [pointer] failed
Explanation atomic tag ring lookup failed.
Recommended Action Contact support.
Error Message%OS-RDS-7-BAD_RDSTYPE TID equals [dec]: [dec]: Wrong replica type passed, expected equals [dec]..
Explanation passed in replica_id is wrong.
Recommended Action Contact support.
Error Message%OS-RDS-7-DUPLICATE_TICKET_NOTIF TID equals [dec]: [dec]: Duplicate Tick Notif (Dropping it) rp equals [pointer] tick equals [hex] curr equals [dec] hi equals [dec] currturn equals [hex] next equals [hex] TickCurr equals [dec] TickHi equals [dec] state equals [hex]
Explanation Got a ticket notification, for an already active ticket.
Recommended Action Contact support.
Error Message%OS-RDS-7-GENERIC_FAILURE_MSG [chars][dec]
Explanation This is a generic error msg.
Recommended Action Contact support.
Error Message%OS-RDS-7-GET_DH_ENTRY [dec]: No entry for Datahandle equals [hex], rp equals [pointer] vec equals [pointer] errno equals [dec]
Explanation Could find datahandle entry in the vector for replica
Recommended Action Contact support.
Error Message%OS-RDS-7-GET_REPLICA [dec]: [chars] for CH equals [hex], errno equals [dec], rds_type equals [dec]
Explanation Couldnt get the replica entry
Recommended Action Contact support.
Error Message%OS-RDS-7-GROUP_SEND_RINFO [chars]: group_send_rinfo failed GID equals [hex], errno equals [dec], rc equals [dec], #resp equals [dec], pattern equals [chars]
Explanation group_send_rinfo failed.
Recommended Action Contact support.
Error Message%OS-RDS-7-GSM_FAIL GSM for [chars] Failed for Handle equals [hex], to (g:[hex]/n:[hex]/p:[dec]), errno equals [dec]
Explanation group_send_memberset failed.
Recommended Action Contact support.
Error Message%OS-RDS-7-INVALID_ARGS [dec]: invalid args passed
Explanation a function was invoked with invalid arguments
Recommended Action Contact support.
Error Message%OS-RDS-7-INVALID_RHDR [dec]: invalid rhdr equals [pointer] passed
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 equals [pointer] nptr equals [pointer] from sender equals 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-NRS_DECODE [chars], Datahandle equals [hex], errno equals [dec]
Explanation An internal NRS function failed.
Recommended Action Contact support.
Error Message%OS-RDS-7-NRS_SEARCH [chars]: nrs_search for [chars] failed, rc equals [dec] errno equals [dec]
Explanation nrs_search failed.
Recommended Action Contact support.
Error Message%OS-RDS-7-QUERY_PEERS_TIMED_OUT TID equals [dec] Couldnt cmd equals [dec] for GID equals [hex] CHDL equals [hex]([hex]) #to_resp equals [dec] req equals [dec] got equals [dec] state equals [hex], expstate equals [hex] preq_id equals [dec] rds_type equals [dec]
Explanation Ticket request timed out.
Recommended Action Contact support.
Error Message%OS-RDS-7-READ_FAILED [chars] DH_ENTRY equals [hex] for exp_len equals [dec] got equals [dec] rc equals [dec] errno equals [dec]
Explanation ens_read API failed.
Recommended Action Contact support.
Error Message%OS-RDS-7-WRONG_PLANE [dec]: Wrong plane [dec] for [chars] failed..
Explanation ens_bulk_register failed.
Recommended Action Contact support.
RDSFS Messages
Error Message%OS-RDSFS-4-BAD_REPLICA Bad Replica detected: Condition-[chars] Path-[chars] Error-[chars].
Explanation The current instance of RDSFS encountered an error so that it is no longer a replica.
Recommended Action Contact customer support.
Error Message%OS-RDSFS-7-DEBUG PID:TID equals [dec]:[dec] [chars] [chars] Error-[chars]
Explanation RDSFS failure.
Recommended Action Contact customer support.
Error Message%OS-RDSFS-7-EDM_INTERNAL There was an internal error with the RDSFS EDM: [chars], [hex] ([chars]).
Explanation RDSFS encountered an internal error within it's EDM, which is a non vital component for normal operation.
Recommended Action Contact customer support
Error Message%OS-RDSFS-7-FAILURE [chars] [chars] Error-[chars]
Explanation RDSFS failure.
Recommended Action Contact customer support.
Error Message%OS-RDSFS-7-INIT_FAILED Failed to initialize [chars] because [chars].
Explanation RDSFS failed to initialize a module.
Recommended Action Contact customer support
REDFS Messages
Error Message%OS-REDFS-4-MIRROR_DISABLED Mirroring disabled because [chars].
Explanation RedFs disabled mirroring because of the specified reason.
Recommended Action Check mirroring configuration.
Error Message%OS-REDFS-5-INIT_FAILED Failed to initialize [chars]: [hex]:[chars].
Explanation RedFs failed to initialize a module.
Recommended Action Contact customer support
Error Message%OS-REDFS-5-MIRROR_ERROR Mirror [chars] error on [chars]/[chars]. Error-[dec]:[chars].
Explanation RedFs indicates that mirroring error occured on the operation and file specified with the specified error.
Recommended Action Check 'show mirror' state and confirm if a re-sync has started or redundancy has been restored. If sync failed or not redundant, contact customer support.
Error Message%OS-REDFS-5-MIRROR_NOT_REDUNDANT Mirroring is not redundant because [chars]. Only using device [chars] now.
Explanation RedFs indicates that mirroring state is no longer redundant and is only using the specified device.
Recommended Action No action is required.
Error Message%OS-REDFS-5-MIRROR_NOT_START Mirroring unable to start because secondary device [chars] is not partitioned. Please format partition it.
Explanation RedFs indicates that mirror sync process cannot start because the specfied secondary device is not partitoned. It must be partitioned to start mirroring.
Recommended Action Verify state of secondary device using 'show media'. If not partitioned, do 'format device partition' to create second partition on specified secondary device. If mirroring fails to start sync, contact customer support.
Error Message%OS-REDFS-5-MIRROR_PAUSED Mirroring has been paused. Please do 'mirror resume' to restart mirroring.
Explanation RedFs indicates that mirroring has been paused.
Recommended Action Please use the 'mirror resume' command to restart mirroring if operations which required 'mirror pause' are complete.
Error Message%OS-REDFS-5-MIRROR_SYNC_FAILED Mirror sync failed on [chars]/[chars]. Error-[dec]:[chars].
Explanation RedFs indicates that mirror sync process has failed on the specified file and is not able to make disks redundant.
Recommended Action Restart mirror sync by doing 'mirror pause' and 'mirror resume' on sync failed node. If sync fails again, contact customer support.
Error Message%OS-REDFS-6-MIRROR_ENABLED Mirroring has been enabled with configured devices of [chars] and [chars].
Explanation RedFs indicates that mirroring has been enabled with the specified devices.
Recommended Action No action is required.
Error Message%OS-REDFS-6-MIRROR_REDUNDANT Mirroring is now fully redundant for devices [chars] and [chars].
Explanation RedFs indicates that mirroring state is now fully redundant for the specified devices.
Recommended Action No action is required.
Error Message%OS-REDFS-6-MIRROR_RESUMED Mirroring has been resumed after being paused.
Explanation RedFs indicates that mirroring has been resumed after being paused.
Recommended Action No action is required.
Error Message%OS-REDFS-6-MIRROR_UPGRADE Mirroring is partitioning device [chars] as part of upgrade procedure.
Explanation RedFs indicates that it is partitioning the specified device as part of the mirroring upgrade procedure.
Recommended Action No action is required.
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.
RSI_AGENT Messages
Error Message%OS-RSI_AGENT-2-OBJ_CREATE Failed to create required '[chars]' object '[chars]', id equals [hex]: [chars]
Explanation Failed to internally create an object required to provide service.
Recommended Action Correct the problem, and restart the rsi_agent process.
Error Message%OS-RSI_AGENT-2-RESOURCE_DOWN Critical resource '[chars]' required to operate was unavailable: [chars]
Explanation A critical resource required to perform an operation was unavailable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RSI_AGENT-3-CONSISTENCY_CHECK '[chars]' had a value of '[chars]', which did not match the expected value '[chars]'.
Explanation A software bug when an internal data consistency check 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-RSI_AGENT-3-ERR_GENERAL '[chars]' failed: [chars]
Explanation Some requested operation failed. The text of the message displays the failed operation with error code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RSI_AGENT-3-ERR_INIT '[chars]' failed during initialization: [chars]
Explanation Initialization of a required module failed. The process was unable to continue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RSI_AGENT-3-INTF_MAPPING_CHANGE Unexpected interface name:handle mapping change from [chars]:[hex] to [chars]:[hex].
Explanation An interface handle was received which does not match the interface handle already in the 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-RSI_AGENT-3-NONRESPONSIVE_CLIENT Client '[chars]' has not processed an update [dec] seconds after being notified. Forcing reconnect. PID equals [dec],
Explanation RSI is forcing the specified client to reconnect, as the client has not processed a notification after a substantial timeout period.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
RSI_MASTER Messages
Error Message%OS-RSI_MASTER-2-ERR_INVALID_THREAD Callback from ENS on incorrect thread, actual/expected equals [dec]/[dec] (CSCsd51829)
Explanation Detected single-threaded RSI Master code running on an unknown thread. This concurrency can result in corruption.
Recommended Action Collect RSI traces
Error Message%OS-RSI_MASTER-2-ERR_MEM_ALLOC Insufficient memory for '[chars]', [unsigned int] bytes, terminating
Explanation RSI Master terminated due to lack of memory for a critical 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-RSI_MASTER-3-ERR_GENERAL '[chars]' failed: [chars]
Explanation Some requested operation failed. The text of the message displays the failed operation with error code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-RSI_MASTER-3-ERR_GENERAL_NO_RC [chars]
Explanation Some requested operation failed. The text of the message displays the failed 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.
RSVDPMEM Messages
Error Message%OS-RSVDPMEM-3-BAD_DATAFILE_VALUES Values from [chars] are invalid. data equals [chars]. start equals [dec], end equals [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 equals [dec], size equals [dec], base_addr equals [hex], mem_size equals [dec], mem_physical_start equals [hex], mem_physical_size equals [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 equals [hex], mem_physical_size equals [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 equals [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-RSI_INIT Failed to initialize RSI client library: [chars]
Explanation Failed to initialize RSI 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-RSI_TBL_ID Failed to get RSI tbl id from vrf name: [chars]
Explanation The RSI failed to translate a vrf name into a tbl 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-RSI_VRF_NAME Failed to get RSI vrf name from tbl id: [chars]
Explanation The RSI failed to translate a tbl id to a vrf name.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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-USAGE usage: [chars] [-m] [-u] [-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-GLOBAL_MUTEX_ERR [chars] ([dec], [chars])
Explanation Mutex lock/unlock failure has occurred for shmwins open/close 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-3-INVALID_ID Invalid window ID or group ID ([dec], [dec])
Explanation Window ID or Group ID specified by client 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-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-SHMWIN_SIZE [chars] area's size [dec] is smaller than [dec](shmwin header size)
Explanation Opened shmwin size is smaller the shmwin header size.
Recommended Action Copy the error message exactly as it appears on 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-3-WINDOW_MUTEX_ERR [chars] window:[chars] ([dec], [chars])
Explanation Mutex lock/unlock failure has occurred for a shmwin open/close 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-3-UNLINK_FAILED SHMWIN: [chars]: shmem unlink failed 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-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.
SPAIPC_NETIO Messages
Error Message%OS-SPAIPC_NETIO-7-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-SPAIPC_NETIO-7-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-SPAIPC_NETIO-7-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-SPAIPC_NETIO-7-DEBUG_INIT_FAILED [chars]:[dec] spaipc-base to register debug.
Explanation debug_register() 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-SPAIPC_NETIO-7-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-SPAIPC_NETIO-7-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-SPAIPC_NETIO-7-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.
SS_LIB Messages
Error Message%OS-SS_LIB-3-BLOCKED Process (pid1 equals [dec]) didn't finish task for [dec] seconds. Overseved by [chars](pid2 equals [dec]). Please raise a bug against infra-lwmsg. attach_process -p pid1 and pid2 are required to fix the issue. Meantime, please try to restart process with pid1 to temporary fix this issue.
Explanation Process may have been blocking in 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-SS_LIB-3-ERROR [chars] [[dec]:[chars]]
Explanation Critical error message from 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-SS_LIB-3-MUTEX_REVIVAL Couldn't register mutex revival service ([chars])
Explanation New service can't be registered due to other infrastructure issue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SS_LIB-3-SERVICE_ENTRY_NOT_AVAILABLE No more memory for monitoring [[chars]] service. Need to expand shared memory array.
Explanation New service can't be registered due to memory exhaustion. Need to fix source code to accept more services.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SS_LIB-3-STRING_LENGTH String length is [dec] where limited to [dec] ([chars])
Explanation Given string is longer than expected. There is mismatch in source code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SS_LIB-6-INVALID_REQUEST Library misuse [[chars]] (pid equals [dec], function equals [chars])
Explanation There is miuse of library.
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-SS_LIB-6-INVALID_REQUEST_ID Invalid ID is given ([dec]) (pid equals [dec], function equals [chars])
Explanation There is miuse of library.
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-SS_LIB-6-OTHER_LIBRARY_ERROR Error from [chars] ([dec]:[chars]), (pid equals [dec],id equals [dec])
Explanation Error in other library
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-SS_LIB-6-WAITING Process (pid equals [dec]) didn't finish task for [dec] seconds. Overseved by [chars](pid equals [dec]).
Explanation Process is experiencing delay in 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-SS_LIB-7-DEBUG MSG1[[chars]] ID[[dec]] MSG2[[chars]]
Explanation Debug message
Recommended Action No action is required.
SSM Messages
Error Message%OS-SSM-2-CFG_FAILED [chars]: ssm_config_init failed, error: [chars]
Explanation ssm_config_init failed due to sysdb intialization problem.
Recommended Action Collect all logs, especially those from SSM. Forward the messages to technical support.
Error Message%OS-SSM-3-CONNECT_ATTACH ConnectAttach to Channel [chars] failed, name equals [chars], id equals [dec], pid equals [dec], coid equals [dec], err equals [chars].
Explanation SSM process tried to connect to the clients channel using ConnectAttach api and encountered a failure.
Recommended Action Collect system log information for the reported service and pid. No action is required.
Error Message%OS-SSM-3-CONNECT_DETACH ConnectDetach to Channel [chars] failed, name equals [chars], id equals [dec], pid equals [dec], coid equals [dec], retval equals [dec], err equals [chars].
Explanation SSM process tried to detach to the clients channel using ConnectDetach api and encountered a failure.
Recommended Action Collect system log information for the reported service and pid. No action is required.
Error Message%OS-SSM-3-EVM_CREATE [chars]: could not create event manager: [chars]
Explanation An internal error was detected when creating Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SSM-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-SSM-3-MDR_RECOVERY ysmgr_start_mdr failed for service [chars], pid equals [dec], err equals [chars]
Explanation SSM process tried to recover service by calling sysmgr_start_mdr and and encountered an error. Collect sysmgr traces and check state of the process specified by pid.
Recommended Action Collect system logs. No action is required.
Error Message%OS-SSM-3-MSG_SEND_PULSE Sending async pulse to Channel [chars] failed, name equals [chars], id equals [dec], pid equals [dec], coid equals [dec].
Explanation SSM process tried to send a pulse to the clients channel using MsgSendPulse api and encountered a failure.
Recommended Action Collect system log information for the reported service and pid. No action is required.
Error Message%OS-SSM-3-PULSE_FAILED Connection to Channel [chars] is stuck, name equals [chars], id equals [dec], pid equals [dec], A detail information is stored on /tmp/ssm_restart_[dec].log, ssm process will restart.
Explanation SSM process sends a pulse to the monitored process over a lwm channel. This error is reported when it tries to open a connection to the channel and is stuck.
Recommended Action Collect system log information for the reported service and pid. No action is required.
Error Message%OS-SSM-3-RESTART_FAIL Failed to send [chars] to [chars], pid equals [dec], err equals [chars]
Explanation SSM process tried to restart the process using the kill command and encountered an error. Check state of the process specified by pid.
Recommended Action Collect system logs. No action is required.
Error Message%OS-SSM-3-SHM_OPEN_FAIL [chars]:ssm_shm_open failed with err: [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-SSM-3-SYSDB_BLOCK_DETECT Sysdb service is not available, ssm process is restarting([chars]:[dec]).
Explanation SSM process detects sysdb is not available. It will restart and configuration will be ignored until sysdb comes back.
Recommended Action Collect system log information for the sysdb. No action is required.
Error Message%OS-SSM-4-MDR_RECOVERY_UNSUPPORTED mdr recovery specified on RP for service [chars], pid equals [dec]
Explanation Recovery action specified (MDR) for the failing service is unsupported on RP.
Recommended Action No action is required.
Error Message%OS-SSM-5-CARD_RELOAD Card Reloading to recover failing service [chars], pid equals [dec]
Explanation SSM Process is taking recovery action for the failing service. Cold reload is the specifed recovery action for this service.
Recommended Action No action is required.
Error Message%OS-SSM-6-ALARM_CHANGE Service [chars], id equals [dec] reports alarm transition from [chars] to [chars]
Explanation Service alarm changes. They are not necessarily critical errors but need investigation by DE
Recommended Action Collect system logs. No action is required.
Error Message%OS-SSM-6-NODAL_SERVICE_STATE_CHANGE Nodal service state changes from [chars] 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-SSM-6-RECOVER_FAIL Recovery unsuccessful for service [chars], pid equals [dec]
Explanation SSM Process took a recovery action, but service is not responding
Recommended Action No action is required.
Error Message%OS-SSM-6-SERVICE_UNAVAIL Service [chars], id equals [dec] is down, fail_count equals [dec], callback_max equals [dec], proc_exited equals [dec], recovery equals [chars]
Explanation Service state has become unavailable. SSM process will try a recovery action. They are not necessarily critical errors but need investigation by DE.
Recommended Action Collect system logs. No action is required.
Error Message%OS-SSM-6-STATE_CHANGE Service [chars], id equals [dec] transitions from [chars] to [chars]
Explanation Service state changes. They are not necessarily critical errors but need investigation by DE
Recommended Action Collect system logs. No action is required.
Error Message%OS-SSM-6-SYSDB_BLOCK_RECOVER Sysdb service becomes available, update configuration.
Explanation SSM process detects sysdb becomes available. It will register with sysdb to read new configurations.
Recommended Action No action is required No action is required.
Error Message%OS-SSM-6-SYSDB_BLOCK_RECOVER_WAIT Wait for sysdb service becomes available.
Explanation SSM process is waiting for sysdb service(s) become available.
Recommended Action No action is required No action is required.
Error Message%OS-SSM-6-SYSDB_BLOCK_SERVICE Sysdb service [[chars]] is not available.
Explanation SSM process detects sysdb service is not available.
Recommended Action Collect system log information for the sysdb. No action is required.
Error Message%OS-SSM-7-SYSCALL [chars]: [chars](): [chars]
Explanation A system call failed. The calling function, the failed call, and error are displayed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SSM-7-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error.
Recommended Action Collect system log information. No action is required.
SYSLOG Messages
Error Message%OS-SYSLOG-7-EVM_CREATE Could not create event manager: [chars]
Explanation The syslog_dev has failed to create an Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SYSLOG-7-EVM_EVENT_BLOCK An error occurred while waiting for an event: [chars]
Explanation The event infrastructure will ignore this error and continue to wait for the next event. If this error is seen repeatedly, the process may not be able to function and will need to be restarted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SYSLOG-7-MISC_ERR [chars] ([chars])
Explanation An unexpected error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SYSLOG-7-RM_ATTACH Could not attach resource manager funtions to event manager: [chars]
Explanation The syslog_dev has failed to attach a Resource Manager to an Event Manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%OS-SYSLOG-7-THREAD_CREATE Could not create a Posix thread
Explanation The pthread_create function reported an error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SYSMGR Messages
Error Message%OS-SYSMGR-0-EMERGENCY [chars]
Explanation The system is unusable.
Recommended Action Contact support.
Error Message%OS-SYSMGR-1-ABORT_WARM_RELOAD Aborting Warm Reload. Cold-restarting the card ([chars]:[dec])
Explanation Attempt to Warm Reload the card has failed. The syslog events logged preceeding this event would indicate the reason for the failure to warm reload the card.
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-GET_PLACEMENT_LIST [chars]: sysmgr_msg_sendv SYSMGR_GET_PLACEMENT_LIST failed: [chars]
Explanation Sysmgr prints this when a request for placement list comes to a wrong node like SC.
Recommended Action None
Error Message%OS-SYSMGR-3-UNEXPECTED [chars]
Explanation A function call returned an unexpcted error
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] at [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-PROC_CRASH_NAME User [chars] ([chars]) requested a crash of process [chars] at [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-PROC_RESTART_JID User [chars] ([chars]) requested a restart of process with jobid [dec] at [chars]
Explanation For high availability demonstration, processes may be intentionally restarted by users.
Recommended Action None
Error Message%OS-SYSMGR-4-PROC_RESTART_NAME User [chars] ([chars]) requested a restart of process [chars] at [chars]
Explanation For high availability demonstration, processes may be intentionally restarted by users.
Recommended Action None
Error Message%OS-SYSMGR-4-PROC_SHUTDOWN_JID User [chars] ([chars]) requested a shutdown of process with jobid [dec] at [chars]
Explanation For high availability demonstration, processes may be intentionally shut down by users.
Recommended Action None
Error Message%OS-SYSMGR-4-PROC_SHUTDOWN_NAME User [chars] ([chars]) requested a shutdown of process [chars] at [chars]
Explanation For high availability demonstration, processes may be intentionally shut down by users.
Recommended Action None
Error Message%OS-SYSMGR-4-PROC_START_JID User [chars] ([chars]) requested a start of process with jobid [dec] at [chars]
Explanation Processes may be started by users. This log maintains a record of process starts
Recommended Action None
Error Message%OS-SYSMGR-4-PROC_START_NAME User [chars] ([chars]) requested a start of process [chars] at [chars]
Explanation Processes may be started by users. This log maintains a record of process starts
Recommended Action None
Error Message%OS-SYSMGR-4-UNLINK_NVLOG [chars] Unable to delete logfile [chars], because device was busy. Please delete this file manually after making a copy.
Explanation Check specified log for important information
Recommended Action Delete the NV_LOG file manually after copying it out of the router.
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-CHECK_LOG [chars]
Explanation Check specified log for important information
Recommended Action Contact support.
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 equals [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-TW_CREATE_TIMESLICE_TOO_SMALL A timer wheel has been created with a timeslice less than 100ms and cannot accurately be supported. The timeslice specified was [dec]ms.
Explanation The kernel will override a request to create a repetitive timer of less than 100ms on a priority 10 thread and internally use 100ms. This could cause software using this timer wheel to behave extremely badly.
Recommended Action Copy the error message exactly as it appears on 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-3-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.