Cisco IOS XR System Error Message Reference Guide, Release 3.8.1
Layer 2 Messages
Downloads: This chapterpdf (PDF - 1.32MB) The complete bookPDF (PDF - 31.25MB) | Feedback

Layer 2 Messages

Table Of Contents

Layer 2 Messages

10GE_PLIM Messages

ACCT_SVR Messages

ALPHA_TCAM Messages

ALPHA Messages

ASIC_ERRORS Messages

ASIC_SCAN_SERVER Messages

ATM_ILMI Messages

ATM_INARP Messages

ATM_NETIO Messages

ATM_OAM Messages

ATM_RM Messages

ATM_SAAR Messages

ATM_SOCKET Messages

ATM_SOP Messages

ATM_VCM Messages

atmdrv Messages

ATMGCMGR Messages

BFD Messages

BM_PD Messages

C12000_FR Messages

CCL Messages

CDP Messages

CEMA Messages

CHDLC_EA Messages

CHDLC_MA Messages

CHDLC_SOCK Messages

CHDLCDLL Messages

CHIPs Messages

d1qnetio Messages

DWDM Messages

E3EGRESSQ Messages

E3INGRESSQ Messages

E5EGRESSQ Messages

E5INGRESSQ Messages

EGRESSQ_HW_DLL Messages

EGRESSQ Messages

EMA Messages

ETHER_NETIO Messages

ether_spa_intr Messages

ether_spa_plugin Messages

ETHER Messages

FB_PLIM Messages

FB_SHIM_ENCAP Messages

FR_EDM Messages

FR_LMI Messages

FR_VCM_EA Messages

FR_VCM Messages

FWD_EDGE_COMMON Messages

GATM Messages

GDO Messages

GE_ASIC_PRP3 Messages

GE_ASIC Messages

GE Messages

GSR Messages

GT64115 Messages

gulf Messages

HALE_QOS Messages

HALE_TCAM Messages

HFA_COMMON Messages

HFA_LIB Messages

if_discovery Messages

IOB Messages

IPV6_EA Messages

JACKET Messages

L2C Messages

L2FIB_DEBUG Messages

L2FIB_LIB Messages

L2FIB_SHM Messages

L2FIB Messages

L2VPN_DEBUG Messages

L2VPN_PW Messages

L2VPN Messages

LACP_LITE Messages

MARVEL Messages

MICKEY Messages

MMSMLIB Messages

MOTHRA Messages

MOUSE Messages

MULTILINK_UV Messages

Multilink Messages

OC768_FRAMER_ASIC Messages

OPTICS Messages

PFILTER_EA Messages

PLAOC768_API Messages

PLAOC768 Messages

PLIM_4P_OC192 Messages

PLIM_ASIC_API Messages

PLIM_ASIC Messages

PLIM_FPGA Messages

PLIM_LIB Messages

plim_oc48 Messages

PLIM_OC768 Messages

PLIM Messages

pm5315 Messages

pm5316 Messages

PM622 Messages

PMSAR Messages

POS Messages

PPP_FSM Messages

PPP_GBL_CFG Messages

PPP_LCP Messages

PPP_MA Messages

PRECAM Messages

PSE Messages

PSELIB Messages

QM_E5 Messages

QM Messages

QUEUEING Messages

RSMLIB Messages

Serial Messages

SLARP_EA Messages

SLARP_LITE Messages

SLARP Messages

SLOGIC Messages

SONET_APS Messages

SONET_LOCAL Messages

SPA_192 Messages

SPA_C_SHIM Messages

SPA_CHOC_DSX Messages

SPA_ETHER Messages

SPA_FPD Messages

SPA_OC3_OC12 Messages

SPA_OC48 Messages

SPA_PLIM_SB Messages

SPA_T3E3 Messages

SPA Messages

SPAMSG Messages

SRP Messages

STP Messages

STREE Messages

TCAM_RM_CARVE_VERIFY Messages

TCAM_RM Messages

UDLD Messages

UIDB_RM Messages

VCM_CLIENT Messages

VCM_EA Messages

VCM Messages

vlan_netio Messages

vlea Messages

vlma Messages

VPA_RULES Messages

WAHOO Messages

XCONNECT Messages


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-STARTUP PLIM Process Error: [chars]

Explanation    The PLIM process failed to spawn correctly.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-10GE_PLIM-2-UNSUP This PLIM is no longer supported

Explanation    This PLIM is a prototype and is not longer supported

Recommended Action    No action is required.

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 a 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-2-XGXS_TX_SYNC An XGXS TX lane failed to syncronize for port [dec].

Explanation    The XGXS Tx Lanes failed to syncronize after a 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 Slot [dec], 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.

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.

ACCT_SVR Messages

Error Message     
 
    
    
   

%L2-ACCT_SVR-3-ERR_INIT init error: [chars] - restarting process to recover.

Explanation    The process acct_svr encountered a software error while initializing. The process is exiting and will be restarted. System will not be affected.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-ACCT_SVR-3-ERR_INTERNAL software internal error: [chars] - restarting process to recover.

Explanation    The process acct_svr encountered an internal error. The process is exiting and will be restarted. System will not be affected.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-ACCT_SVR-4-HFA_CLK_DELTA_FAIL HFA get clock delta has failed consecutively [dec] out of [dec] total times.

Explanation    The process acct_svr has failed to get the HFA clock delta for the given consecutive times. The flow report uses the forwarding asic clock which may be slightly off from the system clock. To correct the timestamp, the HFA clock delta is retrieve and on failure, the previously recorded delta is used. This log is printed out after so many consecutive failures to retrieve the clock delta, which may lead to skewed timestamps in the flow report.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-ACCT_SVR-7-ISR_FIFO_USAGE_FLAG ISR FIFO ring buffer usage is [chars] threshold ([dec]). direction: [dec] num_items equals [dec]

Explanation    The process acct_svr detected the condition of ISR FIFO ring buffer usage above or below the threshold. If the usage is above the threshold, the process acct_svr will bring the ISR FIFO ring buffer usage back to below the threshold after a while. Traffic will not be affected by this condition.

Recommended Action    No action is required.

ALPHA_TCAM Messages

Error Message     
 
    
    
   

%L2-ALPHA_TCAM-3-ERROR_MSG
[chars], rc equals [hex], [chars]

Explanation    This is a error message in the HFA Alpha driver to indicate tcam carving 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.

ALPHA Messages

Error Message     
 
    
    
   

%L2-ALPHA-3-ERR_ACCESS Memory access error: [chars]: Err equals [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 [chars] 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 equals [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 equals [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 equals [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     
 
    
    
   

%IP-STANDBY-6-INFO_STATECHANGE 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_ENCAP [chars] - [dec]: [chars] rc equals [hex] connid equals [dec] key equals [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 equals [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 equals [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 occurance equals [unsigned int] intr_status equals [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-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-ASYNC_DETECT_TIMER_FAULTY_EXPIRY BFD Async Detect timer expired for neighbor [chars] interface [chars] even when async pkt received within timer duration, timer_duration equals [unsigned int] ms, [unsigned int] ms elapsed since last async pkt received

Explanation    BFD Async Detect timer expired even when async pkt received within timer duration, timer_duration

Recommended Action    No action is required.

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 equals [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_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_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_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.

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.

Error Message     
 
    
    
   

%L2-BM_PD-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_PD-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.

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 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 name 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 node proc restart statsd_server location node If the message recurs, copy the error message exactly as it appears on 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 location of failure or proc restart ipv4_ma location location of failure

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 location of failure or proc restart ipv4_ma location location of failure

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 location of failure or proc restart ipv6_ma location location of failure

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 location of failure or proc restart ipv6_ma location location of failure

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 node proc restart statsd_server location node If the message recurs, copy the error message exactly as it appears on 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.

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 CH[hex]: 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 on CH[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 interface CH[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 location'. The command 'show process chdlc_socket location 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 CH[hex]: 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*

CHIPs Messages

Error Message     
 
    
    
   

%L2-CHIPs-2-error [chars]

Explanation    A high severity error has occurred in PLIM 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.

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 [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 [handle].

Recommended Action    Copy the error message exactly as it appears on 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.

DWDM Messages

Error Message     
 
    
    
   

%L2-DWDM-3-FATAL dwdm: fatal error encountered, reason equals [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 equals [chars], errno equals [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 equals [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.

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 [chars] (size [hex] addr [hex]) - [chars]

Explanation    The process could not map the egress asic 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_MEM_MQS_COUNTER_THR_EXCEEDED MQS counter utilization [dec] exceeds the high threshold of [dec]

Explanation    The multicast counter utilization has exceeded the high threshold. This may impact the delay and/or jitter of multciast traffic egressing out of this line card. The maximum counters available are 2048.

Recommended Action    Reduce the multicast traffic rate sent to this line card.

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.

Error Message     
 
    
    
   

%L2-E3EGRESSQ-6-ERR_MEM_MQS_COUNTER_THR_NORMAL MQS counter utilization [dec] within the low threshold of [dec]

Explanation    The multicast counter utilization has eased off to below the low threshold.

Recommended Action    No action required.

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-ERR_MEM_MQS_COUNTER_THR_EXCEEDED MQS counter utilization [dec] exceeds the high threshold of [dec]

Explanation    The multicast counter utilization has exceeded the high threshold. This may impact the delay and/or jitter of multciast traffic egressing out of this line card. The maximum counters available are 16384.

Recommended Action    Reduce the multicast traffic rate sent to this line card.

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.

Error Message     
 
    
    
   

%L2-E5EGRESSQ-6-ERR_MEM_MQS_COUNTER_THR_NORMAL MQS counter utilization [dec] within the low threshold of [dec]

Explanation    The multicast counter utilization has eased off to below the low threshold.

Recommended Action    No action required.

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.

EGRESSQ_HW_DLL Messages

Error Message     
 
    
    
   

%L2-EGRESSQ_HW_DLL-3-ENQ_PKT_LOGIC_ERROR Sharq ENQ packet logic error occurred, shq_enq_reg_debug_mux [hex]

Explanation    Egress Queue Manager encountered a ENQ packet logic error. Possible cause for this error condition is a faulty hardware.

Recommended Action    No action is 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-EGRESSQ_HW_DLL-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_HW_DLL-3-FAIL_TO_GET_BP_MAP_FROM_PLIM_AISC Failed to get backpressure map from Plim ASIC [dec]. reason [chars]

Explanation    Sharq driver invoke Plim ASIC dll to retrieve the per port backpressure map but failed.

Recommended Action    Please check Plim ASIC and related driver process status, Copy the error message exactly as it appears on 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_HW_DLL-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_HW_DLL-3-FORWARD_PACKET_TO_UNALLOCATED_QUEUE Forward 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, or asic reset or linecard reload.

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_HW_DLL-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_HW_DLL-3-NON_ZERO_Q0_COUNTER EgressQ detected packets sent to Illegal queue (counter value [hex])

Explanation    Egressq driver detected that packets are sent to Q0, which is invalid queue.

Recommended Action    If this message appears more than once in short period, Copy the error message exactly as it appears on 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_HW_DLL-3-QUEUE_STUCK EgressQ Stuck condition detected (PLIM link [dec], Port [dec], Group [dec], Queue [dec])

Explanation    Egressq driver detects the queue stuck condition (CSCsj48554). There is no packet output from one or more of the PLIM links and the queue length for related queue(s) is building up.

Recommended Action    By default, driver will perform the asic soft reset after detecting queue stuck condition. If this message appears more than once in short period, Copy the error message exactly as it appears on 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_HW_DLL-3-SBE_THRESHOLD_EXCEED Single Bit Error rate exceeded configured high threshold value: [chars]

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_HW_DLL-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_HW_DLL-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_HW_DLL-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_HW_DLL-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.

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-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.

EMA Messages

Error Message     
 
    
    
   

%L2-EMA-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-EMA-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-EMA-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-EMA-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.

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_intr Messages

Error Message     
 
    
    
   

%L2-ether_spa_intr-1-MAX_BURST_EVENT A Maximum burst of [chars] has occurred for [dec]/[dec]/[dec] [chars]

Explanation    A maximum burst of interrupts have occurred on the interface/ SPA. The interrupt in question has been permanently disabled. Manual intervention required to re-enable the interrupt.

Recommended Action    Copy the error message exactly as it appears on 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_spa_intr-6-BURST_EVENT Burst of [chars] occurred for [dec]/[dec]/[dec]. No Manual intervention required

Explanation    A burst of interrupts have occurred and the interrupt manager has throttled the interrupt. It will be re-enabled automatically after the pause timer expires and no further intervention is required.

Recommended Action    Copy the error message exactly as 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_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-LINK_EVENT Interface TenGige [dec]/[dec]/[dec], [chars]

Explanation    This will log the reason for the link to go 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-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-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.

FB_PLIM Messages

Error Message     
 
    
    
   

%L2-FB_PLIM-3-ERROR [chars]: [hex], [chars]

Explanation    An error occurred in 1p OC12-ch-ds1 PLIM process. This may cause features to not work 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-FB_PLIM-3-ERROR_NO_RC [chars]

Explanation    An error occurred in 1p OC12-ch-ds1 PLIM process, which might involve exiting the process. Some features may not work if this error 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-FB_PLIM-3-INIT_ERROR [chars]: [hex], [chars]

Explanation    An error occurred initialization of 1p OC12-ch-ds1 PLIM process, which will involve exiting the process and 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-FB_PLIM-3-ML_ERROR [chars]

Explanation    An error occurred in the 1p OC12-ch-ds1 Multilink platform dependent component. This may cause the multilink feature to not function properly.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-FB_PLIM-3-ML_PULSE_ERROR [chars]

Explanation    An error occurred in the 1p OC12-ch-ds1 PLIM multilink pulse message processing. This may cause the multilink feature to not function properly.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-FB_PLIM-4-WARNING [chars]: [hex], [chars]

Explanation    This is a warning message in the 1p OC12-ch-ds1 PLIM process 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.

FB_SHIM_ENCAP Messages

Error Message     
 
    
    
   

%L2-FB_SHIM_ENCAP-3-EINVAL [chars]: [hex], [dec]

Explanation    An invalid input condition detected.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-FB_SHIM_ENCAP-3-NO_SHIM [chars]: [hex]

Explanation    The SHIM information not found for the interface given.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-FB_SHIM_ENCAP-3-UNEXPECTED [chars]: [dec]

Explanation    Unexpected encap 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.

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_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 equals 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-FSM_T391_EXPIRY FSM in STOPPED state while timer is running: Interface [chars]

Explanation    This indicates that FSM has gone into an error condition. We should not have a valid timer expiry event if the FSM for this particular interface was in STOPPED 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-FR_LMI-3-IDB_INIT IDB initialization failure for [chars] - [chars]

Explanation    Interface creation within fr_lmi process failed for the named 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-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-IM_ERR [chars]

Explanation    Error in IM operation. Ex: Connection to IM not getting established, or some IM API errored out.

Recommended Action    Copy the error message exactly as it appears on 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-INVALID_VC An error occured while inserting the vc_idb into the tree, a invalid vc_idb(ifh [hex], dlci [dec]) exists

Explanation    Dangling VC found. Possible reasons: VC deletion failed in previous attempt or LMI did not get a deletion nfn from 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-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 equals 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_VCM_EA Messages

Error Message     
 
    
    
   

%L2-FR_VCM_EA-2-INIT FR VCM EA 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_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-DLCI_MATCH_FAILED Failed DLCI match, err: [chars]

Explanation    The FR VCM EA has a wrong value of the DLCI and is not the same as what the MA sends.

Recommended Action    Copy the error message exactly as it appears on 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.

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.

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 equals [hex] rc equals [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 equals [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.

GDO Messages

Error Message     
 
    
    
   

%L2-GDO-5-L2PORT_FAULT_NOTIFY [chars]

Explanation    ATM SPA GDO L-AIS insertion/removal notification messages

Recommended Action    *NONE*

Error Message     
 
    
    
   

%L2-GDO-7-DEBUG [chars]

Explanation    ATM SPA GDO L-AIS insertion/removal debug messages

Recommended Action    *NONE*

GE_ASIC_PRP3 Messages

Error Message     
 
    
    
   

%L2-GE_ASIC_PRP3-3-INIT_ERR GigE hardware initialization failed. Reason equals [chars], Error Decode equals [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.

Error Message     
 
    
    
   

%L2-GE_ASIC_PRP3-3-PKT_ERR GigE hardware packet error. Reason equals [chars]

Explanation    The GE hardware managment subsystem encountered an error during receiving of packets. 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

Recommended Action    Execute 'show process ge_mgmt' to verify that the process is up and running. If the message recurs, copy the error message exactly as 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 equals [chars], Error Decode equals [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.

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.

GSR Messages

Error Message     
 
    
    
   

%L2-GSR-3-ERR_MEM_ALLOC Memory allocation failed for internal data storage

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    Reload the LC using 'hw-module' command. If the problem recurs, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Also ensure the LC is populated with the minimum amount of memory required for proper operation.

Error Message     
 
    
    
   

%L2-GSR-3-ERR_SF_RESET [chars] : Hardware initialization of Fabric interface ASIC failed. Node will be reloaded for recovery after collecting diag information

Explanation    During boot-up or fabric configuration change or error handling, there was a problem in the initialization of fabric interface ASIC. Problem causes the node to be reloaded and will be restored by itself.

Recommended Action    Call your Cisco technical support representative and provide the gathered information. Node will be reloaded and restored in short time.

Error Message     
 
    
    
   

%L2-GSR-3-ERR_THREAD_CREATE Internal OS call to create additional threads failed, [chars]

Explanation    An internal OS library returned an error. The system will usually recover from this error automatically. If the frequency of this alert increases noticeably it could indicate a OS kernel problem on the card. The LC will not boot up successfully and will not be able to participate in data forwarding. This condition can impact various processes on the LC. The LC is in unstable condition.

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-GSR-3-ERR_THREAD_CREATE Internal OS call to create additional threads failed, [chars]

Explanation    An internal OS library returned an error. The system will usually recover from this error automatically. If the frequency of this alert increases noticeably it could indicate a OS kernel problem on the card. The LC will not boot up successfully and will not be able to participate in data forwarding. This condition can impact various processes on the LC. The LC is in unstable condition.

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.

Error Message     
 
    
    
   

%L2-GSR-3-FIA_CHKPT Call to checkpoint library failed, status equals [chars]

Explanation    An internal support library returned an error. The driver was not able to save data for restart ability. A restart of the FIAD process may not be NSF compliant. Any software upgrade requiring FIAD to be restarted will result in traffic loss. The system will usually recover from this error automatically. If the frequency of this alert increases noticeably it could indicate a OS kernel problem on the card.

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-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. This indicates a mismatch in the driver state. The checkpointed data may be corrupted on the LC. Restart ability of processes may be affected.

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-GSR-3-FIA_CHKPT_RECOVERY_NODATA The driver is coming up in restart 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. This can impact the drivers ability to restart without affecting traffic.

Recommended Action    The system may not recover from this error automatically. A reload of the linecard should be initiated in order to recover. Copy the error message exactly as it appears on 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_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. The LC will not boot up successfully and will not be able to participate in data forwarding.

Recommended Action    Copy the error message exactly as it appears on 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_ATTACH Internal OS call to process interrupts failed

Explanation    An internal OS library returned an error. Some error conditions on the LC may not be reported correctly. The system will usually recover from this error automatically. If the frequency of this alert increases noticeably it could indicate a OS kernel problem on the card.

Recommended Action    The system will normally recover from this error without intervention. This error indiactes a more fundamental issue on the LC. 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-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_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_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_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_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_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-FS_ERR1 [chars] : [hex]

Explanation    EE192 SerDes retimer driver error. An internal OS library returned an error. The system will usually recover from this error automatically. If the frequency of this alert increases noticeably it could indicate a OS kernel problem on the card. The LC will not boot up successfully and will not be able to participate in data forwarding. This condition can impact various processes on the LC. The LC is in unstable condition.

Recommended Action    The system will normally recover from this error without intervention. This error indiactes a more fundamental issue on the LC. If the frequency with which this error is occurring increases substantially, call your Cisco technical support representative and provide 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-ERR_SYSDB_SET system database item set failed [chars]

Explanation    Error in communication channel with the system database. There was a problem accessing the named item. This could be a temporary problem caused by an outage in the connection to the server. The connection will be restored, but the operation itself was aborted.

Recommended Action    Call your Cisco technical support representative and provide the gathered information. Copy the output of the following commands exactly as they appear. show processes fiad location X/X/X

Error Message     
 
    
    
   

%L2-GSR-4-FIA_EDM system database access failed [chars]

Explanation    Error in communication channel with clients. There was a problem accessing the system database item. This could be a temporary problem caused by an outage in the connection to the server. The connection will be restored, but the operation itself was aborted.

Recommended Action    Call your Cisco technical support representative and provide the gathered information. Copy the output of the following commands exactly as they appear. show processes fiad location X/X/X

Error Message     
 
    
    
   

%L2-GSR-6-FIA_INFO_MSG [chars]

Explanation    This is a Informational message in the FIA Driver to indicate an operation.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-GSR-6-FIA_PCDS_FAILURE [chars] failed, slot equals [dec], error info equals [chars]

Explanation    This is a message indicating FIA PCDS failure.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-GSR-6-PCDS_STATS_TIMESTAMP_FAILURE pcds_get_timestamp failed for fishstick stats

Explanation    This is a message indicating failed to get timestamp for fishstick stats.

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

Error Message     
 
    
    
   

%L2-GSR-7-FIA_FCTL [chars] failed, slot equals [dec], error info equals [chars]

Explanation    An interprocess call returned an error. Possibly a timeout. The central switch fabric software may not recognize the LC that exhibits this error. Maintenance bus may not be operating as desired.

Recommended Action    Look for other fctl messages. Wait for corrective 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 output of the following commands exactly as they appear. show processes fctl show processes fiad location X/X/X show diag X/X/X show diag chassis-info

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.

HALE_TCAM Messages

Error Message     
 
    
    
   

%L2-HALE_TCAM-3-ERROR [chars]: [chars]

Explanation    A SW exception occurred in TCAM extension Library

Recommended Action    If TCAM 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.

HFA_COMMON Messages

Error Message     
 
    
    
   

%L2-HFA_COMMON-3-FATAL_ERR Fatal error: [chars]: Err equals [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-4-ERR_LOCK [chars] error on [chars], rc equals [dec]

Explanation    An error occurred when un/locking HFA HW

Recommended Action    Copy the error message exactly as it appears on 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-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.

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-3-PLAT_UPD_FAILED Platform update failed: [chars] - [chars](CH[hex])

Explanation    Platform update 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-IPV6_EA-3-PLAT_UPD_FAILED_GL Platform update failed for [dec] interface: [chars] - [chars]

Explanation    Platform update failed for all interfaces in a batch.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

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_DISABLE [dec] requests to disable SPA [dec] due to spa bus error

Explanation    This is an error message indicating a Hardware access error for a SPA and disable the SPA to avoid LC reload

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-JACKET-3-SPA_PIO_ERROR SPA subslot [dec]: had [chars] error when accessing address [hex] with fault code [dec]

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-3-SPA_SELF_DESTRUCT [chars] has requested to disable SPA [dec] due to spa bus error

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.

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 inconsistent 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-3-ERR [chars]

Explanation    Some error occurred in operations related to L2FIB API 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-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-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-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-WAVL_ERR [chars] failed (tree equals [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-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.

Error Message     
 
    
    
   

%L2-L2FIB-6-GEN_INFO_ERR [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-L2FIB-6-XC_MOD XC/BP delete-and-create: [chars]

Explanation    The L2VPN provision message is handled by deleting old XC/BP, and creating a new one.

Recommended Action    None.

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-SANITY_ERROR Pseudowire Sanity check failed

Explanation    This is a fatal software error. It is probably a 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-L2VPN_PW-3-UPDOWN Pseudowire with address [chars], id [unsigned long int], state is [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-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-INTERNAL_ERROR L2VPN sanity check failed for Pseudowire ID [chars] pw-id [unsigned long int]: [chars]. Limit is [dec]

Explanation    An internal error has been encountered and the Pseudowire cannot be established.

Recommended Action    Please provide the exact error message seen on the console, collect a core dump of the running l2vpn_mgr process, and the show tech-support l2vpn output for further analysis of the error condition and potential recovery

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-4-BRIDGE_MTU_MISMATCH [chars] mtu of [dec] does not match bridge mtu of [dec]

Explanation    The interface MTU does not match the bridge payload MTU.

Recommended Action    Configure the bridge to match the interface MTU.

Error Message     
 
    
    
   

%L2-L2VPN-4-ENCAP_REMOVED_PW Pseudowire encapsulation is deleted, pseudowire attached with pw-class '[chars]' will become unresolved

Explanation    Encapsulation in the pw-class is deleted, all pseudowires attached with this pw-class will be unresolved as encapsulation type become not specified.

Recommended Action    Config the psedowire encapsulation in the pw-class and re-attach the pw-class to the pseudowires.

Error Message     
 
    
    
   

%L2-L2VPN-4-MAC_LIMIT_AC_SHUT Number of MAC addresses in AC '[chars]' has reached the configured MAC limit maximum and hence it has been shutdown

Explanation    Number of MAC addresses in the attachment circuit has reached the configured maximum. Since 'shut' action has been configured for MAC limit event on the port, it has been shut down.

Recommended Action    Manual intervention is required to bring the port up again. Please use 'clear l2vpn bridge-domain' command to bring the port up.

Error Message     
 
    
    
   

%L2-L2VPN-4-MAC_LIMIT_BD_SHUT Number of MAC addresses in bridge-domain '[chars]' has reached the configured MAC limit maximum and hence it has been shutdown

Explanation    Number of MAC addresses in the bridge-domain has reached the configured maximum. Since 'shut' action has been configured for MAC limit event on the bridge-domain, it has been shut down. All the ports under the bridge too are automatically shutdown.

Recommended Action    Manual intervention is required to bring the port up again. Please use 'clear l2vpn bridge-domain' command to bring the bridge-domain up.

Error Message     
 
    
    
   

%L2-L2VPN-4-MAC_LIMIT_PW_SHUT Number of MAC addresses in PW '[chars], [unsigned long int]' has reached the configured MAC limit maximum and hence it has been shutdown

Explanation    Number of MAC addresses in the pseudowire has reached the configured maximum. Since 'shut' action has been configured for MAC limit event on the port, it has been shut down.

Recommended Action    Manual intervention is required to bring the port up again. Please use 'clear l2vpn bridge-domain' command to bring the port up.

Error Message     
 
    
    
   

%L2-L2VPN-4-PROVISIONING_WARNING L2VPN sanity check failed for Attachment Circuit on node [chars]: [chars]. Limit is [dec]

Explanation    An internal error has been encountered and the Attachment Circuit cannot be established.

Recommended Action    Verify that the number of Attachment Circuits (AC) on the router does not exceed the L2VPN scaling capability for that line card. It may get resolved by removing the configuration for the ACs that are in UR or DN state including the ones identified in this message. Then re-configure the required ACs without exceeding the node limit.

Error Message     
 
    
    
   

%L2-L2VPN-5-NO_LICENSE L2VPN AC manager could not get a license for node [chars], [chars]

Explanation    License is required for L2VPN feature to work, but AC manager could not get a license for the node from License manager.

Recommended Action    Install license for the feature.

Error Message     
 
    
    
   

%L2-L2VPN-6-BRIDGE_MTU_MISMATCH_CLEAR [chars] mtu of [dec] now matches bridge mtu

Explanation    The interface MTU now matches the bridge payload MTU.

Recommended Action    No particular action is required.

Error Message     
 
    
    
   

%L2-L2VPN-6-ENCAP_REMOVED_PW_CLEAR Unresolved pseudowire encapsulation has been resolved for pw-class '[chars]'

Explanation    Encapsulation in the pw-class is set, all pseudowires attached to this pw-class should be out of the unresolved state.

Recommended Action    No particular action is required.

Error Message     
 
    
    
   

%L2-L2VPN-6-MAC_LIMIT_AC_CLEAR Number of MAC addresses in AC '[chars]' has gone below 75 percent of the configured MAC limit maximum, [chars]

Explanation    Number of MAC addresses in the attachment circuit has gone below 75% of the configured maximum. If MAC learning or/and unicast flooding was disabled on the port due to MAC limit action, then it would get re-enabled automatically.

Recommended Action    No particular action is required.

Error Message     
 
    
    
   

%L2-L2VPN-6-MAC_LIMIT_AC_SET Number of MAC addresses in AC '[chars]' has reached the configured MAC limit maximum, [chars]

Explanation    Number of MAC addresses in the attachment circuit has reached the configured maximum. If MAC limit action to disable MAC learning and unicast flooding has been configured on the port, then that particular action might have been taken automatically.

Recommended Action    No particular action is required.

Error Message     
 
    
    
   

%L2-L2VPN-6-MAC_LIMIT_BD_CLEAR Number of MAC addresses in bridge-domain '[chars]' has gone below 75 percent of the configured MAC limit maximum, [chars]

Explanation    Number of MAC addresses in the attachment circuit has gone below 75% of the configured maximum. If MAC learning or/and unicast flooding was disabled on the bridge-domain due to MAC limit action, then it would get re-enabled automatically.

Recommended Action    No particular action is required.

Error Message     
 
    
    
   

%L2-L2VPN-6-MAC_LIMIT_BD_SET Number of MAC addresses in bridge-domain '[chars]' has reached the configured MAC limit maximum, [chars]

Explanation    Number of MAC addresses in the bridge-domain has reached the configured maximum. If MAC limit action to disable MAC learning and unicast flooding has been configured on the port, then that particular action might have been taken automatically.

Recommended Action    No particular action is required.

Error Message     
 
    
    
   

%L2-L2VPN-6-MAC_LIMIT_PW_CLEAR Number of MAC addresses in PW '[chars], [unsigned long int]' has gone below 75 percent of the configured MAC limit maximum, [chars]

Explanation    Number of MAC addresses in the pseudowire has gone below 75% of the configured maximum. If MAC learning or/and unicast flooding was disabled on the port due to MAC limit action, then it would get re-enabled automatically.

Recommended Action    No particular action is required.

Error Message     
 
    
    
   

%L2-L2VPN-6-MAC_LIMIT_PW_SET Number of MAC addresses in PW '[chars], [unsigned long int]' has reached the configured MAC limit maximum, [chars]

Explanation    Number of MAC addresses in the pseudowire has reached the configured maximum. If MAC limit action to disable MAC learning and unicast flooding has been configured on the port, then that particular action might have been taken automatically.

Recommended Action    No particular action is required.

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.

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.

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.

MMSMLIB Messages

Error Message     
 
    
    
   

%L2-MMSMLIB-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*

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.

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.

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 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 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-INCORRECT_BW_UPDATE Bundle [chars] with bandwidth [dec]. Link ifh [hex] with bandwidth [dec]

Explanation    When the indicated member link was deactivated, bundle bandwidth could not be updated correctly as decrementing the link's bandwidth would have made the bundle bandwidth to go below zero. Bundle bandwidth is now made zero.

Recommended Action    Check the bundle and member interface status. Verify that the bundle bandwidth is correct now. If not, shut all the members of the bundle and then no shut all the members to bring back the bundle bandwidth to correct value.

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.

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.

PFILTER_EA Messages

Error Message     
 
    
    
   

%L2-PFILTER_EA-3-ERR_IM_CAPS [chars] acl failed on interface CH[hex]. [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-3-ERR_IM_CAPS [chars] acl failed on interface CH[hex]. [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-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.

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-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*

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_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_API Messages

Error Message     
 
    
    
   

%L2-PLIM_ASIC_API-7-ERR [chars] Reason:[chars]

Explanation    BAMBI API generated errors.

Recommended Action    No action is required.

PLIM_ASIC Messages

Error Message     
 
    
    
   

%L2-PLIM_ASIC-2-EIO_TRAIN PLASPA: [chars]

Explanation    EIO training errors. The EIO link to the PLASPA failed to train. This will result in traffic loss through this PLIM.

Recommended Action    Check seating of both the PLIM and the MSC and then reload the MSC. If the message recurs, copy the error message exactly as it appears on 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-ERR [chars]

Explanation    Plim asic driver errors. Typically these errors indicate failure in system services or bad programming of the hardware.

Recommended Action    Check whether process 'plaspa_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-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 'plaspa_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.

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_LIB Messages

Error Message     
 
    
    
   

%L2-PLIM_LIB-2-ERR_FM_REPLY Physical layer interface module library failed to reply to the Fault Manager for error recovery: [chars]

Explanation    The PLIM driver soft error recovery failed because the PLIM library function failed with replying to the Fault Manager request. If the PLIM soft error recovery failed, the PLIM hardware state may not be in the correct state, and the traffic may be affected. %s - is the decoded error reason

Recommended Action    The Fault Manager will reset the linecard if the error recovery failed, search through the event logs, if there is no any message indicating that the Fault Manager has reset the linecard, try to do a manually reset with CLI: 'hw-module location 0/x/cpu0 reload' If the message recurs, copy the error message exactly as it appears on 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-2-ERR_FM_REQUEST The Fault Manager cannot send message to physical layer interface module driver to start soft error recovery: [chars]/[chars]

Explanation    When a soft error is detected with any ASIC on the datapath, the Fault Manager will start the soft error recovery on the datapath. If the Fault Manager cannot send request to the PLIM driver, the soft error recovery will not be completed, therefore the traffic will not go through the datapath. %s - indicates the reason for the failure %s - is the decoded error reason

Recommended Action    The Fault Manager will reset the linecard if sending message failed, search through the event logs, if there is no any message indicating that the Fault Manager has reset the linecard, try to do a manually reset with CLI: 'hw-module location 0/x/cpu0 reload' If the message recurs, copy the error message exactly as it appears on 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-3-ERR_INIT Physical layer interface module library initialization failed: ([chars]/[chars]).

Explanation    The physical layer interface module (PLIM) library on the linecard failed to initialize. The PLIM library is used by PLIM driver which creates the SONET controller, POS interface, handling the all the SONET event and applying SONET/POS configuration to the layer1 devices. If the PLIM driver failed to initialize, no traffic will pass, therefore no higher level protocol will work. %s - indicates the reason for the failure %s - is the decoded error reason

Recommended Action    The System Manager process (sysmgr) will automatically respawn the PLIM process, up to a fixed number of times when this error is encountered, to recover. Execute the following command to verify that the process is up and running. 'show process process name location 0/x/cpu0' where process name equals 'e48_plim_oc3' for OC3 linecard; 'pl_e48_pos_4p_oc12' for OC12 linecard; 'pl_e48_pos_1p_oc48' for OC48 linecard; If it is still non-operational, try to do a manually process restart with CLI: 'process restart process name 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_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-4-ERR_MSG_RCV Physical layer interface module library failed in receiving the message: [chars]

Explanation    The PLIM library detects a failure condition when receiving the message. The message is used only for error recovery, the process should not receive the message in normal case. This error means a error condition is detected while the process is waiting for a message, it can be ignored if the error does not persist. Otherwise, if the error persists, it is recommended to restart the process, restarting process will not affect the traffic.

Recommended Action    If the error persists, execute the following command to restart the process. 'process restart process name location 0/x/cpu0' where process name equals 'e48_plim_oc3' for OC3 linecard; 'pl_e48_pos_4p_oc12' for OC12 linecard; 'pl_e48_pos_1p_oc48' for OC48 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-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.

Recommended Action    '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-2-EIO_TRAIN PLA: [chars], [chars]

Explanation    EIO training errors. The PLA EIO failed to train... this will result in traffic loss and the MSC will fail to send traffic thru the PLIM.

Recommended Action    Currently, the only recovery is for an MSC reload. Once the Fault-Mgr is available, the ASIC will be reset in order to retrain the EIO. If the message recurs, copy the error message exactly as it appears on 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-CHK_ERR PLA: [chars], [chars]

Explanation    Checkpoint Initialization Failure. The pla_server process failed to initialize its checkpointing data. The process cannot continue and needs to be restarted.

Recommended Action    None, the process should recover. If it does not, the system will most likely be in an unrecoverable state and will take appropriate action. If the message recurs, copy the error message exactly as it appears on 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-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 sh plim pla trace info sh plim pla trace error

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-INCONSISTENT_CONFIG [chars]

Explanation    As part of trying to configure dot1q vlan with vlan id same as that of outer vlan of QinQ configuration or vice versa on another sub-interface, then error has to be reported to remove the inconsistent config.

Recommended Action    Upon seeing this message, delete the subinterface that has just been created. Otherwise the system will be in inconsistent state.

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 sh plim pla trace info sh plim pla trace error

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

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.

PM622 Messages

Error Message     
 
    
    
   

%L2-PM622-2-error [chars]

Explanation    A high severity error has occurred in PLIM 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.

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.

Recommended Action    No action is required.

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_GBL_CFG Messages

Error Message     
 
    
    
   

%L2-PPP_GBL_CFG-4-ERR_INIT Failure during intialization of [chars]. Error: [chars]

Explanation    The PPP GBL CFG process failed to initialize 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.

PPP_LCP Messages

Error Message     
 
    
    
   

%L2-PPP_LCP-3-AAA_SESSION_CLEANUP_FAILED CH[hex]: Cleanup of a subscriber session has failed: [chars]

Explanation    A call to AAA to remove subscriber session state has failed. The error may cause the LCP session on the subscriber interface to be left permanently in what should be a transient unnegotiated state.

Recommended Action    To remove the stale sessions, run clear subscriber for this interface.

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 lower-layer 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-ERR_AAA_IEDGE_SESSION Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the AAA iEDGE service. The error message describes what operation has failed and why it failed. The most likely reason for this is that the AAA iEDGE server is unavailable. It may also be caused by low memory resource or a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. In many cases, PPP MA will recover by itself. If it does not then restarting the process should 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_LCP-4-L2_NOT_SUPPORTED L2 mode is not supported on CH[hex]

Explanation    L2transport has been configured on an interface that does not support it. The interface will not enter L2 mode, and will remain in whichever mode it was in before. This will occur if the interface capabilities do not support L2 mode, or if L2 mode is configured on a multilink bundle member.

Recommended Action    Reconfigure the interface so that l2transport is not enabled.

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 listname ...'

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-UNEXPECTED_AAA_RESPONSE CH[hex]: A response with unexpected properties has been received from AAA: [chars]

Explanation    AAA has sent a response which is unexpected or malformed in the way explained in the message. The error may cause the interface to be left in what should be a transient state permanently.

Recommended Action    Check the output of 'show ppp interface' for the interface with the problem. If the interface has been left permanently in an unauthenticated state, then it can be manually cleared using the 'clear subscriber' command. Note that if the interface has come up successfully then the unexpected AAA response will probably not have caused problems.

Error Message     
 
    
    
   

%L2-PPP_LCP-4-UNRECOGNIZED_PROTO Unrecognized IfMgr protocol [chars] on CH[hex] (caps equals [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 CH[hex]: Unable to complete LCP negotiations. Interface MTU on CH[hex] needs to be reconfigured taking into account the L2 headers to give an L3 MTU of 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, taking into account the Layer 2 headers. Once these headers have been subtracted, the Layer 3 MTU needs to be at least the value suggested in the message.

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_AAA_ATTR Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the AAA attribute service. The error message describes what operation has failed and why it failed. The most likely reason for this is low memory resource or a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. In many cases, PPP MA will recover by itself. If it does not then restarting the process should 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_AAA_ATTR_IF CH[hex]: Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the AAA attribute service for the interface specified. The error message describes what operation has failed and why it failed. The most likely reason for this is low memory resource or a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. In many cases, PPP MA will recover by itself. If it does not then restarting the process should 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_AAA_SESSION Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the AAA iEDGE service. The error message describes what operation has failed and why it failed. The most likely reason for this is that the AAA iEDGE server is unavailable. It may also be caused by low memory resource or a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. In many cases, PPP MA will recover by itself. If it does not then restarting the process should 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_AAA_SESSION_IF CH[hex]: Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the AAA iEDGE service for the interface specified. The error message describes what operation has failed and why it failed. The most likely reason for this is that the AAA iEDGE server is unavailable. It may also be caused by low memory resource or a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. In many cases, PPP MA will recover by itself. If it does not then restarting the process should 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_BACKEND Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the Backend service related to use of either SysDB or SubDB. The error message describes what operation has failed and why it failed. The most likely reason for this is low memory resources or a 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_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_DAPS Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the DAPS address pool 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 DAPS service, 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_DAPS_IF CH[hex]: Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the DAPS address pool 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 DAPS service, 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_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_IPCP_OPTS_INCONSISTENT CH[hex]: IPCP has negotiated inconsistent options: [chars]

Explanation    PPP MA has negotiated inconsistent IPCP options. The message details which options are inconsistent. IPCP will be brought up, but the inconsistencies could cause problems. The most likely reason for this is a misconfiguration, either locally or on the peer.

Recommended Action    Consider changing the relevant configuration either locally or on the peer.

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_IPCP_SCAN_IF CH[hex]: Failed to scan for configuration, continuing: [chars]

Explanation    PPP MA encountered an error when scanning for IPCP configuration. The error message describes what operation has failed and why it failed. The most likely reason for this is a connection problem with the SubDB service, 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_IPHC Unexpected IPHC error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error communicating with IPHC MA. 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 IPHC MA, 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_IPHC_CONFIG CH[hex]: Invalid IPHC config received: [chars]

Explanation    PPP MA received invalid or unsupported IPHC config for this interface. The error message describes which piece of config is invalid. The most likely reason for this is incorrect IPHC user configuration.

Recommended Action    Check that the IPHC user configuration is valid and supported.

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_L2VPN Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error communicating with the L2VPN 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 L2VPN 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_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_PLAT_PROPS Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error communicating with the Platform Properties DLL. The error message describes what operation has failed and why it failed. This will either have occurred because the Platform DLL failed to be properly initialized, or because of some error occurring in the platform dependent code.

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_RIB Unexpected error encountered whilst [chars]:

Explanation    PPP MA encountered an error using the RIB client library. The error message describes what operation has failed and why it failed. The most likely reason for this is a connection problem with the RIB, 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_SUBDB Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the SubDB 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 SubDB 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_SUBDB_IF CH[hex]: Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the SubDB 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 SubDB 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_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 Unexpected pthread error encountered for '[chars]' thread whilst [chars]: [chars]

Explanation    PPP MA encountered an unexpected error performing a pthread operation. 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_THREAD_COND Unexpected condition error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an unexpected error performing a condition operation. The process may 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_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_THREAD_MUTEX Unexpected mutex error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an unexpected error performing a mutex operation. The process may 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.

PRECAM Messages

Error Message     
 
    
    
   

%L2-PRECAM-2-HW_RESOURCE_FAILURE Failed to allocate hardware resources for feature [chars] on ifh [hex], subtype [dec], stage [chars], instance [chars], loc [dec], error: [dec] ([chars])

Explanation    A runtime error occurred while trying to allocate hardware resources for configuring a feature. The reason for the failure is also displayed.

Recommended Action    Please call Cisco Support with the error information and provide running configuration, configuration steps performed before the message was observed, linecard version and output of commands under: 'show controller pse [ingress|egress] precam ... ' Copy the error message exactly as 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-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-MIPC_STUCK [chars] direction. Data: ([chars])

Explanation    Inter-processor communcation to the Metro is stuck.

Recommended Action    *None*

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-3-INTERNAL_ERR Error: [chars]: Err equals [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 equals [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-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]) is not supported.

Explanation    This message indicates that the version of the PSE ASIC is a prototype, and it is not supported by the s/w release.

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-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-6-MP_INFO [chars] [chars]

Explanation    This is an informational message in the PSE Driver to indicate an event on maintenance processor.

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-3-SANITY_RELOAD [chars] : Card will be reset

Explanation    There is buffer depletion of FreeQs.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. This error message is just a warning message for Buffer Depletion. The card will be reloaded after the time specified in the message, if the problem persists. The dumped Queues and Queue Elements need to be evaluated to find the root-cause of the problem

Error Message     
 
    
    
   

%L2-QM_E5-3-SANITY_WARNING QM Buffer Depletion: [chars]

Explanation    There is buffer depletion of FreeQs.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. This error message is just a warning message. The dumped Queues and Queue Elements need to be evaluated to find the root-cause of the problem

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.

Error Message     
 
    
    
   

%L2-QM_E5-7-INTERRUPT5 [chars]: [chars]: error: [hex] 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.

Error Message     
 
    
    
   

%L2-QM_E5-7-INTERRUPT6 [chars]: [chars]: error: [hex] error_reg: [hex] error_info: 0x[unsigned int]llx

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-3-SANITY_RELOAD [chars] : Card will be reset

Explanation    There is buffer depletion of FreeQs.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. This error message is just a warning message for Buffer Depletion. The card will be reloaded after the time specified in the message, if the problem persists. The dumped Queues and Queue Elements need to be evaluated to find the root-cause of the problem

Error Message     
 
    
    
   

%L2-QM-3-SANITY_WARNING QM Buffer Depletion: [chars]

Explanation    There is buffer depletion of FreeQs.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. This error message is just a warning message. The dumped Queues and Queue Elements need to be evaluated to find the root-cause of the problem

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 equals [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.

RSMLIB Messages

Error Message     
 
    
    
   

%L2-RSMLIB-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*

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-3-NULL_HW_FUNC Detected NULL hw func ptr in Serial interface instance: [chars]

Explanation    Failed to program the hardware.

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.

Error Message     
 
    
    
   

%L2-SONET_LOCAL-5-AIS_PWFAULT [chars] [chars]

Explanation    L-AIS insertion/removal notification messages.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-SONET_LOCAL-6-CLEAR_COUNTERS Clear counters on [chars]

Explanation    Counters on a sonet controller has been cleared by the user. This message is for information only.

Recommended Action    None.

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_C_SHIM Messages

Error Message     
 
    
    
   

%L2-SPA_C_SHIM-3-GET_SHIM_INFO_FAIL Could not get shim info for ifh [hex]

Explanation    Could not get shim info for given interface handle

Recommended Action    If the message recurs, copy the error message exactly as it appears on 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_C_SHIM-3-NULL_SHIM_INFO Null shim info structure for ifh [hex]

Explanation    Null shim info encountered for given interface handle

Recommended Action    If the message recurs, copy the error message exactly as it appears on 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_C_SHIM-3-QUERY_FAIL c-shim query failed for ifh [hex]

Explanation    Unexpected c-shim query failure for given interface handle

Recommended Action    If the message recurs, copy the error message exactly as 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_CHOC_DSX Messages

Error Message     
 
    
    
   

%L2-SPA_CHOC_DSX-3-HDLC_ERR_CHNL_QUE_OV_STAT SPA [dec]/[dec]: [dec] [chars] events on HDLC Controller were encountered.

Explanation    The SPA driver detected an error event on the HDLC Controller

Recommended Action    The SPA driver has encountered an error event on the SPA card. If the condition persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. 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. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).

Error Message     
 
    
    
   

%L2-SPA_CHOC_DSX-3-NULL_PD_FIELD Null platform specific field for link [hex], ifname [chars]

Explanation    The platform specific name in the link record is not set.

Recommended Action    If the message recurs, copy the error message exactly as 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_ETHER Messages

Error Message     
 
    
    
   

%L2-SPA_ETHER-1-LTRACE_INIT_ERR [chars]

Explanation    Jacket process spawns the SPA process and waits for the initialization to complete. But initialization fails putting SPA into FAILED state. As a part of the above, we find the mesage Ltrace init failed message.

Recommended Action    If the issue occurs, Check the SPA state. If it is not OK, then collect the following traces 1) show plim jacket all location 2) show hw-module traces infra detailed location 3) show plim ether trace info/error location 4) console logs

Error Message     
 
    
    
   

%L2-SPA_ETHER-2-LTRACE_RETRY_ERR [chars]

Explanation    Jacket process spawns the SPA process and waits for the initialization to complete. But initialization fails putting SPA into FAILED state. As part of retry mechansim, the above message is seen.

Recommended Action    If the issue occurs, Check the SPA state. If it is not OK, then collect the following traces 1) show plim jacket all location 2) show hw-module traces infra detailed location 3) show plim ether trace info/error location 4) console logs

Error Message     
 
    
    
   

%L2-SPA_ETHER-2-SPA_CTX_ERR [chars]

Explanation    The spa_ether_ctx context data cannot be set.

Recommended Action    collect the trace log via 'show plim ether trace error location ' 'show plim ether trace info location ' 'show tech-support ethernet ' 'show plim jacket trace all location ' and collect console logs and send them to the Engineering team.

Error Message     
 
    
    
   

%L2-SPA_ETHER-2-SPA_JKT_ERR [chars] [chars]

Explanation    The Jacket driver failed to parse spa driver argument.

Recommended Action    --

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-3-INCONSISTENT_CONFIG [chars]

Explanation    As part of trying to configure dot1q vlan with vlan id same as that of outer vlan of QinQ configuration on other sub-interface, then error has to be reported to remove the inconsistent config.

Recommended Action    Upon seeing this message, delete the subinterface that has just been created. Otherwise the system will be in inconsistent state.

Error Message     
 
    
    
   

%L2-SPA_ETHER-3-PORT_DEL_TIMEOUT [chars] [dec]

Explanation    Port deletion failed to complete within the timeout period.

Recommended Action    Upon seeing this message collect the trace log via 'show plim ether trace error location ' 'show plim ether trace info location ' 'show tech-support ethernet ' and send them to the Engineering team.

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.

Error Message     
 
    
    
   

%L2-SPA_ETHER-4-PORT_DEL_WARNING [chars] [dec] [chars]

Explanation    Port deletion is taking longer time as there is large config to be deleted and so SPA driver prints out message every 2 min regarding the same.

Recommended Action    This is a warning message. Upon seeing this message, collect the following trace log via CLI 'show plim ether info location ' 'show plim ether error location ' 'show tech-support ethernet location ' 'show im trace location ' 'show cfgmgr trace location ' 'show vlan trace location all' Send them to the engineering team.

Error Message     
 
    
    
   

%L2-SPA_ETHER-4-WAIT_CONFIG [chars]

Explanation    During brinup of Wanphy SPA, the config has to be restored before init. With this we can decide whether to get SPA in LAN or WAN mode. This message indicates that config restore of wanphy is getting delayed

Recommended Action    No explicit action is required, if it gets delayed, SPA state machine would timeout and reload the SPA.

Error Message     
 
    
    
   

%L2-SPA_ETHER-6-PORT_DEL_INFO [chars] [dec] [chars]

Explanation    Port deletion happened after the threshold time.

Recommended Action    This is an informational message.Upon seeing this message collect the trace log via 'show plim ether trace error location ' 'show plim ether trace info location ' 'show tech-support ethernet ' and send them to the Engineering team.

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/cgi-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-3-ERR_IF [chars]

Explanation    The SPA driver on the linecard failed to call SONET controll or POS interface related system function. The issue may affect the creation of SONET controller or POS interface while the SPA is booting, reloading or SFP OIR with different optics rate. %s - error message indicating location and the reason of the error

Recommended Action    - Try to do the SFP OIR for a few more times; - If the issue persists, reload the SPA with the command: hw-module subslot 0/x/x reload then check if all the POS interface are created, if not, reload LC. If the message recurs, copy the error message exactly as it appears on 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_OC3_OC12-3-ERR_PLUGIN [chars]

Explanation    The operation on SPA object failed. The SPA driver controls all the hardware on the SPA. If the operation on SPA fails, the SPA may not be able to boot or work properly, and the traffic may be affected. %s - error message indicating location and the reason of the error

Recommended Action    The SPA infra will automatically restart the SPA driver up to a fixed number of times if the failure happens during SPA is booting. If the failure doesn't happen with SPA booting, manually SPA reload may be needed. Execute 'show platform' to verify the SPA is in READY state, if not, try to reload the SPA with command: hw-module subslot 0/x/x reload or if the system has no response to the command above, force to reload the SPA with follwoing sequence under config mode: hw-module subslot 0/x/x shutdown commit no hw-module subslot 0/x/x shutdown commit If the message recurs, copy the error message exactly as it appears on 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_OC3_OC12-3-ERR_RESTART [chars]

Explanation    There is an error detected during SPA process restart. During the process restart, the software will do: checking the hardware config compatibility; re-creating SONET controller and POS interface; restoring configurations. Any failure in above will cause restart failed. The traffic may or may not be affected after restart failed, but the further operation on SPA, e.g. changing configuration, may not be carried out properly. %s - error message indicating location and the reason of the error

Recommended Action    The system will try to restart the process again for a few times, If the issue persists, reload the SPA with the command: hw-module subslot 0/x/x reload If the message recurs, copy the error message exactly as it appears on 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_OC3_OC12-3-ERR_SFP [chars]

Explanation    There is an error detected during SFP initialization. SFP is the pluggable optics on the SPA, SFP initialization may happen when linecard boots up, SFP OIR and SPA process restart. SFP error is for any possible error during the initialization. The optics will not work if SFP OIR operation failed, therefore no traffic will be affected. %s - error message indicating location and the reason of the error

Recommended Action    - Check the SFP, make sure it is CISCO certified; - Try to do the SFP OIR for a few more times; - If the issue persists, reload the SPA with the command: hw-module subslot 0/x/x reload then test SFP OIR after SPA comes up. If the message recurs, copy the error message exactly as it appears on 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_OC3_OC12-6-INFO [chars]

Explanation    information message %s - message

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-6-OPTICS_OIR [chars]

Explanation    Optics module has inserted %s - message related to the SFP insertion event

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_DNLD_ERROR [chars][[dec]]: [chars] image download error ([chars])

Explanation    The FPD image download 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-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-SPA_FW_ERR [chars][[dec]] ([chars])

Explanation    The error message in parentheses is generated by SPA firmware for reason as mentioned in the error message. This error, and the message is logged by the plim holding the 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_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_T3E3 Messages

Error Message     
 
    
    
   

%L2-SPA_T3E3-6-SPA_RELOAD_INFO [chars] [dec] [chars] [chars] [chars] [chars]

Explanation    When the cardtype of T3E3 SPA is changed to T3 from E3 or vice versa, it undergoes a reload. A SPA reload is mandatory to have the newly configured cardtype in effect.

Recommended Action    This is an informational message indicating the T3E3 SPA will undergo a reload.

SPA Messages

Error Message     
 
    
    
   

%L2-SPA-3-BUS_FAILURE SPA ERR_L interrupt is asserted on subslot [unsigned int]

Explanation    SPA ERR_L interrupt is asserted by SPA when SPA bus protocol violation happens. This error happens mostly when there is an issue with hardware itself. The SPA reset is not going to recover the problem, hence SPA put into FAILED state.

Recommended Action    Replace SPA hardware or contact TAC to diagnoise the problem.

Error Message     
 
    
    
   

%L2-SPA-3-PLIM_HEARTBEAT_ERR [chars]: bay [dec] heartbeat missed, 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/cgi-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-POWER_FAILURE SPA_OK and PWR_OK signal is deasserted on subslot [unsigned int]

Explanation    SPA_OK and PWR_OK signal is asserted after the SPA is powered on by LC. These signals are deasserted when there is power failure on SPA and this failure indicates that it is SPA hardware issue. The SPA is put into FAILED state.

Recommended Action    Contact TAC to diagnoise the problem.

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] type [chars] [chars]

Explanation    For displaying state of a SPA

Recommended Action    none.

SPAMSG Messages

Error Message     
 
    
    
   

%L2-SPAMSG-3-ERR [chars]

Explanation    SPA related error msg

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPAMSG-6-INFO [chars]

Explanation    SPA related info

Recommended Action    none.

SRP Messages

Error Message     
 
    
    
   

%L2-SRP-3-ERR_DUP_MAC_ADDR [chars]: Duplicate mac addresses in topology

Explanation    Another node on the ring is using the same MAC address as this node. This can effect traffic forwarding.

Recommended Action    Correct the configuration of each node, where necessary, to ensure that each node uses a unique MAC address. Use the 'show srp topology' CLI to identify any nodes using the same MAC address.

Error Message     
 
    
    
   

%L2-SRP-3-ERR_MEDIA_SINGLE_RING [chars] SRR usage changed ([chars])

Explanation    SRR ring usage is changed using Inner, Outer or Both rings. There are/were multiple faults (or user requests) on the ring causing potential loss of traffic/bandwidth.

Recommended Action    Clear the cause of each fault/wrap on the ring. Use the 'show srp topology' CLI to identify which nodes are wrapped.

Error Message     
 
    
    
   

%L2-SRP-3-ERR_MEDIA_WRAP [chars] [chars] on side [char] ([chars])

Explanation    The specified side of the interface has wrapped or unwrapped for the given reason. There is/was a fault (or user request) on the ring causing potential loss of traffic/bandwidth.

Recommended Action    Clear the cause of the fault/wrap. Use the 'show srp ips' and 'show srp failures' CLI to determine the root cause of the fault (if still present).

Error Message     
 
    
    
   

%L2-SRP-3-ERR_SRR_VER_MISMATCH [chars] SRR version mismatch detected.

Explanation    SRR has detected incompatible versions with other nodes on the ring and cannot inter-operate.

Recommended Action    Update the software image on all nodes of the ring to the same SRR version.

Error Message     
 
    
    
   

%L2-SRP-6-INFO_SINGLE_NODE_TOPO [chars]: Single node in topology

Explanation    The topology discovery resulted in a single node being found. This is most likely a transient condition during initial ring bring-up.

Recommended Action    Verify that the condition is not transient by using 'show srp topology' CLI. Verify the interface is not physically looped back, meaning side A is connected to side B. Verify that the other nodes are not in PassThru mode (ADMIN DOWN). Verify that neither of the adjacent nodes have the same BIA address by using 'show interface srp' CLI. If a duplicate BIA address is found: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

STP Messages

Error Message     
 
    
    
   

%L2-STP-4-LOOP_INCONSISTENT STP moved port [chars] to Loop Inconsistent state

Explanation    STP Loopguard feature moves a non-designated port to Loop inconsistent state when it stops receiving bpdu's on this port.

Recommended Action    The problem might be due to software or hardware issues. Wait for a few minutes to see if problem clears or the port gets UDLD err-disabled. If not, file ddts with relevant info and continue. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-STP-6-LOOP_CONSISTENT STP moved port [chars] to Loop consistent state

Explanation    STP Loop inconsistency has been removed due to normal reception of bpdu's.

Recommended Action    No action is required.

STREE Messages

Error Message     
 
    
    
   

%L2-STREE-4-CONNECT_FAIL STP Server not available

Explanation    stp_process is most likely in a bad state or basic system services have failed. stp_process error messages are generally indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-STREE-4-CREATE_FAIL STP Create Failed : [chars]

Explanation    stp_process ran into errors while creating the spanning tree instance for control ethernet. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-STREE-4-MSGSEND_FAIL Message Send Failed : [chars]

Explanation    stp_process is most likely in a bad state or basic system services have failed. stp_process error messages are generally indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-STREE-4-PORT_CREATE_FAIL Stp port creation fail : [chars]

Explanation    Spanning tree port creation failed on the node. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Spanning tree port creation will be retried automatically. Check if the 'stp_process' is up and running if this error is encountered. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-STREE-4-SET_MACADDR_FAIL STP Set Mac Addr Failed : [chars]

Explanation    MAC address assigned to the spanning tree was either invalid or was not able to be set for the spanning tree instance. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-STREE-4-START_FAIL Failed to start STP instance : [chars]

Explanation    Spanning tree could not be started on the control ethernet for the node. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

TCAM_RM_CARVE_VERIFY Messages

Error Message     
 
    
    
   

%L2-TCAM_RM_CARVE_VERIFY-3-FATAL_ERR Fatal error: [chars]: Err equals [dec]

Explanation    A fatal error occurred in TCAM RM Carve Verify 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.

TCAM_RM Messages

Error Message     
 
    
    
   

%L2-TCAM_RM-3-BLWM_CLIENT_CONF_FAILED tcam_rm: blwm client configuration failed, error: [hex] [chars]

Explanation    Unable to configure BLWM client functionality.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-BLWM_CLIENT_REBIND_FAILED tcam_rm: blwm client rebind failed, error: [hex] [chars]

Explanation    Unable to rebind with BLWM client functionality after a connection reconnect.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-BLWM_FAILED_MSG_DUMP TCAM RM: [chars] [dec] REGN TYPE [chars] REG-ID [dec]
vmrid [hex] vmrid_p 0x[pointer],
rc [chars][[dec]]

Explanation    Dump of the value, mask, result, stage, region-id of MSG sent to the TCAM_RM server.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-BLWM_FAILED_MSG_MASK_DUMP TCAM_RM MASK: [hex]%02x[hex]%02x[hex]%02x[hex]%02x[hex]

Explanation    Dump of the mask MSG sent to the TCAM_RM server.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-BLWM_FAILED_MSG_RESULT_DUMP TCAM_RM RESULT: [hex]%02x[hex]%02x[hex]%02x[hex]%02x [hex]%02x[hex]%02x[hex]%02x[hex]%02x

Explanation    Dump of the result MSG sent to the TCAM_RM server.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-BLWM_FAILED_MSG_VALUE_DUMP TCAM_RM VALUE: [hex]%02x[hex]%02x[hex]%02x[hex]%02x[hex]

Explanation    Dump of the value MSG sent to the TCAM_RM server.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-BLWM_MSG_SEND_FAILED tcam_rm: blwm msg send/flush: retried: [dec] time(s), failed to send, error: [hex] [chars]

Explanation    Unable to send/flush a BLWM message to the TCAM_RM server.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-BLWM_RECVD_REPLY_FAIL tcam_rm: Received a failure reply code for a batched request type [dec], failed reason: [chars]

Explanation    This is the message printed by the default handler installed by TCAM_RM to process the replies received for batched requests. The default handler's behavior is to just print this message. The application should install its own handler to handle the replies to batched requests.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-FATAL_ERR Fatal error: [chars]: Err equals [dec]

Explanation    A fatal error occurred in TCAM RM which involves exiting the process.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-MSG_SEND_FAILED tcam_rm: msg: [dec], retried: [dec] time(s), failed to send, errno: [chars]

Explanation    Unable to send a message to the TCAM RM server.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-NONFATAL_ERR Nonfatal error: [chars]: Err equals [dec]

Explanation    This is a error message in the TCAM RM to indicate anomalies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temporary situation is resolved.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-RETURN_ERROR tcam_rm: TCAM returned [dec] ([chars]) because [chars]

Explanation    This is the message printed by the default handler installed by TCAM_RM to process the no memory reply received for batched requests. The default handler's behavior is to just print this message. The application should install its own handler to handle the replies to batched requests.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-3-TCAM_RM_RECVD_REPLY_NOMEM tcam_rm: TCAM could not satisfy allocation request, the node may not function as expected.

Explanation    This is the message printed by the default handler installed by TCAM_RM to process the no memory reply received for batched requests. The default handler's behavior is to just print this message. The application should install its own handler to handle the replies to batched requests.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-4-BLWM_REPLAY_REQUEST tcam_rm: Replaying a batched request of type [dec] that might have been partially processed before.

Explanation    Due to a server restart, a batched request might have been partially processed. The default handler installed by TCAM_RM simply replays the request. Applications that can not afford to replay a request should install their own handler.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-TCAM_RM-4-CACHE_ERR_COUNT tcam_rm: Client Cache Insert warning: Error Count:[dec] Cache Msg type:[dec] Request VMR id: [hex] Cache VMR id: [hex] VMR id pointer: 0x[pointer]

Explanation    If the error count is incrementing there is a discrepancy in the vmr_id pointer in the shared memory. These entries which are being merged do not have the same vmr_id and this can cause a potenital memory leak.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-4-CACHE_UNSUPPORTED_OP_SEQUENCE tcam_rm: prep request warning: prev msg code :[dec] curr msg code :[dec]

Explanation    If this error message is seen, the client of tcam_rm is attempting to send updates in an unsupported sequence.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-4-REPLY_HDLR_ERR_COUNT tcam_rm: Batch Reply Handler warning: Error Count:[dec] Cache Msg type:[dec] Req VMR id: [hex] Expected VMR id: [hex] Resp VMR id: [hex] Req VMR id pointer: 0x[pointer]

Explanation    If the error count is incrementing there is a discrepancy in the vmr_id pointer in the shared memory. These entries which are being merged do not have the same vmr_id and this can cause a potenital memory leak.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-TCAM_RM-5-PARITY_ERR Parity error corrected: ASIC Side equals [chars], TCAM Type equals [chars] TCAM Dev equals [dec], TCAM Offset equals [hex]

Explanation    This is an informational message from the TCAM RM to indicate that it received TCAM parity error Interrupt notification message and corrected the corrupted tcam cell offset through its shadow image.

Recommended Action    Monitor system for additional parity errors. If parity error recurs on this device, contact support.

Error Message     
 
    
    
   

%L2-TCAM_RM-6-INFO_MSG Info: [chars]

Explanation    This is an informational message in the TCAM RM.

Recommended Action    No action is required.

UDLD Messages

Error Message     
 
    
    
   

%L2-UDLD-4-DISABLE_PORT UDLD protocol detected Uni-directional link on [chars], Port Disabled

Explanation    UDLD protocol detects if a link is uni-directional and disables the port. Uni-directional links can cause problems in ethernet networks and should be fixed.

Recommended Action    Check the link on which the error happenned. Try replacing/reconnecting the GBIC/SFP/cable at either end of the link. Re-enable the port on the RP and see if the port comes up. If the problem still exists the port will be disabled again with 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.

UIDB_RM Messages

Error Message     
 
    
    
   

%L2-UIDB_RM-3-INIT_ERR Process initialization failed: ([chars]%s)

Explanation    The uidb-mgr-main process failed to initialize. A uidb is defined as a 'Micro Information Data-Base' used by the hardware ASIC's in the forwarding path. The uidb-mgr-main process is responsible for allocating/de-allocating the hardware uidb's as configured by sw. If the uidb manager fails to initialize, no interfaces can be created or deleted on the linecard. %s - indicates the reason for the failure. %s - is the decoded error reason.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process uidb_mgr_main location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart uidb_mgr_main location 0/x/cpu0'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

VCM_CLIENT Messages

Error Message     
 
    
    
   

%L2-VCM_CLIENT-1-COMM_ERR [chars] : [chars]

Explanation    Error in communication.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

VCM_EA Messages

Error Message     
 
    
    
   

%L2-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-VCM_EA-2-INTERNAL_ERR_2 [chars]: [chars]

Explanation    Internal error with error message.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

VCM Messages

Error Message     
 
    
    
   

%L2-VCM-2-IM_ATTR_ERR IM Attribute Error : [chars] : [dec]

Explanation    Error in IM Attribute 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-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-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.

vlan_netio Messages

Error Message     
 
    
    
   

%L2-vlan_netio-4-DEBUG_INIT_ERROR An error occurred during debug initialization (error: [chars])

Explanation    The VLAN 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.

vlea Messages

Error Message     
 
    
    
   

%L2-vlea-3-NATIVE_VLAN_NOTIF Failed to generate a notification for the Native VLAN (error: [chars])

Explanation    The VLAN EA process encountered a problem while trying to send a Native VLAN change notification. Native VLAN support for interfaces on the affected node may not function correctly.

Recommended Action    Restart the VLAN EA process on the affected node with process restart vlan_ea location (node). If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlea-3-NO_STATS VLAN EA failed to register with the statistics server (error: [chars])

Explanation    The VLAN EA process encountered an error while registering with the statistics server process. No VLAN sub-interface statistics will be gathered on the given linecard.

Recommended Action    This error message indicates a problem with in the statistics server process on the RP, or with the communications between the linecard and the RP. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlea-4-EVENT_BLOCK An error was received while waiting for an event (error: [chars])

Explanation    The VLAN EA process encountered an error while listening for events. The process will automatically restart and retry.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlea-4-IMP_CANT_REPLY Unable to reply to IMP (error: [chars])

Explanation    The VLAN EA process encountered an error processing a message from the IMP process, and is unable send a reply. This may be due to a low memory condition in which case the error code will indicate this.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%L2-vlea-4-IMP_REG_FAILED Failed to register for notifications with IMP, err: [chars]

Explanation    During initialization, the VLAN EA process attempted to register with the IMP process for a required service, but encountered an error. The VLAN EA process will automatically retry. Until it succeeds, VLAN functionality may not work on the affected 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-vlea-4-INIT_FAILED VLAN EA initialization failed: [chars] (error: [chars])

Explanation    The VLAN EA process failed to initialize. The process will automatically restart and retry. Until it succeeds, VLAN functionality may not work on the affected 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-vlea-6-NO_MEM Out of memory (failed attempt to reserve [unsigned int] bytes)

Explanation    The VLAN EA process was not able to allocate the memory that it needed to complete the operation. VLAN functionality on the affected node may be reduced until the problem is resolved.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

vlma Messages

Error Message     
 
    
    
   

%L2-vlma-3-BULK_IM_HANDLER_FAILED The handling of a bulk [chars] notification failed on [chars] for [dec] out of a batch of [dec] interfaces

Explanation    The VLAN MA process encountered an error while processing a batch of messages from Interface Manager about VLAN subinterfaces. The operation of VLAN subinterfaces on the specified node may be affected.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-3-BULK_IM_HANDLER_FAILED_ALL The handling of a bulk [chars] notification failed on [chars] for a batch of [dec] interfaces (all with error: [chars])

Explanation    The VLAN MA process encountered an error while processing a batch of messages from Interface Manager about VLAN subinterfaces. The operation of VLAN subinterfaces on the specified node may be affected.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-3-BULK_L2VPN_FAILED The handling of a bulk [chars] notification failed on [chars] for [dec] out of a batch of [dec] ACs

Explanation    The VLAN MA process encountered an error while processing a batch of L2VPN messages. L2VPN functionality on the affected node may be impaired.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-3-BULK_L2VPN_FAILED_ALL The handling of a bulk [chars] notification failed on [chars] for a batch of [dec] ACs (all with error: [chars])

Explanation    The bulk operation to process the L2VPN notification for a batch of sub-interfaces failed.

Recommended Action    The VLAN MA process encountered an error while processing a batch of L2VPN messages. L2VPN functionality on the affected node may be impaired.

Error Message     
 
    
    
   

%L2-vlma-3-BULK_L2VPN_FAILED_BATCH The handling of a bulk [chars] notification failed on [chars] for a batch of [dec] ACs (error: [chars])

Explanation    The VLAN MA process encountered an error while processing a batch of L2VPN messages. L2VPN functionality on the affected node may be impaired.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-3-IM_ATTR_MSG_FAILED Failed to generate an IM attribute notification on [chars] (error: [chars])

Explanation    The VLAN MA process encountered an error while sending information about subinterfaces to other processes in the system. The operation of VLAN subinterfaces on the affected node may be impaired.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-3-IM_CONNECT_FAILED Failed to connect to IM, err: [chars]

Explanation    The VLAN MA process failed to connect to the IM 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-vlma-3-IM_RESTART_RESYNC_FAILED Could not syncronize interface data for ([chars]) with IM (error: [chars])

Explanation    The VLAN MA process was not able to fully resynchronize its internal database with that of IM. This may cause some loss of VLAN functionality on the VLAN trunk interface on which the error occurred, and its subinterfaces.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-3-L2VPN_DISCONNECT_FAILED The handling of a L2VPN Mgr disconnect notification failed for [unsigned int] trunk interface(s). The first failure was on [chars] (with error: [chars])

Explanation    When the VLAN MA notices that it has lost its connection to the L2PVN Manager process, it needs to update its database to reflect this. This error message indicates that this the update failed. The only expected scenario that could cause the error is a low memory condition.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. *RECUR*

Error Message     
 
    
    
   

%L2-vlma-3-MAIN_INTF_INIT_FAILED Failed to perform initialization of trunk interface [chars], due to the following error: [chars]

Explanation    The VLAN MA process encountered a problem while setting up the specified trunk interface for VLAN operation. No sub-interfaces of the specified trunk interface can be created.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-4-ASYNC_HANDLER Couldn't install the default handler for async msgs, err: [chars]

Explanation    The VLAN MA process couldn't install the default event handler for async msgs.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-vlma-4-ATTR_NOTIF_LOST The IM attribute notification '[chars]' could not be processed (error: [chars])

Explanation    The VLAN MA process encountered an error while processing an attribute change (e.g. a MAC address change) related to an interface. The operation of VLAN subinterfaces on the specified node may be affected.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-4-BULK_IM_HANDLER_FAILED_BATCH The handling of a bulk [chars] notification failed on [chars] for a batch of [dec] interfaces, err: [chars]

Explanation    The VLAN MA process encountered an error while processing a batch of messages from Interface Manager about VLAN subinterfaces. The operation of VLAN subinterfaces on the specified node may be affected.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-4-EVENT_BLOCK An error was received while waiting for an event on the [chars] (error: [chars])

Explanation    The VLAN MA process encountered an error while listening for events. The process will automatically restart and retry.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-4-IM_HANDLER_FAILED The handling of a [chars] notification failed on [chars] due to error: [chars]

Explanation    The VLAN MA process encountered an error while processing a message from Interface Manager. The operation of VLAN subinterfaces on the specified node may be affected.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-4-INIT_FAILED VLAN MA initialization failed: [chars] (error: [chars])

Explanation    The VLAN MA process failed to initialize. Previous messages may give the reason. The process will automatically restart and retry. Until it succeeds, VLAN functionality may not work on the affected 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-vlma-4-RECOVERY_FAILED Failed to recover from resynchronization with another component for [chars], due to the error: [chars]

Explanation    The VLAN MA failed to resynchronize its configuration with another component in the system after an earlier failure, or process restart.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-vlma-6-NO_MEM Out of memory (failed attempt to reserve [unsigned int] bytes)

Explanation    The VLAN MA process was not able to allocate the memory that it needed to complete the operation. VLAN functionality on the affected node may be reduced until the problem is resolved.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%L2-vlma-6-UNKNOWN_NODE_VLAN_LIMIT Failed to determine the maximum number of VLAN sub-interface that are allowed to be configured on the given node (error: [chars])

Explanation    A failure occurred while trying to determine the maximum number of VLAN sub-interfaces that can be supported on the given node. The system may allow configuration of more VLAN sub-interfaces that can be supported, or may not allow the full number supported to be configured.

Recommended Action    After gathering the information specified, it may help to restart the VLAN MA process on the affected node, with proc restart vlan_ma location [location]. If this restart completes without the message appearing again, the problem has been resolved. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

VPA_RULES Messages

Error Message     
 
    
    
   

%L2-VPA_RULES-4-DEBUG_INIT_ERR [chars] [dec] [chars]

Explanation    Internal error. SPA rules library debug library initilization 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.

WAHOO Messages

Error Message     
 
    
    
   

%L2-WAHOO-3-ERR_ACCESS Memory access Error: [chars]: Err equals [dec]

Explanation    A memory access error occurred in programable switching engine (PSE) driver which involves exiting the process. %s - indicates the reason for the failure. %d - is the decoded error reason.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-WAHOO-6-INFO_MSG [chars] [chars] [chars]: [hex]

Explanation    This is an informational message in the programable switching Engine driver to indicate an operation. %s - indicates the PSE (RX/TX) information is about. %s - indicates the pipeline (0-3) information is about. %s - indicates the information message. %x - indicates the register value.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-WAHOO-6-INTERRUPT_INFO [chars]

Explanation    This is an informational message in the programable switching Engine driver to indicate an operation. %s - indicates the PSE (RX/TX) information is about. %s - indicates the information message.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-WAHOO-7-ERR_PIPE_STUCK Pipe stuck error: [chars]: Err equals [dec]

Explanation    An error occurred in programable switching engine (PSE) driver which indicates anomalies. Some of the messages may indicate a failure to allocate resources needed by applications. %s - indicates the reason for the failure. %d - is the decoded error reason.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-WAHOO-7-PAIR_PCR_REG
[chars] [chars] PAIR's PCR register status for pipe [dec]: [hex]

Explanation    An error occurred in programable switching engine (PSE) driver which indicates anomalies. Some of the messages may indicate a failure to allocate resources needed by applications.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-WAHOO-7-PAIR_REG
[chars] [chars] PAIR registers for pipe [dec]:pcr [hex] plu_pirl [hex] pirm1 [hex]
pirm2 [hex] pirh [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] lbl2_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] leaf2_word4 [hex] tcam_cont [hex]
ipv4/v6_dst_1 [hex] ipv4/v6_dst_2 [hex] ipv4/v6_dst_3 [hex] ipv4/v6_dst_4 [hex]
ipv4/v6_src_1 [hex] ipv4/v6_src_2 [hex] ipv4/v6_src_3 [hex] ipv4/v6_src_4 [hex]
mcast_info [hex] ipv6_info [hex] msq_data [hex]

Explanation    An error occurred in programable switching engine (PSE) driver which indicates anomalies. Some of the messages may indicate a failure to allocate resources needed by applications.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-WAHOO-7-PAIR_REG_LIST
[chars] [chars] PAIR registers for pipe [dec]:pcr [hex] plu_pirl [hex] pirm1 [hex]
pirm2 [hex] pirh [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] lbl2_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] leaf2_word4 [hex] cam_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-WAHOO-7-PHB_DUMP
[hex]: [hex] [hex] [hex] [hex]

Explanation    This is a error message in the programable switching Engine to indicate either anomolies which are not service impacting. Some of the messages may indicate a failure to allocate resources needed by applications.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

XCONNECT Messages

Error Message     
 
    
    
   

%L2-XCONNECT-3-ERROR [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-XCONNECT-3-init [chars]

Explanation    Some initialization function 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-XCONNECT-6-GENERIC [chars]

Explanation    Some generic errors.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.