Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.4
Manageability (MGBL) Messages
Downloads: This chapterpdf (PDF - 389.0KB) The complete bookPDF (PDF - 1.84MB) | Feedback

Manageability (MGBL) Messages

Table Of Contents

Manageability (MGBL) Messages

RS232 Messages

S2681 Messages

SCHEMA Messages

SCONBKUP Messages

ST16550 Messages

STATSD Messages

SYS Messages


Manageability (MGBL) Messages


This section contains all Management Plane and Manageability related System Error Messages, including config, cli, sml, pm, and so forth. The following facility codes are represented in this module:

RS232 Messages

S2681 Messages

SCHEMA Messages

SCONBKUP Messages

ST16550 Messages

STATSD Messages

SYS Messages

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-TTY_NOT_REGISTERED The TTY is not registered with the TTY Server

Explanation    The RS232 DLL tried to perform an operation on a TTY that isn't registered with the TTY Server.

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

Error Message     
 
    
    
   

%MGBL-RS232-4-API_LOCATE_ERROR Unable to find the desired details in a loaded DLL

Explanation    The RS232 DLL was unable find the details required from a DLL it had loaded.

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

Error Message     
 
    
    
   

%MGBL-RS232-4-DLL_OPEN_ERROR The RS232 DLL was unable to open a DLL (errno: [dec])

Explanation    The RS232 DLL was unable to open a DLL.

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

Error Message     
 
    
    
   

%MGBL-RS232-4-MAPPING_ERROR The RS232 DLL was unable map from a TTY ID to a UART port

Explanation    The RS232 DLL was unable map from a TTY ID to a UART port

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

Error Message     
 
    
    
   

%MGBL-RS232-4-MEM_ALLOC_ERROR Unable to allocate memory for TTY structures

Explanation    The RS232 DLL was unable allocate the necessary memory it required to hold details about the TTYs.

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

Error Message     
 
    
    
   

%MGBL-RS232-4-NO_PACKET_MODE Packet mode sessions are not yet supported on RS232 TTYs

Explanation    The TTY Server informed the RS232 DLL about a packet mode session, but we don't yet support packet mode.

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

Error Message     
 
    
    
   

%MGBL-RS232-4-PDP_SET_ERROR The RS232 DLL was unable to set the persistant data path

Explanation    The RS232 DLL has failed to enable the persistant data path for a TTY.

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

Error Message     
 
    
    
   

%MGBL-RS232-4-SESSION_SETUP_ERROR The RS232 DLL was unable to setup a session on a TTY

Explanation    The RS232 DLL has been unable to setup a session on a TTY

Recommended Action    Try performing a 'clear line' on the relevent TTY.

Error Message     
 
    
    
   

%MGBL-RS232-4-TEMPLATE_APPLY_ERROR The RS232 DLL encountered an error trying to apply a template.

Explanation    The RS232 DLL tried to apply a template to a TTY but failed.

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

Error Message     
 
    
    
   

%MGBL-RS232-4-TEMPLATE_DEAPPLY_ERROR The RS232 DLL encountered an error trying to deapply a template.

Explanation    The RS232 DLL tried to deapply a template to a TTY but failed.

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

S2681 Messages

Error Message     
 
    
    
   

%MGBL-S2681-3-COND_SIGNAL_ERROR Unable to signal on the status variable

Explanation    The S2681 UART driver was unable to signal that that status variable was ready to be read.

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

Error Message     
 
    
    
   

%MGBL-S2681-3-INTERRUPT_UNMASK_ERROR Unable to unmask UART interrupt (error: [dec])

Explanation    The S2681 UART driver has been unable to unmask the UART interrupt.

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

Error Message     
 
    
    
   

%MGBL-S2681-3-IO_PERM_ERROR Unable to obtain permission to access UART (error: [dec])

Explanation    The S2681 UART driver has been unable to gain the required permissions to access the UART.

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

Error Message     
 
    
    
   

%MGBL-S2681-3-MUTEX_LOCK_ERROR Unable to lock the UART (error: [dec])

Explanation    The S2681 UART driver has been unable to lock access to the UART.

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

Error Message     
 
    
    
   

%MGBL-S2681-3-MUTEX_UNLOCK_ERROR Unable to unlock the UART (error: [dec])

Explanation    The S2681 UART driver has been unable to unlock access to the UART.

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

Error Message     
 
    
    
   

%MGBL-S2681-3-SCHED_PRIORITY_ERROR Unable to raise the priority of the interrupt handler

Explanation    The S2681 UART driver was unable to raise the priority of the interrupt handler.

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

Error Message     
 
    
    
   

%MGBL-S2681-3-SCHEDPARAM_ERROR Unable to set the parameters for the interrupt handler

Explanation    The S2681 UART driver was unable to set the parameters of the interrupt handler.

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

Error Message     
 
    
    
   

%MGBL-S2681-3-SCHEDPOLICY_ERROR Unable to set scheduling policy for the interrupt handler.

Explanation    The S2681 UART driver was unable to set the scheduling policy for the interrupt handler.

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

Error Message     
 
    
    
   

%MGBL-S2681-3-STATUS_MUTEX_LOCK_ERROR Unable to lock the status variable.

Explanation    The S2681 UART driver was unable to lock the status variable for the interrupt thread.

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

Error Message     
 
    
    
   

%MGBL-S2681-3-STATUS_MUTEX_UNLOCK_ERROR Unable to unlock the status variable.

Explanation    The S2681 UART driver was unable to unlock the status variable for the interrupt thread.

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

Error Message     
 
    
    
   

%MGBL-S2681-3-THREAD_CREATE_ERROR Unable to create the interrupt handler thread.

Explanation    The S2681 UART driver was unable to create a thread for the interrupt handler.

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

SCHEMA Messages

Error Message     
 
    
    
   

%MGBL-SCHEMA-6-VERSIONCHANGE A schema version change has occurred due to the [chars] of schema file '[chars]'. Any management applications which use the schema may wish to update to the appropriate schema version.

Explanation    The version of some part(s) of the schema which are running on the router have changed - this is an informational message to let any users of the schema know of the change.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%MGBL-SCHEMA-7-INTERNAL The schema infrastructure has encountered an error. [chars]

Explanation    An internal error has occurred in the schema server or library. Some management functions may not operate correctly.

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

SCONBKUP Messages

Error Message     
 
    
    
   

%ASCIICFG-SCONBKUP-3-INTERNAL_FATAL [chars] [dec]: [chars]

Explanation    Restarting the process as it is not in a recoverable state.

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

Error Message     
 
    
    
   

%ASCIICFG-SCONBKUP-7-INTERNAL_ERR [chars] [dec]: [chars]

Error Message    Error encountered while Backing up the ASCII System Configuration. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. 

ST16550 Messages

Error Message     
 
    
    
   

%MGBL-ST16550-3-INTERRUPT_UNMASK_ERROR Unable to unmask UART interrupt (error: [dec])

Explanation    The ST16550 UART driver has been unable to unmask the UART interrupt.

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

Error Message     
 
    
    
   

%MGBL-ST16550-3-IO_PERM_ERROR Unable to obtain permission to access UART (error: [dec])

Explanation    The ST16550 UART driver has been unable to gain the required permissions to access the UART.

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

Error Message     
 
    
    
   

%MGBL-ST16550-3-MUTEX_LOCK_ERROR Unable to lock the UART (error: [dec])

Explanation    The ST16550 UART driver has been unable to lock access to the UART.

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

Error Message     
 
    
    
   

%MGBL-ST16550-3-MUTEX_UNLOCK_ERROR Unable to unlock the UART (error: [dec])

Explanation    The ST16550 UART driver has been unable to unlock access to the UART.

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

Error Message     
 
    
    
   

%MGBL-ST16550-3-SCHED_PRIORITY_ERROR Unable to raise the priority of the interrupt handler

Explanation    The ST16550 UART driver was unable to raise the priority of the interrupt handler.

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

Error Message     
 
    
    
   

%MGBL-ST16550-3-SCHEDPARAM_ERROR Unable to set the parameters for the interrupt handler

Explanation    The ST16550 UART driver was unable to set the parameters of the interrupt handler.

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

Error Message     
 
    
    
   

%MGBL-ST16550-3-SCHEDPOLICY_ERROR Unable to set scheduling policy for the interrupt handler.

Explanation    The ST16550 UART driver was unable to set the scheduling policy for the interrupt handler.

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

Error Message     
 
    
    
   

%MGBL-ST16550-3-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-3-EVENT_BLOCK An error occurred while handling an event: [chars]

Explanation    The event handling function returned an error which could not be handled

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

Error Message     
 
    
    
   

%MGBL-STATSD-3-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-REGISTRATION_FAILED Registration of a stats collector failed - [chars]

Explanation    Registration of a stats collector with stats server failed.

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

Error Message     
 
    
    
   

%MGBL-STATSD-3-SHMEM_CORRUPTED Stats shared memory window has become corrupted. [chars]

Explanation    In certain unlikely scenarios it is possible that during a process restart the shared memory region used by the stats infrastructure can become corrupted. In most cases this will automatically be recovered from, however there is a possibility that the system will not be able to recover from this - The specific instance of the message will indicate which of these cases has arisen. If the system is unable to restart all necessary processes then multiple process crashes/blockages may be observed. In either case, reported statistics may be reset or inaccurate.

Recommended Action    In the recovery case, processes should restart automatically and the system should recover so no user intervention should be required. If we are unable to automatically recover, then either the node should be reloaded, or support contacted.

Error Message     
 
    
    
   

%MGBL-STATSD-3-SHMEM_LOCK Failed to lock shared memory mutex: [chars]

Explanation    A failure occurred when attempting to acquire a shared memory lock

Recommended Action    This message probably indicates an error elsewhere in the system as some other process must be holding the lock. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

SYS Messages

Error Message     
 
    
    
   

%MGBL-SYS-3-ALREADY_THREADED_MSG [chars]: Attempt to re-add a node to a tree

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-COMPARE_ALREADY_SET [chars]: Compare already set for thread : [dec]

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-FTRUNCATE ftruncate of [chars] at failed because [chars]

Explanation    The packet subsystem was not able to initialize memory.

Recommended Action    The router will not start properly with this condition.
' 'Call your technical support representative for assistance.

Error Message     
 
    
    
   

%MGBL-SYS-3-ILLEGAL_THREAD [chars]: Illegal thread for this wavl : [dec]

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-MALLOCFAIL Memory allocation of [dec] bytes failed from [hex], pool [chars], alignment [dec]

Explanation    The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router's memory.

Recommended Action    Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message     
 
    
    
   

%MGBL-SYS-3-MMAPFAIL mmap of [chars] at failed; errno ([dec]) [chars]

Explanation    The packet subsystem was not able to initialize memory.

Recommended Action    The router will not start properly with this condition.
' 'Call your technical support representative for assistance.

Error Message     
 
    
    
   

%MGBL-SYS-3-MMAPSHIFT mmap of [chars] at failed, returned address [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-NOMEMORY No memory available for [chars] [dec]

Explanation    An operation could not be accomplished because of a low-memory condition.

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

Error Message     
 
    
    
   

%MGBL-SYS-3-NOT_THREADED_MSG [chars]: Attempt to remove an unthreaded node from a tree

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-NULL_HANDLE_MSG [chars]: Received a NULL handle

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-NULLREG NULL registry

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-REG_UNKNOWN_TYPE Unknown registry type ([dec])

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-RN_ASC_DESC Tried to ascend in descend loop

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-RN_DELINK_INODE Attempt to delink inode with 2 decendents [pointer] ([dec], [hex], [pointer], [pointer])

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-RN_NDESC Node [pointer] ([dec]) has no descendents ([hex])

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-RN_PRNT_LINK Parent not linked to inode ([pointer], [pointer], [pointer], [pointer])

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-RN_VPARENT Unable to find virtual node parent for [pointer] ([dec], [hex], [pointer], [pointer])

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-ROOT_ALREADY_SET [chars]: Root already set for thread : [dec]

Explanation    --

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

Error Message     
 
    
    
   

%MGBL-SYS-3-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. Copy the message exactly as it appears, and report it your technical support representative.