Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.3 - Driver Messages [Cisco IOS XR Software (End-of-Sale)]

Table Of Contents

Driver Messages

FABRICQ_MGR Messages

FABRICQ Messages

FIA_API Messages

FIA Messages

INGRESSQ_ALARM Messages

INGRESSQ_DLL Messages

INGRESSQ_LIB Messages

INGRESSQ Messages

Driver Messages

This section contains all Driver related System Error Messages. The following facility codes are represented in this module:

•FABRICQ_MGR Messages

•FABRICQ Messages

•FIA_API Messages

•FIA Messages

•INGRESSQ_ALARM Messages

•INGRESSQ_DLL Messages

•INGRESSQ_LIB Messages

•INGRESSQ Messages

FABRICQ_MGR Messages
Error Message     
%DRIVERS-FABRICQ_MGR-3-ERR_INIT Initialization Error: [chars] Reason: [chars]. Exiting.
Explanation Fabricq manager encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ_MGR-3-ERR_MEM_ALLOC Error Allocating bytes of memory
Explanation Fabricq encountered a fatal memory allocation error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ_MGR-4-ERR_CHKPT_INIT Checkpoint Initialization failed. Reason: [chars]
Explanation Fabricq Checkpoint Init error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ_MGR-7-ERR_BAG_REG Bag register failed for rules. Reason: [chars]
Explanation EDM Bags are used to share information between components using sysdb. This Error indicates that bag registration 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     
%DRIVERS-FABRICQ_MGR-7-ERR_CLIENT_REG Client [chars] failed. Reason: [chars]
Explanation Fabricq Manager client Registration/Unregistration error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ_MGR-7-ERR_DLL_INIT Dll Initialization for [chars] failed. Reason: [chars]
Explanation Fabricq driver tried to register for a dll but it encountered an error. The driver might lose some of its functionality.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ_MGR-7-ERR_EVM_CREATE Event Manager create failed for [chars]. Reason: [chars]
Explanation Fabricq Event Manager create error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ_MGR-7-ERR_EVM_NOTIFY Event Manager notify failed for [chars]. Reason: [chars]
Explanation Fabricq Event Manager notify error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ_MGR-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed. Reason: [chars]
Explanation Fabricq Event Manager event block error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ_MGR-7-ERR_LWM_REPLY An error occurred during LWM message reply. Reason: [chars]
Explanation Fabricq LWM reply error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ_MGR-7-ERR_SYSDB_EDM_REG Sysdb Register EDM failed. Reason: [chars]
Explanation Fabricq Sysdb Register EDM error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

FABRICQ Messages
Error Message     
%DRIVERS-FABRICQ-3-ERR_ASIC_FCRAM_ASSERT Assert error in Fabricq ASIC [dec]. FCRAM Channel [dec].
Explanation Fabricq ASIC encountered a FCRAM Channel error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-3-ERR_BIST Error during [chars] BIST
Explanation Fabricq BIST error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ-3-ERR_INIT Instance: [dec]. Error: [chars]
Explanation Fabricq Asic driver encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ-3-PCL_CCNT_ERR Major error in PCL of fabricq asic [dec]: [chars] data.
Explanation Sponge encountered a PCL cell count mistmatch error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-3-PCL_CSLOT_SYNC Major internal error in PCL of fabricq asic [dec]: [chars].
Explanation Sponge encountered a PCL internal error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-3-PCL_PKT Minor error in PCL of fabricq asic [dec]. [chars]
Explanation Sponge encountered a PCL Packet error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-3-PCL_XCELL_ERR Major error in PCL of fabricq asic [dec]: [chars]
Explanation Sponge encountered a PCL extra cell error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-3-RESET Reseting Fabricq ASIC Device [dec]. Reason: [chars]
Explanation Reseting Fabricq ASIC on detecting fatal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ-4-ERR_ASIC_MBE Fabricq Asic [dec] detected multibit error(s). Details: [chars]
Explanation Fabricq Asic encountered a memory uncorrectable error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-4-ERR_ASIC_PARITY Fabricq Asic [dec] detected parity error(s). Details: [chars]
Explanation Fabricq Asic encountered a parity error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-4-ERR_ASIC_SN_LINK Fabricq ASIC [dec] encountered a CpuCtrl [chars] error
Explanation Fabricq ASIC encountered a CpuCtrl CRC/Sync error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-4-FI_LINK_ALARM Link Alarm on Fabricq ASIC [dec] link [dec]
Explanation Fabricq ASIC encountered a link alarm
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-4-FI_TOPOLOGY Fabric topology inconsistency detected for ASIC [unsigned int] link [unsigned int] (observed topology information: [hex], expected: [hex])
Explanation An inconsistency between the expected and observed topologies of the fabric was detected.
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-4-MI_WEDGE Major error in Fabricq ASIC [dec]. MI [chars] Wedged
Explanation Fabricq ASIC encountered a MI Unicast/Multicast Wedge error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-4-PSN_WRAP Major error in PCL of Fabricq asic [dec]: [chars] . [hex] spo_pcl_mem_ppbr [hex][hex]%08x[hex]%08x[hex]%08x[hex]
Explanation Fabricq encountered a PCL Packet Sequence Wrap error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-5-ERR_RES_PROG Error during Resource Programming [chars] [unsigned int] Reason: [chars]
Explanation An error occured while the Fabricq driver was trying to create queues for an interface. This may leave one or more interfaces out of operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FABRICQ-5-MI_BPDECODE Major error in Fabricq ASIC [dec]. MI [chars] Backpressure decode error
Explanation Fabricq ASIC encountered a MI Unicast/Multicast BP Decode error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-6-ERR_ASIC_EOP Minor error in Fabricq ASIC [dec]. [chars] End of Packet error
Explanation Fabricq ASIC encountered a Unicast/Multicast Unexpected/Missing End Of Packet error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-6-ERR_ASIC_GENERIC Fabric Asic [dec] encountered generic error(s). Details: [chars]
Explanation Fabricq encountered an interrupt that has exceeded its threshold value. Software takes appropriate action to log and fix the error.
Recommended Action No action is required.
Error Message     
%DRIVERS-FABRICQ-6-ERR_ASIC_OOR Fabricq Asic [dec] encountered [chars] Out Of Resources error.
Explanation Fabricq encountered an out of resources error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-FABRICQ-6-ERR_ASIC_SBE Fabricq Asic [dec] detected single bit error(s). Details: [chars]
Explanation Fabricq Asic encountered a memory correctable error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-6-SPI_FBP Minor error: Cluster: [dec] in Fabricq ASIC [dec] has SPI FBP [chars] error
Explanation The Fabricq asic encounted a fabric backpressure error. These sort of errors are to be expected during bootup or during OIR events, and are harmless for the vast majority of the time. The only time they would signify a serious error is if they recur for long periods.
Recommended Action If these messages are recurring and/or you're seeing other faults (such as traffic loss) then contact your support agent.
Error Message     
%DRIVERS-FABRICQ-6-URG_CTX Minor error in PCL of Fabricq asic [dec]. Urgent Context exceeded 5 = [hex]
Explanation Fabricq encountered a PCL Urgent Context error
Recommended Action *SUPPORT*
Error Message     
%DRIVERS-FABRICQ-7-ERR_DMA Error during DMA transfer: Source Addr [hex], Dest Addr [pointer]. Reason: [chars]
Explanation An error occurred while a DMA transfer initiated by the FQM process was taking place. This means certain data requested by the FQM process will not be available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

FIA_API Messages
Error Message     
%DRIVERS-FIA_API-7-ERR_ECM Event Connection Manager (ECM) Error: [chars] : [chars]
Explanation The FIA driver client library encountered the annunciated error condition. There are 3 types of this failure. - ECM create failure: In this case the FIA driver client library will not be able to connect to the FIA driver. - Register notification handler failure: In this case the FIA driver client library will not receive notification of ECM events. - Failure to open a connection:
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

FIA Messages
Error Message     
%DRIVERS-FIA-3-ERR_ECM_CREATE Failed to create Event Connection Manager[[chars]]: [chars], exiting....
Explanation The FIA driver encountered an event connection 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-3-ERR_ECM_REG Failed to register [chars] connection notification handler with the Event Connection Manager: [chars], exiting....
Explanation The FIA driver encountered an event connection 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-3-ERR_EIO_TRAIN EIO link training failure threshold reached. Link will not be re-trained. ASIC instance: [dec], EIO link ID: [dec]
Explanation Repeated attempts to train the EIO links between the FIA and Ingressq/Fabric ASIC has failed. No further attempts to retrain the link will be made. This is indicative of a hardware failure on the serial link between the ASICs or an inter-process communication error between the driver processes.
Recommended Action Collect the required information indicated below. Also, run the field diags and the health check. If the health check or diags fail, then initiate the RMA process. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-3-ERR_EVM_INIT Failed to initialize the event manager: [chars], exiting...
Explanation The FIA driver was unable to initialize 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-3-ERR_INIT Initialization Error [[chars]]: [chars], exiting....
Explanation The FIA driver failed to initialize the device resulting in the restart of the FIA driver process. 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.
Recommended Action Verify that the fia_driver is up and running by executing the following command at the CLI of the active RP: 'show process fia_driver location ' If it is still non-operational, enable the following debugs of the FIA driver process: eio All EIO library events error Errors in the driver fatal Fatal errors which cause driver to exit info All informational events init Initialization events Restart the driver by executing the following command at the CLI of the active RP: process restart fia_driver loc If the problem persists, this could be indicative of a hardware failure and it is recommended to run the field diagnostics on the failing MSC.
Error Message     
%DRIVERS-FIA-3-ERR_MEM_MAP Failed to map ASIC instance [dec] into memory (PROT flags: [dec], MAP flags: [dec]): [chars]
Explanation The FIA driver was unable to map the hardware of the specified ASIC instance into its memory space and therefore 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-3-ERR_PLL Failed to lock TX slice PLL after [unsigned int] retries (ASIC instance: [dec], slice ID: [unsigned int]).
Explanation While initializing the transmit slices of the FIA, the driver failed to lock the PLL. This is caused due to a clock synchronization problem between the MSC and the fabric board. This would result in loss of connectivity and bandwidth to affected fabric board.
Recommended Action Collect the required information indicated below. Also, run the field diags and the health check. If the health check or diags fail, then initiate the RMA process. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-4-ERR_CHKPT Failed to [chars] checkpoint record: [chars]
Explanation The FIA driver encountered an error while updating or accessing its checkpoint information. Further high availability of the driver may be impacted.
Recommended Action Verify that the fia_driver process is up and running by executing the following command at the CLI of the active RP: 'show process fia_driver' If the high availability of the FIA driver is not important, then this message may be ignored. However, if this functionality is necessary then restart the FIA driver by issuing the following command at the CLI of the active RP: 'process restart fia_driver' Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-4-ERR_SYSDB_CONN_TO_COID Failed to [chars] (despite connection to SysDB being open): [chars]
Explanation The FIA driver was unable to become an external data manager (EDM) despite having a connection to SysDB. The operation will be retried.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-4-ERR_SYSDB_EDM_REG Failed to register [chars] (despite connection to SysDB being open): [chars]
Explanation The FIA driver was unable to become an external data manager (EDM) despite having a connection to SysDB. The operation will be retried.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-7-ERR_CHKPT_INIT Failed to initialize checkpoint library: [chars].
Explanation The FIA driver failed to initialize the checkpoint library. 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-7-ERR_CHKPT_REG Failed to register checkpoint table: [chars].
Explanation The FIA driver failed to register the checkpoint table. 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-7-ERR_EVM Failed to attach [chars] to event manager:[chars], exiting...
Explanation The FIA driver 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-7-ERR_EVM_ASYNC_ATTACH Failed to attach an asynchronous [chars] handler to event manager: [chars].
Explanation The FIA driver was unable to attach the indicated asynchronous 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-7-ERR_EVM_CREATE Failed to create event manager for '[chars]': [chars], exiting...
Explanation The FIA 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 process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed on [chars] thread: [chars]
Explanation The FIA driver LWM event manager has failed to block on the indicated 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     
%DRIVERS-FIA-7-ERR_LWM_REPLY Failed to send reply: [chars].
Explanation The FIA driver failed to send messaging reply.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-7-ERR_MEM_ALLOC Failed to allocate memory.
Explanation FIA driver memory allocation error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-7-ERR_SYSDB_EDM_DATALIST Failed to [chars] SYSDB EDM datalist: [chars].
Explanation The FIA driver has failed to either create / add a external data manager datalist.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-7-ERR_SYSDB_EDM_OPEN Failed to open EDM event connection manager: [chars], exiting...
Explanation The FIA driver to failed open the SysDB EDM connection by binding to it and registering using the event connection manager.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-FIA-7-ERR_THREAD_CREATE Failed to create [chars] thread: [chars], exiting....
Explanation The FIA driver failed to create the specified thread. 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

INGRESSQ_ALARM Messages
Error Message     
%DRIVERS-INGRESSQ_ALARM-2-DEVICE_HALT INGRESSQ: device halted, sub-block: [chars], halted entity: [chars]
Explanation INGRESSQ, ASIC got halted. The halted block and its parent block are provided
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

INGRESSQ_DLL Messages
Error Message     
%DRIVERS-INGRESSQ_DLL-2-ASIC_RESET_FAILED Ingressq ASIC reset failed. Bringing the MSC down.
Explanation Ingressq, ASIC reset failed and it could be due to several reasons.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-2-ERR_EIO_TRAIN EIO link training threshold exceeded, link: [dec]
Explanation Ingressq DLL encountered a fatal error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-2-TAKING_NODE_DOWN Taking the node down, Reason: [chars]
Explanation Ingressq DLL encountered a fatal error and taking the node down.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-3-ERR_ASIC_FCRAM_ASSERT Assert Error valid: [dec], block: [dec], debug_info: [dec]
Explanation Ingressq encountered an assert error indicated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-3-ERR_ASIC_MBE Multiple Bit Error in Block: [chars] Error: [chars] at Memory Address [hex].
Explanation Ingressq encountered a multiple bit error in the mentioned block. This error is an uncorrectable error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-3-ERR_BIST Error during [chars] BIST
Explanation Ingressq BIST error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-3-ERR_INIT [chars]
Explanation Ingressq dll manager encountered an fatal error and is not able recover from the error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-3-ERR_MEM_ALLOC Error Allocating memory for
Explanation The Ingressq dll Memory Allocation Error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-3-RESET Reseting IQM ASIC Device
Explanation Reseting IQM ASIC on detecting fatal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-3-SEQ_STATE_POST_OP_FAILED Post OP Failed: sequencer state: [dec], reason: [chars] : [chars], #retries: [dec]
Explanation Sprayer sequencer post op 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     
%DRIVERS-INGRESSQ_DLL-3-SEQ_STATE_PRE_OP_FAILED Pre OP Failed - Exiting : sequencer state: [dec], reason: [chars] : [chars]
Explanation Sprayer sequencer pre op 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     
%DRIVERS-INGRESSQ_DLL-3-WDG_SEG_HUNG Spiller Seg blk is hung, reseting spiller - pkt_fifo [hex], ctrl_fifo [hex], icf_fifo [hex]
Explanation Watchdog detected that spiller seg block is hung, reseting spiller 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     
%DRIVERS-INGRESSQ_DLL-4-BRM_AGGR_DELTA_THRSHLD BRM aggr delta, spo link: [dec], cast: [dec], threshold: [dec]
Explanation Hardware halt is not handled.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-BRM_DELTA_THRSHLD BRM delta threshold, spo link: [dec], cast: [dec], threshold: [dec]
Explanation Hardware halt is not handled.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-BRM_DID_CULPRIT BRM double in delta culprit, spo link: [dec], cast: [dec]
Explanation Hardware halt is not handled.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-BRM_INVALID_INPUT BRM invalid input; spo: [dec], cast: [dec], input_barr: [hex], current_barr: [hex]
Explanation Invalid input on a link
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-BRM_PHASE_CHANGE_COUNTER BRM, phase didn't change, spo link: [dec], cast: [dec], phase: [hex], phase to counter: [hex], phase to thr: [hex]
Explanation Barrier Manager encountered a phase change error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-CDMA_REQ_ERROR CpuCtrl error, addr:([hex],[hex]), dir: [dec], rc: [dec]
Explanation cpuctrl driver was not able to complete the CDMA request.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-ERR_ASIC_CRC Block: [chars], entity: [chars] had CRC error(s), count: [dec]
Explanation PII block got a packet from the entity mentioned above with a CRC error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-ERR_ASIC_LENGTH Block: [chars], entity: [chars] has length error(s), expected: [dec], received: [dec]
Explanation PII block got a packet from the entity mentioned above with a length error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-ERR_ASIC_SN_LINK CpuCtrl Interface RxFIFO Error: [chars]
Explanation Ingressq, cpuctrl net interface Rx FIFO last sync.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-ERR_CHKPT_INIT Error encountered during Checkpoint Initialization
Explanation Ingressq Checkpoint Init error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-ERR_CHKPT_INSERT Error encountered during [chars] Checkpoint Insertion
Explanation Ingressq Checkpoint Insert error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-INTR_ENABLE_FAIL Interrupt enable at addr: [hex] mask: [hex] failed.
Explanation hardware state is not correct.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-LNS_CCDF_OVERFLOW_ERROR control cell fifo overflow error
Explanation Ingressq LNS control cell fifo overflow.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-LNS_LOP_DROP low availability of planes, aggr cell drop count: [unsigned long long int]
Explanation Ingressq LNS dropped cells because of low availability of planes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-4-PFI_PARITY_ERROR parity error in plane RA, name: [chars], link: [dec], RA: [dec], Addr: [dec]
Explanation Ingressq, cpuctrl net interface Rx FIFO last sync.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-5-ERR_ASIC_PARITY Block: [chars], entity: [chars] had parity error(s), addr: [dec], parity: [dec]
Explanation One of the Ingressq blocks had a parity error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-5-ERR_ASIC_SBE Single Bit Error in Block: [chars] Error: [chars] at Memory Address: [hex]
Explanation Ingressq encountered a single bit error in the mentioned block. Persistent errors are corrected by the software. Non-persistent errors are automatically corrected when the memory location is eventually overwritten.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-6-BRM_BARRIER_SYNCUP_FAILED BRM BlocK: Barrier sync up failed for this node.
Explanation Ingressq, Barrier is not synced up.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-6-ERR_ASIC_GENERIC Block: [chars], Generic Error [chars] at Memory Address [hex].
Explanation Ingressq encountered an interrupt that has exceeded its threshold value. Software takes appropriate action to log and fix the error.
Recommended Action No action is required.
Error Message     
%DRIVERS-INGRESSQ_DLL-6-ERR_ASIC_OOR Block: [chars], entity: [chars] had Out Of Resources error(s), count: [dec]
Explanation Ingressq block is unable to get packet memory from FQM.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-6-SEQ_STATE_THRESHOLD_EXCEEDED sequencer state: [dec], threshold: [dec], reason: [chars], #retries: [dec]
Explanation Ingressq sequencer state threshold exceeded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-6-WDG_BARRIER_STALL_CLEARED [chars]: barrier stall cleared.
Explanation Ingressq, Barrier stall cleared on one of the casts
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-6-WDG_BARRIER_STALLED [chars]: barrier stalled.
Explanation Ingressq, Barrier stalled on one of the casts
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ_DLL-7-ERR_REGISTER_GET Register get failed for address [hex], Reason: [chars]
Explanation Hardware register read failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message     
%DRIVERS-INGRESSQ_DLL-7-ERR_RES_PROG Error during Resource Programming: [chars] Reason: [chars]
Explanation Ingressq encountered an error during resource programming.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

INGRESSQ_LIB Messages
Error Message     
%DRIVERS-INGRESSQ_LIB-7-ERR_LWM_SEND Ingressq Lib: LWM Message send failed msg: [dec], retried: [dec] time(s), errno: [chars]
Explanation Unable to send a LWM message to the Ingressq server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

INGRESSQ Messages
Error Message     
%DRIVERS-INGRESSQ-3-ERR_INIT Fatal error encountered, reason=[chars]
Explanation Ingressq encountered a fatal unrecoverable error. This process is mandatory and it will restart itself.
Recommended Action Ingressq Process will restart itself and recover from the error if possible. Otherwise, after fixed number of retries, sysmgr will bring the MSC down.
Error Message     
%DRIVERS-INGRESSQ-3-ERR_MEM_ALLOC Error Allocating bytes of memory
Explanation Ingressq encountered a fatal memory allocation error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-4-ERR_CHKPT_INIT Ingressq Dll: Error encountered during Checkpoint Init. Exiting
Explanation Ingressq Checkpoint Init error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_BAG_REG ingressq: bag register failed for rules
Explanation EDM Bags are used to share information between components using sysdb. This Error indicates that bag registration 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     
%DRIVERS-INGRESSQ-7-ERR_CHKPT_DELETE Error encountered during [chars] Checkpoint Deletion
Explanation Ingressq Checkpoint delete error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_CHKPT_INSERT Error encountered during [chars] Checkpoint Insertion
Explanation Ingressq Checkpoint Insert error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_CLIENT_REG Client [chars] failed. Error: [chars]
Explanation Ingressq client Registration/Unregistration error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_DLL_REG Dll registration for [chars] failed
Explanation Ingressq driver tried to register for a dll but it encountered an error. The driver might lose some of its functionality.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_EVM_CREATE Event Manager create failed for [chars]
Explanation Ingressq Event Manager create error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_EVM_NOTIFY Event Manager notify failed for [chars]
Explanation Ingressq Event Manager notify error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_LWM_CREATE Event Manager create failed
Explanation Ingressq Event Manager create error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed
Explanation Ingressq Event Manager event block error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_LWM_REPLY An Error occurred during LWM message reply. Reason: [chars]
Explanation Ingressq LWM reply error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_RES_PROG Error during Resource Programming: [chars] Reason: [chars]
Explanation Ingressq encountered an error during resource programming.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_SYSDB_BIND Sysdb Bind failed.
Explanation Ingressq Sysdb Bind error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_SYSDB_EDM_REG Sysdb Register EDM failed.
Explanation Ingressq Sysdb Register EDM error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_SYSDB_REG_VERIFY Sysdb Registration verification failed.
Explanation Ingressq Sysdb Registration verification error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message     
%DRIVERS-INGRESSQ-7-ERR_SYSDB_SET Sysdb Item Set Failed : [chars]
Explanation Ingressq Sysdb Set error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

	Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.3
	Driver Messages
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	Download this chapter Driver Messages Download the complete book Book-level PDF: Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages (PDF - 2 MB) Feedback Table Of Contents Driver Messages FABRICQ_MGR Messages FABRICQ Messages FIA_API Messages FIA Messages INGRESSQ_ALARM Messages INGRESSQ_DLL Messages INGRESSQ_LIB Messages INGRESSQ Messages Driver Messages This section contains all Driver related System Error Messages. The following facility codes are represented in this module: •FABRICQ_MGR Messages •FABRICQ Messages •FIA_API Messages •FIA Messages •INGRESSQ_ALARM Messages •INGRESSQ_DLL Messages •INGRESSQ_LIB Messages •INGRESSQ Messages FABRICQ_MGR Messages Error Message %DRIVERS-FABRICQ_MGR-3-ERR_INIT Initialization Error: [chars] Reason: [chars]. Exiting. Explanation Fabricq manager encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ_MGR-3-ERR_MEM_ALLOC Error Allocating bytes of memory Explanation Fabricq encountered a fatal memory allocation error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ_MGR-4-ERR_CHKPT_INIT Checkpoint Initialization failed. Reason: [chars] Explanation Fabricq Checkpoint Init error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ_MGR-7-ERR_BAG_REG Bag register failed for rules. Reason: [chars] Explanation EDM Bags are used to share information between components using sysdb. This Error indicates that bag registration 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 %DRIVERS-FABRICQ_MGR-7-ERR_CLIENT_REG Client [chars] failed. Reason: [chars] Explanation Fabricq Manager client Registration/Unregistration error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ_MGR-7-ERR_DLL_INIT Dll Initialization for [chars] failed. Reason: [chars] Explanation Fabricq driver tried to register for a dll but it encountered an error. The driver might lose some of its functionality. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ_MGR-7-ERR_EVM_CREATE Event Manager create failed for [chars]. Reason: [chars] Explanation Fabricq Event Manager create error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ_MGR-7-ERR_EVM_NOTIFY Event Manager notify failed for [chars]. Reason: [chars] Explanation Fabricq Event Manager notify error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ_MGR-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed. Reason: [chars] Explanation Fabricq Event Manager event block error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ_MGR-7-ERR_LWM_REPLY An error occurred during LWM message reply. Reason: [chars] Explanation Fabricq LWM reply error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ_MGR-7-ERR_SYSDB_EDM_REG Sysdb Register EDM failed. Reason: [chars] Explanation Fabricq Sysdb Register EDM error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. FABRICQ Messages Error Message %DRIVERS-FABRICQ-3-ERR_ASIC_FCRAM_ASSERT Assert error in Fabricq ASIC [dec]. FCRAM Channel [dec]. Explanation Fabricq ASIC encountered a FCRAM Channel error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-3-ERR_BIST Error during [chars] BIST Explanation Fabricq BIST error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ-3-ERR_INIT Instance: [dec]. Error: [chars] Explanation Fabricq Asic driver encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ-3-PCL_CCNT_ERR Major error in PCL of fabricq asic [dec]: [chars] data. Explanation Sponge encountered a PCL cell count mistmatch error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-3-PCL_CSLOT_SYNC Major internal error in PCL of fabricq asic [dec]: [chars]. Explanation Sponge encountered a PCL internal error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-3-PCL_PKT Minor error in PCL of fabricq asic [dec]. [chars] Explanation Sponge encountered a PCL Packet error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-3-PCL_XCELL_ERR Major error in PCL of fabricq asic [dec]: [chars] Explanation Sponge encountered a PCL extra cell error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-3-RESET Reseting Fabricq ASIC Device [dec]. Reason: [chars] Explanation Reseting Fabricq ASIC on detecting fatal error. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ-4-ERR_ASIC_MBE Fabricq Asic [dec] detected multibit error(s). Details: [chars] Explanation Fabricq Asic encountered a memory uncorrectable error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-4-ERR_ASIC_PARITY Fabricq Asic [dec] detected parity error(s). Details: [chars] Explanation Fabricq Asic encountered a parity error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-4-ERR_ASIC_SN_LINK Fabricq ASIC [dec] encountered a CpuCtrl [chars] error Explanation Fabricq ASIC encountered a CpuCtrl CRC/Sync error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-4-FI_LINK_ALARM Link Alarm on Fabricq ASIC [dec] link [dec] Explanation Fabricq ASIC encountered a link alarm Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-4-FI_TOPOLOGY Fabric topology inconsistency detected for ASIC [unsigned int] link [unsigned int] (observed topology information: [hex], expected: [hex]) Explanation An inconsistency between the expected and observed topologies of the fabric was detected. Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-4-MI_WEDGE Major error in Fabricq ASIC [dec]. MI [chars] Wedged Explanation Fabricq ASIC encountered a MI Unicast/Multicast Wedge error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-4-PSN_WRAP Major error in PCL of Fabricq asic [dec]: [chars] . [hex] spo_pcl_mem_ppbr [hex][hex]%08x[hex]%08x[hex]%08x[hex] Explanation Fabricq encountered a PCL Packet Sequence Wrap error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-5-ERR_RES_PROG Error during Resource Programming [chars] [unsigned int] Reason: [chars] Explanation An error occured while the Fabricq driver was trying to create queues for an interface. This may leave one or more interfaces out of operation. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FABRICQ-5-MI_BPDECODE Major error in Fabricq ASIC [dec]. MI [chars] Backpressure decode error Explanation Fabricq ASIC encountered a MI Unicast/Multicast BP Decode error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-6-ERR_ASIC_EOP Minor error in Fabricq ASIC [dec]. [chars] End of Packet error Explanation Fabricq ASIC encountered a Unicast/Multicast Unexpected/Missing End Of Packet error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-6-ERR_ASIC_GENERIC Fabric Asic [dec] encountered generic error(s). Details: [chars] Explanation Fabricq encountered an interrupt that has exceeded its threshold value. Software takes appropriate action to log and fix the error. Recommended Action No action is required. Error Message %DRIVERS-FABRICQ-6-ERR_ASIC_OOR Fabricq Asic [dec] encountered [chars] Out Of Resources error. Explanation Fabricq encountered an out of resources error. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-FABRICQ-6-ERR_ASIC_SBE Fabricq Asic [dec] detected single bit error(s). Details: [chars] Explanation Fabricq Asic encountered a memory correctable error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-6-SPI_FBP Minor error: Cluster: [dec] in Fabricq ASIC [dec] has SPI FBP [chars] error Explanation The Fabricq asic encounted a fabric backpressure error. These sort of errors are to be expected during bootup or during OIR events, and are harmless for the vast majority of the time. The only time they would signify a serious error is if they recur for long periods. Recommended Action If these messages are recurring and/or you're seeing other faults (such as traffic loss) then contact your support agent. Error Message %DRIVERS-FABRICQ-6-URG_CTX Minor error in PCL of Fabricq asic [dec]. Urgent Context exceeded 5 = [hex] Explanation Fabricq encountered a PCL Urgent Context error Recommended Action SUPPORT Error Message %DRIVERS-FABRICQ-7-ERR_DMA Error during DMA transfer: Source Addr [hex], Dest Addr [pointer]. Reason: [chars] Explanation An error occurred while a DMA transfer initiated by the FQM process was taking place. This means certain data requested by the FQM process will not be available. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. FIA_API Messages Error Message %DRIVERS-FIA_API-7-ERR_ECM Event Connection Manager (ECM) Error: [chars] : [chars] Explanation The FIA driver client library encountered the annunciated error condition. There are 3 types of this failure. - ECM create failure: In this case the FIA driver client library will not be able to connect to the FIA driver. - Register notification handler failure: In this case the FIA driver client library will not receive notification of ECM events. - Failure to open a connection: Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. FIA Messages Error Message %DRIVERS-FIA-3-ERR_ECM_CREATE Failed to create Event Connection Manager[[chars]]: [chars], exiting.... Explanation The FIA driver encountered an event connection 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-3-ERR_ECM_REG Failed to register [chars] connection notification handler with the Event Connection Manager: [chars], exiting.... Explanation The FIA driver encountered an event connection 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-3-ERR_EIO_TRAIN EIO link training failure threshold reached. Link will not be re-trained. ASIC instance: [dec], EIO link ID: [dec] Explanation Repeated attempts to train the EIO links between the FIA and Ingressq/Fabric ASIC has failed. No further attempts to retrain the link will be made. This is indicative of a hardware failure on the serial link between the ASICs or an inter-process communication error between the driver processes. Recommended Action Collect the required information indicated below. Also, run the field diags and the health check. If the health check or diags fail, then initiate the RMA process. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-3-ERR_EVM_INIT Failed to initialize the event manager: [chars], exiting... Explanation The FIA driver was unable to initialize 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-3-ERR_INIT Initialization Error [[chars]]: [chars], exiting.... Explanation The FIA driver failed to initialize the device resulting in the restart of the FIA driver process. 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC. Recommended Action Verify that the fia_driver is up and running by executing the following command at the CLI of the active RP: 'show process fia_driver location ' If it is still non-operational, enable the following debugs of the FIA driver process: eio All EIO library events error Errors in the driver fatal Fatal errors which cause driver to exit info All informational events init Initialization events Restart the driver by executing the following command at the CLI of the active RP: process restart fia_driver loc If the problem persists, this could be indicative of a hardware failure and it is recommended to run the field diagnostics on the failing MSC. Error Message %DRIVERS-FIA-3-ERR_MEM_MAP Failed to map ASIC instance [dec] into memory (PROT flags: [dec], MAP flags: [dec]): [chars] Explanation The FIA driver was unable to map the hardware of the specified ASIC instance into its memory space and therefore 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-3-ERR_PLL Failed to lock TX slice PLL after [unsigned int] retries (ASIC instance: [dec], slice ID: [unsigned int]). Explanation While initializing the transmit slices of the FIA, the driver failed to lock the PLL. This is caused due to a clock synchronization problem between the MSC and the fabric board. This would result in loss of connectivity and bandwidth to affected fabric board. Recommended Action Collect the required information indicated below. Also, run the field diags and the health check. If the health check or diags fail, then initiate the RMA process. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-4-ERR_CHKPT Failed to [chars] checkpoint record: [chars] Explanation The FIA driver encountered an error while updating or accessing its checkpoint information. Further high availability of the driver may be impacted. Recommended Action Verify that the fia_driver process is up and running by executing the following command at the CLI of the active RP: 'show process fia_driver' If the high availability of the FIA driver is not important, then this message may be ignored. However, if this functionality is necessary then restart the FIA driver by issuing the following command at the CLI of the active RP: 'process restart fia_driver' Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-4-ERR_SYSDB_CONN_TO_COID Failed to [chars] (despite connection to SysDB being open): [chars] Explanation The FIA driver was unable to become an external data manager (EDM) despite having a connection to SysDB. The operation will be retried. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-4-ERR_SYSDB_EDM_REG Failed to register [chars] (despite connection to SysDB being open): [chars] Explanation The FIA driver was unable to become an external data manager (EDM) despite having a connection to SysDB. The operation will be retried. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-7-ERR_CHKPT_INIT Failed to initialize checkpoint library: [chars]. Explanation The FIA driver failed to initialize the checkpoint library. 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-7-ERR_CHKPT_REG Failed to register checkpoint table: [chars]. Explanation The FIA driver failed to register the checkpoint table. 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-7-ERR_EVM Failed to attach [chars] to event manager:[chars], exiting... Explanation The FIA driver 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-7-ERR_EVM_ASYNC_ATTACH Failed to attach an asynchronous [chars] handler to event manager: [chars]. Explanation The FIA driver was unable to attach the indicated asynchronous 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-7-ERR_EVM_CREATE Failed to create event manager for '[chars]': [chars], exiting... Explanation The FIA 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 process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed on [chars] thread: [chars] Explanation The FIA driver LWM event manager has failed to block on the indicated 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 %DRIVERS-FIA-7-ERR_LWM_REPLY Failed to send reply: [chars]. Explanation The FIA driver failed to send messaging reply. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-7-ERR_MEM_ALLOC Failed to allocate memory. Explanation FIA driver memory allocation error. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-7-ERR_SYSDB_EDM_DATALIST Failed to [chars] SYSDB EDM datalist: [chars]. Explanation The FIA driver has failed to either create / add a external data manager datalist. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-7-ERR_SYSDB_EDM_OPEN Failed to open EDM event connection manager: [chars], exiting... Explanation The FIA driver to failed open the SysDB EDM connection by binding to it and registering using the event connection manager. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-FIA-7-ERR_THREAD_CREATE Failed to create [chars] thread: [chars], exiting.... Explanation The FIA driver failed to create the specified thread. 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 MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC. Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. INGRESSQ_ALARM Messages Error Message %DRIVERS-INGRESSQ_ALARM-2-DEVICE_HALT INGRESSQ: device halted, sub-block: [chars], halted entity: [chars] Explanation INGRESSQ, ASIC got halted. The halted block and its parent block are provided Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. INGRESSQ_DLL Messages Error Message %DRIVERS-INGRESSQ_DLL-2-ASIC_RESET_FAILED Ingressq ASIC reset failed. Bringing the MSC down. Explanation Ingressq, ASIC reset failed and it could be due to several reasons. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-2-ERR_EIO_TRAIN EIO link training threshold exceeded, link: [dec] Explanation Ingressq DLL encountered a fatal error. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-2-TAKING_NODE_DOWN Taking the node down, Reason: [chars] Explanation Ingressq DLL encountered a fatal error and taking the node down. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-3-ERR_ASIC_FCRAM_ASSERT Assert Error valid: [dec], block: [dec], debug_info: [dec] Explanation Ingressq encountered an assert error indicated. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-3-ERR_ASIC_MBE Multiple Bit Error in Block: [chars] Error: [chars] at Memory Address [hex]. Explanation Ingressq encountered a multiple bit error in the mentioned block. This error is an uncorrectable error. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-3-ERR_BIST Error during [chars] BIST Explanation Ingressq BIST error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-3-ERR_INIT [chars] Explanation Ingressq dll manager encountered an fatal error and is not able recover from the error. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-3-ERR_MEM_ALLOC Error Allocating memory for Explanation The Ingressq dll Memory Allocation Error message. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-3-RESET Reseting IQM ASIC Device Explanation Reseting IQM ASIC on detecting fatal error. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-3-SEQ_STATE_POST_OP_FAILED Post OP Failed: sequencer state: [dec], reason: [chars] : [chars], #retries: [dec] Explanation Sprayer sequencer post op 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 %DRIVERS-INGRESSQ_DLL-3-SEQ_STATE_PRE_OP_FAILED Pre OP Failed - Exiting : sequencer state: [dec], reason: [chars] : [chars] Explanation Sprayer sequencer pre op 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 %DRIVERS-INGRESSQ_DLL-3-WDG_SEG_HUNG Spiller Seg blk is hung, reseting spiller - pkt_fifo [hex], ctrl_fifo [hex], icf_fifo [hex] Explanation Watchdog detected that spiller seg block is hung, reseting spiller 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 %DRIVERS-INGRESSQ_DLL-4-BRM_AGGR_DELTA_THRSHLD BRM aggr delta, spo link: [dec], cast: [dec], threshold: [dec] Explanation Hardware halt is not handled. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-4-BRM_DELTA_THRSHLD BRM delta threshold, spo link: [dec], cast: [dec], threshold: [dec] Explanation Hardware halt is not handled. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-4-BRM_DID_CULPRIT BRM double in delta culprit, spo link: [dec], cast: [dec] Explanation Hardware halt is not handled. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-4-BRM_INVALID_INPUT BRM invalid input; spo: [dec], cast: [dec], input_barr: [hex], current_barr: [hex] Explanation Invalid input on a link Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-4-BRM_PHASE_CHANGE_COUNTER BRM, phase didn't change, spo link: [dec], cast: [dec], phase: [hex], phase to counter: [hex], phase to thr: [hex] Explanation Barrier Manager encountered a phase change error. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-4-CDMA_REQ_ERROR CpuCtrl error, addr:([hex],[hex]), dir: [dec], rc: [dec] Explanation cpuctrl driver was not able to complete the CDMA request. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-4-ERR_ASIC_CRC Block: [chars], entity: [chars] had CRC error(s), count: [dec] Explanation PII block got a packet from the entity mentioned above with a CRC error. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-4-ERR_ASIC_LENGTH Block: [chars], entity: [chars] has length error(s), expected: [dec], received: [dec] Explanation PII block got a packet from the entity mentioned above with a length error. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-4-ERR_ASIC_SN_LINK CpuCtrl Interface RxFIFO Error: [chars] Explanation Ingressq, cpuctrl net interface Rx FIFO last sync. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-4-ERR_CHKPT_INIT Error encountered during Checkpoint Initialization Explanation Ingressq Checkpoint Init error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-4-ERR_CHKPT_INSERT Error encountered during [chars] Checkpoint Insertion Explanation Ingressq Checkpoint Insert error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-4-INTR_ENABLE_FAIL Interrupt enable at addr: [hex] mask: [hex] failed. Explanation hardware state is not correct. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-4-LNS_CCDF_OVERFLOW_ERROR control cell fifo overflow error Explanation Ingressq LNS control cell fifo overflow. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-4-LNS_LOP_DROP low availability of planes, aggr cell drop count: [unsigned long long int] Explanation Ingressq LNS dropped cells because of low availability of planes. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-4-PFI_PARITY_ERROR parity error in plane RA, name: [chars], link: [dec], RA: [dec], Addr: [dec] Explanation Ingressq, cpuctrl net interface Rx FIFO last sync. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-5-ERR_ASIC_PARITY Block: [chars], entity: [chars] had parity error(s), addr: [dec], parity: [dec] Explanation One of the Ingressq blocks had a parity error. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-5-ERR_ASIC_SBE Single Bit Error in Block: [chars] Error: [chars] at Memory Address: [hex] Explanation Ingressq encountered a single bit error in the mentioned block. Persistent errors are corrected by the software. Non-persistent errors are automatically corrected when the memory location is eventually overwritten. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-6-BRM_BARRIER_SYNCUP_FAILED BRM BlocK: Barrier sync up failed for this node. Explanation Ingressq, Barrier is not synced up. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-6-ERR_ASIC_GENERIC Block: [chars], Generic Error [chars] at Memory Address [hex]. Explanation Ingressq encountered an interrupt that has exceeded its threshold value. Software takes appropriate action to log and fix the error. Recommended Action No action is required. Error Message %DRIVERS-INGRESSQ_DLL-6-ERR_ASIC_OOR Block: [chars], entity: [chars] had Out Of Resources error(s), count: [dec] Explanation Ingressq block is unable to get packet memory from FQM. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-6-SEQ_STATE_THRESHOLD_EXCEEDED sequencer state: [dec], threshold: [dec], reason: [chars], #retries: [dec] Explanation Ingressq sequencer state threshold exceeded. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-6-WDG_BARRIER_STALL_CLEARED [chars]: barrier stall cleared. Explanation Ingressq, Barrier stall cleared on one of the casts Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-6-WDG_BARRIER_STALLED [chars]: barrier stalled. Explanation Ingressq, Barrier stalled on one of the casts Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ_DLL-7-ERR_REGISTER_GET Register get failed for address [hex], Reason: [chars] Explanation Hardware register read failed. Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error Message %DRIVERS-INGRESSQ_DLL-7-ERR_RES_PROG Error during Resource Programming: [chars] Reason: [chars] Explanation Ingressq encountered an error during resource programming. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. INGRESSQ_LIB Messages Error Message %DRIVERS-INGRESSQ_LIB-7-ERR_LWM_SEND Ingressq Lib: LWM Message send failed msg: [dec], retried: [dec] time(s), errno: [chars] Explanation Unable to send a LWM message to the Ingressq server. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. INGRESSQ Messages Error Message %DRIVERS-INGRESSQ-3-ERR_INIT Fatal error encountered, reason=[chars] Explanation Ingressq encountered a fatal unrecoverable error. This process is mandatory and it will restart itself. Recommended Action Ingressq Process will restart itself and recover from the error if possible. Otherwise, after fixed number of retries, sysmgr will bring the MSC down. Error Message %DRIVERS-INGRESSQ-3-ERR_MEM_ALLOC Error Allocating bytes of memory Explanation Ingressq encountered a fatal memory allocation error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-4-ERR_CHKPT_INIT Ingressq Dll: Error encountered during Checkpoint Init. Exiting Explanation Ingressq Checkpoint Init error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_BAG_REG ingressq: bag register failed for rules Explanation EDM Bags are used to share information between components using sysdb. This Error indicates that bag registration 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 %DRIVERS-INGRESSQ-7-ERR_CHKPT_DELETE Error encountered during [chars] Checkpoint Deletion Explanation Ingressq Checkpoint delete error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_CHKPT_INSERT Error encountered during [chars] Checkpoint Insertion Explanation Ingressq Checkpoint Insert error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_CLIENT_REG Client [chars] failed. Error: [chars] Explanation Ingressq client Registration/Unregistration error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_DLL_REG Dll registration for [chars] failed Explanation Ingressq driver tried to register for a dll but it encountered an error. The driver might lose some of its functionality. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_EVM_CREATE Event Manager create failed for [chars] Explanation Ingressq Event Manager create error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_EVM_NOTIFY Event Manager notify failed for [chars] Explanation Ingressq Event Manager notify error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_LWM_CREATE Event Manager create failed Explanation Ingressq Event Manager create error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed Explanation Ingressq Event Manager event block error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_LWM_REPLY An Error occurred during LWM message reply. Reason: [chars] Explanation Ingressq LWM reply error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_RES_PROG Error during Resource Programming: [chars] Reason: [chars] Explanation Ingressq encountered an error during resource programming. Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_SYSDB_BIND Sysdb Bind failed. Explanation Ingressq Sysdb Bind error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_SYSDB_EDM_REG Sysdb Register EDM failed. Explanation Ingressq Sysdb Register EDM error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_SYSDB_REG_VERIFY Sysdb Registration verification failed. Explanation Ingressq Sysdb Registration verification error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Error Message %DRIVERS-INGRESSQ-7-ERR_SYSDB_SET Sysdb Item Set Failed : [chars] Explanation Ingressq Sysdb Set error Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks