Table Of Contents
Manageability (MGBL) Messages
PARSER Messages
PM Messages
Manageability (MGBL) Messages
This section contains all Management Plane and Manageability related System Error Messages, including config, cli, sml, pm, and so forth. The following facility codes are represented in this module:
•
PARSER Messages
•
PM Messages
PARSER Messages
Error Message
%MGBL-PARSER-3-API_FAIL
[chars]: [chars]: [chars]
Explanation 'An API failed due to the mentioned 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
%MGBL-PARSER-3-BOGUS_HOOKPOINT
Bogus hook point index [unsigned int]
Explanation 'Bogus hook point'
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%MGBL-PARSER-3-BOGUS_LINKPOINT
Bogus link point index [unsigned int], sub
system:[chars], offset:[hex], mask:[hex]
Explanation 'Bogus link point'
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%MGBL-PARSER-3-BUFFER_OVERFLOW
[chars]
Explanation 'buffer overflow'
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%MGBL-PARSER-3-CARD_MODULE_FROM_NODEID_FAILED
Unable to get card number and
module number from nodeid: '[unsigned int]' Error: '[chars]'
Explanation Parser relies on invmger API to get card number and module number. But the API had
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
%MGBL-PARSER-3-CREATETHREAD
Failed to create parse thread: [chars]
Explanation 'pthread_create() API failed due to mentioned 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
%MGBL-PARSER-3-ENV
[chars]: The call to ovl_setup_env() failed
Explanation 'Could not update environment variables due to the error'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-ERR_GENERAL_ERR
[chars]: [chars]
Explanation 'Parser encountered error, see message for more details'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-ERR_SYSDB_BAG_DECODE
bag decode error ([chars])
Explanation 'Failure to decode the bag.'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-ERR_SYSDB_GET
sysdb_item_get of '[chars]': [chars]
Explanation 'sysdb item get operation failed. The error is displyed in the error message.'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-EXTRACT_FAILED
[chars]:[dec]:[chars]
Explanation Nodeid conversion API 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
%MGBL-PARSER-3-EXTRACT_NODEID_FIELDS_FAILED
Extracting rack/slot/module from
'[chars]' failed
Explanation Parser unable to get rack/slot/module field from path.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%MGBL-PARSER-3-INVALID_NOTIFICATION
Unknown or unsupported ovl notification:
[dec]
Explanation 'parser_server got an invalid notification form ovl process'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-INVALID_PARSERFILE
Invalid parser file: [chars]
Explanation 'Invalid parser 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
%MGBL-PARSER-3-INVALIDDETAILS
Invalid details pointer [hex] at offset [hex]
tokentype [hex] in tree '[chars]'
Explanation 'The offset to the token details structure is bogus'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-INVALIDINPUTFMT
Input format(s) do not match output format in:
'[chars]'
Explanation 'The Number output format specification is not in the number input format
specification, so we are writing a number that we probably cannot read back in'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-INVALIDOFFSET
Invalid offset [hex] from offset [hex] in tree
'[chars]'
Explanation 'The offset into the parser tree file is bogus'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-INVALIDRANGE
Invalid [chars] range in tree '[chars]'
Explanation 'The numerical range within the token details structures is invalid'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-INVALIDVERSION
parser version is [dec].[dec] cannot handle
version [dec].[dec] of command chain in component '[chars]'.Please do Jam clean
and build the image.
Explanation 'The version of this file is too old or 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
%MGBL-PARSER-3-INVENTORY_DB_INTEGRITY_ERROR
Duplicate entries in inventory db
for '[chars]'
Explanation Duplicate entries found in inventory 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
%MGBL-PARSER-3-INVENTORY_DB_SIZE_INCREASE_FAILED
Increasing inventory database
size from '[dec]' to '[dec]' failed
Explanation Inventory database size increase failed. Can happen only if memory is too 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
%MGBL-PARSER-3-INVENTORY_DB_SIZE_ZERO
Inventory database size is Zero
Explanation Inventory database size is zero. Can happen only if memory is too 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
%MGBL-PARSER-3-INVENTORY_DESCRIPTION_NULL
Description pointer is null
Explanation Description string is null.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%MGBL-PARSER-3-INVENTORY_FIELD_IS_NULL
'[chars]' is NULL
Explanation Error in extracting rack/slot/module name from sysdb path.
Recommended Action Restart parser_server process (process restart parser_server). If the message
recurs, copy and save the message and call your technical support representative for assistance.
Error Message
%MGBL-PARSER-3-INVENTORY_FIELD_NOT_NUMBER
'[chars]' is not a number
Explanation Rack/slot/module are stored as sysdb path in inventory DB. They are essentially
numbers. So either rack/slot/module are not numbers, or the path is incorrect.
Recommended Action Restart parser_server process (process restart parser_server). If the message
recurs, copy and save the message and call your technical support representative for assistance.
Error Message
%MGBL-PARSER-3-LOCK_ERR
Failed lock operation '[chars]' during '[chars]'.
Error:[chars]
Explanation A lock operation on shared resource, called by parser failed due to the mentioned error.
Recommended Action Collect the output of show logging and inform Copy the error message exactly
as it appears on the console or in the system log, call your Cisco technical support representative
and provide the representative with the gathered information.
Error Message
%MGBL-PARSER-3-MMAP
mmap of file '[chars]'
Explanation 'mmap of 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
%MGBL-PARSER-3-NODE_CREATION_FAILED
Unable to create nodeid for
([dec],[dec],[dec]): error:'[chars]'
Explanation Error in getting rack/slot/module numbers from system 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
%MGBL-PARSER-3-NODEID_TO_STRING_ERROR
Unable to convert nodeid:'[dec]' to string
Explanation Error in conversion 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
%MGBL-PARSER-3-NOTIFICATION_PATH_NULL
NULL notification path
Explanation Parser received notification from NULL path.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%MGBL-PARSER-3-OBJECT_NOT_FOUND_FOR_RANGE
Unable to find the parser object
'[dec]' which is used as range
Explanation 'The range value was given as a parser object ,but object could not be found'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-OVERFLOW
'[chars]' overflows ambig_line '[chars]'
Explanation 'Help string overflows ambig_line'
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%MGBL-PARSER-3-RACK_TO_STR_FAILED
[chars]:[dec]:[chars]
Explanation Nodeid conversion API 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
%MGBL-PARSER-3-REGEX_COMP_ERROR
Regex compilation error:[dec] '[chars]'
Explanation Regex compilation error has occured. The command line execution would either fail or
would not show proper result.
Recommended Action Restart parser_server process (process restart parser_server). If the message
recurs, copy and save the message and call your technical support representative for assistance.
Error Message
%MGBL-PARSER-3-RIGHTARG
Right arg([dec]) type unsupported: [dec]
Explanation 'The test token has invalid right argument'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-SUBMODE
[chars]: Can not find submode : [chars]
Explanation 'The call to parser_submode_find failed to find submode. The error is displayed in the
message'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-SYSDBOPERATION
[chars]: sysdb_action: [chars]
Explanation 'Unexpected error in sysdb call. The error is displayed in the message'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-TASKID_LIMIT
Exceeded '[unsigned int]' of taskids in a command
Explanation 'A command can have only MAX_TASKIDS_PER_COMMAND different taskids'
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%MGBL-PARSER-3-THREAD_LIMIT
Failed to increase the maximum limit of management
connections. An unexpected error has occured, error: ([dec]) [chars].
Explanation An unexpected error caused failure to increase the maximum limit of management
connections to the device. This error would affect the user only if he tries to have the number of
management connections above an approximate count of 25.
Recommended Action Restart parser_server process (process restart parser_server). If the message
recurs, copy and save the message and call your technical support representative for assistance.
Error Message
%MGBL-PARSER-3-TUPLEUNPACK
[chars]: tuple_unpack_mask failed: '[chars]'
Explanation 'sysdb tuple unmask operation failed. The sysdb string is displyed in the error message.'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-UNKNOWNTOKEN
Unknown token type [hex] at offset [hex] in tree
'[chars]'
Explanation 'The parser token type is undefined in the specified tree'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-3-UNRESOLVED_HOOKPOINT
Unresolved hookpoint '[chars]' at chain
'[chars]'
Explanation 'Unresolved hookpoint'
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%MGBL-PARSER-3-UNRESOLVED_LINKPOINT
Unresolved linkpoint '[chars]' at chain
'[chars]'
Explanation 'Unresolved linkpoint'
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%MGBL-PARSER-3-UNSUPPORTEDARG
[chars]: [chars]([dec]) is of unsuppored type:
[dec]
Explanation 'left/right argument is of unsupported type'
Recommended Action *SH_TECH*
Error Message
%MGBL-PARSER-7-ERR_LRD_EVENT
LRd event failed: [chars] Error: '[chars]'
Explanation Registration to LRd failed.
Recommended Action Restart parser_server process after all cards come up.
PM Messages
Error Message
%MGBL-PM-5-CHKPT
[chars] : [chars]
Explanation An error has occurred while doing a checkpointing operation. This may result in loss of
old statistics data during process restart.
Recommended Action No action is required.
Error Message
%MGBL-PM-5-ERR_MEM
[chars]
Explanation The system is running out of memory and was not able to allocate sufficient memory to
carry out a collection operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
Error Message
%MGBL-PM-5-MEMORY_LIMITS
[chars]:[chars]
Explanation Perfmgmt server could not restore configured memory thresholds. Perfmgmt server will
restore the defaults for memory limits.
Recommended Action Reconfigure the memory thresholds via cli.
Error Message
%MGBL-PM-5-TFTP
[chars]:[chars]:[chars]
Explanation An error has occurred while tftp dumping of the collected data from the pm collector
process. This error could error due to various reasons below : a) No tftp server configure in pm
configuration. b) TFTP Server is not reachable. c) TFTP Directory configured does not have write
permissions.
Recommended Action Try eliminating the reasons mentioned in explanation.
Error Message
%MGBL-PM-6-TFTP_DISABLED
[chars]
Explanation This is an informational message.
Recommended Action No action is required.
Error Message
%MGBL-PM-6-TFTP_SEND
[chars]:[chars]
Explanation An informational alarm upon dumping of the collected data on to tftp server.
Recommended Action No action is required.
Error Message
%MGBL-PM-6-THRESHOLD
Entity:[chars], Id:[chars] - Attribute:[chars]:
value:'[unsigned long long int]' threshold: [chars], threshold-op:[chars]
Explanation The Entity Instance has met a threshold condition.
Recommended Action None
Error Message
%MGBL-PM-7-ERR_SYSDB
[chars] : [chars]
Explanation An error has occurred while doing a sysdb operation. See the message text for error
details.
Recommended Action No action is required.
Error Message
%MGBL-PM-7-INTERNAL
[chars]: '[dec]' : [chars]
Explanation The Collector has detected an internal error. Reason of the error is in the message itself.
Some of the errors are self recovering.
Recommended Action If you see any loss of functionality try restarting pm collector and pm server
process.
Error Message
%MGBL-PM-7-WDSYSMON_ERROR
[chars]: [hex]: [chars]
Explanation A wdsysmon api call returned an error. This can happen when the state of a node is
transitioning e.g. a line card is restarted or the node is not booted. The node id is given by the
hexadecimal number after this message and is followed by a more specific error description of the
cause of the failure.
Recommended Action Bring the node up to IOS-XR running stage and then rerun the PM show
command. The node's info should be displayed after the next sample collection interval. If the PM
collection for the node is not configured, configure it.