-
Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.3
-
Overview
-
Preface
-
Diagnostic Messages
-
Driver Messages
-
Fabric Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 2 (L2) Messages
-
Media Messages
-
Manageability (MGBL) Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service (QOS) Messages
-
Routing Messages
-
Feedback
Table Of Contents
Fabric Messages
This section contains all Fabric (hardware and software both) related System Error Messages. The following facility codes are represented in this module:
FAB_SVR Messages
Error Message%FABRIC-FAB_SVR-7-ERR_ASIC_INIT Failed to initialize the the CPU control ASIC interface to [chars]: [chars]. Exiting...
Explanation Fabric server encountered an error while initializing the CPU control ASIC to either receive packets from the fabricq ASIC or transmit packets from the ingressq ASIC. This is crucial for the process and is automatically restarted on this failure.
Recommended Action If problem either persists (following a process restart) then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FAB_SVR-7-ERR_EVM_CREATE Failed to create the event manager. Reason: [chars]. Exiting...
Explanation Fabric server encountered an error while attempting to create an event manager. This failures affects the ability of the process to service various messages / pulses from other threads / processes. This facility is deemed crucial and the process automatically restarts on this failure. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_INIT [chars] during the initialization. Reason: [chars]. Exiting...
Explanation Fabric server encountered the specified error during the initialization sequence. This facility is deemed crucial and hence the process is automatically restarted on this failure. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_THREAD_ATTRIBUTE Failed to set the thread attribute: [chars]. Exiting...
Explanation Fabric server encountered an error while setting the thread attribute during the process initialization sequence. This is crucial for the process and is automatically restarted on this failure.
Recommended Action If the problem is experienced only by this process in the system, restart the fabric server process by executing the following command at the CLI of the active RP: process restart fab_svr location If problem either persists (following a process restart) or also noticed on other processes then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FAB_SVR-7-ERR_THREAD_MUTEX_INIT Failed to initialize a mutex for client with ID [dec]: [chars]. Exiting...
Explanation Fabric server encountered an error while creating a mutex for use by a client with the specified ID. This is crucial for the process and is automatically restarted on this failure.
Recommended Action If the problem is experienced only by this process in the system, restart the fabric server process by executing the following command at the CLI of the active RP: process restart fab_svr location If problem either persists (following a process restart) or also noticed on other processes then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FABRIC_DRVR Messages
Error Message%FABRIC-FABRIC_DRVR-2-ASIC_INITIALIZED Fabric ASICs initialized
Explanation This indicates Fabric ASICs are initialized and is expected during normal operation.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-2-ERR_CHASSIS_TYPE A non-recoverable error occured during fabric driver initialization - [chars]; exiting...
Explanation Fabric driver failed to get the chassis type information during driver initialization. This is a non recoverable error. This indicates a problem with the back plane EEPROM. Verify that the Back plane EEPROM is okay and programmed correctly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_DRV_INIT Initialization of fabric driver failed: [chars] ; exiting...
Explanation Fabric driver encountered the annunciated error during the driver initialization. The System Manager process (sysmgr) will automatically respawn the (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_EVM_CREATE Failed to create event manager for '[chars]'
Explanation The Fabric driver was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_PLD_REV Fabric Driver encountered an error due to having older version of PLD image.
Explanation This indicates that an error occured in the fabric board due to having older version of PLD image. Verify that the PLD image rev is 0x1c or above and update the image.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_POD_INIT Failed to [chars] POD (node: [hex], module: [hex], asic: [unsigned int], POD:[unsigned int]) - error : [chars]; exiting...
Explanation Fabric Driver failed to initialize one of the POD hardware modules. The System Manager process (sysmgr) will automatically respawn the (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_THREAD_ATTRIBUTE FABRIC driver failed to change interupt thread to an IO thread: [chars]
Explanation The Fabric driver was unable to change the interrupt thread to an IO thread. Because of this failure, the interupt thread will not be able to receive the interupt thread events. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERRRATE_EXCEED_GLACIAL [chars] ; Node Key = [hex]
Explanation The Fabric driver encountered the annunciated error. For Error Node Keys - 0x1050016; 0x1050018; 0x105001A : This indicates a hardware problem in Fabric ASIC. Sysmgr will reload the node up to a fixed number of times the error is encountered, to recover. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERRRATE_EXCEED_NO_LIMIT [chars]
Explanation The fabric driver encountered the annunciated error. Sysmgr will reload the node up to a fixed number of times the error is encountered, to recover. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERRRATE_EXCEED_SLOW [chars]
Explanation The fabric driver encountered the annunciated error. Sysmgr will reload the node up to a fixed number of times the error is encountered, to recover. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-4-ERR_ECM_CREATE Failed to create Event Connection Manager : [chars]
Explanation The Fabric driver was unable to create an event connection manager for EDM. Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-4-ERR_ECM_NOTIFY Failed to register with ECM to receive notifications : [chars]
Explanation The Fabric driver was unable register with ECM to receive notifications when the connection to Sysdb goes down/up/closed. Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-4-ERR_LTRACE_INIT Fabric driver failed to initialize the ltrace - rc = [chars]
Explanation The Fabric driver could not open/initialize the ltrace buffer. The Fabric driver and the system should stll function as normal, with the exception that ltrace will not be available for sfe_drvr process.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-6-FAB_MODULE [chars]
Explanation This is to give infomation regarding fabric module type.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_BAG_REG [chars]
Explanation The Fabric driver was unable to register Fabric driver bags. The Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_BP_CFG [chars]: Error in Back pressure configuration, BP Groups : [dec], [dec], [dec]
Explanation The Fabric driver encountered an error in back pressure configuration. This indicates BP configuration received from the fabric control software is incorrect. If this condition prevails, it could impact data traffic when fabric gets congested.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_DEBUG_INIT Fabric driver failed to initialize the debug; rc = [chars]
Explanation The Fabric driver was unable to initialize debug. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_DEBUG_REG Fabric driver failed to register with the debug; rc = [chars]
Explanation The Fabric driver was unable to register with the debug. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_INTERNAL_SW [chars]
Explanation The Fabric driver encountered the annunciated internal SW error. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_LINK_TOPO Topology mismatch for [chars]
Explanation The upstream information received from idle cells on this link does not match with FSDB information.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_SYSDB_EDM_REG [chars]
Explanation The Fabric driver was unable to become an external data manager (EDM) despite having a connection to SysDB. The operation will be retried. The Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERRRATE_EXCEED_DEBUG [chars]
Explanation The fabric driver encountered the annunciated error. The Fabric driver and the System should still continue to function as normal.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-7-LINK_SHUT_DOWN Fabric Link: [chars] - Shutdown: [chars]
Explanation The Fabric driver encountered an error on the annunciated Fabric Switching Element link and the link is brought down.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FDI Messages
Error Message%FABRIC-FDI-2-ERR_CONNECTION [chars]; Conn_id = [dec] Conn_name = [chars]
Explanation The FDI library encountered the annunciated connection error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-2-ERR_INTERNAL_SW [chars] ; rc = [chars]
Explanation The FDI encountered the annunciated internal sw error.
Recommended Action No action is required.
Error Message%FABRIC-FDI-3-ERR_BUFF_Q FDI Buffers are full; Conn_id [dec]. Data_Size [dec]. Buffer_states ([dec] [dec])
Explanation FDI buffers are full and FDI can't buffer any more messages. The System Manager process (sysmgr) will automatically respawn the process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action Examine the state of GSP on the node of the FDI application. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-3-ERR_MSG_TYPE FDI received incorrect message type - [dec]
Explanation FDI received incorrect message type and failed to process the message. The System Manager process (sysmgr) will automatically respawn the process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_DEBUG_CLEAN FDI library failed to cleanup FDI debug info in debug infrastructure ; rc = [chars]
Explanation The FDI library was unable to cleanup FDI debug info in debug infrastructure. The System should still continue to function as normal.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_DEBUG_INIT FDI library failed to initialize debug for fdi - [chars]; rc = [chars]
Explanation The FDI library was unable to initialize debug. The FDI component and the System should still continue to function as normal, with the exception that the debugs will not be available for FDI.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_DEBUG_REG FDI library failed to register with debug infrastructure ; rc = [chars]
Explanation The FDI library was unable to register with debug infrastructure. The FDI component and the System should still continue to function as normal, with the exception that the debugs will not be available for FDI.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_EDM_INIT [chars]; rc = [chars]
Explanation The FDI Library encountered the annunciated EDM Initialization error. The System should still continue to function as normal, with the exception that the 'show' commands for FDI will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_MEM_ALLOC FDI failed to allocate [dec] bytes
Explanation The FDI was unable to allocate memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
FGID_AGG Messages
Error Message%FABRIC-FGID_AGG-3-ERR_DEBUG_INIT fgid_aggregator unable to initialize dbg ; rc = [chars]
Explanation The FGID Aggregator was unable to initialize debug. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_EVM_CREATE FGID Aggregator failed to create [chars] evm ; rc = [chars]
Explanation The FGID aggregator was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_EVM_SYNC_ATTACH FGID Aggregator failed to attach [chars] to evm ; rc = [chars]
Explanation The FGID Aggregator was unable to attach the indicated event handler to the event manager. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_GSP [chars]: rc = [chars]
Explanation The FGID Aggregator was unable to create/join GSP group. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_INTERNAL_SW [chars]; [chars]
Explanation The FGID Aggregator encountered the annunciated SW error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_MEM_ALLOC FGID Aggregator unable to allocate [dec] bytes
Explanation The FGID Aggregator was unable to allocate memory. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_SYSMGR [chars]; rc = [chars]
Explanation The FGID Aggregator encountered the annunciated sysmgr error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-7-ERR_LTRACE_INIT FGID Aggregator failed to initialize the ltrace file [chars] : [chars]
Explanation The FGID Aggregator Could not open the annunciated ltrace buffer. The FGID component and the system should stll function as normal, with the exception that ltrace will not be available for fgid_aggregator process.
Recommended Action No action is required.
FGID_ALLOC Messages
Error Message%FABRIC-FGID_ALLOC-3-ERR_EVM_CREATE FGID Allocator failed to create [chars] evm; rc = [chars]
Explanation The FGID allocator was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_GSP [chars]: rc = [chars]
Explanation The FGID Allocator encountered the annunciated GSP error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_INTERNAL_SW [chars] ; rc = [chars]
Explanation The FGID Allocator encountered the annunciated internal SW error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_MEM_ALLOC FGID Allocator failed to allocate [dec] bytes
Explanation The FGID Allocator was unable to allocate memory. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_SYSMGR [chars]; rc = [chars]
Explanation The FGID Allocator encountered the annunciated sysmgr error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_BAG_REG FGID allocator failed to register FGID bags; rc = [chars]
Explanation The FGID allocator was unable to register FGID bags. The FGID component and the System should continue to function as normal, with the exception that the 'show' commands for FGID allocator will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_CHKPT_INIT FGID Allocator failed to initialize the checkpoint library ; rc = [chars]
Explanation The FGID Allocator was unable to initialize the checkpoint library. The fgid_allocator 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%FABRIC-FGID_ALLOC-7-ERR_CHKPT_ITERATE_START FGID Allocator failed to start to iterate Checkpoint table [chars]; rc = [chars]
Explanation The FGID Allocator was unable to start to iterate checkpoint table. The fgid_allocator 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%FABRIC-FGID_ALLOC-7-ERR_CHKPT_REG FGID Allocator failed to register the Checkpoint table [chars] ; rc = [chars]
Explanation The FGID Allocator was unable to register the checkpoint table. The fgid_allocator 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%FABRIC-FGID_ALLOC-7-ERR_DEBUG_INIT FGID Allocator failed to initialize debug ; rc = [chars]
Explanation The FGID Allocator failed to initialize debug. The FGID component and the System should still continue to function as normal, with the exception that the debugs will not be available fgid_allocator 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%FABRIC-FGID_ALLOC-7-ERR_LTRACE_INIT FGID Allocator failed to initialize the ltrace file [chars]; rc = [chars]
Explanation The FGID Allocator could not open the annunciated ltrace buffer. The FGID component and the system should function as normal, with the exception that ltrace will not be available for fgid_aggregator process.
Recommended Action No action is required.
Error Message%FABRIC-FGID_ALLOC-7-ERR_SYSDB_BIND FGID Allocator failed to bind to Sysdb name space [chars]; rc = [chars]
Explanation The FGID-DB allocator unable to bind to sysdb name space. The fgid_allocator 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%FABRIC-FGID_ALLOC-7-ERR_SYSDB_EDM_REG FGID allocator failed to perform EDM registration; rc = [chars]
Explanation The FGID allocator was unable to become an external data manager (EDM) despite having a connection to SysDB. The operation will be retried. The FGID component and the System should continue to function as normal, with the exception that the 'show' commands for FGID allocator will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FGID_BCDL_CONSUMER Messages
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_BCDL [chars] ; rc = [chars]
Explanation The BCDL Consumer process has encountered the annunciated BCDL error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_BOARD_TYPE FGID BCDL Consumer failed to get hardware board type: rc = [chars]
Explanation The FGID BCDL Consumer was unable to get the board type.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_DEBUG_INIT The FGID BCDL Consumer Failed to initialize debug; rc = [chars]
Explanation The FGID BCDL Consumer was unable to initialize debug. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_EVM [chars] : [chars]
Explanation The FGID BCDL consumer encountered the annunciated Event Manager Error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_FDI_CLIENT_REG Unable to perform FDI client registration; rc = [chars]
Explanation The FGID BCDL Consumer was unable to register with the FDI client. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_FGID_DOWNLOAD_DONE_NOTIF FGID BCDL Consumer failed to notify SFE driver about FGID download complete; rc = [chars]
Explanation The FGID BCDL Consumer encountered an error while notifying the SFE driver about FGID download completion. This indicates a problem with communication between SFE_DRVR and FGID BCDL consumer. Restart SFE driver manually.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_FGID_SET FGID BCDL Consumer failed to set FGID [chars] bitmap; rc = [chars]
Explanation The FGID BCDL Consumer encountered an error while setting S2 or S3 bitmap. This indicates a problem with the communication between the SFE driver and the FGID BCDL consumer. The FGID BCDL consumer and/or SEA driver 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%FABRIC-FGID_BCDL_CONSUMER-3-ERR_RACK_NUM FGID BCDL Consumer failed to get the rack value; rc = [chars]
Explanation The FGID BCDL Consumer encountered an error while retrieving the rack value from nodeid. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_USAGE Invalid argument. USAGE: [chars]
Explanation The FGID BCDL consumer process was invoked with an unknown argument. The BCDL Consumer process was started with an invalid parameter. This is not an expected field event and details about software versions and the .startup file should be returned to engineering.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-7-ERR_LTRACE_INIT FGID BCDL Consumer failed to initialize the ltrace file [chars] : rc = [chars]
Explanation The FGID BCDL Consumer could not open the annunciated ltrace buffer. The FGID component and the system should function as normal, with the exception that ltrace will not be available for FGID BCDL Consumer process.
Recommended Action No action is required.
FGID_LIB Messages
Error Message%FABRIC-FGID_LIB-7-ERR_DEBUG_INIT FGID library failed to initialize the debug ; rc = [chars].
Explanation The FGID library failed to initialize debug. The FGID component and the system should still function as normal, with the exception that the debugs will not be available for FGID 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%FABRIC-FGID_LIB-7-ERR_LTRACE_INIT FGID library failed to initialize the ltrace ; rc = [chars].
Explanation The FGID library failed to initialize ltrace. The FGID component and the system should still function as normal, with the exception that the ltrace will not be available for FGID 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.
FGID_SVR Messages
Error Message%FABRIC-FGID_SVR-3-ERR_BCDL [chars]; rc = [chars]
Explanation The FGID Server encountered the annunciated BCDL error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_DSC Failed to register for DSC notification; rc = [chars]
Explanation The FGID Server encountered DSC error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_EVM_CREATE FGID Server failed to create [chars] evm; rc = [chars]
Explanation The FGID Server was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_EVM_SYNC_ATTACH FGID Server failed to attach [chars] evm; rc = [chars]
Explanation The FGID Server was unable to attach the indicated event handler to the event manager. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_GSP [chars] ; rc = [chars]
Explanation The FGID-DB server encountered the annunciated GSP error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_INTERNAL_SW [chars]; [chars]
Explanation The FGID Server encountered the annunciated SW error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_MEM_ALLOC FGID Server unable to allocate [dec] bytes
Explanation The FGID Server was unable to allocate memory. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_USAGE FGID Server : Server Id requested [chars] is not a allowed server_id
Explanation Incorrect command line parameters were passed to the FGID Server, and so it failed to start.
Recommended Action Check the startup arguments passed to FGID-DB. A default configuration will be used if no parameters are passed. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-7-ERR_LTRACE_INIT FGID Server failed to initiaize the ltrace file [chars]; rc = [chars]
Explanation The FGID Server Could not open the annunciated ltrace buffer. The FGID component and the system should function as normal, with the exception that ltrace will not be available for fgid_server process.
Recommended Action No action is required.
Error Message%FABRIC-FGID_SVR-7-ERR_SYSMGR [chars] ; rc = [chars]
Explanation The FGID-DB server failed in sysmgr 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.
FSDB Messages
Error Message%FABRIC-FSDB-1-ERR_PLANE_CONFIG Fabric hardware found at location [chars] is inconsistent with current configured values : [chars]
Explanation The fabric plane configuration for this multi-chassis system cannot be implemented with the hardware that has been discovered. This error may cause one or more fabric planes to stay down which will affect the bringup of the rest of the system. Possible causes could be incorrect admin plane configuration (ie the configuration states that slot 1 is the first card in a plane whereas slot 0 really is) or an incorrectly sized fiber module is inserted in a slot.
Recommended Action Check the admin plane configuration to ensure that it corresponds with the actual physical topology of the system. If this configuration looks correct then contact support, otherwise correct the configuration and the system should recover.
Error Message%FABRIC-FSDB-1-PLANE_UPDOWN Plane [dec] state changed to [chars]%s; [chars]
Explanation If the plane is reported down other than when administratively brought down, it means that the sprayer cannot reach *any* destination on the plane. This a symptom of too many other fabric errors (DESTINATION_UPDOWN) than an error itself. The plane can no longer be used to send any traffic.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-2-ERR_CONTROL_MSG Rack [dec] sent illegal fabric control message - [chars]
Explanation Fabric control software running in another rack has notified a status change that is impossible or illegal.
Recommended Action This error can be caused by an attempt to use the router with in a fabric configuration that is not supported. For example, there may be three or more linecard racks that have dual-rack fabric cards installed. Ensure that the correct racks are installed in the router and that software displays the correct rack numbers and rack types for each rack. Ensure that the software fabric configuration is correct. If these steps do not find an error, restart fabric control software on the rack that produced this message, and on the rack sending the illegal message. 'admin process restart fsdb_server loc '. As restart process is disruptive, save output of all the commands mentioned in required_info before restarting the process. If problem persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ASERVER_DOWNLOAD Fabric configuration download [chars]: [chars]
Explanation Fabric control software failed to synchronize configuration details between the fsdb_server and fsdb_aserver processes. If the affected rack is being added to the system it cannot be brought into service. If the affected rack is already in service, then it cannot respond to fabric failures or changes.
Recommended Action No action is necessary. If condition persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_CHKPT Failed to register checkpoint record: [chars]. Exiting...
Explanation FSDB server encountered an error while updating or accessing its checkpoint information. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger respective RP/SC switchover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_CHKPT_INIT Failed to initialize check point library: [chars]. Exiting...
Explanation FSDB was unable to setup the checkpointing facility to offer high availability functionality. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger respective RP/SC switchover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_DEBUG Failed to setup the debugging services: [chars]. Exiting...
Explanation FSDB was unable to initialize the debugging services. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger respective RP/SC switchover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_DSC FSDB Server: DSC Error [[chars]]: [chars]
Explanation Fabric Status Database server (FSDB) failed to communicate with the DSC server. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger respective RP/SC switchover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_ECM_CREATE Failed to create the event connection manager for [chars]: [chars]. Exiting...
Explanation FSDB encountered an error while attempting to create an event connection manager for the specified path. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger respective RP/SC switchover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_ECM_NOTIFY Failed to install ECM notification hanlder for [chars] path: [chars]. Exiting...
Explanation FSDB encountered an error while attempting to install an ECM notification handler for the specified path. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger respective RP/SC switchover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_EVM_CREATE Failed to create the event manager: [chars]. Exiting...
Explanation FSDB encountered an error while attempting to create an event manager. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger respective RP/SC switchover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_GET_NODEID FSDB Server: Failed to [chars]: [chars]
Explanation FSDB server failed to obtain either its node ID or extract rack/slot/instance information (having obtained the node ID). The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger respective RP/SC switchover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_INTERNAL [chars] : [chars]
Explanation An internal error occurred that was expected to succeed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_PARSE_FILE Parse error in fabric definition file [chars], line [dec]
Explanation A file describing switch fabric components has errors. Some fabric components cannot be brought into service.
Recommended Action A failed or incomplete software upgrade could cause this error. It could also be caused by corruption of an existing definition file. Ensure that the definition file is not damaged. If the problem persists, re-install the fabric control software.
Error Message%FABRIC-FSDB-3-ERR_RESYNC_TIMEOUT Timeout during initial synchronization with [chars]
Explanation When FSDB starts up it attempts to resynchronise the state with all current entities. This message indicates that one or more of these entities has not responded within the timeout period. This could lead to FSDB having an inconsistent view of the fabric, and can potentially cause traffic loss.
Recommended Action Restarting FSDB process on any racks suffering from traffic loss may help, if not, restart FSDBs on all racks might resolve the issue. 'admin process restart fsdb_server location ' Since 'restart process' is a disruptive operation and all the previous state is lost, all the logs for the commands mentioned in required_info should be saved. If problem persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_SYSDB FSDB Server: Sysdb failed to [chars]: [chars]
Explanation FSDB encountered a Sysdb communication failure. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger respective RP/SC switchover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_SYSDB_BIND Connection to the sysdb server failed: [chars]
Explanation FSDB failed to open a connection to the Sysdb Server process for one of the paths. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger respective RP/SC switchover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_SYSDB_EDM_NOTIF_GEN FSDB Server: Failed generating [chars] notification: [chars]
Explanation FSDB external data manager failed to generate a trap notification. Process would continue to run normally.
Recommended Action This message indicate that trap notifications of the operational states of planes and bundles would not occur. If snmp managability is not enabled, this message can be ignored. However, if this functionality is necessary then restart the process by issuing the following command at the CLI of the active RP after collecting all the output of all the specified commands. 'admin process restart fsdb_server/fsdb_aserver loc ' Restart fsdb_server if the bundle state traps are missing else if plane state traps are missing restart fsdb_aserver. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_SYSDB_EDM_REG Failed to register as an EDM for [chars]: [chars], exiting...
Explanation The FSDB was unable to become an external data manager (EDM) for the specified path. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger respective RP/SC switchover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_SYSDB_REG_NOTIF FSDB Server: Failed to register notification for [chars] path: [chars]. SNMP traps will not be generated for this path
Explanation FSDB external data manager failed to register for notifications for the specified path. Process would continue to run normally, except that SNMP traps will not be generated for changes in fabric state.
Recommended Action This message indicate that trap notifications of the operational states of planes and bundles would not occur. If snmp managability is not enabled, this message can be ignored. However, if this functionality is necessary then restart the process by issuing the following command at the CLI of the active RP after collecting all the output of all the specified commands. 'admin process restart fsdb_server/fsdb_aserver loc ' Restart fsdb_server if the bundle state traps are missing else if plane state traps are missing restart fsdb_aserver. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-3-ERR_UNKNOWN_FAB_DEF Cannot find fabric definition file [chars]
Explanation A file describing switch fabric components is not present on the router.
Recommended Action If the hardware installed in the router has changed, ensure that fabric control software has been upgraded to the correct version. If the correct software has been installed, report the problem to technical support.
Error Message%FABRIC-FSDB-4-ERR_FLED [chars] : [chars], LED(Row [dec], col [dec]), corresponding to node [dec]
Explanation Fabric LED internal software error occurred. It is possible to continue operation, although some LEDs on fabric led board may incorrectly illuminate. However, if this functionality is necessary then restart the process by issuing the following command at the CLI of the active RP after collecting all the output of all the specified commands. 'admin process restart fsdb_server loc ' *SUPPORT*
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-4-ERR_INTERNAL_WARN [chars] : [chars]
Explanation FSDB encountered a minor internal software error. It is possible that fabric operates normally without any issues.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-4-ERR_THREAD_COND_SIGNAL Failed thread conditional signal on [chars]: [chars].
Explanation FSDB encountered an error while attempting to signal a thread conditionally. The operation related to the resource will be affected and the process will continue to run normally.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-4-ERR_THREAD_COND_WAIT Failed thread conditional wait on [chars]: [chars].
Explanation FSDB encountered an error while attempting to wait conditionally on a thread. The operation related to the resource will be affected and the process will continue to run normally.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-4-ERR_THREAD_MUTEX_LOCK Failed to lock [chars] mutex : [chars].
Explanation FSDB encountered an error while locking a mutex to access the specified shared resource. The operation related to the resource may be affected while the process continues to run normally.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-4-ERR_THREAD_MUTEX_UNLOCK Failed to unlock [chars] mutex : [chars].
Explanation FSDB encountered an error while locking unlocking a mutex to access the specified shared resource. The operation related to the resource may be affected while the process continues to run normally.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB-7-ERR_MEM_ALLOC Failed to allocate memory.
Explanation FSDB has failed to allocate memory for its resources. This would affect proper functioning of fabric.
Recommended Action This indicates a low-memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%FABRIC-FSDB-7-ERR_SYSDB_BAG_ENCODE FSDB Server: SYSDB Bag encode[[chars]]: [chars]
Explanation FSDB server encountered error in sysdb bag encode operation. This could affect output of some of the fabric CLI commands.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FSTATSA Messages
Error Message%FABRIC-FSTATSA-3-ERR_BAG_REG Bag register error is detected; [chars].
Explanation Fabric statistics aggregator process encountered a fatal error to register its bags to bag software. This software error will cause process termination for recovery The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_DEBUG_INIT_EVENT Debug initialization for the fstats/server/[chars] event failed; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to initialize debug facility and hence failed to initialize. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_DEBUG_REGISTER Debug registration for fabric statistics server failed; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to register debug facility and hence failed to initialize. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_EVM_CREATE Failed to create event manager; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to create its event manager for receiving events. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_GSP_GROUP_CREATE GSP group [chars] creation/join was failed; [chars]; rc = [hex].
Explanation Fabric statistics aggregator process encountered a fatal error to create group for group communication. This software error will cause process termination to recover. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_INTERNAL Internal software error: [chars]; [chars]
Explanation Fabric statistics aggregator process encountered a fatal internal software error. This software error will cause process termination to recover. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. *RECUR*
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_SYSDB_BIND Can't bind to SysDB at [chars]; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to bind to admin plane sysdb server. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_SYSDB_EDM_REG Failed to register SysDB EDM at [chars]; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to register EDM to admin plane sysdb server. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_SYSMGR_PROC_READY Failed to report process ready to sysmgr; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to report process ready to sysmgr. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FSTATSC Messages
Error Message%FABRIC-FSTATSC-3-ERR_GSP_GROUP_CREATE GSP group [chars] creation/join was failed; [chars].
Explanation Fabric statistics client library encountered failure of creating group for GSP group communication.
Recommended Action Restart Fabric statistics client manually if the error is persistent.
Error Message%FABRIC-FSTATSC-7-ERR_DEBUG_CLEANUP Debug cleanup for fabric statistics client library failed: [chars]
Explanation Fabric statistics client library encountered debug facility clean up failure.
Recommended Action None.
Error Message%FABRIC-FSTATSC-7-ERR_DEBUG_INIT_EVENT Debug initialization for the fstats/client/[chars] event failed: [chars]
Explanation Fabric statistics client library encountered debug facility initialization failure. When this error happens, the library will not able to enable debug.
Recommended Action Restart Fabric statistics client manually if the error is persistent.
Error Message%FABRIC-FSTATSC-7-ERR_DEBUG_REG Debug registration for fabric statistics client library failed: [chars]
Explanation Fabric statistics client library encountered debug facility registration failure. When this error happens, the library will not able to enable debug.
Recommended Action Restart Fabric statistics client manually if the error is persistent.
Error Message%FABRIC-FSTATSC-7-ERR_GSP_LOOKUP_LWG GSP lightweight group [chars] lookup was failed; [chars].
Explanation Fabric statistics client library encountered failure when it looks up Fabric server light weight group for light weight group communication. Normally, this is a transient error. It can be a true error if the error is persistent.
Recommended Action Restart Fabric statistics client manually if the error is persistent in a specific fabric card. Restart Fabric statistics server manually if the error is persistent in many fabric cards.
FSTATSS Messages
Error Message%FABRIC-FSTATSS-3-ERR_BAG_REG Bag register error is detected; [chars].
Explanation Fabric statistics server process encountered a fatal error to register its bags to bag software. This software error will cause process termination for recovery The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_DEBUG_INIT_EVENT Debug initialization for the fstats/server/[chars] event failed; [chars]
Explanation Fabric statistics server process encountered a fatal error to initialize debug facility and hence failed to initialize. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_DEBUG_REGISTER Debug registration for fabric statistics server failed; [chars]
Explanation Fabric statistics server process encountered a fatal error to register debug facility and hence failed to initialize. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_EVM_CREATE Failed to create event manager; [chars]
Explanation Fabric statistics server process encountered a fatal error to create its event manager for receiving events. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_GSP_GROUP_CREATE GSP group [chars] creation/join was failed; [chars]; rc = [hex].
Explanation Fabric statistics server process encountered a fatal error to create group for group communication. This software error will cause process termination to recover. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_INTERNAL Internal software error: [chars]; [chars]
Explanation Fabric statistics server process encountered a fatal internal software error. This software error will cause process termination to recover. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_MEM_ALLOC Could not allocate memory for [chars].
Explanation Fabric statistics server process encountered memory allocation error for creating statistics database or storing statistics data. This software error will cause process termination to recover during process initialization. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action Memory allocation failures will happen if the the router runs out of memory or memory leak in this process or other processes. User needs to do 'process restart ' to recover.
Error Message%FABRIC-FSTATSS-3-ERR_SYSDB_BIND Can't bind to SysDB at [chars]: [chars]
Explanation Fabric statistics server process encountered a fatal error to bind to admin plane sysdb server. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_SYSDB_EDM_REG Failed to register SysDB EDM at at [chars]: [chars]
Explanation Fabric statistics server process encountered a fatal error to register EDM to admin plane sysdb server. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_SYSMGR_PROC_READY Failed to report process ready to sysmgr; [chars]
Explanation Fabric statistics server process encountered a fatal error to report process ready to sysmgr. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-7-ERR_RSC_REG_INCONSISTENT_VALUE [chars]: fabric resource registration error due to inconsistent value.
Explanation Fabric statistics server process encountered a transient error due to the inconsistent checking of the received message. This error message will be a true error if many error message is logged and the error is persistent.
Recommended Action If the error continues, user will need to restart the process for recovery.
