-
Cisco IOS XR System Error Message Reference Guide, Release 3.5
-
Preface
-
Overview
-
Access Control List (ACL) Messages
-
Diagnostic Messages
-
Fabric Messages
-
Forwarding Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 Messages
-
Layer 2 Messages
-
Layer 3 Messages
-
Manageability (MGBL) Messages
-
Media Messages
-
Operating System (OS) Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service (QoS) Messages
-
Routing Messages
-
Security Messages
-
Services Messages
-
Simple Network Management Protocol (SNMP) Messages
-
System Database 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:
10GE_PLIM Messages
Error Message%L2-10GE_PLIM-2-RX_LOSS Interface [chars], Detected RX Loss of Signal
Explanation The PLIM received an Rx LOS or LF on the given interface which will result in a link flap.
Recommended Action No action is required.
Error Message%L2-10GE_PLIM-2-RX_RF Interface [chars], Detected Remote Fault
Explanation The PLIM received a remote fault on the given interface which will result in a link flap.
Recommended Action No action is required.
Error Message%L2-10GE_PLIM-2-RX_UNKNOWN Interface [chars], Detected PLA Fault
Explanation The PLIM PLA ASIC had an unkown fault on the given interface which will result in a link flap.
Recommended Action Copy the error message exactly as it appears 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-10GE_PLIM-2-XGXS_RX_SYNC An XGXS RX lane failed to syncronize for port [dec].
Explanation The XGXS Rx Lanes failed to syncronize after Rx Xenpak OIR or Link Flap.
Recommended Action Try to shut/no shut the port. If the MAC does not get enabled, then A physical OIR of the Xenpak device will be needed. Copy the error message exactly as it appears 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-10GE_PLIM-3-OIM_ERR An Optic Interface Module error occurred at port [dec], reason : [chars]
Explanation A fatal error occurred in 10GE PLIM driver OIM rule validation.
Recommended Action 1. Remove the Xenpak and check if it is Cisco qualified Xenpak. 2. If it is Cisco qualified Xenpak, check DWDM Xenpak placement rule.
Error Message%L2-10GE_PLIM-4-INVALID_MAC Failed to get MAC address for [chars], Interface assigned random MAC address.
Explanation PLIM driver was unable to get a MAC address for the interface.
Recommended Action Check if the process 'shelfmgr' is up and running on the RP. Try to reload the LC to see if that helps. Copy the error message exactly as it appears 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-10GE_PLIM-6-ERR_UPGRADE [chars]
Explanation This is a Informational message in the plim_8p_10ge driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-10GE_PLIM-6-OIM_OIR Optic Interface Module [chars] for port [dec]
Explanation The Optic Interface Module (OIM) for the specified port has either been inserted or removed.
Recommended Action No action is required.
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.
ASIC_ERRORS Messages
Error Message%L2-ASIC_ERRORS-7-ERR_ECM_CREATE ASIC Error library has failed to create an Event Connection Manager. Reason: [chars].
Explanation The ASIC Error library encountered an error during the creation of the Error Connection Manager.
Recommended Action An error would be reported to the client application which should handle this condition appropriately. *None*
Error Message%L2-ASIC_ERRORS-7-ERR_ECM_REG ASIC Error library has failed to register a connection notification handler with the Event Connection Manager. Reason: [chars].
Explanation ASIC Error library encountered an error while setting up a SYSDB notofication handler with the event connection manager.
Recommended Action An error would be reported to the client application which should handle this condition appropriately. *None*
Error Message%L2-ASIC_ERRORS-7-ERR_SYSDB ASIC Error library failed to [chars]. Reason: [chars].
Explanation ASIC Error library encountered an error during the specified SYSDB operation.
Recommended Action An error would be reported to the client application which should handle this condition appropriately. *None*
Error Message%L2-ASIC_ERRORS-7-ERR_SYSDB_BAG_ENCODE ASIC Error library: Encountered SYSDB Bag encode error during [chars] operation.
Explanation ASIC error library encountered a SYSDB encode error while performing the indicated operation.
Recommended Action An error would be reported to the client application which should handle this condition appropriately. *None*
Error Message%L2-ASIC_ERRORS-7-ERR_SYSDB_EDM_REG ASIC Error library has failed to register an EDM. Reason: [chars].
Explanation The ASIC Error library was unable to become an external data manager despite having a connection to the SYSDB.
Recommended Action An error would be reported to the client application which should handle this condition appropriately. *None*
ASIC_SCAN_SERVER Messages
Error Message%L2-ASIC_SCAN_SERVER-2-NODE_BRINGDOWN [chars]
Explanation This is a message in the Asic Scan Server to indicate that it has triggerred a critical alarm and will result in node bringdown. The reason for the failure and the status of the scan operation is reported.
Recommended Action Run the board diagnostics.
Error Message%L2-ASIC_SCAN_SERVER-7-ERR_EVM_CREATE ASIC Scan Server failed to create the event manager: Reason = [chars].
Explanation ASIC scan server has failed to create the event manager. This would result in the automatic restart of 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-ASIC_SCAN_SERVER-7-ERR_INIT ASIC Scan Server encountered error [[chars]]: Reason = [chars].
Explanation ASIC scan server has failed the initialization sequence due to the specified reason. This would result in the automatic restart of 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-ASIC_SCAN_SERVER-7-ERR_IO ASIC Scan Server failed to [chars]: Reason = [chars].
Explanation ASIC scan server has failed the specified io operation.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ATM_ILMI Messages
Error Message%L2-ATM_ILMI-2-IM_ERR [chars] : [chars]
Explanation Error in IM operation
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ATM_ILMI-2-INTERNAL_ERR [chars] : [chars]
Explanation Internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ATM_ILMI-2-SYSDB_ERR [chars]
Explanation Error in sysdb operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
ATM_INARP Messages
Error Message%L2-ATM_INARP-2-INTERNAL_ERR [chars] : [chars]
Explanation Internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ATM_INARP-2-NOMEM Operation failed due to memory shortage, function: [chars]
Explanation Memory on the box is critically low.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
ATM_NETIO Messages
Error Message%L2-ATM_NETIO-3-CARD_DLL Failed to open card specific dll [chars]
Explanation Card specific dll may not be present
Recommended Action Copy the error message exactly as it appears 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-ATM_NETIO-3-INSERT_DICT Insertion to ATM Netio Dictionary fails
Explanation The env variable setting may not be set up for load path variable
Recommended Action Copy the error message exactly as it appears 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-ATM_NETIO-3-INVALID_DLL DLL not found for the specified card : [chars]
Explanation Check the installation Dlls missing from package
Recommended Action Copy the error message exactly as it appears 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-ATM_NETIO-3-LOAD_PATH Failed to get load path env variable for dll [chars]
Explanation The env variable setting may not be set up for load path variable
Recommended Action Copy the error message exactly as it appears 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-ATM_NETIO-3-MEMORY Failed to malloc [unsigned int] bytes
Explanation The DLL has failed to acquire the required amount of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-ATM_NETIO-3-PARSE_FAILURE Failed to parse atm_netio.rules at line: [chars]
Explanation The file atm_netio.rules has been modified and parsing fails
Recommended Action Copy the error message exactly as it appears 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-ATM_NETIO-3-PARSER_NULL_PATH Path to load the atm_netio.rules is NULL
Explanation The path to atm_netio.rules file cannot be located.
Recommended Action Copy the error message exactly as it appears 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-ATM_NETIO-6-DEBUG_REG Debug registration failed: [chars]
Explanation Debug message registration failed
Recommended Action No action is required.
ATM_OAM Messages
Error Message%L2-ATM_OAM-2-IM_ERR [chars] : [chars]
Explanation Error in IM operation
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ATM_OAM-2-INTERNAL_ERR [chars] : [chars]
Explanation Internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ATM_OAM-2-SYSDB_ERR [chars]
Explanation Error in sysdb operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
ATM_RM Messages
Error Message%L2-ATM_RM-1-SYSDB_ERR [chars] : [chars]
Explanation Error in sysdb operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-ATM_RM-2-INTERNAL_ERR [chars] : [chars]
Explanation A critical function failed that expected to succeed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ATM_RM-2-NOMEM Failed to allocate [dec] bytes due to memory shortage
Explanation Memory on the router is critically low.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-ATM_RM-4-BANDWIDTH_ERR [chars] : Bandwidth available [unsigned int] : Failed to reserve [unsigned int]
Explanation Insufficient bandwidth available. possible cause: Too many vc's inheriting QoS from class parameters
Recommended Action check vc class configuration on interface If there are vcs you want specific QoS values for under the main interface, try configuring QoS on these vcs before applying class to the interface in order to stop unwanted inheritance. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ATM_SAAR Messages
Error Message%L2-ATM_SAAR-2-INIT Failed to initialise ATM SAAR: [chars] ([chars])
Explanation There was an error initialising the ATM SAAR component.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-ATM_SAAR-6-DEBUG_REG Debug registration failed: [chars]
Explanation Debug message registration failed
Recommended Action No action is required.
ATM_SOCKET Messages
Error Message%L2-ATM_SOCKET-2-INTERNAL_ERR [chars] : [chars]
Explanation A critical function failed that expected to succeed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ATM_SOCKET-2-NOMEM Allocation of [dec] bytes failed due to memory shortage
Explanation Memory on the router is critically low.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-ATM_SOCKET-3-RESMGR_ATTACH Failed to setup atm socket as a resource manager: [chars]
Explanation The atm_io process failed to advertise itself to the system as a resource manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ATM_SOP Messages
Error Message%L2-ATM_SOP-3-INTR ATM SOP Intr: [chars]: [dec]: [chars]: [dec] [chars]
Explanation The SOP FPGA has been interrupted due a hardware error
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ATM_SOP-7-DEBUG ATM SOP DEBUG: [chars]: [hex]: [hex]: [hex]
Explanation ATM SOP debug message
Recommended Action No action is required.
ATM_VCM Messages
Error Message%L2-ATM_VCM-2-IM_ERR [chars] : [chars]
Explanation Error in IM operation
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ATM_VCM-2-INTERNAL_ERR [chars] : [chars] : [chars]
Explanation Internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ATM_VCM-2-SYSDB_ERR [chars]
Explanation Error in sysdb operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
atmdrv Messages
Error Message%L2-atmdrv-2-ERR [chars], [dec] error, reason:[chars]
Explanation atmdrv generic error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-atmdrv-2-ERR [chars], [dec] error, reason:[chars]
Explanation atmdrv generic error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-atmdrv-2-ERR_ENCAP [chars] - [dec]: [chars] rc=[hex] connid=[dec] key=[hex]
Explanation atmdrv generic error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-atmdrv-2-ERR_ENCAP [chars] - [dec]: [chars] rc=[hex] connid=[dec] key=[hex]
Explanation atmdrv generic error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-atmdrv-2-ERR_STS [chars] - [dec]: [chars] (rc = [hex])
Explanation atmdrv generic error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-atmdrv-2-ERR_STS [chars] - [dec]: [chars] (rc = [hex])
Explanation atmdrv generic error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-atmdrv-2-ERR_VC [chars] - [dec]: [chars] (connid = [dec])
Explanation atmdrv generic error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-atmdrv-2-ERR_VC [chars] - [dec]: [chars] (connid = [dec])
Explanation atmdrv generic error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-atmdrv-3-cpk_err [chars]. Port [dec]: number of occurence = [unsigned int] intr_status = [hex]
Explanation atmdrv cpk24 interrupt handling related errors, or alerts
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-atmdrv-4-warning [chars], [dec] warning, reason:[chars]
Explanation atmdrv warning message
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and mail this message to your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-atmdrv-4-warning [chars], [dec] warning, reason:[chars]
Explanation atmdrv warning message
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and mail this message to your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-atmdrv-7-db_dump reason:[chars] port:[dec], vpi/vci:[dec]/[dec], connid:[dec], channels(r/s):[hex]/[hex], shape:[dec], encap:[dec]
Explanation atmdrv debug message
Recommended Action None
ATMGCMGR Messages
Error Message%L2-ATMGCMGR-2-DBG_INIT Failed to initialize [chars], because of [chars].
Explanation A failure occurred during the initialization of the debug events.
Recommended Action Copy the error message exactly as it appears 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-ATMGCMGR-2-INIT Failed to initialize [chars], because of [chars].
Explanation A failure occurred during the initialization of the process. This resulted in the restart of 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.
BFD Messages
Error Message%L2-BFD-4-RATE_LIMIT_WARNING_HIGH_WATERMARK BFD PPS allocation exceeds 90 percent of maximum.
Explanation BFD has allocated 90 percent of its packet per second allowance on this LC.
Recommended Action No action is required.
Error Message%L2-BFD-4-RATE_LIMIT_WARNING_LOW_WATERMARK BFD PPS allocation now less 85 percent of maximum.
Explanation BFD has released some of the previously allocated packet per second usage and is now at less than 85 percent of its allowance on this LC.
Recommended Action No action is required.
Error Message%L2-BFD-6-SESSION_NO_RESOURCES No resources for session to neighbor [chars] on interface [chars], interval=[unsigned int] ms[chars]
Explanation The BFD session can not be created or modified due to lack of resources.
Recommended Action Remove other BFD sessions to free resources for this session
Error Message%L2-BFD-6-SESSION_NO_RESOURCES_CLR Lack of resources condition has cleared for session to neighbor [chars] on interface [chars]
Explanation Resources are now available for this session.
Recommended Action No action is required.
Error Message%L2-BFD-6-SESSION_REMOVED BFD session to neighbor [chars] on interface [chars] has been removed
Explanation The BFD session has been removed. This is due to the application(s) removing the BFD session. This can happen as a result of BFD being unconfigured under the application(s) or as a result of the application(s) adjacency being removed.
Recommended Action No action is required.
Error Message%L2-BFD-6-SESSION_STATE_DOWN BFD session to neighbor [chars] on interface [chars] has gone down. Reason: [chars]
Explanation The BFD session has gone down. This may be as a result of the forwarding path being down.
Recommended Action Determine if the forwarding path to the neighbor has gone down.
Error Message%L2-BFD-6-SESSION_STATE_UP BFD session to neighbor [chars] on interface [chars] is up
Explanation The BFD session is now up.
Recommended Action No action is required.
Error Message%L2-BFD-6-SESSION_VERSION_CHANGE BFD session to neighbor [chars] on interface [chars] is administratively down due to version change from version [unsigned int] to version [unsigned int]
Explanation The BFD session has been brought administratively down to change protocol version.
Recommended Action No action is required.
BM Messages
Error Message%L2-BM-3-ERR_IIR_MEMBERSHIP Link [chars] in [chars] reported by IIR in bundle [chars].
Explanation When synchronising with IIR during restart the link was reported to be in a different bundle from the checkpoint records of the process. This should never happen and is not recoverable. The information from IIR was discarded and the process is now out of step with IIR, possibly leading to further problems.
Recommended Action Delete the checkpoint data for the Bundle Manager process that reported the error (run rm /tmp/chkpt_bundlemgr_distrib*) and restart the process.
Error Message%L2-BM-4-ERR_ACTIVATE Failure during activation of [chars]. Error: [chars]
Explanation A failure occurred during the activation of the process. Activation occurs when the card transitions to ACTIVE state. This error resulted in the restart of 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-BM-4-ERR_ADJ_DLL_INIT Failure during intialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the platform independent adjacency completion DLL. This will result in the hosting process being restarted.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_ADMINSTATE Unable to [chars] administrative state for [chars] on [chars]. Error: [chars]
Explanation The operation attempted failed. For a set this may mean that the link is UP when the bundle is SHUTDOWN. This can be resolved by 'no shut' and then 'shut' of the bundle. For a clear this may mean that the link remains DOWN when it has been removed from the bundle. This can be resolved by re-adding and then removing the link from the bundle again.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_EVM_EVENT_BLOCK Unrecoverable error in event loop. Error: [chars]
Explanation An error (other than EINTR) occured in the event loop. The process has exited and restarted.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_GROUP_CREATE Unable to create GSP group. Error: [chars]
Explanation Creation of the group used to communicate between Bundle Manager processes failed. This resulted in the restart of the process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show gsp groups command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show gsp groups output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-BM-4-ERR_IDENTICAL Attempting to order [chars] and [chars] that have identical port information
Explanation The comparison between an entry in the bundle member list and a new entry to be inserted showed that both had identical port data. Because of this the new link could not be inserted into the list and the operation leading to this failed.
Recommended Action Remove and re-add the configuration for the links named in the message. Copy the error message exactly as it appears 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-BM-4-ERR_IIR_BDL_DATA Invalid [chars] specified by IIR forCH[hex]: [unsigned int]
Explanation The data specified in the IIR notification is not one of the recognised values for that type. The information is invalid and the result is that adjacencies for this bundle cannot be programmed in hardware.
Recommended Action Delete and recreate the bundle. If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_IIR_BDL_HANDLE Invalid (NULL) interface handle supplied for a bundle by IIR
Explanation The interface handle specified in the IIR notification was NULL. The information is invalid and will be ignored.
Recommended Action If this event can be associated with changes to a particular bundle then delete and recreate the bundle. If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_IIR_MBR_DATA Invalid [chars] specified by IIR forCH[hex] memberCH[hex]: [unsigned int]
Explanation The data specified in the IIR notification is not one of the recognised values for the type. The information is invalid and will be ignored.
Recommended Action Delete and recreate the bundle. If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_IIR_MBR_HANDLE Invalid (NULL) interface handle supplied by IIR for a member ofCH[hex]
Explanation The interface handle specified in the IIR notification was NULL. The information is invalid and will be ignored.
Recommended Action Delete and recreate the bundle. If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_IIR_OP Unable to report IIR op failure for b_ifh [hex], m_ifh [hex] (op [chars], state [chars]). Error: [chars]
Explanation An error occurred processing the IIR event and the bundle EA process was unable to report this error back to IIR. This may lead to some inconsistency with the bundle membership in the data plane not matching what is intended according to the control plane.
Recommended Action The failure to report the error back to IIR suggests a problem in the connection to IIR. This may have been a transient problem, but restarting ifmgr and/or the bundlemgr_ea process on the location of the error might be necessary. The error that should have been reported also needs to be dealt with. This error may have come from some lower layer platform component, possibly a resource allocation error. If the error code provides some information as to the failure then take action appropriate to the error. If the error code is not specific then take action according to whether the event was a link activation or a link deactivation/deletion. For activation problems unconfigure and reconfigure the member link - if this fails try restarting the bundlemgr_ea process after unconfiguring the member link. For deactivation/deletion failures try restarting the improxy process to trigger a complete resync by the bundlemgr EA.
Error Message%L2-BM-4-ERR_IIR_SUB_HANDLE Invalid (NULL) interface handle supplied by IIR for a sub-interface ofCH[hex]
Explanation The interface handle specified in the IIR notification was NULL. The information is invalid and will be ignored.
Recommended Action Delete and recreate the bundle. If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_INIT Failure during intialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the process. This resulted in the restart of 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-BM-4-ERR_INIT_ENS Failure to initialise ENS - retry scheduled. Error: [chars]
Explanation A failure occurred during the initialization of ENS library in the process. This probably indicates an underlying more severe problem. A retry will be attempted.
Recommended Action Copy the error message exactly as it appears 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-BM-4-ERR_LINK_ATTACHED Link [chars] is attached to [chars] that is thought to have no attached members.
Explanation This process believes that there are no aggregatable links, but this link is marked as attached. This error is most likely caused by failing to attach or detach a link correctly.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-BM-4-ERR_MEM_ALLOC Unable to allocate [unsigned int] bytes of memory.
Explanation Memory allocation failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-BM-4-ERR_MIB_CLEANUP Failure during cleanup of [chars] in the dot3ad MIB DLL. Error: [chars]
Explanation A failure occurred during the cleanup of the DLL. This may result in the DLL not being completely cleaned up, possibly causing errors in a subsequent re-initialization of the DLL.
Recommended Action Restart the snmp process reporting the error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-BM-4-ERR_MIB_INIT Failure during intialization of [chars] in the dot3ad MIB DLL. Error: [chars]
Explanation A failure occurred during the initialization of the DLL. This resulted in the DLL not being loaded into the SNMP agent, and thus the MIB services will not be available.
Recommended Action Restart the snmp process reporting the error. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-BM-4-ERR_MTU_IMPOSE Imposition of configured MTU failed for [chars], will continue to use previous value: [unsigned int]
Explanation The MTU imposition was rejected by IM or another client. The bundle will continue to operate with the previously configured MTU.
Recommended Action Check that the configured MTU is within approrpriate ranges for the interface type and network layer protocols on the interface. Remove the configuration and reapply.
Error Message%L2-BM-4-ERR_NETIO_INIT Failure [chars] in the bundle NetIO DLL during [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the bundle NetIO DLL. If this occured during an upgrade operation then it will cause the NetIO process to reload. Otherwise this will cause the capsulation to be unloaded, and an error returned to the user. One possible reason for the error is a low memory condition, particularly if the failure was in allocating trace buffers.
Recommended Action If the error message indicates the failure is low memory condition, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Otherwise, Copy the error message exactly as it appears 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-BM-4-ERR_PAKMAN Unable to handle pakman corruption error: [chars]. Process exiting
Explanation A packet manager corruption has been reported and the Bundle Manager process has failed to cleanup to recover from the problem. The process will exit and be automatically restarted to recover from this situation.
Recommended Action It is expected that restarting the process will fix this problem. This is done automatically so no action should be required. If the problem recurs, then there is a problem in packet manager. A drastic solution would be to reload the linecard.
Error Message%L2-BM-4-ERR_RECREATE_BUNDLE Unable to recreate bundleCH[hex]. Error: [chars]
Explanation When recovering the checkpointed data for a bundle, an error occurred and the data is lost.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface (bundle name) command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show interface output, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log. Issue the show bundle (bundle name) command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show bundle (bundle name) output, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log. Issue the show adjacency detail hardware location command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show adjacency (bundle name) detail hardware location of output, call your Cisco technical support representative and provide the representative with the gathered information. If the bundle appears correctly in the output of all three commands then no further action is required, otherwise unconfigure and reconfigure the bundle.
Error Message%L2-BM-4-ERR_RECREATE_LINK Unable to recreate link [chars] in [chars]. Error: [chars]
Explanation When recovering the checkpointed data for a link, an error occurred and the data is lost.
Recommended Action Identify the bundle in which the link was a member. Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show interface output, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log. Issue the show bundle command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show bundle output, call your Cisco technical support representative and provide the representative with the gathered information. If the member appears correctly in the output of both commands then no further action is required, otherwise unconfigure and reconfigure the member.
Error Message%L2-BM-4-ERR_REPAIR_BUNDLE Unable to repair bundleCH[hex] checkpoint structures. Error: [chars]
Explanation When repairing the checkpoint structures for the bundle database an error occurred for named bundle and the bundle was not checkpointed. The next time an attempt is made to checkpoint the bundle it will fail and the checkpoint table will be reconstructed again, perhaps more successfully.
Recommended Action Copy the error message exactly as it appears 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-BM-4-ERR_REPAIR_DATABASE Unable to repair [chars] database. Failure during checkpoint [chars]. Error: [chars]
Explanation When repairing the checkpoint structures for the named database an error occurred in the database checkpoint registration. As a result the process was intentionally restarted.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_REPAIR_LINK Unable to repair checkpoint structures for link [chars] in [chars]. Error: [chars]
Explanation When repairing the checkpoint structures for the link database an error occurred for named link and the link was not checkpointed. The next time an attempt is made to checkpoint the link it will fail and the checkpoint table will be reconstructed again, perhaps more successfully.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_REPLICATE Replication failed for [chars], when adding member [chars]. Error: [chars]
Explanation When attempting to replicate the bundle to the member interface location, the replication operation failed. This probably happened because some hardware resource on the LC where the member is located was exhausted. The record of the member will be removed from the bundle process on the RP but will still be referenced by the bundle process on the LC.
Recommended Action Determine whether the hardware resources for the LC have been oversubscribed, e.g. more VLANs on the LC and on the bundle that the LC can support. If this is the case, reduce the number of allocated VLANs. Then remove the member configuration and reapply.
Error Message%L2-BM-4-ERR_RESTORE_LINK Unable to restore link [chars] in [chars]. [chars]. Error: [chars]
Explanation When restoring the link an error occurred and to maintain consistency the data was removed. It is likely, given the error, that the link had been OIR removed.
Recommended Action Verify that the link has not been OIR removed. If it has not, remove the bundle membership configuration and reapply it. Copy the error message exactly as it appears 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-BM-4-ERR_RESYNC_EXCEED_IIR Exceeded the IIR resync limit for [chars]. Process exiting.
Explanation The maximum number of attempts to resync with IIR have been exceeded for this bundle. The safest course of action is to restart the process and this has been done.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_RESYNC_SCHED_IIR Unable to schedule an IIR resync for [chars]. Process exiting.
Explanation An attempt to schedule a resync with IIR has failed for this bundle. The safest course of action is to restart the process and this has been done.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_RETRY_EXCEED Exceeded maximum number of retries for [chars]
Explanation After attempting to resend or query information a number of times, the retry limit has been exceeded and no more attempts will be made. The effect of the message will therefore be lost. The impact will depend on the message which was lost. If the message refers to a global error then the process will exit and be restarted.
Recommended Action If the message referred to a global error then check that the process has restarted successfully. If the message referred to a bundle or bundle member then check that the object is still configured and still exists. Make a minor change to the settings of the object experiencing the problem. This will trigger another attempt to send an update. If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_RETRY_EXCEED_GSP Retry limit for GSP initialization exceeded: [chars]
Explanation After attempting to create the GSP group used for communications with the Bundle Manager process on another node a number of times, the retry limit has been exceeded. The cause of the failure is very likely to be some external communication failure - so check for evidence of this. The process will exit and be restarted automatically so no futher action is needed for Bundle Manager to retry.
Recommended Action Check that other processes are not reporting similar communication errors, as this is likely to be a general communication problem. The Bundle Manager process has exited and will be restarted, so no action is needed, though unless the communication problem is resolved the process will still not be able to startup.
Error Message%L2-BM-4-ERR_RETRY_EXCEED_IMP Exceeded the retry limit for IMP events.
Explanation The maximum number of attempts to retry an IMP message has been exceeded. An error has occurred in the clean up of a bundle, so there may be residual data for the bundle in the linecard components which could cause subsequent problems. Restart the process that reported the error to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-BM-4-ERR_RETRY_EXCEED_SYSTEM_MAC Retry limit for system MAC address query exceeded: [chars]
Explanation After attempting to query the system MAC address from SDRd a number of times, the retry limit has been exceeded. The cause of the failure is likely to be an issue with SDRd or Shelfmgr - so check for evidence of this. The process will exit and be restarted automatically so no futher action is needed for Bundle Manager to retry.
Recommended Action The Bundle Manager process has exited and will be restarted, so no action is needed. Check that the board (EEPROM etc.) is correctly programmed since this is the source of the MAC address information and therefore one possible cause of the problem.
Error Message%L2-BM-4-ERR_RETRY_SCHED Unable to send update for [chars] and unable to schedule retry: [chars]
Explanation A timeout occurred sending an update to a Bundle Manager process on another node. Due to a problem with the retry mechanism, a resend of the message could not be scheduled. The effect of the message will therefore be lost. The impact will depend on the message which was lost.
Recommended Action Make a minor change to the settings of the object experiencing the problem. This will trigger another attempt to send an update. If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_SYSMGR Failure communicating readiness to System Manager. Error: [chars]
Explanation The process was initialized successfully but was unable to inform System Manager of the success.
Recommended Action Check on the status of the sysmgr process on the node from which the error was reported. If the message recurs, copy the error message exactly as it appears 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-BM-4-ERR_UNREPLICATE Unreplication failed for [chars], when removing member [chars]. Error: [chars]
Explanation When attempting to unreplicate the bundle from the member interface location, the unreplication operation failed. Some hardware resources may continue to be used for the bundle on the location of the member that was removed. It is also possible that there could be a problem replicating the bundle to that location again if a new member is added.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-BM-5-CHURN Interface [chars] in [chars] [chars] on actor system
Explanation Churn has either been detected (due to the failure of a link to synchronize soon enough) or the churn state has now cleared.
Recommended Action If churn has been declared, check that the configuration for the link allows it to aggregate, and fix as appropriate. Things to check for are links which are incompatible with each other, or misconfigurations between the two ends of the link which is reporting churn.
Error Message%L2-BM-6-DISTRIBUTING [chars] [chars] in Distributing state as part of [chars]
Explanation This is an informational message reporting that a link has entered or left Distributing state as part of a bundle interface. The link configuration may have just been changed or there may be an operational reason for the event such as a state change or LACP protocol update.
Recommended Action Nothing, this is not an error.
Error Message%L2-BM-6-MIN_MAX [chars] is down because the minimum active link threshold ([unsigned int]) is greater than the maximum permitted links ([unsigned int])
Explanation This is an informational message reporting that a bundle is operationally down because the configuration for minimum active links and maximum active links conflicts. The number of active links required for the bundle to come up is greater than the number of links permitted to be active in the bundle, and there are at least enough links held in standby state for the bundle to come up if the maximum active link criteria were removed.
Recommended Action If this situation is not intended then either reduce the minimum active link threshold or increase the maximum links permitted in the bundle.
BM_PD Messages
Error Message%L2-BM_PD-3-DLL_CERRNO Failure registering cerrno DLL with subsys num [unsigned int] and DLL name [chars]. Error: [chars]
Explanation A failure occurred during the registration of the DLL for decoding error codes from the component. This may render certain codes unprintable, but otherwise has no negative impact.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-BM_PD-3-DLL_INIT Failure during intialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the platform dependent adjacency programming DLL. This will result in the hosting process being restarted.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-BM_PD-3-DLL_TRACE Failure initializing tracing ([chars] buffer). Error: [chars]
Explanation A failure occurred during the initialization of tracing for the adjacency management DLL. This will cause the DLL to be unloaded, and adjacency programming will not happen.
Recommended Action If the message recurs, copy the error message exactly as 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-AIB_INIT_FAILED Failed during AIB initialization, err: [chars]
Explanation The C-shim Partner initialization failed while trying to connect to AIB.
Recommended Action Copy the error message exactly as it appears 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_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-ECM_INIT_FAILED Failed during create ECM initialization, Err: [chars]
Explanation 'There is a software error when creating ECM connection.'
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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. Reason: [chars]
Explanation 'There is a software error when handling messages from IM.'
Recommended Action Ignore
C12000_FR Messages
Error Message%L2-C12000_FR-3-SUBIF_COUNT FR Subinterface counter is not initialised
Explanation Initialisation of subinterface counter in the shared memory 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.
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'
CDP Messages
Error Message%L2-CDP-3-ERR_CONN Connection error on [chars]([pointer]): [chars]
Explanation An error occurred on one of the event connections managed by CDP which CDP could not recover automatically.
Recommended Action Try restarting CDP. If the message recurs, copy the error message exactly as it appears 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-CDP-3-ERR_IM_ATTR_REGISTRATION Unable to register for duplex change notifications: [chars]
Explanation CDP registration for duplex change notifications failed. This means that duplex information will be missing from outgoing CDP packets
Recommended Action Try restarting CDP ('proc restart cdp location '). If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CDP-3-ERR_IM_CAPS_ADD Failed to add the CDP capsulation to interface [chars]: [chars]
Explanation CDP could not install the CDP capsulation on the specified interface and hence it is not possible for CDP to send or receive any packets on this interface.
Recommended Action Copy the error message exactly as it appears 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-CDP-3-ERR_IM_CAPS_REMOVE Failed to remove the CDP capsulation on interface [chars]: [chars]
Explanation CDP could not uninstall the CDP capsulation on the specified interface and hence CDP may be in an inconsistent state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CDP-3-ERR_IM_MTU_REGISTER Failed to register for MTU size changes on interface [chars]: [chars]
Explanation CDP failed to register with the interface manager for MTU size changes on this particular interface. This may cause problems sending CDP packets.
Recommended Action Perform 'cdp disable', 'cdp enable' on the interface to try 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-CDP-3-ERR_IM_STATE_REGISTER Failed to register for state changes on interface [chars]: [chars]
Explanation CDP failed to register with the interface manager for state changes on this particular interface. This means CDP will be unable to track the state of the interface. CDP functionality may be impaired.
Recommended Action Perform 'cdp disable', 'cdp enable' on the interface to try 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-CDP-3-ERR_INTF_INIT Initialisation of CDP on interface [chars] failed: [chars].
Explanation CDP is unable to run on the specified interface. It is likely that this is due to a lack of available resources.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Configuring 'cdp disable', 'cdp enable' on the interface, or restarting CDP on the affected node may recover the situation.
Error Message%L2-CDP-3-ERR_INTF_STATS No CDP protocol statistics can be collected on [chars]: [chars]
Explanation It was not possible to register for stats collection on the specified interface. The entry in the 'show interface accounting' command is likely to be inaccurate for CDP packets.
Recommended Action Try restarting CDP and the Statistics server process on this node. proc restart cdp location proc restart statsd_server location If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CDP-3-ERR_IPV4_ADDRESS_SCAN [chars]: Failed to scan the IPv4 addresses for this interface: [chars]. This means that IPv4 information will be missing from outgoing CDP packets
Explanation A scan of the IPv4 addresses on this interface has failed. This means that IPv4 address information for this interface will not be included in outgoing CDP packets. The neighboring device will not see the IPv4 address information for this interface.
Recommended Action Restarting CDP as the address consumer, or the ipv4_ma as the address provider on this node may rectify the problem. proc restart cdp location or proc restart ipv4_ma location
Error Message%L2-CDP-3-ERR_IPV4_REGISTRATION Unable to register for IPv4 address notifications: [chars]. This means that IPv4 information will be missing from outgoing CDP packets.
Explanation CDP registration with the IP address library has failed. This means that IPv4 address information for interfaces local to this node will not be included in outgoing CDP packets. The neighboring devices will not see the IPv4 address information for this router's interfaces.
Recommended Action Restarting CDP as the address consumer, or the ipv4_ma as the address provider on this node may rectify the problem. proc restart cdp location or proc restart ipv4_ma location
Error Message%L2-CDP-3-ERR_IPV6_ADDRESS_SCAN [chars]: Failed to scan the IPv6 addresses for this interface: [chars]. This means that IPv6 information will be missing from outgoing CDP packets
Explanation A scan of the IPv6 addresses on this interface has failed. This means that IPv6 address information for this interface will not be included in outgoing CDP packets. The neighboring device will not see the IPv6 address information for this interface.
Recommended Action Restarting CDP as the address consumer, or the ipv6_ma as the address provider on this node may rectify the problem. proc restart cdp location or proc restart ipv6_ma location
Error Message%L2-CDP-3-ERR_IPV6_REGISTRATION Unable to register for IPv6 address notifications: [chars]. This means that IPv6 information will be missing from outgoing CDP packets.
Explanation CDP registration with the IP address library has failed. This means that IPv6 address information for interfaces local to this node will not be included in outgoing CDP packets. The neighboring devices will not see the IPv6 address information for this router's interfaces.
Recommended Action Restarting CDP as the address consumer, or the ipv6_ma as the address provider on this node may rectify the problem. proc restart cdp location or proc restart ipv6_ma location
Error Message%L2-CDP-3-ERR_STATS No per-interface CDP protocol statistics can be collected: [chars]
Explanation It was not possible for CDP to register for per-interface CDP protocol stats collection. The entries in the 'show interface accounting' command are likely to be inaccurate for CDP packets.
Recommended Action Try restarting CDP and the Statistics server process on this node. proc restart cdp location proc restart statsd_server location If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CDP-3-STALE_TLV On [chars] the [chars] TLV is not up to date: [chars]
Explanation CDP received a notification to update a TLV that it sends but failed to do so due to the error given. The information stored by CDP is now out of date.
Recommended Action Perform 'cdp disable', 'cdp enable' on the 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-CDP-4-DUPLEX_MISMATCH Duplex mismatch discovered on [chars] ([chars]), with [chars] [chars] ([chars]).
Explanation CDP discovered mismatching duplex configuration on neighboring interfaces.
Recommended Action Configure the interfaces with the same duplex (full or half).
Error Message%L2-CDP-4-ERR_MULTICAST_ADDR_SET Error setting up the CDP multicast address on [chars] (media [chars]): [chars]
Explanation The driver returned an error while setting up the CDP multicast address. It is possible that CDP packets will be dropped and not reach the CDP process.
Recommended Action If CDP packet loss is seen then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CDP-4-ERR_TABLE_RESIZE Not enough memory to clear and resize the CDP table
Explanation CDP ran out of memory when trying to resize the CDP hash table.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. CDP will try and continue to use the previous CDP table.
Error Message%L2-CDP-4-NEIGHBOR_LIMIT The CDP cache on this node is full. It contains [dec] neighbor entries
Explanation The limit for neighbors in the CDP cache has been reached. No more neighbors will be added to the neighbor cache until some existing entries have been removed. The number of entries is limited to defend against DoS attacks.
Recommended Action Check the existing CDP neighbors for bogus entries, CDP may be the victim of an attempted DoS attack. The 'clear cdp table' command can be used if CDP neighbor entries need removing.
Error Message%L2-CDP-4-NO_KNOWN_MEDIA CDP did not find any recognized media to run over
Explanation CDP failed to initialize the media module because it could not find any media that it recognizes. This may be a normal situation if CDP does not support the interface types on this node. In other circumstances CDP should recover automatically by restarting.
Recommended Action If there are no interfaces on this node with a media type that CDP is expected to run on then this could be a normal condition. If it is expected that CDP should run on the type of interfaces on this node then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CDP-4-NO_KNOWN_MEDIA_DRIVERS CDP did not find any recognized media drivers
Explanation CDP failed to initialize the media module because it could not find any media drivers that it recognizes. This may be a normal situation if CDP does not support the interface types on this node. In other circumstances CDP should recover automatically by restarting.
Recommended Action There are no media drivers for the interfaces on this node. If CDP does not support the interface types on this node then this could be a normal situation Otherwise Copy the error message exactly as it appears 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-CDP-4-WARN_INIT Initialization warning, module: [chars], operation: [chars]: [chars]
Explanation A failure occurred during the initialization of CDP. CDP will restart and this should resolve the problem.
Recommended Action CDP will try to recover automatically. If the message recurs, copy the error message exactly as it appears 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-CDP-4-WARN_TERM Termination warning, module: [chars], operation: [chars]: [chars]
Explanation A failure occurred during CDP's termination. In this situation CDP should recover automatically.
Recommended Action CDP should recover automatically. If the message recurs, copy the error message exactly as it appears 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-CDP-6-DELETED_NEIGHBOR CDP Neighbour [chars] on interface [chars] has been deleted, remote interface [chars]
Explanation An entry has been removed from the CDP neighbors table. Notification of deleted CDP neighbors requested through 'cdp log adjacency changes'.
Recommended Action No action is required.
Error Message%L2-CDP-6-NEW_NEIGHBOR New CDP neighbor [chars] detected on interface [chars], remote interface [chars]
Explanation A new entry has been added to the CDP neighbors table. Notification of new CDP neighbors requested through 'cdp log adjacency changes'.
Recommended Action No action is required.
CDPCP Messages
Error Message%L2-CDPCP-3-DEBUG_ASSOC Conditional debug association failed; [chars]
Explanation An error has occurred upon attempting to associate conditional debugging with PPP debug commands. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-3-DEBUG_COND_REGISTER Conditional debug registration failed; [chars]
Explanation An error has occurred upon attempting to register for conditional debugs. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-3-DEBUG_REGISTER Debug registration failed; [chars]
Explanation An error has occurred upon attempting to connect to the debug server. This may cause debug messages to not appear.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-3-ERR_CONN Connection [chars] failed for [chars]; [chars]
Explanation An failure in the reconnection software in the 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-CDPCP-3-ERR_EVENT Failed to [chars] [chars] event; [chars]
Explanation An event handler has returned an 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-CDPCP-3-ERR_EVENT_MGR_CREATE CDPCP Failed to initialize event manager; [chars]
Explanation Initialization of the event manager 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-CDPCP-3-ERR_IM_STATE Failed to get basecaps state for [chars]; [chars]
Explanation CDPCP was unable to determine the state of the basecaps and has assumed it to be down. CDPCP will remain closed until the interface is brought down and up again.
Recommended Action Shut the interface and then bring it up again.
Error Message%L2-CDPCP-3-ERR_MBOX_ADD [chars] [chars] failed to add [chars]; [chars]
Explanation An attribute has failed to be added to the message which was being constructed which has caused the message to be discarded.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-CDPCP-3-ERR_MBOX_CREATE [chars] failed to create [chars]; [chars]
Explanation An attempt to allocate a message failed. This may be due to lack of resources.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-CDPCP-3-ERR_MBOX_INIT Failed to init [chars] message for [chars]; [chars]
Explanation The initialization of a message failed, this results in a failure to communicate with the Link Control Protocol.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-3-ERR_MBOX_SEND [chars] failed to send [chars]; [chars]
Explanation A message failed in a send attempt to a particular mailbox.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-CDPCP-3-ERR_MQ_OPEN Failed to open message queue [chars]; [chars]
Explanation CDPCP has failed to open a mailbox channel.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-3-ERR_NETIO_RXQ Failed to support [chars] [chars]; [chars]
Explanation CDPCP has attempted to update the data component with the current status of the control protocol. The attempt has failed which will has the effect of leaving the data component with the previous set of information. This may result in an inability to negotiate CDPCP.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-CDPCP-3-ERR_SYSDB SysDB [chars] failed; [chars]
Explanation CDPCP cannot perform some SysDB operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CDPCP-3-ERR_SYSDB_NOTIFICATION Failed to [chars]register for SysDB notification of [chars]; [chars]
Explanation CDPCP cannot (un)register for SysDB notification.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-3-ERR_TIMER [chars] [chars] timer [chars]
Explanation The manipulation of a timer had an abnormal side effect.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-3-LTRACE_INIT CDPCP Failed to initialize the ltrace buffer; [chars]
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-CDPCP-4-ERR_EVENT_WAIT Error waiting for event; [chars]
Explanation The event loop has received a message of a type it does not recognize. All events should be received by handlers.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-4-ERR_INTERFACE_NULL [chars]: Interface NULL
Explanation A function was called with a NULL interface pointer.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-4-ERR_MEMORY Insufficient memory for [chars]
Explanation CDPCP failed to allocate memory for a 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-CDPCP-4-ERR_MQ_RECEIVE Error receiving from message queue; [chars]
Explanation CDPCP has failed to receive a message from its mailbox.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-4-ERR_NO_INTERFACE Interface [chars] not found
Explanation A SysDB name lookup 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-CDPCP-4-ERR_NO_INTERFACE_STRUCT Structure for interface [chars] not created; [chars]
Explanation CDPCP failed to create an interface structure.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-6-ERR_IM_CONNECT Failed to [chars]bind [chars] IM; [chars]
Explanation CDPCP has failed to either bind to or unbind from the interface manager server.
Recommended Action No action is required.
Error Message%L2-CDPCP-6-ERR_IM_ENCAPS Failed to [chars] [chars] encapsulation; [chars]
Explanation CDPCP has failed an encapsulation operation with the interface manager.
Recommended Action Copy the error message exactly as it appears 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-CDPCP-6-ERR_IM_EVENT Failed to [chars] event; [chars]
Explanation CDPCP has failed to either initialize or specify an event with the interface manager server.
Recommended Action No action is required.
Error Message%L2-CDPCP-6-ERR_IM_PROTO Failed to [chars] [chars] protocol; [chars]
Explanation CDPCP has failed a protocol operation with the interface manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
CEMA Messages
Error Message%L2-CEMA-3-FATAL_ERR CEMA Fatal Error: [chars]
Explanation An internal fatal error was detected in CEMA module operation
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-CEMA-3-MISMATCH_ERR CEMA Mismatch Error: [chars]
Explanation A process on the line card that manages a SPA was restarted. As a part of restart, a mismatch was detected between user specified configuration and the actual configuration of SPA hardware.
Recommended Action The mismatch can be service affecting in certain cases. Please check if the entity specified in the error log and all it's children are functioning correctly. Contact Cisco TAC for further assistance.
Error Message%L2-CEMA-4-GEN_ERR CEMA Internal Error: [chars]
Explanation An internal error was detected in CEMA module operation
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
CHDLC_EA Messages
Error Message%L2-CHDLC_EA-4-ERR_EVM_EVENT_BLOCK Error receiving an event: [chars]. The cHDLC EA process will restart
Explanation An error occured in the event loop. The process will restart which should recover the situation.
Recommended Action *RECUR*
Error Message%L2-CHDLC_EA-4-ERR_INIT Failure during initialization of the [chars]. Error [chars]. The cHDLC EA process will restart
Explanation A failure occured during the initialization of the process. The process will restart which should recover the situation.
Recommended Action *RECUR*
Error Message%L2-CHDLC_EA-6-ERR_IMP_MULTIPLE_NTFCNS : Multiple [chars] notifications received in a single batch from improxy
Explanation A batch from IMProxy contained multiple notifications for a single interface. This should not occur but the situation has been recovered successfully by the cHDLC EA. No problems should be seen as a result.
Recommended Action *NONE*
CHDLC_MA Messages
Error Message%L2-CHDLC_MA-3-ERR_IIR_BDL_OP The cHDLC MA failed to process a bundle IIR [chars] message onCH[hex], error: [chars]
Explanation The chdlc_ma process failed to process a bundle IIR notification message. Further it is not able to propagate the message back to the virtual interface owner, and hence it is possible that the basecaps is out of step with the bundle configuration.
Recommended Action *SUPPORT*
Error Message%L2-CHDLC_MA-3-ERR_INTF_UP_DOWN An error has occured resulting in the interface state being UP, and the line state being DOWN on interfaceCH[hex]. Because keepalives are disabled the line will never come up. The situation may be resolved by shutting and no shutting the interface, or enabling keepalives.
Explanation If keepalives are disabled and certain errors occur then the interface and line state can end up being out of step. Without keepalives enabled, SLARP has no way to recover by discovering the correct line state, so user intervention is required for a chance of recovery.
Recommended Action shut and then no shut the problematic interface, or enable keepalives on the interface.
Error Message%L2-CHDLC_MA-3-ERR_SYSMGR_SOCK_FEAT_START Startup of the cHDLC Socket feature has unexpectedly failed: [chars]
Explanation The cHDLC socket feature unexpectedly failed to be started by sysmgr. This may mean that processes which use cHDLC sockets to send and receive packets will be unable to do so, and may not be working correctly. Symptoms would include loss of SLARP keepalive packets causing the line state to go down, loss of CDP packets and loss of LACP packets on cHDLC encapsulated interfaces.
Recommended Action The problem can be fixed by manually starting the cHDLC Socket server process on the affected node using the command 'process start chdlc_socket location '. The command 'show process chdlc_socket location ' will indicate the state of the process. Once the socket server process is running, no further action is required.
Error Message%L2-CHDLC_MA-4-ERR_EVM_EVENT_BLOCK Error receiving an event: [chars]. The cHDLC MA process will restart
Explanation An error occured in the event loop.The process will restart which should recover the situation.
Recommended Action *RECUR*
Error Message%L2-CHDLC_MA-4-ERR_INIT Failure during initialization of the [chars]. Error [chars]. The process will restart
Explanation A failure occured during the initialization of the process. The cHDLC MA process will restart which should recover the situation.
Recommended Action *RECUR*
Error Message%L2-CHDLC_MA-6-ERR_IM_MULTIPLE_NTFCNS : Multiple [chars] notifications received in a single batch from Interface Manager
Explanation A batch from Interface Manager contained multiple notifications for a single interface. This should not occur but the situation has been recovered successfully by the cHDLC MA. No problems should be seen as a result.
Recommended Action *NONE*
CHDLC_SOCK Messages
Error Message%L2-CHDLC_SOCK-4-ERR_EVM_EVENT_BLOCK Error receiving an event: [chars]. The cHDLC socket server process will restart
Explanation An error occured in the event loop. The process will restart which should recover the situation.
Recommended Action *RECUR*
Error Message%L2-CHDLC_SOCK-4-ERR_INIT Failure during intialisation of the chdlc_socket process - specifically [chars]. Error: [chars]. The process will restart
Explanation A failure occurred during the initialisation of the cHDLC socket process. The process will restart which should recover the situation.
Recommended Action *RECUR*
Error Message%L2-CHDLC_SOCK-4-ERR_PAKMAN_CORRUPTION Unable to handle pakman corruption error: [chars]. chdlc_socket process restarting
Explanation A packet manager corruption has been reported and the cHDLC Socket process has failed to cleanup to recover from the problem. The process will exit and be automatically restarted to recover from this situation.
Recommended Action It is expected that restarting the process will fix this problem. This is done automatically so no action should be required. If the problem recurs, then there is a problem in packet manager. A drastic solution would be to reload the linecard.
CHDLCDLL Messages
Error Message%L2-CHDLCDLL-3-ERR_DEBUG_REGISTER Could not register for debug events : [chars]
Explanation There was an error registering the cHDLC Netio debug with the debug library. No debug will be available for the cHDLC Netio DLLs.
Recommended Action *SUPPORT*
Error Message%L2-CHDLCDLL-3-ERR_PKT_ENCAP Encapsulation of HDLC packet failed. Packet type-code [hex]
Explanation The encapsulation of an HDLC packet failed for the network protocol with the ethernet type code specified. The packet has been dropped.
Recommended Action *SUPPORT*
Error Message%L2-CHDLCDLL-3-ERR_TRACE_REGISTER Could not register with tracing infrastructure: [chars]
Explanation An attempt to register with the tracing infrastructure failed. This will mean that tracing for the cHDLC Netio DLLs will not be available.
Recommended Action *SUPPORT*
d1qnetio Messages
Error Message%L2-d1qnetio-3-CHAIN_BUILDER_FAILED The chain build function failed because '[chars]' (error: [chars])
Explanation The software forwarding support for IEEE802.1Q VLANs was unable to set up an interface. Software forwarding VLAN functionality on the affected node may be impaired.
Recommended Action It may help to restart the VLAN EA process on the affected node, with process restart vlan_ea location. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-d1qnetio-3-IDB_NOT_FOUND The Netio IDB associated with handle [hex] could not be found
Explanation The software forwarding support for IEEE802.1Q VLANs was unable to process a message sent to a particular interface because the interface does not exist in NetIO. Software forwarding VLAN functionality on the affected interface may be impaired. The interface can be determined from its handle with show im chains ifhandle.
Recommended Action Copy the error message exactly as it appears 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-d1qnetio-3-REGISTRY_CREATION_FAILED Unable to create the protocol registries during capsulation initialization
Explanation The 802.1Q NetIO component could not necessary data structures during its initialization. Software forwarding VLAN functionality on the affected is likely not to work.
Recommended Action Copy the error message exactly as it appears 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-d1qnetio-3-SUBBLOCK_REG_FAILED 802.1Q Netio failed to register the dot1q_ether subblock (error: [chars])
Explanation The software forwarding support for IEEE802.1Q VLANs was unable to initialise on the specified node. Software forwarding VLAN functionality on the affected is likely not to work.
Recommended Action Copy the error message exactly as it appears 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-d1qnetio-3-TRACE_INIT_ERROR A error occurred during trace initialization, err: [chars]
Explanation The 802.1Q NetIO component encoutered an error during trace buffer initialization. This is likely to cause VLAN interface setup to fail.
Recommended Action If this error occurred as a result of applying configuration, try removing and reapplying the configuration. If this does not work, it may be necessary to reload the affected linecard. Copy the error message exactly as it appears 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-d1qnetio-4-CHAIN_UNBUILDER_FAILED The chain unbuild function failed because '[chars]' (error: [chars])
Explanation The software forwarding support for IEEE802.1Q VLANs was unable to clean up an interface. Forwarding should not be affected.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-d1qnetio-4-DEBUG_INIT_ERROR An error occurred during debug initialization (error: [chars])
Explanation The 802.1Q NetIO component encoutered an error during debug initialization. This is likely to cause VLAN interface setup to fail.
Recommended Action If this error occurred as a result of applying configuration, try removing and reapplying the configuration. If this does not work, it may be necessary to reload the affected linecard. Copy the error message exactly as it appears 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-d1qnetio-4-DEVCTL_NOT_SUP Unsupported NetIO devctl code ([dec]) received
Explanation The 802.1Q NetIO component received an unexpected message. The message has been ignored. This may indicate that there is a version mismatch among the VLAN components.
Recommended Action Copy the error message exactly as it appears 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-d1qnetio-4-TERM_FAILED 802.1Q NetIO termination failed because '[chars]' (error: [chars])
Explanation The software forwarding support for IEEE802.1Q VLANs was unable to clean up. Forwarding should not be affected.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
DI Messages
Error Message%L2-DI-3-CHANNELCREATE unable to create channel [chars] (Error code [int])
Explanation Process failed to create communication channel and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-CHKPT unable to create checkpoint service.
Explanation Process failed to create checkpoint service and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-COMMAND Three command line parameters required: depository_id promid (0/1/2/3)
Explanation Process received wrong third command line parameter and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-COMMAND3 Third command line parameter is [unsigned long int].It must be 0/1/2/3.
Explanation Process received wrong third command line parameter and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-CONNECTION Unable to connect to channel [chars] (Error code [int])
Explanation Process failed to connect to communication channel and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DESTINSANE Data structure destination organizer [chars] is inconsistent for destination [unsigned long int].
Explanation Process detected inconsistent data structures and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DESTORG unable to create destination organizer.
Explanation Process failed to create destination organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DIDORG unable to create DID organizer.
Explanation Process failed to create DID organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DLLABSENT Driver DLL [chars] is absent on the platform.
Explanation A specific driver DLL is required to run certain hardware detected.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DLLORG unable to create DLL organizer.
Explanation Process failed to create DLL organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-DLLSYMMISSING Driver DLL [chars] has missing symbol [chars].
Explanation A specific driver DLL is not correct.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-ENTRY One of the drivers unable to init.
Explanation Process unable to init one of the drivers and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-ERRORG unable to create error organizer.
Explanation Process failed to create error organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-EVE Failed to init event manager event.
Explanation Process failed to create event manager event and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-EVELOOP IM notify event manager loop exited (Error no=[unsigned long int]).
Explanation Process terminated event manager loop and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-EVEMGR Failed to create event manager.
Explanation Process failed to create event manager and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-INCONSISTINSTHASH Data structure Instance Hash is inconsistent for instance id [unsigned long int].
Explanation Process detected inconsistent data structures and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-INCONSISTRSRCHASH Data structure Resource Hash is inconsistent for resource id [unsigned long int].
Explanation Process detected inconsistent data structures and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-INSTHASH unable to create instance hash.
Explanation Process failed to create instance hash and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-INSTSTORE unable to create instance persistence store.
Explanation Process failed to create instance persistence store and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-INTORG unable to create interrupt organizer.
Explanation Process failed to create interrupt organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-MAINLINE Unable to create mainline ipc server.
Explanation Process unable to create mainline ipc server and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-MUTEXINIT Mutex initialization error [chars] (Error code [int])
Explanation Process failed to initialize a mutex and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-MUTEXLOCKFAIL [chars] operation failed in [chars]; reason [chars]
Explanation DI failed to lock the packet mutex.
Recommended Action Copy the error message exactly as it appears 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-DI-3-NETIOEST NetIO failed to connect to driver_infra_partner and exiting..
Explanation The initial set up between two driver processes failed. NetIO exiting.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-OUTMEM malloc ([unsigned long int] bytes) from::[chars] failed.
Explanation Process failed to allocate run-time memory and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-PEERSTORE unable to create peer persistence store.
Explanation Process failed to create peer persistence store and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-REGOMISSING No installed software to match Hardware in slot [unsigned long int] (PROMID [unsigned long int]).
Explanation Report missing driver registration.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-REGOMISSING1 No installed software to match Hardware in I/O slot in route-processor [unsigned long int] (PROMID [unsigned long int]).
Explanation Report missing driver registration.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-REGOORG unable to create registration organizer.
Explanation Process failed to create registration organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-RESIDORG unable to create RESID organizer.
Explanation Process failed to create RESID organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-RESOURCEHASH unable to create resource hash.
Explanation Process failed to create resource hash and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-SHMWIN failed to reserve the shmwin VM region.
Explanation Process failed to reserve the shmwin VM region and hence exiting.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-STARTCHKPT unable to start checkpoint service.
Explanation Process failed to start checkpoint service and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-STARTDESTORG unable to start destination organizer.
Explanation Process failed to start destination organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-SYNHORG unable to create synchronizer organizer.
Explanation Process failed to create synchronizer organizer and hence terminating.
Recommended Action 'No action is required.'
Error Message%L2-DI-3-THREADCREATE Unable to create thread [chars] (Error code [int])
Explanation Process failed to create thread and hence terminating.
Recommended Action 'No action is required.'
DIV2_DM Messages
Error Message%L2-DIV2_DM-3-INFO driver manager: service degrading error, reason = [chars]
Explanation Driver manager encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears 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-DIV2_DM-3-INIT Driver manager: init. error encountered, reason=[chars]
Explanation Driver manager encountered an error and is not able recover frm it. A reason text will be supplied. Call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-DIV2_DM-3-NO_MEM Driver manager: memory allocation error for bytes
Explanation Driver manager encountered a fatal memory allocation error
Recommended Action Reduce other system activity (e.g. by killing non-essential processes) to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
DRIVERS_UTIL Messages
Error Message%L2-DRIVERS_UTIL-3-TUPLE_READ_ERROR [chars]: Tuple read failed with error [hex] [chars]
Explanation An error occured when trying to read the tuple from sysdb.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
DWDM Messages
Error Message%L2-DWDM-3-FATAL dwdm: fatal error encountered, reason=[chars]
Explanation dwdm encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-DWDM-3-FATAL_2 dwdm: fatal error encountered, reason=[chars], errno=[dec]
Explanation dwdm code encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears 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-DWDM-3-INFO dwdm: service degrading error, reason = [chars]
Explanation The dwdm encountered an error that would lead to degraded service.
Recommended Action Copy the error message exactly as it appears 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-DWDM-3-NOT_YET_IMPLEMENTED dwdm: this function [chars] is not yet implemented
Explanation dwdm, a function was not implemented.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
EGRESSQ Messages
Error Message%L2-EGRESSQ-3-ERR_MEM_ALLOC Failed to allocate memory for [chars]
Explanation System failed to allocate memory. It's likely that the system is running low on memory. Following are some reasons: 1) Failed to allocate memory for Egressq client add. 2) Failed to allocate memory for Egressq mapping table. 3) Failed to allocate memory for Queue leaky bucket limit table Memory. 4) Failed to allocate memory for Queue leaky bucket limit table memory. 5) Failed to allocate memory for Group leaky bucket limit table memory. 6) Failed to allocate memory for Group leaky bucket limit table memory. 7) Failed to allocate memory for Port leaky bucket limit table memory. 8) Failed to allocate memory for PLIM Asic back pressure table memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-EGRESSQ-3-FCRAM_BIST_FAILURE FCRAM BIST failed, channel: [dec], count: [dec], error_addr: [hex]
Explanation Egress Queue Manager encountered a FCRAM BIST failure error. Possible cause for this error condition is a faulty hardware.
Recommended Action No action is required. Process will be automatically restarted. If the message recurs, copy the error message exactly as it appears 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-EGRESSQ-3-HW_ERROR [chars]
Explanation Egress Queue Manager encountered a HW error. This is a severe error and ASIC will be reset by the driver.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-EGRESSQ-3-SBE_THRESHOLD_EXCEED Single Bit Error rate exceeded configured high threshold value:
Explanation Egressq SBE rate has exceeded the configured high threshold value. This is a self healing error condition.
Recommended Action No action is required. It is a self healing 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-EGRESSQ-3-UNALLOCATED_QUEUE_NOT_EMPTY Packets sent to unallocated egress queue [dec]. (queue size [dec] bytes)
Explanation Egressq driver detected that packets were sent to an Egressq queue which is unallocated. These packets will not be serviced and will remain in the queue until this queue is allocated and becomes active. This situation should normally not happen, but may possibly happen during transient conditions when egress queue information is being updated (for e.g. on SPA OIR). During this brief time period, one or few packets may be sent to an incorrect queue.
Recommended Action If this message appears more than once in response to the specific action taken or if the message indicates a large number of bytes (more than 10MB) in an unallocated queue(s), Copy the error message exactly as it appears 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-EGRESSQ-7-ERR_CLIENT_REG Client registration failed: [chars] reason: [chars]
Explanation An internal error was detected while clients are registering to Egressq process.
Recommended Action No action is required. Clients will automatically retry to connect to Egressq. If the message recurs, copy the error message exactly as it appears 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-EGRESSQ-7-ERR_EVM_FAIL EVM error : [chars] reason : [chars]
Explanation An internal error was detected when trying to create EVM connection. It can fail during following scenarios: 1) EDM registration/connect/notify. 2) BAG's rule registration failed.
Recommended Action No action is required. The process retries automatically. If the message recurs, copy the error message exactly as it appears 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-EGRESSQ-7-ERR_INTERNAL Internal error : [chars] reason : [chars]
Explanation An internal error was detected. There are several scenarios which can cause this error condition. Error message describes the cause. Some of these error conditions are serious and result in driver process restart, e.g. ASIC Init/remap, enable/disable failure. Following are some of the reasons for this internal error: 1) Obsolete API usage, it can be caused due to uncompatible component installed in the system. 2) Interface creation failed due to egressq port creation failure. 3) Can't map Interface handle to egressq port, it could be because of: a) Invalid interface handle passed. b) Internal interface to port mapping table is corrupted. 4) Egressq ASIC reinitialization failed, this is an irrecoverable situation, and Egressq driver will be restarted. 5) Egressq Group/Queue creation/ deletion failed. 6) ASIC enable /disable failed.
Recommended Action No action is required. The process will automatically retry. If the message recurs, copy the error message exactly as it appears 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-EGRESSQ-7-ERR_LWM_FAIL LWM message send failed: [chars] reason: [chars]
Explanation An internal error was detected when trying to send a LWM message. There are several scenarios which can cause this error condition. Error message describes the exact cause.
Recommended Action No action is required. The process retries automatically. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
E3EGRESSQ Messages
Error Message%L2-E3EGRESSQ-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. If the message recurs, copy the error message exactly as it appears 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-E3EGRESSQ-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 concurrent processes. This indicates a software error which could lead to data corruption and loss of traffic.
Recommended Action Reload the linecard. If the message recurs, copy the error message exactly as it appears 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-E3EGRESSQ-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 concurrent processes. This indicates a software error which could lead to data corruption and loss of traffic.
Recommended Action Reload the linecard. If the message recurs, copy the error message exactly as it appears 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-E3EGRESSQ-3-MEM_MAP memory mapping of tx mgid failed ([chars])
Explanation The process could not map the egress asic MGID SDRAM into its memory space.
Recommended Action Reload the linecard. If the message recurs, copy the error message exactly as it appears 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-E3EGRESSQ-3-RECONFIG [chars]: error [hex]
Explanation The egress queueing asic was reset, but could not be reconfigured. This may result in partial or complete loss of functionality of the asic.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-E3EGRESSQ-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-E3EGRESSQ-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 Reload the linecard. If the message recurs, copy the error message exactly as it appears 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-E3EGRESSQ-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 concurrent processes. This indicates a software error which could lead to eventual data corruption and loss of traffic.
Recommended Action Reload the linecard. If the message recurs, copy the error message exactly as it appears 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-E3EGRESSQ-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 Reload the linecard. If the message recurs, copy the error message exactly as it appears 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-E3EGRESSQ-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 Reload the linecard. If the message recurs, copy the error message exactly as it appears 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-E3EGRESSQ-4-INTERRUPT [chars]: reg [hex]
Explanation The E3EGRESSQ asic experienced an interrupt, and will be reset. After reset, normal operation should resume.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
E3INGRESSQ Messages
Error Message%L2-E3INGRESSQ-3-RECONFIG [chars]: error [hex]
Explanation The ingress queueing asic was reset, but could not be reconfigured. This may result in partial or complete loss of functionality of the asic.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-E3INGRESSQ-4-INTERRUPT [chars]: reg [hex]
Explanation The E3INGRESSQ asic experienced an interrupt, and will be reset. After reset, normal operation should resume.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
E5EGRESSQ Messages
Error Message%L2-E5EGRESSQ-3-RECONFIG [chars]: error [hex]
Explanation The egress queueing asic was reset, but could not be reconfigured. This may result in partial or complete loss of functionality of the asic.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-E5EGRESSQ-4-ERROR [chars]: error [hex]
Explanation The e5 egress queue driver encountered an internal error. The router may/may not continue to function normally.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-E5EGRESSQ-4-INTERRUPT [chars]: reg [hex]
Explanation The E5EGRESSQ asic experienced an interrupt, and will be reset. After reset, normal operation should resume.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
E5INGRESSQ Messages
Error Message%L2-E5INGRESSQ-3-RECONFIG [chars]: error [hex]
Explanation The ingress queueing asic was reset, but could not be reconfigured. This may result in partial or complete loss of functionality of the asic.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-E5INGRESSQ-4-INTERRUPT [chars]: reg [hex]
Explanation The E5INGRESSQ asic experienced an interrupt, and will be reset. After reset, normal operation should resume.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ETHER_NETIO Messages
Error Message%L2-ETHER_NETIO-4-DEBUG_REG Debug registration failed: [chars]
Explanation It was not possible for the Ethernet slow path support to initialize its debugging support. Some of the output from debug ether-netio output may be incomplete.
Recommended Action No action is required.
ether_spa_plugin Messages
Error Message%L2-ether_spa_plugin-6-ERRORRECOVER A Hardware or Software error occurred. Reason : [chars] Automatic Error recovery initiated. No further intervention required.
Explanation An error occurred in one of the devices, recovery would be attempted. If recovery succeeds no further messages would be logged and no intervention would be required.
Recommended Action No action is required.
Error Message%L2-ether_spa_plugin-6-OPTICS_OIR An Optics is [chars] for bay [dec] and port [dec]
Explanation The Optic Interface Module (OIM) for the specified port either has been inserted or removed.
Recommended Action No action is required.
Error Message%L2-ether_spa_plugin-6-UNSUPPORTED_OPTICS [chars] port [dec] security check failed . Disable
Explanation An Unsupported Optic Interface Module (OIM) for the specified port has been inserted .
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.
Error Message%L2-ETHER-3-BDL_IIR_OP_FAILED The basecaps failed to process a bundle IIR [chars] message on [chars], error: [chars]
Explanation The ethernet driver failed to process a bundle IIR notification message. Further it is not able to propagate the message back to the virtual interface owner, and hence it is possible that the Ether basecaps is out of step with the bundle configuration.
Recommended Action Restart the ether_caps_partner process in an attempt to recover, or if this fails, detach and re-attach the physical member interface that the error was reported on by unconfiguring and reconfiguring the bundle member id.
Error Message%L2-ETHER-4-ERR_EVM_EVENT_BLOCK Failure during receipt of message. Error: [chars]
Explanation A failure occurred handling a message arriving at one of the Ethernet capsulation processes. Under normal circumstances the process restarts with no impact to functionality. If this error message is seen repeatedly then Ethernet services may be affected on all Ether type interfaces on the given node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ETHER-4-INIT Failure during intialisation of [chars] in a Ether basecaps process. Error: [chars]
Explanation A failure occurred during the initialisation of one of the Ethernet capsulation processes. Under normal circumstances the process restarts with no impact to functionality. If this error message is seen repeatedly then Ethernet services may be affected on all Ether type interfaces on the given node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ETHERNET Messages
Error Message%L2-ETHERNET-3-INTERFACE_CREATE Failed to create interface [chars], due to error: [chars]
Explanation It was not possible to create or initialize the physical interface due to a driver error or a system error. The interface's config may not have been restored and the interface will not be usable.
Recommended Action Restart the driver process that reported the error. If the error is reported again then reloading the linecard may allow it to recover, but it will impact all traffic on that node. Copy the error message exactly as it appears 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-ETHERNET-3-MIB_ERROR Unable to fetch requested Etherlike MIB data for interface [hex]: [chars]
Explanation An error occured while trying to collect MIB data requested by the SNMP infrastructure. The data for which an error was encountered will not be presented in SNMP 'get' request results.
Recommended Action Such errors are not expected, and probably indicate an out-of-resource condition, or an inconsistency in the system state. Wait for any likely transient root problems to subside, and attempt to repeat the 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-ETHERNET-3-MTU_IMPOSE_FAILED Failed to set MTU of [unsigned int] on [chars]
Explanation The specified MTU could not be applied on this interface.
Recommended Action Choose a more appropriate MTU to configure on the interface considering the MTU requirements of any L3 protocols that are configured on the interface.
Error Message%L2-ETHERNET-3-STATE_FSM Port state FSM operation failed [chars] on [chars], due to error: [chars]
Explanation An operational error occured when handling a port state event in the port state machine, and the internal state may be left in an inconsistent state without user intervention.
Recommended Action 'shutdown' and 'no shutdown' the affected interface, this should allow the state machine to recover its operational state. Copy the error message exactly as it appears 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-ETHERNET-4-BDL_IIR_OP_FAILED The driver failed to process a bundle IIR [chars] message on [chars], error: [chars]
Explanation The ethernet driver failed to process a bundle IIR notification message. Further it is not able to propagate the message back to the virtual interface owner, and hence it is possible that the driver is out of step with the bundle configuration.
Recommended Action Restart the driver process that generated this error message and it will automatically 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-ETHERNET-4-INITIALIZATION Initialization of the G-Ether library failed, due to error: [chars]
Explanation A error occurred during the initialization of the common Ethernet driver library.
Recommended Action The driver process is restarted automatically, hence no user intervention should be required. If the message recurs, copy the error message exactly as it appears 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-ETHERNET-6-MTU_NEAR_HW_LIMIT The configured MTU of [unsigned int] on [chars] is close to the H/W limit, and hence large [chars] frames may be dropped as oversized frames
Explanation The configured MTU is close the maximum frame size allowed on the interface. Hence large 802.1Q or QinQ frames bigger than the maximum frame size supported on the interface may be dropped.
Recommended Action If 802.1Q or QinQ support is required on the interface, then it is recommended that either the configured interface MTU is reduced by 4 or 8 bytes, or the sub-interface MTU is reduced by 4 or 8 bytes to ensure that all frames are within the H/W limits.
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.
Error Message%L2-FIA-4-FIAHW_WARNING_UNSUPPORTED_CARD Warning: This is an unsupported SIP-600 card with lower revision Fabric Interface ASIC
Explanation This warning indicates that this is an older version of SIP-600 card which does not have a supported Fabric Interface ASIC (FIA). As a result, any CSC switch-over, RP fail-over or fabric card OIR may result in FIA ASIC errors, and the router may experience abnormal behavior.
Recommended Action Replace with a later version of SIP-600.
FIB_IPV4 Messages
Error Message%L2-FIB_IPV4-3-GEN_ERR FIB IPV4 internal error: [chars]
Explanation An internal software error 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-FIB_IPV4-5-RECURSIVE_LOOP FIB IPv4 Recursive loop: [chars]
Explanation Recursive loop was detected. The route update will be dropped
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FIB_IPV6 Messages
Error Message%L2-FIB_IPV6-3-GEN_ERR FIB IPV6 internal error: [chars]
Explanation An internal software error 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-FIB_IPV6-5-RECURSIVE_LOOP FIB IPv6 Recursive loop: [chars]
Explanation Recursive loop was detected. The route update will be dropped
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FR_EDM Messages
Error Message%L2-FR_EDM-2-INIT [chars] : [chars]
Explanation Init error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-FR_EDM-3-NO_STATS unable to get stats for vc [hex], [dec]
Explanation The statistics manager returned null data for vc
Recommended Action Copy the error message exactly as it appears 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-FR_EDM-3-NOMEM unable to allocate [dec] bytes of memory
Explanation The system is low on memory and not enough was available to complete the request
Recommended Action Check the box for processes with excessive memory If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FR_INARP Messages
Error Message%L2-FR_INARP-2-CONNECT_IM failure on IM connection: [chars]
Explanation This error indicates a problem with InARP/IM interaction.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_INARP-2-INIT failed to initialize: [chars]
Explanation During process start up an unrecoverable error occurred. The component will exit and should be restarted by the System Manager.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-FR_INARP-3-IF_VC_CLASS unable to apply class [chars] to interface [chars]: [chars]
Explanation A vc-class was configured on an interface but couldn't be applied for the given 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-FR_INARP-3-INVALID_FD received an event on unknown fd [dec]
Explanation An event was received with an unknown fd
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_INARP-3-NOMEM unable to allocate [dec] bytes of memory
Explanation The system is low on memory and not enough was available to complete the request
Recommended Action Check the box for processes with excessive memory If the message recurs, copy the error message exactly as it appears 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-FR_INARP-3-PVC_VC_CLASS unable to apply class [chars] to interface [chars].[dec]: [chars]
Explanation A vc-class was configured on an interface but couldn't be applied
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_INARP-3-SOCKET_SEND could not send on socket: [chars]
Explanation Socket returned an error, not EAGAIN or EINTR
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_INARP-3-UNKNOWN_EVENT received an unknown event [hex]
Explanation An unknown event was received
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_INARP-3-UNKNOWN_IDB received information about an unrecognised interface
Explanation A set of IDBs are kept with information on each InARP interface. Somehow this information has become inconsistent with the system.
Recommended Action Restart the main process (containing the InARP DLL) If the message recurs, copy the error message exactly as it appears 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-FR_INARP-4-UNKNOWN_INTFTYPE received an event for an unknown interface type: [dec]
Explanation The system sent a messages which wasn't expected. It will be ignored.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_INARP-4-UNKNOWN_MSG received an unknown message: [dec]
Explanation An unknown InARP message was received - it will be ignored
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FR_LMI Messages
Error Message%L2-FR_LMI-2-INIT LMI failed to initialize: [chars]
Explanation During process start up an unrecoverable error occurred. The component will exit and should be restarted by the System Manager.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-FR_LMI-3-CODEP_ERROR Configured values of [chars] and [chars] conflict during application. Changing [chars] to [dec] to maintain consistency
Explanation LMI parameters N392 and N393 are co-dependent - they must obey the rule N392 less than or equal to N393. Somehow SysDB is attempting to apply config which conflicts unreconcilably. The parameter being configured is adjusted to be equal to the other.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_LMI-3-ENCAP Unable to process Frame Relay encapsulation request
Explanation An error occurred processing a request to set Frame Relay encapsulation on an interface. LMI will not be able to control the interface.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_LMI-3-IDB_SEARCH The interface specified by a handle is not one that LMI recognizes as running Frame Relay
Explanation A call to rt_search failed to return an idb object.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_LMI-3-KEEPALIVES An error occurred informing the VC Manager that LMI is [chars] responsible for the line state of an interface: [chars]
Explanation An error occurred in the VCM call to set the keepalive state.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_LMI-3-LINE_STATE An error occurred informing the VC Manager of the line state: [chars]
Explanation The VC Manager returned an error after receving a request to set the line state.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_LMI-3-MALLOC Memory allocation failed: [chars]
Explanation A call to malloc failed.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_LMI-3-RECVFROM An error occurred receiving a packet: [chars]
Explanation The socket call recvfrom returned an error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-FR_LMI-3-SENDTO An error occurred sending a packet: [chars]
Explanation The socket call sendto returned an error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-FR_LMI-3-SET_DLCI_STATUS An error occurred sending the updated VC states to the VC Manager: [chars]
Explanation The VC Manager returned an error after receving a request to update VC states.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_LMI-3-VC_CREATE Unable to create LMI DLCI [dec]: [chars]
Explanation LMI was unable to create a VC it needed to function properly.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_LMI-3-VCM_VC_STATES LMI was unable to send all VC states to the VC Manager
Explanation An error occurred sending the VC states to the VC Manager. This could have occurred searching LMI's internal database or in the call to the VCM.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_LMI-6-CODEP_CHANGE Changing defaulted value of [chars] to [dec] due to configured value of [chars]
Explanation LMI parameters N392 and N393 are co-dependent - they must obey the rule N392 less than or equal to N393. Sometimes when one is changed the other must be changed as well to keep the protocol functioning properly.
Recommended Action None. This is not an error, just a notification.
FR_NETIO Messages
Error Message%L2-FR_NETIO-3-MEMORY Failed to allocate [unsigned int] bytes
Explanation The DLL has failed to acquire the required amount of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-FR_NETIO-6-DEBUG_REG Debug registration failed: [chars]
Explanation Debug message registration failed
Recommended Action No action is required.
FR_SFRAR Messages
Error Message%L2-FR_SFRAR-2-INIT SFRAR failed to initialize: [chars]
Explanation During process start up an unrecoverable error occurred. The component will exit and should be restarted by the System Manager.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-FR_SFRAR-3-SYSMGR SFRAR process ready call failed: [chars]
Explanation The call to inform the System Manager that SFRAR is running failed.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FR_SOCKET Messages
Error Message%L2-FR_SOCKET-2-INIT Socket failed to initialize: [chars]
Explanation During process start up an unrecoverable error occurred. The component will exit and should be restarted by the System Manager.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-FR_SOCKET-3-CONN Failed to setup fr socket EVM connection: [chars]
Explanation The fr_socket process failed to connect to the event manager.
Recommended Action Copy the error message exactly as it appears 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-FR_SOCKET-3-DPC_FAIL Failed to register [chars] protocol in netio
Explanation The fr_socket process failed to send dpc message to Netio
Recommended Action Copy the error message exactly as it appears 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-FR_SOCKET-3-NETIO_OUTPUT_FAIL Failed to send packet out to Netio: [chars]
Explanation The fr_socket process failed to send packet out to Netio.
Recommended Action Copy the error message exactly as it appears 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-FR_SOCKET-3-NOMEM unable to allocate [dec] bytes of memory
Explanation The system is low on memory and not enough was available to complete the request
Recommended Action Check the box for processes with excessive memory If the message recurs, copy the error message exactly as it appears 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-FR_SOCKET-3-PACKET_CONN Failure in packet manager connection: [chars]
Explanation The fr_socket process failed to connect to packet manager
Recommended Action Copy the error message exactly as it appears 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-FR_SOCKET-3-RESMGR_ATTACH Failed to setup fr socket as a resource manager: [chars]
Explanation The fr_socket process failed to advertise itself to the system as a resource manager.
Recommended Action Copy the error message exactly as it appears 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-FR_SOCKET-3-SEND_ASYNC Failed to send async pulse [dec]: [chars]
Explanation The fr_socket process failed to send async pulse to FR socket EVM
Recommended Action Copy the error message exactly as it appears 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-FR_SOCKET-3-SYSMGR SysMgr process ready call failed: [chars]
Explanation The call to inform the System Manager that the FR socket is running failed.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FR_UV Messages
Error Message%L2-FR_UV-3-EVENT Unrecoverable error in event loop. Error: [chars]
Explanation An error (other than EINTR) occured in the event loop. The process must exit.
Recommended Action Identify the location of the card where there error was reported. Copy the error message exactly as it appears on the console or in the system log. Issue the show memory location summary command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show memory location summary output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-FR_UV-3-INIT Failure during intialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the process. This resulted in the restart of 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-FR_UV-3-SYSMGR Failure communicating readiness to System Manager. Error: [chars]
Explanation The process was initialized successfully but was unable to inform System Manager of the success.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FR_VCM_EA Messages
Error Message%L2-FR_VCM_EA-2-INTERNAL_ERR [chars]
Explanation Internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-FR_VCM_EA-3-AIB_INIT_FAILED Failed during AIB initialization, err: [chars]
Explanation The FR VCM EA process initialization failed whilst trying to connect to AIB.
Recommended Action Copy the error message exactly as it appears 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-FR_VCM_EA-3-BATCH_INTERFACE_ERROR Error during messaging: [chars]
Explanation The FR VCM EA process has detected an error during messaging. Possible memory corruption or out of resource.
Recommended Action Copy the error message exactly as it appears 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-FR_VCM_EA-3-DATABASE_KEY_MISSING Internal database access error
Explanation The FR VCM EA process code/data is inconsistent. Possible coding error or data corruption.
Recommended Action Copy the error message exactly as it appears 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-FR_VCM_EA-3-NO_STATS Failed to initialize FR VCM subinterface stats collection, err: [chars]
Explanation The FR VCM EA subinterface stats collection initialization 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.
FR_VCM Messages
Error Message%L2-FR_VCM-2-CONFIG_INIT Configuration registration failed: [chars]
Explanation Unable to register for configuration changes.
Recommended Action Copy the error message exactly as it appears 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-FR_VCM-2-CONNS Connection initialization failed: [chars]
Explanation Unable to initialize connections to one or more servers.
Recommended Action Copy the error message exactly as it appears 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-FR_VCM-3-CONNECT_TO_L2VPN Connect to L2VPN server failed: [chars]
Explanation FR VCM process on linecard tried to connect to L2VPN server on RP. Connect registration failed. FR L2 sub-interfaces will not be operational on this linecard.
Recommended Action Copy the error message exactly as it appears 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-FR_VCM-3-ENCAPS_TYPE Unable to specify [chars] encaps type for interface [chars]: [chars]
Explanation The configuration in the NetIO DLL could not be updated, the system may continue with the existing encapsulation 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.
Error Message%L2-FR_VCM-3-IDB FR [chars] IDB [chars] failed: [chars]
Explanation Unexpected error on Interface Descriptor Block
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_VCM-3-IM_OP FR [chars] on [chars] failed: [chars]
Explanation The operation on the named item is not completing successfully when it is expected to, and hence the FR support may be disabled
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_VCM-3-INTF_NOTFOUND FR interface [chars] not found
Explanation An action has been performed on a FR interface, but FR doesn't have any information about the interface.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_VCM-3-MAIN_IF FR error on main interface [chars]: [chars]
Explanation Unexpected error on the main interface
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_VCM-3-NOMEM unable to allocate [dec] bytes of memory
Explanation The system is low on memory and not enough was available to complete the request
Recommended Action Check the box for processes with excessive memory If the message recurs, copy the error message exactly as it appears 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-FR_VCM-3-PTP_VC FR PVC create (dlci [dec]) on PTP subinterface failed - only one PVC is allowed
Explanation Point-to-point (PTP) subinterfaces only allow one PVC and an attempt to create a second PVC is being rejected
Recommended Action Remove the old PVC before creating the replacement, or use a multipoint subinterface instead
Error Message%L2-FR_VCM-3-SUB_IF FR error on sub-interface [chars]: [chars]
Explanation Unexpected error on the sub-interface
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_VCM-3-SYSDB_OP FR SysDB [chars] on [chars] failed: [chars]
Explanation Unexpected failure performing a SysDB operation.
Recommended Action Check SysDB is still running, and if not restart it. If the message recurs, copy the error message exactly as it appears 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-FR_VCM-3-VC_EXISTS FR VC with DLCI [dec] already exists
Explanation The DLCI is unique per 'main' interface and this dlci is already used
Recommended Action None.
Error Message%L2-FR_VCM-3-VC_NOTFOUND FR VC with DLCI [dec] not found
Explanation An operation was performed which expected a VC with the specified DLCI to exist, but it doesn't
Recommended Action If the message recurs, copy the error message exactly as it appears 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-FR_VCM-6-DEBUG_REG Debug registration failed: [chars]
Explanation Debug message registration failed
Recommended Action No action is required.
FRMIB Messages
Error Message%L2-FRMIB-3-SYSDB FR MIB: [chars]: [chars]: [chars]
Explanation This message indicates the FR MIB library fails to perform a SYSDB operation. *DDTS*
Recommended Action If the message recurs, copy the error message exactly as 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.
Error Message%L2-FWD_EDGE_COMMON-3-EDGE_IP_ERR fib ip engine layer internal error [chars] : [chars]
Explanation A runtime failure occurred in fib ip 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.
G709 Messages
Error Message%L2-G709-4-ALARM [chars]: [chars] [chars]
Explanation The specified G709 Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
GATM Messages
Error Message%L2-GATM-2-ERR [chars] - [dec]: [chars]
Explanation Error in gatm operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-GATM-2-ERR_HEX [chars] - [dec]: [chars] ([hex])
Explanation Error in gatm operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-GATM-2-ERR_IFH_STS [chars] - [dec]: [chars] ifh=[hex] rc=[hex]
Explanation Error in gatm operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-GATM-2-ERR_INT [chars] - [dec]: [chars] ([dec])
Explanation Error in gatm operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-GATM-2-ERR_STR [chars] - [dec]: [chars] ([chars])
Explanation Error in gatm operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-GATM-2-ERR_STS [chars] - [dec]: [chars] (rc = [hex])
Explanation Error in gatm operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
GE Messages
Error Message%L2-GE-3-INIT_ERR PRP Gigabit Ethernet execution agent initialization failed. [chars]/[chars]
Explanation The PRP Gigabit ethernet execution agent failed to initialize. The PRP gigabit ethernet execution agent provides the support for packet forwarding over the GE port present on the Performance Route Processor. A failure of this execution agent likely means that packets being sent to or from the PRP's GE ports are going to be lost. %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 ge_mgmt location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart ge_mgmt 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.
GE_ASIC Messages
Error Message%L2-GE_ASIC-3-INIT_ERR GigE hardware initialization failed. Reason=[chars], Error Decode=[chars]
Explanation The GE hardware managment subsystem encountered an error during initialization. This process monitors and controls hardware components required for the RP management ethernet port. A failure in this subsystem will disable the the RP's onboard ethernet. %s - indicates the reason for the failure %s - indicates 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 ge_mgmt' to verify that the process is up and running. If it is not, try doing 'process restart ge_mgmt' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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 slot 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 slot 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 slot 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-3-SPABRG_ERR4_HW [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_ERR5_HW [chars] : [chars] : [hex] [hex]
Explanation EE192 Spabrg driver single-bit error
Recommended Action No action is required.
Error Message%L2-GSR-3-SPABRG_ERR6_HW [chars] : [chars] : [hex] [hex] [hex]
Explanation EE192 Spabrg driver single-bit error
Recommended Action No action is required.
Error Message%L2-GSR-3-SPABRG_ERR7_HW [chars] : [hex] [hex]
Explanation EE192 Spabrg driver error
Recommended Action No action is required.
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
GT64115 Messages
Error Message%L2-GT64115-2-PCI_CONFIG Fatal error: [chars]: [dec]
Explanation A fatal error occurred during GT64115 PCI Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-GT64115-2-PCI_INIT Fatal error: [chars]
Explanation A fatal error occurred during GT64115 PCI Driver initialization
Recommended Action If the message recurs, copy the error message exactly as it appears 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-GT64115-3-PCI_BRIDGE_INTR PCI Bridge Intr: [chars] [dec] [dec]
Explanation This is an error message resulted from an interrupt from the PCI device.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
gulf Messages
Error Message%L2-gulf-3-FATAL_ERROR Fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in gulf 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-gulf-4-WARNING warning: [chars]: [chars]: [dec]
Explanation A warning condition is detected in gulf 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-gulf-6-INFO_MSG Info: [chars]: [chars]: [dec]
Explanation This is a Informational message in the gulf driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-gulf-7-DEBUG_MSG Debug: [chars]: [chars]: [dec]
Explanation This is a debug message in the gulf driver to indicate anomolies 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 temperory 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.
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.
if_discovery Messages
Error Message%L2-if_discovery-3-FATAL_ERROR Fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in plim pos 4p oc12 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-if_discovery-6-INFO_MSG Info: [chars]: [chars]
Explanation This is a Informational message in the plim pos 4p oc12 driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-if_discovery-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the plim pos 4p oc12 driver to indicate anomolies 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 temperory 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.
IOB Messages
Error Message%L2-IOB-3-INTR IOB Intr: [chars]
Explanation The IOB FPGA has been interrupted due to an access fault
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IOB-5-UNKNOWN_INTR IOB Intr: [chars]: [dec]: [dec]
Explanation This is a message in the IOB FPGA driver to indicate that it has detected an unknown interrupt.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
IPCP Messages
Error Message%L2-IPCP-1-ERR_ADJ_DELETE Failed to remove [chars] from adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPCP-1-ERR_ADJ_UPDATE Failed to add [chars] into adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPCP-1-ERR_RIB_ROUTE_ADD Failed to add route into RIB; [chars]
Explanation An error was encountered while connecting to the RIB.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPCP-3-DEBUG_ASSOC Conditional debug association failed; [chars]
Explanation An error has occurred upon attempting to associate conditional debugging with PPP debug commands. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
Recommended Action Copy the error message exactly as it appears 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-IPCP-3-DEBUG_COND_REGISTER Conditional debug registration failed; [chars]
Explanation An error has occurred upon attempting to register for conditional debugs. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
Recommended Action Copy the error message exactly as it appears 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-IPCP-3-DEBUG_REGISTER Debug registration failed; [chars]
Explanation An error has occurred upon attempting to connect to the debug server. This may cause debug messages to not appear.
Recommended Action Copy the error message exactly as it appears 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-IPCP-3-ERR_CONN Connection [chars] failed for [chars]; [chars]
Explanation An failure in the reconnection software in the 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-IPCP-3-ERR_EVENT Failed to [chars] [chars] event; [chars]
Explanation An event handler has returned an 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-IPCP-3-ERR_EVENT_MGR_CREATE IPCP Failed to initialize event manager; [chars]
Explanation Initialization of the event manager 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-IPCP-3-ERR_IM_STATE Failed to get basecaps state for [chars]; [chars]
Explanation IPCP was unable to determine the state of the basecaps and has assumed it to be down. IPCP will remain closed until the interface is brought down and up again.
Recommended Action Shut the interface and then bring it up again.
Error Message%L2-IPCP-3-ERR_IPARM Error [chars] IP-ARM; [chars]
Explanation IPCP could not perform the operation with IP-ARM that was desired.
Recommended Action Restart the IPCP and IP-ARM processes. Copy the error message exactly as it appears 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-IPCP-3-ERR_MBOX_ADD [chars] [chars] failed to add [chars]; [chars]
Explanation An attribute has failed to be added to the message which was being constructed which has caused the message to be discarded.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPCP-3-ERR_MBOX_CREATE [chars] failed to create [chars]; [chars]
Explanation An attempt to allocate a message failed. This may be due to lack of resources.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPCP-3-ERR_MBOX_INIT Failed to init [chars] message for [chars]; [chars]
Explanation The initialization of a message failed, this results in a failure to communicate with the Link Control Protocol.
Recommended Action Copy the error message exactly as it appears 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-IPCP-3-ERR_MBOX_SEND [chars] failed to send [chars]; [chars]
Explanation A message failed in a send attempt to a particular mailbox.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPCP-3-ERR_MQ_CREATE Failed to create message queue to AAA; [chars]
Explanation IPCP has failed to open its mailbox channel to AAA.
Recommended Action Copy the error message exactly as it appears 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-IPCP-3-ERR_MQ_OPEN Failed to open message queue [chars]; [chars]
Explanation IPCP has failed to open a mailbox channel.
Recommended Action Copy the error message exactly as it appears 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-IPCP-3-ERR_NETIO_RXQ Failed to support [chars] [chars]; [chars]
Explanation IPCP has attempted to update the data component with the current status of the control protocol. The attempt has failed which will has the effect of leaving the data component with the previous set of information. This may result in an inability to negotiate IPCP.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPCP-3-ERR_SYSDB SysDB [chars] failed; [chars]
Explanation IPCP cannot perform some SysDB operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-IPCP-3-ERR_SYSDB_NOTIFICATION Failed to [chars]register for SysDB notification of [chars]; [chars]
Explanation IPCP cannot (un)register for SysDB notification.
Recommended Action Copy the error message exactly as it appears 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-IPCP-3-ERR_SYSDB_VERIFICATION Failed to [chars]register for SysDB verification of [chars]; [chars]
Explanation IPCP cannot (un)register for SysDB verification.
Recommended Action Copy the error message exactly as it appears 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-IPCP-3-ERR_TIMER [chars] [chars] timer [chars]
Explanation The manipulation of a timer had an abnormal side effect.
Recommended Action Copy the error message exactly as it appears 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-IPCP-3-LTRACE_INIT IPCP Failed to initialize the ltrace buffer; [chars]
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-IPCP-4-ERR_CHKPT Failed checkpoint [chars]
Explanation An error has occurred upon attempting to connect to the checkpointing server. This may cause inconsistent state to be present within IPCP.
Recommended Action Copy the error message exactly as it appears 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-IPCP-4-ERR_CHKPT_ITERATE Failed iterating checkpoint store: [chars]
Explanation An error has occurred while iterating the checkpoint data store after a process restart. The process will exit and hope for a clear run next time. If failure persists its checkpoint store will be deleted and it will do a cold restart which should resolve the problem.
Recommended Action If multiple restarts does not work then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-IPCP-4-ERR_EVENT_WAIT Error waiting for event; [chars]
Explanation The event loop has received a message of a type it does not recognize. All events should be received by handlers.
Recommended Action Copy the error message exactly as it appears 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-IPCP-4-ERR_IM_ENCAPS Error checking base encapsulation for [chars]; [chars]
Explanation IPCP was unable to check the base encapsulation of an interface with IM. This may result in IPCP not running on the interface if PPP encapsulation was present.
Recommended Action If the interface that the error is reported for does not have PPP encapsulation then there is no problem. If the interface does have PPP encapsulation then first remove and re-add the IP address or IP unnumbered configuration. If this doesn't get IPCP working then remove and re-add the PPP encapsulation. If IPCP still does not work then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-IPCP-4-ERR_INTERFACE_NULL [chars]: Interface NULL
Explanation A function was called with a NULL interface pointer.
Recommended Action Copy the error message exactly as it appears 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-IPCP-4-ERR_MEMORY Insufficient memory for [chars]
Explanation IPCP failed to allocate memory for a 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-IPCP-4-ERR_MQ_RECEIVE Error receiving from message queue; [chars]
Explanation IPCP has failed to receive a message from its mailbox.
Recommended Action Copy the error message exactly as it appears 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-IPCP-4-ERR_NO_INTERFACE Interface [chars] not found
Explanation A SysDB name lookup 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-IPCP-4-ERR_NO_INTERFACE_STRUCT Structure for interface [chars] not created; [chars]
Explanation IPCP failed to create an interface structure.
Recommended Action Copy the error message exactly as it appears 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-IPCP-6-ERR_IM_CONNECT Failed to [chars]bind [chars] IM; [chars]
Explanation IPCP has failed to either bind to or unbind from the interface manager server.
Recommended Action No action is required.
Error Message%L2-IPCP-6-ERR_IM_EVENT Failed to [chars] event; [chars]
Explanation IPCP has failed to either initialize or specify an event with the interface manager server.
Recommended Action No action is required.
Error Message%L2-IPCP-6-ERR_IM_PROTO Failed to [chars] [chars] protocol; [chars]
Explanation IPCP has failed a protocol operation with the interface manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
IPV6_EA Messages
Error Message%L2-IPV6_EA-3-INIT Failed to initialize [chars], because of [chars]
Explanation Initialization process such as getting an evm failed.
Recommended Action sysmgr will retry to start the ipv6_ea. If not recovered, it's a fatal condition. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*
Error Message%L2-IPV6_EA-3-NOMEM IPv6 EA failed to program '[chars]' due to low memory
Explanation The IPv6 EA process could not allocate memory needed to program some IPv6 feature.
Recommended Action Check memory status.
Error Message%L2-IPV6_EA-4-ERROR [chars]: [chars]
Explanation There was an error with processing an event in the EA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
IPV6_ND_Lite Messages
Error Message%L2-IPV6_ND_Lite-3-ERR_CHAN_CONNECT_FAIL Cannot connect to ipv6 nd lite process; Error [chars]
Explanation Attempt to connect to ipv6 nd lite process channel fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
IPV6CP Messages
Error Message%L2-IPV6CP-1-ERR_ADJ_DELETE Failed to remove [chars] from adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPV6CP-1-ERR_ADJ_UPDATE Failed to add [chars] into adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPV6CP-3-DEBUG_ASSOC Conditional debug association failed; [chars]
Explanation An error has occurred upon attempting to associate conditional debugging with PPP debug commands. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-3-DEBUG_COND_REGISTER Conditional debug registration failed; [chars]
Explanation An error has occurred upon attempting to register for conditional debugs. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-3-DEBUG_REGISTER Debug registration failed; [chars]
Explanation An error has occurred upon attempting to connect to the debug server. This may cause debug messages to not appear.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-3-ERR_CONN Connection [chars] failed for [chars]; [chars]
Explanation An failure in the reconnection software in the 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-IPV6CP-3-ERR_EVENT Failed to [chars] [chars] event; [chars]
Explanation An event handler has returned an 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-IPV6CP-3-ERR_EVENT_MGR_CREATE IPV6CP Failed to initialize event manager; [chars]
Explanation Initialization of the event manager 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-IPV6CP-3-ERR_IM_STATE Failed to get basecaps state for [chars]; [chars]
Explanation IPV6CP was unable to determine the state of the basecaps and has assumed it to be down. IPV6CP will remain closed until the interface is brought down and up again.
Recommended Action Shut the interface and then bring it up again.
Error Message%L2-IPV6CP-3-ERR_MBOX_ADD [chars] [chars] failed to add [chars]; [chars]
Explanation An attribute has failed to be added to the message which was being constructed which has caused the message to be discarded.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPV6CP-3-ERR_MBOX_CREATE [chars] failed to create [chars]; [chars]
Explanation An attempt to allocate a message failed. This may be due to lack of resources.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPV6CP-3-ERR_MBOX_INIT Failed to init [chars] message for [chars]; [chars]
Explanation The initialization of a message failed, this results in a failure to communicate with the Link Control Protocol.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-3-ERR_MBOX_SEND [chars] failed to send [chars]; [chars]
Explanation A message failed in a send attempt to a particular mailbox.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPV6CP-3-ERR_MQ_OPEN Failed to open message queue [chars]; [chars]
Explanation IPV6CP has failed to open a mailbox channel.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-3-ERR_NETIO_RXQ Failed to support [chars] [chars]; [chars]
Explanation IPV6CP has attempted to update the data component with the current status of the control protocol. The attempt has failed which will has the effect of leaving the data component with the previous set of information. This may result in an inability to negotiate IPV6CP.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IPV6CP-3-ERR_SYSDB SysDB [chars] failed; [chars]
Explanation IPV6CP cannot perform some SysDB operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-IPV6CP-3-ERR_SYSDB_NOTIFICATION Failed to [chars]register for SysDB notification of [chars]; [chars]
Explanation IPV6CP cannot (un)register for SysDB notification.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-3-ERR_SYSDB_VERIFICATION Failed to [chars]register for SysDB verification of [chars]; [chars]
Explanation IPV6CP cannot (un)register for SysDB verification.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-3-ERR_TIMER [chars] [chars] timer [chars]
Explanation The manipulation of a timer had an abnormal side effect.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-3-LTRACE_INIT IPV6CP Failed to initialize the ltrace buffer; [chars]
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-IPV6CP-4-ERR_CHKPT Failed checkpoint [chars]
Explanation An error has occurred upon attempting to connect to the checkpointing server. This may cause inconsistent state to be present within IPV6CP.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-4-ERR_CHKPT_ITERATE Failed iterating checkpoint store: [chars]
Explanation An error has occurred while iterating the checkpoint data store after a process restart. The process will exit and hope for a clear run next time. If failure persists its checkpoint store will be deleted and it will do a cold restart which should resolve the problem.
Recommended Action If multiple restarts does not work then Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-IPV6CP-4-ERR_EVENT_WAIT Error waiting for event; [chars]
Explanation The event loop has received a message of a type it does not recognize. All events should be received by handlers.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-4-ERR_INTERFACE_NULL [chars]: Interface NULL
Explanation A function was called with a NULL interface pointer.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-4-ERR_MEMORY Insufficient memory for [chars]
Explanation IPV6CP failed to allocate memory for a 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-IPV6CP-4-ERR_MQ_RECEIVE Error receiving from message queue; [chars]
Explanation IPV6CP has failed to receive a message from its mailbox.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-4-ERR_NO_INTERFACE Interface [chars] not found
Explanation A SysDB name lookup 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-IPV6CP-4-ERR_NO_INTERFACE_STRUCT Structure for interface [chars] not created; [chars]
Explanation IPV6CP failed to create an interface structure.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-6-ERR_IM_CONNECT Failed to [chars]bind [chars] IM; [chars]
Explanation IPV6CP has failed to either bind to or unbind from the interface manager server.
Recommended Action No action is required.
Error Message%L2-IPV6CP-6-ERR_IM_ENCAPS Failed to [chars] [chars] encapsulation; [chars]
Explanation IPV6CP has failed an encapsulation operation with the interface manager.
Recommended Action Copy the error message exactly as it appears 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-IPV6CP-6-ERR_IM_EVENT Failed to [chars] event; [chars]
Explanation IPV6CP has failed to either initialize or specify an event with the interface manager server.
Recommended Action No action is required.
Error Message%L2-IPV6CP-6-ERR_IM_PROTO Failed to [chars] [chars] protocol; [chars]
Explanation IPV6CP has failed a protocol operation with the interface manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
IXP2800_FWD Messages
Error Message%L2-IXP2800_FWD-3-IPCP_FAILURE Function [chars] failure errno [chars]
Explanation IPCP communication failure.
Recommended Action None
Error Message%L2-IXP2800_FWD-3-NONFATAL_ERROR Nonfatal error: [chars] error code [dec]
Explanation This is a error message of the IXP2800 forwarding driver to indicate either anomalies which are not fatal. Some of the messages may indicate a failure to allocate resources needed by applications.
Recommended Action None
Error Message%L2-IXP2800_FWD-7-LOG_FILE_ERROR Test DLL failed to open log file [chars] ([chars])
Explanation The NPU test DLL failed to open the log file
Recommended Action None
Error Message%L2-IXP2800_FWD-7-UNEXPECTED_FUNC_INVOC Function [chars] invoked
Explanation An unexpected function invocation occured
Recommended Action None
IXP2800_HW Messages
Error Message%L2-IXP2800_HW-2-NOMEM ixp2800 HW driver Could not allocate memory
Explanation 'ixp2800 HW driver has failed to aquire the required amount of memory.'
Recommended Action *REDUCE*
Error Message%L2-IXP2800_HW-3-FATAL_ERROR [chars]()[[dec]]: [chars]: [chars] ([dec])
Explanation A fatal error occurred in IXP2800_HW 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-IXP2800_HW-4-WARNING [chars]()[[dec]]: [chars]: [chars] ([dec])
Explanation A warning condition occurred in IXP2800_HW Driver which involves exiting the process.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-IXP2800_HW-6-INFO [chars]
Explanation SERVICE card ixp2800_hw driver informational message
Recommended Action NONE : Informational message only
Error Message%L2-IXP2800_HW-7-LOG_FILE_ERROR ixp2800 HW driver DLL failed to open log file [chars] ([chars])
Explanation The NPU HW driver DLL failed to open the log file
Recommended Action None
IXP2800_SERVICE Messages
Error Message%L2-IXP2800_SERVICE-2-NOMEM ixp2800 service Could not allocate memory
Explanation 'ixp2800 service has failed to aquire the required amount of memory.'
Recommended Action *REDUCE*
Error Message%L2-IXP2800_SERVICE-3-FATAL_ERROR [chars]()[[dec]]: [chars]: [chars] ([dec])
Explanation A fatal error occurred in IXP2800_SERVICE 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-IXP2800_SERVICE-3-HOST_SPU_ERROR [chars] Fatal error - [chars]
Explanation A fatal error occurred in SPU common Driver
Recommended Action If the message recurs, copy the error message exactly as it appears 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-IXP2800_SERVICE-3-IPCP_FAILURE Function [chars] failure errno [chars]
Explanation IPCP communication failure.
Recommended Action None
Error Message%L2-IXP2800_SERVICE-4-WARNING [chars]()[[dec]]: [chars]: [chars] ([dec])
Explanation A warning condition occurred in IXP2800_SERVICE Driver which involves exiting the process.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-IXP2800_SERVICE-6-INFO [chars]
Explanation SERVICE card ixp2800_service driver informational message
Recommended Action NONE : Informational message only
Error Message%L2-IXP2800_SERVICE-7-LOG_FILE_ERROR ixp2800 service DLL failed to open log file [chars] ([chars])
Explanation The NPU service DLL failed to open the log file
Recommended Action None
IXP2800_VFW Messages
Error Message%L2-IXP2800_VFW-2-NOMEM ixp2800 service Could not allocate memory
Explanation 'ixp2800 vFW service has failed to aquire the required amount of memory.'
Recommended Action *REDUCE*
Error Message%L2-IXP2800_VFW-3-FATAL_ERROR [chars]()[[dec]]: [chars]: [chars] ([dec])
Explanation A fatal error occurred in IXP2800_SERVICE 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-IXP2800_VFW-3-IPCP_FAILURE Function [chars] failure errno [chars]
Explanation IPCP communication failure.
Recommended Action None
Error Message%L2-IXP2800_VFW-3-NONFATAL_ERROR Nonfatal error: [chars] error code [dec]
Explanation This is a error message of the IXP2800 service driver to indicate either anomalies which are not fatal. Some of the messages may indicate a failure to allocate resources needed by applications.
Recommended Action None
Error Message%L2-IXP2800_VFW-4-WARNING [chars]()[[dec]]: [chars]: [chars] ([dec])
Explanation A warning condition occurred in IXP2800_SERVICE Driver which involves exiting the process.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-IXP2800_VFW-6-INFO [chars]
Explanation SERVICE card ixp2800_service driver informational message
Recommended Action NONE : Informational message only
Error Message%L2-IXP2800_VFW-7-LOG_FILE_ERROR ixp2800 service DLL failed to open log file [chars] ([chars])
Explanation The NPU service DLL failed to open the log file
Recommended Action None
JACKET Messages
Error Message%L2-JACKET-3-CRITICAL_ERROR [chars]: [chars]: [hex]
Explanation A critical error occurred in jacket driver which involves exiting the process. The jacket driver will restart and unless the same error occurs on the next attempt the driver will function normally. If the error is persistent, it indicates the system error or HW error which needs further investigation.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-JACKET-3-PIO_CRITICAL_ERROR Asic PIO failure : [chars], instance [dec]: rc [dec] cerr [chars] errno [dec] data1 [hex] data2 [hex]
Explanation A critical error occurred while accessing the hardware in jacket driver which involves exiting the process. The driver will restart and attempt normal functionality. If the error is transient, the jacket driver and the SPAs will continue normal operation. If the error is persistent, the jacket card hardware needs to be checked out for access failures.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-JACKET-3-RULES_CRITICAL_ERROR SPA subslot [dec]: FAILED: [chars] for [chars]
Explanation A critical error occurred in jacket driver rules validation for a SPA which results in the SPA not being enabled. This does not affect the other slots on the jacket card. Please check the SW support for the SPA slot for which this message is seen.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-JACKET-3-SPA_PIO_ERROR SPA subslot [dec]: had [chars] error when accessing address [hex]
Explanation This is an error message indicating a Hardware access error for a SPA. If this is a recurrent message, it usually is due to faulty hardware, loose connection at the SPA connector on the jacket card. Try reseating the SPA and see if the issue is resolved. If not, please check with TAC.
Recommended Action No action is required.
Error Message%L2-JACKET-6-EVENT_INFO SPA subslot [dec]: [chars] for [chars], driver [chars]
Explanation This is an informational message in the jacket driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-JACKET-6-INFO [chars]: [chars]
Explanation This is an informational message in the jacket driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-JACKET-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the jacket driver to indicate anomolies which are not critical. 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.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
JDAM Messages
Error Message%L2-JDAM-3-FATAL_ERROR Fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in JDAM Driver which involves exiting the PLIM 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-JDAM-6-INFO_MSG [chars] [chars] [dec]
Explanation This is a Informational message in the JDAM driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-JDAM-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the JDAM driver to indicate anomolies 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 temperory 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.
L2C Messages
Error Message%L2-L2C-3-ERR_MISCONFIG Misconfiguration: Item [chars] on interface [chars] is incompatible with other configuration. The system may now be in an inconsistant state.
Explanation The L2VPN Uberverifier has detected a misconfiguration. It was not detected in the verification phase, so the Uberverifier cannot correct this.
Recommended Action The misconfiguration can be corrected by deleting all configuration from the specified interface and its subinterfaces, and then reapplying the configuration. If the problem persists, do the following: Copy the error message exactly as it appears 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-L2C-4-WARN_EVENT Event loop error: [chars]
Explanation The L2VPN Uberverifier has encountered a problem in its event loop and cannot continue. In this situation it should restart.
Recommended Action The L2VPN Uberverifier should recover on restart. If the problem persists, do the following: Copy the error message exactly as it appears 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-L2C-4-WARN_INIT Failed to initialize [chars]: [chars]
Explanation The L2VPN Uberverifier process failed to initialize correctly. In this situation it restarts, but may not recover if there is a persistant error in the IOS-XR system and the L2VPN Uberverifier is later unable to reestablish its connections and initialize successfully.
Recommended Action The Uberverifier is not essential for system operation. However, if it is not running as intended, it may be possible for a misconfiguration to be allowed. If this persists, do the following: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
L2FIB_DEBUG Messages
Error Message%L2-L2FIB_DEBUG-3-ERR [chars]: [chars]
Explanation Some error occurred in operations related to Shared Memory area. The text of the message displays the failed operation and the related error code. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
L2FIB_LIB Messages
Error Message%L2-L2FIB_LIB-2-OOR L2FIB has run out of [chars] resource memory. No more updates will be handled by the L2FIB. Please delete ACs to resume normal operation on this node
Explanation The l2fib_mgr process on the node has detected an out of resource condition for the indicated resource. Normal operation cannot resume until routes are deleted.
Recommended Action Run show l2vpn forwarding resource command and check which resource(s) are running low on memory. Significant ACs will have to be deleted on the affected node to resume normal l2fib operation.
Error Message%L2-L2FIB_LIB-2-SHM_INIT L2FIB shared memory initialization failed: [chars]
Explanation Initialization of L2FIB failed. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB_LIB-3-MEM_ERR [chars] failed :[chars]
Explanation Some error occurred in Alloc/Chunk related memory operations. The text of the message displays the failed operation and the related memory construct. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB_LIB-3-SHM_ERR [chars] failed: [chars]
Explanation Some error occurred in operations related to Shared Memory area. The text of the message displays the failed operation and the related error code. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB_LIB-4-RSRC_LOW L2FIB running low on [chars] resource memory. L2FIB will now begin resource constrained forwarding. Only route deletes will be handled in this state, which may result in mismatch between L2VPN mgr/AIB/L2FIB and L2FIB. Traffic loss on certain ACs can be expected. The L2FIB will automatically resume normal operation, once the resource utilization returns to normal level
Explanation The l2fib_mgr process has detected that average utilization for specified resource has risen above a predefined high watermark value, and has entered resource contrained forwarding mode. In this mode, the l2fib will only handle route deletes which may potentially freeup some memory. Due to this operational mode, the L2VPN mgr/AIB/L2FIB and L2FIB will be out of sync. Once ACs are deleted and resource utilization level drops to acceptable levels again, l2fib will come out of this operational mode and resume normal operation.
Recommended Action Run show l2vpn forwarding resource command and check which resource(s) are running low on memory. Any action that reduces number of ACs will eventually result in the l2fib returning to normal operation after few seconds.
L2FIB_SHM Messages
Error Message%L2-L2FIB_SHM-2-DEBUG L2FIB debug init failed: [chars] ([chars])
Explanation Initialization of L2FIB failed. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB_SHM-2-INIT L2FIB initialization failed: [chars]
Explanation Initialization of L2FIB failed. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB_SHM-3-ERR [chars] failed: [chars]
Explanation Some error occurred in operations related to Shared Memory area. The text of the message displays the failed operation and the related error code. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
L2FIB Messages
Error Message%L2-L2FIB-2-INIT L2FIB initialization failure: [chars] [chars]
Explanation L2FIB initialization 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-L2FIB-2-INVALID_MSG L2FIB thread [chars] received an invalid message: [chars] [unsigned int]
Explanation L2FIB thread got an invalid message so it is exiting
Recommended Action Copy the error message exactly as it appears 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-L2FIB-2-SHM_INIT L2FIB shared memory initialization failed: [chars]
Explanation Initialization of L2FIB failed. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB-3-ADJ_INIT L2FIB initialization with the AIB failed [chars]: [chars]
Explanation An internal software error occurred that prevented the L2FIB from working with AIB.
Recommended Action Try restarting the l2fib process to see if the route gets programmed again. LC OIR can be tried as well.
Error Message%L2-L2FIB-3-MEM_ERR [chars] failed :[chars]
Explanation Some error occurred in Alloc/Chunk related memory operations. The text of the message displays the failed operation and the related memory construct. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB-3-PAK_ERR [chars] failed: [chars]
Explanation Some error occurred in Packet (IP/MPLS/ICMP) related operations. The text of the message displays the failed operation and the related error code. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB-3-SHM_ERR [chars] failed: [chars]
Explanation Some error occurred in operations related to Shared Memory area. The text of the message displays the failed operation and the related error code. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB-3-TIMER_ERR [chars] failed for '[chars]': [chars]
Explanation Some error occurred in Managed Timer related operations. The text of the message displays the failed operation and the related timer construct with error code. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB-3-WAVL_ERR [chars] failed (tree=[chars])
Explanation Some error occurred in WAVL operations The text of the message displays the failed operation and the related wavl tree. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB-3-WAVL_ERR_RC [chars] failed (tree=[chars]): [chars]
Explanation Some error occurred in WAVL operations The text of the message displays the failed operation and the related wavl tree with error code. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2FIB-6-GEN_INFO_CERR [chars]: [chars]
Explanation An internal software error 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.
L2TP Messages
Error Message%LAYER2-L2TP-2-INIT L2TP initialization failure: [chars] [chars]
Explanation L2TP initialization 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%LAYER2-L2TP-3-GEN_ERR L2TP internal error: [chars]
Explanation An internal software error 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%LAYER2-L2TP-3-IPC_ERR L2TP IPC transport error: [chars] [chars]
Explanation An IPC transport software error 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.
L2VPN_DEBUG Messages
Error Message%L2-L2VPN_DEBUG-3-ERR [chars]: [chars]
Explanation Debug and ltrace library initialization 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.
L2VPN_PW Messages
Error Message%L2-L2VPN_PW-3-UPDOWN Pseudowire with address [chars], id [unsigned long int], changed state to [chars]
Explanation The L2VPN Pseudowire went up or down
Recommended Action If the state change was unexpected, confirm the configuration settings for the cross-connect.
L2VPN Messages
Error Message%L2-L2VPN-2-CRIT_MEM_SHUT [chars] process shutting down due to 'Critical' memory state.
Explanation The system has notified a process that it is critically short of memory and the process is shutting down.
Recommended Action Copy the error message exactly as it appears 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-L2VPN-2-NO_MEM No memory for '[chars]'
Explanation The requested operation could not be accomplished because of a low memory 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-L2VPN-3-BAG_REG_ERR bag(s) registration failed: [chars]
Explanation Some error occured while trying to register edm bags. The text of the message displays the failed operation with error code.
Recommended Action Copy the error message exactly as it appears 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-L2VPN-3-EVENT_ERR [chars] failed: [chars]
Explanation Some error occured in event/event manager/event connection operations. The text of the message displays the failed operation with error code. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2VPN-3-GEN_ERR [chars] failed: [chars]
Explanation Some requested operation failed. The text of the message displays the failed operation with error code.
Recommended Action Copy the error message exactly as it appears 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-L2VPN-3-SYSDB_BIND_ERR sysdb_bind failed for '[chars]': [chars]
Explanation Some error occured in sysdb bind operation bind. The text of the message displays the failed operation for the bindpoint with error code.
Recommended Action Copy the error message exactly as it appears 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-L2VPN-3-SYSDB_ERR [chars] failed: [chars]
Explanation Some error occured in sysdb operation. The text of the message displays the failed operation with error code. The traceback can be used to get the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears 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-L2VPN-6-GEN_INFO [chars]
Explanation Some information for process status.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
LACP_lite Messages
Error Message%L2-LACP_lite-3-ERR_LL_DLL_ASYNC_SEND_FAIL Send async pulse to lacp lite process fails; Error [chars]
Explanation Attempt to send pulse to LACP lite process fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LACP_lite-3-ERR_LL_DLL_CHAN_CONNECT_FAIL Cannot connect to lacp lite process; Error [chars]
Explanation Attempt to connect to LACP lite process channel fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LACP_lite-3-ERR_SHMEM_MMAP_FAIL Cannot mmap file [chars]; Error [chars]
Explanation Attempt to mmap the shared memory fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LACP_lite-3-ERR_SHMEM_OPEN_FAIL Cannot open shmem file [chars]; Error [chars]
Explanation Attempt to open the shared memory fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LACP_lite-3-ERR_SHMEM_TRNC_FAIL Cannot truncate file [chars] to [dec] bytes; Error [chars]
Explanation Attempt to truncate the shared memory file fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LACP_lite-3-ERR_SHMEM_UNAVAILABLE LACP lite SHMEM can accommodate only [dec] records (request for [dec] records)
Explanation BM-Local has requested transfer of more interface records than shared memory can accommodate
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LACP_lite-3-ERR_UNSUPPORTED_FLAG LACP lite API is called with unsupportd flag (request for [dec])
Explanation BM-Local has called LACP lite API with unsupported flag
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
LC Messages
Error Message%L2-LC-0-TESTEMERG [chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
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.
LCGE Messages
Error Message%L2-LCGE-6-AUTONEG_STATE Interface [chars]: Link [chars]
Explanation Autonegotiation is either ok or not ok and link is either up or not.
Recommended Action If autonegptiation is not complete, check the other end for autonegotiation capabilities.
Error Message%L2-LCGE-6-GBIC_OIR GBIC [chars] for port [dec]
Explanation GBIC is removed/inserted for specified port.
Recommended Action Check GBIC and cable connections. Local RX cable must be connected to remote TX cable and vice versa. If this is printed during bootup or GBIC insertion it's ok.
Error Message%L2-LCGE-6-GBIC_TX_FAULT Interface [chars]: GBIC TX Fault [chars]
Explanation A GBIC TX Fault error was detected/fixed as specified in the message.
Recommended Action Check GBIC and cable connections. Local RX cable must be connected to remote TX cable and vice versa. If this is printed during bootup or GBIC insertion it's ok.
Error Message%L2-LCGE-6-IM_STATE_UPDATE im_state_update operation failed for interface [chars], error ([chars])
Explanation IM state update operation failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LCGE-6-LINE_STATE Interface [chars]: Line state [chars]
Explanation A GBIC line state error was detected/fixed as specified in the message.
Recommended Action Check GBIC and cable connections. Local RX cable must be connected to remote TX cable and vice versa.
Error Message%L2-LCGE-6-LINK_UPDOWN Interface [chars]: changed state to [chars]
Explanation Link state going up or down.
Recommended Action If state down, check physical link, GBIC and auto negotiation mode configuration on both sides .
Error Message%L2-LCGE-6-MTU_ERROR mtu operation [chars] failed for interface [chars], error [dec] ([chars])
Explanation IM mtu operation failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LCGE-6-NOT_HANDLED not handled condition on interface [chars] ([chars]:[dec]) [hex]
Explanation Condition unexpected or not handled.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LCGE-6-RX_LOS Interface [chars]: [chars] RX Loss of Signal
Explanation A GBIC RX loss of signal error was detected/fixed as specified in the message.
Recommended Action Check GBIC and cable connections. Local RX cable must be connected to remote TX cable and vice versa.
Error Message%L2-LCGE-6-SERVICE_ERROR service:[chars] [chars] ([chars]:[dec]), error [dec] ([chars])
Explanation Library service returned error status.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L2-LCGE-6-SH_CAM_ALLOC Failed to allocate shadow cam for slot [dec]
Explanation Failed to allocate a shadow CAM for the given slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-LCGE-6-SH_CAM_FULL Failed to add address %e to full [dec] entry shadow CAM
Explanation Failed to add an entry to the CAM MAC address filter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-LCGE-6-SYNC_LOSS Interface [chars]: [chars]
Explanation A GBIC loss of synchronization error was detected or is gone as specified in the message.
Recommended Action Check GBIC and cable connections. Local RX cable must be connected to remote TX cable and vice versa. Also check autonegotiation settings on both sides.
Error Message%L2-LCGE-6-UNKNOWN_LOOPBACK_ST Item [chars] is unknown state: [chars]
Explanation Loopback item in SysDB is neither internal nor external.
Recommended Action Copy the error message exactly as it appears on the console. 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-LCGE-6-UNSUP Interface ([chars]): unsupported feature: [chars]
Explanation This feature is not supported by GSR Gigabit Ethernet.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
LCPOS Messages
Error Message%L2-LCPOS-1-INITFAIL LCPOS([dec]/[dec]), initialization timeout failure
Explanation LC POS ASIC and framer initialization failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-LCPOS-3-BMAENG [chars] POS, [chars] [chars]%s. (src=[hex], det1=[hex], det2=[hex])
Explanation POS BMA engine hardware errors
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LCPOS-3-BMAPAR [chars] POS, [chars]. BMA_DATA[3:0]=[hex]. (src=[hex], det1=[hex], det2=[hex])
Explanation Parity error occurred on POS asic BMA engine
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LCPOS-3-ERROR [chars]
Explanation A POS driver error occured prior to debug service initialization
Recommended Action Copy the error message exactly as it appears 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-LCPOS-3-LINKBADEVT Unexpected event woke up LC POS link process.
Explanation LC POS link report process receives an unexpected event
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show subsys command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show subsys output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LCPOS-3-LINKNOPRC LCPOS, lcpos_add_process: Unable to create lcpos_link_report process
Explanation LC POS link report process can not be created
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show subsys command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show subsys output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LCPOS-3-LINKPROC LCPOS, lcpos_link_report process: Could not get argument
Explanation LC POS link report process stops working
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show subsys, show memory summary commands to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show subsys, show memory summary output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LCPOS-3-POSENG [chars] POS, [chars]. [chars], port [dec]. (src=[hex], det1=[hex], det2=[hex])
Explanation POS engine hardware errors
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LCPOS-3-RXPOSTO LCPOS([dec]/[dec]), RX POS engine shutdown failed
Explanation The software is trying to shutdown the Rx POS engine. POS engine refuses to shutdown, the software timeout
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, issue the execute-on slot (X) show controller pos registers command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the execute-on slot (X) show controller pos registers output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LCPOS-3-SOP [chars] SOP. (source=[hex], halt_minor0=[hex])
Explanation SOP hardware errors
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LCPOS-3-SRAMPAR [chars] POS, [chars]. [chars]=[hex][chars]. (src=[hex], det1=[hex], det2=[hex])
Explanation Parity error occurred on POS asic SRAM
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-LCPOS-3-TXPOSTO LCPOS([dec]/[dec]), TX POS engine shutdown failed
Explanation The software is trying to shutdown the Tx POS engine. POS engine refuses to shutdown, the software timeout
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot (X). If diagnostics pass, issue the execute-on slot (X) show controller pos registers command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the execute-on slot (X) show controller pos registers output, call your Cisco technical support representative and provide the representative with the gathered information.
LINK Messages
Error Message%L2-LINK-4-BERTSTATUS [chars] [chars]
Explanation The bert status of the link
Recommended Action None.
MAC_ACCOUNT Messages
Error Message%L2-MAC_ACCOUNT-4-OOR_WARNING Resource limit hit for MAC accounting entries on this port: [chars]
Explanation The resource limit for MAC accounting entries on this port has been reached, no more MAC accounting entries will be accounted for. This error message is displayed when one or more MAC accounting entries fails to be added as a result of this out of resource condition.
Recommended Action Clear the ARP cache for this interface/node to remove stale entries and repopulate MAC accounting. Use the MAC accounting show command to identify the number of available accounting entries on the port.
MARVEL Messages
Error Message%L2-MARVEL-3-CHAN_CREATE Failed to create channel : [chars]
Explanation Failed to create marvel-test (driver) channel using event_manager_create.
Recommended Action Copy the error message exactly as it appears 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-MARVEL-3-DEBUG_INIT Debug initialization failed
Explanation Initialization of the debug event 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-MARVEL-3-DEBUG_REG Debug registration failed : [chars]
Explanation debug_register() 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-MARVEL-3-EVENT_MGR_FAIL [chars] : [chars]
Explanation Generic failure of any event manager API.
Recommended Action Copy the error message exactly as it appears 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-MARVEL-3-MMAP Failed to map device address : [chars]
Explanation mmap() system call failed to map the device physical address.
Recommended Action Copy the error message exactly as it appears 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-MARVEL-3-MSG_REPLY Failed to send reply message : [chars]
Explanation This error is reported when msg_reply() (LWM call) fails.
Recommended Action Copy the error message exactly as it appears 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-MARVEL-3-NOMEM Failed to allocate memory
Explanation This error is reported when malloc()/calloc() type system call fails.
Recommended Action Copy the error message exactly as it appears 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-MARVEL-3-OPEN Failed to open file [chars] : [chars]
Explanation This error is generated when the open() system call fails.
Recommended Action Copy the error message exactly as it appears 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-MARVEL-6-RX_ASYNC_MSG Invalid asynchronous message received.
Explanation This error is generated when an invalid asynchronous message is received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
MFR_EA Messages
Error Message%L2-MFR_EA-2-DPC_CALL_FAILED MFR EA failed handling a DPC [chars]
Explanation Internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MFR_EA-2-INTERNAL_ERR [chars]
Explanation Internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MFR_EA-3-AIB_INIT_FAILED Failed during AIB initialization, err: [chars]
Explanation The MFR EA process initialization failed whilst trying to connect to AIB.
Recommended Action Copy the error message exactly as it appears 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-MFR_EA-3-INTERFACE_OPERATION_FAILED Interface [chars] operation failed for index [dec]
Explanation The MFR EA process failed whilst trying to change interface state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MFR_EA-3-MALLOC Memory allocation failed: [chars]
Explanation A call to malloc failed.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MFR_EA-3-MEMBER_AIB_REMOVE_FAILED Failed during AIB remove, err: [chars]
Explanation The MFR EA process failed whilst trying to remove entry from AIB.
Recommended Action Copy the error message exactly as it appears 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-MFR_EA-3-MEMBER_AIB_SET_FAILED Failed during AIB set , err: [chars]
Explanation The MFR EA process failed whilst trying to insert entry to AIB.
Recommended Action Copy the error message exactly as it appears 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-MFR_EA-3-MEMBER_CAPS_ADD_FAILED Failed during caps set, err: [chars]
Explanation The MFR EA process failed whilst trying to set 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-MFR_EA-3-MEMBER_CAPS_REMOVE_FAILED Failed during caps remove, err: [chars]
Explanation The MFR EA process failed whilst trying to remove 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-MFR_EA-3-MEMBER_ENCAP_REMOVE_FAILED Failed during encaps remove, err: [chars]
Explanation The MFR EA process failed whilst trying to remove encaps.
Recommended Action Copy the error message exactly as it appears 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-MFR_EA-3-MEMBER_ENCAP_SET_FAILED Failed during encaps set, err: [chars]
Explanation The MFR EA process failed whilst trying to set encaps.
Recommended Action Copy the error message exactly as it appears 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-MFR_EA-3-NO_STATS Failed to initialize MFR interface stats collection, err: [chars]
Explanation The MFR EA interface stats collection initialization 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-MFR_EA-3-STATE_CHANGE_FAILED Failed during interface state change, err: [chars]
Explanation The MFR EA process failed whilst trying to change interface state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
MFR_MA Messages
Error Message%L2-MFR_MA-2-FAIL MFR MA failed to [chars]. Thread id is [dec]. [chars]
Explanation During process start up an unrecoverable error occurred. The component will exit and should be restarted by the System Manager.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MFR_MA-3-DPC_ERROR [chars] [hex] [chars]
Explanation An error occurred during an operation.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MFR_MA-3-ENCAP Unable to process mfr encapsulation request
Explanation An error occurred processing a request to set mfr encapsulation on an interface.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MFR_MA-3-ERR_MEMBER_ADD Cannot add [chars] to bundle with nodeid [hex] and group [dec]
Explanation Could not find the bundle interface with the nodeid and group. Hence cannot add the member interface to bundle.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MFR_MA-3-ERR_MUTEX_LOCK Mutex lock failed. [chars]
Explanation Locking the mutex governing the access to MFR MA IDB database failed.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MFR_MA-3-ERR_PULSE Received unexpected Async Event [hex] for ifhandle [hex]
Explanation IPC thread received an async event pulse for which there is no handler.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MFR_MA-3-ERROR [chars] [chars]
Explanation An error occurred during an operation.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MFR_MA-3-MALLOC Memory allocation failed: [chars]
Explanation A call to malloc failed.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MFR_MA-3-RECVFROM An error occurred receiving a packet: [chars]
Explanation The socket call recvfrom returned an error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MFR_MA-3-SENDTO An error occurred sending a packet: [chars]
Explanation The socket call sendto returned an error.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MFR_MA-3-THREAD_ERROR [chars] . Thread id is [dec]. [chars]
Explanation An error occurred during an operation.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MFR_MA-4-ERR_EVC_ERROR Error resetting '[chars]' connection: [chars]
Explanation After detecting an error with the connection to the specified service, MFR MA failed to reset that connection. This is an internal error. It requires a restart of the process for recovery.
Recommended Action Copy the error message exactly as it appears 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-MFR_MA-4-ERR_MEM_ALLOC Failed to allocate [unsigned int] bytes for '[chars]'
Explanation The process failed to allocate memory for the specified resource.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-MFR_MA-4-ERR_MGD_TIMER Unexpected error encountered whilst [chars]: [chars]
Explanation MFR MA encountered an unexpected error using the Managed Timer library. This is most likely due to a low memory condition but may also be an internal programming error. The error message should provide more information about the cause.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Consider restarting the MFR MA process. *RECUR*.
Error Message%L2-MFR_MA-4-ERR_THREAD_CREATE Failed to create '[chars]' thread: [chars]
Explanation MFR MA encountered an unexpected error creating a new thread. The process will restart to attempt to recover. This is possibly due to a low memory condition but may also be an internal programming error. The error message should provide more information about the cause.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.
METRO_STATS Messages
Error Message%L2-METRO_STATS-7-ERR_INIT [chars]: [chars]
Explanation These errors are encountered at mstats process initialization time. The types of errors are: 1 Unable to determine hardware version. 2 Unable to create event manager. This will prevent stats process from receiving events. 3 Unable to create timer. 4 Unable to initialize client database. This will result in clients not being able to register with stats server to collect stats. 5 Unable to allocate Ingress/Egress stats. This will result in Stats manager not being able to maintain/update any hardware stats. 6 Unable to register with debug. This will prevent stats process from logging debug messages. 7 Unable to initialize or register with checkpoint service. This will prevent stats manager from restoring the information required at restart. 8 Unable to connect with SYSDB. This includes failure to connect, bind, register with SYSDB. 9 Unable to Initialize hardware packet service.
Recommended Action No action is required. Process will be restarted. If the message recurs, copy the error message exactly as it appears 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-METRO_STATS-7-ERR_MEM Memory error: [chars]: [chars]
Explanation An error occurred in Hardware Stats Manager during shared memory operations. This may be because the system is running low on memory. The types of errors are: 1 Cannot open/reset/close shared memory window 2 Cannot allocate/free shared memory. This will cause Stats Server to not be able to have a shadow copy of stats for all clients.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
METRO_STATS_API Messages
Error Message%L2-METRO_STATS_API-7-DEBUG_MSG Debug Msg : [chars]: [chars]
Explanation This is a debug message in the Hardware Stats Manager Library to indicate anomalies. In most cases these messages will stop once the temporary condition is resolved. Examples of when this error occurs are: 1. The client connection handle received is NULL 2. The arguments to the bind message are incorrect 3. Unable to bind to the hardware IPC driver 4. Error while trying to initialize debug event. 5. Not enough memory to bind to the client
Recommended Action No action is required. These are Debug messages. An error was returned by Stats Manager APIs to applications. Applications receiving this error will report the error.
Error Message%L2-METRO_STATS_API-7-ERR_DLL_INIT DLL INIT : [chars]: [chars]
Explanation This error indicates that there was an error while initializing the stats dll.
Recommended Action No action is required. The process is restarted automatically.
Error Message%L2-METRO_STATS_API-7-ERR_THREAD Locking issues: [chars]: [chars]
Explanation This error indicates that the Hardware Stats Manager Library is unable to initialize/destroy locking for client's attributes and tables.
Recommended Action An error was returned by Stats Manager APIs to applications. Applications receiving this error will report it. Take recommended actions specified in the application's error 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.
METRO_UIDB Messages
Error Message%L2-METRO_UIDB-7-ERR_INIT [chars] failed due to [chars]
Explanation Initialization of uidb_svr process has failed due to one of the following reasons: 1) Failed to create server context. 2) Failed to get schedular parameters. 3) Failed to initialize event manager. This would prevent process from receiving events. 4) Failed to register with debug. This would prevent process from logging debug messages. 5) Failed to bind UIDB server with MIPC server. This is needed to program features in hardware. 6) Failed to connect to PLIM asic processes. This is needed to program features in hardware. 7) Failed to initialize checkpoint. This is needed to checkpoint UIDB data to restore on process restart. 8) Failed to allocate, initialize and checkpoint shadow memory. This is needed to store and restore UIDB internal data. 9) Failed to get metro asic version. 10) Failed to attach event handlers needed to handle LWM messages. This is needed to enable/disable various features in hardware. 11) Various Sysdb or EDM failures 12) event_block failed. This indicates process has encountered unexpected error while waiting for events.
Recommended Action No action is required. Process will be restarted. If not recovered, it's a fatal condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
MICKEY Messages
Error Message%L2-MICKEY-2-INTR Mickey Intr: [chars]: [dec]: [dec]
Explanation A high severity error has interrupted the Mickey FPGA. This might result in the PLIM being reset.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MICKEY-3-SERDES_CTRL Mickey Serdes Ctrl: [chars]: [dec]: [dec]: [dec]
Explanation This message indicates that the software tried to configure an unsupported loopback type.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MICKEY-5-UNKNOWN_INTR Mickey Intr: [chars]: [dec]: [dec]
Explanation This message indicates the Mickey FPGA has detected an unknown interrupt.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
MLCTRLR Messages
Error Message%L2-MLCTRLR-2-NOMEM [chars]([dec]): not enough memory for [chars]
Explanation The process is out of memory.
Recommended Action Check process list for source of memory loss. Check if h/w memory requirements are met.
Error Message%L2-MLCTRLR-3-ERROR [chars]([dec]): [chars] failed ([chars]) - [chars]
Explanation A general failure occured while executing the function in question. The message contains info about the location and cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of MLCTRLR.
Error Message%L2-MLCTRLR-4-ALARM [chars]: [chars] [chars]
Explanation The specified MLCTRLR Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
Error Message%L2-MLCTRLR-4-FEAC [chars] [chars]
Explanation New Far End Alarm Code received.
Recommended Action None.
Error Message%L2-MLCTRLR-4-LOOPSTATUS [chars] [chars]
Explanation A configurable controller loopback status.
Recommended Action None.
Error Message%L2-MLCTRLR-4-UPDOWN [chars]: [chars] [chars]
Explanation The specified MLCTRLR is operationally down due to alarm. Check alarm status using show controller Mlt command on the cli.
Recommended Action Recommended action is to repair the source of the alarm.
Error Message%L2-MLCTRLR-4-WARNING [chars]([dec]): [chars] - [chars]
Explanation A non-fatal error occured while executing the function in question. The message contains info about the location and cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of MLCTRLR.
MOUSE Messages
Error Message%L2-MOUSE-2-INTR Mouse Intr: [chars]: [dec]: [dec]
Explanation A high severity error has interrupted the Mouse FPGA. This might result in the PLIM being reset.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MOUSE-5-UNKNOWN_INTR Mouse Intr: [chars]: [dec]: [dec]
Explanation This message indicates the Mouse FPGA has detected an unknown interrupt.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
MOTHRA Messages
Error Message%L2-MOTHRA-3-FATAL_ERROR Fatal error: [chars]: [chars]: [hex]
Explanation A fatal error occurred in mothra 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-MOTHRA-3-PIO_FATAL_ERROR Asic PIO failure : [chars], instance [dec]: rc [dec] cerr [chars] errno [dec] data1 [hex] data2 [hex]
Explanation A fatal error occurred in Santa 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-MOTHRA-6-INFO_MSG Info: [chars]: [chars]
Explanation This is a Informational message in the mothra driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-MOTHRA-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the mothra driver to indicate anomolies 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 temperory 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.
MPLSCP Messages
Error Message%L2-MPLSCP-1-ERR_ADJ_DELETE Failed to remove [chars] from adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MPLSCP-1-ERR_ADJ_UPDATE Failed to add [chars] into adjacency; [chars]
Explanation An error was encountered while connecting to the AIB.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MPLSCP-3-DEBUG_ASSOC Conditional debug association failed; [chars]
Explanation An error has occurred upon attempting to associate conditional debugging with PPP debug commands. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-3-DEBUG_COND_REGISTER Conditional debug registration failed; [chars]
Explanation An error has occurred upon attempting to register for conditional debugs. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-3-DEBUG_REGISTER Debug registration failed; [chars]
Explanation An error has occurred upon attempting to connect to the debug server. This may cause debug messages to not appear.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-3-ERR_CONN Connection [chars] failed for [chars]; [chars]
Explanation An failure in the reconnection software in the 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-MPLSCP-3-ERR_EVENT Failed to [chars] [chars] event; [chars]
Explanation An event handler has returned an 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-MPLSCP-3-ERR_EVENT_MGR_CREATE MPLSCP Failed to initialize event manager; [chars]
Explanation Initialization of the event manager 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-MPLSCP-3-ERR_IM_STATE Failed to get basecaps state for [chars]; [chars]
Explanation MPLSCP was unable to determine the state of the basecaps and has assumed it to be down. MPLSCP will remain closed until the interface is brought down and up again.
Recommended Action Shut the interface and then bring it up again.
Error Message%L2-MPLSCP-3-ERR_MBOX_ADD [chars] [chars] failed to add [chars]; [chars]
Explanation An attribute has failed to be added to the message which was being constructed which has caused the message to be discarded.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MPLSCP-3-ERR_MBOX_CREATE [chars] failed to create [chars]; [chars]
Explanation An attempt to allocate a message failed. This may be due to lack of resources.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MPLSCP-3-ERR_MBOX_INIT Failed to init [chars] message for [chars]; [chars]
Explanation The initialization of a message failed, this results in a failure to communicate with the Link Control Protocol.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-3-ERR_MBOX_SEND [chars] failed to send [chars]; [chars]
Explanation A message failed in a send attempt to a particular mailbox.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MPLSCP-3-ERR_MQ_OPEN Failed to open message queue [chars]; [chars]
Explanation MPLSCP has failed to open a mailbox channel.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-3-ERR_NETIO_RXQ Failed to support [chars] [chars]; [chars]
Explanation MPLSCP has attempted to update the data component with the current status of the control protocol. The attempt has failed which will has the effect of leaving the data component with the previous set of information. This may result in an inability to negotiate MPLSCP.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-MPLSCP-3-ERR_SYSDB SysDB [chars] failed; [chars]
Explanation MPLSCP cannot perform some SysDB operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MPLSCP-3-ERR_SYSDB_NOTIFICATION Failed to [chars]register for SysDB notification of [chars]; [chars]
Explanation MPLSCP cannot (un)register for SysDB notification.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-3-ERR_TIMER [chars] [chars] timer [chars]
Explanation The manipulation of a timer had an abnormal side effect.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-3-LTRACE_INIT MPLSCP Failed to initialize the ltrace buffer; [chars]
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-MPLSCP-4-ERR_EVENT_WAIT Error waiting for event; [chars]
Explanation The event loop has received a message of a type it does not recognize. All events should be received by handlers.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-4-ERR_INTERFACE_NULL [chars]: Interface NULL
Explanation A function was called with a NULL interface pointer.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-4-ERR_MEMORY Insufficient memory for [chars]
Explanation MPSLCP failed to allocate memory for a 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-MPLSCP-4-ERR_MQ_RECEIVE Error receiving from message queue; [chars]
Explanation MPLSCP has failed to receive a message from its mailbox.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-4-ERR_NO_INTERFACE Interface [chars] not found
Explanation A SysDB name lookup 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-MPLSCP-4-ERR_NO_INTERFACE_STRUCT Structure for interface [chars] not created; [chars]
Explanation MPLSCP failed to create an interface structure.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-6-ERR_IM_CONNECT Failed to [chars]bind [chars] IM; [chars]
Explanation MPLSCP has failed to either bind to or unbind from the interface manager server.
Recommended Action No action is required.
Error Message%L2-MPLSCP-6-ERR_IM_ENCAPS Failed to [chars] [chars] encapsulation; [chars]
Explanation MPLSCP has failed an encapsulation operation with the interface manager.
Recommended Action Copy the error message exactly as it appears 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-MPLSCP-6-ERR_IM_EVENT Failed to [chars] event; [chars]
Explanation MPLSCP has failed to either initialize or specify an event with the interface manager server.
Recommended Action No action is required.
Error Message%L2-MPLSCP-6-ERR_IM_PROTO Failed to [chars] [chars] protocol; [chars]
Explanation MPLSCP has failed a protocol operation with the interface manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
MULTILINK_UV Messages
Error Message%L2-MULTILINK_UV-3-ERR_MISCONFIG Misconfiguration: Item [chars] on interface [chars] is incompatible with other configuration. The system may now be in an inconsistant state.
Explanation The Multilink Uberverifier has detected a misconfiguration. It was not detected in the verification phase, so the Uberverifier cannot correct this.
Recommended Action The misconfiguration can be corrected by deleting all configuration from the specified interface and its subinterfaces, and then reapplying the configuration. If the problem persists, do the following: Copy the error message exactly as it appears 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-MULTILINK_UV-3-EVENT Unrecoverable error in event loop. Error: [chars]
Explanation An error (other than EINTR) occured in the event loop. The process must exit.
Recommended Action Identify the location of the card where there error was reported. Copy the error message exactly as it appears on the console or in the system log. Issue the show memory location summary command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show memory location summary output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MULTILINK_UV-3-INIT Failure during initialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the process. This resulted in the restart of 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-MULTILINK_UV-3-SYSMGR Failure communicating readiness to System Manager. Error: [chars]
Explanation The process was initialized successfully but was unable to inform System Manager of the success.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Multilink Messages
Error Message%L2-Multilink-3-MTU_IMPOSE_FAILED Failed to set MTU of [unsigned int] on [chars]
Explanation The specified MTU could not be applied on this interface.
Recommended Action No action is required.
Error Message%L2-Multilink-4-ALARM [chars]: [chars] [chars]
Explanation The specified Multilink Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
ND Messages
Error Message%L2-ND-3-INIT Process initialisation failed. [chars]: [chars] ([hex])
Explanation There was a software error during process startup.
Recommended Action The process will restart and try to recover. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise, check whether the error code contained in the message indicates that there was a failure to allocate the necessary memory and take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If resource allocation was not the problem and it hasn't been fixed by a subsequent restart, then take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. If the process does not restart automatically, restart it manually. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
OC768_FRAMER_ASIC Messages
Error Message%L2-OC768_FRAMER_ASIC-3-CRITICAL_ERROR [chars]: [chars]: [hex]
Explanation OC768 Framer ASIC Driver encountered a critical error which causes the process to exit.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-OC768_FRAMER_ASIC-6-INFO [chars]: [chars]
Explanation This is a informational message from OC768 Framer ASIC driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-OC768_FRAMER_ASIC-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in OC768 Framer ASIC driver to indicate anomolies 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 temperory 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.
OPTICS Messages
Error Message%L2-OPTICS-3-CRITICAL_ERROR Optical init failure: [chars]: [chars]: [hex]
Explanation A critical error occurred in OPTICS Driver which involves exiting the process.
Recommended Action Power cycle the plim.
Error Message%L2-OPTICS-6-INFO Info: [chars]: [chars]
Explanation This is an informational message in the OPTICS driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-OPTICS-7-DEBUG_MSG Debug: [chars]: [chars] value [dec]
Explanation This is a debug message in the optics driver to indicate anomolies 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 temperory 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.
OSICP Messages
Error Message%L2-OSICP-3-DEBUG_ASSOC Conditional debug association failed; [chars]
Explanation An error has occurred upon attempting to associate conditional debugging with PPP debug commands. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
Recommended Action Copy the error message exactly as it appears 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-OSICP-3-DEBUG_COND_REGISTER Conditional debug registration failed; [chars]
Explanation An error has occurred upon attempting to register for conditional debugs. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.
Recommended Action Copy the error message exactly as it appears 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-OSICP-3-DEBUG_REGISTER Debug registration failed; [chars]
Explanation An error has occurred upon attempting to connect to the debug server. This may cause debug messages to not appear.
Recommended Action Copy the error message exactly as it appears 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-OSICP-3-ERR_CONN Connection [chars] failed for [chars]; [chars]
Explanation An failure in the reconnection software in the 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-OSICP-3-ERR_EVENT Failed to [chars] [chars] event; [chars]
Explanation An event handler has returned an 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-OSICP-3-ERR_EVENT_MGR_CREATE OSICP Failed to initialize event manager; [chars]
Explanation Initialization of the event manager 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-OSICP-3-ERR_IM_STATE Failed to get basecaps state for [chars]; [chars]
Explanation OSICP was unable to determine the state of the basecaps and has assumed it to be down. OSICP will remain closed until the interface is brought down and up again.
Recommended Action Shut the interface and then bring it up again.
Error Message%L2-OSICP-3-ERR_MBOX_ADD [chars] [chars] failed to add [chars]; [chars]
Explanation An attribute has failed to be added to the message which was being constructed which has caused the message to be discarded.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-OSICP-3-ERR_MBOX_CREATE [chars] failed to create [chars]; [chars]
Explanation An attempt to allocate a message failed. This may be due to lack of resources.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-OSICP-3-ERR_MBOX_INIT Failed to init [chars] message for [chars]; [chars]
Explanation The initialization of a message failed, this results in a failure to communicate with the Link Control Protocol.
Recommended Action Copy the error message exactly as it appears 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-OSICP-3-ERR_MBOX_SEND [chars] failed to send [chars]; [chars]
Explanation A message failed in a send attempt to a particular mailbox.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-OSICP-3-ERR_MQ_OPEN Failed to open message queue [chars]; [chars]
Explanation OSICP has failed to open a mailbox channel.
Recommended Action Copy the error message exactly as it appears 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-OSICP-3-ERR_NETIO_RXQ Failed to support [chars] [chars]; [chars]
Explanation OSICP has attempted to update the data component with the current status of the control protocol. The attempt has failed which will has the effect of leaving the data component with the previous set of information. This may result in an inability to negotiate OSICP.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-OSICP-3-ERR_SYSDB SysDB [chars] failed; [chars]
Explanation OSICP cannot perform some SysDB operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-OSICP-3-ERR_SYSDB_NOTIFICATION Failed to [chars]register for SysDB notification of [chars]; [chars]
Explanation OSICP cannot (un)register for SysDB notification.
Recommended Action Copy the error message exactly as it appears 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-OSICP-3-ERR_TIMER [chars] [chars] timer [chars]
Explanation The manipulation of a timer had an abnormal side effect.
Recommended Action Copy the error message exactly as it appears 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-OSICP-3-LTRACE_INIT OSICP Failed to initialize the ltrace buffer; [chars]
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-OSICP-4-ERR_EVENT_WAIT Error waiting for event; [chars]
Explanation The event loop has received a message of a type it does not recognize. All events should be received by handlers.
Recommended Action Copy the error message exactly as it appears 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-OSICP-4-ERR_INTERFACE_NULL [chars]: Interface NULL
Explanation A function was called with a NULL interface pointer.
Recommended Action Copy the error message exactly as it appears 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-OSICP-4-ERR_MEMORY Insufficient memory for [chars]
Explanation OSICP failed to allocate memory for a 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-OSICP-4-ERR_MQ_RECEIVE Error receiving from message queue; [chars]
Explanation OSICP has failed to receive a message from its mailbox.
Recommended Action Copy the error message exactly as it appears 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-OSICP-4-ERR_NO_INTERFACE Interface [chars] not found
Explanation A SysDB name lookup 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-OSICP-4-ERR_NO_INTERFACE_STRUCT Structure for interface [chars] not created; [chars]
Explanation OSICP failed to create an interface structure.
Recommended Action Copy the error message exactly as it appears 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-OSICP-6-ERR_IM_CONNECT Failed to [chars]bind [chars] IM; [chars]
Explanation OSICP has failed to either bind to or unbind from the interface manager server.
Recommended Action No action is required.
Error Message%L2-OSICP-6-ERR_IM_ENCAPS Failed to [chars] [chars] encapsulation; [chars]
Explanation OSICP has failed an encapsulation operation with the interface manager.
Recommended Action Copy the error message exactly as it appears 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-OSICP-6-ERR_IM_EVENT Failed to [chars] event; [chars]
Explanation OSICP has failed to either initialize or specify an event with the interface manager server.
Recommended Action No action is required.
Error Message%L2-OSICP-6-ERR_IM_PROTO Failed to [chars] [chars] protocol; [chars]
Explanation OSICP has failed a protocol operation with the interface manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PFILTER_EA Messages
Error Message%L2-PFILTER_EA-3-ERR_IM_CAPS [chars] acl failed on interface . [chars]
Explanation 1) An ACL could not be applied to hardware because of one of the following reasons: a) TCAM max limit has been reached. b) RLB resources are not available. c) IPv6 address compression table is full. This error can happen when a new bundle member is added and the ACL can not be programmed successfully. 2) An ACL could not be removed from hardware.
Recommended Action 1) When this error occurs the running-config will not be in sync with line card configuration. It is recommended that the bundle member on which the error occured be removed from the bundle. The ACL configuration may also be reduced until it can be successfully programmed on the new bundle member. 2) If the ACL could not be removed from hardware a line card reload is recommended.
Error Message%L2-PFILTER_EA-7-INIT [chars] failed due to [chars]
Explanation Initialization of packet filter process has failed due to one of the following reasons: 1) Failed to initialize event manager. This would prevent process from receiving events. 2) Failed to register with debug. This would prevent process from logging debug messages. 3) Failure to connect with SYSDB. 4) Failed initialize internal permit/deny entries for IPv4/IPv6. These entries are needed for programming/removal of hardware entries for IPv4/IPv6 security ACLs. 5) Failed to initialize connection with interface manager proxy service. 6) Failed to initialize RLB (range logic block) checkpoint. This is needed for checkpointing range logic block information for restore on process restart. 7) Failed to initialize Feature EA DLL API needed for programming of hardware resources. 8) Failed to initialize callback function from Feature EA DLL for compiling IPv4/IPv6 TCAM entries needed for security ACL programming in hardeare. 9) Failed to initialize callback function from Feature EA DLL to handle reprogramming of RLB and IPv6 source prefix compression table request from TCAM manager. 10) Failed to initialize feature checkpoint info. This is needed for checkpointing IPv4 and IPv6 security ACLs programmed in hardware. 11) Failed to initialize callback functions from ACL configuration manager to perform hardware resource checks and ACE resequencing. 12) event_block failed. This indicates process has encountered unexpected error while waiting for events. 13) Failed to initialize callback functions for receiving incremental updates for IPv4/IPv6 security ACL configuration.
Recommended Action No action is required. Process will be restarted. If not recovered, it's a fatal condition. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*
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.
PLAOC768_API Messages
Error Message%L2-PLAOC768_API-3-CRITICAL_ERROR [chars]: [chars]: [hex]
Explanation PLAOC768 system checkout Library encountered a critical error 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-PLAOC768_API-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message from the PLAOC768 system checkout Library to indicate either anomolies 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.
PLAOC768 Messages
Error Message%L2-PLAOC768-3-ASIC_ERROR [chars] : block [dec] error [dec], [chars]
Explanation An ASIC error occurred in PLAOC768 ASIC which is reported here.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PLAOC768-3-CRITICAL_ERROR [chars]: [chars]: [dec]
Explanation PLAOC768 Driver encountered an critical error condition 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-PLAOC768-3-PIO_CRITICAL_ERROR Asic PIO failure : [chars], instance [dec]: rc [dec] cerr [chars] errno [dec] data1 [hex] data2 [hex]
Explanation A critical error occurred in PLAOC768 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-PLAOC768-6-INFO [chars]: [chars]
Explanation This is a informational message in the PLAOC768 driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-PLAOC768-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message from the PLAOC768 driver to indicate anomolies 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 temperory 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.
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_4P_OC192 Messages
Error Message%L2-PLIM_4P_OC192-3-DEVICE_INTR_CLEAR No Framer/RAC devices are generating excessive interrupts
Explanation The previously reported excessive interrupts condition has been cleared. Interrupt rate limiting has been disabled.
Recommended Action none
Error Message%L2-PLIM_4P_OC192-3-DEVICE_INTR_DISABLE Excessive interrupts from the [chars] device of port [hex]
Explanation The specified device is generating excessive interrupts. This message indicates that we are rate limiting the interrupt coming from this device. This indicates a potential HW issue, traffic forwarding (protection switching) may be impacted.
Recommended Action Check the fiber or the peer connection. If the problem persist after checking fiber and peer router, please contact support.
Error Message%L2-PLIM_4P_OC192-3-ERR [chars]
Explanation fail to init debug service event manager fails to provide its service
Recommended Action sysmgr will respawn plim_4p_oc192 'show logging' to look for the errors from event manager
Error Message%L2-PLIM_4P_OC192-3-MEM_ERR [chars]
Explanation fail to allocate memory.
Recommended Action sysmgr would restart the process. show process memory to find out whehter there is potential memory leak show memory to confirm system memory goes low
PLIM_ASIC Messages
Error Message%L2-PLIM_ASIC-3-HW_ERR plaspa instance [dec] [chars], [chars]
Explanation Plim Asic errors. Typically these indicate errors detected by the ASIC. Too many of these errors might indicate problem with the board, and can trigger a reload of the LC.
Recommended Action Check whether process 'bambi_server' is up and running. Check if the linecard reported any other errors and/or traffic loss was observed. If the message recurs, copy the error message exactly as it appears 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_ASIC-3-LTRACE_INIT Ltrace init for file [chars] failed [chars]
Explanation --
Recommended Action Typcially these indicate that ltrace is out of service. check at other processes using ltrace and see whether the problem happens to them.
Error Message%L2-PLIM_ASIC-7-ERR [chars]
Explanation Plim asic driver errors. Typically these errors indicate failure in system services or bad programming of the hardware.
Recommended Action No action is required.
PLIM_FPGA Messages
Error Message%L2-PLIM_FPGA-3-CRITICAL_ERROR [chars]: [chars]: [hex]
Explanation PLIM FPGA ASIC Driver encountered a critical error as described in the error message. This error causes PLIM OC768 process to exit.
Recommended Action If the message recurs, copy the error message exactly as it appears 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_FPGA-3-PIO_CRITICAL_ERROR Asic PIO failure : [chars], instance [dec]: rc [dec] cerr [chars] errno [dec] data1 [hex] data2 [hex]
Explanation A critical error occurred in PLIM FPGA 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-PLIM_FPGA-6-INFO [chars]: [chars]
Explanation This is a informational message from PLIM FPGA driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-PLIM_FPGA-7-DEBUG_MSG Debug: [chars]: [chars] value [dec]
Explanation This is a debug message in PLIM FPGA driver to indicate anomolies 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 temperory 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.
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_LIB Messages
Error Message%L2-PLIM_LIB-3-ERROR error: [chars]: [chars]: [hex]
Explanation A fatal error occurred in the plim library driver which involves exiting the process.
Recommended Action collect the info from 'show diag', 'show hfr', 'show inv' If the message recurs, copy the error message exactly as it appears 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_LIB-7-DEBUG [chars]: [chars] errno [dec]
Explanation This is a debug message in the PLIM library driver to indicate anomolies 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 temperory situation is resolved.
Explanation 'show logging' to confirm sysdb errors
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.
PLIM_OC768 Messages
Error Message%L2-PLIM_OC768-3-CRITICAL_ERROR [chars]: [chars]: [hex]
Explanation PLIM OC768 driver encountered a critical error as described in the error message. This error causes PLIM OC768 process to exit.
Recommended Action If the message recurs, copy the error message exactly as it appears 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_OC768-6-INFO [chars]: [chars]
Explanation This is an informational message from PLIM OC768 driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-PLIM_OC768-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the plim_oc768 driver to indicate anomolies 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 temperory 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.
PLIM Messages
Error Message%L2-PLIM-3-HW_ERR asic error: [chars]
Explanation Plim Asic errors. Typically these indicate errors detected by the ASIC. Too many of these errors might indicate problem with the board, and can trigger a reload of the LC.
Recommended Action Check whether process 'pla_server' is up and running. Check if the linecard reported any other errors and/or traffic loss was observed. If the message recurs, copy the error message exactly as it appears 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-3-MEM_ERR [chars]
Explanation fail to allocate memory.
Recommended Action show process memory to find out whehter there is potential memory leak show memory to confirm system memory goes low
Error Message%L2-PLIM-3-SQUID_ERR [chars]
Explanation squid fails to find the device
Recommended Action 1. reseat the plim. 2. if the problem is still there after reseating, run diag on the plim
Error Message%L2-PLIM-7-ERR [chars]
Explanation fail to init debug events; sysdb fails to provide services; event mgr fails to provides its services;
Recommended Action pla_server would be restarted by sysmgr. check out whether there is any problems with sysdb check out whether there is any problems with the event mgr there should be error msgs from sysdb or event msg. 'show logging' could confirm this
Error Message%L2-PLIM-7-LTRACE_ERR [chars] : [chars]
Explanation failed to inititialize ltrace events;
Recommended Action check out whether there is any problems with ltrace subsytem
pm5315 Messages
Error Message%L2-pm5315-3-FATAL_ERROR Fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in karachi 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-pm5315-6-INFO_MSG Info: [chars]: [chars]
Explanation This is a Informational message in the karachi driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-pm5315-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the karachi driver to indicate anomolies 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 temperory 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.
pm5316 Messages
Error Message%L2-pm5316-3-FATAL_ERROR [chars](): fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in plim 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-pm5316-4-WARNING [chars](): warning: [chars]: [chars]: [dec]
Explanation A warning condition occurred in plim Driver which involves exiting the process.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
PMSAR Messages
Error Message%L2-PMSAR-2-CFG_ERR : [chars]: [dec]
Explanation A fatal error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-2-CHAN_STATS_ERR [chars]() [dec], chan:[dec],[dec],[dec]; cid:[dec], sar:[dec] reason:[chars] status:[dec], ack:[hex], [hex], [hex], [hex]
Explanation A fatal error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-2-CLOSE_VC_COSQ_ERR [chars]() [dec], close cosq failure. rsar:[dec], ssar:[dec], queue:[dec], cosq_id:[dec] reason:[chars]; status:[dec] ack:[hex], [hex], [hex], [hex]
Explanation A fatal error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-2-CLOSE_VC_ERR [chars]() [dec], close vc failure. rsar:[dec], ssar:[dec], vpi:[dec], vci:[dec] reason:[chars]; status:[dec] ack:[hex], [hex], [hex], [hex]
Explanation A fatal error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-2-CMD_ACK_ERR [chars]() [dec], SAR:[dec] poll incomplete cmd ack, [chars]
Explanation A fatal error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-2-CMD_ERR [chars]
Explanation A critical PM622 TSP command failed that expected to succeed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PMSAR-2-CMD_POLL_TIMEOUT [chars]() [dec], SAR:[dec] cmd poll timed out, [chars]
Explanation A fatal error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-2-CMD_POST_ERR [chars]() [dec], SAR:[dec] post cmd failure. status:[dec], [chars] [dec] ack:[hex], [hex], [hex], [hex]
Explanation A fatal error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-2-INITERR Fatal error: [chars]: [hex]
Explanation SAR device cx27470 initialization failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-PMSAR-2-MMAPERR [chars](),[dec]: [chars] [hex]
Explanation SAR device cx27470 mmap access violation failure
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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-PMSAR-2-MUTEX_TIMEOUT [chars]() [dec], Get SAR:[dec], thread_id:[dec] mutex timed out, [chars]
Explanation A fatal error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-2-OPEN_VC_ERR [chars]() [dec], open vc failure. rsar:[dec], ssar:[dec], vpi:[dec], vci:[dec] reason:[chars]; status:[dec], ack:[hex], [hex], [hex], [hex]
Explanation A fatal error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-2-OPEN_VP_ERR [chars]() [dec], open vp failure. sar:[dec] vpi:[dec], reason:[chars]; ack:[hex], [hex], [hex], [hex]
Explanation A fatal error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-2-PORT_STATS_ERR [chars]() [dec], port stats failure. sar:[dec] reason:[chars]; status:[dec], ack:[hex], [hex], [hex], [hex]
Explanation A fatal error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-2-RESOURCE_ERR [chars] [dec], [chars] with errno:[dec]
Explanation A critical IOX resource request failed that expected to succeed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PMSAR-3-ESYS_ERR [chars] [dec]: reason [chars] errno:[dec]
Explanation CX27470 esys generic fatal error message.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-3-ESYS_LOAD_ELF [chars] [dec]: file [chars] [chars] [chars]
Explanation CX27470 esys load elf input file symbol not found.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-3-EVENT_INDICATE [chars]() [dec], reason:[chars]; sar:[dec], log_entry_index:[dec], type:[dec], status:[dec]
Explanation An event raised PM SAR Driver, check the event type
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PMSAR-3-UNKNOWN_EVENT [chars]() [dec], reason:[chars]; sar:[dec], log_entry_index:[dec]
Explanation An unknown event raised PM SAR Driver
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-4-WARNING [chars]
Explanation PM622 TSP CX27470 warning condition
Recommended Action Debug message only. No action is required.
Error Message%L2-PMSAR-6-event_dump [chars]() [dec], sar:[dec], event type:[dec], status:[dec]; hex dump:[hex], [hex], [hex], [hex]
Explanation A warning or error occurred during PM SAR Driver cofiguration
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PMSAR-6-INFO [chars] [hex]
Explanation PM622 TSP CX27470 information
Recommended Action No action is required.
Error Message%L2-PMSAR-7-DEBUG [chars]
Explanation PM622 TSP CX27470 debug information
Recommended Action Debug message only. No action is required.
POS Messages
Error Message%L2-POS-3-MTU_IMPOSE_FAILED Failed to set MTU of [unsigned int] on [chars]
Explanation The specified MTU could not be applied on this interface.
Error Message No action is required.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.
Error Message%L2-PPP_EA-4-ERR_EVM_EVENT_BLOCK Error encountered in the event loop: [chars]. The PPP EA process will restart
Explanation An error occured in the event loop. The process will restart which should recover the situation.
Recommended Action *RECUR*
Error Message%L2-PPP_EA-4-ERR_INIT Failure during initialization of the [chars]. Error [chars]. The PPP EA process will restart
Explanation A failure occured during the initialization of the process. The process will restart which should recover the situation.
Recommended Action *RECUR*
Error Message%L2-PPP_EA-6-ERR_IMP_MULTIPLE_NTFCNS : Multiple [chars] notifications received in a single batch from improxy
Explanation A batch from IMProxy contained multiple notifications for a single interface. This should not occur but the situation has been recovered successfully by the PPP EA. No problems should be seen as a result.
Recommended Action *NONE*
PPP_FSM Messages
Error Message%L2-PPP_FSM-3-ERR_SOCKET [chars]: Socket [chars] failed; [chars]
Explanation There is a communication problem with the PPP socket.
Recommended Action Restart the ppp_socket process on the node where the error is reported. If the message recurs, copy the error message exactly as 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_LCP Messages
Error Message%L2-PPP_LCP-3-MTU_UNUSABLE [chars] has an interface MTU of [unsigned int] which is smaller than the PPP packet header size ([unsigned int]) and so PPP cannot run on the interface
Explanation PPP has been informed that the interface MTU has been set to a value smaller than the PPP header size, which makes it impossible for PPP to operate.
Recommended Action Reconfigure the interface's MTU to a larger value. In order to ensure correct operation with peers, values which provide a layer 2 payload capacity (after allowing for 4 bytes of PPP header) of 1500 bytes or greater are required.
Error Message%L2-PPP_LCP-4-MISSING_AUTHENTICATION_LIST AAA authentication list [chars] is not defined for PPP
Explanation One or more PPP interfaces have been configured to authenticate the peer using the authentication list identified in the error message, but this authentication list has not been configured in AAA itself. As a result PPP will be unable to authenticate the peer and the line protocol on the relevant interface or interfaces will not come up.
Recommended Action Configure 'aaa authentication ppp ...'
Error Message%L2-PPP_LCP-4-MTU_WARNING [chars] has a PPP MTU of [unsigned int] which is smaller than the minimum value ([unsigned int]) required for correct operation
Explanation RFC 1661 requires that the media that PPP is running over is always able to receive PPP packets of sizes up to 1500 bytes (where this value excludes the 4 bytes of PPP header). This is to ensure that the peer can always send control protocol packets up to this size if they ever need to renegotiate. IOS-XR routers set their MRU to the same value as the MTU, and this message has been issued because the configured MTU is too small to meet the above condition.
Recommended Action Reconfigure the interface's MTU to a larger value. In order to ensure correct operation with peers, values which provide a layer 2 payload capacity (after allowing for 4 bytes of PPP header) of 1500 bytes or greater are required. Note that as most Control Protocol packets are much smaller than 1500 bytes, it is unlikely that MTU values which are smaller than 1500 bytes will actually cause problems, but this cannot be guaranteed.
Error Message%L2-PPP_LCP-4-UNRECOGNIZED_PROTO Unrecognized IfMgr protocol [chars] onCH[hex] (caps=[chars])
Explanation Interface Manager notified LCP about a protocol that it doesn't recognize, either by sending a request to LCP to adopt this node or by informing LCP that it exists. This is a programming error as LCP needs to recognized all of the protocols which run above it in order to be able to run the relevant CP.
Recommended Action Copy the error message exactly as it appears 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-PPP_LCP-5-MTU_NEGOTIATED The PPP MTU for [chars] has been negotiated to be [unsigned int]. This is less than the configured PPP MTU of [unsigned int]
Explanation The PPP MTU is reduced when the PPP MRU of the peer is less than the PPP MTU derived from the locally configured interface MTU. The reduced value will be used until LCP is renegotated (such as when the interface goes down and comes back up, or a new MTU is configured), or if the PPP encapsulation is removed from the interface. The MTU then returns to the configured value and another message will indicate if a value less than the configured value is negotiated again. The reduced MTU is a normal part of PPP operation and is not indicative of any problems.
Recommended Action No action is required.
Error Message%L2-PPP_LCP-6-LOCAL_MTU_TOO_SMALL : Unable to complete LCP negotiations. Interface MTU onCH[hex] needs to be reconfigured to at least [unsigned int]
Explanation The peer has sent a NAK in response to the local MRRU value. The value it is suggesting for the MRRU is larger than the local bundle admin MTU, so it cannot be accepted. However, suggesting a smaller value will almost certainly lead to repeated NAKs (since the peer should be suggesting its minimum possible MRRU value), so the LCP session will be closed for a short time and then negotiations will be retried.
Recommended Action Reconfigure the interface's MTU to a larger value (at least the value suggested in the message).
PPP_lite Messages
Error Message%L2 control-PPP_lite-3-ERR_PL_DLL_ASYNC_SEND_FAIL Send async pulse to ppp lite process fails; Error [chars]
Explanation Attempt to send pulse to PPP lite process fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2 control-PPP_lite-3-ERR_PL_DLL_CHAN_CONNECT_FAIL Cannot connect to ppp lite process; Error [chars]
Explanation Attempt to connect to PPP lite process channel fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2 control-PPP_lite-3-ERR_SHMEM_MMAP_FAIL Cannot mmap file [chars]; Error [chars]
Explanation Attempt to mmap the shared memory fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2 control-PPP_lite-3-ERR_SHMEM_OPEN_FAIL Cannot open shmem file [chars]; Error [chars]
Explanation Attempt to open the shared memory fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2 control-PPP_lite-3-ERR_SHMEM_TRNC_FAIL Cannot truncate file [chars] to [dec] bytes; Error [chars]
Explanation Attempt to truncate the shared memory file fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2 control-PPP_lite-3-ERR_SHMEM_UNAVAILABLE PPP lite SHMEM can accommodate only [dec] records (request for [dec] records)
Explanation PPP MA has requested transfer of more interface records than shared memory can accommodate
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 or from theshow tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
PPP_MA Messages
Error Message%L2-PPP_MA-4-ERR_AAA Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the AAA service. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary problem communicating with the AAA server, but the error could also be caused by low memory resource or programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the process may help. If the message recurs, copy the error message exactly as it appears 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-PPP_MA-4-ERR_AIB Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error communicating with the AIB server. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary connection problem with the AIB server, but the error could also be caused by low memory resource or programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the process may help. If the message recurs, copy the error message exactly as it appears 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-PPP_MA-4-ERR_ATTR Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error communicating with the infrastructure. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary connection problem, but the error could also be caused by low memory resource or programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the process may help. If the message recurs, copy the error message exactly as it appears 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-PPP_MA-4-ERR_BAG Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the Bag Client library. The error message describes what operation has failed and why it failed. The most likely reason for this a low memory condition but the error could also be caused by a programming error. The error will affect PPP MA's ability to provide operational management data, but won't otherwise affect PPP MA's operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.
Error Message%L2-PPP_MA-4-ERR_CHKPT Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the Checkpoint Service. The error message describes what operation has failed and why it failed. The most likely reason for this a low memory condition but the error could also be caused by a programming error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.
Error Message%L2-PPP_MA-4-ERR_CHKPT_CORRUPT Corrupt [chars] checkpoint record found: [chars]
Explanation Whilst restoring one of its checkpoint tables PPP MA found a corrupt checkpoint entry. The entry will be ignored and so the relevant interface's PPP session will be renegotiated after the restart and as a result there may be a short period where traffic is lost.
Recommended Action Copy the error message exactly as it appears 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-PPP_MA-4-ERR_CHKPT_DUPLICATE Duplicate [chars] checkpoint record found for [chars]
Explanation Whilst restoring one of its checkpoint tables PPP MA found multiple entries for the same interface. PPP MA will use the first checkpoint entry it finds for each interface and ignore any subsequent duplicates. This is caused by a programming error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..
Error Message%L2-PPP_MA-4-ERR_CLOCK Unexpected error encountered whilst retrieving the value of the [chars] clock: [chars]
Explanation PPP MA encountered an error whilst retrieving the value of the realtime clock. The error message includes details of the reason for the error. This is a fatal error and the PPP MA process will abort and be restarted to recover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PPP_MA-4-ERR_DEBUG Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the debug service. The error message describes what operation has failed and why it failed. The error could be caused by low memory resource or programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the process may help. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.
Error Message%L2-PPP_MA-4-ERR_EVC_CLOSE Error closing '[chars]' connection: [chars]
Explanation PPP MA failed to close a connection to an essential service. This is an internal error and it requires a restart of the process for recovery.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PPP_MA-4-ERR_EVC_CREATE Error creating '[chars]' connection: [chars]
Explanation PPP MA failed to create a connection to an essential service during initialization. This is an internal error. It requires a restart of the process for recovery.
Recommended Action Copy the error message exactly as it appears 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-PPP_MA-4-ERR_EVC_ERROR Error resetting '[chars]' connection: [chars]
Explanation After detecting an error with the connection to the specified service, PPP MA failed to reset that connection. This is an internal error. It requires a restart of the process for recovery.
Recommended Action Copy the error message exactly as it appears 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-PPP_MA-4-ERR_EVC_EVM_HANDLER Error registering for data events on '[chars]' connection: [chars]
Explanation During initialization, PPP MA failed to register for input or output notifications for the specified service. This is an internal error. It requires a restart of the process for recovery.
Recommended Action Copy the error message exactly as it appears 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-PPP_MA-4-ERR_EVC_GET_FD Error retrieving the Connection ID from the '[chars]' connection: [chars]
Explanation PPP MA failed to retrieve the file descriptor associated with the specified service. This is an internal error.
Recommended Action Consider restarting the PPP MA process. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PPP_MA-4-ERR_EVC_NOTIFY Error registering for critical events on '[chars]' connection: [chars]
Explanation During initialization, PPP MA failed to register for essential notifications regarding the state of the connection for the specified service. This is an internal error. It requires a restart of the process for recovery.
Recommended Action Copy the error message exactly as it appears 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-PPP_MA-4-ERR_EVC_OPEN Error opening '[chars]' connection: [chars]
Explanation PPP MA failed to open a connection to an essential service during initialization. This is an internal error. It requires a restart of the process for recovery.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PPP_MA-4-ERR_EVM_ATTACH Failed to register a handler for '[chars]' messages: [chars]
Explanation PPP MA failed to register a handler for the specified class of event. This is an initialization error and implies that PPP MA will not be able to operate correctly. The PPP MA process will abort and be restarted in an attempt to recover. The cause may be a resource starvation problem but is most likely to be an internal programming error. The error message should give more details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Restart the PPP MA process. *RECUR*
Error Message%L2-PPP_MA-4-ERR_EVM_CREATE Error creating the PPP MA Event Manager: [chars]
Explanation PPP MA failed to create its Event Manager which is a critical resource for the operation of the process. This error may be caused by low memory resources. The process will abort and be restarted in an attempt to recover.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *SUPPORT*
Error Message%L2-PPP_MA-4-ERR_EVM_SEND Failed to send '[chars]': [chars]
Explanation PPP MA failed to send the specified message. The cause may be a resource starvation problem but is most likely to be an internal programming error. The error message should give more details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Restart the affected PPP MA process. *RECUR*
Error Message%L2-PPP_MA-4-ERR_EVQ_CREATE Error creating event queue for '[chars]': [chars]
Explanation This is an unexpected error. The PPP MA process will attempt to recover by restarting. The cause may be a resource starvation problem. The error message should provide more details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%L2-PPP_MA-4-ERR_EVQ_DEQUEUE Error dequeuing event for '[chars]': [chars]
Explanation This is an unexpected error. The PPP MA process will attempt to recover by restarting. The cause may be a resource starvation problem. The error message should provide more details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%L2-PPP_MA-4-ERR_EVQ_ENQUEUE Error queuing event for '[chars]': [chars]
Explanation This is an unexpected error. The PPP MA process will attempt to recover by restarting. The cause may be a resource starvation problem. The error message should provide more details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*
Error Message%L2-PPP_MA-4-ERR_IMC Unexpected IfMgr error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error communicating with Interface Manager. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary connection problem with the Interface Manager Control Server, but the error could also be caused by low memory resource or programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the process may help. If the message recurs, copy the error message exactly as it appears 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-PPP_MA-4-ERR_IP_ARM Failed to [chars] [chars]: [chars]
Explanation IPCP encountered an error using the IP-ARM API. The error message describes what operation failed. This may be a resource starvation problem or an internal programming error.
Recommended Action Restart the local ipv4_ma process and/or the ppp_ma process. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.
Error Message%L2-PPP_MA-4-ERR_LAS Failed to [chars] [chars]: [chars]
Explanation IPV6CP encountered an error using the LAS API. The error message describes what operation failed. This may be a resource starvation problem or an internal programming error.
Recommended Action Restart the local ipv6_ma process and/or the ppp_ma process. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.
Error Message%L2-PPP_MA-4-ERR_LTRACE Unexpected error encountered whilst [chars] the [chars] buffer: [chars]
Explanation PPP MA encountered an error using the Lightweight Tracing service. The error message describes what operation has failed and why it failed. This is a fatal error and the PPP MA process cannot continue. It will abort and subsequently be restarted by SysMgr in an attempt to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PPP_MA-4-ERR_MEM_ALLOC Failed to allocate [unsigned int] bytes for '[chars]'
Explanation The process failed to allocate memory for the specified resource.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-PPP_MA-4-ERR_MGD_TIMER Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an unexpected error using the Managed Timer library. This is most likely to be due to a low memory condition but may also be an internal programming error. The error message should provide more information about the cause.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Consider restarting the PPP MA process. *RECUR*.
Error Message%L2-PPP_MA-4-ERR_PAK Error handling pakman corruption problem: [chars]. Process exiting.
Explanation The connection to packet manager was errored and the attempt to recover failed. Restarting the process should resolve the problem.
Recommended Action Restart the ppp_ma process. If the message recurs, copy the error message exactly as it appears 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-PPP_MA-4-ERR_SYSDB Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the SysDB service. The error message describes what operation has failed and why it failed. The most likely reason for this is a connection problem with the SysDB server, but the error could also be caused by low memory resources or programming error.
Recommended Action Consider restarting the PPP MA process. If the message recurs, copy the error message exactly as it appears 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-PPP_MA-4-ERR_SYSMGR Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error whilst communicating with SysMgr. The error message describes what operation has failed and why it failed. This is a fatal error and the PPP MA process will abort and be restarted to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PPP_MA-4-ERR_SYSMGR_MDR Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error whilst communicating with SysMgr. The error message describes what operation has failed and why it failed. Sysmgr will take action to recover if appropriate. It is possible that this error has occured after MDR. If so then the recovery may require a cold reload of the card
Recommended Action If the message recurs, copy the error message exactly as it appears 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-PPP_MA-4-ERR_THREAD_CREATE Failed to create '[chars]' thread: [chars]
Explanation PPP MA encountered an unexpected error creating a new thread. The process will restart to attempt to recover. This is possibly due to a low memory condition but may also be an internal programming error. The error message should provide more information about the cause.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.
Error Message%L2-PPP_MA-4-ERR_WAVL_INIT Error initializing the WAVL tree used to store PPP MA IDBs: [chars].
Explanation PPP MA encountered an unexpected error which prevents it from functioning. This error may be caused by low memory resources. The process will abort and be restarted in an attempt to recover.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*
Error Message%L2-PPP_MA-6-ERR_EVC_DESTROY Error destroying '[chars]' connection: [chars]
Explanation During process termination PPP MA failed to destroy a connection to a service provided by another process. This is an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PPP_MA-6-ERR_EVM_EVENT_BLOCK Error blocking waiting for an event to process: [chars]
Explanation This is an unexpected error. The PPP MA process may recover by itself, or it may need to be restarted to recover.
Recommended Action Restart the affected PPP MA process. If the message recurs, copy the error message exactly as it appears 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-PPP_MA-6-ERR_EVQ_DESTROY Error destroying event queue for '[chars]': [chars]
Explanation During process termination PPP MA failed to destroy an event queue. The process will terminate regardless so there should be no lasting problems.
Recommended Action Copy the error message exactly as 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.
Error Message%L2-PSE-2-CRIT_EXIT Exit on error: [chars]: Caused by [chars]
Explanation An critical error occurred in PSE Driver which requires exiting (and, hence, restarting) 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-PSE-2-NODE_BRINGDOWN [chars] device: Caused by [chars]
Explanation The PSE driver was unable to perform a critical function and must trigger a node bringdown to effect recovery.
Recommended Action No action is required.
Error Message%L2-PSE-4-COLD_RESET_FAILED [chars] device: Caused by [chars]
Explanation This is an error message in the PSE Driver to indicate that it failed to perform cold reset of specified pse instance due to the specified reason.
Recommended Action No action is required.
Error Message%L2-PSE-4-ERRRATE_EXCEED_FAST [chars] device: High rate of ASIC errors of type: [chars]
Explanation This is an error message in the PSE Driver to indicate that a high rate of specified errors is being detected.
Recommended Action No action is required.
Error Message%L2-PSE-4-ERRRATE_EXCEED_GLACIAL [chars] device: High rate of ASIC errors of type: [chars]
Explanation This is an error message in the PSE Driver to indicate that a high rate of specified errors is being detected.
Recommended Action No action is required.
Error Message%L2-PSE-4-PROTO_HW_VERSION [chars] PSE ASIC prototype hardware detected. This version ([unsigned int]) will be unsupported in future releases.
Explanation This message indicates that the version of the PSE ASIC is a prototype, and will be unsupported in future s/w releases.
Recommended Action No action is required.
Error Message%L2-PSE-4-WARM_RESET_FAILED [chars] device: Caused by [chars]
Explanation This is an error message in the PSE Driver to indicate that it failed to perform warm reset of specified pse instance due to the specified reason.
Recommended Action No action is required.
Error Message%L2-PSE-5-ERR_CONT Continuing execution: [chars]: Caused by [chars]
Explanation This message indicates an error occurred beyond which execution of the pse_driver may continue, attempting to effect recovery or work-around internally, minimizing loss of information/functionality.
Recommended Action If the message recurs, copy the error message exactly as it appears 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 [chars]
Explanation This is a informational message in the PSE Driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-PSE-7-DEBUG_MSG [chars]
Explanation This is a debug message in the PSE Driver to indicate an operation or condition.
Recommended Action No action is required.
Error Message%L2-PSE-7-ERR_EXIT Exit on error: [chars]: Caused by [chars]
Explanation An error occurred in PSE Driver which requires exiting (and, hence, restarting) 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-PSE-7-MP_CORE MP Core File saved in [chars].
Explanation An error occurred in PSE MP Microcode Driver which required exiting (and, hence, restarting) the process. This message records the location of the MP Core File.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PSELIB Messages
Error Message%L2-PSELIB-4-EXIT_ON_ERR [chars]. Reason: [chars]
Explanation An error occurred in the PSE ASIC client library after which the client code cannot continue. This error is encountered when a client module (e.g. cli command) has difficulty retrieving information from the PSE driver. The root cause may be located in either hardware or software.
Recommended Action *RECUR*
QM_E5 Messages
Error Message%L2-QM_E5-4-INTERRUPT [chars]: [chars] : reg value [hex]
Explanation The queueing asic experienced an interrupt, and will be reset. After reset, normal operation should resume.
Recommended Action Log the error. If the error persists after reset, contact support.
Error Message%L2-QM_E5-4-INTERRUPT2 [chars]: [chars] : reg1 [hex]: reg2 [hex]
Explanation The queueing asic experienced an interrupt, and will be reset. After reset, normal operation should resume.
Recommended Action Log the error. If the error persists after reset, contact support.
Error Message%L2-QM_E5-7-INTERRUPT3 [chars]: [chars]: error_reg: [hex] error_info: [hex]
Explanation The queueing asic experienced an interrupt, and is non-fatal. In some cases its corrected by software and remaining cases its occurences logged.
Recommended Action Log the error.
Error Message%L2-QM_E5-7-INTERRUPT4 [chars]: [chars]: error_reg: [hex]
Explanation The queueing asic experienced an interrupt, and is non-fatal. In some cases its corrected by software and remaining cases its occurences logged.
Recommended Action Log the error.
QM Messages
Error Message%L2-QM-4-INTERRUPT [chars]: [chars] : reg value [hex]
Explanation The queueing asic experienced an interrupt, and will be reset. After reset, normal operation should resume.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
QUEUEING Messages
Error Message%L2-QUEUEING-3-FATAL_ERR [chars]: Err=[dec]
Explanation A fatal error occurred in QUEUEING ASIC Driver which involves exiting the process. The process will be respawned, but if it continues to fail the linecard will be reset, as the linecard cannot operate without this 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.
Serial Messages
Error Message%L2-Serial-3-MTU_IMPOSE_FAILED Failed to set MTU of [unsigned int] on [chars]
Explanation The specified MTU could not be applied on this interface.
Recommended Action No action is required.
Error Message%L2-Serial-4-ALARM [chars]: [chars] [chars]
Explanation The specified Serial Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
SLARP_EA Messages
Error Message%L2-SLARP_EA-2-EVENT_BLOCK Failure during receipt of message. Error: [chars]
Explanation A failure occurred handling a message arriving at the SLARP capsulation EA 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-SLARP_EA-2-INIT Failure during intialisation of SLARP Caps EA. Error: [chars]
Explanation A failure occurred during the initialisation of the SLARP capsulation EA 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-SLARP_EA-3-ADJ_UPDATE_FAIL [hex]: unable to update adjacency : [chars]
Explanation Adjacency information was not able to be updated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SLARP_Lite Messages
Error Message%L2-SLARP_Lite-3-ERR_CSL_DLL_ASYNC_SEND_FAIL Send async pulse to slarp lite process fails; Error [chars]
Explanation Attempt to send pulse to SLARP lite process fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-SLARP_Lite-3-ERR_CSL_DLL_CHAN_CONNECT_FAIL Cannot connect to slarp lite process; Error [chars]
Explanation Attempt to connect to slarp lite process channel fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-SLARP_Lite-3-ERR_SHMEM_MMAP_FAIL Cannot mmap file [chars]; Error [chars]
Explanation Attempt to mmap the shared memory fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-SLARP_Lite-3-ERR_SHMEM_OPEN_FAIL Cannot open shmem file [chars]; Error [chars]
Explanation Attempt to open the shared memory fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-SLARP_Lite-3-ERR_SHMEM_TRNC_FAIL Cannot truncate file [chars] to [dec] bytes; Error [chars]
Explanation Attempt to truncate the shared memory file fails
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-SLARP_Lite-3-ERR_SHMEM_UNAVAILABLE SLARP lite SHMEM can accommodate only [dec] records (request for [dec] records)
Explanation cHDLC MA has requested transfer of more interface records than shared memory can accommodate
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 or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.
SLARP Messages
Error Message%L2-SLARP-1-CAPS_ADD [chars]: Could not add slarp capsulation : [chars]
Explanation Could not add the slarp capsulation in 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-SLARP-1-CAPS_REMOVE [chars]: Could not remove slarp capsulation : [chars]
Explanation Could not remove the capsulation in question.
Recommended Action Copy the error message exactly as it appears 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-SLARP-1-CLOCK_READ_ERROR Unable to read the clock: [chars]
Explanation Unable to read the clock.
Recommended Action Copy the error message exactly as it appears 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-SLARP-1-CONN_ALLOC Failed to allocate event connection with [chars].
Explanation An attempt to allocate a connection resource 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-SLARP-1-CONN_NOTIFY Failed to attach event connection handler for [chars].
Explanation An attempt to attach a handler for an event connection 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-SLARP-1-DEBUG_REGISTER Could not register for debug events : [chars]
Explanation An attempt ot register with the debug infrastructure failed. The failure cannot be handled, so the process will have exited and will be automatically restarted.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-SLARP-1-EVENT_CONN Unable to initialize slarp timers
Explanation Can not initialize the even channel used by slarp timers.
Recommended Action Copy the error message exactly as it appears 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-SLARP-1-EVENTBLOCK event_block returned early : [chars]
Explanation An unexpected or erroneous return while waiting for events.
Recommended Action Copy the error message exactly as it appears 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-SLARP-1-IM_STATEQUERY Failed to query IM interface state: [chars]
Explanation An attempt to query the interface state from IM 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-SLARP-1-INVTIMER invalid timer [dec]
Explanation An error occurred attempting to transmit a SLARP packet.
Recommended Action Copy the error message exactly as it appears 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-SLARP-1-NO_INITIAL_CONFIG Failed to get the initial configuration: [chars]
Explanation The initial configuration of the box was unable to be determined.
Recommended Action Copy the error message exactly as it appears 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-SLARP-1-NOIDB [chars]: Event which we do not have record of
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-SLARP-1-NORESOURCE [chars] failed to allocate resource in [chars]
Explanation An attempt to allocate a resource 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-SLARP-1-TIMER_ALLOC [chars]: Could not allocate a timer for SLARP : [chars]
Explanation Could not allocate a timer. SLARP will not run on this interface.
Recommended Action Copy the error message exactly as it appears 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-SLARP-1-TRACE_REGISTER Failed to register with tracing infrastructure: [chars]
Explanation An attempt to register with the tracing infrastrucure failed. The failure cannot be handled, so the process will have exited and will be automatically restarted. The root cause of the problem is likely to be with the tracing infrastructure, rather than with this process in particular.
Recommended Action If the message recurs, copy the error message exactly as it appears 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-SLARP-1-TREE_INSERT [chars]: Could not insert interface into storage.
Explanation We could not store information about this interface.
Recommended Action Copy the error message exactly as it appears 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-SLARP-5-OLDSEQ [chars]: Outdated sequence number [dec], current [dec]
Explanation A keepalive packet was received out of sequence with previous keepalives.
Recommended Action Copy the error message exactly as it appears 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-SLARP-5-PKTLENGTH Invalid packet length [dec] recv on [chars], should be [dec]
Explanation An invalid SLARP packet was received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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.
SONET_APS Messages
Error Message%L2-SONET_APS-4-WARNING [chars] - [chars]
Explanation A non-fatal error occured while executing the function in question. The message contains info about the cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of SONET APS.
Error Message%L2-SONET_APS-4-WP_INFO Connection to [chars]%s [chars]
Explanation State change in the APS group internal communication system detected. Expected during transitory conditions at config changes, OIR, etc. The message contains info about the WP communication components affected.
Recommended Action Verify continued correct operation of SONET APS.
Error Message%L2-SONET_APS-6-CONFLICT [chars] ([chars]) - [chars]
Explanation A conflict failure occured The message contains info about the cause of the failure and possibly anticipated actions/effects.
Recommended Action Fix the confguration error for proper operation of SONET APS.
Error Message%L2-SONET_APS-6-CONTACT [chars] [chars] [dec] [chars] [dec] [chars]
Explanation Debug messages for APS.
Recommended Action No Action requirements.
Error Message%L2-SONET_APS-6-REQUEST_PREEMPTED APS group [dec] [chars] [dec]: preempted
Explanation The user external request is preempted.
Recommended Action Not Action requirements.
Error Message%L2-SONET_APS-6-UPDOWN [chars] [chars] [dec] [chars] [dec] [chars]
Explanation Debug messages for APS.
Recommended Action No Action requirements.
Error Message%L2-SONET_APS-7-ERROR [chars] failed ([chars]) - [chars]
Explanation A general failure occured while executing the function in question. The message contains info about the cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of SONET APS.
Error Message%L2-SONET_APS-7-NOMEM Not enough memory for [chars]
Explanation The process is out of memory.
Recommended Action Check process list for source of memory loss. Check if h/w memory requirements are met.
SONET_LOCAL Messages
Error Message%L2-SONET_LOCAL-3-ERROR [chars]([dec]): [chars] failed ([chars]) - [chars]
Explanation A general failure occured while executing the function in question. The message contains info about the location and cause of the failure and possibly anticipated actions/effects.
Recommended Action This error indicates a problem in the code and cannot be easily recovered from. Copy the error message exactly as it appears 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-SONET_LOCAL-4-ALARM [chars]: [chars] [chars]
Explanation The specified SONET Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
SPA_192 Messages
Error Message%L2-SPA_192-3-ERR_SPA_UNSUPPORTED Inserted node [chars] is not supported by Cisco 12000 Series SPA Interface Processor-600 line card. Please remove to prevent damages to the hardwares.
Explanation A SPA identified by nodeid %s above is not supported by Cisco 12000 Series SPA Interface Processor-600 line card. The SPA should be remove immediately to prevent damages to the hardwares.
Recommended Action Physcially remove the SPA module from the line card.
Error Message%L2-SPA_192-3-ERR_SPA_UNSUPPORTED Inserted node [chars] is not supported by Cisco 12000 Series SPA Interface Processor-601 line card. Please remove to prevent damages to the hardwares.
Explanation A SPA identified by nodeid %s above is not supported by Cisco 12000 Series SPA Interface Processor-601 line card. The SPA should be remove immediately to prevent damages to the hardwares.
Recommended Action Physcially remove the SPA module from the line card.
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_ETHER Messages
Error Message%L2-SPA_ETHER-2-SPA_MAC_ERR [chars]
Explanation The internal SPA MAC got out of sync. SW needs to reset the device in order to clear the issue
Recommended Action If reseting the MAC device fixes the issue, nothing needs to be done. If the reset does not work, the SPA will need to be SW OIR'd. This can be easily checked by doing 'top' on the LC with the issue. If the CPU is very high, the reset did not work.
Error Message%L2-SPA_ETHER-4-INVALID_MAC Failed to get MAC address for port [dec], Interface assigned random MAC address.
Explanation PLIM driver was unable to get a MAC address for the interface.
Recommended Action Check if the process 'shelfmgr' is up and running on the RP. Try to reload the LC to see if that helps. Copy the error message exactly as 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_FPD Messages
Error Message%L2-SPA_FPD-3-FATAL_ERROR [chars]
Explanation An internal system software error has occurred. This type of errors are in general SW bugs that are caused by providing wrong information to SPA FPD API.
Recommended Action Copy the error message exactly as it appears 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-SPA_FPD-3-GET_IMG_ERROR [chars][[dec]]: [chars]
Explanation An image for an FPD could not be obatined so that it could be updated. The cause of the failure is indicated in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-SPA_FPD-3-GET_VERSION_ERROR [chars][[dec]]: Failed to get FPD version information.
Explanation The version of the FPD could not be obtained from the specified SPA. The FPD information will not be available for the specified SPA. System processing will continue normally.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-SPA_FPD-3-SW_ERROR [chars][[dec]]: [chars]
Explanation An internal software error has occurred on the specified SPA.
Recommended Action Copy the error message exactly as it appears 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-SPA_FPD-3-UPDATE_FAILED [chars][[dec]]: Failed to update FPD '[chars]' image
Explanation The update operation for the specified FPD image has failed.
Recommended Action Retry the operation to update the image. If the retry operation fails, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2-SPA_FPD-3-WRONG_OIR_STATE [chars][[dec]]: Cannot perform FPD image update on '[chars]' OIR state, it should be in '[chars]' OIR state
Explanation The FPD image update operation could not be performed because the specified SPA is not in the correct state. The correct OIR state for the SPA is specified in the message text.
Recommended Action Do not perform the update operation while the SPA is in the middle of a reload operation or while it is being initialized. Wait until the specified SPA is in the correct OIR state and retry the operation.
Error Message%L2-SPA_FPD-5-OFFLINE_NOTICE [chars][[dec]]: Changing operational status to offline for update of FPD image
Explanation An attempt has been made to temporarily change the operaional status of the SPA from online to offline before the image for the FPD could be updated on the target SPA. For some SPA types, this operation is required.
Recommended Action Ensure that you have redirected the traffic of the target SPA before performing this action, since the target SPA will require a power cycle operation after the image update for the FPD on the target SPA has been performed.
Error Message%L2-SPA_FPD-5-RELOAD_NOTICE [chars][[dec]]: Reloading the SPA for the updated FPD image(s) to take effect
Explanation Indicates the reloading operation of the SPA after the completion of the FPD image update opearation.
Recommended Action No action is required.
Error Message%L2-SPA_FPD-6-UPDATE_PASSED [chars][[dec]]: Successfully updated FPD '[chars]' image
Explanation The FPD image was updated successfully.
Recommended Action No action is required.
Error Message%L2-SPA_FPD-6-UPDATE_START [chars][[dec]]: Starting update of FPD '[chars]' image
Explanation The FPD update update operation has started for the specified image.
Recommended Action No action is required.
SPA_OC3_OC12 Messages
Error Message%L2-SPA_OC3_OC12-3-DRIVER_ERR [chars] [chars]
Explanation SPA OC3/OC12 driver error messages
Recommended Action *NONE*
Error Message%L2-SPA_OC3_OC12-6-INFO [chars] [chars]
Explanation SPA OC3/OC12 informational message
Recommended Action *NONE*
Error Message%L2-SPA_OC3_OC12-7-DEBUG [chars] [chars]
Explanation SPA OC3/OC12 debug message
Recommended Action *NONE*
SPA_OC48 Messages
Error Message%L2-SPA_OC48-3-DRIVER_ERR [chars] [chars]
Explanation SPA OC48 driver error messages
Recommended Action *NONE*
Error Message%L2-SPA_OC48-6-INFO [chars] [chars]
Explanation SPA OC48 informational message
Recommended Action *NONE*
Error Message%L2-SPA_OC48-7-DEBUG [chars] [chars]
Explanation SPA OC48 debug message
Recommended Action *NONE*
SPA_PLIM_SB Messages
Error Message%L2-SPA_PLIM_SB-3-FPD_GETVER_FAIL [chars][[dec]]: Failed to get FPD image version for [chars]
Explanation The FPD image version could not be retrieved from the SPA for the pogrammable device that is specified in the message text. This condition can occur if the system attempts to retrieve the version information while the SPA is not in the correct operational state.
Recommended Action Try to reload the affected SPA or physically remove and then insert the SPA to correct 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-SPA_PLIM_SB-3-FPD_IMG_UPD_ERROR [chars][[dec]]: [chars] image update error ([chars])
Explanation The FPD image update operation for the indicated device has failed. The cause of the error is also indicated in the message.
Recommended Action Retry the image update operation and if it fails again, copy the error message exactly as it appears 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-SPA_PLIM_SB-3-MSG_REPLY_FAIL [chars][[dec]]: Failed to reply a message ([chars])
Explanation A message to the specified SPA did not receive a reply. The reason for the failure is specified in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-SPA_PLIM_SB-3-MSG_SEND_FAIL [chars][[dec]]: Failed to send message ([chars]) after retries: [[dec]]
Explanation A message to the specified SPA could not be sent. The reason for the failure is specified in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-SPA_PLIM_SB-3-OPEN_CH_FAIL [chars][[dec]]: Open channel for [chars] failed ([chars])
Explanation A communication channel could not be opened with the specified SPA. The reason for the failure is specified in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-SPA_PLIM_SB-3-SW_ERROR [chars][[dec]]: [chars]
Explanation An internal software error has occurred for the specified SPA.
Recommended Action Copy the error message exactly as 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 Messages
Error Message%L2-SPA-3-PLIM_HEARTBEAT_ERR [chars]: bay [dec] heartbeat failed, expected seq# [unsigned int] received seq# [unsigned int], Time since last message [dec]s
Explanation The IPC communication between local CPU and host in the specified slot indicated in the message is not functional. If the problem persists the SPA will be reloaded to recover from the failure.
Recommended Action If the problem persists, try to reseat the SPA. If reseating does not help, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%L2-SPA-3-SYSDB_ERROR [chars]
Explanation SPA Infrastructure SysDb error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-SPA-4-CERR_REGISTRATION_FAILURE Registration of error strings failed with error [hex]
Explanation Error string reistration 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-SPA-5-APPS_IMAGE_DOWNLOADING Downloading SPA Application Image ([chars])...
Explanation Downloading SPA Application image as indicated in the message
Recommended Action none.
Error Message%L2-SPA-5-APPS_IMAGE_ERROR Download SPA Application Image failed.
Explanation Failed to download the SPA Application image.
Recommended Action none.
Error Message%L2-SPA-5-APPS_IMAGE_SIZE_ERR SPA Application image exceeds RAM size: Image size ([dec]) Shared mem size ([dec])
Explanation The size of the SPA Application image is too big.
Recommended Action none.
Error Message%L2-SPA-5-DOWNLOAD_METHOD_ERR SPA Download method [dec] not supported
Explanation The specified download method is not supported
Recommended Action none.
Error Message%L2-SPA-5-FILE_SIZE_ERR SPA File exceeds Rdisk size: File size ([dec]) Rdisk size ([dec])
Explanation The size of the SPA File is too big.
Recommended Action none.
Error Message%L2-SPA-5-OIR_ERROR [chars]
Explanation SPA related error as indicated in the msg
Recommended Action none.
Error Message%L2-SPA-5-OIR_INSERTED SPA discovered in bay [dec]
Explanation For displaying SPA OIR.
Recommended Action none.
Error Message%L2-SPA-5-OIR_REMOVED SPA removed from bay [dec]
Explanation For displaying SPA OIR.
Recommended Action none.
Error Message%L2-SPA-5-OS_IMAGE_DOWNLOADING Downloading SPA OS Image ([chars])...
Explanation Downloading SPA OS image as indicated in the message
Recommended Action none.
Error Message%L2-SPA-5-OS_IMAGE_ERROR Download SPA OS Image failed
Explanation Failed to download the SPA OS image.
Recommended Action none.
Error Message%L2-SPA-5-OS_IMAGE_SIZE_ERR SPA OS image exceeds RAM size: Image size ([dec]) Shared mem size ([dec])
Explanation The size of the SPA OS image is too big.
Recommended Action none.
Error Message%L2-SPA-5-PLIM_EVENT_INIT_ERR SPA Init Event Server failed
Explanation Creating SPA event handling server failed.
Recommended Action none.
Error Message%L2-SPA-5-PLIM_KA_INIT_ERR SPA Init SPA Keepavlie Handler failed
Explanation Creating SPA keepalive server failed.
Recommended Action none.
Error Message%L2-SPA-5-PLIM_RELOADING Reloading [chars] in subslot [unsigned int] after heartbeat failure ...
Explanation Reloading SPA because of heartbeat failure.
Recommended Action none.
Error Message%L2-SPA-5-STATE_CHANGE SPA in bay [dec] [chars]
Explanation For displaying state of a SPA
Recommended Action none.
Error Message
