-
Cisco IOS XR System Error Message Reference Guide, Release 3.8
-
Preface
-
Overview
-
Access Control List (ACL) Messages
-
Application Infrastructure Messages
-
Diagnostic Messages
-
Fabric Messages
-
Forwarding Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 Messages
-
Layer 2 Messages
-
Layer 3 Messages
-
License Messages
-
Media Messages
-
Manageability (MGBL) Messages
-
Operating System (OS) Messages
-
Platform Messages
-
Quality of Service (QoS) Messages
-
Routing Messages
-
Security Messages
-
Services Messages
-
Simple Network Management Protocol (SNMP) Messages
-
System Database Messages
-
Index
-
FeedbackTable Of Contents
Fabric Messages
This section contains all Fabric (hardware and software both) related System Error Messages. The following facility codes are represented in this module:
•
HFR_FSDB_FADB_LTRACE Messages
FAB_SVR Messages
Error Message%FABRIC-FAB_SVR-7-ERR_ASIC_INIT Failed to initialize the the CPU control ASIC interface to [chars]: [chars]. Exiting...
Explanation Fabric server encountered an error while initializing the CPU control ASIC to either receive packets from the fabricq ASIC or transmit packets from the ingressq ASIC. This is crucial for the process and is automatically restarted on this failure.
Recommended Action If problem either persists (following a process restart) then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FAB_SVR-7-ERR_ASIC_INIT Failed to initialize the the CPU control ASIC interface to [chars]: [chars]. Exiting...
Explanation Fabric server encountered an error while initializing the CPU control ASIC to either receive packets from the fabricq ASIC or transmit packets from the ingressq ASIC. This is crucial for the process and is automatically restarted on this failure.
Recommended Action If problem either persists (following a process restart) then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FAB_SVR-7-ERR_EVENT_CONN_CREATE Failed to create event connection to EVM, Reason: [chars]([dec]). Exiting...
Explanation Fabric server encountered an error while trying to create a connection to event manager to manage the posix message queue. This facility is deemed crucial and the process automatically restarts on this failure.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_EVENT_CONN_CREATE Failed to create event connection to EVM, Reason: [chars]([dec]). Exiting...
Explanation Fabric server encountered an error while trying to create a connection to event manager to manage the posix message queue. This facility is deemed crucial and the process automatically restarts on this failure.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_EVENT_CONN_EVM_HANDLER Failed to register event handler, Reason: [chars]([dec]). Exiting...
Explanation Fabric server encountered an error while trying to register event handler for the posix message queue. This facility is deemed crucial and the process automatically restarts on this failure.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_EVENT_CONN_EVM_HANDLER Failed to register event handler, Reason: [chars]([dec]). Exiting...
Explanation Fabric server encountered an error while trying to register event handler for the posix message queue. This facility is deemed crucial and the process automatically restarts on this failure.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_EVENT_CONN_NOTIFY Failed to register handler for disconnection with EVM, Reason: [chars]([dec]). Exiting...
Explanation Fabric server encountered an error while trying to register event handler for disconnection or connection error event. This facility is deemed crucial and the process automatically restarts on this failure.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_EVENT_CONN_NOTIFY Failed to register handler for disconnection with EVM, Reason: [chars]([dec]). Exiting...
Explanation Fabric server encountered an error while trying to register event handler for disconnection or connection error event. This facility is deemed crucial and the process automatically restarts on this failure.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_EVENT_CONN_OPEN Failed to open connection with EVM, Reason: [chars]([dec]). Exiting...
Explanation Fabric server encountered an error while trying to open connection with event manager. This facility is deemed crucial and the process automatically restarts on this failure.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_EVENT_CONN_OPEN Failed to open connection with EVM, Reason: [chars]([dec]). Exiting...
Explanation Fabric server encountered an error while trying to open connection with event manager. This facility is deemed crucial and the process automatically restarts on this failure.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_EVM_CREATE Failed to create the event manager. Reason: [chars]. Exiting...
Explanation Fabric server encountered an error while attempting to create an event manager. This failures affects the ability of the process to service various messages / pulses from other threads / processes. This facility is deemed crucial and the process automatically restarts on this failure. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_EVM_CREATE Failed to create the event manager. Reason: [chars]. Exiting...
Explanation Fabric server encountered an error while attempting to create an event manager. This failures affects the ability of the process to service various messages / pulses from other threads / processes. This facility is deemed crucial and the process automatically restarts on this failure. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_INIT [chars] during the initialization. Reason: [chars]. Exiting...
Explanation Fabric server encountered the specified error during the initialization sequence. This facility is deemed crucial and hence the process is automatically restarted on this failure. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_INIT [chars] during the initialization. Reason: [chars]. Exiting...
Explanation Fabric server encountered the specified error during the initialization sequence. This facility is deemed crucial and hence the process is automatically restarted on this failure. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%FABRIC-FAB_SVR-7-ERR_THREAD_ATTRIBUTE Failed to set the thread attribute: [chars]. Exiting...
Explanation Fabric server encountered an error while setting the thread attribute during the process initialization sequence. This is crucial for the process and is automatically restarted on this failure.
Recommended Action If the problem is experienced only by this process in the system, restart the fabric server process by executing the following command at the CLI of the active RP: process restart fab_svr location loc If problem either persists (following a process restart) or also noticed on other processes then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FAB_SVR-7-ERR_THREAD_ATTRIBUTE Failed to set the thread attribute: [chars]. Exiting...
Explanation Fabric server encountered an error while setting the thread attribute during the process initialization sequence. This is crucial for the process and is automatically restarted on this failure.
Recommended Action If the problem is experienced only by this process in the system, restart the fabric server process by executing the following command at the CLI of the active RP: process restart fab_svr location loc If problem either persists (following a process restart) or also noticed on other processes then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FAB_SVR-7-ERR_THREAD_MUTEX_INIT Failed to initialize a mutex for client with ID [dec]: [chars]. Exiting...
Explanation Fabric server encountered an error while creating a mutex for use by a client with the specified ID. This is crucial for the process and is automatically restarted on this failure.
Recommended Action If the problem is experienced only by this process in the system, restart the fabric server process by executing the following command at the CLI of the active RP: process restart fab_svr location loc If problem either persists (following a process restart) or also noticed on other processes then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FAB_SVR-7-ERR_THREAD_MUTEX_INIT Failed to initialize a mutex for client with ID [dec]: [chars]. Exiting...
Explanation Fabric server encountered an error while creating a mutex for use by a client with the specified ID. This is crucial for the process and is automatically restarted on this failure.
Recommended Action If the problem is experienced only by this process in the system, restart the fabric server process by executing the following command at the CLI of the active RP: process restart fab_svr location loc If problem either persists (following a process restart) or also noticed on other processes then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FABQ Messages
Error Message%FABRIC-FABQ-0-PRP3_FAULT_RECOVERY_ERR The fault recovery procedure for the ToFab component of the fabric driver has failed. The root fault was: [chars]
Explanation When a hardware fault occurs and the device driver cannot correct it, the Platform Manager is required to reset the ASICs. This error indicates that the Platform Manager failed to reset the ASICs and the hardware on the PRP may not be in an operational state. This condition affects the functionality of the entire router. %s is the Interrupt Source.
Recommended Action If the system has not failed over automatically and a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0 ' where x is the slot of route processor that generated the error. If no redundant RP is configured you will need to reboot the router by issuing the reload command. Call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-2-PRP3_DRVR_INIT_ERROR Process initialization failed: ([chars]%s)
Explanation PRP fabric queue process failed to initialize. The fabric driver process handles fabric connectivity. It initializes the packet FPGA and coordinates with that fabric DLLs that allow applications to send and recieve packets via the fabric. An unrecoverable failure of the process may prevent this route processor from communicating with other cards in the chassis. %s - indicates the reason for the failure. %s - is the error reason.
Recommended Action If a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0' where x is the slot of route processor that generated the error. If no redundant RP is configured, you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-2-PRP3_PKT_INIT_ERROR Packet carving failed to initialize: ([chars]%s)
Explanation Initial carving of a packet particle pool failed. Platform specific memory region, packet header and particle pool configuration information are required by the generic packet manager process (PAKMAN) to operate. A failure in packet carving initialization may prevent this route processor from communicating with other cards in the chassis. %s - indicates the reason for the failure. %s - is the error reason.
Recommended Action If a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0' where x is the slot of route processor that generated the error. If no redundant RP is configured, you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-FATAL FABQ: fatal error encountered, reason equals [chars]
Explanation Fabric Queue 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%FABRIC-FABQ-3-PKT_INIT_FAIL PKT_INIT: [chars] failed, rc equals [dec], reason:[chars]
Explanation Packet carving function has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PKT_INIT_POOL PKT_INIT: particle_multi_pool_define failed ([chars]), rc equals [dec], reason:[chars]
Explanation Initial carving of a packet particle pool has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PRP3_FABMSG Fabric messaging infrastructure error: ([chars]%s)
Explanation PRP fabric messaging infrastructure failed. The fabric driver process handles fabric connectivity. It initializes the packet FPGA and coordinates with that fabric DLLs that allow applications to send and recieve packets via the fabric. An unrecoverable failure of the process may prevent this route processor from communicating with other cards in the chassis. %s - indicates the reason for the failure. %s - is the error reason.
Recommended Action If a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0' where x is the slot of route processor that generated the error. If no redundant RP is configured, you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PRP3_FRFAB_PKT_NO_STREAM Client([dec]) Port([dec]) From Fabric Packet from slot [dec] has invalid Stream ID([dec])
Explanation The packet received from the fabric begins with a header with Stream ID not initialized. The issue can happen due to hardware issue or the sender of the packet encoded invalid information in the packet header. %d - Client ID. Every process that uses the fabric API has an unique Client ID. %d - Port number (0 to 15) %d - Sender's slot number (0 to 15) %d - Stream ID encoded in the packet's header
Recommended Action If the error recurs very frequently call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PRP3_FRFAB_PKT_STARTOFFSET Client([dec]) Port([dec]) From Fabric Packet from slot [dec] has invalid Start Offset([dec])
Explanation The packet received from the fabric begins with a header with Start Offset less than the required. This suggests the packet is corrupted. The issue can happen due to hardware issue or the sender of the packet encoded invalid information in the packet header. %d - Client ID. Every process that uses the fabric API has an unique Client ID. %d - Port number (0 to 15) %d - Sender's slot number (0 to 15) %d - Start Offset encoded in the packet's header
Recommended Action If the error recurs very frequently call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PRP3_FRFAB_TAIL_PAR_ERR Client([dec]) Port([dec]) Fabric FPGA detects parity error from a packet received from the fabric
Explanation The Hummer detects a parity error on a packet received from the fabric. This is likely due to a hardware issue, or software misconfigured the hardware. %d - Client ID. Every process that uses the fabric API has an unique Client ID. %d - Port number (0 to 15)
Recommended Action The prp3_fabric_driver process should be able to detect the error and decide to reset fabric FPGA if necessary. If the error is persistent, and router traffic is affected, and if the system has not failed over automatically and a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0 ' where x is the slot of route processor that generated the error. If no redundant RP is configured you will need to reboot the router by issuing the reload command. Call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PRP3_HW_IRQ_ERR Port([dec]) Interrupt([dec]) - [chars]: [chars]
Explanation An error is detected when the software is trying to service an interrupt from the Hummer FPGA. Hummer is the fabric packet processing FPGA on the route processor. There are 16 bidirectional ports for 16 different traffic streams. A Hummer port needs to be enabled in the hardware level in order to function. A failure in servicing the Hummer interrupt may prevent this route processor from communicating with other cards in the chassis. %d - indicates the port number (0 to 15) %d - interrupt number that identifies the type %s - a decription of the interrupt event failure %s - is the error reason
Recommended Action Try restarting the process where the error message was found. Otherwise, try the following: If a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0' where x is the slot of route processor that generated the error. If no redundant RP is configured, you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PRP3_IRQ_ERR Fabric FPGA Error Interrupt: [chars]
Explanation An error is detected when the software is trying to service an interrupt from the Hummer fabric FPGA. Hummer is the fabric packet processing FPGA on the route processor. There are 16 bidirectional ports for 16 different traffic streams. A Hummer port needs to be enabled in the hardware level in order to function. An error status interrupt may indicate a hardware condition that may prevent this route processor from communicating with other cards in the chassis.
Recommended Action If a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0' where x is the slot of route processor that generated the error. If no redundant RP is configured, you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PRP3_PORT_DISABLE_ERR Cannot disable port([dec]): [chars]
Explanation Failed to disable Hummer port. Hummer is the fabric packet processing FPGA on the route processor. There are 16 bidirectional ports for 16 different traffic streams. A Hummer port needs to be enabled in the hardware level in order to function. A failure in disabling the Hummer port may prevent this route processor from communicating with other cards in the chassis. It points to a HW issue or a serious software defects. %d - indicates the port number (0 to 15) %s - is the error reason.
Recommended Action Try restarting the process where the error message was found. Otherwise, try the following: If a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0' where x is the slot of route processor that generated the error. If no redundant RP is configured, you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PRP3_PORT_ENABLE_ERR Cannot enable port([dec]): [chars]
Explanation Failed to enable Hummer port. Hummer is the fabric packet processing FPGA on the route processor. There are 16 bidirectional ports for 16 different traffic streams. A Hummer port needs to be enabled in the hardware level in order to function. A failure in enabling the Hummer port may prevent this route processor from communicating with other cards in the chassis. %d - indicates the port number (0 to 15) %s - is the error reason.
Recommended Action Try restarting the process where the error message was found. Otherwise, try the following: If a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0' where x is the slot of route processor that generated the error. If no redundant RP is configured, you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PRP3_REUSE_NO_BUFFER Client([dec]) Port([dec]) Packet passed to client cannot be reused since there is no buffer
Explanation The packet processing code formats packets from the fabric and passes them to the clients. When the client finished with the packet, the packet processing code cannot reuse the packet buffer because none is found associated with the packet. The issue can happen due to a software issue with the client. %d - Client ID. Every process that uses the fabric API has an unique Client ID. %d - Port number (0 to 15)
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PRP3_SHM shared memory failed during [chars]: [chars]
Explanation An internal software error occurred that prevented the fabric interface from working properly with shared memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-PRP3_TOFAB_QUEUE_BLOCKED RP To Fabric Queue slot:[dec] is blocked, report fault to sysldr
Explanation The PRP3 to fabric queue of the particular priority and slot is blocked. This means packets that go that slot of that priority will fail. In addition, at least one of the multicast queues (high or low priority) is blocked as well. This likely means the particular slot is failing to accept packets and will cause backpressure on the PRP to fabric queue. Because of hardware design, if a multicast packet includes the one faulty slot then it will be stuck in the tofab multicast queue, and subsequent multicast packets will be stuck even if they do not include the faulty slot in their slotmask. Having the unicast queue blocked is somewhat allowable, but having the multicast queue blocked is not acceptable. This error message is raised when both unicast and multicast are blocked. In order to alleviate this problem, the fault is sent to sysldr, for sylsdr to decide to reload the slot. It is very likely that the problem slot was not accepting packets. slot:%d is the slot that is back pressuring to the PRP
Recommended Action The slot should be reloaded to correct the problem, if not done already by sysldr. Copy the error message exactly as it appears and report it to your Cisco technical representative together with the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-3-SHOW_ERR FABQ_SHOW: fatal error encountered: [chars]
Explanation Error while executing a show command
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABQ-6-PKT_INIT_INFO PKT_INIT: pak mem size:[hex], pak mem start: [hex], pak scaling:[dec]
Explanation Information on packet memory carving
Recommended Action This is information and does not require any correction.
Error Message%FABRIC-FABQ-7-PRP3_PKT_INIT_INFO Packet initialization: pak mem size:[hex], pak mem start: [hex], pak scaling:[dec]
Explanation Information on packet memory carving.
Recommended Action This is informational and does not require any correction.
FABRIC_DRIVER_LITE Messages
Error Message%FABRIC-FABRIC_DRIVER_LITE-3-ERR_ASIC_ACCESS_EXCEPTION Fabric ASIC access timed out (reported by lite process)
Explanation This indicates that the fabric ASIC failed to acknowledge an access request from the CPU. This can happen if the host CPU tries to access an address that is out of range for the ASIC. Also, accessing a register from a block that is still in the logic reset state could stall this access and subsequent accesses to the ASIC.
Recommended Action If this condition is noticed for every access to the ASIC, then the ASIC is possibly wedged. Resetting the ASIC or reloading the fabric card will help to recover from this condition. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRIVER_LITE-3-ERR_DRIVER_INIT Initialization of fabric driver lite failed: [chars] ; exiting...
Explanation Fabric driver encountered the annunciated error during the driver initialization. The System Manager process (sysmgr) will automatically respawn the (sfe_drvr_lite) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRIVER_LITE-3-ERR_EVM_CREATE Failed to create event manager for '[chars]'
Explanation The Fabric driver was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr_lite) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRIVER_LITE-3-ERR_SHMEM_INIT Shared Memory Error: [chars]
Explanation Attempt to init/open the shared memory fails
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRIVER_LITE-3-ERR_THREAD_ATTRIBUTE FABRIC driver lite failed to change interupt thread to an IO thread: [chars]
Explanation The Fabric driver was unable to change the interrupt thread to an IO thread. Because of this failure, the interupt thread will not be able to receive the interupt thread events. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr_lite) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRIVER_LITE-4-ERR_LTRACE_INIT Fabric driver lite failed to initialize the ltrace - rc equals [chars]
Explanation The Fabric driver could not open/initialize the ltrace buffer. The Fabric driver and the system should stll function as normal, with the exception that ltrace will not be available for sfe_drvr process.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRIVER_LITE-6-ASIC_INITIALIZED Fabric ASICs initialized (reported by lite process)
Explanation This indicates Fabric ASICs are initialized and is expected during normal operation.
Recommended Action No action is required.
FABRIC_DRVR Messages
Error Message%FABRIC-FABRIC_DRVR-3-ERR_ASIC_ACCESS_EXCEPTION Fabric ASIC access timed out.
Explanation This indicates that the fabric ASIC failed to acknowledge an access request from the CPU. This can happen if the host CPU tries to access an address that is out of range for the ASIC. Also, accessing a register from a block that is still in the logic reset state could stall this access and subsequent accesses to the ASIC.
Recommended Action If this condition is noticed for every access to the ASIC, then the ASIC is possibly wedged. Resetting the ASIC or reloading the fabric card will help to recover from this condition. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_BOARD_PLD_VERSION Fabric Board PLD Version ([dec]) not supported. Upgrade to latest.
Explanation This indicates that the fabric board is running with PLD version that is not supported. Version lower than (0x1c) is not supported. Please upgrade to the latest PLD Version.
Recommended Action Shut down the plane associated to this fabric card, and upgrade the PLD Version of this board. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_DRV_INIT Initialization of fabric driver failed: [chars] ; exiting...
Explanation Fabric driver encountered the annunciated error during the driver initialization. The System Manager process (sysmgr) will automatically respawn the (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_DRV_INIT Initialization of fabric driver failed: [chars] ; exiting...
Explanation Fabric driver encountered the annunciated error during the driver initialization. The System Manager process (sysmgr) will automatically respawn the (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_EVM_CREATE Failed to create event manager for '[chars]'
Explanation The Fabric driver was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_EVM_CREATE Failed to create event manager for '[chars]'
Explanation The Fabric driver was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_FGID_ACCESS Fabric Board Going down. FGID access being aborted.
Explanation One or more ASICs for the stage on the fabric card are being reset. Hence this multicast FGID access operation for the specified stage is aborted. This may be seen on any SM node going down, during asic reset cleanup process.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_FGID_REFRESH Request [dec] to refresh FGID entry [hex].
Explanation An FGID entry is disabled following a parity error. A request to refresh the entry is issued.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_FGID_REFRESH_RETRY Failed to refresh FGID entry. Reload the fabric card.
Explanation An FGID entry is disabled following a parity error. Request to refresh the entry wasn't entertained. This will reload the fabric card to recover.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_FGID_WRITE Device(s) being reset. [chars] FGID write to offset [hex] aborted.
Explanation One or more ASICs for the stage on the fabric card are in being reset. Hence this multicast FGID write operation for the specified stage is aborted.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_MAX_TOPO_TIME_OUT Maximum attempts to receive topology information exceeded. Restarting sfe_drvr ...
Explanation This indicates that the maximum tries for the driver to receive the necessary topology information to initialize the asic has exceeded. The driver will not continually re-request topology information.
Recommended Action Check if all the required fabric cards are UP and running.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_POD_INIT Failed to [chars] POD (node: [hex], module: [hex], asic: [unsigned int], POD:[unsigned int]) - error : [chars]; exiting...
Explanation Fabric Driver failed to initialize one of the POD hardware modules. The System Manager process (sysmgr) will automatically respawn the (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_POD_INIT Failed to initialize POD for node: [hex], error : [chars]; exiting...
Explanation Fabric Driver failed to initialize one of the POD hardware modules. The System Manager process (sysmgr) will automatically respawn the (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_STUCK_BARRIER_FLOW Barriers stuck for type [dec] at phase [dec] [curr: [hex] prev: [hex]] on [chars].
Explanation Barrier flow of certain type is stuck at identified phase on the specified ASIC.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_THREAD_ATTRIBUTE FABRIC driver failed to change interupt thread to an IO thread: [chars]
Explanation The Fabric driver was unable to change the interrupt thread to an IO thread. Because of this failure, the interupt thread will not be able to receive the interupt thread events. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_THREAD_ATTRIBUTE FABRIC driver failed to change interupt thread to an IO thread: [chars]
Explanation The Fabric driver was unable to change the interrupt thread to an IO thread. Because of this failure, the interupt thread will not be able to receive the interupt thread events. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_TIMER_START Leaf Timer Failed to start. Timer Type: [dec].
Explanation Fabric driver could not start timer.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-3-ERR_WAITING_FOR_TOPO_TIMED_OUT Driver timed out waiting for topology information. Attempt re-request for topology.
Explanation This indicates that the driver has not received the necessary topology information to initialize the asic. The driver will continually re-request topology. This message can also be seen in a multichassis system when a fabric card is pulled out or powered down and the other end is still up and running or if the plane config for this card is missing.
Recommended Action Check if all the required fabric cards are UP and running.
Error Message%FABRIC-FABRIC_DRVR-3-ERRRATE_EXCEED_GLACIAL [chars] ; Node Key equals [hex]
Explanation The Fabric driver encountered the annunciated error. For Error Node Keys - 0x1050016; 0x1050018; 0x105001A : This indicates a hardware problem in Fabric ASIC. Sysmgr will reload the node up to a fixed number of times the error is encountered, to recover. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERRRATE_EXCEED_GLACIAL [chars] ; Node Key equals [hex]
Explanation The Fabric driver encountered the annunciated error. For Error Node Keys - 0x1050016; 0x1050018; 0x105001A : This indicates a hardware problem in Fabric ASIC. Sysmgr will reload the node up to a fixed number of times the error is encountered, to recover. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERRRATE_EXCEED_NO_LIMIT [chars]
Explanation The fabric driver encountered the annunciated error. Sysmgr will reload the node up to a fixed number of times the error is encountered, to recover. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERRRATE_EXCEED_NO_LIMIT [chars]
Explanation The fabric driver encountered the annunciated error. Sysmgr will reload the node up to a fixed number of times the error is encountered, to recover. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERRRATE_EXCEED_SLOW [chars]
Explanation The fabric driver encountered the annunciated error. Sysmgr will reload the node up to a fixed number of times the error is encountered, to recover. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-3-ERRRATE_EXCEED_SLOW [chars]
Explanation The fabric driver encountered the annunciated error. Sysmgr will reload the node up to a fixed number of times the error is encountered, to recover. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-4-ERR_LTRACE_INIT Fabric driver failed to initialize the ltrace - rc equals [chars]
Explanation The Fabric driver could not open/initialize the ltrace buffer. The Fabric driver and the system should stll function as normal, with the exception that ltrace will not be available for sfe_drvr process.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-4-ERR_LTRACE_INIT Fabric driver failed to initialize the ltrace - rc equals [chars]
Explanation The Fabric driver could not open/initialize the ltrace buffer. The Fabric driver and the system should stll function as normal, with the exception that ltrace will not be available for sfe_drvr process.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-6-ASIC_INITIALIZED Fabric ASICs initialized
Explanation This indicates Fabric ASICs are initialized and is expected during normal operation.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-6-ASIC_INITIALIZED Fabric ASICs initialized
Explanation This indicates Fabric ASICs are initialized and is expected during normal operation.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-6-BARRIER_FLOW_STARTED Barrier flow started on all ASICs
Explanation Barriers started flowing on all the nodes/types.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-6-DLL_LOAD SEA ASIC driver loaded
Explanation Fabric driver loaded for the SEA asics.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-6-MISSING_PLANE_CONFIG Plane config is missing or inconsistent.
Explanation Missing admin plane configuration for this module.
Recommended Action Check the admin plane configuration to ensure that it corresponds with the actual physical topology of the system. If this configuration looks correct then contact support, otherwise correct the configuration and the system should recover.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_BP_CFG [chars]: Error in Back pressure configuration, BP Groups : [dec], [dec], [dec]
Explanation The Fabric driver encountered an error in back pressure configuration. This indicates BP configuration received from the fabric control software is incorrect. If this condition prevails, it could impact data traffic when fabric gets congested.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_BP_CFG [chars]: Error in Back pressure configuration, BP Groups : [dec], [dec], [dec]
Explanation The Fabric driver encountered an error in back pressure configuration. This indicates BP configuration received from the fabric control software is incorrect. If this condition prevails, it could impact data traffic when fabric gets congested.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_DEBUG_REG Fabric driver failed to register with the debug; rc equals [chars]
Explanation The Fabric driver was unable to register with the debug. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_DEBUG_REG Fabric driver failed to register with the debug; rc equals [chars]
Explanation The Fabric driver was unable to register with the debug. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_INTERNAL_SW [chars]
Explanation The Fabric driver encountered the annunciated internal SW error. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_INTERNAL_SW [chars]
Explanation The Fabric driver encountered the annunciated internal SW error. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_LINK_TOPO Topology mismatch for [chars]
Explanation The upstream information received from idle cells on this link does not match with FSDB information.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERR_LINK_TOPO Topology mismatch for [chars]
Explanation The upstream information received from idle cells on this link does not match with FSDB information.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-ERRRATE_EXCEED_DEBUG [chars]
Explanation The fabric driver encountered the annunciated error. The Fabric driver and the System should still continue to function as normal.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-7-ERRRATE_EXCEED_DEBUG [chars]
Explanation The fabric driver encountered the annunciated error. The Fabric driver and the System should still continue to function as normal.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_DRVR-7-LINK_SHUT_DOWN Fabric Link: [chars] - Shutdown: [chars]
Explanation The Fabric driver encountered an error on the annunciated Fabric Switching Element link and the link is brought down.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_DRVR-7-LINK_SHUT_DOWN Fabric Link: [chars] - Shutdown: [chars]
Explanation The Fabric driver encountered an error on the annunciated Fabric Switching Element link and the link is brought down.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FABRIC_SRVR Messages
Error Message%FABRIC-FABRIC_SRVR-3-ERR_ANNOUNCE EES announcement failed, rc equals [chars]
Explanation EES domain enabling failed. This will prevent ucd/mcd messages to be exchanged between the applications and driver.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_SRVR-3-ERR_DRV_INIT Initialization of fabric driver failed: [chars] ; exiting...
Explanation Fabric driver encountered the annunciated error during the driver initialization. The System Manager process (sysmgr) will automatically respawn the (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-3-ERR_DRV_INIT Initialization of fabric driver failed: [chars] ; exiting...
Explanation Fabric driver encountered the annunciated error during the driver initialization. The System Manager process (sysmgr) will automatically respawn the (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-3-ERR_EES_REG EES registration failed, rc equals [chars]
Explanation EES domain enabling failed. This will prevent ucd/mcd messages to be exchanged between the applications and driver.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_SRVR-3-ERR_ENABLE [chars] domain enable failed for ucd [dec], rc equals [chars]
Explanation EES domain enabling failed. This will prevent ucd/mcd messages to be exchanged between the applications and driver.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_SRVR-3-ERR_EVM_CREATE Failed to create event manager for '[chars]'
Explanation The Fabric driver was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-3-ERR_EVM_CREATE Failed to create event manager for '[chars]'
Explanation The Fabric driver was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-3-ERR_FGID_CONS_THREAD Process sfe_drvr will be restarted. Asic status(oper_up/avl_map) equals [hex]/[hex]. Cfg availability (topo/oob/bpe) equals [hex]/[hex]/[hex].
Explanation This is an error message and is seen in the abnormal condition when the fgid consumer thread fails to start successfully. Fgid consumer thread will successfully start if all the asics are operationally up. If the asics do not report oper-up within the timeout period fgid_consumer thread cannot be started. As a consequence SFE Driver is restarted. avl_map is a bitmap representing all the asics that are required to be operationally up to successfully start the fgid consumer thread. The oper_up bitmap indicates the asics that are currently operationally up. The topo/oob/bpe information indicates which of the asics have received the specific (topo/oob/bpe) configuration.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_SRVR-3-RESET_ALL_ASICS FDI request to reset all the ASICs on the fabric board.
Explanation Process a request received from FSDB to reset all the ASICs on the fabric card.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_SRVR-4-ERR_ECM_CREATE Failed to create Event Connection Manager : [chars]
Explanation The Fabric driver was unable to create an event connection manager for EDM. Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-4-ERR_ECM_CREATE Failed to create Event Connection Manager : [chars]
Explanation The Fabric driver was unable to create an event connection manager for EDM. Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-4-ERR_ECM_NOTIFY Failed to register with ECM to receive notifications : [chars]
Explanation The Fabric driver was unable register with ECM to receive notifications when the connection to Sysdb goes down/up/closed. Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-4-ERR_ECM_NOTIFY Failed to register with ECM to receive notifications : [chars]
Explanation The Fabric driver was unable register with ECM to receive notifications when the connection to Sysdb goes down/up/closed. Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-4-ERR_LTRACE_INIT Fabric driver failed to initialize the ltrace - rc equals [chars]
Explanation The Fabric driver could not open/initialize the ltrace buffer. The Fabric driver and the system should stll function as normal, with the exception that ltrace will not be available for sfe_drvr process.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_SRVR-4-ERR_LTRACE_INIT Fabric driver failed to initialize the ltrace - rc equals [chars]
Explanation The Fabric driver could not open/initialize the ltrace buffer. The Fabric driver and the system should stll function as normal, with the exception that ltrace will not be available for sfe_drvr process.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_SRVR-6-ASIC_RESET_REASONS Asics being reset, Respawn Count equals [dec] Checkpoint status equals [dec] Interrupt Status equals [hex]
Explanation This message is seen when fabric ASICS are being reset. The status reported here provide information about the reason for the reset.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_SRVR-6-FAB_MODULE [chars]
Explanation This is to give infomation regarding fabric module type.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_SRVR-6-FAB_MODULE [chars]
Explanation This is to give infomation regarding fabric module type.
Recommended Action No action is required.
Error Message%FABRIC-FABRIC_SRVR-7-ERR_BAG_REG [chars]
Explanation The Fabric driver was unable to register Fabric driver bags. The Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-7-ERR_BAG_REG [chars]
Explanation The Fabric driver was unable to register Fabric driver bags. The Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-7-ERR_DEBUG_INIT Fabric driver failed to initialize the debug; rc equals [chars]
Explanation The Fabric driver was unable to initialize debug. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-7-ERR_DEBUG_INIT Fabric driver failed to initialize the debug; rc equals [chars]
Explanation The Fabric driver was unable to initialize debug. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-7-ERR_DEBUG_REG Fabric driver failed to register with the debug; rc equals [chars]
Explanation The Fabric driver was unable to register with the debug. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-7-ERR_DEBUG_REG Fabric driver failed to register with the debug; rc equals [chars]
Explanation The Fabric driver was unable to register with the debug. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-7-ERR_INTERNAL_SW [chars]
Explanation The Fabric driver encountered the annunciated internal SW error. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-7-ERR_INTERNAL_SW [chars]
Explanation The Fabric driver encountered the annunciated internal SW error. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-7-ERR_SYSDB_EDM_REG [chars]
Explanation The Fabric driver was unable to become an external data manager (EDM) despite having a connection to SysDB. The operation will be retried. The Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRIC_SRVR-7-ERR_SYSDB_EDM_REG [chars]
Explanation The Fabric driver was unable to become an external data manager (EDM) despite having a connection to SysDB. The operation will be retried. The Fabric driver and the System should continue to function as normal, with the exception that the 'show' commands for Fabric driver will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FABRICQ_MGR Messages
Error Message%FABRIC-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%FABRIC-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%FABRIC-FABRICQ_MGR-3-ERR_MEM_ALLOC Error Allocating [dec] 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%FABRIC-FABRICQ_MGR-3-ERR_MEM_ALLOC Error Allocating [dec] 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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-FABRICQ-4-ERR_ASIC_MBE Fabricq Asic [dec] detected multibit error(s). Details: [chars]
Explanation Fabricq Asic encountered a memory uncorrectable error
Recommended Action The multi-bit errors can happen in one of many blocks of the fabricq ASIC. One of them is the Fabric Interface (FI). If these error messages are generated for short intervals for FI links when a fabric card is disabled / reloaded / OIR'ed, then they are harmless. If these messages continue for more than 2 minutes, with incrementing uncorrectable error (UCE) counters, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FABRICQ-4-ERR_ASIC_MBE Fabricq Asic [dec] detected multibit error(s). Details: [chars]
Explanation Fabricq Asic encountered a memory uncorrectable error
Recommended Action The multi-bit errors can happen in one of many blocks of the fabricq ASIC. One of them is the Fabric Interface (FI). If these error messages are generated for short intervals for FI links when a fabric card is disabled / reloaded / OIR'ed, then they are harmless. If these messages continue for more than 2 minutes, with incrementing uncorrectable error (UCE) counters, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-FABRICQ-4-FI_LINK_BRINGDOWN Fabric link [dec] on ASIC [dec] may be brought down due to too many errors
Explanation A fabric link was brought down due to too many UCE or parity errors.
Recommended Action *SUPPORT*
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-FABRICQ-6-URG_CTX Minor error in PCL of Fabricq asic [dec]. Urgent Context exceeded 5 equals [hex]
Explanation Fabricq encountered a PCL Urgent Context error
Recommended Action *SUPPORT*
Error Message%FABRIC-FABRICQ-6-URG_CTX Minor error in PCL of Fabricq asic [dec]. Urgent Context exceeded 5 equals [hex]
Explanation Fabricq encountered a PCL Urgent Context error
Recommended Action *SUPPORT*
Error Message%FABRIC-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.
Error Message%FABRIC-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.
FDI Messages
Error Message%FABRIC-FDI-2-ERR_CONNECTION [chars]; Conn_id equals [dec] Conn_name equals [chars]
Explanation The FDI library encountered the annunciated connection error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-2-ERR_CONNECTION [chars]; Conn_id equals [dec] Conn_name equals [chars]
Explanation The FDI library encountered the annunciated connection error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-2-ERR_INTERNAL_SW [chars] ; rc equals [chars]
Explanation The FDI encountered the annunciated internal sw error.
Recommended Action No action is required.
Error Message%FABRIC-FDI-2-ERR_INTERNAL_SW [chars] ; rc equals [chars]
Explanation The FDI encountered the annunciated internal sw error.
Recommended Action No action is required.
Error Message%FABRIC-FDI-2-ERR_MSG_TYPE FDI received incorrect message type - [dec] from mid ([dec]:[dec]:[dec])
Explanation FDI received incorrect message type and failed to process the message. The System Manager process (sysmgr) will automatically respawn the process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-3-ERR_BUFF_Q FDI Buffers are full; Conn_id [dec]. Data_Size [dec]. Buffer_states ([dec] [dec])
Explanation FDI buffers are full and FDI can't buffer any more messages. The System Manager process (sysmgr) will automatically respawn the process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action Examine the state of GSP on the node of the FDI application. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-3-ERR_BUFF_Q FDI Buffers are full; Conn_id [dec]. Data_Size [dec]. Buffer_states ([dec] [dec])
Explanation FDI buffers are full and FDI can't buffer any more messages. Buffer will fill up for 2 main reasons: 1. Receiver is blocked and not able to return ack 2. Some kind of transport problem In such cases, FDI would flap the connection and flush the buffers hoping that conditions 1 or 2 were transient.
Recommended Action Examine the state of GSP on the node of the FDI application. Collect gsp stats for the sender and receiver application. Also determine if receiver application was ever blocked during the time buffer went full. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-3-ERR_CORRUPT_MSG Possible Corrupt Msg Returned By GSP Case ([chars])
Explanation 1. Possible null msg returned back by gsp 2. Possible corrupt msg causing msgtype outofbounds
Recommended Action Examine the state of GSP on the node of the FDI application. Collect gsp stats for the sender and receiver application. Also determine if receiver application was ever blocked during the time buffer went full. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-3-ERR_MSG_TYPE FDI received incorrect message type - [dec]
Explanation FDI received incorrect message type and failed to process the message. The System Manager process (sysmgr) will automatically respawn the process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_COMM_SYSTEM_ERROR IPC non blocking communication failed to group id: [dec], tag [hex] - id [dec], seq [dec], status [dec]: [chars]
Explanation The FDI Library uses gsp_group_memberset_nb ( non blocking api ). Any errors are communicated back via a callback. These errors are considered bad, since it is likely a member did not receive a message. These errors returned are communicated via this msg. This may indicate some transport issue.
Recommended Action Restart application may be required, if messages continued to be logged.
Error Message%FABRIC-FDI-7-ERR_DEBUG_CLEAN FDI library failed to cleanup FDI debug info in debug infrastructure ; rc equals [chars]
Explanation The FDI library was unable to cleanup FDI debug info in debug infrastructure. The System should still continue to function as normal.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_DEBUG_CLEAN FDI library failed to cleanup FDI debug info in debug infrastructure ; rc equals [chars]
Explanation The FDI library was unable to cleanup FDI debug info in debug infrastructure. The System should still continue to function as normal.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_DEBUG_INIT FDI library failed to initialize debug for fdi - [chars]; rc equals [chars]
Explanation The FDI library was unable to initialize debug. The FDI component and the System should still continue to function as normal, with the exception that the debugs will not be available for FDI.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_DEBUG_INIT FDI library failed to initialize debug for fdi - [chars]; rc equals [chars]
Explanation The FDI library was unable to initialize debug. The FDI component and the System should still continue to function as normal, with the exception that the debugs will not be available for FDI.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_DEBUG_REG FDI library failed to register with debug infrastructure ; rc equals [chars]
Explanation The FDI library was unable to register with debug infrastructure. The FDI component and the System should still continue to function as normal, with the exception that the debugs will not be available for FDI.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_DEBUG_REG FDI library failed to register with debug infrastructure ; rc equals [chars]
Explanation The FDI library was unable to register with debug infrastructure. The FDI component and the System should still continue to function as normal, with the exception that the debugs will not be available for FDI.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_EDM_INIT [chars]; rc equals [chars]
Explanation The FDI Library encountered the annunciated EDM Initialization error. The System should still continue to function as normal, with the exception that the 'show' commands for FDI will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_EDM_INIT [chars]; rc equals [chars]
Explanation The FDI Library encountered the annunciated EDM Initialization error. The System should still continue to function as normal, with the exception that the 'show' commands for FDI will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FDI-7-ERR_GROUP_MEMBER_ALREADY_EXISTS Group ([dec]) Member ([dec]:[dec]:[dec]) already exsts overriding with latest member info([dec]:[dec]:[dec]).
Explanation A member is attempting to be added to a group with an entry already present. The member likely did not get cleaned up correctly. Assumed latest member info is correct, and override existing entry.
Recommended Action No action is required.
Error Message%FABRIC-FDI-7-ERR_MEM_ALLOC FDI failed to allocate [dec] bytes
Explanation The FDI was unable to allocate memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%FABRIC-FDI-7-ERR_MEM_ALLOC FDI failed to allocate [dec] bytes
Explanation The FDI was unable to allocate memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%FABRIC-FDI-7-ERR_MEMBER_ALREADY_EXISTS Member [chars] entry already exists and registered. Updating with new member info.
Explanation The FDI Library has received a new member notification for a member that already exists in the FDI db, and registered. Possible that we failed to cleanup old member, or a delayed new member msg. There should be no system impact as FDI will just update with the latest info.
Recommended Action No action is required.
Error Message%FABRIC-FDI-7-ERR_MSG_SEQ_GT Out of sequence (greater than) message received from [chars] [chars] reset connection.
Explanation The FDI Library encountered an internal error with a message received. Since one message is active at one time, the message received should be the next expected seqnum. This may indicate system resource issue, or a period where system is heavily loaded. If message persists, application may need to be restarted.
Recommended Action Restart application may be required, if messages continued to be logged.
FEATURE_LPTS Messages
Error Message%FABRIC-FEATURE_LPTS-3-ERR_DOUBLE_FREE Double free of FGID [dec]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FEATURE_LPTS-3-ERR_DOUBLE_FREE Double free of FGID [dec]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FEATURE_LPTS-3-ERR_FGID_DB_RETRIES_EXCEEDED Number of unknown errors from FGID-DB ([dec]) has exceeded maximum
Explanation A software error occurred, when the PA attempted to allocate FGID's from the FGID aggregator.
Recommended Action The process will attempt to recover by restarting. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FEATURE_LPTS-3-ERR_UNALLOCATED_FREE Attempt to free unallocated FGID [dec]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FEATURE_LPTS-3-ERR_UNALLOCATED_FREE Attempt to free unallocated FGID [dec]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FEATURE_LPTS-3-ERR_UNKNOWN_FGID_DB_ERROR Unknown error from FGID-DB, [chars] FGID [dec] [[dec]]([dec], [dec]): [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FEATURE_LPTS-3-ERR_UNKNOWN_FGID_DB_ERROR Unknown error from FGID-DB, [chars] FGID [dec] [[dec]]([dec], [dec]): [chars]
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FGID_AGG Messages
Error Message%FABRIC-FGID_AGG-3-ERR_DEBUG_INIT fgid_aggregator unable to initialize dbg ; rc equals [chars]
Explanation The FGID Aggregator was unable to initialize debug. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_DEBUG_INIT fgid_aggregator unable to initialize dbg ; rc equals [chars]
Explanation The FGID Aggregator was unable to initialize debug. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_EVM_CREATE FGID Aggregator failed to create [chars] evm ; rc equals [chars]
Explanation The FGID aggregator was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_EVM_CREATE FGID Aggregator failed to create [chars] evm ; rc equals [chars]
Explanation The FGID aggregator was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_EVM_SYNC_ATTACH FGID Aggregator failed to attach [chars] to evm ; rc equals [chars]
Explanation The FGID Aggregator was unable to attach the indicated event handler to the event manager. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_EVM_SYNC_ATTACH FGID Aggregator failed to attach [chars] to evm ; rc equals [chars]
Explanation The FGID Aggregator was unable to attach the indicated event handler to the event manager. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_GSP [chars]: rc equals [chars]
Explanation The FGID Aggregator was unable to create/join GSP group. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_GSP [chars]: rc equals [chars]
Explanation The FGID Aggregator was unable to create/join GSP group. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_INTERNAL_SW [chars]; [chars]
Explanation The FGID Aggregator encountered the annunciated SW error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_INTERNAL_SW [chars]; [chars]
Explanation The FGID Aggregator encountered the annunciated SW error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_MEM_ALLOC FGID Aggregator unable to allocate [dec] bytes
Explanation The FGID Aggregator was unable to allocate memory. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_MEM_ALLOC FGID Aggregator unable to allocate [dec] bytes
Explanation The FGID Aggregator was unable to allocate memory. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_SYSMGR [chars]; rc equals [chars]
Explanation The FGID Aggregator encountered the annunciated sysmgr error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-3-ERR_SYSMGR [chars]; rc equals [chars]
Explanation The FGID Aggregator encountered the annunciated sysmgr error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_AGG-7-ERR_LTRACE_INIT FGID Aggregator failed to initialize the ltrace file [chars] : [chars]
Explanation The FGID Aggregator Could not open the annunciated ltrace buffer. The FGID component and the system should stll function as normal, with the exception that ltrace will not be available for fgid_aggregator process.
Recommended Action No action is required.
Error Message%FABRIC-FGID_AGG-7-ERR_LTRACE_INIT FGID Aggregator failed to initialize the ltrace file [chars] : [chars]
Explanation The FGID Aggregator Could not open the annunciated ltrace buffer. The FGID component and the system should stll function as normal, with the exception that ltrace will not be available for fgid_aggregator process.
Recommended Action No action is required.
FGID_ALLOC Messages
Error Message%FABRIC-FGID_ALLOC-3-ERR_EVM_CREATE FGID Allocator failed to create [chars] evm; rc equals [chars]
Explanation The FGID allocator was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_EVM_CREATE FGID Allocator failed to create [chars] evm; rc equals [chars]
Explanation The FGID allocator was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_GSP [chars]: rc equals [chars]
Explanation The FGID Allocator encountered the annunciated GSP error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_GSP [chars]: rc equals [chars]
Explanation The FGID Allocator encountered the annunciated GSP error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_INTERNAL_SW [chars] ; rc equals [chars]
Explanation The FGID Allocator encountered the annunciated internal SW error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_INTERNAL_SW [chars] ; rc equals [chars]
Explanation The FGID Allocator encountered the annunciated internal SW error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_MEM_ALLOC FGID Allocator failed to allocate [dec] bytes
Explanation The FGID Allocator was unable to allocate memory. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_MEM_ALLOC FGID Allocator failed to allocate [dec] bytes
Explanation The FGID Allocator was unable to allocate memory. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_SYSMGR [chars]; rc equals [chars]
Explanation The FGID Allocator encountered the annunciated sysmgr error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-3-ERR_SYSMGR [chars]; rc equals [chars]
Explanation The FGID Allocator encountered the annunciated sysmgr error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_BAG_REG FGID allocator failed to register FGID bags; rc equals [chars]
Explanation The FGID allocator was unable to register FGID bags. The FGID component and the System should continue to function as normal, with the exception that the 'show' commands for FGID allocator will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_BAG_REG FGID allocator failed to register FGID bags; rc equals [chars]
Explanation The FGID allocator was unable to register FGID bags. The FGID component and the System should continue to function as normal, with the exception that the 'show' commands for FGID allocator will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_CHKPT_INIT FGID Allocator failed to initialize the checkpoint library ; rc equals [chars]
Explanation The FGID Allocator was unable to initialize the checkpoint library. The fgid_allocator process may need restarting, if the errors persist.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_CHKPT_INIT FGID Allocator failed to initialize the checkpoint library ; rc equals [chars]
Explanation The FGID Allocator was unable to initialize the checkpoint library. The fgid_allocator process may need restarting, if the errors persist.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_CHKPT_ITERATE_START FGID Allocator failed to start to iterate Checkpoint table [chars]; rc equals [chars]
Explanation The FGID Allocator was unable to start to iterate checkpoint table. The fgid_allocator process may need restarting, if the errors persist.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_CHKPT_ITERATE_START FGID Allocator failed to start to iterate Checkpoint table [chars]; rc equals [chars]
Explanation The FGID Allocator was unable to start to iterate checkpoint table. The fgid_allocator process may need restarting, if the errors persist.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_CHKPT_REG FGID Allocator failed to register the Checkpoint table [chars] ; rc equals [chars]
Explanation The FGID Allocator was unable to register the checkpoint table. The fgid_allocator process may need restarting, if the errors persist.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_CHKPT_REG FGID Allocator failed to register the Checkpoint table [chars] ; rc equals [chars]
Explanation The FGID Allocator was unable to register the checkpoint table. The fgid_allocator process may need restarting, if the errors persist.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_DEBUG_INIT FGID Allocator failed to initialize debug ; rc equals [chars]
Explanation The FGID Allocator failed to initialize debug. The FGID component and the System should still continue to function as normal, with the exception that the debugs will not be available fgid_allocator process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_DEBUG_INIT FGID Allocator failed to initialize debug ; rc equals [chars]
Explanation The FGID Allocator failed to initialize debug. The FGID component and the System should still continue to function as normal, with the exception that the debugs will not be available fgid_allocator process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_LTRACE_INIT FGID Allocator failed to initialize the ltrace file [chars]; rc equals [chars]
Explanation The FGID Allocator could not open the annunciated ltrace buffer. The FGID component and the system should function as normal, with the exception that ltrace will not be available for fgid_aggregator process.
Recommended Action No action is required.
Error Message%FABRIC-FGID_ALLOC-7-ERR_LTRACE_INIT FGID Allocator failed to initialize the ltrace file [chars]; rc equals [chars]
Explanation The FGID Allocator could not open the annunciated ltrace buffer. The FGID component and the system should function as normal, with the exception that ltrace will not be available for fgid_aggregator process.
Recommended Action No action is required.
Error Message%FABRIC-FGID_ALLOC-7-ERR_SYSDB_BIND FGID Allocator failed to bind to Sysdb name space [chars]; rc equals [chars]
Explanation The FGID-DB allocator unable to bind to sysdb name space. The fgid_allocator may need restarting if the errors persist.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_SYSDB_BIND FGID Allocator failed to bind to Sysdb name space [chars]; rc equals [chars]
Explanation The FGID-DB allocator unable to bind to sysdb name space. The fgid_allocator may need restarting if the errors persist.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_SYSDB_EDM_REG FGID allocator failed to perform EDM registration; rc equals [chars]
Explanation The FGID allocator was unable to become an external data manager (EDM) despite having a connection to SysDB. The operation will be retried. The FGID component and the System should continue to function as normal, with the exception that the 'show' commands for FGID allocator will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_ALLOC-7-ERR_SYSDB_EDM_REG FGID allocator failed to perform EDM registration; rc equals [chars]
Explanation The FGID allocator was unable to become an external data manager (EDM) despite having a connection to SysDB. The operation will be retried. The FGID component and the System should continue to function as normal, with the exception that the 'show' commands for FGID allocator will not be available.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FGID_BCDL_CONSUMER Messages
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_BCDL [chars] ; rc equals [chars]
Explanation The BCDL Consumer process has encountered the annunciated BCDL error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_BCDL [chars] ; rc equals [chars]
Explanation The BCDL Consumer process has encountered the annunciated BCDL error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_BOARD_TYPE FGID BCDL Consumer failed to get hardware board type: rc equals [chars]
Explanation The FGID BCDL Consumer was unable to get the board type.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_BOARD_TYPE FGID BCDL Consumer failed to get hardware board type: rc equals [chars]
Explanation The FGID BCDL Consumer was unable to get the board type.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_DEBUG_INIT The FGID BCDL Consumer Failed to initialize debug; rc equals [chars]
Explanation The FGID BCDL Consumer was unable to initialize debug. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_DEBUG_INIT The FGID BCDL Consumer Failed to initialize debug; rc equals [chars]
Explanation The FGID BCDL Consumer was unable to initialize debug. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_EVM [chars] : [chars]
Explanation The FGID BCDL consumer encountered the annunciated Event Manager Error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_EVM [chars] : [chars]
Explanation The FGID BCDL consumer encountered the annunciated Event Manager Error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_FDI_CLIENT_REG Unable to perform FDI client registration; rc equals [chars]
Explanation The FGID BCDL Consumer was unable to register with the FDI client. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_FDI_CLIENT_REG Unable to perform FDI client registration; rc equals [chars]
Explanation The FGID BCDL Consumer was unable to register with the FDI client. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_FGID_DOWNLOAD_DONE_NOTIF FGID BCDL Consumer failed to notify SFE driver about FGID download complete; rc equals [chars]
Explanation The FGID BCDL Consumer encountered an error while notifying the SFE driver about FGID download completion. This indicates a problem with communication between SFE_DRVR and FGID BCDL consumer. Restart SFE driver manually.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_FGID_DOWNLOAD_DONE_NOTIF FGID BCDL Consumer failed to notify SFE driver about FGID download complete; rc equals [chars]
Explanation The FGID BCDL Consumer encountered an error while notifying the SFE driver about FGID download completion. This indicates a problem with communication between SFE_DRVR and FGID BCDL consumer. Restart SFE driver manually.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_FGID_SET FGID BCDL Consumer failed to set FGID [chars] bitmap; rc equals [chars]
Explanation The FGID BCDL Consumer encountered an error while setting S2 or S3 bitmap. This indicates a problem with the communication between the SFE driver and the FGID BCDL consumer. The FGID BCDL consumer and/or SEA driver may need restarting if the errors persist.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_FGID_SET FGID BCDL Consumer failed to set FGID [chars] bitmap; rc equals [chars]
Explanation The FGID BCDL Consumer encountered an error while setting S2 or S3 bitmap. This indicates a problem with the communication between the SFE driver and the FGID BCDL consumer. The FGID BCDL consumer and/or SEA driver may need restarting if the errors persist.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_RACK_NUM FGID BCDL Consumer failed to get the rack value; rc equals [chars]
Explanation The FGID BCDL Consumer encountered an error while retrieving the rack value from nodeid. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_RACK_NUM FGID BCDL Consumer failed to get the rack value; rc equals [chars]
Explanation The FGID BCDL Consumer encountered an error while retrieving the rack value from nodeid. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_USAGE Invalid argument. USAGE: [chars]
Explanation The FGID BCDL consumer process was invoked with an unknown argument. The BCDL Consumer process was started with an invalid parameter. This is not an expected field event and details about software versions and the .startup file should be returned to engineering.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-3-ERR_USAGE Invalid argument. USAGE: [chars]
Explanation The FGID BCDL consumer process was invoked with an unknown argument. The BCDL Consumer process was started with an invalid parameter. This is not an expected field event and details about software versions and the .startup file should be returned to engineering.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_BCDL_CONSUMER-7-ERR_LTRACE_INIT FGID BCDL Consumer failed to initialize the ltrace file [chars] : rc equals [chars]
Explanation The FGID BCDL Consumer could not open the annunciated ltrace buffer. The FGID component and the system should function as normal, with the exception that ltrace will not be available for FGID BCDL Consumer process.
Recommended Action No action is required.
Error Message%FABRIC-FGID_BCDL_CONSUMER-7-ERR_LTRACE_INIT FGID BCDL Consumer failed to initialize the ltrace file [chars] : rc equals [chars]
Explanation The FGID BCDL Consumer could not open the annunciated ltrace buffer. The FGID component and the system should function as normal, with the exception that ltrace will not be available for FGID BCDL Consumer process.
Recommended Action No action is required.
FGID_LIB Messages
Error Message%FABRIC-FGID_LIB-7-ERR_DEBUG_INIT FGID library failed to initialize the debug ; rc equals [chars].
Explanation The FGID library failed to initialize debug. The FGID component and the system should still function as normal, with the exception that the debugs will not be available for FGID library.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_LIB-7-ERR_DEBUG_INIT FGID library failed to initialize the debug ; rc equals [chars].
Explanation The FGID library failed to initialize debug. The FGID component and the system should still function as normal, with the exception that the debugs will not be available for FGID library.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_LIB-7-ERR_LTRACE_INIT FGID library failed to initialize the ltrace ; rc equals [chars].
Explanation The FGID library failed to initialize ltrace. The FGID component and the system should still function as normal, with the exception that the ltrace will not be available for FGID library.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_LIB-7-ERR_LTRACE_INIT FGID library failed to initialize the ltrace ; rc equals [chars].
Explanation The FGID library failed to initialize ltrace. The FGID component and the system should still function as normal, with the exception that the ltrace will not be available for FGID library.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FGID_SVR Messages
Error Message%FABRIC-FGID_SVR-2-ERR_EES_INIT Rack num could not be determined, rc equals [chars]
Explanation Rack num could not be determined because platform_get_my_nodeid failed.
Recommended Action Whenever this happens, fgid_server will dump a core file. No action is required.
Error Message%FABRIC-FGID_SVR-3-ERR_BCDL [chars]; rc equals [chars]
Explanation The FGID Server encountered the annunciated BCDL error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_BCDL [chars]; rc equals [chars]
Explanation The FGID Server encountered the annunciated BCDL error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_DSC Failed to register for DSC notification; rc equals [chars]
Explanation The FGID Server encountered DSC error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_DSC Failed to register for DSC notification; rc equals [chars]
Explanation The FGID Server encountered DSC error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_EES [chars], rc equals [chars]
Explanation Issue with EES
Recommended Action No action is required.
Error Message%FABRIC-FGID_SVR-3-ERR_EVM_CREATE FGID Server failed to create [chars] evm; rc equals [chars]
Explanation The FGID Server was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_EVM_CREATE FGID Server failed to create [chars] evm; rc equals [chars]
Explanation The FGID Server was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_EVM_SYNC_ATTACH FGID Server failed to attach [chars] evm; rc equals [chars]
Explanation The FGID Server was unable to attach the indicated event handler to the event manager. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_EVM_SYNC_ATTACH FGID Server failed to attach [chars] evm; rc equals [chars]
Explanation The FGID Server was unable to attach the indicated event handler to the event manager. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_GSP [chars] ; rc equals [chars]
Explanation The FGID-DB server encountered the annunciated GSP error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_GSP [chars] ; rc equals [chars]
Explanation The FGID-DB server encountered the annunciated GSP error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_INTERNAL_SW [chars]; [chars]
Explanation The FGID Server encountered the annunciated SW error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_INTERNAL_SW [chars]; [chars]
Explanation The FGID Server encountered the annunciated SW error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_MEM_ALLOC FGID Server unable to allocate [dec] bytes
Explanation The FGID Server was unable to allocate memory. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_MEM_ALLOC FGID Server unable to allocate [dec] bytes
Explanation The FGID Server was unable to allocate memory. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_USAGE FGID Server : Server Id requested [chars] is not a allowed server_id
Explanation Incorrect command line parameters were passed to the FGID Server, and so it failed to start.
Recommended Action Check the startup arguments passed to FGID-DB. A default configuration will be used if no parameters are passed. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-3-ERR_USAGE FGID Server : Server Id requested [chars] is not a allowed server_id
Explanation Incorrect command line parameters were passed to the FGID Server, and so it failed to start.
Recommended Action Check the startup arguments passed to FGID-DB. A default configuration will be used if no parameters are passed. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-4-WARNING_INTERNAL_SW [chars]; [chars]
Explanation The FGID Server encountered the annunciated SW error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-7-ERR_LTRACE_INIT FGID Server failed to initiaize the ltrace file [chars]; rc equals [chars]
Explanation The FGID Server Could not open the annunciated ltrace buffer. The FGID component and the system should function as normal, with the exception that ltrace will not be available for fgid_server process.
Recommended Action No action is required.
Error Message%FABRIC-FGID_SVR-7-ERR_LTRACE_INIT FGID Server failed to initiaize the ltrace file [chars]; rc equals [chars]
Explanation The FGID Server Could not open the annunciated ltrace buffer. The FGID component and the system should function as normal, with the exception that ltrace will not be available for fgid_server process.
Recommended Action No action is required.
Error Message%FABRIC-FGID_SVR-7-ERR_SYSMGR [chars] ; rc equals [chars]
Explanation The FGID-DB server failed in sysmgr API
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FGID_SVR-7-ERR_SYSMGR [chars] ; rc equals [chars]
Explanation The FGID-DB server failed in sysmgr API
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FIA_API Messages
Error Message%FABRIC-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.
Error Message%FABRIC-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%FABRIC-FIA-2-ARB_SERDES_0_FAIL Arbitration Serdes Link 0 Failure
Explanation Arbitration serdes link 0 failure.
Recommended Action Wait a few minutes. If it doesn't recover, please reload the board using command 'reload location '. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-2-ARB_SERDES_1_FAIL Arbitration Serdes Link 1Failure
Explanation Arbitration serdes link 1 failure.
Recommended Action Wait a few minutes. If it doesn't recover, please reload the board using command 'reload location '. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-2-DATA_SERDES_0_FAIL Data Serdes Link 0 Failure
Explanation Data serdes link 0 failure.
Recommended Action Wait a few minutes. If it doesn't recover, please reload the board using command 'reload location '. Make sure board is seated properly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-2-DATA_SERDES_1_FAIL Data Serdes Link 1 Failure
Explanation Data serdes link 1 failure.
Recommended Action Wait a few minutes. If it doesn't recover, please reload the board using command 'reload location '. Make sure board is seated properly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-2-DATA_SERDES_2_FAIL Data Serdes Link 2 Failure
Explanation Data serdes link 2 failure.
Recommended Action Wait a few minutes. If it doesn't recover, please reload the board using command 'reload location '. Make sure board is seated properly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-2-DATA_SERDES_3_FAIL Data Serdes Link 3 Failure
Explanation Data serdes link 3 failure.
Recommended Action Wait a few minutes. If it doesn't recover, please reload the board using command 'reload location '. Make sure board is seated properly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-2-FIAHW_INT_FIFO [chars] [chars] ([hex])
Explanation This error usually indicates an internal hardware problem on the card. The internal parity error affects the communication bus between adjacent ASICs on the hardware datapath. The From Fabric or To Fabric direction, the detailed error string and the slot number are provided as part of the message.
Recommended Action If there are other error reports about the switch fabric (CSC/SFC) then wait atleast 3 minutes for corrective action. Otherwise, run diagnostics for slot reporting error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-2-FIAHW_INT_PARITY [chars] [chars] ([hex])
Explanation This error usually indicates an internal hardware problem on the card. The internal parity error affects the communication bus between adjacent ASICs on the hardware datapath. The From Fabric or To Fabric direction, the detailed error string and the slot number are provided as part of the message.
Recommended Action If there are other error reports about the switch fabric (CSC/SFC) then wait atleast 3 minutes for corrective action. Otherwise, run diagnostics for slot reporting error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-2-PKT_INT_ERR_AT_DDRIF_0 Pkt Integrity Error at DDR interface from Punt/Bridge-0 FPGA
Explanation Packet Integrity Error at DDR interface from Punt/Bridge-0 FPGA.
Recommended Action Verify correct version of Punt/Bridge FPGA is loaded. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-2-PKT_INT_ERR_AT_DDRIF_1 Pkt Integrity Error at DDR interface from Punt/Bridge-1 FPGA
Explanation Packet Integrity Error at DDR interface from Punt/Bridge-1 FPGA.
Recommended Action Verify correct version of Punt/Bridge FPGA is loaded. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-2-TEMP_TOO_HIGH Crossbar fabric interface ASIC temperature is too high
Explanation Crossbar fabric interface ASIC is reporting a very high temperature.
Recommended Action Check if board is reporting temperature alarm. If not, it is due to Crossbar fabric interface heatsink not being installed properly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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 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%FABRIC-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 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%FABRIC-FIA-3-ERR_INIT Initialization Error: [chars]. Exiting.
Explanation FIA 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%FABRIC-FIA-3-ERR_MEM_ALLOC Memory allocation failed for internal data structures
Explanation Memory was not available for an internal data structure. The requested operation could not be accomplished because of a low memory condition. The LC will not boot up successfully and will not be able to participate in data forwarding.
Recommended Action Run the debug show commands, gather data and contact tac. Also ensure the LC is populated with the minimum amount of memory required for proper operation. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-ERR_MEM_ALLOC Memory allocation failed for internal data structures
Explanation Memory was not available for an internal data structure. The requested operation could not be accomplished because of a low memory condition. The LC will not boot up successfully and will not be able to participate in data forwarding.
Recommended Action Run the debug show commands, gather data and contact tac. Also ensure the LC is populated with the minimum amount of memory required for proper operation. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-FIA-3-FFIAHW_ERR_FIFO [chars]: [chars] [hex]
Explanation This error usually indicates an internal hardware problem on the card. The internal parity error affects the communication bus between adjacent ASICs on the hardware datapath. In this case parity error was detected in the FFIA internal reassembly memory. This error will trigger a recovery operation. The LC may not be able to forward data packets and traffic loss may be observed due to this error.
Recommended Action If there are other error reports about the switch fabric (CSC/SFC) then wait several minutes for corrective action. Otherwise, run diagnostics for slot reporting error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FFIAHW_ERR_PARITY [chars]: [chars] [hex]
Explanation This error usually indicates an internal hardware problem on the card. The internal parity error affects the communication bus between adjacent ASICs on the hardware datapath. In this case the backpressure signals between FFIA and Tx PSE is having signal integrity issue. This error will trigger a recovery operation. The LC may not be able to forward data packets and traffic loss may be observed due to this error.
Recommended Action If there are other error reports about the switch fabric (CSC/SFC) then wait several minutes for corrective action. Otherwise, run diagnostics for slot reporting error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_CHIP Failed to configure [chars] config value : [hex] in hardware, fc_mask equals [hex], staus equals [hex]
Explanation The low level FIA driver was unable to complete its write operation. Possible cause is harware failure. Error recovery will be triggered for this error. The direction value of fia_config passed and status returned of the failure are indicated in th emessage.
Recommended Action Wait atleast 3 minutes for corrective action to occur. Look for error reports about the switch fabric (CSC/SFC.)
Error Message%FABRIC-FIA-3-FIAHW_CRC16 Too many CRC errors on fabric serial line (from fabric plane [dec])
Explanation This error indicates a problem in the interface between the card reporting error and the switch fabric card in the indicated fabric plane. Data corruption is imminent.
Recommended Action Wait atleast 3 minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about the switch fabric (CSC/SFC.) If errors persist, you can try moving the card to another slot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_CRC16 Too many CRC errors on fabric serial line (from fabric plane [dec])
Explanation This error indicates a problem in the interface between the card reporting error and the switch fabric card in the indicated fabric plane. Data corruption is imminent.
Recommended Action Wait several minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about the switch fabric (CSC/SFC.) If errors persist, Move the card to another slot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_DEVCTL FIA device access (read) failed for [chars]
Explanation The low level fabric interface ASIC driver was unable to complete its hardware access operation. Hardware configuration may not have been successfully completed. This may result in traffic loss. The output of the show command may not be valid. The direction of the error is indicated in the message.
Recommended Action Restart the fiad process on the LC. If the error persists, reload the LC using 'hw-module' command.
Error Message%FABRIC-FIA-3-FIAHW_EMPTY_DEST_SOFTREQ [chars] Empty destination software request error [hex]
Explanation An unexpected error has occurred. This error typically means that a unicast or a multicast packet was received by the fabric interface ASIC to be forwarded across the switching fabric without any destination slot set in the header of the data packet. The direction of the error and the slot are indicated by the parameter in the message.
Recommended Action None, this is a transient error and can be safely ignored. However multiple occurrences of this error indiactes a software problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_EXT_FIFO [chars] [chars] ([hex])
Explanation This error indicates a (possibly temporary) problem in the interface between the card reporting error and the switch fabric. Either the switch fabric is not able source or drain the data packets to this LC. This error is traffic affecting. Error recovery will be triggered. The From Fabric or To Fabric direction, the detailed error string and the slot number are provided as part of the message.
Recommended Action Wait atleast 3 minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about the switch fabric (CSC/SFC.) If errors persist, you can try moving the card to another slot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_EXT_PARITY [chars] [chars] ([hex])
Explanation This error indicates a (possibly temporary) problem in the interface between the card reporting error and the switch fabric. The error recovery will be triggered and the process should recover after a reset of the affected ASIC. The From Fabric or To Fabric direction, the detailed error string and the slot number are provided as part of the message.
Recommended Action Wait atleast 3 minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about the switch fabric (CSC/SFC.) If errors persist, you can try moving the card to another slot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_INT Unexpected [chars] interrupt
Explanation An unexpected error has occurred. This error will trigger an error recovery and is traffic affecting. The direction in which the error occurred is specified as part of the meassage. This error message indicates a masked interrupt occured, even though its handled by the driver, this error should not have happened.
Recommended Action Wait atleast 3 minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about the switch fabric (CSC/SFC.)
Error Message%FABRIC-FIA-3-FIAHW_LOS Persistent LOS on serial link (from fabric plane [dec])
Explanation This error indicates a problem (Loss of Sync) in the interface between the card reporting error and the switch fabric card in the indicated fabric plane. This error is traffic affecting. Error recovery is triggered by this error.
Recommended Action Wait several minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about the switch fabric (CSC/SFC.) If errors persist, Move the card to another slot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_LOS Persistent LOS on serial link (from fabric plane [dec])
Explanation This error indicates a problem (Loss of Sync) in the interface between the card reporting error and the switch fabric card in the indicated fabric plane. This error is traffic affecting. Error recovery is triggered by this error.
Recommended Action Wait atleast 3 minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about the switch fabric (CSC/SFC.) If errors persist, you can try moving the card to another slot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_LOS_CLEAR LOS cleared on serial link (from fabric plane [dec])
Explanation An earlier reported error (Loss of Sync) is now cleared. Normal operations can resume.
Recommended Action No action is required.
Error Message%FABRIC-FIA-3-FIAHW_LOS_CLEAR LOS cleared on serial link (from fabric plane [dec])
Explanation An earlier reported error (Loss of Sync) is now cleared. Normal operations can resume.
Recommended Action No action is required.
Error Message%FABRIC-FIA-3-FIAHW_MULTI_DEST_SOFTREQ [chars] Multi destination unicast software request error [hex]
Explanation An unexpected error has occurred. This error typically means that a unicast data packet was received by the fabric interface ASIC to be forwarded across the switching fabric with more than one destination slot. The direction of the error and the slot are indicated by the parameter in the message.
Recommended Action None, this is a transient error and can be safely ignored. However multiple occurrences of this error indiactes a software problem. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_NOHALT Unexpected [chars] interrupt without halt
Explanation An unexpected error has occurred. This error will trigger an error recovery procedure & is traffic affecting. The direction in which the error occurred is specified as part of the meassage.
Recommended Action Wait atleast 3 minutes for the corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about the switch fabric (CSC/SFC.)
Error Message%FABRIC-FIA-3-FIAHW_RATE Error report timer wheel failure detected
Explanation An internal data structure was missing a field. Some errors may not be reported to the fabric control software. This error indicates data corruption in internal structures.
Recommended Action The system will normally recover from this error without intervention. If the frequency with which this error is occurring increases substantially, call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_RATE Error report timer wheel failure detected
Explanation An internal data structure was missing a field. Some errors may not be reported to the fabric control software. This error indicates data corruption in internal structures.
Recommended Action The system will normally recover from this error without intervention. If the frequency with which this error is occurring increases substantially, call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_TMR Forced timeout of an internal timer failed, error [chars]
Explanation The library call failed. This indicates internal data corruption on the LC. Certain errors may not be reported to the fabric control software. The error string as returned by the library call is included in the message.
Recommended Action The system will normally recover from this error without intervention. If the frequency with which this error is occurring increases substantially, call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_TMR Forced timeout of an internal timer failed, error [chars]
Explanation The library call failed. This indicates internal data corruption on the LC. Certain errors may not be reported to the fabric control software.
Recommended Action The system will normally recover from this error without intervention. If the frequency with which this error is occurring increases substantially, call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-FIAHW_UNHANDLED Unexpected error case
Explanation An unexpected error has occurred. This error will trigger an error recovery and is traffic affecting. An error other than the CRC or LOS has occurred.
Recommended Action Wait atleast 3 minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about the switch fabric (CSC/SFC.)
Error Message%FABRIC-FIA-3-FIAHW_UNHANDLED Unexpected error case
Explanation An unexpected error has occurred. This error will trigger an error recovery and is traffic affecting.
Recommended Action Wait several minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about the switch fabric (CSC/SFC.)
Error Message%FABRIC-FIA-3-TFIAHW_ERR_PACKET [chars]: [chars] [hex]
Explanation This error usually indicates an internal hardware problem on the card. A corrupted packet was received from the Rx BMA, this indicates communication bus between the FIA and Rx BMA on the hardware datapath may have signal integrity issues. This error will trigger an error recovery. The LC may not be able to forward data packets and traffic loss may be observed due to this error.
Recommended Action If there are other error reports about the switch fabric (CSC/SFC) then wait several minutes for corrective action. Otherwise, run diagnostics for slot reporting error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FIA-3-TFIAHW_ERR_PARITY [chars]: [chars] [hex]
Explanation This error usually indicates an internal hardware problem on the card. The internal parity error affects the communication bus between adjacent ASICs on the hardware datapath. The LC may not be able to forward data packets and traffic loss may be observed due to this error. The From Fabric or To Fabric direction, the detailed error string and the slot number are provided as part of the message.
Recommended Action If there are other error reports about the switch fabric (CSC/SFC) then wait several minutes for corrective action. Otherwise, run diagnostics for slot reporting error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-FIA-4-FIAHW_WARNING_UNSUPPORTED_CARD Warning: This is an unsupported SIP-600 card with lower revision Fabric Interface ASIC
Explanation This warning indicates that this is an older version of SIP-600 card which does not have a supported Fabric Interface ASIC (FIA). As a result, any CSC switch-over, RP fail-over or fabric card OIR may result in FIA ASIC errors, and the router may experience abnormal behavior.
Recommended Action Replace with a later version of SIP-600.
Error Message%FABRIC-FIA-5-ERR_DEV_NOT_FOUND Driver has not discovered ASIC instance [dec] yet [[chars]], retrying....
Explanation The FIA driver is polling for the device.
Recommended Action If the message appears once and then stops, there is no cause for concern. If it persists or if fia_driver gets respawned by sysmgr for not returning EOI, then this could indicate a problem.
Error Message%FABRIC-FIA-6-PCDS_STATS_TIMESTAMP_FAILURE pcds_get_timestamp failed for superfish stats
Explanation This is a message indicating failed to get timestamp for superfish stats.
Recommended Action No action is required.
Error Message%FABRIC-FIA-6-PCDS_STATS_TIMESTAMP_FAILURE pcds_get_timestamp failed for fia stats
Explanation This is a message indicating failed to get timestamp for fia stats.
Recommended Action No action is required.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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.
Error Message%FABRIC-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.
FIFO Messages
Error Message%FABRIC-FIFO-2-SW_FATAL_ERROR fatal s/w error encountered - [chars], [chars]
Explanation An unrecoverable fatal s/w error was encountered, which results in severe board malfunction. The exact cause is appended to the error msg.
Recommended Action Reload the board. *SUPPORT*
FSDB_FADB_MAIN Messages
Error Message%FABRIC-FSDB_FADB_MAIN-3-EVT_MGR_CREATE_FAIL event manager create failed: [chars]
Explanation FSDB FADB encountered an error while attempting to create an event manager for process fsdb_fadb
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB_FADB_MAIN-3-EXTRACT_NODE_ID_FAIL nodeid_extract_fields failed: [chars]
Explanation FSDB FADB encountered an error while attempting to extract info from node id in process fsdb_fadb
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB_FADB_MAIN-3-GET_NODE_ID_FAIL platform_get_my_nodeid failed: [chars]
Explanation FSDB FADB encountered an error while attempting to get node id in process fsdb_fadb
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB_FADB_MAIN-3-RESPAWN_COUNT_GET_FAIL respawn count get failed: [chars]
Explanation FSDB FADB encountered an error while attempting to attach sync event handler for process fsdb_fadb
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB_FADB_MAIN-3-SYNC_HDLR_ATTACH_FAIL sync event handler attach failed: [chars]
Explanation FSDB FADB encountered an error while attempting to attach sync event handler for process fsdb_fadb
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB_FADB_MAIN-3-SYSDB_BIND_FAIL sysdb bind failed: [chars]
Explanation FSDB FADB encountered an error while attempting to bind to the rack endpoint to get router inventory
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB_FADB_MAIN-3-SYSDB_LIST_FREE_FAIL sysdb list free failed: [chars]
Explanation FSDB FADB encountered an error while attempting to free a list while getting the sysdb inventory
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FSDB_FADB Messages
Error Message%FABRIC-FSDB_FADB-3-SHM_CREATE_FAIL Shared memory creation failed: [chars]
Explanation FSDB FADB encountered an error while attempting to create the FADB shared memory
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB_FADB-3-SHM_OPEN_FAIL shm_open failed: [chars]
Explanation FSDB FADB encountered an error while attempting to open the FADB shared memory
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB_FADB-4-SHM_FILE_TRUNCATE_FAIL [chars]: shared memory file truncate failed: [chars]
Explanation FSDB FADB encountered an error while attempting to truncate the FADB shared memory file
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSDB_FADB-4-SHM_MMAP_FAIL [chars]: shared memory mapping failed: [chars]
Explanation FSDB FADB encountered an error while attempting to map the FADB shared memory
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FSTATSA Messages
Error Message%FABRIC-FSTATSA-3-ERR_BAG_REG Bag register error is detected; [chars].
Explanation Fabric statistics aggregator process encountered a fatal error to register its bags to bag software. This software error will cause process termination for recovery The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_DEBUG_INIT_EVENT Debug initialization for the fstats/server/[chars] event failed; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to initialize debug facility and hence failed to initialize. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_DEBUG_REGISTER Debug registration for fabric statistics server failed; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to register debug facility and hence failed to initialize. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_EVM_CREATE Failed to create event manager; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to create its event manager for receiving events. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_GSP_GROUP_CREATE GSP group [chars] creation/join was failed; [chars]; rc equals [hex].
Explanation Fabric statistics aggregator process encountered a fatal error to create group for group communication. This software error will cause process termination to recover. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_INTERNAL Internal software error: [chars]; [chars]
Explanation Fabric statistics aggregator process encountered a fatal internal software error. This software error will cause process termination to recover. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. *RECUR*
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_SYSDB_BIND Can't bind to SysDB at [chars]; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to bind to admin plane sysdb server. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_SYSDB_EDM_REG Failed to register SysDB EDM at [chars]; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to register EDM to admin plane sysdb server. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSA-3-ERR_SYSMGR_PROC_READY Failed to report process ready to sysmgr; [chars]
Explanation Fabric statistics aggregator process encountered a fatal error to report process ready to sysmgr. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FSTATSC Messages
Error Message%FABRIC-FSTATSC-3-ERR_GSP_GROUP_CREATE GSP group [chars] creation/join was failed; [chars].
Explanation Fabric statistics client library encountered failure of creating group for GSP group communication.
Recommended Action Restart Fabric statistics client manually if the error is persistent.
Error Message%FABRIC-FSTATSC-7-ERR_DEBUG_CLEANUP Debug cleanup for fabric statistics client library failed: [chars]
Explanation Fabric statistics client library encountered debug facility clean up failure.
Recommended Action None.
Error Message%FABRIC-FSTATSC-7-ERR_DEBUG_INIT_EVENT Debug initialization for the fstats/client/[chars] event failed: [chars]
Explanation Fabric statistics client library encountered debug facility initialization failure. When this error happens, the library will not able to enable debug.
Recommended Action Restart Fabric statistics client manually if the error is persistent.
Error Message%FABRIC-FSTATSC-7-ERR_DEBUG_REG Debug registration for fabric statistics client library failed: [chars]
Explanation Fabric statistics client library encountered debug facility registration failure. When this error happens, the library will not able to enable debug.
Recommended Action Restart Fabric statistics client manually if the error is persistent.
Error Message%FABRIC-FSTATSC-7-ERR_GSP_LOOKUP_LWG GSP lightweight group [chars] lookup was failed; [chars].
Explanation Fabric statistics client library encountered failure when it looks up Fabric server light weight group for light weight group communication. Normally, this is a transient error. It can be a true error if the error is persistent.
Recommended Action Restart Fabric statistics client manually if the error is persistent in a specific fabric card. Restart Fabric statistics server manually if the error is persistent in many fabric cards.
FSTATSS Messages
Error Message%FABRIC-FSTATSS-3-ERR_BAG_REG Bag register error is detected; [chars].
Explanation Fabric statistics server process encountered a fatal error to register its bags to bag software. This software error will cause process termination for recovery The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_DEBUG_INIT_EVENT Debug initialization for the fstats/server/[chars] event failed; [chars]
Explanation Fabric statistics server process encountered a fatal error to initialize debug facility and hence failed to initialize. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_DEBUG_REGISTER Debug registration for fabric statistics server failed; [chars]
Explanation Fabric statistics server process encountered a fatal error to register debug facility and hence failed to initialize. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_EVM_CREATE Failed to create event manager; [chars]
Explanation Fabric statistics server process encountered a fatal error to create its event manager for receiving events. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_GSP_GROUP_CREATE GSP group [chars] creation/join was failed; [chars]; rc equals [hex].
Explanation Fabric statistics server process encountered a fatal error to create group for group communication. This software error will cause process termination to recover. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_INTERNAL Internal software error: [chars]; [chars]
Explanation Fabric statistics server process encountered a fatal internal software error. This software error will cause process termination to recover. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_MEM_ALLOC Could not allocate memory for [chars].
Explanation Fabric statistics server process encountered memory allocation error for creating statistics database or storing statistics data. This software error will cause process termination to recover during process initialization. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action Memory allocation failures will happen if the the router runs out of memory or memory leak in this process or other processes. User needs to do 'process restart memory hog process job id' to recover.
Error Message%FABRIC-FSTATSS-3-ERR_SYSDB_BIND Can't bind to SysDB at [chars]: [chars]
Explanation Fabric statistics server process encountered a fatal error to bind to admin plane sysdb server. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_SYSDB_EDM_REG Failed to register SysDB EDM at at [chars]: [chars]
Explanation Fabric statistics server process encountered a fatal error to register EDM to admin plane sysdb server. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-3-ERR_SYSMGR_PROC_READY Failed to report process ready to sysmgr; [chars]
Explanation Fabric statistics server process encountered a fatal error to report process ready to sysmgr. This software error will cause process termination for recovery. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-FSTATSS-7-ERR_RSC_REG_INCONSISTENT_VALUE [chars]: fabric resource registration error due to inconsistent value.
Explanation Fabric statistics server process encountered a transient error due to the inconsistent checking of the received message. This error message will be a true error if many error message is logged and the error is persistent.
Recommended Action If the error continues, user will need to restart the process for recovery.
HFR_FSDB_FADB_LTRACE Messages
Error Message%FABRIC-HFR_FSDB_FADB_LTRACE-3-ERROR_INIT_FAIL ltrace initialization operation failed for error traces: [chars]
Explanation The FSDB FADB ltrace lib failed to initialize the error ltrace
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-HFR_FSDB_FADB_LTRACE-3-EVENT_INIT_FAIL ltrace initialization operation failed for events: [chars]
Explanation The FSDB FADB ltrace lib failed to initialize the events ltrace
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-HFR_FSDB_FADB_LTRACE-3-INTERNAL_INIT_FAIL ltrace initialization operation failed for internal traces: [chars]
Explanation The FSDB FADB ltrace lib failed to initialize the internal ltrace
Recommended Action Copy the error message exactly as 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%FABRIC-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.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-INGRESSQ_DLL-2-ERR_EIO_TRAIN EIO link training threshold exceeded, link: [dec]
Explanation Repeated attempts to train the EIO links to the neighboring Asic have failed. No further attempts to retrain the link will be made.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-INGRESSQ_DLL-2-TAKING_NODE_DOWN Taking the node down, Reason: [chars]
Explanation Ingressq DLL encountered an fatal error mentioned above. The driver triggers MSC node-down to recover from the error.
Recommended Action This might be a recovery action from a fault. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-INGRESSQ_DLL-3-BRM_BARRIER_SYNCUP_FAILED BRM Block: Barrier sync up failed for this node. Last sync state equals [dec]
Explanation There might be a fabric disconnect in the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-INGRESSQ_DLL-3-ERR_ASIC_FCRAM_ASSERT Assert Error valid: [dec], block: [dec], debug_info: [dec]
Explanation Ingressq encountered an assert error in the FCRAM. The driver triggers a device reset. The device should be reinitialized.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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. Driver takes appropriate action to log and fix the error which may include a device reset.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-INGRESSQ_DLL-3-ERR_BIST Error during [chars] BIST
Explanation BIST failed for the mentioned block. The driver should trigger a device reset to fix this error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-INGRESSQ_DLL-3-ERR_INIT [chars]
Explanation The Ingressq driver failed to initialize the device resulting in the restart of the Ingressq driver process.
Recommended Action Collect all the event logs and the output of the following command executed from the CLI of the active RP: 'show process ingressq' Also, collect the fabric snapshot: 'show fabric-snapshot file loc '
Error Message%FABRIC-INGRESSQ_DLL-3-ERR_MEM_ALLOC Error Allocating memory for [chars]
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%FABRIC-INGRESSQ_DLL-3-ERR_MEM_ALLOC Error Allocating memory for [chars]
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%FABRIC-INGRESSQ_DLL-3-RESET Resetting IQM ASIC Device
Explanation Ingressq, cpuctrl net interface encountered a CRC/Sync Error. This will result in the PIO or CDMA failure.
Recommended Action If it is possible to isolate the trigger point for the sn link error, collect all the necessary condition that caused the error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-INGRESSQ_DLL-3-RESET Resetting 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%FABRIC-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%FABRIC-INGRESSQ_DLL-3-SEQ_STATE_POST_OP_FAILED Sequencer state: [dec], reason: [chars] : [chars], #retries: [dec]
Explanation Ingressq driver state machine encountered a failure in initializing the device above threshold number of times. Driver will continue to initialize the device.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-INGRESSQ_DLL-3-SEQ_STATE_PRE_OP_FAILED Exiting. sequencer state: [dec], reason: [chars] : [chars]
Explanation Ingressq driver state machine encountered an unrecoverable error. This will result in driver restart.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. Verify that the ingressq driver is up and running by executing the following command at the CLI of the active RP: 'show process ingressq location ' If it is still non-operational, enable the following debugs of the ingressq driver process: asic error asic fatal asic info and restart the driver by executing the following command at the CLI of the active RP: 'process restart ingressq location ' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-INGRESSQ_DLL-4-BRM_AGGR_DELTA_THRSHLD BRM aggr delta, spo link: [dec], cast: [dec], threshold: [unsigned long int]
Explanation There might be a fabric disconnect in the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-INGRESSQ_DLL-4-BRM_DELTA_THRSHLD BRM delta threshold, spo link: [dec], cast: [dec], threshold: [unsigned long int]
Explanation There might be a fabric disconnect in the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-INGRESSQ_DLL-4-BRM_DID_CULPRIT BRM double in delta culprit, spo link: [dec], cast: [dec]
Explanation There might be a fabric disconnect in the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-INGRESSQ_DLL-4-BRM_INVALID_INPUT BRM invalid input; spo: [dec], cast: [dec], current_barr: [hex] input_barr: [hex]
Explanation There might be a fabric disconnect in the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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 for the above specified address location. This may be caused if the device is not initialized correctly or synchronized correctly.
Recommended Action If it is possible to isolate the trigger point for the cdma failure, collect all the necessary condition that caused the error. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-INGRESSQ_DLL-4-CONFIG_ERR Ingressq recieved packets in invalid queue(s). [chars]
Explanation Ingressq has various queues that are used by Ingress ASICs to send specific stream of traffic. These queues are specifically configured before they are used to forward traffic. Ingressq recived a few packets in queues that were misconfigured or not configured at all. The driver will automatically try to recover from the condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-INGRESSQ_DLL-4-ERR_ASIC_CRC CRC Error: Block:[chars] Error:[chars] Count: [dec]
Explanation Ingressq block received a packet with a CRC error. It is primarily caused by either the link errors between the devices or packet corruption in the upstream asic. This error may cause performance degradation.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-INGRESSQ_DLL-4-ERR_ASIC_LENGTH Block: [chars] encountered error: [chars]. It received a packet with length error(s), expected: [dec], received: [dec]
Explanation Ingressq received a packet with incorrect length either from cpuctrl or Ingress PSE. It is primarily caused by either the link errors between the devices or packet corruption in the upstream asic.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-INGRESSQ_DLL-4-INTR_ENABLE_FAIL Interrupt enable at addr: [hex] mask: [hex] failed.
Explanation Hardware state is not correct.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-INGRESSQ_DLL-4-LNS_LOP_DROP Error: Cells dropped due to low availability of planes, aggr cell drop count: [unsigned long long int]
Explanation Ingressq dropped a few cells because of unavailability of enough planes to forward the cells to its destination. If the cells are dropped intermittently during system reconfiguration (LC reload, RP fail over, etc), then these drops are expected. System will recover after the hardware reprogramming completes. If these drops are seen continuously for long periods, then this indicates that either the node is not programmed correctly, or there is an error in data plane software.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-INGRESSQ_DLL-5-ERR_ASIC_PARITY Block: [chars], entity: [chars] had parity error(s), addr: [dec], parity: [dec]
Explanation In the specified block a parity error encountered at mentioned addr offset. If the error exceeds its threshold, the driver trigger a corrective action which may include device reset or MSC reload.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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 by the next write operation.
Recommended Action This error is an correctable error. There are no side effects. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-INGRESSQ_DLL-6-BRM_BARRIER_SYNCED_UP BRM Block: Barrier synced up on this node.
Explanation This message indicates that system barriers synced on this node. This message is expected during normal operation.
Recommended Action No action is required.
Error Message%FABRIC-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%FABRIC-INGRESSQ_DLL-6-ERR_ASIC_GENERIC Block: [chars], Generic Error [chars] at Memory Address [hex].
Explanation Ingressq encountered a device error that has exceeded its threshold value. Driver takes appropriate action to log and fix the error which may include a device reset.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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 for the incoming packets. This condition is caused by over subscription or hitting the Packet Per Second rate. This will affect the QOS. Thus it is recommended to reduce the packet rate to this MSC.
Recommended Action Reduce the incoming packet rate to this MSC as under the OOR condition the QOS If the OOR is seen in non-oversubscribed case, contact TAC Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-INGRESSQ_DLL-7-ERR_REGISTER_GET Register get failed for address [hex], Reason: [chars]
Explanation An attempt to read a Hardware register failed. This could result in inconsistent behavior of the device.
Recommended Action Run diags on the board and contact TAC support. If it is possible to isolate the trigger point for the read failure, collect all the necessary condition that caused the error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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.
Error Message%FABRIC-INGRESSQ_DLL-7-ERR_RES_PROG Error during Resource Programming: [chars] Reason: [chars]
Explanation Ingressq encountered an error during resource programming. If there are no further attempts to reprogram the device, the device behavior may be inconsistent.
Recommended Action The driver/client processes try to recover from this error. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
INGRESSQ_LIB Messages
Error Message%FABRIC-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.
Error Message%FABRIC-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%FABRIC-INGRESSQ-2-ASIC_RESET_FAILED Ingressq: Error encountered during hw reset of sprayer.
Explanation Ingressq hw reset 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%FABRIC-INGRESSQ-2-ASIC_RESET_FAILED Ingressq: Error encountered during hw reset of sprayer.
Explanation Ingressq hw reset 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%FABRIC-INGRESSQ-3-ERR_INIT Fatal error encountered, reason equals [chars]
Explanation The Ingressq driver failed to initialize the device resulting in the restart of the Ingressq driver process.
Recommended Action Collect all the event logs and the output of the following command executed from the CLI of the active RP: 'show process ingressq' Also, collect the fabric snapshot: show fabric-snapshot file loc
Error Message%FABRIC-INGRESSQ-3-ERR_INIT Fatal error encountered, reason equals [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%FABRIC-INGRESSQ-3-ERR_MEM_ALLOC Error Allocating [dec] 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%FABRIC-INGRESSQ-3-ERR_MEM_ALLOC Error Allocating [dec] 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%FABRIC-INGRESSQ-4-ERR_CHKPT_INIT 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%FABRIC-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%FABRIC-INGRESSQ-7-ERR_BAG_REG 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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-INGRESSQ-7-ERR_CLIENT_REG Client [chars] failed. Error: [chars]
Explanation Ingressq client failed to Register/Unregister with Ingressq Server process. This error is also detected from the client's side. Retrial attempts would be made by the client.
Recommended Action 1. Verify the connectivity between the client and the Ingressq process. 'show controllers ingressq clients location ' Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-INGRESSQ-7-ERR_LWM_CREATE Event Manager create failed. Error([dec]) [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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-INGRESSQ-7-ERR_RES_PROG Error during Resource Programming: [chars] Reason: [chars]
Explanation Ingressq encountered an error during resource programming. If there are no further attempts to reprogram the device, the device behavior may be inconsistent.
Recommended Action The driver/client processes try to recover from this error. If any discrepancies are found in the device functionality, contact TAC Support. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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%FABRIC-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.
Error Message%FABRIC-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.