-
Cisco IOS XR System Error Reference Guide for XR1200 Series Platform Specific Messages, Release 3.3
-
Preface
-
Overview
-
Fabric Messages
-
ASIC Fabric Interface Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 (L1) Messages
-
Layer 2 (L2) Messages
-
Line Card (LC) Messages
-
Media Messages
-
Manageability (MGBL) Messages
-
Operating System (OS) Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service (QOS) Messages
-
Routing Messages
-
Feedback
Table Of Contents
Layer 2 Messages
This section contains all Layer 2 related System Error Messages, including Ethernet drivers, Packet-over-Sonet (PoS), SONET, PLIMS, and so forth. The following facility codes are represented in this module:
ALPHA Messages
Error Message%L2-ALPHA-3-ERR_ACCESS Memory access error: [chars]: Err=[chars]
Explanation A memory access error occurred in programable switching engine (PSE) driver which involves exiting the process. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ALPHA-3-ERROR_MSG
[chars] [chars]: [hex] [hex]Explanation This is a error message in the HFA Alpha driver to indicate either anomolies which are not service impacting. Some of the messages may indicate a failure to allocate resources needed by applications.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ALPHA-6-VERSION_WARNING [chars] [chars] error [hex]
Explanation This is an informational message in the programable switching Engine driver to indicate an operation. %s - is the warning message. %s - is the decoded warning reason. %x - is the decoded error code.
Recommended Action No action is required.
Error Message%L2-ALPHA-7-INFO_MSG [chars] [chars]
Explanation This is an informational message in the programable switching Engine driver to indicate an operation. %s - indicates the direction of the PSE. %s - is the decoded informational reason.
Recommended Action No action is required.
Error Message%L2-ALPHA-7-PAIR_REG [chars] [chars] PAIR registers:
pcr [hex] plu_pirl [hex] pirm1 [hex]
pirm2 [hex] pirh [hex] ip_dst [hex]
ip_src [hex] mpls_label [hex] mpls_info [hex]
ip_header [hex] l4_port [hex] start_adr [hex]
msq_info [hex] ltr [hex] tlu_force [hex]
pre_cam_prof [hex] lbl1_lo [hex] lbl1_hi [hex]
tlbl2_lo [hex] lbl2_hi [hex] leaf1_word1 [hex]
leaf1_word2 [hex] leaf1_word3 [hex] leaf1_word4 [hex]
leaf2_word1 [hex] leaf2_word2 [hex] leaf2_word3 [hex]
tleaf2_word4 [hex] tcam_cont [hex]Explanation An error occurred in programable switching engine (PSE) driver which indicates anomalies. Some of the messages may indicate a failure to allocate resources needed by applications.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ALPHA-7-PHB_DUMP
[hex]: [hex] [hex] [hex] [hex]Explanation This is a error message in the programable switching engine to indicate either anomolies which are not service impacting. Some of the messages may indicate a failure to allocate resources needed by applications.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
C_SHIM_PARTNER Messages
Error Message%L2-C_SHIM_PARTNER-3-CAP_ADD_ERR Fatal Error: Adding batched channelized interface caps failed. Reason: [chars]
Explanation 'There is an error when adding batched channelized interface caps.'
Recommended Action Please try to reload that particular SPA or restart the SPA process associated with that SPA. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-C_SHIM_PARTNER-3-CAP_CNTL_ERR Fatal Error: Failed to modify channelized interface caps. Reason: [chars]
Explanation 'There is an error when modifying channelized interface caps.'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-C_SHIM_PARTNER-3-CAP_LKP_ERR Fatal Error: Channelized caps definition file is missing. Reason: [chars]
Explanation 'The Channelized Caps definition file is missing. There may have a packaging issue or someone just accidently removed that file.'
Recommended Action Please reload the corresponding Jacket Card. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-C_SHIM_PARTNER-3-SET_CALLBACK_ERR Fatal Error: Setting call-back to IM failed. Reason: [chars]
Explanation 'There is a software error when trying to set call-back to IM.'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-C_SHIM_PARTNER-3-SVR_UBIND_ERR Fatal Error: Failed to unbind to IM. Reason: [chars]
Explanation 'There is a software error when trying to unbind to IM.'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-C_SHIM_PARTNER-4-SVR_BIND_ERR Warning: Failed to bind to IM. Reason: [chars]
Explanation 'There is a software error when trying to bind to IM.'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-C_SHIM_PARTNER-7-IFH_ERR Warning: Wrong if-handle [hex] [chars]
Explanation 'Receive a message with wrong interface handle. This may be ignored.'
Recommended Action Ignore
Error Message%L2-C_SHIM_PARTNER-7-IM_CALLBACK_ERR Warning: [chars] failed for if-handle([hex]), caps([dec]), proto([dec]). Reason: [chars]
Explanation 'There is a software error when handling messages from IM.'
Recommended Action Ignore
CCL Messages
Error Message%L2-CCL-3-INIT_ERROR Initialization failed: ([chars]%s)
Explanation The classification control list (ccl) DLL failed to initialize. This DLL does a generalization of an Access Control List to include matching on MQC match criteria like QOS group, MPLS EXP, etc. If the ccl DLL fails to initialize, the access control list cannot be programmed into the hardware. %s - indicates the reason for the initialization failure. %s - is the decoded error reason.
Recommended Action The failure should be handled by the process that is loading the DLL. The calling process should retry the initialization. Collect all debug information if the DLL is continually failing: 'debug ccl ace error location 0/x/cpu0' 'debug ccl api detail location 0/x/cpu0'
CONGA Messages
Error Message%L2-CONGA-3-ERR_MEM_ALLOC Failed to allocate [dec] bytes from [chars] ([chars])
Explanation The process failed to allocate memory. Most likely, all system memory has been allocated already.
Recommended Action Verify that the card has at least the minimum supported memory configuration. Use the 'show memory' and 'show processes memory location' commands to identify what processes use the memory. If memory usage for a process seems abnormal, restarting the process using the command 'process restart' could be a workaround.
Error Message%L2-CONGA-3-ERR_THREAD_MUTEX_LOCK Failed to lock mutex
Explanation The process failed to obtain a software mutex lock. Software mutex are used to protect certain operations from being executed simultaneously by concurent processes. This indicates a software error which could lead to data corruption and loss of traffic.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CONGA-3-ERR_THREAD_MUTEX_UNLOCK Failed to unlock mutex
Explanation The process failed to obtain a software mutex unlock. Software mutex are used to protect certain operations from being executed simultaneously by concurent processes. This indicates a software error which could lead to data corruption and loss of traffic.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CONGA-3-MEM_MAP EGRESSQ: memory mapping of tx mgid failed ([chars])
Explanation The process could not map the egress asic MGID SDRAM into its memory space.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CONGA-4-ANOMALY EGRESSQ: [chars]: error [hex]
Explanation A SW exception occurred in CONGA Library
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CONGA-4-ERR_MEM_ALLOC_SHMWIN Failed to open shared memory window [chars] ([chars])
Explanation The process failed to open the specified shared memory window. This problem can be caused by a lack of system memory.
Recommended Action Verify that the card has at least the minimum supported memory configuration. Use the 'show memory' and 'show processes memory location' commands to identify what processes use the memory. If memory usage for a process seems abnormal, restarting the process using the command 'process restart' could be a workaround.
Error Message%L2-CONGA-4-ERR_MEM_FREE Failed to free [chars] ([chars])
Explanation The process failed to free memory. This is likely a symptom of software corruption. The system may be in an unstable condition. The software failed to free memory, and this can eventually lead to an out-of-memory condition.
Recommended Action Use the 'show memory' and 'show processes memory location' commands to identify what processes use the memory. If memory usage for a process seems abnormal, restarting the process using the command 'process restart' could be a workaround.
Error Message%L2-CONGA-4-ERR_MUTEX_INIT Failed to [chars] ([chars])
Explanation The process failed to initialize a software mutex. Software mutex are used to protect certain operations from being executed simultaneously by concurent processes. This indicates a software error which could lead to eventual data corruption and loss of traffic.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CONGA-4-ERR_MUTEX_REVIVE Failed to register for mutex revival ([chars])
Explanation The process failed to register for mutex revival. In the event of a software error where another process would crash while holding a shared mutex, this process would not self-recover. This warning does not cause any degradation in the router operation. The warning simply means that a particular error recovery mechanism will not be effective.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CONGA-4-ERR_PLATFORM_INFO Failed to obtain platform info for [chars] ([chars])
Explanation The process failed to obtain information on the specified shared memory window. This will prevent proper initialization and operation multicast feature. This indicates a software error 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%L2-CONGA-6-INFO_MSG EGRESSQ: [chars]
Explanation This is a Informational message in the XBMA Driver to indicate an operation.
Recommended Action No action is required.
ETHER Messages
Error Message%L2-ETHER-1-CONFIGERROR Ethernet: Invalid configuration, [chars] is not supported by this interface
Explanation Invalid configuration
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ETHER-1-IMERROR Ethernet: [chars]() line [dec]: interface manager call [chars] failed: [chars]
Explanation The call to im failed for some reason.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ETHER-2-DEVCTLFAILED Ethernet: [chars]: devctl failed with code [hex]
Explanation A devctl call 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%L2-ETHER-2-OUTOFMEMORY Ethernet: [chars]() line [dec]: out of memory, unable to create [chars]
Explanation Card has no more memory available.
Recommended Action Verify that the card is not out of memory. Contact your Cisco technical support representative if the problem persists.
Error Message%L2-ETHER-2-SYSDBREGISTERFAILED Ethernet: Sysdb registration failed ([chars])
Explanation The driver failed to initialize communication with sysdb.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ETHER-3-BADASYNCEVENT Ethernet: Unknown asynchronous event [dec] in [chars]
Explanation An invalid asynchronous event was received by the driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ETHER-3-DILBFAILED Ethernet: [chars]() line [dec]: failed to [chars].
Explanation A dilb call failed, preventing communication between threads/processes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ETHER-3-DPCFAILED Ethernet: [chars]() line [dec]: DPC call to [chars] failed.
Explanation A direct procedure call 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%L2-ETHER-3-EDMERROR Ethernet: [chars]() line [dec]: Bad sysdb call for tuple [chars]: [chars]
Explanation An edm sysdb call was improperly formed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ETHER-3-INITFAILED Ethernet: [chars]() line [dec]: init failed in function [chars]: [chars]
Explanation Basic initialization failed due to problem in a called function.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ETHER-3-INVALIDARGSIZE Ethernet: Incompatible structure definition for [chars] in [chars]
Explanation A structure passed is the wrong size due most likely to compilation problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ETHER-3-INVALIDTIMER Ethernet: [chars](): Invalid timer type [dec]
Explanation An invalid timer type was found in an expired timer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ETHER-3-RESTARTFAILED Ethernet: [chars]() line [dec]: [chars]: [dec]
Explanation Restarting the driver failed for some reason.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. If the problem persists, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ETHER-3-TIMERINITFAILED Ethernet: Failure initializing asynchronous timers: [chars]() - [chars]
Explanation A failure occured while creating or initializing the timers for the driver.
Recommended Action Make sure there is enough memory available. Contact your representative if the problem persists.
Error Message%L2-ETHER-3-UNSUPPORTEDSTATS Ethernet: Unsupported stats request [dec] in [chars]
Explanation A driver has requested an unsupported stats type.
Recommended Action Copy the error message exactly as 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%L2-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%L2-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%L2-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%L2-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%L2-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%L2-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%L2-FIA-3-FIAHW_CHIP Failed to configure [chars] config value in hardware
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 of the failure is 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%L2-FIA-3-FIAHW_CRC16 Too many CRC errors on fabric serial line (from slot [dec])
Explanation This error indicates a problem in the interface between the card reporting error and the switch fabric card in the indicated slot. 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%L2-FIA-3-FIAHW_CRC16 Too many CRC errors on fabric serial line (from slot [dec])
Explanation This error indicates a problem in the interface between the card reporting error and the switch fabric card in the indicated slot. 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%L2-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%L2-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%L2-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%L2-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%L2-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%L2-FIA-3-FIAHW_LOS Persistent LOS on serial link (from slot [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 slot. 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%L2-FIA-3-FIAHW_LOS Persistent LOS on serial link (from slot [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 slot. 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%L2-FIA-3-FIAHW_LOS_CLEAR LOS cleared on serial link (from slot [dec])
Explanation An earlier reported error (Loss of Sync) is now cleared. Normal operations can resume.
Recommended Action No action is required.
Error Message%L2-FIA-3-FIAHW_LOS_CLEAR LOS cleared on serial link (from slot [dec])
Explanation An earlier reported error (Loss of Sync) is now cleared. Normal operations can resume.
Recommended Action No action is required.
Error Message%L2-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%L2-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%L2-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%L2-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%L2-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%L2-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%L2-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%L2-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%L2-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%L2-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.
FWD_EDGE_COMMON Messages
Error Message%L2-FWD_EDGE_COMMON-3-EDGE_ADJ_ERR adj engine layer internal error [chars] : [chars]
Explanation A runtime failure occurred in adjacency engine layer resulting in a failure to provide some system service as indicated in the message text. This is most likely an internal error. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
GSR_aib Messages
Error Message%L2-GSR_aib-3-RES_ERROR Error: [chars]: Err=[chars]
Explanation A error occurred in GSR aib Driver resulting in a failure to provide some system service as indicated in the message text.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-GSR_aib-6-INFO_MSG Info: [chars]
Explanation This is a Informational message in the GSR aib driver to indicate an operation.
Recommended Action No action is required.
GSR_edge_fwd_lib Messages
Error Message%L2-GSR_edge_fwd_lib-3-RES_ERROR [chars]: Err=[chars]
Explanation An error occurred in Edge fowarding lib resulting in a failure to provide some system service as indicated in the message text. %s - indicates the reason for the failure. %s - is the decoded error reason. This error indicates there is problem in LC Forwarding resources
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
GSR Messages
Error Message%L2-GSR-2-FIA_INT_FIFO [chars] [chars] ([hex])
Explanation This error usually indicates an internal hardware problem on the card.
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. Use 'diag verbose' command. (This command may not work for the slot containing the primary route processor.) If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-2-FIA_INT_PARITY [chars] [chars] ([hex])
Explanation This error usually indicates an internal hardware problem on the card.
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. Use 'diag verbose' command. (This command may not work for the slot containing the primary route processor.) If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-2-SPABRG_CRIT_INFO [chars] : [dec]
Explanation This message indicates a slew of interrupts are being generated from the SPA bridge ASIC. This error triggers error recovery if more than 50 interrupts are received from the SPA bridge ASIC. The second parameter in the error messgae indicates the interrupt count in the last second. The SPA bridge ASIC will be reset as part of this recovery action. This error may affect traffic flow.
Recommended Action Wait for several minutes for the recovery operation to complete. If problem still persists, restart the 'spa_192_jacket' process and ensure all the SPAs are securely inserted in the bays.
Error Message%L2-GSR-3-FIA_CHIP Failed to update [chars] config value on slot [dec], value=[hex] mask=[hex]
Explanation The low level fia driver was unable to complete its operation. Possible cause is failure to synchronize.
Recommended Action Wait several minutes for corrective action to occur. 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%L2-GSR-3-FIA_CHKPT Call to [chars] failed, chkpt_status=[hex]
Explanation The library call 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%L2-GSR-3-FIA_CHKPT_DATA_EXISTS The driver is coming up in NORMAL_MODE, but checkpoint information already exists.
Explanation When a driver comes up in NORMAL_MODE, checkpointing data should not already exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_CHKPT_NOINIT Error initializing checkpointing table.
Explanation The driver was not able to initialize a table to store checkpointed data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_CHKPT_NORESTORE The driver was not able to restore '[chars]' from checkpointed data.
Explanation No checkpointing record was found in the table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_CHKPT_NOSAVE The driver was not able to save '[chars]' in checkpointed data.
Explanation FIA configuration information could not be saved in the checkpoint record.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_CHKPT_RECOVERY_NODATA The driver is coming up in RECOVERY_MODE, but the checkpoint info does not exist.
Explanation When a driver comes up in RECOVERY_MODE, checkpointing data should have already been saved to the checkpointing record by the previous life of the driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_CONFIG Failed to set [chars] config value, cerrno=[hex]
Explanation The high level fia driver was unable to complete its operation.
Recommended Action Wait several minutes for corrective action to occur. 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%L2-GSR-3-FIA_CRC16 Too many crc errors on fabric serial line (from slot [dec])
Explanation This error indicates a problem in the interface between the card reporting error and the switch fabric card in the indicated slot.
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, 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%L2-GSR-3-FIA_CTX Invalid context information received ([chars])
Explanation A internal callback function was called with improper input.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_DEVCTL Fia devctl failed for [chars]
Explanation The low level fia driver was unable to complete its operation.
Recommended Action Wait several minutes for corrective action to occur. 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%L2-GSR-3-FIA_DEVCTL_ERR Unsupported devctl case [dec]
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_DI_INVALID_MODE DI started the driver in an invalid mode: [hex]
Explanation The Driver Infrastructure (DI) started the driver in an invalid or unsupported mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_DLOPEN Failed to load [chars]
Explanation The library (dll) named could not be found or there was an error while loading. Indicates a software installation problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_DLSYM Could not map symbol [chars] in fia chip library dll
Explanation Invalid dynamic library.
Recommended Action Reload software on slot which reports this error. See 'microcode reload' and 'hw_module' commands. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_EVENT Call to [chars] failed, errno=[hex]
Explanation The library call 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%L2-GSR-3-FIA_EVMC Call to c12000_evm_create failed (pathname [chars])
Explanation The library call failed. The cause would have been reported by the library.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_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.
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, 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%L2-GSR-3-FIA_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.
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, 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%L2-GSR-3-FIA_FCTL [chars] failed in [chars]([dec]), slot = [dec], errno = [dec], [chars]
Explanation An interprocess call returned an error. Possibly a timeout.
Recommended Action Look for other fctl messages. Wait for corrective action. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_INT Unexpected [chars] interrupt
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_LOS Persistent LOS on serial link (from slot [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 slot.
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, 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%L2-GSR-3-FIA_MEM Memory allocation failed for [chars]
Explanation Memory was not available for an internal data structure.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_MEM_CHIP_ERR ([chars]): no memory for chip data.
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_MEM_ERROR ([chars]): FIA failed to initialize memory. Exiting
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_MMAP_ERROR ([chars]): FIA memory mapping failed. Exiting
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_NOHALT Unexpected [chars] interrupt without halt
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_NOT_RESET FIA was not reset before programming
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_PDATA Invalid par_data ([hex]) received from upper layer driver
Explanation There is a mismatch between two driver components. Either the data is is NULL or it is the wrong size. Indicates a software installation problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_PTHREAD Call to [chars] failed, errno=[hex]
Explanation The kernel call 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%L2-GSR-3-FIA_RATEI No timer interval for [chars]
Explanation An internal data structure was missing a field.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_RATEW No timer wheel for [chars]
Explanation An internal data structure was missing a field.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_RELTOKEN Failed to release DI access token in [chars] (code [hex])
Explanation An unexpected error has occurred. A resource could not be released.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_SOFTREQ [chars] Software request error [hex]
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_STARTUP_DATA ([chars]), Illegal size of input for FIA startup data structure
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_STTMR [chars] timer could not be started. cerrno=[hex]
Explanation An error occurred when an internal timer was being started.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_SYNC_ERROR ([chars]): FIA failed to sync, los_status [hex], los_error [hex], fia_config [hex]
Explanation This error usually indicates an internal hardware problem on the card.
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. Use 'diag verbose' command. (This command may not work for the slot containing the primary route processor.) If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_SYSDB_BIND could not bind to sysdb rc=[hex], [chars]
Explanation The fia driver could not bind to sysdb.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_TMR Call to [chars] failed, cerrno=[hex]
Explanation The library call 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%L2-GSR-3-FIA_TOKEN Failed to acquire DI access token in [chars] (code [hex])
Explanation An unexpected error has occurred. A software resource was unavailable.
Recommended Action Wait for corrective action. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_UNHALT Could not unhalt [chars]
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_UNHANDLED Unexpected error case
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_UNSUPPORTED_CDB Unsupported cdb version
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-FIA_UNSUPPORTED_OPAQUE_DATA Unsupported opaque data version
Explanation An unexpected error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-3-SPABRG_ERR_HW [chars] : [chars] : [hex]
Explanation EE192 Spabrg driver error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%L2-GSR-3-SPABRG_ERR2_HW [chars] : [chars] : [hex] [hex]
Explanation EE192 Spabrg driver error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%L2-GSR-3-SPABRG_ERR3_HW [chars] : [chars] : [hex] [hex] [hex]
Explanation EE192 Spabrg driver error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%L2-GSR-4-FIA_NOREF Timer expired without reference
Explanation An internal timer expired but could not be handled.
Recommended Action No action required for occasional occurrence of this message. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-GSR-5-FIA_NOLOS LOS cleared on serial link (from slot [dec])
Explanation An earlier reported error (Loss of Sync) is now cleared. Normal operations can resume.
Recommended Action No action is required.
Error Message%L2-GSR-6-SPABRG_CRIT_INFO [chars] : [chars] : [hex]
Explanation EE192 Spabrg driver critical info
Recommended Action NONE : Informational message only
Error Message%L2-GSR-6-SPABRG_INFO1_HW [chars] : [chars] : [hex]
Explanation EE192 Spabrg driver informational message
Recommended Action NONE : Informational message only
Error Message%L2-GSR-6-SPABRG_INFO2_HW [chars] : [chars] : [hex], [hex]
Explanation EE192 Spabrg driver informational message
Recommended Action NONE : Informational message only
Error Message%L2-GSR-6-SPABRG_INFO3_HW [chars] : [chars] : [hex], [hex], [hex]
Explanation EE192 Spabrg driver informational message
Recommended Action NONE : Informational message only
HALE_QOS Messages
Error Message%L2-HALE_QOS-3-ERR_COMMIT Route ([chars],[chars])
Explanation This message indicates a failure in committing route (S, G). This means QoS feature will not be applied for the specified route; Traffic through this route would go to the default queue. The causes for this error could be lack of memory, a hardware resource limitation, or an internal error. %s,%s - indicates the (S, G)
Recommended Action If memory is the issue, reduce other system activity to ease memory demands. If conditions warrant and minimum memory requirements not met, upgrade to a larger memory configuration. Retry the QoS configuration. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
HFA_COMMON Messages
Error Message%L2-HFA_COMMON-3-FATAL_ERR Fatal error: [chars]: Err=[chars]
Explanation A fatal error occurred in HFA common Driver which involves exiting the 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%L2-HFA_COMMON-4-ANOMALY [chars]
Explanation A SW exception of unexpected condition or an out of resources (memory, HW profiles, etc) situation.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-HFA_COMMON-6-INFO_MSG [chars] [chars]
Explanation This is a Informational message in the HFA common Driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-HFA_COMMON-6-INFO_WARNING [chars] err [hex]
Explanation This is a Informational message in the HFA common Driver to indicate an operation.
Recommended Action No action is required.
HFA_LIB Messages
Error Message%L2-HFA_LIB-3-ANOMALY [chars]
Explanation Software exception. Quite probably a SW bug.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-HFA_LIB-3-BLWM_CLIENT_CONF_FAILED hfa: blwm client configuration failed, error: [hex] [chars]
Explanation Unable to configure BLWM client 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%L2-HFA_LIB-3-BLWM_CLIENT_REBIND_FAILED hfa: blwm client rebind failed, error: [hex] [chars]
Explanation Unable to rebind with BLWM client functionality after a connection reconnect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-HFA_LIB-3-BLWM_MSG_SEND_FAILED hfa: blwm msg send/flush: retried: [dec] time(s), failed to send, error: [hex] [chars]
Explanation Unable to send/flush a BLWM message to the HFA 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%L2-HFA_LIB-3-BLWM_RECVD_REPLY_FAIL hfa: Received a failure reply code for a batched request, reply code: [dec]
Explanation This is the message printed by the default handler installed by HFA to process the replies received for batched requests. The default handler's behavior is to just print this message. The application should install its own handler to handle the replies to batched requests.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-HFA_LIB-3-MSG_SEND_FAILED hfa: msg: [dec], retried: [dec] time(s), failed to send, errno: [chars]
Explanation Unable to send a message to the HFA 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%L2-HFA_LIB-4-BLWM_REPLAY_REQUEST hfa: Replaying a batched request of type [dec] that might have been partially processed before.
Explanation Due to a server restart, a batched request might have been partially processed. The default handler installed by HFA simply replays the request. Applications that can not afford to replay a request should install their own handler.
Recommended Action No action is required.
Error Message%L2-HFA_LIB-6-INFO_WARNING [chars]: [dec]
Explanation This is a Informational message in the HFA client LIB to indicate an operation.
Recommended Action No action is required.
LC Messages
Error Message%L2-LC-1-TESTALERT [chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message%L2-LC-2-TESTCRIT [chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message%L2-LC-3-BMA_CHKPT Call to [chars] failed, chkpt_status=[hex]
Explanation The library call 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%L2-LC-3-BMA_CHKPT_NOINIT Error initializing checkpointing table.
Explanation The driver was not able to initialize a table to store checkpointed data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LC-3-BMA_CHKPT_NORESTORE The driver was not able to restore '[chars]' from checkpointed data.
Explanation No checkpointing record was found in the table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LC-3-BMA_CHKPT_NOSAVE The driver was not able to save '[chars]' in checkpointed data.
Explanation BMA buffer carve information could not be saved in the checkpoint record.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LC-3-BMA_CHKPT_RECOVERY_NODATA The driver is coming up in RECOVERY_MODE, but the checkpoint info does not exist.
Explanation When a driver comes up in RECOVERY_MODE, checkpointing data should have already been saved to the checkpointing record by the previous life of the driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LC-3-BMA_DI_INVALID_MODE DI started the driver in an invalid mode: [hex]
Explanation The Driver Infrastructure (DI) started the driver in an invalid or unsupported mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LC-3-BMA48ERR [chars] BMA error: stat_reg [hex] adr [hex] data [hex] qm [hex] plim [hex] l3 [hex] ms [hex] sdram [hex]
Explanation There is an error in the BMA (reg. information).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMA48ERRS [chars] BMA48 [chars] error [hex]
Explanation There is an error in the BMA48.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMA48FIM [chars] BMA48 [chars] error fim_cf_status [hex]; fim_df0: adr [hex] data [hex]; fim_df1: adr [hex] data [hex]; fim_df2: adr [hex] data [hex]; fim_df3: adr [hex] data [hex]
Explanation There is an error in the BMA.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMABUFF [chars] BMA has [unsigned int] buffers in queue [unsigned int] when maximum of [unsigned int] are allowed
Explanation Number of buffers in one of the BMA queues has overflowed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMACMDFTCH Problem in BMA command fetching, status=[dec] [chars] BMA
Explanation The BMA encountered problems while trying to fetch the given command. If appears more than once we may have a HW problem. The GRP should recognize a lost of communication with the LC and reload it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-BMACMDLOST [chars] BMA has lost a command
Explanation The given BMA has lost a command. If appears more than once we may have a HW problem. The GRP should recognize a lost of communication with the LC and reload it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-BMACMDRPLY Problem in BMA reply to command type [dec] [chars] BMA sequence no=[dec]
Explanation There was a problem in the reply to the given BMA command. If appears more than once we may have a HW problem. The GRP should recognize a lost of communication with the LC and reload it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMAERR [chars] error: msstat [hex] dma0 [hex] dma1 [hex] dma2 [hex] qm [hex] plim [hex] fia [hex] l3 [hex] ms [hex] sdram [hex]
Explanation There is an error in the BMA (reg. information).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMAERRS [chars] [chars] error [hex]
Explanation There is an error in the BMA.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMAERRSS [chars] [chars] error [hex] [chars] [hex]
Explanation There is an error in the BMA.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMAMEM [chars] SDRAM data error [hex] in address [hex]
Explanation Packet memory parity error. Each bit (0-15) set in data error word represents a parity error in one byte of the errored location in memory. Bits 16 and 17 of data error word, if either is set, indicate the error happened during CPU access to the packet memory, otherwise it is during normal operation. Address represents the offset of the memory location being accessed from the beginning of packet memory on the side mentioned (to or from fabric.) This error indicates a possibly temporary problem in either the packet memory device or the BMA.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LC-3-BMASDRAM_BADCAS_LATENCY [chars] DIMMs do not support CAS latency needed. got [hex]
Explanation SDRAM DIMM modules installed in BMA SDRAM DIMM sockets do not support CAS latency needed. CAS latency is specified in the DIMM EEPROM as a number. When converted to a binary number, each bit corresponds to one CAS latency. Bit 2 must be set to 1, indicating that a CAS latency of 3 is supported.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMASDRAM_BADSIZE [chars] DIMMs are of unsupported size. Read this: rows [dec], cols [dec], DIMM banks [dec], SDRAM Device banks [dec]
Explanation SDRAM DIMM modules installed in BMA SDRAM DIMM sockets are of unsupported size.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMASDRAM_BADWIDTH [chars] DIMMs have unsupported data width, expected [dec], got [dec]
Explanation SDRAM DIMM modules installed in BMA SDRAM DIMM sockets have unsupported data width.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMASDRAM_NOTMATCH [chars] SDRAM DIMMs do not match
Explanation SDRAM DIMM modules installed in to Fabric or from Fabric BMA DIMM0 and DIMM1 sockets do not match. While the DIMMs on one side (to Fabric) could be different from the DIMMs on the other side (from Fabric), the two DIMMs on the same side have to be identical. Also, all four DIMMs need to be mounted and making proper contact.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMAUCODE_GET [chars] BMA: feature [chars], line card type [chars], could not get [chars] BMA microcode
Explanation For the BMA microcode download command, failed to get the given BMA microcode bundled in the image.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMAUCODE_LCTYPE [chars] BMA: feature [chars], specified linecard type(s) ([hex]) != current ([hex])
Explanation For the BMA microcode download command, there was a mismatch between what was specified in the BMA microcode file and the current type of line card
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-BMAUCODE_NULL Null downloaded BMA microcode
Explanation For the BMA microcode download command, failed to get the given BMA microcode bundled in the image because it is null.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-CARVE_BUFHDRS [chars] BMA: out of SDRAM buffer headers
Explanation Ran out of available SDRAM buffer headers while attempting to carve buffers. This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-CARVE_BUFSIZE [chars] BMA: illegal specified/real SDRAM buffer size(s) = ([unsigned long int],[unsigned long int]). Range=([dec],[dec])
Explanation The calculated SDRAM buffer size (in bytes and including header and data portions), is not within the given range. This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-CARVE_EXBUFS [chars] BMA: [unsigned int] SDRAM buffers max ([unsigned int])
Explanation The maximum number of SDRAM buffer headers is limited to a maximum number which has been exceeded. This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-CARVE_EXFREEQS [chars] BMA: [unsigned int] free queues max ([unsigned int])
Explanation Number of free queues allowed for SDRAM buffer carving has been exceeded. This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-CARVE_EXPCT [chars] BMA: [unsigned int] sum SDRAM buffer percentages 100
Explanation The sum of percentages per SDRAM buffer size has exceeded 100. This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-CARVE_EXSDRAM [chars] BMA: used SDRAM ([unsigned long long int] bytes) available for carve ([unsigned long int] bytes)
Explanation The calculated sum of SDRAM to be carved is larger than the available SDRAM for carving. This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-CARVE_NOFREEQS [chars] BMA: no more free queues
Explanation There are no more available free queues which can be used for SDRAM buffer carve. This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-CARVE_PARMS [chars] BMA: = 1 SDRAM bufmem parameters == 0
Explanation This is an internal parameter error with one or more SDRAM buffer memory parameters: maximum buffer header count or SDRAM sizes (total, not available for carve, and available for carve
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-CARVE_QELEM [chars] BMA: [unsigned int] Queue Manager SRAM elements max ([unsigned int])
Explanation Ran out of Queue Manager elements, which are used for SDRAM buffer carving. This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-CARVE_QMREAD BMA address [hex]: Queue Manager SRAM [hex], read error(s)
Explanation This happened during Queue Manager SRAM initialization. Reading one or more zeroed Queue Manager SRAM locations gave a non-zero result. Possible errors are in head, tail, length, length threshold, buffer address, next queue element, or scratch RAM locations.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-DOWNREV BMA is an old version.
Explanation The system software detected an old version of the BMA.
Recommended Action Call your technical support for an upgraded verion.
Error Message%L2-LC-3-IICDEV_NOTACKADDR IIC Device [dec] failed to ack address
Explanation BMA SDRAM DIMM failed to acknowledge address. This is an SDRAM IIC bus protocol error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-IICDEV_NOTACKREAD IIC Device [dec] failed to ack read command
Explanation BMA SDRAM DIMM failed to acknowledge read command. This is an SDRAM IIC bus protocol error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-IICDEV_NOTRESPOND IIC Device [dec] does not respond, perhaps absent
Explanation BMA SDRAM DIMM does not respond, perhaps absent.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-INIT_CARD_TYPE Unknown card type ([hex])
Explanation A card was either manufactured improperly, has failed, or is newer than the software
Recommended Action Replace the card or upgrade the software
Error Message%L2-LC-3-INIT_MEM Memory failure, addr [hex], read [hex]%08x, not [hex]%08x
Explanation Initialization of the memory address failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-INIT_READ Error reading memory at [hex]
Explanation Failed to read the given memory location.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-INIT_RESET Failed to take line card out of reset
Explanation Initialization of the line card IO registers failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-INIT_ZERO No bytes to write to location [hex]
Explanation No bytes were written to the given location.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-INVQ Invalid local output queue: [hex] [hex] [hex] [hex] [hex] [hex]
Explanation The above packet was routed to an invalid queue. The data shown s the packet header.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-L3FEERR L3FE error: rxbma [hex] addr [hex] txbma [hex] addr [hex] dram [hex] addr [hex] io [hex] addr [hex]
Explanation There was an error in the line card's L3FE ASIC (reg. information).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-L3FEERRS L3FE [chars] error [hex] address [hex]
Explanation There was an error in the line card's L3FE ASIC.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-LC_CODE_DLD_ALLOC Failed buffer allocation for code download
Explanation Could not allocate a data buffer to contain contents of the given linecard downloaded file. There may be insufficient DRAM.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-LC_CODE_DLD_CHKSUM code download IPC data checksum error
Explanation For the GLC code download command, failed the checksum verification.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-LC_CODE_PROG no downloaded code to program
Explanation For the GLC code program command, no downloaded code to program.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-LOOKUP_ERROR Hardware assist lookup error [hex] in memory encountered
Explanation Memory corruption detected.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-MACSTR Adj/midb ([chars]) has incorrect high word ([hex]) in its mac string
Explanation The line card CEF/MDS received an adjacency/midb with the incorrect mac rewrite string. Packets forwarded to that adjacency/midb will be dropped.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-OUTINFO Adj/midb([chars]): incorrect output_info=[hex] maclen=[dec]
Explanation The line card CEF/MDS received an adjacency/midb with the incorrect output_info field. Packets forwarded to that adjacency/midb will be dropped.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-3-PARITYERRTTM48 Parity error in memory encountered
Explanation One bit memory corruption detected.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-SELECTOR [dec]: unknown BMA selector value
Explanation An unknown BMA selector value was encountered.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative
Error Message%L2-LC-3-TESTERR [chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message%L2-LC-4-CARVE_JVMASK [chars] BMA: suspect return value [dec] on quiesce-for-carve
Explanation The BMA quiesce-for-carve algorithm retrieved a bad jump vector mask return value. This could indicate an error in the quiesce.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-4-CARVE_TIME [chars] BMA: quiesce-for-carve exceeded timeout ([dec] ms) in [chars] loop, [dec] times
Explanation The BMA quiesce-for-carve algorithm waits an allotted time for line card queues to flush. One or more waits exceeded this allotted time. These queues are specific to the line card's ASICs. This error message might not actually indicate an error - the allotted time might not be sufficient and should be increased.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LC-4-TESTWARNING [chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message%L2-LC-5-TESTNOTICE [chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message%L2-LC-6-TESTINFO [chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message%L2-LC-7-TESTDEBUG [chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
PFILTER_EA Messages
Error Message%L2-PFILTER_EA-3-INIT_ERROR Process initialization failed: ([chars]%s)
Explanation The pfilter_ea process failed to initialize. This pfilter_ea process programs the 'packet filter' security access control list in the hardware. If the pfilter_ea process fails to initialize, the access control list cannot be programmed into the hardware. %s - indicates the reason for the initialization failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process pfilter_ea location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart pfilter_ea location 0/x/cpu0'. Collect all debug information if the process is continually restarting 'debug pfilter-ea all' (during the process restart). If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PFILTER_EA-7-EVENT_ERROR Event Failure: ([chars])
Explanation The pfilter_ea process received a bad event. This pfilter_ea process programs the 'packet filter' security access control list in the hardware. %s - is the decoded error reason.
Recommended Action Monitor the event messages. The pfilter_ea process will handle the failure gracefully but if they continually appear on the console, try doing 'process restart pfilter_ea location 0/x/cpu0'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PIRANHA Messages
Error Message%L2-PIRANHA-4-ANOMALY INGRESSQ: [chars]: reg [hex]
Explanation A SW exception occurred in PIRANHA Library
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PIRANHA-6-INFO_MSG INGRESSQ: [chars]: error [hex]
Explanation This is a Informational message in the XBMA Driver to indicate an operation.
Recommended Action No action is required.
plim_4p_oc12 Messages
Error Message%L2-plim_4p_oc12-3-ALLOC_FAILED Process failed to allocate memory [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialized due to unavailable memory and will be restarted. It may affect traffic passing through the ports located on the PLIM. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller,...
Recommended Action The System Manager process (sysmgr) will automatically restart this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_4p_oc12 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-CREATE_THREAD_ERROR Process init failed [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialize. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller,... %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_4p_oc12 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-DEBUG_INIT_ERROR Debugging subsystem initialization failed
Explanation Physical Layer Interface Module(PLIM) driver failed to initialize it's debug subsystem. As result plim debug commands will not work on the PLIM module in question. The rest of functionality of the PLIM driver remains unaffected by the failure. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller.
Recommended Action Restart the process using 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0'. Process restart may affect traffic on all 4 oc12 interfaces located on the line card. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-ERR_EVM_CREATE Interface module driver initialization failed
Explanation Physical Layer Interface Module(PLIM) driver failed to initialize. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller. As result of such failure no trafiic may pass on all 4 oc12 ports located on the 4 port linecard. The interfaces associated with failed PLIM will not come up.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered to recover. Execute 'show process pl_e48_pos_4p_oc12 location 0/slot/cpu0' to verify that the process is up and running. If it's not operational attempt to restart the process using command 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-ERR_EVM_EVENT_BLOCK process received invalid event [chars]
Explanation Physical Layer Interface Module(PLIM) driver experience an errorr while awaiting for event arrival. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller. As result of the error the PLIM process will be restarted. Traffic may be interrupted on all affected interfaces. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered to recover. Execute 'show process pl_e48_pos_4p_oc12 location 0/slot/cpu0' to verify that the process is up and running. If it's not operational attempt 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0 If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-ERR_PORT_INIT PLIM port init failed [dec] stage-[chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialize port. As result of the failure affected interfaces will not come up. %d - failed port number %s - specific stage of port initialization that failed PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer and Packet Over Sonet(POS) controller.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_4p_oc12 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-FWD_REGISTER_ERROR Process initialization error [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialized and will be restarted. It will affect traffic passing through the ports located on the PLIM. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller,... %s - error code
Recommended Action The System Manager process (sysmgr) will automatically restart this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_4p_oc12 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-PORT_AVAILABLE_FAILED Port failed to become available [chars] [dec]
Explanation Physical Layer Interface Module(PLIM) driver failed to make port available for forwarding. The interface in question will not forward packets. %s - error code %d - port number
Recommended Action Restart the process using 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0'. Process restart may affect traffic on all 4 oc12 interfaces located on the line card. Reload the line card using 'hw-module location 0/slot/cpu0 reload' if the process restart failed to solve the problem.. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-RESET_FAILED PLIM reset failed [chars]
Explanation The Physical Layer Interface Module(PLIM) driver failed to reset PLIM hardware. %s - error code PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller.
Recommended Action If the error occurred during user command execution retry the command and if the error persist consider restarting plim process ( 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0'. PLIM process restart may affect traffic on all 4 oc12 ports. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-STATS_COLLECT_REGISTER_FAILED Statistics collector registration error [chars] [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to register PLIM interface statistics collector. No interface statistics such as sonet counters and packet counters will be available on the specified interface. %s - contains interface name %s - contains error code
Recommended Action Restart the process using 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0'. Process restart may affect traffic on all 4 oc12 interfaces located on the line card. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-STATSD_COLL_INIT_ERROR Process initialization error [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialized and will be restarted. It will affect traffic passing through the ports located on the PLIM. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller,... %s - error code
Recommended Action The System Manager process (sysmgr) will automatically restart this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_4p_oc12 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-TIMER_INIT_FAILED Process init failed [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialize. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller,... %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_4p_oc12 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-3-TX_CLK_GET_INVALID_PORT_CTX Failed to retrieve tx clock source
Explanation Physical Layer Interface Module(PLIM) driver was unable to determine transmit clock source for the sonet port. The error may appear during show or configuration of the sonet port.
Recommended Action If the error occurred during user command execution retry the command and if the error persist contact technical support.
Error Message%L2-plim_4p_oc12-3-TX_CLK_SET_INVALID_PORT_CTX Failed to configure tx clock source for sonet port
Explanation Physical Layer Interface Module(PLIM) driver failed to make configure transmit clock source for the sonet port. The sonet port hardware configuration is invalid and may result in traffic being dropped or high error count on the port. This error may appear during attempt to configure clock source for the sonet port.
Recommended Action Retry the sonet port configuration. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_4p_oc12-4-INVALID_TIMER Invalid timer [dec]
Explanation Physical Layer Interface Module(PLIM) driver received unknown timer event. %d - timer 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.
PLIM_IOX_4P_GE Messages
Error Message%L2-PLIM_IOX_4P_GE-3-INIT_ERR Initialization error: [chars]: [chars]
Explanation The 4 port Gigabit Ethernet (GE) driver failed to initialize properly. This driver provides the system access to the hardware. A failure during initialization of this process may render the interfaces provided by the hardware unusable. %s - indicates the reason for the failure %s - is the decoded error reason
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process plim_iox_4p_ge location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart plim_iox_4p_ge location 0/x/cpu0' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PLIM_IOX_4P_GE-6-INFO_MSG [chars] [dec]
Explanation This is an Informational message in the plim_iox_4p_ge driver to indicate operation that may be of interest to the user.
Recommended Action No action is required.
Error Message%L2-PLIM_IOX_4P_GE-6-RXLOS_INT SFP Rx LOS Interrupt: port: [dec], count=[dec]
Explanation This is an informational message in the gigE driver driver to indicate a Loss of Signal (LOS) has occurred on the indicated port.
Recommended Action 1. Ensure the equipment at the far end of the link is functioning and configurations are correct. 2. Ensure the cable are installed correctly Rx plugged into far-end Tx & Tx plugged into far-end Rx 3. Check SFP and cable compatability. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
plim_oc48 Messages
Error Message%L2-plim_oc48-3-ALLOC_FAILED Process failed to allocate memory [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialized due to unavailable memory and will be restarted. It may affect traffic passing through the ports located on the PLIM. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller, optical transceiver.
Recommended Action The System Manager process (sysmgr) will automatically restart this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_1p_oc48 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-CREATE_THREAD_ERROR Process init failed [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialize. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller, optical transceiver %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_1p_oc48 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-DEBUG_INIT_ERROR Debugging subsystem initialization failed
Explanation Physical Layer Interface Module(PLIM) driver failed to initialize it's debug subsystem. As result plim debug commands will not work on the PLIM module in question. The rest of functionality of the PLIM driver remains unaffected by the failure. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller.
Recommended Action Restart the process using 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0'. Process restart may affect traffic on the oc48 interface located on the line card. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-ERR_EVM_CREATE Interface module driver initialization failed
Explanation Physical Layer Interface Module(PLIM) driver failed to initialize. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller. As result of such failure no trafiic may pass on the oc48 port located on the linecard. The interfaces associated with failed PLIM will not come up.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered to recover. Execute 'show process pl_e48_pos_1p_oc48 location 0/slot/cpu0' to verify that the process is up and running. If it's not operational attempt to restart the process using command 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-ERR_EVM_EVENT_BLOCK process received invalid event [chars]
Explanation Physical Layer Interface Module(PLIM) driver experience an errorr while awaiting for event arrival. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller. As result of the error the PLIM process will be restarted. Traffic may be interrupted on all affected interfaces. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered to recover. Execute 'show process pl_e48_pos_1p_oc48 location 0/slot/cpu0' to verify that the process is up and running. If it's not operational attempt 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0 If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-ERR_MBUS_OP Optical parameter measurement error [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to measure laser bias or optical receive power. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller, optical transceiver. PLIM driver performs periodic measurements of the laser bias and received signal optical power. The results of such measurements are represented in the 'show controller pos 0/slot/0/0' command under the 'optical power monitoring' section. %s - error code
Recommended Action If the error persist reset the linecard using 'hw-module location 0/slot/CPU0 reload' command. The line card restart may affect traffic passing on the oc48 interface. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-ERR_PORT_INIT PLIM port init failed [dec] stage-[chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialize port. As result of the failure affected interfaces will not come up. %d - failed port number %s - specific stage of port initialization that failed PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer and Packet Over Sonet(POS) controller.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_1p_oc48 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-FWD_REGISTER_ERROR Process initialization error [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialized and will be restarted. It will affect traffic passing through the ports located on the PLIM. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller, optical transceiver. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically restart this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_1p_oc48 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-PORT_AVAILABLE_FAILED Port failed to become available [chars] [dec]
Explanation Physical Layer Interface Module(PLIM) driver failed to make port available for forwarding. The interface in question will not forward packets. %s - error code %d - port number
Recommended Action Restart the process using 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0'. Process restart may affect traffic on the oc48 interface located on the line card. Reload the line card using 'hw-module location 0/slot/cpu0 reload' if the process restart failed to solve the problem. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-RESET_FAILED PLIM reset failed [chars]
Explanation The Physical Layer Interface Module(PLIM) driver failed to reset PLIM hardware. %s - error code PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller.
Recommended Action If the error occurred during user command execution retry the command and if the error persist consider restarting plim process ( 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0'. PLIM process restart may affect traffic on the oc48 port located on the line card. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-STATS_COLLECT_REGISTER_FAILED Statistics collector registration error [chars] [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to register PLIM interface statistics collector. No interface statistics such as sonet counters and packet counters will be available on the specified interface. %s - contains interface name %s - contains error code
Recommended Action Restart the process using 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0'. Process restart may affect traffic on the oc48 interface located on the line card. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-STATSD_COLL_INIT_ERROR Process initialization error [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialized and will be restarted. It will affect traffic passing through the ports located on the PLIM. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller, optical transceiver %s - error code
Recommended Action The System Manager process (sysmgr) will automatically restart this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_1p_oc48 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-TIMER_INIT_FAILED Process init failed [chars]
Explanation Physical Layer Interface Module(PLIM) driver failed to initialize. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller, optical transceiver. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered. Execute 'show process pl_e48_pos_1p_oc48 location 0/slot/cpu0' to verify that the process is up and running. If the process is not operational attempt 'process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0' where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-3-TX_CLK_GET_INVALID_PORT_CTX Failed to retrieve tx clock source
Explanation Physical Layer Interface Module(PLIM) driver was unable to determine transmit clock source for the sonet port. The error may appear during show or configuration of the sonet port.
Recommended Action If the error occurred during user command execution retry the command and if the error persist contact technical support.
Error Message%L2-plim_oc48-3-TX_CLK_SET_INVALID_PORT_CTX Failed to configure tx clock source for sonet port
Explanation Physical Layer Interface Module(PLIM) driver failed to make configure transmit clock source for the sonet port. The sonet port hardware configuration is invalid and may result in traffic being dropped or high error count on the port. This error may appear during attempt to configure clock source for the sonet port.
Recommended Action Retry the sonet port configuration. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-plim_oc48-4-INVALID_TIMER Invalid timer [dec]
Explanation Physical Layer Interface Module(PLIM) driver received unknown timer event. %d - timer 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.
PPP_EA Messages
Error Message%L2-PPP_EA-3-INIT_ERROR Process Initialization Failed: ([chars]%s)
Explanation The PPP execution agent process failed to initialize. PPP execution agent programs the Physical Layer Interface Module (PLIM) for handling PPP encapsulation on a POS link and also add capsulation for slowpath packet processing. The reason of the failure could be that the interface manager could not set the interface and returned an error, or could be due to unavailability of memory resources. This can happen when the linecard is coming up, or when the encapsulation is changed to PPP. The effect is that the interface will not come up using PPP encapsulation. %s - indicates the reason for the failure. %s - is the error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process ppp_ea location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart ppp_ea location 0/x/cpu0' Also try reapplying the configuration. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PSE Messages
Error Message%L2-PSE-3-INTERNAL_ERR Error: [chars]: Err=[dec]
Explanation A driver internal error occurred which involves exiting the process. %s - indicates the reason for the failure. %d - is the error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PSE-3-INVALID_COUNT Error: [chars]: Err=[dec]
Explanation This is a error message in the PSE Driver to indicate either anomolies which are notservice impacting. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved. %s - indicates the reason for the failure. %d - is the error reason.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PSE-6-INFO_MSG Info: [chars]
Explanation This is a Informational message in the PSE Driver to indicate an operation. %s - indicates the informational message.
Recommended Action No action is required.
QM_E5 Messages
Error Message%L2-QM_E5-4-ANOMALY [chars]: [chars] : reg value [hex]
Explanation A SW exception occurred in QM_E5 Library
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-QM_E5-6-INFO_MSG [chars]: [chars] : reg value [hex]
Explanation This is a Informational message in the XBMA Driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-QM_E5-6-INFO_MSG2 [chars]: [chars] : reg1 [hex]: reg2 [hex]
Explanation This is a Informational message in the XBMA Driver to indicate an operation.
Recommended Action No action is required.
QM Messages
Error Message%L2-QM-4-ANOMALY Queue ISR [chars]: [chars] : reg value [hex]
Explanation A SW exception occurred in QM Library
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-QM-6-INFO_MSG Queue: [chars]
Explanation This is a Informational message in the XBMA Driver to indicate an operation.
Recommended Action No action is required.
RADAR Messages
Error Message%L2-RADAR-4-ANOMALY INGRESSQ: [chars]: error [hex]
Explanation A SW exception occurred in RADAR Library
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-RADAR-6-INFO_MSG INGRESSQ: [chars]
Explanation This is a Informational message in the XBMA Driver to indicate an operation.
Recommended Action No action is required.
SLOGIC Messages
Error Message%L2-SLOGIC-4-ANOMALY [chars]
Explanation A SW exception occurred in SLOGIC Library
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SPA_192 Messages
Error Message%L2-SPA_192-3-JACKET_ERROR [chars]
Explanation SPA 192 Jacket error
Recommended Action When errors occur in jacket, it is very likely the jacket process will restart itself.
Error Message%L2-SPA_192-3-JACKET_V2_ERROR [chars]
Explanation SPA 192 Jacket V2 error
Recommended Action When errors occur in jacket, it is very likely the jacket process will restart itself.
Error Message%L2-SPA_192-3-SPARULE_INT_ERROR [chars]
Explanation SPA 192 Jacket V2 SPA rule internal error
Recommended Action This would indicate an internal error in SPA rule module affecting our ability to insert/remove new SPA. This may require jacket process restart.
Error Message%L2-SPA_192-6-SPARULE_ERROR [chars]
Explanation SPA 192 Jacket V2 SPA rule error
Recommended Action This would indicate an error during insertion/removal of SPA. If error occures during OIR than it is likely that problem could be due to invalid combination or SPA type used as indicated by additional text.
Error Message%L2-SPA_192-6-UPGRADE_FPGA [chars]
Explanation Upgrade SPA FPGA message
Recommended Action none
Error Message%L2-SPA_192-6-UPGRADE_FPGA [chars]
Explanation Upgrade SPA FPGA message
Recommended Action none
SPA Messages
Error Message%L2-SPA-6-OPTICS_INSERTION Optics module inserted into SPA in bay [dec]
Explanation Optics module has been inserted. %d - indicates the bay number
Recommended Action None. This is an informational message only.
Error Message%L2-SPA-6-OPTICS_REMOVAL Optics module removed from SPA in bay [dec]
Explanation Optics module has been removed. %d - indicates the bay number
Recommended Action None. This is an informational message only.
STINGRAY Messages
Error Message%L2-STINGRAY-4-ANOMALY EGRESSQ: [chars]: error [hex]
Explanation A SW exception occurred in STINGRAY Library
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
TCAM_RM Messages
Error Message%L2-TCAM_RM-3-BLWM_CLIENT_CONF_FAILED tcam_rm: blwm client configuration failed, error: [hex] [chars]
Explanation Unable to configure BLWM client 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%L2-TCAM_RM-3-BLWM_CLIENT_REBIND_FAILED tcam_rm: blwm client rebind failed, error: [hex] [chars]
Explanation Unable to rebind with BLWM client functionality after a connection reconnect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-TCAM_RM-3-BLWM_MSG_SEND_FAILED tcam_rm: blwm msg send/flush: retried: [dec] time(s), failed to send, error: [hex] [chars]
Explanation Unable to send/flush a BLWM message to the TCAM_RM 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%L2-TCAM_RM-3-BLWM_RECVD_REPLY_FAIL tcam_rm: Received a failure reply code for a batched request type [dec], failed reason: [chars]
Explanation This is the message printed by the default handler installed by TCAM_RM to process the replies received for batched requests. The default handler's behavior is to just print this message. The application should install its own handler to handle the replies to batched requests.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-TCAM_RM-3-FATAL_ERR Fatal error: [chars]: Err=[dec]
Explanation A fatal error occurred in TCAM RM which involves exiting the 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%L2-TCAM_RM-3-MSG_SEND_FAILED tcam_rm: msg: [dec], retried: [dec] time(s), failed to send, errno: [chars]
Explanation Unable to send a message to the TCAM RM 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%L2-TCAM_RM-3-NONFATAL_ERR Nonfatal error: [chars]: Err=[dec]
Explanation This is a error message in the TCAM RM to indicate anomalies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temporary situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-TCAM_RM-3-TCAM_RM_RECVD_REPLY_NOMEM tcam_rm: TCAM could not satisfy allocation request, the node may not function as expected.
Explanation This is the message printed by the default handler installed by TCAM_RM to process the no memory reply received for batched requests. The default handler's behavior is to just print this message. The application should install its own handler to handle the replies to batched requests.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-TCAM_RM-4-BLWM_REPLAY_REQUEST tcam_rm: Replaying a batched request of type [dec] that might have been partially processed before.
Explanation Due to a server restart, a batched request might have been partially processed. The default handler installed by TCAM_RM simply replays the request. Applications that can not afford to replay a request should install their own handler.
Recommended Action No action is required.
Error Message%L2-TCAM_RM-6-INFO_MSG Info: [chars]
Explanation This is an informational message in the TCAM RM.
Recommended Action No action is required.
UIDB_RM Messages
Error Message%L2-UIDB_RM-3-INIT_ERR Process initialization failed: ([chars]%s)
Explanation The uidb-mgr-main process failed to initialize. A uidb is defined as a 'Micro Information Data-Base' used by the hardware ASIC's in the forwarding path. The uidb-mgr-main process is responsible for allocating/de-allocating the hardware uidb's as configured by sw. If the uidb manager fails to initialize, no interfaces can be created or deleted on the linecard. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process uidb_mgr_main location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart uidb_mgr_main location 0/x/cpu0'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
WAHOO Messages
Error Message%L2-WAHOO-3-ERR_ACCESS Memory access Error: [chars]: Err=[dec]
Explanation A memory access error occurred in programable switching engine (PSE) driver which involves exiting the process. %s - indicates the reason for the failure. %d - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-WAHOO-6-INFO_MSG
[chars] [chars] [chars]: [hex]Explanation This is an informational message in the programable switching Engine driver to indicate an operation. %s - indicates the PSE (RX/TX) information is about. %s - indicates the pipeline (0-3) information is about. %s - indicates the information message. %x - indicates the register value.
Recommended Action No action is required.
Error Message%L2-WAHOO-7-ERR_PIPE_STUCK Pipe stuck error: [chars]: Err=[dec]
Explanation An error occurred in programable switching engine (PSE) driver which indicates anomalies. Some of the messages may indicate a failure to allocate resources needed by applications. %s - indicates the reason for the failure. %d - is the decoded error reason.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-WAHOO-7-INFO_MSG_1 [chars] [chars]
Explanation This is an informational message in the programable switching Engine driver to indicate an operation. %s - indicates the PSE (RX/TX) information is about. %s - indicates the information message.
Recommended Action No action is required.
Error Message%L2-WAHOO-7-PAIR_REG
[chars] [chars] PAIR registers for pipe [dec]:pcr [hex] plu_pirl [hex] pirm1 [hex]
pirm2 [hex] pirh [hex] ip_src [hex]
ip_dst [hex] mpls_label [hex] mpls_info [hex]
ip_header [hex] l4_port [hex] start_adr [hex]
msq_info [hex] ltr [hex] tlu_force [hex]
pre_cam_prof [hex] lbl1_lo [hex] lbl1_hi [hex]
tlbl2_lo [hex] lbl2_hi [hex] leaf1_word1 [hex]
leaf1_word2 [hex] leaf1_word3 [hex] leaf1_word4 [hex]
leaf2_word1 [hex] leaf2_word2 [hex] leaf2_word3 [hex]
tleaf2_word4 [hex] tcam_cont [hex] ipv4/v6_dst_1 [hex]
tipv4/v6_dst_2 [hex] ipv4/v6_dst_3 [hex] ipv4/v6_dst_4 [hex]
tipv4/v6_src_1 [hex] ipv4/v6_src_2 [hex] ipv4/v6_src_3 [hex]
t ipv4/v6_src_4 [hex] mcast_info [hex] ipv6_info [hex] msq_data [hex]Explanation An error occurred in programable switching engine (PSE) driver which indicates anomalies. Some of the messages may indicate a failure to allocate resources needed by applications.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-WAHOO-7-PHB_DUMP
[hex]: [hex] [hex] [hex] [hex]Explanation This is a error message in the programable switching Engine to indicate either anomolies which are not service impacting. Some of the messages may indicate a failure to allocate resources needed by applications.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
XBMA Messages
Error Message%L2-XBMA-3-ANOMALY Queueing [chars]: error [hex]
Explanation A SW exception occurred in XBMA Driver. Reliability could be compromised.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-XBMA-3-FATAL_ERR Fatal error: [chars]: Err=[dec]
Explanation A fatal error occurred in XBMA Driver which involves exiting the 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%L2-XBMA-6-INFO_MSG Queueing info: [chars] error [hex]
Explanation This is a Informational message in the XBMA Driver to indicate an operation.
Recommended Action No action is required.
