-
Cisco IOS XR System Error Message Reference Guide, Release 4.0.1
-
Preface
-
Overview
-
Access Control List (ACL) Messages
-
Application Infrastructure Messages
-
Diagnostic Messages
-
Fabric Messages
-
Forwarding Messages
-
High Availability (HA) Messages
-
Infrastructure 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
-
Packet Infrastructure Messages
-
Platform Messages
-
Policy Manager Messages
-
Quality of Service (QoS) Messages
-
Routing Messages
-
Security Messages
-
Services Messages
-
Simple Network Management Protocol (SNMP) Messages
-
Subscriber Messages
-
System Database Messages
-
Index
-
Feedback
Table Of Contents
System Database Messages
This section contains all system database related System Error Messages.
BACKEND Messages
Error Message%SYSDB-BACKEND-7-INTERNAL [chars]: rc [hex] ([chars])
Explanation The backend 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%SYSDB-BACKEND-7-INTERNAL_PATH [chars] for pathname [chars]: rc [hex] ([chars])
Explanation The backend 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%SYSDB-BACKEND-7-INVALIDARG Invalid arguments to [chars]
Explanation Invalid arguments were supplied to a backend 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%SYSDB-BACKEND-7-INVALIDARG_PATH Invalid arguments to [chars] for path [chars]
Explanation Invalid arguments were supplied to a backend 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%SYSDB-BACKEND-7-IPADDR_AS_UINT An ipaddress was passed in with '[chars]' but a uint was expected. The value passed was '[chars]'; backend converted this to '[chars]'
Explanation The backend library has detected a mismatch between the actual and parsed values of a 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%SYSDB-BACKEND-7-MISMATCH A [chars] argument was not in a valid format. The value passed was '[chars]'; backend converted this to '[chars]'
Explanation The backend library has detected a mismatch between the actual and parsed values of a 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.
BACKUPDB Messages
Error Message%SYSDB-BACKUPDB-7-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.
BAG Messages
Error Message%SYSDB-BAG-7-INTERNAL The bag infrastructure has encountered an error. [chars]
Explanation An internal error has occurred in the bag library. Some management functions may not operate 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.
IXDB Messages
Error Message%SYSDB-IXDB-3-GC_ERROR [chars] : [chars] - Error:[chars]
Explanation There was an internal error during garbage collection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-IXDB-4-RECOVERY ixdb state recovered from interrupted add/remove operation.
Explanation The low level ixdb database has recovered after a process restart. Upper layers must recover from a potentially incomplete bulk operation as well as any application data inconsistency within ixdb. Ixdb only recovers its own state.
Recommended Action NONE. The router will attempt to recover automatically.
LIBSYSDB Messages
Error Message%SYSDB-LIBSYSDB-4-CFG_SIZE_CRIT The config size([dec] operations) exceeds critical mem limits, the config request requires ([dec] kbytes) of mem Wdsysmon mem state([dec]) total node free memory([dec]). Split the config in to smaller chunks and reattempt the config to avoid config failures
Explanation The message to the user to indicate that the requested config size exceeds the critical system memory limits and the config request will be allowed to proceed
Recommended Action *SUPPORT*
Error Message%SYSDB-LIBSYSDB-6-CFG_SIZE_HIGH The config size([dec] operations) exceeds high watermark Requires ([dec] kbytes) of memory. Wdsysmon mem state([dec]) total node free memory([dec])
Explanation The message to the user to indicate that the requested config size exceeds the high end of the system memory limits
Recommended Action *RECURR*
Error Message%SYSDB-LIBSYSDB-7-APPLY [unsigned int] out of [unsigned int] apply callbacks failed (first error: [chars]), system may now be in an inconsistent state.
Explanation An apply function failed while a verifier was scanning SysDB (e.g. after restarting), so the operational state of the system may be inconsistent with the running configuration.
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%SYSDB-LIBSYSDB-7-CERRNO_REG Failed to register block [dec] errors - cerr_register_dll returned [chars]
Explanation The client library has failed to register SysDB's error code (cerrno) definitions.
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%SYSDB-LIBSYSDB-7-CFG_SIZE_LOW The config size([dec] operations) exceeds low watermark Requires ([dec] kbytes) of memory. Wdsysmon mem state([dec]) total node free memory([dec])
Explanation The message to the user to indicate that the requested config size exceeds the low end of the system memory limits
Recommended Action *RECURR*
Error Message%SYSDB-LIBSYSDB-7-EDM_BIND SysDB client library received an EDM 'BIND' message not intended for it. Most probable cause of this error is that some other EDM has registered with the same LWM channel name as this EDM.
Explanation The SysDB client library was unable to complete an EDM 'BIND' request as the EDM registration information sent with the message was invalid for the EDM.
Recommended Action Ensure the LWM channel name used by this client is not being used by any other EDM. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-LIBSYSDB-7-INTERNAL [chars]: rc [hex] ([chars])
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%SYSDB-LIBSYSDB-7-LOCKING Failed to [chars] [chars]. Error [dec] ([chars])
Explanation The client library 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%SYSDB-LIBSYSDB-7-LOCKING_RETRY Failed to [chars] [chars]. Error [dec] ([chars]). Retrying
Explanation The client library 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%SYSDB-LIBSYSDB-7-MULT_DEFAULTIFIERS An attempt was made to register a multiple verifier with a default function on path '[chars]' which already has a default provider.
Explanation Another process has already registered a default provider function on this path. It is not possible to have multiple default providers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-LIBSYSDB-7-PICKUP_FAILED Failed to pick up a message from the server. Client connid: [dec], server connid: [dec]. Error: [hex] ([chars]).
Explanation The SysDB client library has failed to pick up a message from the server after receiving an async pulse.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-LIBSYSDB-7-RECONNECTION Failed to reconnect to SysDB server and re-register: rc [hex] ([chars])
Explanation The client library has failed to reconnect to the SysDB 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%SYSDB-LIBSYSDB-7-REFERRAL_COUNT Maximum number of bind referrals hit attempting to connect to path [chars].
Explanation An internal library error has caused a connection attempt from a client to SysDB to fail.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-LIBSYSDB-7-RESTORE Failed to restore items after EDM registration on [chars], system may now be in an inconsistent state.
Explanation If an EDM registers or reregisters on a path on which items already exist (and SYSDB_REGISTRATION_OPTION_SCAN has been specified), then those items have been deleted but not all restored after the EDM registration, so the system may now be in an inconsistent state.
Recommended Action *RECUR*
Error Message%SYSDB-LIBSYSDB-7-UNEXPECTED_SEND_ERROR Unable to send a LWM message due to a non-connection-related error ([dec]).
Explanation The SysDB client library has failed to send a LWM message to the server, due to receiving an unexpected non-connection-related error in sending 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.
REPLICATOR Messages
Error Message%SYSDB-REPLICATOR-3-BAD_HANDLENAME Handle name ([chars]) has been corrupted. rc: [hex] ([chars])
Explanation The replicator library got an error back from NRS indicating that the data handle is no longer valid. This handle would have been validated on initialisation, so the likely cause of this error is memory corruption. The client process will be forcibly restarted to try to recover.
Recommended Action *RECUR*
Error Message%SYSDB-REPLICATOR-3-IDT_FAIL Failed to complete IDT after several retries: rc [hex] ([chars])
Explanation The replicator has repeatedly failed to complete IDT for a system data handle. There may be problems with communications or other low-level infrastructure.
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%SYSDB-REPLICATOR-3-LARGE_HANDLE Large item handle detected ([hex]/[hex])
Explanation The replicator library has received an exceptionally large item handle from NRS which may cause conflicts within the replicator 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%SYSDB-REPLICATOR-3-WRITE_OWNERSHIP_FAIL Failed to acquire data handle after several retries: rc [hex] ([chars])
Explanation The replicator has repeatedly failed to acquire ownership of a system data handle. The client process may need restarting.
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%SYSDB-REPLICATOR-7-BAD_MAGIC A corrupted persistent data structure was discovered ([chars])
Explanation The replicator library discovered a bad magic number in a persistent data structure. This suggests that the data has been corrupted. The replicator library will attempt to recover the situation.
Recommended Action *RECUR*
Error Message%SYSDB-REPLICATOR-7-CTX_NOT_FOUND Could not access [chars] context structure: rc [hex] ([chars])
Explanation The replicator library was unable to access an internal structure. This may result in failure of data replication to the standby node(s).
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%SYSDB-REPLICATOR-7-INTERNAL [chars]: rc [hex] ([chars])
Explanation The replicator 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%SYSDB-REPLICATOR-7-LOCKING Failed to [chars] [chars]. Error [dec] ([chars])
Explanation The replicator library 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%SYSDB-REPLICATOR-7-MEMORY Failed to malloc [unsigned int] bytes
Explanation The replicator 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%SYSDB-REPLICATOR-7-NO_CB No completion notification received for update message [unsigned int]
Explanation The replicator library did not receive a callback from the transport library. The update will be allowed to continue without the replication acknowledgement. If any replicas have not received the update, they will resync on the next update.
Recommended Action *RECUR*
Error Message%SYSDB-REPLICATOR-7-SEND_FAILED Failed to send update: rc [hex] ([chars])
Explanation An error was returned from RDS when trying to send an update. Clients will handle this condition differently either by retrying later, or failing the operation. If this condition persists, data may be lost on failover.
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%SYSDB-REPLICATOR-7-UPDATE_FAILED Failed to apply [chars] update: rc [hex] ([chars])
Explanation The client returned an error when trying to apply an update. The replicator library will try to recover by requesting a replay of the update. If this condition persists, data may be lost on failover.
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%SYSDB-REPLICATOR-7-WRITE_OWNERSHIP Failed to acquire data handle: rc [hex] ([chars])
Explanation The replicator has failed to acquire ownership of a system data handle.
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.
SMC Messages
Error Message%SYSDB-SMC-7-DEPRECATED_PATH SysDB path '[chars]' is deprecated
Explanation An operation has been attempted on a part of the SysDB namespace that should no longer be used.
Recommended Action *RECUR*
Error Message%SYSDB-SMC-7-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%SYSDB-SMC-7-INTERNAL_STATE [chars]
Explanation The server 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%SYSDB-SMC-7-INVALID_PATH SysDB path '[chars]' is invalid
Explanation An operation has been attempted on a part of the SysDB namespace that should not be used.
Recommended Action *RECUR*
Error Message%SYSDB-SMC-7-MISSING_NODE_NFN Missing node down notification from node [chars]
Explanation No node down notification was received from the underlying infrastructure for a recent node reload.
Recommended Action *SUPPORT*
Error Message%SYSDB-SMC-7-MULTI_NODE_TRANS Multi-node access from transaction will be non-atomic (transaction node [dec]:[dec], accessing node [dec]:[dec], by [chars])
Explanation An application tried to use a transaction to access multiple nodes; this is not supported currently.
Recommended Action *SUPPORT*
Error Message%SYSDB-SMC-7-PARSE_FAILED [chars] ('[chars]' from '[chars]')
Explanation A pathname was used for a SysDB operation from which the destination node could not be parsed.
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%SYSDB-SMC-7-PROTOCOL A incompatible version of a message was received from process id [dec], node [dec]
Explanation There was a mismatch between the messaging protocol version used by the SysDB MC and the SysDB MS.
Recommended Action Upgrade all nodes to have the same version of SysDB installed.
Error Message%SYSDB-SMC-7-RESTARTING This process is restarting, as ([chars]) is failing. [chars] ([chars]).
Explanation The SysDB server is unable to function due to a problem with one of its modules. The only hope of recovery is to restart. If the problem persists, the card will be automatically reloaded.
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%SYSDB-SMC-7-TIMEOUT Message #[unsigned int], destined for [chars], timed out having received [unsigned int] of [unsigned int] expected responses: returning [chars] to client [chars]. Check for potential transport issues within the system, or deadlocked SysDB processes.
Explanation A request timed out before SysDB MC received the expected number of replies
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%SYSDB-SMC-7-TRANS Attempted multi-node access from transaction was prevented (attempted to access multi-cast group [dec])
Explanation A client attempted to use an unsupported distributed transaction.
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%SYSDB-SMC-7-UNEXPECTED_MSG_TYPE An unexpected([chars]) message type was received: [hex]: sender gid([unsigned int]) nid([hex]) pid ([unsigned int])
Explanation We are receiving messages of a type that we did not expect. This should not cause failures of any kind, but probably does indicate an error in another part of the system.
Recommended Action *SUPPORT*
Error Message%SYSDB-SMC-7-UNEXPECTED_MULTIPLE_RESPONSES Received unexpected multiple responses for message of type [hex]
Explanation The SysDB Medusa process received multiple responses for a message type for which only a single response was expected.
Recommended Action *SUPPORT*
Error Message%SYSDB-SMC-7-UNEXPECTED_VALUE Encountered unexpected [chars]: [hex]
Explanation The server has come across an unexpected value for the specified 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%SYSDB-SMC-7-WRONG_PLANE An attempt was made to access SysDB path '[chars]'. This resolves to the [chars] plane and cannot be accessed on this card type.
Explanation An application has tried to access a plane of SysDB data that does not exist on this node.
Recommended Action *RECUR*
SMS Messages
Error Message%SYSDB-SMS-3-ASYNC_MSG_TAG_INVALID Unable to respond back to client jid: [dec] nid : [dec]. This will be reported as an SMC timeout by the sysdb_mc originating the request
Explanation An internal error left the msg tag to be an invalid one. Causing the request to be timedout.
Recommended Action *SUPPORT*
Error Message%SYSDB-SMS-3-GSP_EVQ_HANDLE_ERROR An Invalid TAG was dequeued rc([hex]), tag([hex]), len([hex])
Explanation We are dequeuing an invalidly TAGGED message for transmission This should not cause failures of any kind, but probably does indicate an error in another part of the system.
Recommended Action *SUPPORT*
Error Message%SYSDB-SMS-3-MSG_SEND_ZERO_BYTES A zero BYTE message was posted,type([dec]),flags([hex]),msg_id([hex]) event_msg_id([hex]), client_connid([dec]) server_connid([dec])
Explanation We are posting zero sized messages that we did not expect. This should not cause failures of any kind, but probably does indicate an error in another part of the system.
Recommended Action *SUPPORT*
Error Message%SYSDB-SMS-6-EDM_RESPONSE_TOO_BIG EDM Manager jid: [dec] nid: [dec] response too big, size: [dec]
Explanation A Client is responding with a very huge data, it should split the response.
Recommended Action *SUPPORT*
Error Message%SYSDB-SMS-7-INTERNAL [chars]: rc [hex] ([chars])
Explanation The SysDB 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%SYSDB-SMS-7-LOCKING Failed to [chars] [chars]. Error [dec] ([chars])
Explanation The SysDB server 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%SYSDB-SMS-7-MISSING_NODE_NFN Missing node down notification from node [chars]
Explanation No node down notification was received from the underlying infrastructure for a recent node reload.
Recommended Action *SUPPORT*
Error Message%SYSDB-SMS-7-PROTOCOL A incompatible version of a message was received from process id [dec], node [dec]
Explanation There was a mismatch between the messaging protocol version used by the SysDB MC and the SysDB server.
Recommended Action Upgrade all nodes to have the same version of SysDB installed.
Error Message%SYSDB-SMS-7-REG_CONTEXT_EXISTS Reg from [dec]/[dec]/[dec] already exists for connid [dec] and reg_handle [dec]
Explanation Sysdb is attempting to add a registration that already exists in its registration context. This will cause a sysdb server restart.
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%SYSDB-SMS-7-REG_SEC_CONTEXT_EXISTS Reg from [dec]/[dec]/[dec] already exists for msgid [dec]
Explanation Sysdb is attempting to add a registration that already exists in its secondary registration context. This will cause a sysdb server restart.
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%SYSDB-SMS-7-REG_SEC_DEL_FAIL Delete of Reg from [dec]/[dec]/[dec] exists for msgid [dec] fails
Explanation Sysdb is attempting to del a registration that does not exist in its secondary registration context.
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%SYSDB-SMS-7-REQUEST_REG_SEND_ERR Not able to send message out, as an essential piece of infrastructure ([chars]) is failing. [chars] ([chars]).
Explanation The SysDB server is unable to function due to a problem with a piece of infrastructure. The only hope of recovery is to restart. If the problem persists, the card will be automatically reloaded.
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%SYSDB-SMS-7-RESTARTING This process is restarting, as an essential piece of infrastructure ([chars]) is failing. [chars] ([chars]).
Explanation The SysDB server is unable to function due to a problem with a piece of infrastructure. The only hope of recovery is to restart. If the problem persists, the card will be automatically reloaded.
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%SYSDB-SMS-7-SEND_RESPONSE Sending [chars] via group_sendv_memberset failed [msg_size [unsigned int]]: [hex] ([chars])
Explanation The SysDB server failed to send a message to the SysDB Medusa Client
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%SYSDB-SMS-7-UNEXPECTED_MSG_TYPE An unexpected([chars]) message type was received: [hex]: sender gid([unsigned int]) nid([hex]) pid ([unsigned int])
Explanation We are receiving messages of a type that we did not expect. This should not cause failures of any kind, but probably does indicate an error in another part of the system.
Recommended Action *SUPPORT*
Error Message%SYSDB-SMS-7-UNEXPECTED_VALUE Encountered unexpected [chars]: [hex]
Explanation The SysDB server came across an unexpected value for the specified 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.
SYSDB Messages
Error Message%SYSDB-SYSDB-3-SC_BIND [Sysdbcon] Could not bind to SysDB: [chars]
Explanation Sysdbcon was unable to bind to the root of SysDB. It is possible that there is a problem with SysDB.
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%SYSDB-SYSDB-3-SC_DATATYPERET [Sysdbcon] SysDB returned unrecognized datatype ([unsigned int])
Explanation The datatype returned by SysDB does not match any of those expected by Sysdbcon. This is probably because the type is missing in Sysdbcon.
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%SYSDB-SYSDB-3-SC_EXTFMTSTR [Sysdbcon] Unable to extract format string from packed tuple
Explanation The packed tuple returned from SysDB is in some way corrupt. The format string it contains could not be read.
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%SYSDB-SYSDB-3-SC_FILEREAD [Sysdbcon] Unable to read from command file
Explanation An error occurred during a read operation from the instruction file.
Recommended Action Check that the file format is correct. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-3-SC_INTERR [Sysdbcon] An internal error has occurred
Explanation The code has performed an action which should not be possible.
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%SYSDB-SYSDB-3-SC_NOFILE [Sysdbcon] The specified command file ([chars]) could not be opened
Explanation The instruction file specified when Sysdbcon was started cannot be found. The most probable reason is that an incorrect name was supplied.
Recommended Action Check that the file name supplied was correct. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-3-SC_PKDREAD [Sysdbcon] Unable to read in data for packed tuple
Explanation An error occurred while preparing to read instructions from the command line.
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%SYSDB-SYSDB-3-SC_PKDTUPLECRE [Sysdbcon] Unable to create packed tuple
Explanation An error occurred creating a packed tuple.
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%SYSDB-SYSDB-3-SC_PKDTUPLEFILE [Sysdbcon] No data for packed tuple in file
Explanation An error occurred during a read operation from the instruction file.
Recommended Action Check that the file format is correct. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-3-SC_READERINIT [Sysdbcon] Unable to initialize the command line reader
Explanation An error occurred while preparing to read instructions from the command line.
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%SYSDB-SYSDB-3-SC_UNPACKTUP [Sysdbcon] Unable to unpack packed tuple
Explanation The packed tuple returned from SysDB is in some way corrupt. The data it contains could not be read.
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%SYSDB-SYSDB-3-THREAD_EXIT Process is exiting, thread ID: ([dec])
Explanation A thread of SysDB server or medusa process has exited for some critical reason and will be restarted.
Recommended Action Check to make sure the process has restarted. If not, restart manually. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-REPLICATOR_OOS A possible configuration inconsistency has been detected. Please check recent configuration changes and verify that configuration is consistent with binary files.
Explanation The SysDB replicator module has been informed that it may have been out of sync when taking over as the new active server. The other replica nodes will sync up, but it is possible that a recent configuration change may have been partially or completely lost.
Recommended Action Check any recent commits to see if the configuration has been lost. Run 'clear configuration inconsistency' for the relevant plane.
Error Message%SYSDB-SYSDB-4-SC_ABORTBULK [Sysdbcon] While aborting a bulk operation the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_ABORTTRANS [Sysdbcon] While aborting a transaction the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_BAD_INTEGER [Sysdbcon] Warning: bad integer format or integer value is out of range.
Explanation The user entered integer in unrecognized format or out of range of current integer data type.
Recommended Action Correct input value and run command again.
Error Message%SYSDB-SYSDB-4-SC_BADFORMAT [Sysdbcon] Badly formatted command
Explanation An unescaped ''' character was found part way through a token in a command string.
Recommended Action Re-enter the command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_BIND_NOTFOUND [Sysdbcon] Warning: now bound to a non-existent node.
Explanation The user bound to a node which does not exist. This is a warning only - this action is perfectly legal.
Recommended Action Check that this is the directory you intended to bind to.
Error Message%SYSDB-SYSDB-4-SC_BULK_NUM_OPS [Sysdbcon] While getting the number of operations in the bulk the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. This could be because the operation does not exist. The details are in the error string.
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%SYSDB-SYSDB-4-SC_CFGMGR_ADD_DELETES [Sysdbcon] While adding deletes to the bulk buffer the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_CFGMGR_ADDDIFFS [Sysdbcon] While adding diffs to the bulk the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_CFGMGR_DELETE [Sysdbcon] While performing a bulk regular expression delete the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_CFGMGR_MERGE [Sysdbcon] While merging files the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_CFGMGR_REMOVE_DELETES [Sysdbcon] While removing deletes to the bulk buffer the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_COMMITTRANS [Sysdbcon] While committing a transaction the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_COPY [Sysdbcon] While copying item [chars] to [chars] the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. This could be because the item to copy does not exist. The details are in the error string.
Recommended Action Check that the item to copy exists. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_CREATE [Sysdbcon] While creating item [chars] the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. This could be because the item to create already exists. The details are in the error string.
Recommended Action Check that the item to create does not exist. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_DATAFIND [Sysdbcon] While executing the find data request the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_DATALIST [Sysdbcon] While executing the datalist request the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_DATATYPE [Sysdbcon] Unrecognized datatype ([chars])
Explanation A datatype other than one of those supported was supplied.
Recommended Action Use help for a list of supported datatypes. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_DELETE [Sysdbcon] While deleting item [chars] the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. This could be because the item does not exist. The details are in the error string.
Recommended Action Check that the item to delete exists. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_EDM_NOT [Sysdbcon] While generating EDM notifications the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_ENDBULK [Sysdbcon] While ending a bulk operation the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_ERRORSLIST [Sysdbcon] While executing the errors list request the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_EVENT [Sysdbcon] Unrecognized notification event ([chars])
Explanation A notification event other than one of those supported was supplied.
Recommended Action Use help for a list of supported events. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_EVENTFIND [Sysdbcon] While executing the event find request the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_EXCESS [Sysdbcon] Excess tokens in command string
Explanation There were more tokens entered as part of the command string than are required for the command.
Recommended Action Use the help command to determine the correct usage for this command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_FILERESTORE [Sysdbcon] While restoring items from a file the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_FILESAVE [Sysdbcon] While saving items to a file the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_FIND [Sysdbcon] While executing the find request the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_GENERIC [Sysdbcon] While performing operation '[chars]' the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_GET [Sysdbcon] While fetching item [chars] the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. This could be because the item to fetch does not exist. The details are in the error string.
Recommended Action Check that the requested item exists. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_GET_ITEMS [Sysdbcon] While fetching items from path [chars] the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. This could be because the items to fetch do not exist. The details are in the error string.
Recommended Action Check that the requested items exists. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_ITERATE [Sysdbcon] While executing the iterate request the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_LIST [Sysdbcon] While executing the list request the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_MISMATCH [Sysdbcon] Mismatched quotes in command
Explanation A quoted token was not terminated with a quote character.
Recommended Action Re-enter the command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_MISSEVENT [Sysdbcon] Missing notification event
Explanation The command entered requires a notification event type and one was not supplied.
Recommended Action Use the help command to determine the correct usage for this command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_MISSFILENAME [Sysdbcon] Missing file name
Explanation The command entered requires an file name and one was not supplied.
Recommended Action Use the help command to determine the correct usage for this command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_MISSNAME [Sysdbcon] Missing item name
Explanation The command entered requires an item name and one was not supplied.
Recommended Action Use the help command to determine the correct usage for this command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_MISSTYPE [Sysdbcon] Missing item type
Explanation The command entered requires an item type and one was not supplied.
Recommended Action Use the help command to determine the correct usage for this command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_MISSVALUE [Sysdbcon] Missing item value
Explanation The command entered requires an item value and one was not supplied.
Recommended Action Use the help command to determine the correct usage for this command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_PATHCREATE [Sysdbcon] Unable to create full path from path supplied
Current dir: [chars]
Path supplied [chars]Explanation When combining the path supplied with the path Sysdbcon is currently bound to an error occurred. This could be because the path created would be invalid.
Recommended Action Check that the combination of paths is valid. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_PKDFMTSTR [Sysdbcon] Format string contains illegal character ([char])
Explanation The packed tuple format string should only contain combinations of '%', 'd', 'ld' and 's'. A character other than one of these was found in the string.
Recommended Action Check that the format string is correct. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_RDLOCK [Sysdbcon] While getting a read lock the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_REBIND [Sysdbcon] While binding to [chars] the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. This could be because the path supplied is invalid. The details are in the error string.
Recommended Action Check that the path is valid. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_REMOVE_BULK_OP [Sysdbcon] While removing operation on [chars] the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. This could be because the operation does not exist. The details are in the error string.
Recommended Action Check that the operation to remove exists. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_SET [Sysdbcon] While setting item [chars] the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. This could be because the item does not exist or has the wrong type. The details are in the error string.
Recommended Action Check that the item to set exists and has the same type as it is being set to. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_STARTBULK [Sysdbcon] While starting a bulk operation the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_STARTTRANS [Sysdbcon] While starting a transaction the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. This could be because the timeout time was not correctly entered. The details are in the error string.
Recommended Action Check that the format of the timeout time is correct. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_UNKCMD [Sysdbcon] Unrecognized command. Type help or ? for a list of available commands
Explanation The first token in a command string was not a recognized Sysdbcon command.
Recommended Action Check the list of available commands and retry. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_UNLOCK [Sysdbcon] While releasing a lock the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_VERIFY [Sysdbcon] Verification failed on item [chars] for the following reason
[chars]Explanation An error occurred invoking a SysDB function. This could be because the item does not exist or has the wrong type. Or because the verifier did not allow the change. The details are in the error string.
Recommended Action Check that the item to set exists and has the same type as it is being set to. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-4-SC_VRFNRES [Sysdbcon] While resuming verification the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_VRFNSUSP [Sysdbcon] While suspending verification the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-SC_WRLOCK [Sysdbcon] While getting a write lock the following error occurred:
[chars]Explanation An error occurred invoking a SysDB function. The details are in the error string.
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%SYSDB-SYSDB-4-TIMEOUT_NFN Process '[chars]' (jid [dec], node [chars]) failed to pick up notification event within the timeout period ([unsigned int] seconds)
Explanation A notification event sent by the SysDB server timed out.
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%SYSDB-SYSDB-6-TIMEOUT_EDM EDM request for '[chars]' from '[chars]' (jid [dec], node [chars]). No response from '[chars]' (jid [dec], node [chars]) within the timeout period ([unsigned int] seconds)
Explanation A timeout occurred whilst processing a 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%SYSDB-SYSDB-7-CFG_WRITE [chars] (jid [dec]) wrote to the configuration namespace (item: /[chars]). Illegal modification of configuration is not allowed.
Explanation A non-management client illegally modified part of the system configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-7-CLIENT_STATS [chars]: client name: [chars], jid: [dec], nid: [dec], counter: [hex]
Explanation A SysDB server process was unable to update a per-client statistics counter for one of its clients. This is an unexpected condition, though has no effect on router 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%SYSDB-SYSDB-7-CLIENT_STATS_MISMATCH SysDB usage statistics for [chars] (jid: [dec], nid: [dec]) and [chars] (jid: [dec], nid: [dec]) have been unexpectedly combined and should be treated as inaccurate
Explanation The per-client usage statistics for the SysDB clients identified in the message have been combined, when they should be stored separately. The statistics for these processes should be treated as inaccurate. This is an unexpected condition, though has no effect on router 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%SYSDB-SYSDB-7-INFO [chars]: rc [hex] ([chars])
Explanation The server detected an error with one of its clients.
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%SYSDB-SYSDB-7-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%SYSDB-SYSDB-7-INVALID_PATHNAME [chars] attempted an item get on a subtree path ([chars]). Item gets should only be attempted on items, with no trailing '/'
Explanation A process, likely to be a show command, is attempting to access a sysdb item with an incorrect path string.
Recommended Action *DEBUG*
Error Message%SYSDB-SYSDB-7-LOCKING Failed to [chars] [chars]. Error [dec] ([chars])
Explanation The server 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%SYSDB-SYSDB-7-LTRACE_INIT SysDB ltrace init failed. Error initializing [[chars]] trace buffer. Error returned by ltrace initialisation: [chars]
Explanation The ltrace buffer could not be initialized
Recommended Action *RECUR*
Error Message%SYSDB-SYSDB-7-REPLICATOR_NO_CB No completion notification received for update message [unsigned int]
Explanation The SysDB replicator module on the active server did not receive a callback from the transport library. The request will be allowed to continue without the replication acknowledgement. If any replicas have not received the update, they will resync on the next update.
Recommended Action *RECUR*
Error Message%SYSDB-SYSDB-7-REPLY Failed to send reply to client jid [unsigned int] tid [unsigned int] node [chars]: rc [hex] ([chars])
Explanation The server failed to reply to a client request. A likely reason for this is that the process in question has exited.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show process jid location all 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 process jid location all output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-7-RPL_INIT [chars]: rc [hex] ([chars])
Explanation An unexpected error occurred during initialisation of the replicator module.
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%SYSDB-SYSDB-7-SEND [chars] to process '[chars]' (jid [dec], node [chars]): errno: [dec] ([chars])
Explanation The SysDB server failed to send an asynchronous message to a SysDB client. A likely reason for this is that the process in question has exited.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show process jid location all 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 process jid location all output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-7-SHUTDOWN Process is shutting down, rc [hex] ([chars])
Explanation A SysDB server process has performed a graceful shutdown and will be restarted.
Recommended Action Check to make sure the process has restarted. If not, restart manually. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SYSDB-SYSDB-7-STARTUP Startup request for '[chars]' from '[chars]' (jid [dec]) failed for a process on a slow starting node
Explanation A startup request failed during the second round of callbacks.
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%SYSDB-SYSDB-7-USAGE Incorrect arguments: Usage: [chars] l|s|a [svr_threads] l equals local-plane; s equals shared-plane; a equals admin-plane Maximum number of threads is [dec].
Explanation Incorrect command line parameters were passed to the sysdb server, and so it failed to start.
Recommended Action Check the startup arguments passed to sysdb. 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.
SYSDBHELPER Messages
Error Message%SYSDB-SYSDBHELPER-7-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%SYSDB-SYSDBHELPER-7-LOCKING Failed to [chars] [chars]. Error [dec]
Explanation The client library 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.
SYSDBUTILS Messages
Error Message%SYSDB-SYSDBUTILS-7-INTERNAL [chars]: rc [hex] ([chars])
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%SYSDB-SYSDBUTILS-7-INTERNAL_NODEID_STR NodeID to string conversion failed for node id [dec] (rc [hex] - [chars])
Explanation The client library was unable to convert the specified node ID into a node description string.
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%SYSDB-SYSDBUTILS-7-LOCKING Failed to [chars] [chars]. Error [dec]
Explanation The client library 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.