-
Cisco IOS XR System Error Message Reference Guide, Release 3.2
-
Preface
-
Cisco IOS XR System Error Messages Overview
-
Access Control List (ACL) Error Messages for Cisco IOS XR
-
Fabric (FABRIC) Error Messages for Cisco IOS XR
-
Hardware Accessibility (HA) Messages for Cisco IOS XR
-
Installation (INSTALL) Messages for Cisco IOS XR
-
Internet Protocol (IP) Messages for Cisco IOS XR
-
Layer 2 (L2) Messages for Cisco IOS XR
-
Media (MEDIA) Messages on Cisco IOS XR
-
Manageability (MGBL) Messages for Cisco IOS XR
-
Operating System (OS) Messages for Cisco IOS XR
-
Packet Infrastructure (PKT_INFRA) Messages for Cisco IOS XR
-
Platform (PLATFORM) Messages for Cisco IOS XR
-
Quality of Service (QOS) Messages for Cisco IOS XR
-
Routing (ROUTING) Messages for Cisco IOS XR
-
Security (SECURITY) Messages for Cisco IOS XR
-
Simple Network Management Protocol (SNMP) Messages for Cisco IOS XR
-
System Database (SYSDB) Messages for Cisco IOS XR
-
Feedback
Table Of Contents
Manageability (MGBL) Messages
This section contains all Management Plane and Manageability related System Error Messages, including config, cli, sml, pm, and so forth. The following facility codes are represented in this module
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-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_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-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.
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.
CFGLAUNCH Messages
Error Message%MGBL-CFGLAUNCH-3-MEMORY Failed to malloc [unsigned int] bytes
Explanation A Configuration Manager command executable has failed to allocate the required amount of memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGLAUNCH-3-PARAMETER [chars]
Explanation Invalid parameters have been passed between processes - contact TAC
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGLAUNCH-3-RESOURCE_CERRNO [chars]. Error: [chars]
Explanation The client library failed to use a resource of one of its (cerrno-returning) libraries.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGLAUNCH-3-STARTUP_ERROR [chars]: Error: '[chars]'
Explanation A component has failed to complete its expected functionality - contact TAC
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGLAUNCH-4-SYSDB_ITEM [chars] '[chars]'. Error: [chars]
Explanation The client library failed to carry out the desired request on a SysDB item or directory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGLAUNCH-6-STARTUP_INFO [chars]
Explanation A component has failed to complete its expected functionality - contact TAC
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
CFGMGR Messages
Error Message%MGBL-CFGMGR-3-ADMIN Can not apply saved admin configuration. Error: '[chars]'
Explanation None.
Recommended Action None.
Error Message%MGBL-CFGMGR-3-BOOT_ERROR [chars] [chars]
Explanation Configuration Manager is displaying an error message during boot time.
Recommended Action None.
Error Message%MGBL-CFGMGR-3-CFS_SYNC_ERR Failed to mirror config files on standby RP. The standby RP is now in an inconsistent state. Please check if there is enough space on the standby RP flash and if the connectivity between the active and standby RP is up. You can initiate a config mirroring operation through a write mem operation on the active RP.
Explanation Configuration manager failed to copy the configuration files from active RP to standby RP.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-3-COMMITDB_WARNING The commit database has reached an inconsistent state. Please use the command 'cfs check' to resynchronize it with the running configuration.
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-CFGMGR-3-DISK_FULL [chars] '[chars]' does not have enough free space. Please free up some space on the storage device.
Explanation The specified storage device is full.
Recommended Action Free up some space on the storage device.
Error Message%MGBL-CFGMGR-3-GIVEUP Giving up on waiting for unavailable nodes to come up. Application of some configuration may fail since all nodes are not up yet. You may need to re-apply any failed configuration.
Explanation None.
Recommended Action None.
Error Message%MGBL-CFGMGR-3-INIT 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.
Recommended Action Please fix the problem and reboot the router is required.
Error Message%MGBL-CFGMGR-3-INIT_RETRY Configuration Manager was unable to initialize the [chars] module. Error: '[chars]'. [chars]. Initialization will be tried again after 60 seconds.
Explanation An error was encountered while initializing one of the modules of configuration manager server. It will sleep for 60 seconds and retry intialization.
Recommended Action Please fix the problem and reboot the router is required.
Error Message%MGBL-CFGMGR-3-INTERNAL [chars]. Error: [chars]
Explanation The client library has reached 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-CFGMGR-3-INTERNAL_NULL A NULL pointer was passed by the Configuration Manager client library to itself
Explanation The client library has passed itself a NULL pointer.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-3-INTFCFG_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-CFGMGR-3-INVENTORY Failed to get the complete node inventory. (Error: '[chars]'). Application of some configuration may fail and you may need to re-apply it.
Explanation None.
Recommended Action None.
Error Message%MGBL-CFGMGR-3-LOCKING Failed to [chars] [chars]. Error: [chars]
Explanation The client library has either failed to obtain or release a lock.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-3-MEMORY Failed to malloc [unsigned int] bytes
Explanation The client library has failed to allocate the required amount of memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-3-NODE_CHECK Checking to make sure all nodes are up prior to application of global configuration.
Explanation None.
Recommended Action None.
Error Message%MGBL-CFGMGR-3-PARAMETER [chars]
Explanation The client library was passed an invalid parameter.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-3-PARAMETER_NULL A NULL parameter was passed by the caller of Configuration Manager
Explanation The client library was passed a NULL pointer.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-3-PARAMETER_OPTION An unsupported combination of options were passed by the caller of Configuration Manager
Explanation The client library was passed an unsupported option parameter.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-3-PARAMETER_STRING A string parameter passed by the caller of Configuration Manager is too long
Explanation The client library was passed a string which is too long.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-3-RESOURCE_CERRNO [chars]. Error: [chars]
Explanation The client library failed to use a resource of one of its (cerrno-returning) libraries.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-3-RESOURCE_ERRNO [chars]. Error: [chars]
Explanation The client library failed to use a resource of one of its (errno-setting) libraries.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-3-VERIFY *** Operation '[chars]' for configuration item '[chars]' has no verifier. Please add a verifier for this configuration item. Use '[chars]' to fix this problem ***
Explanation No verifier found for this config item.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-3-WAIT_NODE Waiting for node '[chars]' to come up. [Time remaining is '[dec]' seconds]
Explanation None.
Recommended Action None.
Error Message%MGBL-CFGMGR-4-CFG_APPLY Config manager was unable to [chars] [chars]. Error - [chars]
Explanation There was an error in applying configuration for a partition or interface, during startup.
Recommended Action None.
Error Message%MGBL-CFGMGR-4-FAILED_PRECONFIGURATION The configuration item '[chars]' could not be moved from active configuration to preconfiguration, so has been removed from the router's configuration. The reason for the failure is: [chars]
Explanation It is likely that the component which is responsible for the configuration is unable to handle preconfiguration, and so needs to be changed to support preconfiguration.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-4-INTERFACE_PORTS [chars]: interface [[chars]]
Explanation None.
Recommended Action None.
Error Message%MGBL-CFGMGR-4-INVALID_PRECONFIGURATION The configuration item '[chars]' could not be moved from preconfiguration to active configuration, so has been removed from the router's configuration. You should check your original configuration as it is likely that the piece of configuration being moved was invalid. The reason for the failure is: [chars]
Explanation If this message appears while the router is starting, it means that an invalid configuration command is contained in the startup configuration. If it appears when a card is inserted, it means that an invalid configuration command had been entered in the preconfiguration of one of the interfaces belonging to that card.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-4-LTRACE [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 the ltrace messages may not be logged.
Recommended Action None.
Error Message%MGBL-CFGMGR-4-SYSDB_ITEM [chars] '[chars]'. Error: [chars]
Explanation The client library failed to carry out the desired request on a SysDB item or directory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CFGMGR-6-BOOT_INFO [chars]
Explanation Configuration Manager is displaying the informational message during boot time.
Recommended Action None.
Error Message%MGBL-CFGMGR-6-CONFIG_COMPLETE Configuration for node '[chars]' has been restored.
Explanation This is an informational message to indicate that configuration for this node has been restored.
Recommended Action None.
Error Message%MGBL-CFGMGR-6-INTERFACE_SHUTDOWN Interface [chars] is being shut down since it does not have any configuration.
Explanation This is an informational message to indicate that this interface has no configuration and will be shutdown by default.
Recommended Action None.
Error Message%MGBL-CFGMGR-7-BOOT_DEFAULT Configuration Manager is applying the default configuration as specified by the boot command option.
Explanation Configuration Manager is displaying the informational message during boot time.
Recommended Action None.
Error Message%MGBL-CFGMGR-7-BOOT_FILE Configuration Manager is applying startup file '[chars]' passed to boot command.
Explanation Configuration Manager is displaying the error message during boot time.
Recommended Action None.
CLEAR Messages
Error Message%MGBL-CLEAR-3-MALLOC_FAILURE 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-SYSDB_BIND_ERROR 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-SYSDB_SET_ERROR 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-SYSDB_UNBIND_ERROR 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.
CLIENTLIBCFGMGR Messages
Error Message%MGBL-CLIENTLIBCFGMGR-3-CFS_CORRUPT The configuration file system seems to be corrupt. Please use the command 'cfs check' to diagnose/fix the problem.
Explanation The configuration file system may be missing some directories/files. Alternatively, the disk itself may be corrupt. The command 'cfs check' should detect and if possible fix the problem.
Recommended Action Use the command 'cfs check' to check/fix the problem.
Error Message%MGBL-CLIENTLIBCFGMGR-3-COMMITDB_WARNING The commit database is not in sync with the running configuration. Please use the command 'cfs check' to resynchronize it.
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-CLIENTLIBCFGMGR-3-DISK_FULL [chars] '[chars]' does not have enough free space. Please free up some space on the storage device before carrying out the operation.
Explanation The specified storage device is full.
Recommended Action Free up some space on the storage device.
Error Message%MGBL-CLIENTLIBCFGMGR-3-INTERNAL [chars]: Error: [chars]
Explanation The client library has reached 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-CLIENTLIBCFGMGR-3-INTERNAL_NULL A NULL pointer was passed by the Configuration Manager client library to itself
Explanation The client library has passed itself a NULL pointer.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CLIENTLIBCFGMGR-3-LOCKING Failed to [chars] [chars]. Error: [chars]
Explanation The client library has either failed to obtain or release a lock.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CLIENTLIBCFGMGR-3-MEMORY Failed to malloc [unsigned int] bytes
Explanation The client library has failed to allocate the required amount of memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CLIENTLIBCFGMGR-3-PARAMETER [chars]
Explanation The client library was passed an invalid parameter.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CLIENTLIBCFGMGR-3-PARAMETER_NULL A NULL parameter was passed by the caller of Configuration Manager
Explanation The client library was passed a NULL pointer.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CLIENTLIBCFGMGR-3-PARAMETER_OPTION An unsupported combination of options were passed by the caller of Configuration Manager
Explanation The client library was passed an unsupported option parameter.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CLIENTLIBCFGMGR-3-PARAMETER_STRING A string parameter passed by the caller of Configuration Manager is too long
Explanation The client library was passed a string which is too long.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CLIENTLIBCFGMGR-3-RESOURCE [chars]. Error: [chars]
Explanation Config manager client library failed to use a resource.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CLIENTLIBCFGMGR-3-RESOURCE_CERRNO [chars]. Error: [chars]
Explanation The client library failed to use a resource of one of its (cerrno-returning) libraries.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CLIENTLIBCFGMGR-3-RESOURCE_ERRNO [chars]. Error: [chars]
Explanation The client library failed to use a resource of one of its (errno-setting) libraries.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CLIENTLIBCFGMGR-3-TARCFG_UNUSABLE The target config session (Id - '[chars]') has entered an inconsistent state and is no longer usable. Error - '[chars]'
Explanation The target config session is unusable.
Recommended Action The config session in question should be ended and a new one started, if required.
Error Message%MGBL-CLIENTLIBCFGMGR-4-SYSDB_ITEM [chars] '[chars]'. Error: [chars]
Explanation The client library failed to carry out the desired request on a SysDB item or directory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-CLIENTLIBCFGMGR-6-ADMIN_CONFIG_CHANGE A configuration commit by user '[chars]' occurred at '[chars]' for the admin configuration.
Explanation A configuration change for the admin config occurred by the specified user.
Recommended Action No action is required.
Error Message%MGBL-CLIENTLIBCFGMGR-6-CONFIG_CHANGE A configuration commit by user '[chars]' occurred at '[chars]'. The configuration changes are saved on the router by commit Id: '[chars]'. To view configuration change(s) use the command - 'show configuration commit changes'.
Explanation A configuration changed occurred by the specified user.
Recommended Action No action is required.
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], line [dec] - 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], line [dec] - 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], line [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-TUPLE_PACK Error packing tuple received from sysdb in [chars], line [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-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], line [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.'
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-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 = [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-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-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-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_CHECK [chars]:Failed to check the presence of items in 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_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-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.
EMORB_XMLAGENT Messages
Error Message%MGBL-EMORB_XMLAGENT-3-CRYPTO_DEACT xmlagent process has exited due to crypto package deactivation. Please unconfigure this command via '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.
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 xmlaent 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-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_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 'getline() API not able to read from terminal devices even after trying' ' many times.'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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-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-SIGNAL_ATTACH Error: [chars]
Explanation The call to event_signal_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-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-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_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.
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.
FAULT_MGR Messages
Error Message%MGBL-FAULT_MGR-2-FAULT_LC LC Reset: Reason - [chars]
Explanation Fault manager Error Handling recieved an error from one of the LC devices. The LC MUST be reset.
Recommended Action Copy the error message exactly as 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_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-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-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_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-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_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-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.
HTTP_COMMON Messages
Error Message%MGBL-HTTP_COMMON-3-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_COMMON-3-EMWEB An EmWeb function to [chars] returned an error to the HTTP ENA filesystem handler
Explanation The HTTP Server 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_COMMON-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 If the message recurs, copy the error message exactly as it appears on 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_COMMON-3-FILE [chars], Error: [chars]
Explanation The HTTP Server 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_COMMON-3-INTERNAL_NULL A NULL pointer was passed by the HTTP Server to itself
Explanation The HTTP Server 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_COMMON-3-MEMORY The HTTP Server handler was unable to allocate [unsigned int] bytes of memory
Explanation The HTTP Server 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.
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-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_PIE SSL could not be enabled because Crypto pie has not been installed. [chars]
Explanation The HTTP Server detects the condition that crypto pie is not installed on router
Recommended Action If the message recurs, copy the error message exactly as it appears on 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-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_VALUE An invalid value was passed by the HTTP Server to itself
Explanation The HTTP Server has passed itself an invalid value - 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-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_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-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.
IFSTATS Messages
Error Message%MGBL-IFSTATS-3-GSP Group error: [chars]: [chars]
Explanation This process failed to perform some GSP related operation.
Recommended Action This message is likely to mean that a periodic stats update has been lost. This probably indicates a failure in the underlying transport mechanism. Copy the error message exactly as it appears on 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 This process failed during initialisation.
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-NOMEM [chars]: Could not allocate memory.
Explanation This process has tried and failed to allocate memory. This probably means that the system as a whole is running low on memory.
Recommended Action Reduce other system activity (e.g. by killing non-essential processes) to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
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.
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*
LIBCFGMGRUTILS Messages
Error Message%MGBL-LIBCFGMGRUTILS-0-CFS_INIT [chars] '[chars]'. Error: [chars]. Please check the CONFIG_FILE variable and the storage medium it points to and reload.
Explanation cfgmgr failed to create the set of directories comprising the CFS repository under the cfs root directory. This renders the system practically unusable though the exec shell prompt shall appear after a while. The potential problems could range from no space on disk to invalid settings of the CONFIG_FILE boot variable (it should be of the form CONFIG_FILE=disk0:/config/startup) or a flawed disk. The system definitely needs to be rebooted after fixing the disk or the CONFIG_FILE boot variable.
Recommended Action Make sure there's enough space on disk or bootflash (where ever CONFIG_FILE points to). Make sure the CONFIG_FILE boot var is set properly as explained above and then reload. If the storage media is flawed then replace it and reload.
Error Message%MGBL-LIBCFGMGRUTILS-1-QSM_ERR Failed to publish a QSM link to top level config directory: '[chars]'. Error: [chars]. Configuration is no longer accessible. Please check the CONFIG_FILE variable and the storage medium it points to and reload.
Explanation Configuration manager failed to publish the CFSROOT qsm link.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-CFS_SYNC_ERR Failed to mirror config files on standby RP. The standby RP is now in an inconsistent state. Please check if there is enough space on the standby RP flash and if the connectivity between the active and standby RP is up. You can initiate a config mirroring operation through a write mem operation on the active RP.
Explanation Configuration manager failed to copy the configuration files from active RP to standby RP.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-COMMITDB_INIT Error encountered in commit database initialization. [chars] Error: '[chars]'
Explanation An error was encountered during initialization of 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. Though, this should not cause loss of configuration as the system applies the alternate ascii file maintained for such situations. But in certain scenarios, changes made in the last one or two commits may be lost.
Recommended Action None.
Error Message%MGBL-LIBCFGMGRUTILS-3-COMMITDB_WARNING The commit database is not in sync with the running configuration. Please use the command 'cfs check' to resynchronize it.
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-LIBCFGMGRUTILS-3-COMMITID_CORRUPT Commit database corruption detected. All changes made after commit '[chars]' will be lost.
Explanation None.
Recommended Action None.
Error Message%MGBL-LIBCFGMGRUTILS-3-DSC_GIVEUP Can not determine if this node is the DSC to apply any admin configuration.
Explanation None.
Recommended Action None.
Error Message%MGBL-LIBCFGMGRUTILS-3-INTERNAL [chars]: Error: [chars]
Explanation The client library has reached 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-LIBCFGMGRUTILS-3-INTERNAL_NULL A NULL pointer was passed by the Configuration Manager client library to itself
Explanation The client library has passed itself a NULL pointer.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-LOCKING Failed to [chars] [chars]. Error: [chars]
Explanation The client library has either failed to obtain or release a lock.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-MEMORY Failed to malloc [unsigned int] bytes
Explanation The client library has failed to allocate the required amount of memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-PARAMETER [chars]
Explanation The client library was passed an invalid parameter.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-PARAMETER_NULL A NULL parameter was passed by the caller of Configuration Manager
Explanation The client library was passed a NULL pointer.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-PARAMETER_OPTION An unsupported combination of options were passed by the caller of Configuration Manager
Explanation The client library was passed an unsupported option parameter.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-PARAMETER_STRING A string parameter passed by the caller of Configuration Manager is too long
Explanation The client library was passed a string which is too long.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-PARSE_INTERFACE The platform library failed to parse interface '[chars]'. Error: [chars].
Explanation The platform library could not parse the interface name.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-RESOURCE [chars]. Error: [chars]
Explanation Config manager common library failed to use a resource.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-RESOURCE_CERRNO [chars]. Error: [chars]
Explanation The client library failed to use a resource of one of its (cerrno-returning) libraries.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-RESOURCE_ERRNO [chars]. Error: [chars]
Explanation The client library failed to use a resource of one of its (errno-setting) libraries.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-3-WAIT_DSC Waiting to find out if this node is the DSC. retrying...
Explanation None.
Recommended Action None.
Error Message%MGBL-LIBCFGMGRUTILS-4-FAILED_CONFIGURATION Some '[chars]' Configuration could not be restored by Configuration Manager. To view failed config(s) use the command - '[chars]'
Explanation None
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-4-LTRACE [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 the ltrace messages may not be logged.
Recommended Action None.
Error Message%MGBL-LIBCFGMGRUTILS-4-READ_VERSION Error: '[chars]'. Please use the command 'cfs check' to bring the commit database back to a consistent state.
Explanation None
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-4-SYSDB_ITEM [chars] '[chars]'. Error: [chars]
Explanation The client library failed to carry out the desired request on a SysDB item or directory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-4-VERSION Version of existing [chars] detected to be incompatible with the installed software. [chars]
Explanation None
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-6-ADMIN_CLEANUP Local administration configuration files on this non-owner Logical Router are being removed.
Explanation Stale administration configuration files on an Logical Router that boots as a non-owner Logical Router are being removed to prevent unwanted administration configuration getting applied later if this Logical Router is later booted as a DSC.
Recommended Action None.
Error Message%MGBL-LIBCFGMGRUTILS-6-BOOT_INFO [chars]
Explanation Configuration Manager is displaying the informational message during boot time.
Recommended Action None.
Error Message%MGBL-LIBCFGMGRUTILS-6-FILE_DELETE Failed to delete file [chars] - '[chars]'. This is a non-fatal error, but if it persists, may lead to filling up of primary disk on designated LR shelf controller.
Explanation Deletion of a file failed. Deletion will be retried whenever it is triggered again. If the error keeps recurring, it may fill up the disk this file resides on.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBCFGMGRUTILS-6-INFO [chars]
Explanation This is just an informational message.
Recommended Action None
LIBMDA Messages
Error Message%MGBL-LIBMDA-3-COMMS [chars]. Error: [chars]
Explanation A communication problem occurred between the management subsystem and the schema server. The management operation that was requested will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBMDA-3-COMP_SCHEMA [chars]
Explanation It is likely that a component has changed its internal management data format but not updated its corresponding schema. The management operation that was requested will not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBMDA-3-INTERNAL [chars]
Explanation The management subsystem has detected an internal error. The management operation that was requested will not be carried out. It may be necessary to restart the process that issued this 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-LIBMDA-3-INTERNAL_NULL The MDA library encountered an internal error (unexpected NULL pointer)
Explanation The management subsystem library has reached an inconsistent state. The management operation that was requested will not be carried out. It may be necessary to restart the process that issued this 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-LIBMDA-3-INTERNALDATA [chars]. Error: [chars]
Explanation An inconsistency has been detected in the data structures of the management subsystem. The management operation that was requested will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBMDA-3-LOCKING The management subsystem library was unable to [chars] the [chars]. Error: [chars]
Explanation The management subsystem encountered an unexpected problem when attempting to lock its internal data structures. The management operation that was requested will not be carried out. It may be necessary to restart the process that issued this 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-LIBMDA-3-MEMOPTS A client of the management subsystem has passed an invalid combination of memory options
Explanation A programming error or memory corruption has led to an invalid parameter being passed to the management 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-LIBMDA-3-MEMORY Could not complete operation due to lack of memory: could not allocate [unsigned int] bytes
Explanation The system is running out of memory and was not able to allocate sufficient memory to carry out a management operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MGBL-LIBMDA-3-PARAMETER [chars]
Explanation An internal error has occurred in an application that has caused it to pass invalid data to the management subsystem. The management operation that was requested will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBMDA-3-PARAMETER_NULL An invalid (null) parameter was passed to the MDA
Explanation An internal error has occurred in an application that has caused it to pass invalid data to the management subsystem. The management operation that was requested will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBMDA-3-PARAMETER_OPTION An unsupported combination of options were passed by a client of the management subsystem
Explanation An internal error has occurred in an application that has caused it to pass invalid data to the management subsystem. The management operation that was requested will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBMDA-3-SYSDB_CONN [chars]. Error: [chars]
Explanation The management subsystem could not connect to the system database, perhaps because either the system database or the communications infrastructure is not yet up.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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-BAG_DECODE [chars]: error decoding the bag. Error: [chars]
Explanation 'Unable to decode the bag containing the result of parsing'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-BAG_FREE [chars]: error in function bag_free_indirections(). Error: [chars]
Explanation 'Unable to free resources associated with the bag'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-BAGENCODE [chars]: [chars]
Explanation 'The call to bag_encode() was unsuccessful'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-BAGENCODEERR bag encode error ([chars])
Explanation 'Failure to encode the bag.'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-BAGFREE [chars]: [chars]
Explanation 'The call to bag_free_indirections() was unsuccessful'
Recommended Action *SH_TECH*
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-CONDITIONALDELETE [chars]: 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-CONDWAIT [chars]: [chars]
Explanation 'The call to pthread_cond_wait() was unsuccessful'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-DEBUG_DATA_FORMAT_INVALID [chars]: Invalid debug data format :'[chars]'. Format should be 'XX.
Explanation 'The cmd file stores the debug data in invalid format.'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-DEBUGREG [chars]: debug registration failed: [dec]
Explanation 'Debug registration failed. The reporting function and error number is listed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-DEBUGUNREG [chars]: debug unregistration failed: [dec]
Explanation 'Debug unregistration failed. The reporting function and error number is listed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-DUPLICATE_INTERFACE_NAME [chars]:Interface name duplication:'[chars]'
Explanation 'Duplicacy in interface name'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-DUPLICATE_INTERFACE_SLOT_NAME [chars]:Interface slot name duplication:'[chars]''[chars]'
Explanation 'Duplicacy in interface slot name'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-EXIT_SUBMODE [chars]
Explanation 'Unable to leave submode'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-FAIL_TO_REGISTER_NOTIFICATION_FOR_PARSER_PERFORMANCE [chars]: sysdb_register_notification failed with error message:[chars]
Explanation 'An internal software error occurred which will result in parser performance not being calculated (if enabled)'
Recommended Action Copy the error message exactly as it appears on 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_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-LIBPARSER-3-FREE [chars]: Bad pointer
Explanation 'Invalid pointer to parser_memory_free function'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-IFMGRBIND Failed to connect with IM after [dec] retries, error: [chars]
Explanation 'Connection to interface manager failed. The failure cause is mentioned in the error message displayed.'
Recommended Action *SH_TECH*
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-INVAL_APP [chars]: [chars]
Explanation 'The global variable spawned_app is not set correctly'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-INVALIDOBJ [chars]: Invalid object format '[chars]'
Explanation 'The format of parser object is invalid. The object is displayed in the message'
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-ITEMDELETE [chars]: 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-ITEMGET [chars]: 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-LIBPARSER-3-ITEMSET [chars]: sysdb_item_set of [chars] '[chars]': [chars]
Explanation 'sysdb item set failed. The error is displyed in the error message.'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-ITEMSETPACKED [chars]: sysdb_item_set of packed '[chars]': [chars]
Explanation 'sysdb item set packed failed. The error is displyed in the error message.'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-LENGTH_EXCEEDED [chars]: [chars]
Explanation 'A Parameter exceeded max length '
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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-MAGICNUM1 [chars]: Bad magic in parser free 1
Explanation 'Invalid magic number in memory to be freed'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-MAGICNUM2 [chars]: Bad magic in parser free 2
Explanation 'Invalid magic number in memory to be freed'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-MALLOC [chars]: Bad arguments
Explanation 'Invalid input parameter to parser_memory_malloc function'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-MEMORY [chars]: parser_memory_free has been called before parser_memory_malloc
Explanation 'Attemting to free unallocated memory'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-MEMORYALLOC [chars]: memory allocation routine failed
Explanation 'The system has run out of memory'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-MUTEXLOCK [chars]: [chars]
Explanation 'The call to pthread_mutex_lock() was unsuccessful'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-MUTEXUNLOCK [chars]: [chars]
Explanation 'The call to pthread_mutex_unlock() was unsuccessful'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-NULL_TREE [chars]: Parser Tree is NULL
Explanation 'The parser tree info 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-LIBPARSER-3-OBJECTSET OBJECT: type [dec] instance [dec]
Explanation 'set parser object'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-OPENCONN [chars]: Opening connection to [chars]: [chars]
Explanation 'The call to open a connection to the parser_server/nvgen_server failed. The error message is displayed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-OPENCONNFM [chars]: Opening connection to parser_filter_fm: [chars]
Explanation 'The call to open a connection to the parser_filter_fm failed. The error message is displayed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-PACKEDTUPLE [chars]: [chars]
Explanation 'construct packed tuple failed. The error is displyed in the error message.'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-READ_BAGSIZE [chars]: [chars]
Explanation 'Unable to read the size of the bag containing the result of parsing'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-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-LIBPARSER-3-SYSDB_DECODE_ERR [chars]: Unable to perform sysdb decode on '[chars]' : Error:[chars]
Explanation 'sysdb decoding of string filter failed'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-SYSDB_GET [chars]: [chars]
Explanation 'Unable to read a value from sysDB. The error message is displayed'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-SYSDB_PREPARE_ERR [chars]:sysdb_transaction_commit() failed. Unable to retieve error associated with the failure. [chars]
Explanation 'The call to sysdb_prepare_error_string() failed'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-SYSDB_TRANS_ABORT [chars]: [chars]. Rebinding to sysDB...
Explanation 'Unable to abort a sysDB transaction. Rebinding...'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-SYSDB_TRANS_START [chars]: [chars]
Explanation 'Unable to start a sysDB transaction'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-SYSDBBIND [chars]: 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-SYSDBBULK [chars]: [chars]
Explanation 'The sysdb bulk operation failed'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-SYSDBLIST [chars]: sysdb_list of '[chars]': [chars]
Explanation 'The sysdb operation failed. Error text is displayed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-SYSDBLISTNEXT [chars]: sysdb_list_next of '[chars]': [chars]
Explanation 'The sysdb operation failed. Error text is displayed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-SYSTEM_ERROR Error code:[dec]. [chars]
Explanation 'A system call 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-LIBPARSER-3-TIMER_CREATE [chars]: [chars]
Explanation 'Unable to create a timer for the pager process'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-TIMER_SETTIME [chars]: [chars]
Explanation 'Unable to set time for the timer for the pager process'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-TOOMANYALIASES [chars]: 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_PACK [chars]: [chars]
Explanation 'Unable to pack values using tuple_pack() API'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-3-UNKNOWNDLL 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-UNKNOWNDLLFUNC 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-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-3-WRONG_FLAG Unknown or wrong combination of flag!!
Explanation 'Flag has to be ENTER,EXIT,DUMP,or RESET. The only valid combination of flags is EXIT|DUMP'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBPARSER-3-WRONG_SEQUENCE measure_performance was called in wrong sequence, [chars]
Explanation 'measure_performance with ENTER should be followed with an 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-LIBPARSER-6-CMT_NOT_SUPPORTED [chars]: Currently comment not supported for '[chars]'
Explanation 'Unable to get tuple information as it is being set by the executable itself'
Recommended Action Copy the error message exactly as it appears on 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-6-HIDDEN_COMMAND This command has been deprecated: '[chars]'
Explanation 'User entered a deprecated command, please use the new form of the command'
Recommended Action Copy the error message exactly as it appears on 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-6-INTERNAL_COMMAND This is a internal cisco-support command: '[chars]'
Explanation 'User entered a internal cisco-support command'
Recommended Action Copy the error message exactly as it appears on 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-BACKMAGIC [chars]: Bad back magic number [dec] '[chars]'
Explanation 'Invalid back magic number'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBPARSER-7-DEBUGINIT [chars]: debug_init_event failed
Explanation 'Debug event logic failed. The reporting function is listed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-7-ERROPENTRACEFILE Unable to open the file [chars].Error: [chars]
Explanation 'Failed to open the trace file and hence tracing failed.'
Recommended Action *DEBUG*
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*
Error Message%MGBL-LIBPARSER-7-FRONTMAGIC [chars]: Bad front magic number [dec] '[chars]'
Explanation 'Invalid front magic number'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBPARSER-7-INVALID_TIMEOUT [chars]: [chars]
Explanation 'Logic error. The value of timeout type is NOT valid'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-7-KWSETTYPE [chars]: Invalid kwset_type: [dec]
Explanation 'The value of iterator-type is invalid'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-7-MEMORYLEAK [chars]: Unfree'ed memory size [dec] '[chars]'
Explanation 'There is unfreed memory'
Recommended Action *SH_TECH*
Error Message%MGBL-LIBPARSER-7-MEMORYPRINT Current parser memory size = [dec] high mark = [dec] since last call = (allocd = [dec], freed = [dec])
Explanation 'It just displays the parser memory statistics'
Recommended Action Copy the error message exactly as it appears on 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-NOTIFREGISTER [chars]: 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-NOTIFUNREGISTER [chars]: 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-WRITEERR [chars]: write failed: [chars]
Explanation 'The call to send the parse request failed. The error message is displayed in the message'
Recommended Action *SH_TECH*
LIBTARCFG Messages
Error Message%MGBL-LIBTARCFG-3-COMMITDB_WARNING The commit database is not in sync with the running configuration. Please use the command 'cfs check' to resynchronize it.
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-LIBTARCFG-3-DISK_FULL [chars] '[chars]' does not have enough free space. Please free up some space on the storage device before carrying out the operation.
Explanation The specified storage device is full.
Recommended Action Free up some space on the storage device.
Error Message%MGBL-LIBTARCFG-3-INTERNAL [chars]: Error: [chars]
Explanation The client library has reached 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-LIBTARCFG-3-INTERNAL_NULL A NULL pointer was passed by the Configuration Manager client library to itself
Explanation The client library has passed itself a NULL pointer.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBTARCFG-3-LOCKING Failed to [chars] [chars]. Error: [chars]
Explanation The client library has either failed to obtain or release a lock.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBTARCFG-3-MEMORY Failed to malloc [unsigned int] bytes
Explanation The client library has failed to allocate the required amount of memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBTARCFG-3-PARAMETER [chars]
Explanation The client library was passed an invalid parameter.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBTARCFG-3-PARAMETER_NULL A NULL parameter was passed by the caller of Configuration Manager
Explanation The client library was passed a NULL pointer.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBTARCFG-3-PARAMETER_OPTION An unsupported combination of options were passed by the caller of Configuration Manager
Explanation The client library was passed an unsupported option parameter.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBTARCFG-3-PARAMETER_STRING A string parameter passed by the caller of Configuration Manager is too long
Explanation The client library was passed a string which is too long.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBTARCFG-3-RESOURCE [chars]. Error: [chars]
Explanation Config manager client library failed to use a resource.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBTARCFG-3-RESOURCE_CERRNO [chars]. Error: [chars]
Explanation The client library failed to use a resource of one of its (cerrno-returning) libraries.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBTARCFG-3-RESOURCE_ERRNO [chars]. Error: [chars]
Explanation The client library failed to use a resource of one of its (errno-setting) libraries.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBTARCFG-3-TARCFG_UNUSABLE The target config session (Id - '[chars]') has entered an inconsistent state and is no longer usable. Error - '[chars]'
Explanation The target config session is unusable.
Recommended Action The config session in question should be ended and a new one started, if required.
Error Message%MGBL-LIBTARCFG-4-SYSDB_ITEM [chars] '[chars]'. Error: [chars]
Explanation The client library failed to carry out the desired request on a SysDB item or directory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBTARCFG-6-ADMIN_COMMIT Administration configuration committed by user '[chars]'.
Explanation A configuration change for the admin config occurred by the specified user.
Recommended Action No action is required.
Error Message%MGBL-LIBTARCFG-6-COMMIT Configuration committed by user '[chars]'. Use 'show configuration commit changes [chars]' to view the changes.
Explanation A configuration changed occurred by the specified user.
Recommended Action No action is required.
Error Message%MGBL-LIBTARCFG-6-REMOVE 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 with the removed configuration 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-LIBTARCFG-6-SYSTEM_ADMIN_COMMIT Administration configuration committed by system.
Explanation A configuration change for the admin config occurred by the the system.
Recommended Action No action is required.
LIBXMLALARM Messages
Error Message%MGBL-LIBXMLALARM-3-INTERNAL An internal error was encountered in the XML Alarm Operations library
Explanation The XML Alarm operation provider has detected an internal error. The XML operation that was requested has not been completely carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBXMLALARM-3-KERNEL An unexepected error was encountered making a kernel call
Explanation The XML Alarm Operations provider has failed to make a kernel call. As a result the XML request has not been completed.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBXMLALARM-3-MEMORY Could not complete operation due to lack of memory: could not allocate [unsigned int] bytes
Explanation The system is running out of memory and was not able to allocate sufficient memory to carry out an XML operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
LIBXMLCFGMGR Messages
Error Message%MGBL-LIBXMLCFGMGR-3-LOCKING Failed to [chars] lock on [chars]. Error - [chars]
Explanation The XML Cfgmgr Operation Provider was unable lock/unlock list of XML sessions.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MGBL-LIBXMLCFGMGR-3-MEMORY Could not complete operation due to lack of memory: could not allocate [unsigned int] bytes
Explanation The system is running out of memory and was not able to allocate sufficient memory to carry out an XML operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MGBL-LIBXMLCFGMGR-3-SESSION_START Failed to add XML session to list of active XML sessions because:
'[chars]'Explanation The XML Cfgmgr Operation Provider was unable to create a target config buffer or add the session to list of active sessions.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
LIBXMLCLI Messages
Error Message%MGBL-LIBXMLCLI-3-MEMORY Could not complete operation due to lack of memory: could not allocate [unsigned int] bytes
Explanation The system is running out of memory and was not able to allocate sufficient memory to carry out an XML operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MGBL-LIBXMLCLI-3-MUTEX Failed to [chars] XML CLI mutex for user '[chars]' from thread '[dec]'. Error: '[chars]'. Ensuing CLI over XML requests may fail.
Explanation An error was encountered in obtaining or releasing the lock on the mutex for CLI over XML module.
Recommended Action Restarting the XML agent the CLI over XML request was sent to should fix the problem.
LIBXMLMDA Messages
Error Message%MGBL-LIBXMLMDA-3-INTERNAL [chars]: '[dec]'
Explanation The XML MDA operation provider has detected an internal error. The XML operation that was requested has not been completely carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBXMLMDA-3-MEMORY Could not complete operation due to lack of memory: could not allocate [unsigned int] bytes
Explanation The system is running out of memory and was not able to allocate sufficient memory to carry out an XML operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MGBL-LIBXMLMDA-3-PARAMETER An invalid parameter was passed to the XML MDA translation library
Explanation An internal error has occurred in an application that has caused it to pass invalid data to the management subsystem. The management operation that was requested will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LIBXMLSERVICE Messages
Error Message%MGBL-LIBXMLSERVICE-3-DEBUG The XML Service Library was unable to register or unregister with the debugging infrastructure. Error : [chars]
Explanation There is a problem with the system infrastructure - perhaps the communication infrastructure has not yet stabilised.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBXMLSERVICE-3-INTERNAL An internal error was encountered in the XML Service Library
Explanation The XML Service Library has detected an internal error. The XML operation that was requested has not been completely carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBXMLSERVICE-3-INVALIDXML The XML Service Library was unable to parse the XML request.
Explanation The XML Service Library has been passed an XML request containing elements which are unknown, incorrectly positioned or of an incorrect format. The XML operation that was requested has not been completely carried out.
Recommended Action No action is required.
Error Message%MGBL-LIBXMLSERVICE-3-KERNEL An unexepected error was encountered making a kernel call
Explanation The XML Service Library has failed to make a kernel call. As a result the XML request has not been completed.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBXMLSERVICE-3-MEM_NOTIF [chars] [chars]
Explanation The XML library has received an erroneous notification for change in memory usage of the router.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBXMLSERVICE-3-MEMORY Could not complete operation due to lack of memory: could not allocate [unsigned int] bytes
Explanation The system is running out of memory and was not able to allocate sufficient memory to carry out an XML operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MGBL-LIBXMLSERVICE-3-RBTREE An error has been encountered when calling the Red Black tree library
Explanation The Red Black tree used by the XML Service Library has returned an unexpected error. This library is critical for supporting XML iterators.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-LIBXMLSERVICE-3-XMLPARSING Failed to parse the XML request '[chars]'
Explanation The XML Service Library has encountered an error when attempting to parse the XML request provided. The details of the error condition should explain more about the problems that were encountered.
Recommended Action No action is required.
MDACON Messages
Error Message%MGBL-MDACON-3-BIND [MDACon] Could not bind to the MDA: [chars]. MDACon cannot carry out any operations - try quitting and restarting it
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-3-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-3-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-3-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.
Error Message%MGBL-MDACON-3-NOMEM [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-3-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-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_NOTFOUND [MDACon] Warning: now bound to a non-existent node.
Explanation The user bound to a node which does not exist. This is a warning only - this action is perfectly legal.
Recommended Action Check that this is the directory you intended to bind to.
Error Message%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-DATALIST
[MDAcon] While executing the datalist 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-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-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-FIND [MDACON] While executing the find or find_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-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-MISSNAME [MDACon] Missing object name
Explanation The command entered requires an object 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-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-SETTIMEOUT [MDACon] While setting the timeout time 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-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-4-VALUEFMT [MDACon] [chars]
Explanation The MDA is behaving unexpectedly.
Recommended Action None.
NFEA Messages
Error Message%MGBL-NFEA-3-FATAL_ERR [chars]
Explanation A fatal error occurred in Netflow which involves exiting the process.
Recommended Action *SUPPORT*
Error Message%MGBL-NFEA-6-INFO_MSG Info: [chars]
Explanation This is a Informational message in the Netflow to indicate an operation.
Recommended Action No action is required.
NFMA Messages
Error Message%MGBL-NFMA-3-CFG_APPLY_ERR Could not apply verified config: [chars]
Explanation This is a error message in the Netflow MA to indicate that due to specified reasons, it was unable to apply the config that it had previously verified and accepted. This errmsg usually means that the netflow running config and and netflow operational state are out of sync.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFMA-3-FATAL_ERR Fatal error: [chars]
Explanation A fatal error occurred in Netflow MA.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFMA-3-NONFATAL_ERR Nonfatal error: [chars]
Explanation This is a error message in the Netflow MA to indicate either anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
NFMGR Messages
Error Message%MGBL-NFMGR-3-CFG_APPLY_ERR Could not apply verified config: [chars]
Explanation This is a error message in the Netflow manager to indicate that due to specified reasons, it was unable to apply the config that it had previously verified and accepted. This errmsg usually means that the netflow running config and and netflow operational state are out of sync.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFMGR-3-FATAL_ERR Fatal error: [chars]
Explanation A fatal error occurred in netflow manager.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFMGR-3-NONFATAL_ERR Nonfatal error: [chars]
Explanation This is a error message in the Netflow manager to indicate either anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
NFSVR Messages
Error Message%MGBL-NFSVR-1-BFM_RET_BUFFER Could not return buffman buffer - [chars]
Explanation The NetFlow Server could not return a buffman buffer. The error code is displayed.
Recommended Action No action is required.
Error Message%MGBL-NFSVR-1-CONDVAR_INIT Could not create condvar for [chars] synchronization
Explanation The OS could not create the specified condvar
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-CORRUPT_REGION BufferBufBu Manager region has been corrupted
Explanation The Buffer Manager region used by the NetFlow Server has been corrupted
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-DEBUG_REGISTER Could not register for debug events : [chars]
Explanation 'Could not register to manage NetFlow Server specific debugs.'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-DESCRIPTOR_RING Could not create descriptor ring to receive packets from cpuctrl
Explanation The atomic descriptor ring for receiving packets from the cpuctrl could not be created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-EDM Error initializing nfsvr EDM : [chars], reason: [chars]
Explanation Could not establish EDM connection with SysDB (possible transient).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-EVENT_CONN Can not establish connection with [chars]: [chars]
Explanation Can not establish event connection with the specified 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-NFSVR-1-EVENT_MANAGER_CREATE Can not create event manager for [chars]
Explanation Can not create the specified event manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-IRP_INIT Could not intialize the IRP table. Error: [chars]
Explanation The NetFlow Server could not create the AVL tree for the IRP table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-LTRACE Failed to initialize ltrace support. Cerr: [chars]
Explanation The NetFlow Server could not initialize the ltrace support functionality
Recommended Action No action is required.
Error Message%MGBL-NFSVR-1-MUTEX_INIT Could not create mutex for [chars] communication
Explanation The OS could not initialize the specified mutex
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-MUTEX_LOCK Could not lock buffman mutex - [chars]
Explanation The NetFlow Server could not lock the buffman mutex. The error code is displayed.
Recommended Action No action is required.
Error Message%MGBL-NFSVR-1-NETIO Could not register with NetIO rc: [chars]
Explanation The NetFlow Server could not register with NetIO.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-NFMGR Could not register with ENS/NRS for NetFlow Manager rc: [chars]
Explanation The NetFlow Server could not establish an ENS/NRS connection with the NetFlow 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-NFSVR-1-NO_COVERAGEID Unable to get coverage id
Explanation Could not obtain coverage ID of the card where NetFlow Server is running.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-NOCHUNKS Could not create chunks for cache [chars]
Explanation The chunk memory blocks could not be allocated for the specified cache.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-NORESOURCE Can not allocate resource for [chars]
Explanation An attempt to allocate a resource 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-NFSVR-1-PACKET_INTERFACE Failed to initialize input packet interface for flows: [chars]
Explanation Can not establish the interface for receiving netflow packets.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-SEND_ASYNC Could not send async event to kill exporter thread for [chars]. Error: [chars]
Explanation The NetFlow Server could not send an async pulse to the exporter thread for the specified exporter. Restart the NetFlow Server 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-NFSVR-1-THREAD Could not create [chars] thread: [chars]
Explanation The system could not create the specified thread. The error code is displayed
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-THREAD_KEY Could not create the thread key: [chars]
Explanation The NetFlow Server could not create a thread key for the for the avl tree object thread specific data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-THREAD_SPECIFIC Could not create a thread specific key. Error: ([hex]). [chars]
Explanation The NetFlow Server could not create thread specific key to be used by the AVL tree for Interface Resolution Processing
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-1-TIMER_ALLOC Could not allocate a timer for netflow ager : [chars]
Explanation Could not allocate a timer. Netflow will not run on this line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-3-FATAL_ERR Fatal error: [chars]
Explanation A fatal error occurred in NetFlow 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-NFSVR-3-NONFATAL_ERR Nonfatal error: [chars]
Explanation This is a error message in the NetFlow Server to indicate either anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources or cache over flows, excessive esport drops etc. In many cases these messages must not keep appearing after the temperory situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NFSVR-7-REINIT_REGION Buffer Manager (buffman) has reinitialized
Explanation The Buffer Manager (buffman) has been restarted
Recommended Action No action is required.
Error Message%MGBL-NFSVR-7-RTRID Could not register for Router ID notifications: [chars]
Explanation The NetFlow Server could not register with the NetFlow Manager to receive router-id configuration notifications
Recommended Action No action is required.
NVGEN Messages
Error Message%MGBL-NVGEN-3-ALIASDELETE [chars]: The deleted alias :[chars] was not found in the alias table
Explanation 'The alias delete notification correponds to a non-existing entry'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-ALIASREPLACE [chars]: The replaced alias :[chars] was not found in the alias table
Explanation 'The alias set notification correponds to a non-existing entry'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-ALIASSUBMODE [chars]: The alias submode: [chars] does not exist.
Explanation 'The alias's submode does not exist in the parser's alias table'
Recommended Action *SH_TECH*
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-BGCOPTIONMISSING2 [chars]: bgcoption missing ',' after type: '[chars]'
Explanation 'The input is invalid. The calling function and the command are displayed'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-BGCOPTIONMISSING3 [chars]: bgcoption missing ',' after path count: '[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:[hex] ref [hex] : [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-CFGDATANEXT [chars]: failed to get next data from [chars]: [chars]
Explanation 'Unable to get next value in sysdb iterator. The error text is displayed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-CONDWAIT [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-CONNIFMGR [chars]: Unable to connect to interface manager. Error: [dec]
Explanation 'Interface Manager API im_control_server_bind returned an error.'
Recommended Action *SH_TECH*
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-DEBUGREG [chars]: debug registration failed: [dec]
Explanation 'Debug registration failed. The reporting function and error number is listed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-DEBUGUNREG [chars]: debug unregistration failed: [dec]
Explanation 'Debug unregistration failed. The reporting function and error number is listed in the message'
Recommended Action *SH_TECH*
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-DUPCSBFLAGS [chars]: [chars]
Explanation 'The call to parser_get_flags_ptr returned a null pointer'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-DUPCSBOBJ [chars]: [chars]
Explanation 'The call to parser_dup_objects returned a null pointer'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-DUPLICATE_INTERFACE_NAME [chars]:Interface name duplication:'[chars]'
Explanation 'Duplicacy in interface name'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-DUPLICATE_INTERFACE_SLOT_NAME [chars]:Interface slot name duplication:'[chars]''[chars]'
Explanation 'Duplicacy in interface slot name'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-DUPSUBMODE [chars]: [chars]
Explanation 'The call to parser_dup_submode_q failed'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-ENCRYPT1 [chars]: pw_encrypt 1-way of '[chars]' failed.
Explanation 'The 1-way encryption operation failed. The reporting function is displayed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-ENCRYPT2 [chars]: pw_encrypt 2-way of '[chars]' failed.
Explanation 'The 2-way encryption operation failed. The reporting function is displayed in the message'
Recommended Action *SH_TECH*
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-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-EVENTMGRDESTROY [chars]: event_manager_destroy failed : [chars]
Explanation 'The call to event manager destroy in parser server failed. Parser must exit in this case. The error is displayed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-FAIL_TO_SYSDB_REGISTER_NOTIFICATION_FOR_FAILED_CONFIG [chars]: sysdb_register_notification failed with error message:[chars]
Explanation 'An internal software error occurred which might result in failed config in not being applied when a new interface is detected'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-NVGEN-3-FAILED_CONFIG_NOT_APPLIED [chars]: sysmgr_start_process failed to spawn config process ! rc=[chars]
Explanation 'Unable to apply failed config automatically when the pie was installed'
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 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-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-IMIFHANDLE [chars]: im_ifhandle_allocate of [chars] gets [dec]: [chars]
Explanation 'Error condition detected. Calling function and error text is displayed in the message'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-INITIFMGR [chars]:im_control_server_bind gets [dec]: [chars]
Explanation 'Initialization of interface manager connection failed. The reporting function and the error text 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-INTDELETEFAIL [chars]:Can not delete interface (name-slot): [chars]-[chars]
Explanation 'Unable to delete the inteface name with given slot'
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-INTFNOTFOUND [chars]: Interface not found - [chars]
Explanation 'Interface not found by interface manager API im_interface_find.'
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-INVALIDARG [chars]: left arg([dec]) is null, string expected
Explanation 'Argument found is either null or does not match with the expected arg type'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-INVALIDDEFAULT Invalid default value '[chars]' in tree '[chars]'
Explanation 'A default value of a numstring (used when user omits that part) cannot be parsed correctly. Because it is the default, it must be of legal syntax.'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-INVALIDDLL Invalid dll spec: name:[chars], fcn:[chars], errmsg:[chars],
in tree '[chars]'Explanation 'An error occurred when trying to open the dll library or function for hostname validation. The function type is specified in parser.h: typedef parser_loolean_t (*parser_validate_hostname_func_type)(char *str); Please refer to ENG-29318 for more details.'
Recommended Action *SH_TECH*
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-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-NVGEN-3-INVALIDRANGE Invalid [chars] range in tree '[chars]'
Explanation 'The numerical range within the token details structures is invalid'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-INVALIDSTRING Invalid string pointer [hex] in tree '[chars]'
Explanation 'The offset to the string heap, or the offset within the string heap, is bogus'
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-ITEMDELETE [chars]: 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-NVGEN-3-ITEMGET [chars]: 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-NVGEN-3-ITEMSET [chars]: sysdb_item_set of [chars] '[chars]': [chars]
Explanation 'sysdb item set failed. The error is displyed in the error message.'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-ITEMSETPACKED [chars]: sysdb_item_set of packed '[chars]': [chars]
Explanation 'sysdb item set failed. The error is displyed in the error message.'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-ITEMSETUINT32 [chars]: sysdb_item_set of uint32 '[chars]'=[dec]: [chars]
Explanation 'sysdb item set failed. The error is displyed in the error message.'
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-MALLOCFAILED [chars]:[chars]
Explanation 'system does not have enough memory to allocate test strings during nvgen'
Recommended Action *SH_TECH*
Error Message%MGBL-NVGEN-3-MEMORYALLOC [chars]: memory allocation routine failed
Explanation 'The system has run out of memory'
Recommended Action *SH_TECH*
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 'type is invalid'
Recommended Action *SH_TECH*
Error Message%MGBL-PARSER-7-LRD_EVENT_NODEID_FAILED LRd event type nodeid get failed: Error: '[chars]'
Explanation Parser has received notification from LRd. But couldn't ascertain what node has caused this notification.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PARSER-7-LRD_EVENT_TYPE_FAILED LRd event type get failed: Error: '[chars]'
Explanation Parser has received notification from LRd. But couldn't ascertain what type of notification 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-PARSER-7-LRD_NOTIFREGISTER LRd notification registration failed: Error: '[chars]'
Explanation Registration to LRd failed.
Recommended Action Restart parser_server process after all cards come up.
Error Message%MGBL-PARSER-7-NOTIFICATION [chars]: notifier action: [hex]
Explanation 'Unexpected notification event'
Recommended Action *SH_TECH*
Error Message%MGBL-PARSER-7-NOTIFREGISTER [chars]: 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-PARSER-7-NOTIFUNREGISTER [chars]: 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-PARSER-7-PIPEMODE [chars]: [chars]
Explanation 'Unable to find pipemode submode'
Recommended Action *SH_TECH*
PM_COLLECTOR Messages
Error Message%MGBL-PM_COLLECTOR-3-BAG_DECODE Entity:[chars], Error:[chars]
Explanation The Collector has failed to decode the bag read from sysdb
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_COLLECTOR-3-BAG_ENCODE Entity:[chars], Error:[chars]
Explanation The Collector has failed to encode the PM generated bag
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_COLLECTOR-3-BGP_DATALIST_NEXT Error reading bgp data. Error: [chars]
Explanation An error has occurred when bgp_client_nbr_datalist_next() was called
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-BGP_DATALIST_START Error reading bgp. Error: [chars]
Explanation An error has occurred when bgp_client_nbr_datalist_start() was called
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-BGP_INIT Error initializing bgp library. Error: [chars]
Explanation An error has occurred when bgp_client_init() was called
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-BGP_NBR_COUNT Error reading bgp neighbor count. Error: [chars]
Explanation An error has occurred when bgp_client_nbr_count() was called
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-BGP_NBR_DATALIST Error reading bgp datalist. Error: [chars]
Explanation An error has occurred when bgp_client_nbr_datalist() was called
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-BGP_NBR_GET Error reading data for bgp neighbor. Error: [chars]
Explanation An error has occurred when bgp_client_nbr_get() was called
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-CHKPT [chars] : [chars]
Explanation An error has occurred while doing a checkpointing operation at the collector
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-CREATE_TIMER [chars]
Explanation The Collector has been unable to initialize/allocate memory for a collection request
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-DATA_NOT_FOUND [chars]: [chars]
Explanation Data collection cannot be enabled because requested entity is not enabled or does not provide data. Please check if the requested entity is configured properly.
Recommended Action Configure and enable the protocol e.g. OSPF, MPLS for which the data is to be gathered using peformance management collector and then configure PM.
Error Message%MGBL-PM_COLLECTOR-3-DATALIST_FREE [chars] : [chars]
Explanation An error has occurred while doing a sysdb_datalist_free() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-DATALIST_NEXT [chars] : [chars]
Explanation An error has occurred while doing a sysdb_datalist_next() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-DATALIST_START [chars] : [chars]
Explanation An error has occurred while doing a sysdb_datalist_start() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-DB_INIT_BUFFER [chars]
Explanation The Collector has been unable to initialize/allocate memory for a collection request
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-DEBUG [chars]: [chars]
Explanation An error while initializing/registering debugging events
Recommended Action *NONE*
Error Message%MGBL-PM_COLLECTOR-3-GROUP_SEND_NB GSP error sending. Error code: [dec]
Explanation An error has occurred when group_send_nb() was called
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-IM_ATTR_GET Unable to get interface bandwidth : [chars]
Explanation An error has occurred while doing a im_attr_get() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-IM_ATTR_INIT IM client library initialization failed : [chars]
Explanation An error has occurred while doing a im_attr_init() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-IM_CONTROL_BIND IM initialization failed : [chars]
Explanation An error has occurred while doing a im_control_server_bind() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-IM_INTF_FIND Error: [chars]
Explanation An error has occurred while doing a im_interface_find() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-IM_INTF_NAME Error: [chars]
Explanation An error has occurred while doing a im_interface_name() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-INIT [chars], ERROR: '[chars]'
Explanation The Collector has failed to initialise.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_COLLECTOR-3-INSTANCE_COUNT [chars]
Explanation The Collector has been unable to get # of entity instances
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-INTERNAL [chars]: '[dec]' : [chars]
Explanation The Collector has detected an internal error. The Collection operation that was requested has not been completely carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_COLLECTOR-3-LIST_FREE [chars] : [chars]
Explanation An error has occurred while doing a sysdb_list_free() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-LIST_NEXT [chars] : [chars]
Explanation An error has occurred while doing a sysdb_list_next() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-LIST_START [chars] : [chars]
Explanation An error has occurred while doing a sysdb_list_start() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-LOGIC_ERROR [chars]: [chars] : [chars]
Explanation This is a generic error message. The message content will specify the actual error.
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-MALLOC_ERR [chars]:[chars]
Explanation Unable to malloc the memory.
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-MEMORY Could not complete operation due to lack of memory.
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_COLLECTOR-3-MSG_SEND [dec]: [chars]
Explanation An error while sending a message from collector to server.
Recommended Action *SH_TECH*
Error Message%MGBL-PM_COLLECTOR-3-PLATFORM_NODE_PARSE Error: [chars]
Explanation An error has occurred while doing a platform_node_parse_ifname() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-SERVERDATA [chars]
Explanation The Collector has been passed invalid or inconsistent data by the server.
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-TE_LINK_TABLE_FULL Can not perform TE Link collection for interface: [chars]
Explanation There is no more space in the instance-based collection table
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-TE_NOT_ACTIVE TE applications are not active on interface : [chars]
Explanation Can not perform TE statistics collection, since TE applications are not active.
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-3-TFTP [chars]:[chars]:[chars]
Explanation An error has occurred while tftp dumping of the collected data from the pm collector process.
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-6-TFTP_DISABLED [chars]
Explanation This is an informational message
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-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_COLLECTOR-7-SYSDB_BIND [chars] : [chars]
Explanation An error has occurred while doing a sysdb_bind() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-7-SYSDB_DATALIST [chars] : [chars]
Explanation An error has occurred while doing a sysdb_datalist() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-7-SYSDB_FIND [chars] : [chars]
Explanation An error has occurred while doing a sysdb_find() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-7-SYSDB_GET [chars] : [chars]
Explanation An error has occurred while doing a sysdb_item_get() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-7-SYSDB_LIST [chars] : [chars]
Explanation An error has occurred while doing a sysdb_list() operation
Recommended Action No action is required.
Error Message%MGBL-PM_COLLECTOR-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.
PM_SERVER Messages
Error Message%MGBL-PM_SERVER-3-CERRNO_REGISTER Failed to register cerrno error DLL:[chars]
Explanation The call to cerr_register_dll 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-PM_SERVER-3-CHKPT [chars]:'[chars]'
Explanation The pm server has failed to perform a check point operation.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_SERVER-3-COLLECTION [chars]:[chars]
Explanation pm server failed to do a collection operation.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_SERVER-3-DEBUG_CLEANUP [chars]
Explanation The call to debug_cleanup() failed
Recommended Action *RECUR*
Error Message%MGBL-PM_SERVER-3-DEBUG_INIT [chars]
Explanation The call to debug_init_event() failed
Recommended Action *RECUR*
Error Message%MGBL-PM_SERVER-3-DEBUG_REGISTER [chars]
Explanation The call to debug_init_event() failed
Recommended Action *RECUR*
Error Message%MGBL-PM_SERVER-3-ENTITY_ERROR [chars]
Explanation Logic error. The specified entity is not supported.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_SERVER-3-EVENT_MGR [chars]
Explanation The call to event_manager_create() failed
Recommended Action *RECUR*
Error Message%MGBL-PM_SERVER-3-GSP [chars]:[chars]
Explanation returned failure from GSP operation/API.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_SERVER-3-GSP_MSG Unexpected/unknown msg from '[chars]'. Code:[dec], sender:[dec]
Explanation Unknown message from collector/gsp.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_SERVER-3-LOGIC_ERR [chars]
Explanation Unexpected condition, as specified, has been detected
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_SERVER-3-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. If problem still persists then 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-PM_SERVER-3-NOMEM [chars]
Explanation The pm server failed to allocate memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_SERVER-3-NOTIF_REGISTER Failed to register for notifications : '[chars]'
Explanation The server has failed to register for notification from sysdb.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM_SERVER-3-SYSDB_BIND [chars]
Explanation The call to sysdb_bind() 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-PM_SERVER-3-SYSDB_DATALIST [chars]
Explanation The call to sysdb_datalist() 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-PM_SERVER-3-SYSDB_DATALIST_NEXT [chars]
Explanation The call to sysdb_datalist_next() failed
Recommended Action *RECUR*
Error Message%MGBL-PM_SERVER-3-SYSDB_DATALIST_START [chars]
Explanation The call to sysdb_list_start() 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-PM_SERVER-3-SYSDB_ITEM_GET [chars]
Explanation The call to sysdb_item_get() 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-PM_SERVER-3-SYSDB_LIST [chars]
Explanation The call to sysdb_list() 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-PM_SERVER-3-SYSDB_REG_VER [chars]
Explanation The call to sysdb_register_verification3() 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-PM_SERVER-3-SYSDB_VRFN [chars]
Explanation The call to sysdb_vrfn_fns_verify_init() 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-PM_SERVER-3-SYSMGR Unable to notify System Mgr. Error:[chars]
Explanation Notification of system manger process 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-PM_SERVER-3-TUPLE_UNPACK [chars]
Explanation The call to tuple_unpack() 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-PM_SERVER-3-VERIF_REGISTER Failed to register for verification: '[chars]'
Explanation The server has failed to register for verification from sysdb.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PM_THRESHOLD Messages
Error Message%MGBL-PM_THRESHOLD-5-ERROR 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 If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PM Messages
Error Message%MGBL-PM-CPU-THRESHOLD-5-CPU-UTILIZATION Slot [dec] : '[chars]'
Explanation The CPU Utilization has met a threshold condition.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM-IF-THRESHOLD-5-IF-ERRORS Interface [dec] : '[chars]'
Explanation The Interface Errors has met a threshold condition.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-PM-IF-THRESHOLD-5-IF-UTILIZATION Interface [dec] : '[chars]'
Explanation The Interface Utilization has met a threshold condition.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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 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 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-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-PUSH_BYTE_ERROR The RS232 DLL was unable to push a byte to the TTY Server
Explanation The RS232 DLL has failed to register the RS232 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-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-CERRNO Failed to register the RS232 error codes ([chars])
Explanation The RS232 DLL has failed to register the RS232 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-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.
S2681 Messages
Error Message%MGBL-S2681-3-ASYNC_ATTACH_ERROR Unable to attach event for the UART interrupt (error: [dec])
Explanation The S2681 UART driver has been unable to attach an event for 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-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-INT_HOOK_ERROR Unable to attach to the UART interrupt (error: [dec])
Explanation The S2681 UART driver has been unable to attach to 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-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-OVERRUN_ERROR Character overrun detected
Explanation The S2681 UART driver detected a character overrun condition.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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-STACKSIZE_ERROR Unable to set stack size for the interrupt handler.
Explanation The S2681 UART driver was unable to set the stack size 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.
SCHEMA_CMN Messages
Error Message%MGBL-SCHEMA_CMN-3-DEBUG The schema infrastructure was unable to register or unregister with the debugging infrastructure. Error : [chars]
Explanation There is a problem with the system infrastructure - perhaps the communication infrastructure has not yet stabilised. The management operation that was requested will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-SCHEMA_CMN-3-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.
Error Message%MGBL-SCHEMA_CMN-3-MEMORY Could not complete operation due to lack of memory: could not allocate [unsigned int] bytes
Explanation The system is running out of memory and was not able to allocate sufficient memory to carry out a management operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MGBL-SCHEMA_CMN-3-PARAMETER_NULL A NULL parameter was passed by the caller of the Management Data API
Explanation An internal error has occurred in an application that has caused it to pass invalid data to the management subsystem. The management operation that was requested will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SCHS Messages
Error Message%MGBL-SCHS-3-BACKEND Invalid data has been passed by the backend library when processing a request for MDA management data. The running of the server has not been affected, but further requsts for management data may be equally unsuccessful.
Explanation The Schema Server was sent an invalid parameter when being invoked to handle a request for management data. The request will not be handled. It may be necessary to restart the schema server process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-SCHS-3-CMDARGS Too many arguments were passed when starting the Schema Server process
Explanation The schema was passed more command-line arguments than it was expecting. This could indicate a problem with an installed package.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-SCHS-3-COMMS Schema Server communication problem: [chars]. Error: [chars]
Explanation The schema server encountered a problem when setting up a communication channel or when sending or receiving a message. This may be due to a problem with the communications transport, or it may help to restart the schema 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-SCHS-3-CONNECTIONS [chars]. Error: [chars]
Explanation The schema server encountered a problem while setting up its internal connection structures. It may not be possible to use the schema server. It may help to restart the schema 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-SCHS-3-FILE File error: [chars]
Explanation The Schema Server has failed to load a file, because it is corrupt, invalid or contains information conflicting with another schema file.
Recommended Action It may be necessary to reinstall the package that contains the offending file.
Error Message%MGBL-SCHS-3-FILELOAD Unable to load schema file '[chars]' due to error '[chars]'
Explanation The Schema Server has failed to load a file, because it is corrupt, invalid or contains information conflicting with another schema file.
Recommended Action It may be necessary to reinstall the package that contains the offending file.
Error Message%MGBL-SCHS-3-FILEUNLOAD Unable to unload schema file '[chars]' due to error '[chars]'
Explanation The Schema Server has unexpectedly failed to unload a file, and the datastructures in the Schema Server may no longer be consistent or useable. It may be necessary to restart the Schema Server process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-SCHS-3-INITERROR Schema server failed to initialise: [chars] ([chars])
Explanation The schema server encountered an error during its initialisation. The schema server will restart.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-SCHS-3-INSTALL An error occurred in the install infrastructure when interacting with the schema server to determine which files are installed, or are being installed or removed. Error: [chars] ([chars]).
Explanation The install infrastructure has returned an invalid response to the schema server when determining which schema files are installed, or are being installed or removed. The schema files on the router may not be correctly loaded, and may not be useable. It may be necessary to restart the schema server process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-SCHS-3-INTERNAL [chars]. Error: [chars]
Explanation The Schema Server has reached an inconsistent state. The management operation requested will not be carried out. It may be necessary to restart the schema server process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-SCHS-3-INTERNAL_NULL The schema server encountered an unexpected problem (unexpected NULL pointer)
Explanation The management subsystem has encountered an internal problem. The management operation that was requested will not be carried out. It may be necessary to restart the schema server process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-SCHS-3-REDUNDANCY [chars]. Error: [chars]
Explanation The schema server encountered a problem preparing for a failover scenario. The schema server may not recover correctly if a failover occurs. It may help to restart the schema 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-SCHS-3-REDUNDANCY_STATE The System Manager process passed an unrecognised node state ([hex]) to the schema server
Explanation The schema server encountered a problem preparing for or during a failover scenario. The schema server may not recover correctly if a failover occurs. It may help to restart the schema 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-SCHS-3-SHUTDOWNERROR Schema server error during shutdown: [chars] ([chars])
Explanation The schema server encountered an error during its shutdown process. The schema server will shut down anyway.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-SCHS-3-VERSION Different versions of the Schema Server and Management Data API client library are in use - one will have to be upgraded if they are to be able to communicate. Client library version [dec], Server version [dec]
Explanation The Schema Server and Management Data API have incompatible versions - the older one will have to be upgraded.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-SCHS-4-MALLOC_OPTS The schema server was unable to enable memory checking. Error: [chars]. The server will continue to initialise, as this doesn't affect its operation.
Explanation The schema server encountered an error while enabling memory checking. The error is ignored as it does not affect the functioning of schema 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-SCHS-6-VERSIONCHANGE A schema version change has occurred. Any management applications which use the schema may wish to update to the latest 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 Copy the error message exactly as 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-ASYNC_ATTACH_ERROR Unable to attach event for the UART interrupt (error: [dec])
Explanation The ST16550 UART driver has been unable to attach an event for 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-COND_SIGNAL_ERROR Unable to signal on the status variable
Explanation The ST16550 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-ST16550-3-INT_HOOK_ERROR Unable to attach to the UART interrupt (error: [dec])
Explanation The ST16550 UART driver has been unable to attach to 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-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-OVERRUN_ERROR Character overrun detected
Explanation The ST16550 UART driver detected a character overrun condition.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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-STACKSIZE_ERROR Unable to set stack size for the interrupt handler.
Explanation The ST16550 UART driver was unable to set the stack size 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-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.
STATSD Messages
Error Message%MGBL-STATSD-2-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-2-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-ERROR [chars]
Explanation A stats error occured prior to debug service initialization
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-STATSD-3-GSP Group error: [chars]: [chars]
Explanation This process failed to perform some GSP related operation.
Recommended Action This message is likely to mean that a periodic stats update has been lost. This probably indicates a failure in the underlying transport mechanism. Copy the error message exactly as it appears on 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-INIT Init failure: [chars]: [chars]
Explanation This process failed during initialisation.
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-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-2-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-2-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-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-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 [hex] is, expected [hex]
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-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-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-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 [dec] 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 Copy the error message exactly as it appears on 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.
Recommended Action Copy the error message exactly as 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-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 whilst 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-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-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 [dec] 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_ARGUMENT Unexpected argument: '[chars]' in command line
Explanation The TTY Management Commands Process has been given invalid command line arguments. Usage: tty_mgmt_terminal_cmds -f -a [ -i | -s | -p ] -v [ [] [...]]
Recommended Action Copy the error message exactly as it appears on 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_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_NO_VALUE No value provided.
Explanation No value 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-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-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-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-CHKPT_DELETE Failed to delete checkpointed process: '[chars]'
Explanation The TTY Server attempted to deleted the checkpointed PID of a spawned process but 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-CHKPT_ITEM Failed to checkpoint process: '[chars]'
Explanation The TTY Server attempted to checkpoint the PID of a spawned process but 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-CHKPT_REGISTRATION Failed to register with the checkpoint API: '[chars]'
Explanation The TTY Server attempted to register with the checkpoint API 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_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.
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-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-3-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-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-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.
XML_TTY_CLNT Messages
Error Message%MGBL-XML_TTY_CLNT-3-COMMS XML TTY Agent communication problem: [chars]. Error: [chars]
Explanation The XML TTY Agent encountered a problem when setting up a communication channel or when sending or receiving a message. This may be due to a problem with the communications transport, or it may help to restart the XML TTY Agent.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_CLNT-3-EVENT An error was returned from the communications infrastructure. [chars]. Error: [chars]
Explanation The XML TTY Agent encountered a problem when setting up a communications infrastructure. This may be due to a problem with the communications transport, or it may help to restart the XML TTY Agent.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_CLNT-3-INTERNAL [chars]
Explanation The XML TTY Agent has encountered an internal problem. The operation that was requested will not be carried out. It may be necessary to restart the XML TTY Agent.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_CLNT-3-INTERNAL_NULL The XML TTY Agent client encountered an unexpected problem (unexpected NULL pointer)
Explanation The XML TTY Agent has encountered an internal problem. The operation that was requested will not be carried out. It may be necessary to restart the XML TTY Agent.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_CLNT-3-TTY [chars]. Error: [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, or it may help to restart the XML TTY Agent.
Recommended Action If the message recurs, copy the error message exactly as 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_CMN Messages
Error Message%MGBL-XML_TTY_CMN-3-DEBUG The XML TTY Agent was unable to register or unregister with the debugging infrastructure. Error : [chars]
Explanation There is a problem with the system infrastructure - perhaps the communication infrastructure has not yet stabilised. The XML TTY Agent will continue to operate, but debugging may not be available for it.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-XML_TTY_CMN-3-INTERNAL The XML TTY Agent has encountered an internal error: [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 If the message recurs, copy the error message exactly as it appears on 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_CMN-3-INTERNAL_NULL The XML TTY Agent has passed itself an invalid parameter
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 If the message recurs, copy the error message exactly as it appears on 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_CMN-3-MEMORY Could not complete operation due to lack of memory: could not allocate [unsigned int] bytes
Explanation The system is running out of memory and the XML TTY Agent was not able to allocate sufficient memory to carry out an operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
XML_TTY_SVR Messages
Error Message%MGBL-XML_TTY_SVR-3-COMMS XML TTY Agent communication problem: [chars]. Error: [chars]
Explanation The XML TTY Agent encountered a problem when setting up a communication channel or when receiving a message. This may be due to a problem with the communications transport, or it may help to restart the XML TTY Agent.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_SVR-3-INITERROR XML TTY Agent failed to initialise: [chars] ([chars])
Explanation The XML TTY Agent encountered an error during its initialisation. The Agent will restart.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-XML_TTY_SVR-3-INTERNAL [chars]
Explanation The XML TTY Agent has encountered an internal problem. The operation that was requested will not be carried out. It may be necessary to restart the XML TTY Agent.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_SVR-3-INTERNAL_NULL The XML TTY Agent encountered an unexpected problem (unexpected NULL pointer)
Explanation The XML TTY Agent has encountered an internal problem. The operation that was requested will not be carried out. It may be necessary to restart the XML TTY Agent.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_SVR-3-LOCKING An unexpected error was encounted when the XML TTY Agent attempted to [chars] [chars]. Error: [chars]
Explanation The XML TTY Agent has failed to make a kernel call. As a result the XML request has not been completed.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_SVR-3-REDUNDANCY [chars]. Error: [chars]
Explanation The XML TTY Agent encountered a problem preparing for a failover scenario. The Agent may not recover correctly if a failover occurs. It may help to restart the Agent.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_SVR-3-REDUNDANCY_STATE The System Manager process passed an unrecognised node state ([hex]) to the XML TTY Agent
Explanation The XML TTY Agent encountered a problem preparing for or during a failover scenario. The Agent may not recover correctly if a failover occurs. It may help to restart the Agent.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_SVR-3-SEMAPHORE An unexpected error was encounted when the XML TTY Agent attempted to [chars] a semaphore. Error: [chars]
Explanation The XML TTY Agent has failed to make a kernel call. As a result the XML request has not been completed.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_SVR-3-SHUTDOWNERROR XML TTY Agent error during shutdown: [chars] ([chars])
Explanation The XML TTY Agent encountered an error during its shutdown process. The Agent will shut down anyway.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_SVR-3-SYSDB An invalid parameter was passed to the XML TTY Agent by the system database
Explanation An invalid parameter was passed to the XML TTY Agent during a management data request. The management data which was being requested by a user will not be able to be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-XML_TTY_SVR-3-VERSION Different versions of the XML TTY Agent server and client are in use - one will have to be upgraded if they are to be able to communicate. Client version [dec], Server version [dec]
Explanation The XML TTY Agent client and server have incompatible versions - the older one will have to be upgraded.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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_SVR-3-XMLINFRA An invalid parameter was passed to the XML TTY Agent by the XML infrastructure
Explanation An invalid parameter was passed to the XML TTY Agent during a management data request. The management data which was being requested by a user will not be able to be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%MGBL-XML_TTY_SVR-6-COMMS_SEND XML TTY Agent message communication problem: [chars]. Warning: [chars]
Explanation The XML TTY Agent encountered a problem when sending an asynchronous event or a synchronous reply. This may be a result of the client no longer being there to receive the 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.
XML Messages
Error Message%MGBL-XML-3-DEBUG_INIT_FAIL The XML Parser Library was unable to register or unregister with the debugging infrastructure. Error : [chars]
Explanation There is a problem with the system infrastructure - perhaps the communication infrastructure has not yet stabilised.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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-3-LTRACE_INIT_FAIL The XML Parser Library was unable to register or unregister with the ltrace infrastructure. Error : [chars]
Explanation There is a problem with the system infrastructure - perhaps the communication infrastructure has not yet stabilised.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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-4-CERR_REG_FAIL The XML Parser Library was unable to register its error messages with the cerrno infrastructure. Error : [chars]
Explanation There is a problem with the system infrastructure - perhaps the communications infrastructure has not yet stabilised. Note that the inability to register is not a fatal error, and the XML Parser will continue to operate as normal, but any errors returned by the XML Parser will not appear as decoded error strings.
Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered
