Cisco IOS XR System Error Message Reference Guide, Release 4.3.x
Manageability (MGBL) Messages
Downloads: This chapterpdf (PDF - 1.0 MB) The complete bookPDF (PDF - 18.29 MB) | Feedback

Table of Contents

Manageability (MGBL) Messages

adminexec Messages

ALARM_LOC_TEST Messages

ALARMS Messages

APP_OBJ Messages

ATM_VCCLASS Messages

CFGHLP Messages

CLEAR Messages

CONAUX Messages

CONFIG_HIST_UPDATE Messages

CONFIG Messages

CONFIGCLI Messages

CONFIGEDM Messages

CORRELATOR Messages

EMORB_XMLAGENT Messages

exec Messages

GSR_NETFLOW Messages

HTTP_CLI Messages

HTTP_ENA Messages

HTTP Messages

IFSTATS Messages

INTERFACE Messages

INVENTORYCI Messages

IPSLA_TS_SVR Messages

IPSLA Messages

LIBNVGEN Messages

LIBPARSER Messages

LIBSHELL Messages

MDACON Messages

NETFLOW Messages

NVGEN Messages

PARSER Messages

PM Messages

PRP_UPGRADE Messages

RS232 Messages

S2681 Messages

SCHBRO Messages

SCHEMA Messages

SCONBKUP Messages

ST16550 Messages

STATSD Messages

SYS Messages

TTY_CONNECT Messages

TTY_DB Messages

TTY Messages

VTY Messages

XML_INFRA Messages

XML_TTY Messages

Manageability (MGBL) Messages

This section contains all Management Plane and Manageability related System Error Messages, including config, cli, sml, pm, and so forth.

adminexec Messages

Error Message %MGBL-adminexec-3-ACCT_ERR

[chars] - [chars]

Explanation failed to send accounting record

Recommended Action Copy the error message exactly as it appears 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-adminexec-3-AUTHORIZATION_ERR

[chars] - [chars]

Explanation Admin exec process failed to send AAA authorization record.

Recommended Action collect the traceback, show log, show proc, show exec trace from SDR and admin modes. Show run and show user out. And contact Copy the error message exactly as it appears 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-adminexec-3-EVENT_ATTACH

Event [chars] attach error: [chars]

Explanation The call to event_*_attach() failed

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MGBL-adminexec-3-EVENT_BLOCK

Error: [chars]

Explanation The call to event_block() 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-adminexec-3-EVENT_MANAGER_CREATE

Failed to create event manager. Error code: [dec]

Explanation The call to event_manager_create() 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-adminexec-3-EVENT_MANAGER_DESTORY_FAILED

[chars]: [chars]

Explanation ’Unable to destroy event manager on exec 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 %MGBL-adminexec-3-GETLINE_DATA

[chars]: [chars]

Explanation ’lib/ui library API related to getline 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-adminexec-3-GETLINE_INIT

[chars]

Explanation getline_init() failed.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MGBL-adminexec-3-LTRACE_INIT

Failed to initialize tracing functionality for adminexec process([dec]). Shell will continue but trace messages will not be generated. Error:[chars]

Explanation Initialization of trace functionality for exec shell failed. This would affect the debugging of exec shell.

Recommended Action Try logging out and login again. If the message appears again, copy and save the message. Collect show logging output and any other suspicious error messages on console and inform technical support representative for assistance.

Error Message %MGBL-adminexec-3-LWM

Failure in lwm API call, [chars]. Error:[chars]

Explanation The LWM 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 %MGBL-adminexec-3-PTHREAD_CREATE

Error code:[dec]. [chars]

Explanation Unable to create exec’s event handling 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 %MGBL-adminexec-3-SYSDB_BIND_FAILED

[chars]. [chars]

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 %MGBL-adminexec-3-SYSDB_REGISTER_NOTIFICATION

sysdb_register_notification failed with error messsage:[chars]

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 %MGBL-adminexec-4-DISPLAYING_DEFAULT_HOSTNAME

failed to detect hostname displaying default: [chars]

Explanation Unable to bind to sysdb to get hostname hence displaying default hostname.

Recommended Action Copy the error message exactly as 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_LOC_TEST Messages

Error Message %MGBL-ALARM_LOC_TEST-4-SIMPLE_NO_SOURCELOC

Normally a bear has [[dec]] eyes and [[dec]] legs, can speak Bearish

Explanation This is a simple message with alarm_location set to false

Recommended Action No action is required.

Error Message %MGBL-ALARM_LOC_TEST-4-SIMPLE_WITH_SOURCELOC

Today the bear has [[dec]] eyes and [[dec]] legs, can speak [[chars]]

Explanation This is a simple message with alarm_location set to true

Recommended Action No action is required.

ALARMS Messages

Error Message %MGBL-ALARMS-6-CLEAR

alarm buffer [chars]: [unsigned int] event(s) deleted

Explanation Some (or all) of the alarms in the alarm buffer have been deleted as a consequence of an action initiated by the user. This message does not require any action. It informs that a clear logging event delete command or an alarm buffer resize operation (or equivalent operation through another management interface) was executed.

Recommended Action No action is required.

APP_OBJ Messages

Error Message %MGBL-APP_OBJ-2-ELEMENT_EXISTS

Inconsistency for element in ENS and app-obj db - ’[chars]’

Explanation The app-obj DB and ENS are inconsistent with registration/existence. of this element.

Recommended Action *SUPPORT*

Error Message %MGBL-APP_OBJ-2-INVALID_ELEM_COUNT

Inconsistency in element count in db: [chars]

Explanation The number of elements in the app-obj DB is inconsistent with the element count.

Recommended Action *SUPPORT*

Error Message %MGBL-APP_OBJ-2-NULL_PARAM

Fatal Error: [chars]

Explanation The parameter specified by the message is unexpectedly null

Recommended Action *SUPPORT*

Error Message %MGBL-APP_OBJ-7-ERR

Nonfatal error: [chars]

Explanation This is an error message in the Netflow manager to indicate anomolies which are not FATAL. Some of the messages may indicate a failure to allocate a resource needed by the application. In many cases these messages must not keep appearing after the temperory situation is resolved.

Recommended Action These error message is does not impact the functionality of NetFlow. Therefore no action is needed.

ATM_VCCLASS Messages

Error Message %MGBL-ATM_VCCLASS-2-CONSUMER_INIT_ERROR

[chars]

Explanation A failure occurred during the initialization of ENS library or during NRS class creation. This probably indicates an underlying more severe 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 %MGBL-ATM_VCCLASS-2-MEM_ERROR

[chars]

Explanation Failed to allocate dynamic memory.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %MGBL-ATM_VCCLASS-2-PRODUCER_INIT_ERROR

[chars]

Explanation A failure occurred during the initialization of ENS library or during NRS class creation. This probably indicates an underlying more severe 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 %MGBL-ATM_VCCLASS-2-VCCLASS_LIB_INIT_ERROR

[chars]

Explanation A failure occurred during the initialization of the common VCCCLASS library. This probably indicates an underlying more severe 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 %MGBL-ATM_VCCLASS-3-ATTACH_ERROR

[chars]

Explanation An ATM VCCLASS consumer has attempted to attach an unknown vcclass to its interface.

Recommended Action Copy the error message exactly as it appears 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-ATM_VCCLASS-3-CONSUMER_ENS_ERROR

[chars]

Explanation One or more ENS or NRS APIs has returned an error. The failure happens while the consumer is calling the ATM VCCLASS 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 %MGBL-ATM_VCCLASS-3-CONSUMER_ERROR

[chars]

Explanation These are general ATM VCCLASS client API 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 %MGBL-ATM_VCCLASS-3-CONSUMER_RCV_BUF_ERROR

[chars]

Explanation The consumer finds one or more invalid fields in the buffer received from the producer.

Recommended Action Copy the error message exactly as it appears 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-ATM_VCCLASS-3-EDM_ERROR

[chars]

Explanation A failure occurred in the ATM VCCLASS EDM backend. As a result the VCCLASS data will not be delievered to the front 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 %MGBL-ATM_VCCLASS-3-ENS_ERROR

[chars]

Explanation One or more ENS or NRS APIs has returned an error. This failure happens on the producer side.

Recommended Action Copy the error message exactly as it appears 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-ATM_VCCLASS-3-INVALID_ARG

[chars]

Explanation One or more input arguments to an internal function 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 %MGBL-ATM_VCCLASS-3-PRODUCER_DATA_ERROR

[chars]

Explanation A failure occurred in the ATM VCCLASS producer while preparing the vcclass data to be sent to ENS.

Recommended Action Copy the error message exactly as it appears 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-ATM_VCCLASS-3-PRODUCER_HDLR_ERROR

[chars]

Explanation A failure occurred in the ATM VCCLASS producer handler while processing requests from the consumer.

Recommended Action Copy the error message exactly as it appears 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-ATM_VCCLASS-3-SYSDB_ERROR

[chars]

Explanation A failure occurred related to SysDB or in one of the verify/apply/notify SysDB callback 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 %MGBL-ATM_VCCLASS-3-TREE_ERROR

[chars]

Explanation A failure occurred while accessing the ATM VCCLASS internal data structrure. There might be an inconsistency between the SysDB and the vcclass tree or the vcclass tree is 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.

CFGHLP Messages

Error Message %MGBL-CFGHLP-6-CONFIG_SAVE_DELAY

Configuration save request delayed [chars] for [dec] seconds for node [chars].

Explanation An attempt to save the node configuration has taken longer than expected. This may be due to a high volume of activity within the configuration management system.

Recommended Action No action is required.

CLEAR Messages

Error Message %MGBL-CLEAR-3-ERR_MEM_ALLOC

Unable to allocate memory to copy: ’[chars]’

Explanation ’Memory allocation 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 %MGBL-CLEAR-3-ERR_SYSDB_BIND

Unable to bind to ’[chars]’: ’[chars]’

Explanation ’Unable to bind to action/gl 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-CLEAR-3-ERR_SYSDB_SET

Unable to set value in path ’[chars]’: ’[chars]’. Probably nothing to clear. (process to clear is not running)

Explanation ’Unable to set the value in the specified 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-CLEAR-3-ERR_SYSDB_UNBIND

sysdb unbind failed: ’[chars]’

Explanation ’Unable to Unbind sysdb bind’ ;

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

CONAUX Messages

Error Message %MGBL-CONAUX-3-AUX_BLOCK_REG_ERROR

Unable to register the aux block ([chars])

Explanation The ConAux Identity module has been unable to register the aux block.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-CONAUX-3-AUX_REG_ERROR

Unable to register the aux TTY ([chars])

Explanation The ConAux Identity module has been unable to register the aux TTY.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-CONAUX-3-CONSOLE_BLOCK_REG_ERROR

Unable to register the console block ([chars])

Explanation The ConAux Identity module has been unable to register the console block.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-CONAUX-3-CONSOLE_REG_ERROR

Unable to register the console TTY ([chars])

Explanation The ConAux Identity module has been unable to register the console TTY.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

CONFIG_HIST_UPDATE Messages

Error Message %MGBL-CONFIG_HIST_UPDATE-3-INET_NTOP_ERR

The call to inet_ntop() failed. Family: [dec]

Explanation 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 %MGBL-CONFIG_HIST_UPDATE-3-SYSDB_BIND_ERR

Can’t bind to sysdb, aborting operation

Explanation 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 %MGBL-CONFIG_HIST_UPDATE-3-SYSDB_DELETE

Error [chars] deleting [chars] from sysdb

Explanation 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 %MGBL-CONFIG_HIST_UPDATE-3-SYSDB_GET

Error [chars] getting [chars] from sysdb

Explanation 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 %MGBL-CONFIG_HIST_UPDATE-3-SYSDB_SET

Error [chars] setting [chars] in sysdb

Explanation 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 %MGBL-CONFIG_HIST_UPDATE-3-TRANSACTION_START

Could not start transaction in, [chars] - abort operation

Explanation 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 %MGBL-CONFIG_HIST_UPDATE-3-TTY_NMSPC_PATH

[chars]

Explanation 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 %MGBL-CONFIG_HIST_UPDATE-3-TUPLE_LOCK_ERROR

Could not lock tuple [chars], in [chars] - abort operation

Explanation 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 %MGBL-CONFIG_HIST_UPDATE-3-TUPLE_NULL_ON_SUCCESS

Got NULL tuple although sysdb reported success in, [chars]

Explanation 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 %MGBL-CONFIG_HIST_UPDATE-3-TUPLE_PACK

Error packing tuple received from sysdb in, [chars]

Explanation 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 %MGBL-CONFIG_HIST_UPDATE-3-TUPLE_UNLOCK_ERROR

Could not unlock tuple [chars], in [chars], line [dec] - will time out eventually.

Explanation 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 %MGBL-CONFIG_HIST_UPDATE-3-TUPLE_UNPACK

Error unpacking tuple received from sysdb in, [chars]

Explanation 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.’

CONFIG Messages

Error Message %MGBL-CONFIG-0-INIT_FAILURE

Configuration Manager was unable to initialize the [chars] module. Error: ’[chars]’. Initialization will be tried again after 60 seconds.

Explanation An error was encountered while initializing one of the critical modules of the configuration manager server. Without proper initialization of this module, configuration manager can not operate properly. Initialization will be retried every 60 seconds if required.

Recommended Action Configuration Manager is a critical component and must be operational in order to configure the router. Please note that if the probem is caused by a system resource shortage continued initilization of the module may repair the problem. If this error is seen more than 5 times, contact Cisco TAC support because a reboot of the node may be required.

Error Message %MGBL-CONFIG-0-INIT_RETRY_SUCCEEDED

Configuration Manager succeeded in initializing the [chars] module upon retry.

Explanation An error was previously encountered while initializing one of the critical modules of the configuration manager server. However, the initialization was retried and succeeded.

Recommended Action No action is required.

Error Message %MGBL-CONFIG-3-ADMIN_INCONSISTENCY_ALARM

Admin plane configuration inconsistency alarm has been [chars]

Explanation The admin plane configuration inconsistency alarm has been raised or cleared.

Recommended Action If the configuration inconsistency alarm has been raised, run ’clear configuration inconsistency’ in admin mode to synchronize the persistent configuration with the running configuration.

Error Message %MGBL-CONFIG-3-CFS_NATIVITY_CLEANUP

Could not clean the local CFS before use. Error: ’[chars]’.

Explanation Local CFS is non-native and automatic cleanup of it has failed.

Recommended Action Run ’commit replace’. If contacting support, please provide trace information from executing command ’show cfgmgr trace location node ID’ for the node with this problem.

Error Message %MGBL-CONFIG-3-DB_CONSOLIDATE

The commit database is not in sync with the running configuration. Please use the command ’cfs check’ to resynchronize the commit database. Error: ’[chars]’

Explanation The chain of configuration changes stored in commit database is possibly broken.

Recommended Action Use the command ’cfs check’ to check/fix the problem.

Error Message %MGBL-CONFIG-3-DB_DISK

[chars]

Explanation The specified storage device is full or some files can not be deleted.

Recommended Action Use the ’delete’ command to free up some space on the storage device.

Error Message %MGBL-CONFIG-3-FILESAVE_ERROR

The OS returned an error while SysDb was attempting to perform a file save operation. Any changes have been rolled back. Error: ’[chars]’

Explanation There was an internal error encountered while attempting to save a file during the user interactive commit operation.

Recommended Action Retry the commit operation and if it gives the same error, copy the error message exactly as it appears 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-CONFIG-3-INCONSISTENCY_ALARM

A configuration inconsistency alarm has been [chars]

Explanation The configuration inconsistency alarm has been raised or cleared.

Recommended Action If the configuration inconsistency alarm has been raised, run ’clear configuration inconsistency’ to synchronize the persistent configuration with the running configuration.

Error Message %MGBL-CONFIG-3-INTERFACE_ERROR

Error encountered while [chars] configuration for ’[chars]’. Some configuration may not have been applied and any missing configuration needs to be reapplied manually. Error: ’[chars]’

Explanation An error was encountered during interface configuration restore/save operation. Some configuration may not have been applied or the line card may be in unusable state.

Recommended Action Reapply the missing configuration. If the interface still doesn’t come up, try restarting the line card.

Error Message %MGBL-CONFIG-3-OIR_TIMEOUT

OIR ’[chars]’ request for interface ’[chars]’ could not be processed due to a pending commit operation or commit database consolidation operation.

Explanation This is an error message to indicate that the configuration could not be either saved or restored because of a pending commit operation or commit database consolidation operation. A manual reset of the node after the pending operation has completed should save or restore the configuration for the node.

Recommended Action Use the command ’show configuration sessions detail’ to verify if the pending operations are still occurring. After the pending commit operation or commit database consolidation operation has completed, use the admin mode command ’hw-module location node reload’ to reset the node and restore its configuration.

Error Message %MGBL-CONFIG-3-PARSE

The platform library failed to parse interface ’[chars]’. Error: [chars].

Explanation The platform library could not parse the interface name.

Recommended Action The interface name flagged as an error could not be parsed by the platform libraries. This interface name should be corrected by the user during the next configuration.

Error Message %MGBL-CONFIG-3-READ

Illegal file read operation of configuration files by this process.

Explanation The process has illegally read configuration files before configuration manager has applied configuration. This configuration read by this process might be inaccurate after configuration manager completes applying the configuration.

Recommended Action Provide traceback details for further analysis. The process emitting this error message may need to be restarted after the node has completely rebooted.

Error Message %MGBL-CONFIG-3-STARTUP

[chars]

Explanation Configuration Manager is displaying an error message during boot time.

Recommended Action Most likely the error has caused some kind of configuration loss that is not saved as failed configuration. Check running configuration and any reported failed startup configuration. Manually reapply any missing running configuration.

Error Message %MGBL-CONFIG-3-UNLOCK_ERR

Error encountered while deleting the configuration lock. Err: ’[chars]’

Explanation An error was encountered during deletion of the configuration lock. This configuration operation (e.g. save/restore configuration, CLI commit) is successful, but subsequent configuration operations could be affected by this error if not corrected.

Recommended Action Use ’show configuration lock’ CLI to view the pending lock and ’clear configuration lock lock’ CLI to force deletion of it.

Error Message %MGBL-CONFIG-4-CFS_NATIVITY

Could not determine the nativity of the local CFS; will assume that it is native. Error: ’[chars]’. Problem: ’[chars]’.

Explanation Could not determine the nativity of the local CFS. If it is native, this message should be ignored; if it is non-native, then automatic cleanup is not done and user intervention is required.

Recommended Action If it is non-native, run ’commit replace’. If contacting support, please provide trace information from executing command ’show cfgmgr trace location node ID’ for the node with this problem.

Error Message %MGBL-CONFIG-4-DB_DISK_FAILURE

[chars]. Please check for problems with the boot device.

Explanation Configuration manager failed to create the set of directories comprising the CFS repository under the cfs root directory. This renders the system practically unusable. The potential problems could range from no space on disk to a flawed disk.

Recommended Action Make sure there’s enough space on disk; or if the storage media is flawed then replace it.

Error Message %MGBL-CONFIG-4-DB_INIT_FAILURE

Commit database initialization Failure. [chars]

Explanation An error was encountered during initialization of the commit database. This is most likely due to an error in reading the commitdb info file, which could be due to disk0: or CFS being corrupted or the file itself being truncated. The system recovers from this situation by cleaning up all files in commitdb if needed and initializing it empty. This may result in loss of all rollback points. However, this should not cause loss of configuration as the system applies the alternate ASCII file maintained for such situations. In certain scenarios, changes made in the last one or two commits may be lost.

Recommended Action None.

Error Message %MGBL-CONFIG-4-DIR_MODE_ERR

Path ’[chars]’. Mode [hex]. Unlink: ’[chars]’.

Explanation This message indicates that the directory path specified in the message has incorrect mode (ie. not a directory). As a corrective action, the software attempts to automatically remove the file. A message of ’No Error’ for unlink, for example, would indicate that it has successfully removed the file.

Recommended Action None.

Error Message %MGBL-CONFIG-4-FAILED

Some ’[chars]’ Configuration could not be restored by Configuration Manager. To view failed config(s) use the command - ’[chars]’

Explanation None

Recommended Action Run the commands specified in the message to browse and reapply the failed configurations.

Error Message %MGBL-CONFIG-4-INIT_ERROR

Configuration Manager was unable to initialize the [chars] module. Error: ’[chars]’. [chars].

Explanation An error was encountered while initializing one of the modules of configuration manager server. The failure of this module initialization is not critical to configuration manager to be completely operational.

Recommended Action Provide the message details to Cisco Support personal.

Error Message %MGBL-CONFIG-4-INTERFACE_PORTS

[chars]: interface [[chars]]

Explanation The total number of ports could not be determined for this interface. Configuration manager will not be able to determine if there is any more configuration for remaining ports.

Recommended Action None.

Error Message %MGBL-CONFIG-4-TRACE

[chars] Error:[chars]

Explanation This is a non-fatal error and can happen when router is low on memory. It should not affect the functioning of the router, but trace messages may not be logged.

Recommended Action None.

Error Message %MGBL-CONFIG-4-VERSION

Version of existing [chars] detected to be incompatible with the installed software. [chars]

Explanation None

Recommended Action The previous saved configuration is not compatible with the current loaded software.

Error Message %MGBL-CONFIG-5-SESSION_CLEAR

Configuration session ID ’[chars]’ (started by user ’[chars]’ from line ’[chars]’) was terminated by user ’[chars]’ from line ’[chars]’.

Explanation This message indicates that the session specified in the message had been cleared via CLI ’clear configuration session seesion_ID’.

Recommended Action None.

Error Message %MGBL-CONFIG-6-DB_COMMIT

Configuration committed by user ’[chars]’. Use ’show configuration commit changes [chars]’ to view the changes.

Explanation An SDR plane configuration change was made by the specified user.

Recommended Action No action is required.

Error Message %MGBL-CONFIG-6-DB_COMMIT_ADMIN

[chars]. Use ’show configuration commit changes [chars]’ to view the changes.

Explanation An administration plane router configuration change occurred by the specified user.

Recommended Action No action is required.

Error Message %MGBL-CONFIG-6-OIR_RESTORE

Configuration for node ’[chars]’ has been restored.

Explanation This is message indicates that configuration for this node has been restored.

Recommended Action None.

Error Message %MGBL-CONFIG-6-OIR_SAVE

Configuration for removed node ’[chars]’ has been saved.

Explanation This is message indicates that configuration for this node has been saved.

Recommended Action None.

Error Message %MGBL-CONFIG-6-PKG

Some incompatible configuration was removed from the running configuration during this software activation/deactivation operation and saved in file ’[chars]’. To address the incompatibility issue enter configuration mode and use the ’load configuration removed [chars]’ and ’commit’ commands.

Explanation Some configuration was removed for this software activation /deactivation operation.

Recommended Action No action is required.

Error Message %MGBL-CONFIG-6-STARTUP_ALTERNATE

[chars]

Explanation Configuration Manager is displaying a message during boot time to indicate an alternate configuration will be restored during the router boot operation. The alternate configuration is specified by the user by using a boot option or ROMMON variable setting.

Recommended Action None.

Error Message %MGBL-CONFIG-7-INTERNAL

[chars]

Explanation An unexpected internal error occurred in the configuration 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.

CONFIGCLI Messages

Error Message %MGBL-CONFIGCLI-2-STARTUP_ANNOUNCE_ERR

Failed to announce the completion of startup configuration. [chars] - ’[chars]’

Explanation Under normal circumstances configuration manager announces the completion of startup configuration. If for some reason config_cli cannot connect to configuration manager then it should announce the completion of startup configuration. This is so that the administrator can perform some basic tasks like configuring the ethernet interface, format a disk, kill some processes, etc., to restore some order to the system for a subsequent reload.

Recommended Action Copy the error message exactly as it appears 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-CONFIGCLI-3-AAA_ERR

Failed to execute a AAA operation - [chars] - [chars]

Explanation Failed to execute a AAA 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 %MGBL-CONFIGCLI-3-ADMIN_BATCH_CONFIG_FAIL

[dec] admin config(s) failed during [chars]. To view failed config(s) use the command - admin show configuration failed startup

Explanation Some admin configurations can not be handled correctly because: - invalid configuration - configuration can not be accepted at this moment

Recommended Action Use ’admin show configuration failed’ to see all the failed configurations.

Error Message %MGBL-CONFIGCLI-3-ADMIN_CONFIG_INIT_ERR

Failed to [chars]: Error: [chars]

Explanation Initialization of admin config cli auto-save commit verifier failed.

Recommended Action Collect show logging output and any other suspicious error messages on console and inform technical support representative for assistance.

Error Message %MGBL-CONFIGCLI-3-AUTOSAVE_INIT_ERR

Failed to [chars]: Error: [chars]

Explanation Initialization of config cli auto-save commit verifier failed.

Recommended Action Collect show logging output, show config failed before exiting from admin config mode, to see which config commit caused this error. Also any other suspicious error messages on console and inform technical support representative for assistance.

Error Message %MGBL-CONFIGCLI-3-BATCH_CONFIG_FAIL

[dec] config(s) failed during [chars]. To view failed config(s) use the command - show configuration failed startup

Explanation Some configurations can not be handled correctly because: - invalid configuration - configuration can not be accepted at this moment

Recommended Action Use ’show configuration failed’ to see all the failed configurations.

Error Message %MGBL-CONFIGCLI-3-CHILD_TERMINATED

[chars] process: abnormal termination, signal number equals [dec]

Explanation A child process received a signal and terminated abnormally.

Recommended Action Copy the error message exactly as it appears 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-CONFIGCLI-3-CONFIG_ABORT

Aborting startup configuration. [chars].

Explanation Failed to get the startup config file name.

Recommended Action *SH_TECH*

Error Message %MGBL-CONFIGCLI-3-EVENT_ATTACH

Event [chars] attach error: [chars]

Explanation The call to event_*_attach() failed. Config CLI library failed to attach events to event manager. The effect is that config-cli would not handle any 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 %MGBL-CONFIGCLI-3-EVH_INIT_ERR

[chars]:Failed to create event manager:[chars]

Explanation Config process is failing to create an event manager. See error for reason.

Recommended Action Copy the error message exactly as it appears 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-CONFIGCLI-3-FAILED_CREATE_THREAD

[chars]:Failed to create the event handling thread:[chars]

Explanation config process is failing to create a separate thread for creating and handling edm requests.

Recommended Action Copy the error message exactly as it appears 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-CONFIGCLI-3-FILE_OPERATION

[chars] : [chars]: [chars]

Explanation config process failed to perform a file operation due to either filesystem restart/busy or an internal error.

Recommended Action This error could happen when config process can not perform a file operation successfully. This is mostly the case when filesystem has restarted or network connectivity is broken (if tftp file). Collect the show context output, config file being copied, show config failed output, console logs, pidin, top output and contact Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.. Workaround: Retry the config operation.

Error Message %MGBL-CONFIGCLI-3-GETLINE_DATA

[chars]: [chars]

Explanation ’lib/ui library API related to getline 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-CONFIGCLI-3-LTRACE_INIT

Failed to initialize tracing functionality for config cli library. No trace messages will be generated. Error:[chars]

Explanation Initialization of trace functionality for config failed. This would affect the debugging of config shell.

Recommended Action Retype the command to do config operation again. If the message appears again, copy and save the message. Collect show logging output and any other suspicious error messages on console and inform technical support representative for assistance.

Error Message %MGBL-CONFIGCLI-3-LTRACE_INIT

Failed to initialize tracing functionality for config process. No trace messages will be logged. Error:[chars]

Explanation Initialisation of trace functionality for config failed. This would affect the debugging of config shell.

Recommended Action Retype the command to do config operation again. If the message appears again, copy and save the message. Collect show logging output and any other suspicious error messages on console and inform technical support representative for assistance.

Error Message %MGBL-CONFIGCLI-3-LWM

Failure in lwm API call, [chars]. Error:[chars]

Explanation The LWM 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 %MGBL-CONFIGCLI-3-MALLOC_ERROR

Failed to allocate memory:[chars]

Explanation System could not successfully provide the request memory 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 %MGBL-CONFIGCLI-3-MEMORY_INFO_ERROR

Unable to get memory info for the current node:[chars]

Explanation Config process failed to get memory state info from wdsysmon when it came up.

Recommended Action Copy the error message exactly as it appears 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-CONFIGCLI-3-PIPE_FAILURE

Unable to create piping subproc: [chars]

Explanation This condition might result in failure of communication between two 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 %MGBL-CONFIGCLI-3-PROGRESS_BAR

[chars]

Explanation Config process bar failed to creation/deletion

Recommended Action *SH_TECH*

Error Message %MGBL-CONFIGCLI-3-READ_FAILURE

Error associating [chars] stream with file descriptor : [chars]

Explanation Read or Write operation not possible as there is an error in associating a stream with 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 %MGBL-CONFIGCLI-3-SIGNAL_ATTACH

config process failed to attach event handler for signal ’[chars]’:[chars]

Explanation Config process is failing to perform event handling intialisation for a signal. The operations could cause bad handling of the signal.

Recommended Action Copy the error message exactly as it appears 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-CONFIGCLI-3-STARTUP_FILE_DIR_ERR

specified source is a ditectory; filename is expected :[chars]

Explanation Failed to open the startup configration file for the following reason: - CONFIG_FILE is set to a directory.

Recommended Action CONFIG_FILE should be set to a valid startup configuration file.

Error Message %MGBL-CONFIGCLI-3-SYSDB

[chars]:[chars]:[chars]

Explanation Config process is failing to perform a sysdb operation. The operation and cause of failure in 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 %MGBL-CONFIGCLI-3-TARGET_CFG_CLEAR

[chars]:Failed to clear target config:[chars]

Explanation Config process failed to clear target config buffer. Configured items will not be cleared from buffer.

Recommended Action *SH_TECH*

Error Message %MGBL-CONFIGCLI-3-TARGET_CFG_COMMIT

[chars]:Failed to commit target config:[chars].

Explanation Config process failed to commit target config buffer. Configured items will not be committed in sysdb.

Recommended Action *SH_TECH*

Error Message %MGBL-CONFIGCLI-3-TARGET_CFG_COMMIT

[chars]:Failed to commit target config:[chars]

Explanation Config process failed to commit target config buffer. Configured items will not be committed in sysdb.

Recommended Action *SH_TECH*

Error Message %MGBL-CONFIGCLI-3-TARGET_CFG_CREATE

[chars]:Failed to create target config:[chars].

Explanation Config process failed to create target config buffer. Configuration can not proceed.

Recommended Action *SH_TECH*

Error Message %MGBL-CONFIGCLI-3-TARGET_CFG_DESTROY

[chars]:Failed to destroy target config:[chars]

Explanation Config process failed to destroy target config buffer.

Recommended Action *SH_TECH*

Error Message %MGBL-CONFIGCLI-3-TARGET_CFG_LOCKERR

[chars]:Failed to obtain exclusive lock for this session:[chars]

Explanation Config process failed to obtain exclusive lock for this session. Terminate the other open sessions and try again.

Recommended Action *SH_TECH*

Error Message %MGBL-CONFIGCLI-3-TARGET_CFG_UNLOCKERR

[chars]:Failed to release the lock held by session:[chars]

Explanation Config process failed to release exclusive lock held by this session.

Recommended Action *SH_TECH*

Error Message %MGBL-CONFIGCLI-4-DISPLAYING_DEFAULT_HOSTNAME

failed to detect hostname displaying default: [chars]: [chars]

Explanation Unable to bind to sysdb to get hostname hence displaying default hostname.

Recommended Action Copy the error message exactly as it appears 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-CONFIGCLI-4-FAILED_CONFIG_NOT_DELETED

failed to delete failed config file: [chars]: [chars]

Explanation The failed_config file should be deleted when all the configurations are successfully reapplied.

Recommended Action Check for failed_config under bootflash:/config and delete the file using ’delete bootflash:/config/failed_config’.

Error Message %MGBL-CONFIGCLI-4-SPAWN_FAILURE

failed to spawn: [chars]: [chars]

Explanation An executable was not spawned 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-CONFIGCLI-4-STARTUP_FILE_OPEN_WRN

failed to open startup file: [chars]: [chars]

Explanation Failed to open the startup configration file for any of the following reasons: - file does not exist. This may be case when booting for the first time or when even the default startup config file does not exist. IGNORE the message in this case. - CONFIG_FILE is set to a directory. - the config file doesn’t exist under the current directory. - Illegal file name. set CONFIG_FILE to a valid file name an retry. - Other system errors. The last part of the error message should give a hint of the system error.

Recommended Action Since the startup configuration file cannot be opened, no run time configuation will be available. Make sure a startup config file exists somewhere and CONFIG_FILE points to it. Run copy running-config startup-config

Error Message %MGBL-CONFIGCLI-7-INFRA_READY

[chars]

Explanation Config process is delaying applying configuration until infrastructure is 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.

CONFIGEDM Messages

Error Message %MGBL-CONFIGEDM-3-FAILEDLIST

Failed to add item to for [chars] - [chars]:[chars]

Explanation ’Config library failed to add node to the given list with the reason mentioned in the message. This may lead to wrong ’show config failed’ listing.’

Recommended Action If the error recurs frequently, it may be possible to rectify it by restarting ’nvgen_server’ process. But please collect the logs mentioned n required info, before restarting the process.

Error Message %MGBL-CONFIGEDM-3-FAILEDREGCOMP

Regular expression compilation failed with error ’[chars]’.

Explanation ’Compiling a regular expression failed with the reason mentioned in the message. This may lead to wrong ’show config failed’ listing.’

Recommended Action Please contact TAC with the output of the following commands: - console logs - show version - show process nvgen_server - show nvgen trace ascii-backup reverse - show configuration history If the error recurs frequently, it may be possible to rectify it by restarting ’nvgen_server’ process. But please collect the logs mentioned above, before restarting the process.

Error Message %MGBL-CONFIGEDM-3-FAILEDREGEXEC

Regular expression match failed with error ’[chars]’.

Explanation ’Regular expression match failed with the reason mentioned in the message. This may lead to wrong ’show config failed’ listing.’

Recommended Action Please contact TAC with the output of the following commands: - console logs - show version - show process nvgen_server - show nvgen trace ascii-backup reverse - show configuration history If the error recurs frequently, it may be possible to rectify it by restarting ’nvgen_server’ process. But please collect the logs mentioned above, before restarting the process.

Error Message %MGBL-CONFIGEDM-3-REGISTER

Failed to initialise edm for [chars] option - [chars]:[chars]

Explanation Config library is failing to initialise the 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 %MGBL-CONFIGEDM-3-UNREGISTER

Failed to unregister edm - [chars]:[chars]

Explanation Failing to unregister the 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.

CORRELATOR Messages

Error Message %MGBL-CORRELATOR-4-BUFFER_RECYCLE

Maximum buffer size [[dec]] reached, deleting correlation ID [[dec]] from correlation buffer

Explanation The alarm correlation buffer is full; the oldest correlation specified in the message is dropped from the buffer to make room for the new correlation.

Recommended Action No action is required.

EMORB_XMLAGENT Messages

Error Message %MGBL-EMORB_XMLAGENT-3-CRYPTO_DEACT

xmlagent process has stopped due to crypto package deactivation. Unconfigure xmlagent with ’no xml agent corba’

Explanation The crypto pie is deactived or removed while xmlagent is running in ssl mode.

Recommended Action Unconfigure xmlagent or configure it to run in non-ssl

Error Message %MGBL-EMORB_XMLAGENT-3-CRYPTO_INIT

xmlagent process exits due to crypto initialization failure. Unconfigure xmlagent with ’no xml agent corba’

Explanation The crypto pie is not properly configured and can’t be initailized

Recommended Action Configure crypto according to crypto setup procedures

Error Message %MGBL-EMORB_XMLAGENT-6-PIPE_RESTART

xmlagent process detected an anomaly with pipe due to possible pipe process restart. xmlagent process is now terminating and will be restarted automatically.

Explanation The pipe process is probably restarted which is caught in TCP_Monitor

Recommended Action just information message, no action is required

Error Message %MGBL-EMORB_XMLAGENT-6-RESTART_WAIT_TIMEOUT

xmlagent process is restarting after wait for configuration completion timeout.

Explanation The xmlagent process is restarting while wait for config operation completion times out. Commit database info may lose

Recommended Action just information message, no action is required

Error Message %MGBL-EMORB_XMLAGENT-6-TCP_RESTART

xmlagent process detected an anomaly with underlying transport layer due to possible TCP process restart. xmlagent process is now terminating and will be restarted automatically.

Explanation The tcp process is probably restarted which is caught in TCP_Monitor

Recommended Action just information message, no action is required

exec Messages

Error Message %MGBL-exec-3-ACCT_ERR

[chars]: [chars] - [chars]

Explanation failed to send accounting record

Recommended Action Copy the error message exactly as it appears 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-exec-3-BAG_REGISTER

[chars]: [chars]

Explanation The call to bag_register_all_outgoing_conn_bag() 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-exec-3-CHDIR_FAILED

Unable to chdir [chars]:[chars]

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 %MGBL-exec-3-DEBUG_DLL_HOOK_FAILED

[chars]: debug_dll_hook() - ([chars])

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 %MGBL-exec-3-DEBUGINIT

Debug initialization failed: [chars]

Explanation ’Failed to initialize a debugging event for the reason listed in’ ’ the message’

Recommended Action *SH_TECH*

Error Message %MGBL-exec-3-DEBUGREG

Debug registration failed: [chars]

Explanation ’Debug registration failed for the reason listed in the message.’

Recommended Action *SH_TECH*

Error Message %MGBL-exec-3-EVENT_ATTACH

Event [chars] attach error: [chars]

Explanation The call to event_*_attach() failed

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MGBL-exec-3-EVENT_BLOCK

Error: [chars]

Explanation The call to event_block() 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-exec-3-EVENT_INIT_EVENT

[chars]: Error code: [dec]

Explanation The call to event_init_event() 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-exec-3-EVENT_MANAGER_CREATE

[chars]: Failed to create event manager. Error code: [dec]

Explanation The call to event_manager_create() 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-exec-3-EVENT_MANAGER_DESTORY_FAILED

[chars]: [chars]: [chars]

Explanation ’Unable to destroy event manager on exec 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 %MGBL-exec-3-GET_ENVPATH

Unable to get path for env var [chars]

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 %MGBL-exec-3-GETLINE_DATA

[chars]: [chars]

Explanation ’lib/ui library API related to getline 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-exec-3-GETLINE_INIT

[chars]: [chars]

Explanation getline_init() failed.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MGBL-exec-3-LOGIN_AUTHEN

[chars]

Explanation login() 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-exec-3-LOGIN_ECM_CONN_SYSDB_FAILED

[chars]: Call to login_ecm_conn_sysdb() failed.

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 %MGBL-exec-3-LTRACE_INIT

Failed to initialize tracing functionality for exec process([dec]). Exec shell will continue but trace messages will not be generated. Error:[chars]

Explanation Initialization of trace functionality for exec shell failed. This would affect the debugging of exec shell.

Recommended Action Try logging out and login again. If the message appears again, copy and save the message. Collect show logging output and any other suspicious error messages on console and inform technical support representative for assistance.

Error Message %MGBL-exec-3-LWM

Failure in lwm API call, [chars]. Error:[chars]

Explanation The LWM 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 %MGBL-exec-3-MUTEX_LOCK

Error code: [dec]. [chars]

Explanation Unable to create exec’s event handling 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 %MGBL-exec-3-PARSER_UNAVAIL

[chars]: [chars]

Explanation shell_parser_init() failed.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MGBL-exec-3-PTHREAD_CREATE

Error code:[dec]. [chars]

Explanation Unable to create exec’s event handling 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 %MGBL-exec-3-PTHREAD_MUTEX_LOCK

[chars]: pthread_mutex_lock failed with error messsage:[chars]

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 %MGBL-exec-3-PTHREAD_MUTEX_UNLOCK

[chars]: pthread_mutex_unlock failed with error messsage:[chars]

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 %MGBL-exec-3-SETENV_FAILED

Unable to set [chars]:[chars]

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 %MGBL-exec-3-SYSDB_BIND_FAILED

[chars]: sysdb_bind failed. [chars]

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 %MGBL-exec-3-SYSDB_ITEM_DELETE_FAILED

[chars]: sysdb_item_delete() failed. [chars]

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 %MGBL-exec-3-SYSDB_ITEM_GET_FAILED

[chars]: sysdb_item_get failed. [chars]

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 %MGBL-exec-3-SYSDB_REGISTER_EDM

Exec failed to register EDM: [[hex]] [chars]

Explanation Exec registers its EDM path for storing data. This registration of EDM has failed due to reasons mentioned in the error message. This failure could cause, exec session not to start up or could cause problem in entering configuration submodes.

Recommended Action Close the exec session and relogin. If the message recurs, copy and save the message and call your technical support representative for assistance.

Error Message %MGBL-exec-3-SYSDB_REGISTER_NOTIFICATION

[chars]: sysdb_register_notification failed with error messsage:[chars]

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 %MGBL-exec-3-SYSDB_UNBIND_FAILED

[chars]: sysdb_unbind failed. [chars]

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 %MGBL-exec-3-TASKMAP_GET

Unable to obtain user’s taskmap via ([chars]):[chars]

Explanation When exec is launched by certain clients like ssh/Fault-manager the authentication is bypassed. It is because authentication is done by clients already. In this case exec needs to obtain the user’s taskmap though. This is done by calling suitable AAA apis. If one of the apis fails, then this ios msg is emitted.

Recommended Action Close the exec session and relogin. If the message recurs, copy and save the message and call your technical support representative for assistance.

Error Message %MGBL-exec-3-TCGETATTR_FAIL

[chars]: tcgetattr call failed with error [dec] [chars]

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 %MGBL-exec-3-TCSETATTR_FAIL

[chars]: tcsetattr call failed with error [dec] [chars]

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 %MGBL-exec-3-TTY_DETAILS

[chars]: [chars]

Explanation tty_details_from_device_file() 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-exec-3-TTY_MGMT_CONNECT

[chars]: [chars]

Explanation The call to tty_mgmt_connect() 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-exec-3-TTY_MGMT_DEREGISTER

[chars]: [chars]

Explanation The call to tty_mgmt_deregister_tty_options() 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-exec-3-TTY_MGMT_REG_SUBSET

[chars]: Error:[dec]. [chars]

Explanation The call to tty_mgmt_register_tty_subset() 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-exec-3-TTY_MGMT_SCAN

[chars]: [chars]

Explanation The call to tty_mgmt_scan() 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-exec-3-TUPLE_PACK

[chars]: [chars]

Explanation The call to tuple_pack() 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-exec-3-TUPLE_UNPACK

[chars]: [chars]

Explanation The call to tuple_unpack() 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-exec-3-TUPLE_UNPACK_MASK

[chars]: [chars]

Explanation The call to tuple_unpack_mask() 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-exec-6-TTY_MGMT_REG_OPTIONS

[chars]: Error code: [dec]. Description: [chars]

Explanation The call to tty_mgmt_register_tty_options() 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.

GSR_NETFLOW Messages

Error Message %MGBL-GSR_NETFLOW-3-ERR_INIT

Init Error: [chars]

Explanation The process nf_gsr_perf encountered a software error while initializing.

Recommended Action The process will be restarted to recover from the error without any negative impact. If the message recurs, copy the error message exactly as it appears 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-GSR_NETFLOW-3-HW_PROG

HW Programming Failed: [chars]

Explanation A problem is detected in programming the hardware.

Recommended Action Remove the existing Netflow config and reapply it again. If the message recurs, copy the error message exactly as it appears 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-GSR_NETFLOW-7-ERR

Nonfatal error: [chars]

Explanation This is an error message in the nf_gsr_perf process to indicate anomolies which are not FATAL.In many cases these messages must not keep appearing after the temperory situation is resolved.

Recommended Action These error message does not impact the functionality of NetFlow. Therefore no action is needed.

HTTP_CLI Messages

Error Message %MGBL-HTTP_CLI-3-AAA

[chars]

Explanation An AAA operation carried out by the HTTP CLI Agent returned unexpected 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 %MGBL-HTTP_CLI-3-AAA

[chars]

Explanation An AAA operation carried out by the HTTP CLI Agent returned unexpected 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 %MGBL-HTTP_CLI-3-EMWEB

An EmWeb function to [chars] returned an error to the HTTP CLI Agent

Explanation The HTTP CLI Agent was unable to carry out an EmWeb server function. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-EMWEB

An EmWeb function to [chars] returned an error to the HTTP CLI Agent

Explanation The HTTP CLI Agent was unable to carry out an EmWeb server function. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-FILE

[chars], Error: [chars]

Explanation The HTTP CLI Agent was unable to carry out an operation on an internal file. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-FILE

[chars], Error: [chars]

Explanation The HTTP CLI Agent was unable to carry out an operation on an internal file. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-INTERNAL

[chars]

Explanation The HTTP CLI Agent has encountered an invalid state - this point in the code should not have been reached. The HTTP process may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-INTERNAL

[chars]

Explanation The HTTP CLI Agent has encountered an invalid state - this point in the code should not have been reached. The HTTP process may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-INTERNAL_NULL

A NULL pointer was passed by the HTTP CLI Agent to itself

Explanation The HTTP CLI Agent has passed itself a NULL pointer when it should not have done - this point in the code should not have been reached. The HTTP process may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-INTERNAL_NULL

A NULL pointer was passed by the HTTP CLI Agent to itself

Explanation The HTTP CLI Agent has passed itself a NULL pointer when it should not have done - this point in the code should not have been reached. The HTTP process may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-INTERNAL_PARAMETER

[chars]

Explanation The HTTP CLI Agent has passed itself an invalid parameter - this point in the code should not have been reached. The HTTP process may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-INTERNAL_PARAMETER

[chars]

Explanation The HTTP CLI Agent has passed itself an invalid parameter - this point in the code should not have been reached. The HTTP process may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-MEMORY

The HTTP CLI Agent was unable to allocate [unsigned int] bytes of memory

Explanation The HTTP CLI Agent was unable to allocate the required amount of memory, as the HTTP process has run out of resources. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-MEMORY

The HTTP CLI Agent was unable to allocate [unsigned int] bytes of memory

Explanation The HTTP CLI Agent was unable to allocate the required amount of memory, as the HTTP process has run out of resources. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-PARSER

[chars]

Explanation A Parser operation carried out by the HTTP CLI Agent returned unexpected 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 %MGBL-HTTP_CLI-3-PARSER

[chars]

Explanation A Parser operation carried out by the HTTP CLI Agent returned unexpected 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 %MGBL-HTTP_CLI-3-SYSDB

[chars] ’[chars]’

Explanation A SysDB operation carried out by the HTTP CLI Agent returned unexpected 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 %MGBL-HTTP_CLI-3-SYSDB

[chars] ’[chars]’

Explanation A SysDB operation carried out by the HTTP CLI Agent returned unexpected 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 %MGBL-HTTP_CLI-3-SYSDB_CONN

The HTTP CLI Agent was unable to create a connection to SysDB

Explanation The HTTP CLI Agent was unable to create a connection to the SysDB component. It may be that the communication infrastructure is faulty, or that the SysDB component has not yet restarted. If the errors persist, the router may need to be 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 %MGBL-HTTP_CLI-3-SYSDB_CONN

The HTTP CLI Agent was unable to create a connection to SysDB

Explanation The HTTP CLI Agent was unable to create a connection to the SysDB component. It may be that the communication infrastructure is faulty, or that the SysDB component has not yet restarted. If the errors persist, the router may need to be 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 %MGBL-HTTP_CLI-3-SYSDB_GET

The HTTP CLI Agent was unable to retrieve the item [chars] from SysDB

Explanation The HTTP CLI Agent was unable to retrieve the specified item from the SysDB component.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-SYSDB_GET

The HTTP CLI Agent was unable to retrieve the item [chars] from SysDB

Explanation The HTTP CLI Agent was unable to retrieve the specified item from the SysDB component.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-THREAD

[chars], Error: [chars]

Explanation The HTTP CLI Agent was unable to carry out an operation on an internal thread. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-3-THREAD

[chars], Error: [chars]

Explanation The HTTP CLI Agent was unable to carry out an operation on an internal thread. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_CLI-5-WARN

[chars]

Explanation No error has occurred, but you should be aware that an unusual or unwanted situation may have arisen, and you may want to take preventation action as outlined in the warning message.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MGBL-HTTP_CLI-5-WARN

[chars]

Explanation No error has occurred, but you should be aware that an unusual or unwanted situation may have arisen, and you may want to take preventation action as outlined in the warning message.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

HTTP_ENA Messages

Error Message %MGBL-HTTP_ENA-3-AUTH

[chars]

Explanation Authentication related error occured or returned unexpected 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 %MGBL-HTTP_ENA-3-AUTH

[chars]

Explanation Authentication related error occured or returned unexpected 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 %MGBL-HTTP_ENA-3-BACKEND_SCAN

The HTTP Server was unable to carry out a backend scan on the SysDB item [chars]

Explanation The HTTP Server was unable to retrieve the specified item(s) from the SysDB component.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-BACKEND_SCAN

The HTTP Server was unable to carry out a backend scan on the SysDB item [chars]

Explanation The HTTP Server was unable to retrieve the specified item(s) from the SysDB component.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-CRYPTO_DEACT

HTTP server process has exited due to crypto package deactivation. Please unconfigure this command via ’no http server’.

Explanation The crypto pie is deactived or removed while http server is running in ssl mode.

Recommended Action Unconfigure http server or configure it to run in non-ssl

Error Message %MGBL-HTTP_ENA-3-CRYPTO_DEACT

HTTP server process has exited due to crypto package deactivation. Please unconfigure this command via ’no http server’.

Explanation The crypto pie is deactived or removed while http server is running in ssl mode.

Recommended Action Unconfigure http server or configure it to run in non-ssl

Error Message %MGBL-HTTP_ENA-3-EMWEB

An EmWeb function to [chars] returned an error to the HTTP ENA filesystem handler

Explanation The HTTP ENA filesystem handler was unable to carry out an EmWeb server function. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-EMWEB

An EmWeb function to [chars] returned an error to the HTTP ENA filesystem handler

Explanation The HTTP ENA filesystem handler was unable to carry out an EmWeb server function. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-EVENT_MGR

[chars], Error: [chars]

Explanation An Event Manager operation carried out by the HTTP ENA filesystem handler returned unexpected results. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-EVENT_MGR

[chars], Error: [chars]

Explanation An Event Manager operation carried out by the HTTP ENA filesystem handler returned unexpected results. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-FILE

[chars], Error: [chars]

Explanation The HTTP ENA filesystem handler was unable to carry out an operation on an internal file. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-FILE

[chars], Error: [chars]

Explanation The HTTP ENA filesystem handler was unable to carry out an operation on an internal file. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-INTERNAL_NULL

A NULL pointer was passed by the HTTP ENA filesystem handler to itself

Explanation The HTTP ENA filesystem handler has passed itself a NULL pointer when it should not have done - this point in the code should not have been reached. The HTTP process may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-INTERNAL_NULL

A NULL pointer was passed by the HTTP ENA filesystem handler to itself

Explanation The HTTP ENA filesystem handler has passed itself a NULL pointer when it should not have done - this point in the code should not have been reached. The HTTP process may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-MEMORY

The HTTP ENA filesystem handler was unable to allocate [unsigned int] bytes of memory

Explanation The HTTP ENA filesystem handler was unable to allocate the required amount of memory, as the HTTP process has run out of resources. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-MEMORY

The HTTP ENA filesystem handler was unable to allocate [unsigned int] bytes of memory

Explanation The HTTP ENA filesystem handler was unable to allocate the required amount of memory, as the HTTP process has run out of resources. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP_ENA-3-SSL_INIT

HTTP SSL init failed

Explanation The HTTP Server SSL 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 %MGBL-HTTP_ENA-3-SSL_INIT

HTTP SSL init failed

Explanation The HTTP Server SSL 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 %MGBL-HTTP_ENA-3-SYSDB

[chars] ’[chars]’

Explanation A SysDB operation carried out by the HTTP Server returned unexpected 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 %MGBL-HTTP_ENA-3-SYSDB

[chars] ’[chars]’

Explanation A SysDB operation carried out by the HTTP Server returned unexpected 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 %MGBL-HTTP_ENA-3-SYSDB_CONN

The HTTP Server was unable to create a connection to SysDB

Explanation The HTTP Server was unable to create a connection to the SysDB component. It may be that the communication infrastructure is faulty, or that the SysDB component has not yet restarted. If the errors persist, the router may need to be 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 %MGBL-HTTP_ENA-3-SYSDB_CONN

The HTTP Server was unable to create a connection to SysDB

Explanation The HTTP Server was unable to create a connection to the SysDB component. It may be that the communication infrastructure is faulty, or that the SysDB component has not yet restarted. If the errors persist, the router may need to be 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 %MGBL-HTTP_ENA-6-TCP_FAIL

HTTP server is restarting since underlying transport is not available.

Explanation TCP accept call failed, the HTTP server can’t function.

Recommended Action No action is required. The server will automatically restart

Error Message %MGBL-HTTP_ENA-6-TCP_FAIL

HTTP server is restarting since underlying transport is not available.

Explanation TCP accept call failed, the HTTP server can’t function.

Recommended Action No action is required. The server will automatically restart

Error Message %MGBL-HTTP_ENA-7-TCP_UNKNOWN

HTTP server encountered unexpected TCP error during accept function call, the errno is: [dec]. If this message continues to appear, try restarting the HTTP server.

Explanation TCP accept call failed, the HTTP server can’t function.

Recommended Action No action is required. The server will continue.

Error Message %MGBL-HTTP_ENA-7-TCP_UNKNOWN

HTTP server encountered unexpected TCP error during accept function call, the errno is: [dec]. If this message continues to appear, try restarting the HTTP server.

Explanation TCP accept call failed, the HTTP server can’t function.

Recommended Action No action is required. The server will continue.

HTTP Messages

Error Message %MGBL-HTTP-3-EMWEB_ERROR

[chars]

Explanation The EmWeb code has encountered an error condition or state. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action Restart http server if the errors persist.

Error Message %MGBL-HTTP-3-EMWEB_ERROR

[chars]

Explanation The EmWeb code has encountered an error condition or state. The HTTP process may no longer be able to function correctly, and may need restarting if the errors persist.

Recommended Action Restart http server if the errors persist.

Error Message %MGBL-HTTP-6-CRYPTO_DEACT

HTTP server over ssl would not work correctly due to crypto package deactivation. Please unconfigure this command via ’no http server ssl’.

Explanation The crypto pie is deactived or removed while http server is running in ssl mode.

Recommended Action Unconfigure http server or configure it to run in non-ssl

Error Message %MGBL-HTTP-7-DEBUGGING

[chars], Error: [chars]

Explanation A Debugging operation carried out by the HTTP Server returned unexpected 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 %MGBL-HTTP-7-DEBUGGING

[chars], Error: [chars]

Explanation A Debugging operation carried out by the HTTP Server returned unexpected 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 %MGBL-HTTP-7-INTERNAL

[chars]

Explanation The HTTP Server has encountered internal error conditions or this point in the code should not have been reached. The HTTP process may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-HTTP-7-INTERNAL

[chars]

Explanation The HTTP Server has encountered internal error conditions or this point in the code should not have been reached. The HTTP process may need restarting if the errors persist.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

IFSTATS Messages

Error Message %MGBL-IFSTATS-3-COUNTER_OVERRUN

Counter overrun for one or more deltas for interface [chars], stats type [unsigned int], from collector [chars], on node [chars]. Overrun counters: [chars]example overrun value: [unsigned long long int]

Explanation The statistics infrastructure has received an update from a stats collector for which one or more values are erroneously high, and may cause the datarate calculation to wrap. This message indicates a bug exists in the relevant stats collector. The collector’s node and jid will be indicated in the error message. The output of ’show statsd collector brief’ can be used to determine what process the JID belongs to.

Recommended Action Copy the error message exactly as it appears 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-IFSTATS-3-INIT

Init failure: [chars]: [chars]

Explanation A fatal error was encountered during initialization.

Recommended Action If the process does not restart automatically then try manually restarting it. A likely cause for this error is that the system has run out of memory. In this case reduce system activity by killing non-essential processes. If this is not an out-of-memory problem and restarting the process does not solve it then contact support.

Error Message %MGBL-IFSTATS-3-LOAD_INTERVAL_CONFIG

Failed to apply load-interval configuration for [unsigned int] interfaces: [chars]

Explanation The statistics infrastructure failed to apply load-interval configuration for some interfaces. This means that the data rates reported for the affected interfaces (in ’show interfaces’, for example) may not cover the time periods specified in the running load-interval configuration.

Recommended Action Restart the global Stats Manager process (statsd_manager_g). If the error is still seen, re-apply the load-interval configuration for all interfaces. Copy the error message exactly as it appears 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-IFSTATS-3-MESSAGE_SIZE

Received a stats message which was [chars] from sender [chars] on node [chars].

Explanation This stats manager handled a message which didn’t meet the expected size requirements.

Recommended Action Some statistics related to the specified collector may be lost. There is no other detrimental effect. Copy the error message exactly as it appears 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-IFSTATS-3-MISSING_STATS

This Stats Manager has gone active prior to completion of inital data transfer - statistics for some or all interfaces may have been cleared.

Explanation An RP switchover occurred before the standby stats manager (now active) was able to complete an initial sync with the previously active stats manager. As such, some or all statistics data maintained by this stats manager may have been lost. Depending on how much data was transferred prior to the RP switchover, some or all statistics may be impacted. The ’last discontinuity’ timestamp for each item of interface statistics will indicate whether the statistics for that interface have been preserved or not.

Recommended Action None. There is no way to recover any statistics that have been lost. However, note that the operation of the statistics infrastructure is not impacted and subsequent statistics collection will function as normal.

Error Message %MGBL-IFSTATS-3-TYPE_LOOKUP

Stats type ID lookup for feature ’[chars]’, item ’[chars]’ by client with node [hex], job [unsigned int] failed. Statistics collection for this process may not operate correctly. Error: [chars]

Explanation The process that is described by the node ID and job ID in this message sent a request for a stats type ID that cannot be handled. This will result in a failure to register for statistics collection.

Recommended Action Restarting the process described in this message will cause the request to be resent. Copy the error message exactly as it appears 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-IFSTATS-3-TYPE_UPDATE

Stats type ID update for feature ’[chars]’, item ’[chars]’, ID [unsigned int], by client with node [hex], job [unsigned int] failed. Statistics collection for this process may not operate correctly. Error: [chars]

Explanation The process that is described by the node ID and job ID in this message sent a request for a stats type ID that cannot be handled. This will result in a failure to register for statistics collection.

Recommended Action Restarting the process described in this message will cause the request to be resent. Copy the error message exactly as it appears 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-IFSTATS-4-COLLECTOR_TIMEOUT

A stats collector has timed out during a request: Node [chars], PID [chars]

Explanation The stats collector process that is described by the Node and PID in this message has timed out during a stats request. This may result in some stats being out of date.

Recommended Action If this continues to be seen then investigate the process that is causing this message. If the Node and PID are ’UNKNOWN’ then ’show proc blocked’ should be used to find the unresponsive collector.

Error Message %MGBL-IFSTATS-4-ERR_EVENT_WAIT

Error waiting for event: [chars].

Explanation The event loop has received a message of a type it does not recognize. All events should be received by handlers. This message is only a warning and does not represent a problem in its own right.

Recommended Action If the process is otherwise working OK then a one-off occurrance of this message can be ignored. If the process is experiencing other problems then include this error message in the details given to support.

Error Message %MGBL-IFSTATS-6-CLEAR_COUNTERS

Clear counters on [chars]

Explanation Counters on one or more interfaces have been cleared by the user. This message is for information only.

Recommended Action None.

INTERFACE Messages

Error Message %MGBL-INTERFACE-3-CI_GEN_ERROR

Interface CI DLL error:[chars] [dec]

Explanation Failed to do DLL operation

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message %MGBL-INTERFACE-3-CI_NOMEM_ERROR

Interface CI DLL error:[chars]

Explanation Failed to do DLL operation

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message %MGBL-INTERFACE-4-ERR_SYSDB_BAG_DECODE

Failed decode [chars] data, Error : [chars]

Explanation Failed to decode data retrieved from database

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message %MGBL-INTERFACE-4-ERR_SYSDB_BIND

Path : [chars], Error : [chars]

Explanation Failed to bind to system database. Interface stats retrieval could fail because of this error

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

INVENTORYCI Messages

Error Message %MGBL-INVENTORYCI-3-INIT_ERROR

Failure during initialization. Error: [chars].

Explanation A failure occured during the initialization of the process.

Recommended Action Restart mibd_entity

IPSLA_TS_SVR Messages

Error Message %MGBL-IPSLA_TS_SVR-3-EVENT

Error while processing event ([chars])

Explanation An error occurred while processing an event at the time stamp server event manager

Recommended Action This is an unusual situation which should not occur under normal circumstances. If the situation persists it may require the restart of the time stamping process.

Error Message %MGBL-IPSLA_TS_SVR-3-INIT

Failed to initialize [chars]:[chars]

Explanation Time stamp server failed to perform initialization task. The initialization step where it failed and the exact error are mentioned in the message.

Recommended Action This could happen in a fatal situation. Such as system low on resources or communication failures. 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.

IPSLA Messages

Error Message %MGBL-IPSLA-4-ERR_MEM

[chars]

Explanation IPSLA modules are failed to allocate memory due to low memory conditions in the System.

Recommended Action Increase System Memory or stop some applications which are not required.

Error Message %MGBL-IPSLA-4-ERR_MPLSLM

MPLSLM([dec]) [chars]: [chars]

Explanation IPSLA MPLS LSP Monitor module has failed to perform an operation.

Recommended Action See the message text for details of failure.

Error Message %MGBL-IPSLA-4-ERR_OPER

OP:[dec].[chars].[chars]

Explanation IPSLA operation module has failed to perform an operation.

Recommended Action See the message text for details of failure.

Error Message %MGBL-IPSLA-5-INTERNAL

[chars]:[dec]:[chars]

Explanation IPSLA module incurred an internal error. This could happen in various situations. Such as system low on memory or communication failures with other processes.

Recommended Action Try restarting the IPSLA process showing this error.

Error Message %MGBL-IPSLA-5-LPD_RESULT_CHG

Op:[unsigned int] Tree trace for target address [chars] [chars] (retcode: [chars])

Explanation Result of the LSP Path Discovery has changed for the operation. In case of a failure, the value of the retcode field indicates the cause of the failure. Refer to the Textual Convention RttMplsVpnMonLpdFailureSense at the CISCO-RTTMON-MIB for possible reported causes.

Recommended Action When result changes to a value other than ’OK’, it means that the ECMP discovery could not be completed successfully for the particular period. When paths are reported as broken or unexplorable, identify the available paths through the ’show ipsla mpls lsp-monitor lpd summary’ command and use the ’traceroute mpls’ tool to collect more information about the failure.

Error Message %MGBL-IPSLA-5-LSP_GROUP_CHG

Op:[unsigned int] for target address [chars] from [chars] to [chars]

Explanation LSP Group status has changed for the operation. This is a result of some/all of the ECMPs monitored by the operation changing their status to Up or Down. Refer to the Textual Convention RttMplsVpnMonLpdGrpStatus at the CISCO-RTTMON-MIB for possible reported status values.

Recommended Action When status of the group changes to ’Down’ or ’Partial’, check the output of ’show ipsla statistics group_id’ and look for those reported paths with ’Path Sense’ value different from 1. Run ’traceroute mpls’ for the failed paths to collect more information about the failure.

Error Message %MGBL-IPSLA-5-THRESHOLD_CLEAR

Monitor element has reset the threshold reaction. Op:[unsigned int], TargetAddr:[chars], MonElem:[chars]([chars])

Explanation A threshold condition has cleared for the operation

Recommended Action None.

Error Message %MGBL-IPSLA-5-THRESHOLD_SET

Monitor element has exceeded the threshold condition. Op:[unsigned int], TargetAddr:[chars], MonElem:[chars]([chars])

Explanation A threshold condition has raised for the operation

Recommended Action None

Error Message %MGBL-IPSLA-6-DISC_LIMIT

[chars]

Explanation Discovered PE targets has exceeded the maximum number.

Recommended Action Dicrease PEs in a topology or stop ipsla mpls-lsp-monitor which are not required.

Error Message %MGBL-IPSLA-7-AGENT

[chars]:id(gid:[dec],nid:[dec],pid:[dec]):[chars]

Explanation An operation on agent table is failed. Error message displays operation:error.

Recommended Action None

Error Message %MGBL-IPSLA-7-ERR_SYSDB

[chars]:[chars]

Explanation A sysdb operation failed. See error message text for details of error. This may impact some functionality of IPSLA depending upon where the error occured.

Recommended Action None

LIBNVGEN Messages

Error Message %MGBL-LIBNVGEN-3-CIDR_API_ERR

[chars] Error - [chars]

Explanation Failure in check_cidr_knob API, input parameter is a NULL pointer’

Recommended Action Collect the following logs and contact your technical support representative for assistance. a) Console messages b) show tech-support parser

Error Message %MGBL-LIBNVGEN-3-ERR_MEM_ALLOC

[chars]: memory allocation routine failed

Explanation ’The system has run out of memory’

Recommended Action Collect the following logs and contact your technical support representative for assistance. a) show memory summary location Current RP Location b) ’show process nvgen_server’ and get JID of this process c) show memory heap dllname JID of nvgen_server process If conditions warrant, upgrade to a larger memory configuration.

Error Message %MGBL-LIBNVGEN-3-ERR_SYSDB_BIND

sysdb_bind: [chars], [chars]

Explanation ’Unable to bind to sysdb. The error is displyed in the error message.’

Recommended Action Collect the following logs and contact your technical support representative for assistance. a) Console logs b) show tech-support parser c) show tech-support sysdb

Error Message %MGBL-LIBNVGEN-3-ERR_SYSDB_ITEM_GET

sysdb_item_get: [chars], [chars]

Explanation ’Unable to get the item from sysdb. The error is displyed in the error message.’

Recommended Action Collect the following logs and contact your technical support representative for assistance. a) Console logs b) show tech-support parser c) show tech-support sysdb

Error Message %MGBL-LIBNVGEN-3-ERR_THREAD_MUTEX_LOCK

[chars]: [chars]

Explanation ’The call to pthread_mutex_lock() was unsuccessful’

Recommended Action Collect the following logs and contact your technical support representative for assistance. a) Console messages b) show tech-support parser c) follow process nvgen_server d) show proces blocked e) follow process Name of process on which nvgen is blocked

Error Message %MGBL-LIBNVGEN-3-ERR_THREAD_MUTEX_UNLOCK

[chars]: [chars]

Explanation ’The call to pthread_mutex_unlock() was unsuccessful’

Recommended Action Collect the following logs and contact your technical support representative for assistance. a) Console messages b) show tech-support parser c) follow process nvgen_server d) show proces blocked e) follow process Name of process on which nvgen is blocked

Error Message %MGBL-LIBNVGEN-3-GENERAL_ERR

[chars] Error - [chars]

Explanation General error in nvgen client library’

Recommended Action Collect the following logs and contact your technical support representative for assistance. a) Console messages b) show tech-support parser

Error Message %MGBL-LIBNVGEN-3-LTRACE_INIT

Failed to initialize tracing functionality, error: ([unsigned int]) [chars].

Explanation Initialisation of trace functionality for nvgen failed. This would affect the debugging of nvgen.

Recommended Action If the message recurs, copy and save the message and call your technical support representative for assistance.

Error Message %MGBL-LIBNVGEN-3-LWM_API_ERR

[chars], ’[chars]’: Error - ’[chars]’

Explanation Failure in LWM client API.

Recommended Action Collect the following logs and contact your technical support representative for assistance. a) Console messages b) show tech-support parser

LIBPARSER Messages

Error Message %MGBL-LIBPARSER-3-AAA_STRING_TASKID_CHECK

Error in checking taskid:’[chars]’

Explanation ’Special taskid string check against user taskmap 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-LIBPARSER-3-ADD_SESSION

[chars]: Unable to create an entry for suspended connection: [dec]

Explanation ’The call to add_session() was unsuccessful’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-API_FAIL

[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-LIBPARSER-3-COMMENT_LIMIT

Total length of the comment reached its limit.

Explanation The total length of comment permitted for a command is 1024. Multiple lines of comments associated for a command is considered as a single comment for that command and the total length of all the comments would be considered as the total length of the comment associated to that command. This allowed limit would approximate to 10 lines of comments of width 100. Any more lines of comments 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 %MGBL-LIBPARSER-3-ERR_DLL_UNKNOWN

Failed to locate DLL: [chars] specified in tree ’[chars]’

Explanation ’An error occurred when trying to open the dll library specified in command tree. This failure will cause the command tree unload.’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-ERR_DLL_UNKNOWN_FUNC

Failed to locate function: [chars] in DLL ’[chars]’

Explanation ’An error occurred when trying to locate the dll function in DLL.’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-ERR_ETIMEOUT

Timeout reading file. If tftp, try increasing the timeout value with config CLI ’tftp client timeout’. Error: [chars]

Explanation ’Error while reading the file, Aborting the connection.’

Recommended Action Please consider increasing the tftp timeout value using, config CLI tftp client timeout.

Error Message %MGBL-LIBPARSER-3-ERR_INVALID_DATA

Unknown or wrong Input: [chars]

Explanation ’Wrong/Unknown Input’

Recommended Action Copy the error message exactly as it appears 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-LIBPARSER-3-ERR_MEM_ALLOC

[chars]: memory allocation routine failed

Explanation ’The system has run out of memory’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-ERR_PARSE

[chars]: Parse error

Explanation ’Parse 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-LIBPARSER-3-ERR_SYSDB_API

[chars]: [chars]: [chars]

Explanation ’Unable to perform a sysdb api call. The module which is calling this api, the description of the api and the error is displyed in the error message.’

Recommended Action collect show parser trace, show logging, any abnormal console message, and configuration of the router. Then send this output to tech support.

Error Message %MGBL-LIBPARSER-3-ERR_SYSDB_BIND

sysdb_bind: [chars], [chars]

Explanation ’Unable to bind to sysdb. The error is displyed in the error message.’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-ERR_SYSDB_CONDITIONAL_DELETE

sysdb_item_conditional_delete of ’[chars]’: [chars]

Explanation ’sysdb conditional delete operation failed. The error is displyed in the error message.’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-ERR_SYSDB_DATALIST

Failed to get datalist for ’[chars]’: [chars]

Explanation ’The sysdb operation failed. Error text is displayed in the message’

Recommended Action Unexpected failure happened while reading data from sysdb datastore. This could affect parser from parsing some commands. Please collect the console log, show logging output, any other messages related to system database, and unexpected syntax error failure in some commands if any noticed. Please contact technical support representative with this information.

Error Message %MGBL-LIBPARSER-3-ERR_SYSDB_DATALIST_NEXT

Failed to get item in data list for ’[chars]’: [chars]

Explanation ’The sysdb operation failed. Error text is displayed in the message’

Recommended Action Unexpected failure happened while reading data from sysdb datastore. This could affect parser from parsing some commands. Please collect the console log, show logging output, any other messages related to system database, and unexpected syntax error failure in some commands if any noticed. And call your technical support representative for assistance.

Error Message %MGBL-LIBPARSER-3-ERR_SYSDB_DELETE

sysdb_item_delete of ’[chars]’: [chars]

Explanation ’sysdb item delete operation failed. The error is displyed in the error message.’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-ERR_SYSDB_SET

sysdb_item_set of [chars] failed: [chars]

Explanation ’sysdb item set failed. The error is displyed in the error message.’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-ERR_THREAD_COND_WAIT

[chars]: [chars]

Explanation ’The call to pthread_cond_wait() was unsuccessful’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-ERR_THREAD_MUTEX_LOCK

[chars]: [chars]

Explanation ’The call to pthread_mutex_lock() was unsuccessful’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-ERR_THREAD_MUTEX_UNLOCK

[chars]: [chars]

Explanation ’The call to pthread_mutex_unlock() was unsuccessful’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-FAILEDREGCOMP

Regex operation ([chars]) failed for pattern:[chars]. Error([chars])

Explanation The regex operation failed for some reason. This may lead to parser errors. The possible causes are a regex compilation failure or a memory allocation failure. If the failure shows up during memory allocation, please check memory status for router.

Recommended Action Collect ’show parser trace parsing’ output, and open a DDTS report.

Error Message %MGBL-LIBPARSER-3-FILE_IO

Error on file IO ’[chars]’: ’[chars]’

Explanation Unable to read/write the 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-LIBPARSER-3-FILE_SIZE

Error in file ’[chars]’ of size : ’%zu’

Explanation Unable to add command defined under the 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-LIBPARSER-3-INITIFMGR

[chars], error: [chars]

Explanation ’Initialization of interface manager connection failed. The failure cause is mentioned in the error message displayed.’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-IP_ADDR2_HEX_STRING_FAILED

[chars]: Conversion of ip_addr_t to string failed

Explanation ’Conversion of ip_addr_t to string 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-LIBPARSER-3-IPV46_COMPRESSION_ERROR

[chars]: Error in compression ipv6 address ’[chars]’ with ipv4 address ’[chars]’ as it’s subset.

Explanation ’After compression, ipv4 address in ipv6 address should have been converted into’ ’ two 16 hexs, but this did not 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 %MGBL-LIBPARSER-3-LTRACE_INIT

Failed to initialize tracing functionality, error: ([unsigned int]) [chars].

Explanation Initialisation of trace functionality for parser failed. This would affect the debugging of parser.

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-LIBPARSER-3-LWM_API_ERR

[chars], ’[chars]’: Error - ’[chars]’

Explanation Failure in LWM client 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 %MGBL-LIBPARSER-3-TESTPOINT_LIMIT

[chars]:Reached testpoint callback limit for callback([pointer])

Explanation Failure in adding a new testpoint 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 %MGBL-LIBPARSER-3-TOOMANYALIASES

Only support 1000 aliases

Explanation ’The system has 1000 aliases limitation’

Recommended Action ’please remove some unused aliases before defining more aliases’ *NONE*

Error Message %MGBL-LIBPARSER-3-TTY_NMSPC_PATH

[chars]: [chars]

Explanation ’Unable to get the sysDB path of an item from TTY nmspc library’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-3-TUPLE_UNPACK

can not unpack data for item/entity([chars]): [chars]

Explanation ’This error will happen if parser can not unpack interface encap ’ ’info from sysdb. This information is published in sysdb by ifmgr ’ ’As a result parser may not be able to parse subinterfaces for ’ ’interface mentioned in the error message. Usually this error could ’ ’happen in the low memory condition. If this happens analyse the low ’ ’memory situation and once solved, restart parser_server’.

Recommended Action This error can only happen in the low memory condition. Collect the error message, show logging output, show interface brief output and show it to tech support.

Error Message %MGBL-LIBPARSER-3-WDSYSMON_REGISTER_ERROR

Error in registering with wdsysmon:’[chars]’

Explanation ’Error in registering with wdsysmon’

Recommended Action Copy the error message exactly as it appears 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-LIBPARSER-7-ERR_DEBUG

debug_event failed: [chars]

Explanation ’Debug event logic failed. The reporting function is listed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-7-ERR_SYSDB_REG_NOTIFY

sysdb_notification_register_evm of ’[chars]’: [chars]

Explanation ’The sysdb operation failed. Error test is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-7-ERR_SYSDB_UNREG_NOTIFY

sysdb_notification_unregister of ’[chars]’: [chars]

Explanation ’The sysdb operation failed. Error test is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-LIBPARSER-7-FDOPEN

[chars]: fdopen failed: [chars]

Explanation ’The call to function fdopen failed. The error message is displayed in the message’

Recommended Action *SH_TECH*

LIBSHELL Messages

Error Message %MGBL-LIBSHELL-3-PTHREAD_MUTEX_LOCK

Failed lock operation ’[chars]’ during ’[chars]’. Error:[chars]

Explanation A lock operation for synchronising shared resource, 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-LIBSHELL-3-WS_INIT

[chars]: [chars]

Explanation Initialization of functionality in getline library failed for reason mentioned in the error message. The whitespace completion behaviour could not be modified.

Recommended Action Exit the shell and get into the shell again. This would re-initialize the libshell library and error messages should no more appear. If the error message, persist; then undo the cli whitespace completion configuration from the line and call you’re technical support representatives for assistance.

MDACON Messages

Error Message %MGBL-MDACON-4-ABORTBULK

[MDACon] While aborting a bulk operation the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-ABORTTRANS

[MDACon] While aborting a transaction the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-ARRAYTOOBIG

[MDACon] Unable to handle the large number of elements in data array

Explanation The number of elements entered by user in an array are more than this application is designed to handle.

Recommended Action * RECUR *

Error Message %MGBL-MDACON-4-BADCLASS

[MDACON] Invalid class name - [chars]

Explanation An invalid class name was entered either by itself or as part of a hierarchy string.

Recommended Action Use the classinfo command to get more information about available class names. If the message recurs, copy the error message exactly as it appears 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-MDACON-4-BADFILTER

[MDACON] Invalid filter name - [chars]

Explanation An invalid filter name was entered for the related class.

Recommended Action Use the classinfo command to get more information about available filters for a given class. If the message recurs, copy the error message exactly as it appears 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-MDACON-4-BADFORMAT

[MDACon] Badly formatted [chars]

Explanation The command entered is badly formatted.

Recommended Action Re-enter the command. (Use the help command to find valid entry formats.) If the message recurs, copy the error message exactly as it appears 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-MDACON-4-BADHRCHY

[MDACON] Invalid hierarchy - [chars]

Explanation An invalid hierarchy was entered by the user.

Recommended Action Use the ’children’ command to progressively find out the correct hierarchy string. If the message recurs, copy the error message exactly as it appears 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-MDACON-4-BADOPTION

[MDACon] Invalid option - [chars]

Explanation The command option is invalid

Recommended Action Re-enter the command. (Use the help command to find valid options.) If the message recurs, copy the error message exactly as it appears 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-MDACON-4-BIND

[MDACon] Could not bind to the MDA: [chars]. MDACon cannot carry out any operations. XML agent (either corba or tty) needs to be configured to execute MDACon - try quitting and restarting it after configuring ’xml agent (corba|tty)’

Explanation MDACon was unable to bind to MDA. It is possible that there is a problem with MDA or the Schema Server, or the communication 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 %MGBL-MDACON-4-COMMITTRANS

[MDACon] While committing a transaction the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-COPY

[MDACon] While copying object [chars] to [chars] the following error occurred:
[chars]

Explanation An error occurred invoking an MDA function. This could be because the object to copy does not exist. The details are in the error string.

Recommended Action Check that the object 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 %MGBL-MDACON-4-CREATE

[MDACon] While creating object [chars] the following error occurred:
[chars]

Explanation An error occurred invoking an MDA function. This could be because the object to create already exists. The details are in the error string.

Recommended Action Check that the object 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 %MGBL-MDACON-4-DATAARRAYLENGTH

[MDACON] Too little or too much [chars] provided for class [chars]

Explanation The number of elements entered for a data array does not match the expected value.

Recommended Action Use the classinfo command to get more information about the naming or value information of a class. If the message recurs, copy the error message exactly as it appears 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-MDACON-4-DATAARRAYTYPE

[MDACON] Invalid [chars] entered for class [chars]

Explanation The datatypes entered in a data array do not match the the expected datatypes.

Recommended Action Use the classinfo command to get more information about the naming or value information of a class. If the message recurs, copy the error message exactly as it appears 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-MDACON-4-DELETE

[MDACon] While deleting object [chars] the following error occurred:
[chars]

Explanation An error occurred invoking an MDA function. This could be because the object does not exist. The details are in the error string.

Recommended Action Check that the object 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 %MGBL-MDACON-4-ENDBULK

[MDACon] While ending a bulk operation the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-ERR_MEM_ALLOC

[MDACon] Not enough memory

Explanation MDACon was unable to allocate enough memory required to process the command

Recommended Action Memory on the box must be running low - are there services that can be stopped, or can more memory be added.

Error Message %MGBL-MDACON-4-ERRORLIST

[MDACon] While listing the errors which occurred in the previous operation the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-EVENTLIST

[MDACon] While listing the operations which have been made within the current bulk operation, the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-EXCESS

[MDACon] 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 %MGBL-MDACON-4-FILEOPEN

[MDACon] The specified file ([chars]) could not be opened for [chars]

Explanation The file specified for reading instructions from, or writing output to, when MDACon was started, cannot be found. The most probable reason is that an incorrect incorrect name or path was supplied.

Recommended Action Check that the file name sor path upplied 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 %MGBL-MDACON-4-FILEREAD

[MDACon] 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 %MGBL-MDACON-4-FINDDATA

[MDACON] While executing the find data or finddata_next request, the following error occured:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-GET

[MDACon] While fetching object [chars] the following error occurred:
[chars]

Explanation An error occurred invoking an MDA function. This could be because the object to fetch does not exist. The details are in the error string.

Recommended Action Check that the requested object 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 %MGBL-MDACON-4-LIST

[MDACon] While executing the list request the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-MISMATCH

[MDACon] Mismatched quotes or brackets in command

Explanation An unmatched ’’’ or ’{’ 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 %MGBL-MDACON-4-MISSDESTNAME

[MDACon] Missing destination object name or path.

Explanation The command entered requires a destination object name or path 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 %MGBL-MDACON-4-MISSFILTER

[MDACon] Missing filter name

Explanation The command entered requires a filter 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 %MGBL-MDACON-4-MISSNUMBER

[MDACon] Missing number

Explanation The command entered requires a number 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 %MGBL-MDACON-4-MISSSTARTOBJECT

[MDACon] Missing start object naming information

Explanation The command entered requires naming information of start 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 %MGBL-MDACON-4-MISSVALUE

[MDACon] Missing object value

Explanation The command entered requires an object 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 %MGBL-MDACON-4-NOTLEAF

[MDACON] Class [chars] is not a leaf

Explanation The entered class name is not a leaf class, as is expected by the command.

Recommended Action Use the classinfo command to get more information about available class names. If the message recurs, copy the error message exactly as it appears 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-MDACON-4-READERINIT

[MDACon] 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 %MGBL-MDACON-4-SET

[MDACon] While setting object [chars] the following error occurred:
[chars]

Explanation An error occurred invoking an MDA function. This could be because the object does not exist or has the wrong type. The details are in the error string.

Recommended Action Check that the object 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 %MGBL-MDACON-4-STARTBULK

[MDACon] While starting a bulk operation the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-STARTTRANS

[MDACon] While starting a transaction the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-SYSDBMATCH

[MDACon] While determining the MDA object instance which corresponds to the SysDB path, the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-TASKNAMES

[MDACon] While requesting the AAA task names of a hierarchy point, the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-MDACON-4-TEST

[MDACon] Verification failed on object [chars] for the following reason
[chars]

Explanation An error occurred invoking an MDA function. This could be because the object 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 object 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 %MGBL-MDACON-4-UNKCMD

[MDACon] No such command - [chars] Type help or ? for a list of available commands

Explanation The first token in a command string was not a recognised MDACon 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 %MGBL-MDACON-7-INTERNAL

[MDACon] [chars]%s:
[chars]

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.

NETFLOW Messages

Error Message %MGBL-NETFLOW-3-ERR_CFG_APPLY

Could not apply verified config: [chars]

Explanation This is an error message in the Netflow manager to indicate that due to specified reasons, it was unable to apply the configuration that it had previously verified and accepted. This errmsg usually means that the netflow running config and netflow operational state are out of sync.

Recommended Action This error message indicates that a configuration problem occurred. Try reapplying the configuration. If that fails, the try restarting the process that issued the error message with the command process restart name location node.

Error Message %MGBL-NETFLOW-4-WARNING_CFG_APPLY

Could not apply configuration: [chars]

Explanation This message indicates that a configuration that was previously verified cannot be applied due to the reason specified. This may happen if a configuration that was applied to a Bundle interface cannot be applied due to either resources not being available in the Line Card where the member resides, or some configuration mismatch was detected.

Recommended Action Check the reason for the application failure and correct it as appropriate.

Error Message %MGBL-NETFLOW-6-INFO_CACHE_SIZE_EXCEEDED

Cache size of [dec] for monitor [chars] has been exceeded

Explanation This is an informational message to indicate that the specified flow monitor map cache size has been exceeded.

Recommended Action If this message is being issued too often, you might consider increasing the cache size. But keep in mind that the maximum cache size is 1,000,000 entries and it may put a strain on memory consumption in the LC.

Error Message %MGBL-NETFLOW-7-ERR

Nonfatal error: [chars]

Explanation This is an error message in the Netflow manager to indicate anomolies which are not FATAL. Some of the messages may indicate a failure to allocate a resource needed by the application. In many cases these messages must not keep appearing after the temperory situation is resolved.

Recommended Action These error message is does not impact the functionality of NetFlow. Therefore no action is needed.

Error Message %MGBL-NETFLOW-7-INFO_ROUTE_FLAP

Exporter [chars] destination [chars] is [chars]. Ifhandle: [hex], NextHop: [chars]

Explanation This is simply a debug message that indicates that the route to the collector has flapped. It shows the exporter name the collector IP address, the route reachability, as well as the interface handle and the IP next hop.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

NVGEN Messages

Error Message %MGBL-NVGEN-3-ARG

[chars]: Invalid argument

Explanation ’Invalid argument has been passed to the function’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-BASENAME

[chars]: basename of: [chars]

Explanation ’The call to basename failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-BGCOPTIONMISSING1

[chars]: bgcoption missing ’,’ after id: ’[chars]’

Explanation ’The input is invalid. The calling function and the command are displayed’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-BLANKENTERTUPLE

[chars]: blank enter tuple template ptr:0x[pointer] ref 0x[pointer] : [chars]

Explanation ’The enter tuple is blank. The calling function and enter tuple are displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-BUFFER

[chars]: new_cmd buffer null

Explanation ’The command buffer is invalid. The calling function is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-CFS_INIT_ERR

[chars] [chars]

Explanation ’Nvgen server could not initialize the CFS’

Recommended Action Collect the show logging output, console logs and error trace. Collect the show nvgen trace output. And contact tac representative with this information.

Error Message %MGBL-NVGEN-3-COPTIONNOTPRESENT

[chars]: Coption Not Present:’[chars]’

Explanation ’Coption is missing in the command. The calling function and the command are displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-DECODE_TUPLE

Failed to generate ’[dec]’ configuration lines for the requested operation.

Explanation Nvgen server failed to convert sysdb tuple into readable config command. This may result in failure to show some of the configuration or in in writing configurations to internal config backup.

Recommended Action Collect the following details show version, show logging, ’show nvgen trace ascii | include DECODE TUPLE’ output, show nvgen trace output, show runnning output, show config history and show tech-support parser. Contact TAC representative with this information.

Error Message %MGBL-NVGEN-3-DECODESTR

[chars]: sysdb_string_decode of ’[chars]’: [chars]

Explanation ’The sysdb decode operation failed. The error message is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-DIR_IO

[chars]: Error on directory ’[chars]’ during ’[chars]’: ’[chars]’

Explanation Unable to open/create the directory

Recommended Action Copy the error message exactly as it appears 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-NVGEN-3-ENDCOPTIONINCOMPLETE

[chars]: Incomplete endcoption mark for [hex]: ’[chars]’, new cmd: ’[chars]’

Explanation ’end option mark is incomplete in the command. The calling function the coption id and the commands are are displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ENDCOPTIONMISSINGCOMMA

[chars]: Missing comma in endcoption mark for [hex]: ’[chars]’

Explanation ’end option mark is missing a comma in the command. The calling function the coption id and the command are are displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ENDCOPTIONNOTPRESENT

[chars]: No endcoption mark for [hex]: ’[chars]’

Explanation ’end option mark is missing in the command. The calling function the coption id and the command are are displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-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-NVGEN-3-ERR_DLL_UNKNOWN

Unknown DLL [chars] in tree ’[chars]’

Explanation ’The nvgen try to load an unknow dll in the specified tree’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ERR_DLL_UNKNOWN_FUNC

Failed to locate function: [chars] in DLL ’[chars]’

Explanation ’An error occurred when trying to locate the dll function in DLL.’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ERR_MEM_ALLOC

[chars]: memory allocation routine failed

Explanation ’The system has run out of memory’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ERR_SYSDB_API

[chars]: [chars]: [chars]

Explanation ’Unable to perform a sysdb api call. The module which is calling this api, the description of the api and the error is displyed in the error message.’

Recommended Action collect show nvgen trace, show logging, any abnormal console message, and configuration of the router. Then send this output to tech support

Error Message %MGBL-NVGEN-3-ERR_SYSDB_BIND

sysdb_bind: [chars] [chars]

Explanation ’Unable to bind to sysdb. The error is displyed in the error message.’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ERR_SYSDB_GET

[chars] while accessing [chars]

Explanation ’An error occurred while accessing sysdb. The error is displayed in the error message.’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ERR_SYSDB_LIST

sysdb_list of ’[chars]’: [chars]

Explanation ’The sysdb operation failed. Error text is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ERR_SYSDB_SET

Unable to set item in sysdb:[chars]: [chars]

Explanation Nvgen server failed to set an item in sysdb database. The item name is part of the error. This may result in failure to generate running config properly in show run command. Or an impact may be seen during the internal config backup.

Recommended Action Collect the show logging output, show nvgen trace output, show runnning output, show config history and show tech-support sysdb. Contact TAC representative with this information.

Error Message %MGBL-NVGEN-3-ERR_THREAD_COND_WAIT

[chars]: pthread_cond_wait of: [chars]

Explanation ’The call to wait on a condition failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ERR_THREAD_CREATE

[chars]: pthread_create of : [chars]

Explanation ’The call to pthread_create failed. The error text is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ERR_THREAD_JOIN

[chars]: pthread_join of: [chars]

Explanation ’The call to pthread_join failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ERR_THREAD_MUTEX_LOCK

[chars]: pthread_mutex_lock of: [chars]

Explanation ’The call to lock a mutex failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ERR_THREAD_MUTEX_UNLOCK

[chars]: pthread_mutex_unlock of: [chars]

Explanation ’The call to unlock a mutex failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-EVENT_ATTACH

[chars]: Failed to attach event handler: [chars]

Explanation ’The call to attach nvgen requst handler to event manager failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-EVENTBLOCK

[chars]: event_block failed : [chars]

Explanation ’The call to event block in parser server failed. Parser may exit in this case. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-EVENTMGRCREATE

[chars]: event_manager_create failed : [chars]

Explanation ’The call to create parser event manager failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-FAILEDREGCOMP

[chars]. Pattern: [chars]

Explanation ’The regcomp function failed for some reason. This may lead to NVGEN errors.

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-FILE_COMPRESS

[chars]: Error on compressing file in ’[chars]’: ’[chars]’

Explanation Unable to compress the 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-NVGEN-3-FILE_IO

[chars]: Error on file IO ’[chars]’ for ’[chars]’: ’[chars]’

Explanation Unable to read/write the 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-NVGEN-3-FILE_NOT_OPEN

[chars]: Unable to open file ’[chars]’ for ’[chars]’: ’[chars]’

Explanation Unable to open the specified file. The error is mentioned as part of the message. This could impact the show run functionality or cause the config loss at upgrade or reload. If this error has happened at the time of doing copying configuration to a file, then copy will not be successful. If this happens during internal system configuration backup then certain configuration will not be updated in the backup. This could result in the config loss at next reboot. If this happens during nvgen server process restart or during initialization after a pie/package upgrade then either command files or config order or partition files are not opened. In which case certain config lines will be missing in the show run.

Recommended Action proc restart nvgen_server. If situation persists the 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 %MGBL-NVGEN-3-GENERAL_ERR

[chars]: [chars]

Explanation ’Nvgen server encountered an error, see message for more details’

Recommended Action Collect the show logging output, console logs and error trace. Collect the show nvgen trace output. And contact tac representative with this information.

Error Message %MGBL-NVGEN-3-ILLEGAL_TEMPLATE_TUPLE

Incorrect CLI template tuple:[chars]: [chars]

Explanation Nvgen server obtained an incorrect cli template config tuple from system database. This may result in failure to generate complete template configuration in show run command. Or in internal config backup.

Recommended Action Collect the show logging output, console logs, tracebacks, show nvgen trace output, show runnning output, show config history and show tech-support sysdb. Contact TAC representative with this information.

Error Message %MGBL-NVGEN-3-ILLEGALENTERSTR

[chars]: Illegal enter string ’[chars]’ on cmd ’[chars]’

Explanation ’The enter string is illegal. The calling function and enter string and command are displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-ILLEGALENTERTUPLE

[chars]: Illegal enter tuple ’[chars]’ for cmd ’[chars]’

Explanation ’The enter tuple is invalid. The calling function and enter string and command are displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-INSTALL_READY_FAILED

[chars]: Call to install_proc_ready failed with id: [dec] error: [chars]

Explanation ’nvgen_server got an error return from calling install_proc_ready’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-INTF_NAME_NULL

[chars]: interface name is NULL

Explanation ’Interface name send for parsing is NULL.’

Recommended Action Collect the nvgen debug output 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-NVGEN-3-INTF_NAME_PARSE_ERROR

[chars]: display of interfaces may not be in order. Name: [chars] Error: [chars]

Explanation ’interfaces during nvgen are ordered based on logical intf or slot/’ ’/port/sub-intf. This ordering failed due to the mentioned reason’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-INTFINFO

[chars]: Unable to get information about interface - [chars]

Explanation ’Interface Manager API im_is_hw_interface was not successful.’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-INVALID_IPV4_6_FLAG

[chars]:Invalid nvgen generic ipv4/6 flag. [dec].

Explanation ’generic ipv4/6 nvgen flags are incorrect. Probably error in ’ ’dumping the flags.’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-INVALID_IPV6_FLAG

[chars]:Invalid flag in ipv6address template. [dec].

Explanation ’ ipv6 nvgen flags are incorrect. Probably error in ’ ’dumping the flags.’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-INVALID_NOTIFICATION

[chars]: Unknown or unsupported ovl notification: [dec]

Explanation ’nvgen_server got an invalid notification form ovl process’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-INVALID_ORDER

Incorrect ordering info read from order table at:[chars]

Explanation Nvgen server obtained an incorrect order list entry from an internal order file. This may result in the show run output to have a different ordering than intended.

Recommended Action Collect the show version, show logging, show nvgen trace output, show runnning output, show config history and show tech-support sysdb. Contact TAC representative with this information.

Error Message %MGBL-NVGEN-3-INVALIDINPUT

[chars]: invalid input (no ’B’): ’[chars]’

Explanation ’The input is invalid. The calling function and the command are displayed’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-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-NVGEN-3-INVALIDNXCOPTION

[chars]: invalid NXCOPTION mark:’[chars]’

Explanation ’The input is invalid. The calling function and the command are displayed’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-INVALIDTEMPLATE

Invalid template file:’[chars]’

Explanation ’The template in this file is invalid or wrong version’

Recommended Action Copy the error message exactly as it appears 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-NVGEN-3-INVALIDVERSION

nvgen (version: [dec].[dec]) cannot handle version [dec].[dec] of nvgen template in component ’[chars]’

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-NVGEN-3-INVALTUPLEPATH

[chars]: [chars]: [chars]

Explanation ’The path of the tuple is invalid’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-LOCK_ERR

Failed lock operation ’[chars]’. Error:[chars]

Explanation A lock operation on shared resource, called by nvgen 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-NVGEN-3-MASKFORMAT_REGISTER

[chars]: Failed to register for ipaddress mask in prefix format. [chars]

Explanation ’The call to register the maskformat in prefix form failed. The error is displayed in the message’

Recommended Action Collect show nvgen trace, show logging and send this to tech support.

Error Message %MGBL-NVGEN-3-MASKFORMATINIT

[chars]: Failed to initialize ipaddress mask in prefix format.[chars]

Explanation ’The call to initialize the maskformat in prefix form failed. The error is displayed in the message’

Recommended Action Collect show nvgen trace, show logging and send this to tech support.

Error Message %MGBL-NVGEN-3-MINMSGLENGTH

The length: [unsigned int] of the message: ’[chars]’ is less than minimum message length

Explanation ’The message length must be greater than minimum message length. The minimum message length varies by request code.’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-MISSINGBRACKET

[chars] : [chars]: missing ’’ in sysdb string ’[chars]’ for command ’[chars]’

Explanation ’The ’’ is missing in sysdb string. The sysdb string and the command are displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-MISSINGEQUALSIGN

[chars]: [chars]: missing ’ equals ’ in sysdb string ’[chars]’ for command ’[chars]’

Explanation ’The equal is missing in sysdb string. The sysdb string and the command are displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-MSGREADV

[chars]: MsgReadv of: [chars]

Explanation ’The call to MsgReadv failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-NAMESPACE_ERR

Failed a namespace operation ([chars]). Partition([chars]), Error:[chars]

Explanation Nvgen server failed to build config namespaces from internal namespace module. This may result in failure to output the configuration in the intended order in show run command. Or in internal config backup.

Recommended Action Collect the show version, show logging, show nvgen trace output, show runnning output, show config history and show tech-support sysdb. Contact TAC representative with this information.

Error Message %MGBL-NVGEN-3-NESTEDCOPTION

[chars]: incorrect nested coption:’[chars]’

Explanation ’The input is invalid. The calling function and the command are displayed’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-NULLCHARMISSING

The message is not null terminated.

Explanation ’Parser messages must be null terminated.’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-OBJINREPLACE

[chars]: [chars]: Unknown object type [unsigned int] in replace_type

Explanation ’The object type in the replace_type is invalid. The objtype is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-OPEN

[chars]: open of [chars] failed : [chars]

Explanation ’The call to open() failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-PART_NAMES_GET_ERR

Could not get partitions names from cfgmgr: [chars]

Explanation ’Nvgen server could not get the changed partition names from cfgmgr’

Recommended Action Collect the show logging output, console logs and error trace. Collect the show nvgen trace output. And contact tac representative with this information.

Error Message %MGBL-NVGEN-3-PATTERN_NOT_FOUND

[chars]: Pattern:’[chars]’ not found in template ’[chars]’.

Explanation Taskid pattern not found where it was expected.

Recommended Action Copy the error message exactly as it appears 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-NVGEN-3-READERR

[chars]: read failed: [chars]

Explanation ’The call to function read failed. The error message is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-REGISTER_INSTMGR

[chars]: Failed to register with installmgr for software change notification : [chars]

Explanation ’The call to register for notification from install mgr failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-RESMGRATTACH

[chars]: event_resmgr_attach of : [chars]

Explanation ’The call to attach to parser resource manager failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-SHRINK_IPV4_6ADDRESS_FAILED

[chars]: Unable to shrink ipv4_6address: ’[chars]’

Explanation Shrinking of expanded ipv4_6address 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-NVGEN-3-SLOTORDER_REGISTER

[chars]: Failed to register for slot order display for interfaces. [chars]

Explanation ’The call to register the slot order display failed. The error is displayed in the message’

Recommended Action Collect show nvgen trace, show logging and send this to tech support.

Error Message %MGBL-NVGEN-3-SLOTORDERINIT

[chars]: slot order initialization failed : [chars]

Explanation ’The call to initialize slot order failed. The error is displayed in the message’

Recommended Action Collect show nvgen trace, show logging and send this to tech support.

Error Message %MGBL-NVGEN-3-STAT

[chars]: stat of [chars] failed: [chars]

Explanation ’The call to stat() failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-SUBMODESTRING

[chars]: get_submode_string: no end mark: [chars]

Explanation ’The end mark is missing in the submode string. The submode is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-SYSDBOPERATION

sysdb_operation of [chars] : ’[chars]’: [chars]

Explanation ’The sysdb find data operation failed. The error is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-TARGET_CFG_CREATE

[chars]:Failed to create target config:[chars].

Explanation Nvgen client failed to create target config buffer. Configuration can not proceed.

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-TARGET_CFG_DESTROY

[chars]:Failed to destroy target config:[chars]

Explanation Nvgen client failed to destroy target config buffer.

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-TARGET_CFG_LOCKERR

[chars]:Failed to obtain exclusive lock for this session:[chars]

Explanation Nvgen client failed to obtain exclusive lock for this session. Terminate the other open sessions and try again.

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-TARGET_CFG_UNLOCKERR

[chars]:Failed to release the lock held by session:[chars]

Explanation Nvgen client failed to release exclusive lock held by this session.

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-TASKID_COMPARE_ERROR

[chars]: aaa_compare_tasktable_alt failed! Error: ’[chars]’

Explanation ’nvgen_server got an error from calling aaa_compare_tasktable_alt.’

Recommended Action Copy the error message exactly as it appears 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-NVGEN-3-TASKID_EXCEEDED

[chars]: Number of taskid in.parser exceed maximum taskid limit for template :’[chars]’

Explanation Number of taskid found in.parser exceeded the maximum 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 %MGBL-NVGEN-3-TASKID_MISMATCH

[chars]:Taskid found but number of taskid is 0:’[chars]’

Explanation Total number of taskid for the template is 0, but taskid struct is not 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-NVGEN-3-TASKID_NOT_FOUND

[chars]: Taskid not found, where it is expected:’[chars]’

Explanation Taskid not found, but total number of taskid is greater than 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 %MGBL-NVGEN-3-TOKENNUMBER

[chars]: [chars]: Possible loop detected in command ’[chars]’

Explanation ’The token number is invalid. The command is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-TOKENTYPE

[chars]: token [dec], old type:[dec], new:[dec] cmd:’[chars]’

Explanation ’The token type is invalid. The calling function, token number and token type is displayed in the message’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-UNMATCHEDCOPTIONS

[chars]

Explanation ’Filter coption index is not zero. There could be unmatched coptions’

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-3-WRMEM_ABORT

Aborting update of startup configuration. [chars].

Explanation Failed to get the startup config file name or run out of space on disk or some other transient error.

Recommended Action *SH_TECH*

Error Message %MGBL-NVGEN-4-CONFIG_GEN_ERR

Generation of configuration in ASCII format failed due to internal error. The file ’[chars]’ was not updated

Explanation Generation of configuration in ASCII format has failed. During periodic backup operation this may lead to internal backup files not getting updated with recent config changes

Recommended Action For a system initiated ascii generation please run ’show running cache refresh’ in SDR mode. Look for similar IOS messages for additional recommended actions. Collect the show logging output, console logs, tracebacks, show nvgen trace output, show runnning output, show config history and show tech-support sysdb.

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-ERR_SYSDB_STRING_ENCODE

[chars]

Explanation ’Sysdb path has string that has special character without sysdb_encode flag’

Recommended Action Collect the following details: 1. Command issued 2. show parser trace. 3. console logs. 4. If config is restored from file, then filename/contents. 5.If command failed at startup, show config trace and show config failed startup.

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 0x%zx at offset 0x%zx 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 [unsigned int],[unsigned int] 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 ’%zd’ to ’%zd’ 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

Failed to resolve linkpoint ’[chars]’ specified in chainname ’[chars]’ in ’[chars]’ file.

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-DUMP_FAIL

[chars]: [chars]: [chars]

Explanation An error has occurred while dumping of the collected data from the pm collector process. This error could error due to various reasons below : a) Local disk is full or something wrong. 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-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-DUMP

[chars]: [chars]

Explanation An informational alarm upon dumping of the collected data

Recommended Action No action is required.

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.

PRP_UPGRADE Messages

Error Message %MGBL-PRP_UPGRADE-3-BOOTVAR_FILE_OPEN

Failed to open bootvar file, [chars] ([dec])

Explanation Failed to open bootvar file.

Recommended Action No action is required.

Error Message %MGBL-PRP_UPGRADE-3-MBI_BOOT_HOLD

sysmgr_mbi_boot_hold failed, [chars], ([dec])

Explanation The function sysmgr_mbi_boot_hold failed.

Recommended Action No action is required.

Error Message %MGBL-PRP_UPGRADE-3-MBI_BOOT_UNHOLD

sysmgr_mbi_boot_unhold failed, [chars] ([dec])

Explanation The function sysmgr_mbi_boot_unhold failed.

Recommended Action No action is required.

Error Message %MGBL-PRP_UPGRADE-3-SPAWN_CP

spawn a ’cp’ process failed, [chars] ([dec])

Explanation Failed to spawn the ’cp’ process

Recommended Action No action is required.

Error Message %MGBL-PRP_UPGRADE-3-SPAWN_RM

spawn a ’rm’ process failed, [chars] ([dec])

Explanation Failed to spawn the ’rm’ process

Recommended Action No action is required.

Error Message %MGBL-PRP_UPGRADE-3-WAITPID_CP

waitpid for the ’cp’ process failed, [chars] ([dec])

Explanation waitpid for the ’cp’ process failed

Recommended Action No action is required.

Error Message %MGBL-PRP_UPGRADE-3-WAITPID_RM

waitpid for the ’rm’ process failed, [chars] ([dec])

Explanation waitpid for the ’rm’ process failed

Recommended Action No action is required.

Error Message %MGBL-PRP_UPGRADE-4-PROC_AS_IO

Process address space file IO failure for [chars], [chars], ([dec])

Explanation IO failure on process address space.

Recommended Action No action is required.

Error Message %MGBL-PRP_UPGRADE-6-COMPLETE_SYNC

Successfully sync’ed configure files: [chars] ([dec])

Explanation Sync successfully completed.

Recommended Action No action is required.

Error Message %MGBL-PRP_UPGRADE-6-START_SYNC

Sync’ing configure files from ’[chars]’

Explanation Status information while starting config file sync.

Recommended Action No action is required.

RS232 Messages

Error Message %MGBL-RS232-1-CONSOLE_SESSION_ANYWAY

Trying to start unconfigured console session anyway.

Explanation The RS232 DLL tried to apply a template to the console and failed, but we are attempting to start a session anyway to try and ensure that it’s possible to log onto the router from the console. This may mean it’s impossible to gain terminal access any other way (ie via telnet, ssh, etc).

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the *param* 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 *param* output, call your Cisco technical support representative and provide the representative with the gathered information. show running-config

Error Message %MGBL-RS232-3-BAUD_RATE

The RS232 driver encountered an error retrieving the baud rate for the console; default to a value of [unsigned int]: [hex] ’[chars]’.

Explanation The console baud rate is retrieved from the configurate register. Problems were encounted during this operation.

Recommended Action Check the default value that the system has resorted to and configure the terminal server to this speed. This will allow the console to be used to gain further diagnostics. Copy the error message exactly as it appears 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-RS232-3-CABLE_MONITOR_DISABLED

Error in cable monitor thread. ’[chars]([dec])’. Please restart ’[chars]’ to enable this functionality.

Explanation Failure in cable monitoring function. Since this functionality is not so important in console driver, any error in this thread will be reported through syslog and thread will retire. Errors are failure in malloc or pthread operation and if such basic functions fail, then it might mean system is in bad shape. So we’re not sure restarting this process will recover the situation. To avoid worst case -lose console/aux accessibility-, this process will remain without cable disconnect function. Operator might want to restart this process if this functionality is required in which this router is physically located, such as datacenter or co-location house.

Recommended Action If you need cable monitor functionality, please restart the process to recover.

Error Message %MGBL-RS232-3-FRAMING_ERROR

The UART driver encountered an framing error for [chars] port

Explanation UART encountered Framing 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-RS232-3-KERNEL

The RS232 driver encountered an error making a kernel call

Explanation The RS232 driver has made a kernel call which is failing; it cannot proceed.

Recommended Action Copy the error message exactly as it appears 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-RS232-3-LINE_CONNECT_FAILURE

Failed to process Line connect request because of ’[chars]’ (category:[dec] port:[dec] rc:[dec]). Connect the cable tightly

Explanation Failed to process connect request.

Recommended Action Disconnect and re-connect the (aux/console) cable of the corresponding port mentioned in the syslog properly. Check whether corresponding (aux/console) port is accessible or not after that.

Error Message %MGBL-RS232-3-OVERRUN_ERROR

The UART driver encountered an over run error for [chars] port

Explanation UART encountered over run 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-RS232-3-PARITY_ERROR

The UART driver encountered an parity error for [chars] port

Explanation UART encountered parity 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-RS232-3-SESSION_DISCONNECT_FAILURE

Failed to close the existing session because of ’[chars]’ (category:[dec] port:[dec] rc:[dec]). If session should be closed, please issue ’clear line’ command

Explanation Failed to close session.

Recommended Action If you want to close existing session, please run ’clear line’ command.

Error Message %MGBL-RS232-3-SESSION_NOTIFICATION_ABORT

Couldn’t acquire mutex to notify [chars] (category:[dec] port:[dec] rc:[dec]). If session should be closed, please issue ’clear line’ command

Explanation Failed to notify line status change.

Recommended Action If you want to close existing session, please run ’clear line’ command.

Error Message %MGBL-RS232-3-TTY_NOT_REGISTERED

The TTY is not registered with the TTY Server

Explanation The RS232 DLL tried to perform an operation on a TTY that isn’t registered with the TTY Server.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-RS232-4-API_LOCATE_ERROR

Unable to find the desired details in a loaded DLL

Explanation The RS232 DLL was unable find the details required from a DLL it had loaded.

Recommended Action Copy the error message exactly as it appears 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-RS232-4-DLL_OPEN_ERROR

The RS232 DLL was unable to open a DLL (errno: [dec])

Explanation The RS232 DLL was unable to open a DLL.

Recommended Action Copy the error message exactly as it appears 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-RS232-4-MAPPING_ERROR

The RS232 DLL was unable map from a TTY ID to a UART port

Explanation The RS232 DLL was unable map from a TTY ID to a UART port

Recommended Action Copy the error message exactly as it appears 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-RS232-4-MEM_ALLOC_ERROR

Unable to allocate memory for TTY structures

Explanation The RS232 DLL was unable allocate the necessary memory it required to hold details about the TTYs.

Recommended Action Copy the error message exactly as it appears 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-RS232-4-NO_PACKET_MODE

Packet mode sessions are not yet supported on RS232 TTYs

Explanation The TTY Server informed the RS232 DLL about a packet mode session, but we don’t yet support packet mode.

Recommended Action Copy the error message exactly as it appears 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-RS232-4-PDP_SET_ERROR

The RS232 DLL was unable to set the persistant data path

Explanation The RS232 DLL has failed to enable the persistant data path for a TTY.

Recommended Action Copy the error message exactly as it appears 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-RS232-4-SESSION_SETUP_ERROR

The RS232 DLL was unable to setup a session on a TTY

Explanation The RS232 DLL has been unable to setup a session on a TTY

Recommended Action Try performing a ’clear line’ on the relevent TTY.

Error Message %MGBL-RS232-4-TEMPLATE_APPLY_ERROR

The RS232 DLL encountered an error trying to apply a template.

Explanation The RS232 DLL tried to apply a template to a TTY but 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-RS232-4-TEMPLATE_DEAPPLY_ERROR

The RS232 DLL encountered an error trying to deapply a template.

Explanation The RS232 DLL tried to deapply a template to a TTY but 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-RS232-6-DCD_DISCOVERED

Discovered data carrier detect signal (category:[dec] port:[dec])

Explanation The RS232 driver discovered Data Carrier Detect signal.

Recommended Action Copy the error message exactly as it appears 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-RS232-6-DCD_LOST

Lost data carrier detect signal (category:[dec] port:[dec]). Existing session will be closed.

Explanation The RS232 driver lost Data Carrier Detect signal. Process will close existing session.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

S2681 Messages

Error Message %MGBL-S2681-3-COND_SIGNAL_ERROR

Unable to signal on the status variable

Explanation The S2681 UART driver was unable to signal that that status variable was ready to 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 %MGBL-S2681-3-INTERRUPT_UNMASK_ERROR

Unable to unmask UART interrupt (error: [dec])

Explanation The S2681 UART driver has been unable to unmask the UART interrupt.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-S2681-3-IO_PERM_ERROR

Unable to obtain permission to access UART (error: [dec])

Explanation The S2681 UART driver has been unable to gain the required permissions to access the UART.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-S2681-3-MUTEX_LOCK_ERROR

Unable to lock the UART (error: [dec])

Explanation The S2681 UART driver has been unable to lock access to the UART.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-S2681-3-MUTEX_UNLOCK_ERROR

Unable to unlock the UART (error: [dec])

Explanation The S2681 UART driver has been unable to unlock access to the UART.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-S2681-3-SCHED_PRIORITY_ERROR

Unable to raise the priority of the interrupt handler

Explanation The S2681 UART driver was unable to raise the priority of the interrupt handler.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-S2681-3-SCHEDPARAM_ERROR

Unable to set the parameters for the interrupt handler

Explanation The S2681 UART driver was unable to set the parameters of the interrupt handler.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-S2681-3-SCHEDPOLICY_ERROR

Unable to set scheduling policy for the interrupt handler.

Explanation The S2681 UART driver was unable to set the scheduling policy for the interrupt handler.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-S2681-3-STATUS_MUTEX_LOCK_ERROR

Unable to lock the status variable.

Explanation The S2681 UART driver was unable to lock the status variable for the interrupt thread.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-S2681-3-STATUS_MUTEX_UNLOCK_ERROR

Unable to unlock the status variable.

Explanation The S2681 UART driver was unable to unlock the status variable for the interrupt thread.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-S2681-3-THREAD_CREATE_ERROR

Unable to create the interrupt handler thread.

Explanation The S2681 UART driver was unable to create a thread for the interrupt handler.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-S2681-6-STAT_CREATE_ERROR

Unable to create statistics file ([dec]).

Explanation The S2681 UART driver was unable to create a file to store statistics. Show statistics command would fail. We can still see the statistics content from core file.

Recommended Action No action is required.

SCHBRO Messages

Error Message %MGBL-SCHBRO-7-ARRAYTOOBIG

[xml-schema] Unable to handle the large number of elements in data array

Explanation The number of elements entered by user in an array are more than this application is designed to handle.

Recommended Action * RECUR *

Error Message %MGBL-SCHBRO-7-AUTHENTICATE

[xml-schema] [chars]%s:
[chars]

Explanation An error occurred invoking an AAA 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 %MGBL-SCHBRO-7-BADCLASS

[xml-schema] Invalid class name - [chars]

Explanation An invalid class name was entered either by itself or as part of a hierarchy string.

Recommended Action Use the classinfo command to get more information about available class names. If the message recurs, copy the error message exactly as it appears 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-SCHBRO-7-BADFORMAT

[xml-schema] Badly formatted [chars]

Explanation The command entered is badly formatted.

Recommended Action Re-enter the command. (Use the help command to find valid entry formats.) If the message recurs, copy the error message exactly as it appears 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-SCHBRO-7-BADHRCHY

[xml-schema] Invalid hierarchy - [chars]

Explanation An invalid hierarchy was entered by the user.

Recommended Action Use the ’children’ command to progressively find out the correct hierarchy string. If the message recurs, copy the error message exactly as it appears 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-SCHBRO-7-BADOPTION

[xml-schema] Invalid option - [chars]

Explanation The command option is invalid

Recommended Action Re-enter the command. (Use the help command to find valid options.) If the message recurs, copy the error message exactly as it appears 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-SCHBRO-7-BIND

[xml-schema] Could not bind to the MDA: [chars]. XML schema browser cannot carry out any operations. XML agent (either corba or tty) needs to be configured to execute XML schema browser - try quitting and restarting it after configuring ’xml agent (corba|tty)’

Explanation XML schema browser was unable to bind to MDA. It is possible that there is a problem with MDA or the Schema Server, or the communication 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 %MGBL-SCHBRO-7-DATAARRAYLENGTH

[xml-schema] Too little or too much [chars] provided for class [chars]

Explanation The number of elements entered for a data array does not match the expected value.

Recommended Action Use the classinfo command to get more information about the naming or value information of a class. If the message recurs, copy the error message exactly as it appears 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-SCHBRO-7-DATAARRAYTYPE

[xml-schema] Invalid [chars] entered for class [chars]

Explanation The datatypes entered in a data array do not match the the expected datatypes.

Recommended Action Use the classinfo command to get more information about the naming or value information of a class. If the message recurs, copy the error message exactly as it appears 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-SCHBRO-7-ERR_MEM_ALLOC

[xml-schema] Not enough memory

Explanation XML schema browser was unable to allocate enough memory required to process the command

Recommended Action Memory on the box must be running low - are there services that can be stopped, or can more memory be added.

Error Message %MGBL-SCHBRO-7-EXCESS

[xml-schema] 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 %MGBL-SCHBRO-7-FILEOPEN

[xml-schema] The specified file ([chars]) could not be opened for [chars]

Explanation The file specified for reading instructions from, or writing output to, when XML schema browser was started, cannot be found. The most probable reason is that an incorrect name or path was supplied.

Recommended Action Check that the file name sor path upplied 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 %MGBL-SCHBRO-7-FILEREAD

[xml-schema] 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 %MGBL-SCHBRO-7-FINDDATA

[xml-schema] While executing the walk data or walkdata_next request, the following error occured:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-SCHBRO-7-GET

[xml-schema] While fetching object [chars] the following error occurred:
[chars]

Explanation An error occurred invoking an MDA function. This could be because the object to fetch does not exist. The details are in the error string.

Recommended Action Check that the requested object 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 %MGBL-SCHBRO-7-INTERNAL

[xml-schema] [chars]%s:
[chars]

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 %MGBL-SCHBRO-7-LIST

[xml-schema] While executing the list request the following error occurred:
[chars]

Explanation An error occurred invoking an MDA 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 %MGBL-SCHBRO-7-MISMATCH

[xml-schema] Mismatched quotes or brackets in command

Explanation An unmatched ’’’ or ’{’ 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 %MGBL-SCHBRO-7-NOTLEAF

[xml-schema] Class [chars] is not a leaf

Explanation The entered class name is not a leaf class, as is expected by the command.

Recommended Action Use the classinfo command to get more information about available class names. If the message recurs, copy the error message exactly as it appears 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-SCHBRO-7-READERINIT

[xml-schema] 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 %MGBL-SCHBRO-7-UNKCMD

[xml-schema] No such command - [chars] Type help or ? for a list of available commands

Explanation The first token in a command string was not a recognised XML schema browser 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.

SCHEMA Messages

Error Message %MGBL-SCHEMA-6-VERSIONCHANGE

A schema version change has occurred due to the [chars] of schema file ’[chars]’. Any management applications which use the schema may wish to update to the appropriate schema version.

Explanation The version of some part(s) of the schema which are running on the router have changed - this is an informational message to let any users of the schema know of the change.

Recommended Action No action is required.

Error Message %MGBL-SCHEMA-7-INTERNAL

The schema infrastructure has encountered an error. [chars]

Explanation An internal error has occurred in the schema server or 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.

SCONBKUP Messages

Error Message %MGBL-SCONBKUP-3-INTERNAL_FATAL

[chars] [dec]: [chars]

Explanation Restarting the process as it is not in a recoverable 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 %MGBL-SCONBKUP-7-INTERNAL_ERR

[chars] [dec]: [chars]

Explanation Error encountered while Backing up the ASCII 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 %MGBL-SCONBKUP-7-RELOAD_REPLY_ERR

Reload([dec]) fail to reply to svr Sconbkup on [chars] [chars]. Error([dec]): [chars].

Explanation Error encountered while replying message during ASCII 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 %MGBL-SCONBKUP-7-REPLY_ERR

Sconbkup([dec]) fail to reply to Reload([dec]) on [chars] [chars]. Error([dec]): [chars].

Explanation Error encountered while replying message during ASCII 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.

ST16550 Messages

Error Message %MGBL-ST16550-3-INTERRUPT_UNMASK_ERROR

Unable to unmask UART interrupt (error: [dec])

Explanation The ST16550 UART driver has been unable to unmask the UART interrupt.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-ST16550-3-IO_PERM_ERROR

Unable to obtain permission to access UART (error: [dec])

Explanation The ST16550 UART driver has been unable to gain the required permissions to access the UART.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-ST16550-3-MUTEX_LOCK_ERROR

Unable to lock the UART (error: [dec])

Explanation The ST16550 UART driver has been unable to lock access to the UART.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-ST16550-3-MUTEX_UNLOCK_ERROR

Unable to unlock the UART (error: [dec])

Explanation The ST16550 UART driver has been unable to unlock access to the UART.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-ST16550-3-SCHED_PRIORITY_ERROR

Unable to raise the priority of the interrupt handler

Explanation The ST16550 UART driver was unable to raise the priority of the interrupt handler.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-ST16550-3-SCHEDPARAM_ERROR

Unable to set the parameters for the interrupt handler

Explanation The ST16550 UART driver was unable to set the parameters of the interrupt handler.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-ST16550-3-SCHEDPOLICY_ERROR

Unable to set scheduling policy for the interrupt handler.

Explanation The ST16550 UART driver was unable to set the scheduling policy for the interrupt handler.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-ST16550-3-SEM_ERROR

Unable to perform ’[chars]’ operation on semaphore ([chars]).

Explanation The ST16550 UART driver was unable to perform semaphore operation for interrupt handler.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-ST16550-3-STATUS_MUTEX_LOCK_ERROR

Unable to lock the status variable.

Explanation The ST16550 UART driver was unable to lock the status variable for the interrupt thread.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-ST16550-3-STATUS_MUTEX_UNLOCK_ERROR

Unable to unlock the status variable.

Explanation The ST16550 UART driver was unable to unlock the status variable for the interrupt thread.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-ST16550-3-THREAD_CREATE_ERROR

Unable to create the interrupt handler thread.

Explanation The ST16550 UART driver was unable to create a thread for the interrupt handler.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-ST16550-6-STAT_CREATE_ERROR

Unable to create statistics file ([dec]).

Explanation The ST16550 UART driver was unable to create a file to store statistics. Show statistics command would fail. We can still see the statistics content from core file.

Recommended Action No action is required.

STATSD Messages

Error Message %MGBL-STATSD-3-EVENT_BLOCK

An error occurred while handling an event: [chars]

Explanation The event handling function returned an error which could not be handled

Recommended Action Copy the error message exactly as it appears 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-STATSD-3-LTRACE_INIT

Failed to initialise tracing for Stats library: [chars]

Explanation The infrastructure for tracing returned an error.

Recommended Action Some Stats tracing will not be available for this process, which will make triage of any Stats problems more difficult. There is otherwise no detrimental effect to this process.

Error Message %MGBL-STATSD-3-REGISTRATION_FAILED

Registration of a stats collector failed - [chars]

Explanation Registration of a stats collector with stats server 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-STATSD-3-SHMEM_CORRUPTED

Stats shared memory window has become corrupted. [chars]

Explanation In certain unlikely scenarios it is possible that during a process restart the shared memory region used by the stats infrastructure can become corrupted. In most cases this will automatically be recovered from, however there is a possibility that the system will not be able to recover from this - The specific instance of the message will indicate which of these cases has arisen. If the system is unable to restart all necessary processes then multiple process crashes/blockages may be observed. In either case, reported statistics may be reset or inaccurate.

Recommended Action In the recovery case, processes should restart automatically and the system should recover so no user intervention should be required. If we are unable to automatically recover, then either the node should be reloaded, or support contacted.

Error Message %MGBL-STATSD-3-SHMEM_LOCK

Failed to lock shared memory mutex: [chars]

Explanation A failure occurred when attempting to acquire a shared memory lock

Recommended Action This message probably indicates an error elsewhere in the system as some other process must be holding the lock. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

SYS Messages

Error Message %MGBL-SYS-3-ALREADY_THREADED_MSG

[chars]: Attempt to re-add a node to a tree

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 %MGBL-SYS-3-COMPARE_ALREADY_SET

[chars]: Compare already set for thread : [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 %MGBL-SYS-3-FTRUNCATE

ftruncate of [chars] at failed because [chars]

Explanation The packet subsystem was not able to initialize memory.

Recommended Action The router will not start properly with this condition.
’ ’Call your technical support representative for assistance.

Error Message %MGBL-SYS-3-ILLEGAL_THREAD

[chars]: Illegal thread for this wavl : [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 %MGBL-SYS-3-MALLOCFAIL

Memory allocation of [dec] bytes failed from [hex], pool [chars], alignment [dec]

Explanation The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router’s memory.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %MGBL-SYS-3-MMAPFAIL

mmap of [chars] at failed; errno ([dec]) [chars]

Explanation The packet subsystem was not able to initialize memory.

Recommended Action The router will not start properly with this condition.
’ ’Call your technical support representative for assistance.

Error Message %MGBL-SYS-3-MMAPSHIFT

mmap of [chars] at failed, returned address [pointer] is, expected [pointer]

Explanation The packet subsystem was not able to initialize memory.

Recommended Action The router will not start properly with this condition.
’ ’Call your technical support representative for assistance.

Error Message %MGBL-SYS-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 %MGBL-SYS-3-NODE_DEL_FAILED

[chars]: failure to delete a node

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 %MGBL-SYS-3-NOMEMORY

No memory available for [chars] [dec]

Explanation An operation could not be accomplished because of a low-memory condition.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %MGBL-SYS-3-NOT_THREADED_MSG

[chars]: Attempt to remove an unthreaded node from a tree

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 %MGBL-SYS-3-NULL_HANDLE_MSG

[chars]: Received a NULL handle

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 %MGBL-SYS-3-NULLREG

NULL registry

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 %MGBL-SYS-3-REG_UNKNOWN_TYPE

Unknown registry 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 %MGBL-SYS-3-RN_ASC_DESC

Tried to ascend in descend loop

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 %MGBL-SYS-3-RN_DELINK_INODE

Attempt to delink inode with 2 decendents [pointer] ([dec], [hex], [pointer], [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 %MGBL-SYS-3-RN_NDESC

Node [pointer] ([dec]) has no descendents ([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 %MGBL-SYS-3-RN_PRNT_LINK

Parent not linked to inode ([pointer], [pointer], [pointer], [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 %MGBL-SYS-3-RN_VPARENT

Unable to find virtual node parent for [pointer] ([dec], [hex], [pointer], [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 %MGBL-SYS-3-ROOT_ALREADY_SET

[chars]: Root already set for thread : [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 %MGBL-SYS-3-SHMEM_MIXUP

[chars]: Attempt to use non-SHMEM API on SHMEM wavl tree

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 %MGBL-SYS-3-SHMOPENFAIL

shm_open of [chars] at failed because [chars]

Explanation The packet subsystem was not able to initialize memory.

Recommended Action The router will not start properly with this condition.
’ ’Call your technical support representative for assistance.

Error Message %MGBL-SYS-3-THREAD_NOT_EXIST

[chars]: Thread [dec] 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 %MGBL-SYS-3-UNINIT_MSG

[chars]: Attempt to reference an uninitialized wavl tree

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 %MGBL-SYS-5-CONFIG_I

Configured from [chars] by [chars]

Explanation The routers’s configuration was changed.

Recommended Action ’No action is required.’

Error Message %MGBL-SYS-5-TABLEERR

[chars] table [chars] damaged: [chars]

Explanation An internal table entry became corrupted.

Recommended Action Copy the message exactly as it appears, and report it your technical support representative.

TTY_CONNECT Messages

Error Message %MGBL-TTY_CONNECT-2-UNLOCKING

Error releasing an internal lock ([dec]) - process aborting

Explanation The TTY Connection library encountered an unexpected error releasing a lock. To avoid the potential for deadlock the process is aborting.

Recommended Action Copy the error message exactly as it appears 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-TTY_CONNECT-3-INTERNAL

An unexpected internal error occurred ([hex], ’[chars]’)

Explanation The TTY Connection library encountered an unexpected error during normal operation.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message %MGBL-TTY_CONNECT-3-LOCKING

Error acquiring an internal lock ([dec])

Explanation The TTY Connection library encountered an unexpected error occurred acquiring 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 %MGBL-TTY_CONNECT-3-MEMORY

Failed to allocate %zd bytes of memory

Explanation The TTY Connection library has failed to acquire the required amount of memory

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %MGBL-TTY_CONNECT-7-LWM

An error ([dec]) occurred performing the following messaging operation: [chars]

Explanation The TTY Connection library encountered an unexpected error whilst communicating with the TTY Server.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

TTY_DB Messages

Error Message %MGBL-TTY_DB-2-PANIC

The TTY DB library has encountered a critical error and must restart the process.

Explanation A critical internal error has ocurred which requires the process to restart. For example if a lock cannot be released then the process is restarted to avoid deadlock.

Recommended Action Please get the information specified under the component required_info and call your Cisco technical support representative and provide the gathered information with this error message text. Copy the error message exactly as it appears 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-TTY_DB-3-KERNEL_ERROR

Kernel operation failed unexpectedly: [chars] ([dec])

Explanation A system library call failed unexpectedly. This failure can occur due to any of the following failures. 1. Failure while obtaining DB read lock 2. Failure while obtaining DB write lock 3. Failure while releasing DB read/write lock 4. Failure while obtaining TTY lock 5. Failure while releasing TTY lock

Recommended Action Please get the information specified under the component required_info and call your Cisco technical support representative and provide the gathered information with this error message text. Copy the error message exactly as it appears 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-TTY_DB-3-LOCK_BUSY

Lock busy, Lock operation failed: Requester ([hex]) Owner ([hex]) Lock address ([pointer])

Explanation A system call for locking read-write lock failed because lock is busy.

Recommended Action Copy the error message exactly as it appears 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-TTY_DB-3-LOCK_ERROR

Lock operation failed: Requester ([hex]) Owner ([hex]) Lock address ([pointer]) Error ([dec]) Reason : [chars]

Explanation A system call for locking read-write lock 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.

TTY Messages

Error Message %MGBL-TTY-0-ISSU_STDBY_CON_AVAILABLE

STANDBY Console is now available ([chars]) [hex], ’[chars]’

Explanation ’Standby Console available during ISSU Load Exec and Load Done Phase’

Recommended Action Copy the error message exactly as it appears 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-TTY-2-FATAL

Fatal condition detected. TTY Server is restarting

Explanation The TTY Server has encountered a fatal error and must restart in order to continue operation.

Recommended Action Check to ensure that the TTY Server has restarted. Copy the error message exactly as it appears 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-TTY-2-PHASE2_FATAL

Failed to complete phase 2 initialization: [hex], ’[chars]’

Explanation The TTY Server has failed to complete phase 2 initialization. For this instance of the server the failure is fatal; without the services that were being initialized the code will not be able 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 %MGBL-TTY-3-ACCESS_CHECK

Access checks for requested connections cannot proceed. TTY-Server restart required

Explanation The TTY Server previously encountered an unexpected error while applying access configuration changes to a TTY. As a result it cannot allow future connection requests to be authorized.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-TTY-3-ACL

Unexpected ACL error encountered: [hex], ’[chars]’

Explanation The TTY Server has encountered an error using the IPV4 ACL Library.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message %MGBL-TTY-3-CLOSE_DEVICE

Failed to close file descriptor [dec]: ’[chars]’

Explanation Failed to close a file descriptor inheritited from the spawning process so that the appropriate device files can be reopened for exec to read/write.

Recommended Action Copy the error message exactly as it appears 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-TTY-3-ENV_VARS

Failed to set the process’ environment: [hex], ’[chars]’

Explanation Some instances of exec require the environment to be set up before exec initializes. The process which execs ’exec’ has failed to do this.

Recommended Action Copy the error message exactly as it appears 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-TTY-3-EXEC

exec of ’[chars]’ failed: [unsigned int], ’[chars]’

Explanation The Exec launcher failed to exec ’exec’. This could be due to an error picking up the load path from install 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 %MGBL-TTY-3-GET_CLINFO_FAILED

Failed to obtain the clinfo of the given server handle: [hex], [hex], ’[chars]’

Explanation Matching clinfo could not be obtained for the given server handle.

Recommended Action Debug message only. No action is required.

Error Message %MGBL-TTY-3-INTERNAL

Unexpected internal error encountered: [hex], ’[chars]’

Explanation The TTY Server has either failed on a function which it expected to succeed, or has got itself 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 %MGBL-TTY-3-INVALID_PULSE

TTY Invalid pulse recvd! sender:[chars] ([dec]) recvr:[chars] ([dec]) EvPcode: [dec] DevCtlPcode: [dec] EvPload: [dec] Node [hex] SerHdl: [hex] [hex], ’[chars]’

Explanation This is due to either of the following reasons. First, TTY Server receives an invalid pulse code. Or the send process is not tty server. This message added to capture maximum debug information to dig this issue further.

Recommended Action Debug message only. No action is required.

Error Message %MGBL-TTY-3-INVALID_SRVR_HANDLE

TTY device control pulse received with invalid server handle: [hex], ’[chars]’

Explanation This may be due to corruption in Event structure.

Recommended Action Debug message only. No action is required.

Error Message %MGBL-TTY-3-ISSU_NFN_REG_FAIL

Failed to register for ISSU on STANDBY ([chars]), [hex], ’[chars]’

Explanation Failed to register for ISSU Install notification registration.

Recommended Action Copy the error message exactly as it appears 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-TTY-3-KERNEL

Unexpected internal error encountered ’[chars]’

Explanation The TTY Server has encountered an unexpected error while using the system 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 %MGBL-TTY-3-MEMORY

Failed to allocate %zd bytes of memory

Explanation The server has failed to acquire the required amount of memory

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %MGBL-TTY-3-MGMT_HOST_IP_ERROR

Error getting host’s IP address.

Explanation The show line command was unable to get the host IP address.

Recommended Action Copy the error message exactly as it appears 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-TTY-3-MGMT_NO_ATTR

No attribute provided.

Explanation No attrbiute name was provide to the TTY Management terminal command 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 %MGBL-TTY-3-MGMT_NO_FEATURE

No feature provided.

Explanation No feature name was provide to the TTY Management terminal command 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 %MGBL-TTY-3-MGMT_NOT_ENOUGH_VALUES

Not enough command line values supplied.

Explanation The TTY Management Commands Process has been supplied with less values on the command line than it was expecting.

Recommended Action Copy the error message exactly as it appears 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-TTY-3-MGMT_TOO_MANY_VALUES

Too many command line values supplied.

Explanation The TTY Management Commands Process has been supplied with more values on the command line than it was expecting.

Recommended Action Copy the error message exactly as it appears 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-TTY-3-MGMT_TTY_DETAILS_ERROR

Error getting TTY details

Explanation The show line command was unable to get details about the mnemonic for the TTY.

Recommended Action Copy the error message exactly as it appears 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-TTY-3-MGMT_UNEXPECTED

Unexpected error: ’[chars]’

Explanation The TTY Management Commands Process has encountered an unexpected 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-TTY-3-OPEN_OR_DUP_DEVICE

Failed to [chars] device file ’[chars]’: ’[chars]’

Explanation Failed to open or duplicate the device file that exec requires for read/write 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 %MGBL-TTY-3-PACKET

Unexpected packet error encountered

Explanation The TTY Server has encountered an error using the Packet 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 %MGBL-TTY-3-PHASE2_NON_FATAL

Failed to complete phase 2 initialization: [hex], ’[chars]’.

Explanation The TTY Server has failed to complete phase 2 initialization. For this instance of the server the failure is not fatal; some services are still available, in particular if the aux port is running ksh then this should still be running unimpacted.

Recommended Action Copy the error message exactly as it appears 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-TTY-3-SET_PROCESS_GROUP

Failed to set ’[chars]’ as the controlling terminal for the process: ’[chars]’

Explanation Failed to set the specified device as the controlling terminal 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 %MGBL-TTY-3-SYS_CALL_FAILED

System call failed: [chars], [hex], ’[chars]’

Explanation QNX OS System call failed.

Recommended Action Debug message only. No action is required.

Error Message %MGBL-TTY-3-SYSDB

Unexpected SysDB error encountered: [hex], ’[chars]’

Explanation The TTY Server has encountered an error using the SysDB 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 %MGBL-TTY-3-SYSDB_BIND_ERROR

Error binding to SysDB.

Explanation The show line command was unable to bind to SysDB to retrieve the information required.

Recommended Action Copy the error message exactly as it appears 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-TTY-3-SYSDB_UNBIND_ERROR

Error un-binding to SysDB.

Explanation The show line command was unable to un-bind 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 %MGBL-TTY-3-VERIFYD_EXIT

Process exit with error ’[chars]’, rc equals [dec]

Explanation tty_verifyd exit with failure. TTY related configuration might have not applied.

Recommended Action Please check the configuration and reapply if required.

Error Message %MGBL-TTY-3-WAIT_ON_SIGNAL

An error occured while waiting for a signal: [hex], ’[chars]’

Explanation The exec launcher waits on a signal from the TTY server before continuing. The signal was not successfully received.

Recommended Action Copy the error message exactly as it appears 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-TTY-6-FILE_OPER

Error encountered while opening fpd lock file ’[chars]’

Explanation The TTY Server has encountered an error while opening FPD lock file. Devc-conaux has no issue to run, but FPD warning message will not be printed on AUX port during FPD upgrade.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-TTY-6-ISSU_NFN_REG

Registration for ISSU notification on STANDBY ([chars]), [hex], ’[chars]’ Successful

Explanation Register for ISSU Install notification on standby.

Recommended Action Copy the error message exactly as it appears 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-TTY-6-PHASE2_RETRY

Timeout in phase 2 initialization([chars]) [dec]([chars])

Explanation The TTY Server found error in part of phase 2 initialization. Server is set not-to-restart, so retry. in particular if the aux port is running ksh then this should still be running unimpacted.

Recommended Action Copy the error message exactly as it appears 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-TTY-6-SESSION_STARTUP

Skip detailed routine and proceed([chars]) [dec]([chars])

Explanation The TTY Session startup found some error. Error is ignored and console will be activated.

Recommended Action No action is required.

Error Message %MGBL-TTY-6-SYSDB_INTERN

Unexpected internal error encountered:’[chars]’ [hex], ’[chars]’

Explanation TTY Server is trying to access Sysdb-mc and an error [no members in group] is returned from Sysdb-mc to all the Clients. This is a generic issue with all the admin band processes which comes up earlier than sysdb svrs will have to attempt the reconnect to sysdb with ECM retry.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-TTY-7-CERRNO

Failed to register the TTY error codes: [hex], ’[chars]’

Explanation The TTY Server has failed to register the TTY error codes with the error 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 %MGBL-TTY-7-ISSU_LOAD_DONE

ISSU Notification received for Load Done phase ([chars])

Explanation ’ISSU install notification message for LOAD DONE Phase received’

Recommended Action Copy the error message exactly as it appears 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-TTY-7-ISSU_LOAD_EXEC

ISSU Notification received for Load-Exec (or Load and EXEC) phase ([chars])

Explanation ’ISSU install notification message for LOAD EXEC Phase received’

Recommended Action Copy the error message exactly as it appears 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-TTY-7-MGMT_STATE

Failed to update TTY general state in SysDB: [hex], ’[chars]’

Explanation The TTY server tried to update the TTY’s state in SysDB and failed to do so.

Recommended Action Copy the error message exactly as it appears 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-TTY-7-MGMT_TTY_ATTR_EXTRACT_ERROR

Couldn’t extract TTY attribute (type equals [dec],name equals [[chars]])

Explanation The show line command was unable to extract attribute for the TTY.

Recommended Action Debug message only. No action is required.

Error Message %MGBL-TTY-7-SESSION_STARTUP_OK

[chars]

Explanation Debug 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 %MGBL-TTY-7-TTY_INTERNAL

Unexpected internal error encountered: [hex], ’[chars]’

Explanation The TTY Server unable to access the TTY db for the given ttyid 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.

VTY Messages

Error Message %MGBL-VTY-2-PANIC

Critical error - restarting process.

Explanation A critical internal error has ocurred which requires the process to restart. For example if a lock cannot be released then the process is restarted to avoid deadlock.

Recommended Action Copy the error message exactly as it appears 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-VTY-3-DB

Error performing TTY DB operation ’[chars]’: [hex], ’[chars]’

Explanation An unexpected error occurred whilst the VTY Device DLL was using the TTY DB library.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR* *SUPPORT*

Error Message %MGBL-VTY-3-MEM

Failed to allocate [dec] bytes of memory for object ’[chars]’

Explanation The VTY DLL has failed to acquire the required amount of memory

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message %MGBL-VTY-3-OPERATION

Unsupported or invalid operation request: [chars]

Explanation The TTY Server has asked the VTY DLL to perform an unexpected or incorrectly defined 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 %MGBL-VTY-3-POOL_APPLY_FAILURE

Error performing vty-pool operation [dec]([chars]) ’[chars]’ [chars] will restart to recover

Explanation An unexpected error occurred when process was trying to apply vty-pool configuration. Process will abort to take process core file then restart to recover.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR* *SUPPORT*

Error Message %MGBL-VTY-3-REGISTRATION

Error performing TTY registration operation ’[chars]’: [hex], ’[chars]’

Explanation An unexpected error occurred when the VTY Device DLL asked the TTY Server to perform a TTY management operation.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR* *SUPPORT*

Error Message %MGBL-VTY-3-SESSION

Error performing TTY session operation ’[chars]’: [hex], ’[chars]’

Explanation An unexpected error occurred when the VTY Device DLL asked the TTY Server to perform a session operation.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR* *SUPPORT*

Error Message %MGBL-VTY-3-SYSDB

Error performing SysDB operation ’[chars]’: [hex], ’[chars]’

Explanation An unexpected error occurred when the VTY Device DLL interacted with the SysDB client library.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR* *SUPPORT*

Error Message %MGBL-VTY-3-SYSTEM_LIB_ERROR

System library operation failed unexpectedly: [chars] ([dec])

Explanation A system library call failed unexpectedly.

Recommended Action Copy the error message exactly as it appears 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-VTY-3-TTY_MANAGEMENT

Error performing TTY Management operation ’[chars]’: [hex], ’[chars]’

Explanation An unexpected error occurred when the VTY Device DLL interacted with the TTY Management library

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR* *SUPPORT*

Error Message %MGBL-VTY-6-COMMAND_LINE_ARGS

Unexpected initialization arguments

Explanation Command line arguments were passed to the VTY Device DLL when it was initialized. It does not expect to be passed any arguments.

Recommended Action No action is required.

Error Message %MGBL-VTY-6-SYSDB_TIMEOUT_SET

Couldn’t extend SysDB timeout ’[chars]’

Explanation Couldn’t extend timeout value for ’vty-pool’ config.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the *param* 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 *param* output, call your Cisco technical support representative and provide the representative with the gathered information. *SUPPORT* *SH_TECH*

Error Message %MGBL-VTY-7-CONTROL

Error performing device control operation ’[chars]’: [hex], ’[chars]’

Explanation An unexpected error occurred when the VTY Device DLL asked the TTY Server to perform a control operation.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR* *SUPPORT*

Error Message %MGBL-VTY-7-DATA_PATH

Error performing TTY Data Path operation ’[chars]’: [hex], ’[chars]’

Explanation An unexpected error occurred when the VTY Device DLL asked the TTY Server to perform a Data Path 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. *SUPPORT*

Error Message %MGBL-VTY-7-SYSDB_BULKING

Error calling [chars] for ’[chars]’ sysdb connection: [hex], ’[chars]’ ([chars])

Explanation An unexpected error occurred when interacting with SysDB’s bulking API.

Recommended Action Debug message only. No action is required. *RECUR*

XML_INFRA Messages

Error Message %MGBL-XML_INFRA-7-INIT_ERR

[chars]. Error : [chars]

Explanation There is a problem with the system infrastructure - perhaps the communication infrastructure has not yet stabilized.

Recommended Action If the message recurs, copy the error message exactly as it appears 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-XML_INFRA-7-INTERNAL

[chars]

Explanation The XML Service Library has detected an internal error. As a result, the XML operation that was requested has not been completely carried out.

Recommended Action Repeat the XML operation, transient errors should have passed, and in all likelihood, this operation will go through. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

XML_TTY Messages

Error Message %MGBL-XML_TTY-7-INTERNAL

[chars]

Explanation An internal error has occurred in the XML TTY Agent. Some XML requests (over TTY) may not be able to complete correctly.

Recommended Action Retry the XML request that had the error. Transient conditions should have passed, and in all likelihood, this request will go through. If not, close this TTY session, and restart a new TTY session. If the message recurs, copy the error message exactly as it appears 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-XML_TTY-7-LOGIN

[chars]

Explanation An internal error has occurred in the XML Dedicated Agent. The logint authentication (over dedicated) may not be able to complete correctly.

Recommended Action Retry the XML request that had the error. Transient conditions should have passed, and in all likelihood, this request will go through. If not, close this TTY session, and restart a new TTY session. If the message recurs, copy the error message exactly as it appears 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-XML_TTY-7-SSLINIT

[chars]

Explanation An internal error has occurred in the XML SSL Agent. SSL library initialization may not be able to complete correctly.

Recommended Action Retry the XML request that had the error. Transient conditions should have passed, and in all likelihood, this request will go through. If not, close this TTY session, and restart a new TTY session. If the message recurs, copy the error message exactly as it appears 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-XML_TTY-7-TRANSPORT

[chars]

Explanation The XML TTY Agent encountered a problem when interacting with the device file. This may be due to a problem with the infrastructure

Recommended Action Retry the XML request. Any transient conditions should have passed, and in all likelihood, the request will go through. If not, it may help to close the current TTY session and restart another. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.