Cisco IOS XR System Error Message Reference Guide, Release 4.3.x
Layer2 Messages
Downloads: This chapterpdf (PDF - 2.83 MB) The complete bookPDF (PDF - 18.29 MB) | Feedback

Table of Contents

Layer 2 Messages

10GE_PLIM Messages

ACCT_SVR Messages

ALPHA_TCAM Messages

ALPHA Messages

ASIC_ERRORS Messages

ASIC_SCAN_EXEC 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

B_SHIM_PARTNER Messages

BFD Messages

BGP_AD Messages

BM_PD Messages

BM Messages

BVI_MA Messages

C_SHIM_PARTNER Messages

C12000_FR Messages

CCL Messages

CDP Messages

CEM_PLATFORMS Messages

CEM Messages

CEMA Messages

CFM Messages

CFMMIB Messages

CHDLC_EA Messages

CHDLC_MA Messages

CHDLC_SOCK Messages

CHDLCDLL Messages

CHIPs Messages

CHNLZD_EFCM Messages

COMMS Messages

CPP_EXMEM Messages

cpp_sbs Messages

CPP_TCAM_RM Messages

CPPHA Messages

cpposlib Messages

CRS_PAK_BUFHDR Messages

d1qnetio Messages

DATAPATH_FPGA_API Messages

DIV2_DM Messages

DRIVERS_UTIL Messages

DWDM Messages

E3EGRESSQ Messages

E3INGRESSQ Messages

E5EGRESSQ Messages

E5INGRESSQ Messages

edge_l2fwd_rewrite Messages

edge_l2fwd_table Messages

EGRESSQ_HW_DLL Messages

EGRESSQ Messages

ELMI Messages

ELO_COMMON Messages

ELO Messages

ELOGM Messages

EMA Messages

EPI Messages

eth_gl Messages

ETHER_NETIO Messages

ether_spa_dwdm Messages

ether_spa_intr Messages

ether_spa_mac_error Messages

ether_spa_plugin Messages

ETHER Messages

ETHERNET Messages

FB_PLIM Messages

FB_SHIM_ENCAP Messages

FHRP_COMMS Messages

FIB_IPV4 Messages

FIB_IPV6 Messages

FIB_MPLS Messages

FR_EDM Messages

FR_INARP Messages

FR_LMI Messages

FR_NETIO Messages

FR_SFRAR Messages

FR_SOCKET Messages

FR_UV Messages

FR_VCM_EA Messages

FR_VCM Messages

FRMIB Messages

FSYNC Messages

FWD_EDGE_COMMON Messages

G709 Messages

G8032 Messages

GATM Messages

GDO Messages

GE_ASIC_PRP3 Messages

GE_ASIC Messages

GE Messages

GSR_aib Messages

GSR_edge_fwd_lib Messages

GSR Messages

GT64115 Messages

gulf Messages

HALE_MQS Messages

HALE_QOS Messages

HALE_REPLICORD Messages

HALE_TCAM Messages

HALE_TLU Messages

HFA_COMMON Messages

HFA_LIB Messages

if_discovery Messages

IGMPSN_POLICY Messages

IGMPSN Messages

IMA Messages

IMACTRLR Messages

IOB Messages

IPV6_EA Messages

IXP2800_FWD Messages

IXP2800_HW Messages

IXP2800_SERVICE Messages

JACKET Messages

JDAM Messages

L2C Messages

L2FIB_DEBUG Messages

L2FIB_LIB Messages

L2FIB_SHM Messages

L2FIB Messages

L2TP Messages

L2VPN_DEBUG Messages

L2VPN_MA_PWHE Messages

L2VPN_MA Messages

L2VPN_PW Messages

L2VPN_PWHE Messages

L2VPN Messages

LACP_LITE Messages

LI_EA Messages

MARVEL Messages

METRO_STATS_API Messages

METRO_STATS Messages

MFR_EA_LTRACE_DLL Messages

MFR_EA_LTRACE Messages

MFR_EA Messages

MFR_MA Messages

MICKEY Messages

MLCTRLR Messages

MMSMLIB Messages

MOTHRA Messages

MOUSE Messages

MRP_MAD Messages

MULTILINK_UV Messages

Multilink Messages

MVRP Messages

ND Messages

OAMMIB Messages

OC768_FRAMER_ASIC Messages

OPTICS Messages

OTN_DRIVER Messages

PAL_CGM Messages

PAL_IPHC Messages

PFILTER_EA Messages

PLAOC768_API Messages

PLAOC768 Messages

PLAT_L2FIB_VPLS Messages

PLATFORM_ATM_OAM Messages

plim_4p_oc12 Messages

PLIM_4P_OC192 Messages

PLIM_ASIC_API Messages

PLIM_ASIC Messages

PLIM_CLKSEL Messages

PLIM_ETHER Messages

PLIM_FPGA Messages

PLIM_IOX_4P_GE Messages

PLIM_LIB Messages

plim_oc48 Messages

PLIM_OC768 Messages

PLIM Messages

pm5315 Messages

pm5316 Messages

PM622 Messages

PMSAR Messages

POS Messages

PP_CNSMR Messages

PPP_EA Messages

PPP_FSM Messages

PPP_GBL_CFG Messages

PPP_LCP Messages

PPP_lite Messages

PPP_MA Messages

PPP_NETIO Messages

PPP_SOCK Messages

PRECAM Messages

PREFIX_COMPR Messages

PSE_UIDB Messages

PSE Messages

PSELIB Messages

PTP Messages

PVSTAG Messages

QFP_ACL_EA Messages

QFP_BQS Messages

QFP_DRIVER Messages

QFP_EXMEM Messages

QFP_FM_LIB Messages

QFP_FM Messages

QFP_IFM Messages

QFP_LPTS_EA Messages

QFP_MDM Messages

QFP_PFILTER_EA Messages

QFP_SBS Messages

QFP_TCAM_RM Messages

QFP_UIDB Messages

QFP_XCONNECT Messages

QM_E5 Messages

QM Messages

QUEUEING Messages

RSMLIB Messages

Serial Messages

SLARP_LITE Messages

SLOGIC Messages

SONET_APS Messages

SONET_LOCAL Messages

SPA_192 Messages

SPA_ATM_V2 Messages

SPA_C_SHIM Messages

spa_cema_platform Messages

SPA_CHOC_DSX Messages

SPA_ETHER Messages

SPA_FPD Messages

SPA_OC3_OC12 Messages

SPA_OC48 Messages

SPA_PD_CEM Messages

SPA_PLIM_SB Messages

SPA_T3E3 Messages

SPA Messages

SPABRG Messages

SPAMSG Messages

SPAN Messages

SPU_LIB Messages

SPU Messages

SRP Messages

SSRP Messages

STP_IO Messages

STP_LIB Messages

STP Messages

STREE Messages

T1E1_LNM Messages

T1E1 Messages

T3E3 Messages

TCAM_RM_CARVE_VERIFY Messages

TCAM_RM Messages

UDLD Messages

UIDB_RM Messages

VCM_EA Messages

VCM Messages

VIF_MA_DEBUG Messages

VIF_MA_MSG Messages

vlan_netio Messages

vlea Messages

vlma Messages

VPA_1P_OC192 Messages

VPA_8P_GE Messages

VPA_RULES Messages

VPLS Messages

WAHOO Messages

WAN_INARP Messages

WAN_LIB_IFDB Messages

WAN_LIB_VCC Messages

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

10GE_PLIM Messages

Error Message %L2-10GE_PLIM-2-RX_FAULT

Interface [chars], Detected RX Fault

Explanation The PLIM received an Rx 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 Suggest running diags to determine which part of the Rx path is broken and potentially RMA to replace the bad hardware.

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 synchronize for port [dec].

Explanation The XGXS Rx Lanes failed to synchronize 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 synchronize for port [dec].

Explanation The XGXS Tx Lanes failed to synchronize 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-FAULTY_XFP

Port [dec], XFP unable to reach ready state, powering off

Explanation The XFP inserted encountered a fault condition when powering on.

Recommended Action Verify the XFP is supported in the hardware manuals and is inserted correctly.

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-4-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-4-RX_RF

Interface [chars], [chars]

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

Error Message %L2-10GE_PLIM-6-UNSUPPORTED_XENPAK

Port [dec], Unsupported Xenpak inserted

Explanation The Xenpak inserted in the given interface is not supported on this PLIM.

Recommended Action Verify the Xenpak is supported in the hardware manuals

Error Message %L2-10GE_PLIM-6-UNSUPPORTED_XFP

Port [dec], Unsupported XFP inserted

Explanation The XFP inserted in the given interface is not supported on this PLIM.

Recommended Action Verify the XFP is supported in the hardware manuals

Error Message %L2-10GE_PLIM-6-XFP_OIR

Optic Interface Module [chars] for port [dec]

Explanation The Optic Interface Module (XFP) for the specified port has either been inserted or removed.

Recommended Action No action is required.

Error Message %L2-10GE_PLIM-6-XFP_RETRY_READ

Port [dec], Retrying XFP EEPROM read : (retry_count [dec])

Explanation The Reading of XFP EEPROM failed; Retry is attempted

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 The process will be restarted automatically to recover.

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-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 The process acct_svr will automatically be restarted to recover.

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

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 If the message recurs, copy the error message exactly as 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_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 Reload of LC will be 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.

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. This error may occur during the error recovery mechanism for programmable switching engine (PSE) while HFA Alpha driver fixes the parity errors in the memories after restart of the PSE.

Recommended Action If the message recurs, copy the error message exactly as it appears on 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-5-THREAD_INFO_MSG

Previous Count: [unsigned int], current Count: [unsigned int].

Explanation This is an informational message when the thread 20 count is incrementing. If it is seen continuously, it indicates hardware issue. Or else, it is safe to ignore. %u - indicates previous thread 20 count. %u - indicates current thread 20 count.

Recommended Action Please refer to the following link. http://zed.cisco.com/confluence/display/GSRTR/Debugging+Thread_20+Count-+precam1_profile_drop_count

Error Message %L2-ALPHA-6-TUPLE_WARNING

7 Tuple L4 LBA not supported on E3, will continue to load balance using L3 LBA

Explanation This is a informational message in the programable switching Engine driver to indicate that Alpha doesn’t support 7 tuple and hence will continue forwarding with L3 LBA.

Recommended Action None.

Error Message %L2-ALPHA-6-VERSION_WARNING

[chars] [chars] error [hex]

Explanation This is an informational message in the programable switching Engine driver to indicatng unsupported version of programmable Switching engine (PSE) for some features. %s - is the warning message. %s - is the decoded warning reason. %x - is the decoded error code.

Recommended Action Debug message only. 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 Debug message only. No action is required.

Error Message %L2-ALPHA-7-PHB_DUMP


[hex]: [hex] [hex] [hex] [hex]

Explanation This is a debug message to display PHB dump of programable switching engine (PSE).

Recommended Action Debug message only. No action is required.

Error Message %L2-ALPHA-7-REG_DUMP


[chars]
cpu_int [hex] cpu_mask_int_reg [hex] error_addr_reg [hex]
error_data_hi_reg [hex] error_data_lo_reg [hex] error_parity_reg [hex]
fs_error_reg [hex] pf_err_reg [hex] prep_int_status_reg [hex]
prep_pc_reg [hex] pc1_status_reg [hex] plu_int_reg [hex]
plu_int_en_reg [hex] plu_err_en_reg [hex] plu_ecc_error_reg [hex]
plu_ecc_syndrome_reg [hex] tlu_int_reg [hex] tlu_sdram_adr_err_reg [hex]
tlu_sdram_ecc_syndrome_reg [hex] mip_int_status_reg [hex] mip_pc_reg [hex]
pc2_status_reg [hex] pst_status_reg [hex] cam_status_reg [hex]
nf_stat_reg [hex] pop_int_status_reg [hex] pop_pc_reg [hex]
ssram_adr_err_reg [hex] ssram_err_data_reg [hex] pl_pipeline_ctl_reg [hex]
pl_aa_pak_avl_1_reg [hex] pl_aa_end_reg [hex] pl_aa_fatal_err_reg [hex]
gather_int_stat_reg [hex] xbm_read_status_reg [hex] xbm_rcl_w_status_1_reg [hex]
xbm_rcl_w_status_2_reg [hex] xbm_rcl_r_status_reg [hex] xbm_tail_w_status_1_reg [hex]
xbm_tail_w_status_2_reg [hex] xbm_tail_w_status_reg [hex] xbm_control_status_1_reg [hex]
xbm_control_status_2_reg [hex] fs_pcr_reg [hex] prep_pair_reg[0] [hex]
plu_pcr_reg [hex] pc1_pcr_reg [hex] tlu_pcr_reg [hex]
dummy_pcr_reg [hex] mip_pair_reg[0] [hex] pc2_pcr_reg [hex]
cam_match_pcr_reg [hex] pst_pcr_reg [hex] pop_pair_reg[0] [hex] gather_pcr_reg[hex]

Explanation This is a debug message to display registers of programable switching engine (PSE).

Recommended Action Debug message only. No action is required.

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

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

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

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*

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

Error Message %L2-ASIC_SCAN_EXEC-2-START

[chars]: sending request to asic scan server...

Explanation This is informational message indicating that the ASIC SCAN is started from CLI.

Recommended Action Copy the error message exactly as 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_SCAN_SERVER Messages

Error Message %L2-ASIC_SCAN_SERVER-2-COMPLETE

ASIC Scan is completed successfully.

Explanation Informational message indicating the ASIC SCAN is completed.

Recommended Action No action is required.

Error Message %L2-ASIC_SCAN_SERVER-2-EXIT

ASIC Scan Server exits after a successful scan

Explanation ASIC scan server exits, expected behavior.

Recommended Action No action is required.

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-2-START

ASIC Scan is started.

Explanation Informational message indicating the ASIC SCAN is started.

Recommended Action No action is required.

Error Message %L2-ASIC_SCAN_SERVER-2-XSVF_ERROR

[chars]

Explanation ASIC scan server xsvf execution encountered an error condition, usually this could be caused by hardware failure in JTAG chain.

Recommended Action If the message recurs, copy the error message exactly as it appears on 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_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_GET_CARD_TYPE

ASIC Scan Server failed to get the card type: Reason equals [chars].

Explanation ASIC scan server has failed to get the card type. This would result in termination of the server 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(Interface Manager) operation first %s - Type of the failure second %s - Interface/PVC which failed the lookup This erro happens on an LC with ATM interfaces

Recommended Action Check if the interface or pvc exists and retry the operation. Copy the error message exactly as it appears on 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. first %s - Type of failure second %s - reason for failure

Recommended Action Action to be taken based on the error message. In case of initilization/registration failures. Restart the atm_ilmi process for recovering Copy the error message exactly as it appears on 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. The datatype sent by sysdb is invalid w.r.t atm_ilmi %s - invalid datatype that we received

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. process restart of atm_ilmi. If that does not recover spa/plim reload.

ATM_INARP Messages

Error Message %L2-ATM_INARP-2-INTERNAL_ERR

[chars] : [chars]

Explanation Internal error.

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

Error Message %L2-ATM_INARP-2-NOMEM

Operation failed due to memory shortage, function: [chars]

Explanation Memory on the box is critically low.

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

ATM_NETIO Messages

Error Message %L2-ATM_NETIO-3-CARD_DLL

Failed to open card specific dll [chars]

Explanation Card specific dll may not be present

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

Error Message %L2-ATM_NETIO-3-INSERT_DICT

Insertion to ATM Netio Dictionary fails

Explanation The env variable setting may not be set up for load path variable

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

Error Message %L2-ATM_NETIO-3-INVALID_DLL

DLL not found for the specified card : [chars]

Explanation Check the installation Dlls missing from package

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

Error Message %L2-ATM_NETIO-3-LOAD_PATH

Failed to get load path env variable for dll [chars]

Explanation The env variable setting may not be set up for load path variable

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

Error Message %L2-ATM_NETIO-3-MEMORY

Failed to malloc [unsigned int] bytes

Explanation The DLL has failed to acquire the required amount of memory.

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

Error Message %L2-ATM_NETIO-3-PARSE_FAILURE

Failed to parse atm_netio.rules at line: [chars]

Explanation The file atm_netio.rules has been modified and parsing fails

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

Error Message %L2-ATM_NETIO-3-PARSER_NULL_PATH

Path to load the atm_netio.rules is NULL

Explanation The path to atm_netio.rules file cannot be located.

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

Error Message %L2-ATM_NETIO-6-DEBUG_REG

Debug registration failed: [chars]

Explanation Debug message registration failed

Recommended Action No action is required.

ATM_OAM Messages

Error Message %L2-ATM_OAM-2-IM_ERR

[chars] : [chars]

Explanation Error in IM(Interface Manager) operation %s - Type of error %s - reason for the error This error happens on the LC with ATM interfaces

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

Error Message %L2-ATM_OAM-2-INTERNAL_ERR

[chars] : [chars]

Explanation Internal error. %s - Failure %s - ifhandle/interface_name/function name This happens on the LC with ATM interfaces

Recommended Action Copy the error message exactly as 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_oam is not the owner of anything. Process restart of atm_oam will recover the issue

Error Message %L2-ATM_OAM-2-SYSDB_ERR

[chars]

Explanation Error in sysdb operation. %s - Type of the error. This error happens on the LC with ATM interfaces

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Error in the config that is being committed. Check the configuartion and change it according to the error.

ATM_RM Messages

Error Message %L2-ATM_RM-1-SYSDB_ERR

[chars] : [chars]

Explanation Error in sysdb operation. Error while setting the value in sysdb. first %s - type of the error second %s - reason of the 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. retry the commit operation of the failed tuple based on the error message

Error Message %L2-ATM_RM-2-INTERNAL_ERR

[chars] : [chars]

Explanation A critical function failed that expected to succeed. first %s - type of error second %s - reason for the error

Recommended Action Restart the atm_vcm process. Initialization failure will lead to lot of other errors. Copy the error message exactly as it appears on 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. %d - amount of memory that is tried to be allocated

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. LC reload alone can recover from this situation. All info to be collected before the reload.

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 %s - gives the name of the interface %u - gives the available bandwidth size %u - gives the bandwith that failed to apply

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. first %s - type of failure second %s - reason for the failure.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. If the error is during the initialization, restart the process. For memory related errors, reload the LC.

Error Message %L2-ATM_SOCKET-2-NOMEM

Allocation of [dec] bytes failed due to memory shortage

Explanation Memory on the router is critically low. %d - amount of memory that was tried to be allocated.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. LC reload alone will recover the situation. All information to be collected before the reload

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. %s - reason for failure.

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

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 %s - Error message %d - Interrupt %s - Data1 %s - Data2 %s - Data3

Recommended Action If the message recurs, copy the error message exactly as it appears on 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 %s - Debug message %lx - Asic %x - Data1 %x - Data2

Recommended Action No action is required.

ATM_VCM Messages

Error Message %L2-ATM_VCM-2-IM_ERR

[chars] : [chars]

Explanation Error in IM(Interface Manager) operation first %s - Failure second %s - reason for the failure This happens on the LC with ATM interfaces

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Either caps addition or removal failed. Depending on the failure, reapply the configuration.

Error Message %L2-ATM_VCM-2-INTERNAL_ERR

[chars] : [chars] : [chars]

Explanation Internal error. Type of error and reason will be there in the msg %s - ifhandle/ name of errored interface %s - Type of the error occured %s - Reason for the error This happens on the LC with ATM interfaces

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. Most of the errors are because of low memory. Others are not very critical. LC reload will resolve the low memory condition. Information to be collected before the reload

Error Message %L2-ATM_VCM-2-SYSDB_ERR

[chars]

Explanation Error in initialization of verification functions with Sysdb or the registration of the debug %s - reason for the error. This error happens on the LC with ATM interfaces

Recommended Action Restart the atm_vcm process to recover 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 PLIM Drivers for the ATM have encountered an error.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. If you cannot determine the nature of the error from the error message text, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-atmdrv-2-ERR

[chars], [dec] error, reason:[chars]

Explanation atmdrv generic error

Recommended Action Copy the error message exactly as it appears on the console or in the system log. If you cannot determine the nature of the error from the error message text, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-atmdrv-2-ERR

error, reason:[chars]

Explanation GSR SPA Driver encountered an error while bringing up the SPA devices. %s - Error message

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 error occurred while updating the canonical header for a connection.

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_STS

[chars] - [dec]: [chars] (rc equals [hex])

Explanation atmdrv error occurred when initializing any of the devices in E3 ATM card or while programming a VC.

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

Explanation GSR SPA Driver encountered an error while initializing the SPA device. %s - Error message %x - Error Code

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-2-ERR_VC

[chars] - [dec]: [chars] (connid equals [dec])

Explanation atmdrv error occurred when trying to add, modify or delete a VC. The error can be returned from the SAR or the CPK Asic.

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-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-4-warning

[chars], [dec] warning, reason:[chars]

Explanation atmdrv warning message while working with a wred profile

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.

B_SHIM_PARTNER Messages

Error Message %L2-B_SHIM_PARTNER-3-AIB_INIT_FAILED

Failed during AIB initialization, err: [chars]

Explanation The C-shim Partner initialization failed while trying to connect to AIB.

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

Error Message %L2-B_SHIM_PARTNER-3-CAP_ADD_ERR

Fatal Error: Adding batched channelized interface caps failed. Reason: [chars]

Explanation ’There is an error when adding batched channelized interface caps.’

Recommended Action Please try to reload that particular SPA or restart the SPA process associated with that SPA. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-B_SHIM_PARTNER-3-CAP_CNTL_ERR

Fatal Error: Failed to modify channelized interface caps. Reason: [chars]

Explanation ’There is an error when modifying channelized interface caps.’

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

Error Message %L2-B_SHIM_PARTNER-3-CAP_LKP_ERR

Fatal Error: Channelized caps definition file is missing. Reason: [chars]

Explanation ’The Channelized Caps definition file is missing. There may have a packaging issue or someone just accidently removed that file.’

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

Error Message %L2-B_SHIM_PARTNER-3-ECM_INIT_FAILED

Failed during create ECM initialization, Err: [chars]

Explanation ’There is a software error when creating ECM connection.’

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

Error Message %L2-B_SHIM_PARTNER-3-SET_CALLBACK_ERR

Fatal Error: Setting call-back to IM failed. Reason: [chars]

Explanation ’There is a software error when trying to set call-back to IM.’

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

Error Message %L2-B_SHIM_PARTNER-3-SVR_UBIND_ERR

Fatal Error: Failed to unbind to IM. Reason: [chars]

Explanation ’There is a software error when trying to unbind to IM.’

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

Error Message %L2-B_SHIM_PARTNER-4-SVR_BIND_ERR

Warning: Failed to bind to IM. Reason: [chars]

Explanation ’There is a software error when trying to bind to IM.’

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

Error Message %L2-B_SHIM_PARTNER-7-IFH_ERR

Warning: Wrong if-handle [hex] [chars]

Explanation ’Receive a message with wrong interface handle. This may be ignored.’

Recommended Action Ignore

Error Message %L2-B_SHIM_PARTNER-7-IM_CALLBACK_ERR

Warning: [chars] failed. Reason: [chars]

Explanation ’There is a software error when handling messages from IM.’

Recommended Action Ignore

BFD Messages

Error Message %L2-BFD-3-CHANGE_ECHO_SOURCE_ADDRESS_FAILED

BFD session [chars] has failed to update echo source address to [chars].

Explanation Failed to change echo source address and construct echo packet hdr for BFD session.

Recommended Action Recreate the BFD session and reconfigure echo source address for it.

Error Message %L2-BFD-3-PROT_BFD_SESSION_DOWN_MESSAGE_LOST

One or more PROT_BFD_SESSION_DOWN event(s) has been lost due to lack of protect server initialization

Explanation One or more PROT_BFD_SESSION_DOWN PFI fast protect event has been lost. If a link which BFD session failed happened to be fast-reroute protected, fast-reroute may not have been triggered.

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

Error Message %L2-BFD-3-PROT_SERVER_INIT_FAILURE

Failed to initialize protect server with error ’[chars]’

Explanation BFD could not initialize itself as PFI fast protect server, PROT_SERVER_BFD, since PFI fast protect infrastructure returned failure. BFD will continuously retry initialization in the background until successful. However, until successfully initialized, BFD session failure can not generate PFI fast protect event for PROT_BFD_SESSION_DOWN, which may prevent fast-reroute from being triggered.

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

Error Message %L2-BFD-3-REVERT_ECHO_SOURCE_ADDRESS_FAILED

BFD session [chars] has failed to revert echo source address to [chars].

Explanation Failed to revert echo source and construct echo packet hdr for BFD session.

Recommended Action Recreate the BFD session and reconfigure echo source address for it.

Error Message %L2-BFD-3-REVERT_ECHO_SOURCE_ADDRESS_SUCCESS

BFD session [chars] has reverted echo source address to [chars].

Explanation Revert echo source and construct echo packet hdr for BFD session successfully.

Recommended Action Recreate the BFD session and reconfigure echo source address for it.

Error Message %L2-BFD-4-ASYNC_DETECT_TIMER_FAULTY_EXPIRY

BFD Async Detect timer expired [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 than 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-4-RATE_LIMIT_WARNING_MP_HIGH_WATERMARK

BFD multipath resource allocation exceeds 90 percent of maximum on all multipath-configured linecards

Explanation BFD has allocated 90 percent of its multipath-specific packet per second allowance or maximum number of BFD sessions on every multipath-configured linecard in the system

Recommended Action Either configure new BFD multipath linecards or limit the number of new BFD sessions for the multipath-configured linecards.

Error Message %L2-BFD-4-RATE_LIMIT_WARNING_MP_LOW_WATERMARK

BFD multipath resource allocation now less than or equal to 85 percent of maximum on at least one multipath-configured linecard

Explanation BFD has released some of the previously allocated packet per second usage or number of BFD sessions and is now less than or equal to 85 percent of its allowance on at least one multipath-configured linecard.

Recommended Action No action is required.

Error Message %L2-BFD-4-RESOURCE_LEAK

BFD has detected resource leak in [chars] area(s)

Explanation BFD was not able to free certain resources, such as allocated memory, discriminator or checkpoint object, due to infrastructure API returning error from free/deletion operation(s). BFD should be able to continue processing by allocating new resources. However, support personel should be contacted to investigate the cause of resource 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-BFD-6-ADJACENCY_DELETE

Adjacency [chars] was deleted

Explanation The adjacency for neighbor ip address was deleted.

Recommended Action No action is required.

Error Message %L2-BFD-6-FIB_NOT_READY

Forwarding is not ready [chars]

Explanation The forwarding for session is not ready.

Recommended Action No action is required.

Error Message %L2-BFD-6-MAX_AGENT_SESSIONS_EXCEEDED

Number of requested sesssions has exceeded limit [dec]

Explanation Each linecard is only able to host specific number of BFD sessions. This message indicates that maximum number of hosting BFD sessions has reached its maximum. Those session creating requests after reaching this limit will purposely be prevented from being created. These prevented sessions will continuously be retried to be created in the These prevented sessions will continuously be retried to be created in the background, and they will be once resources are available (ex: once some existing essions are deleted). Those sessions in the retry queue can be viewed via ’show bfd session pending’ command.

Recommended Action No action is required.

Error Message %L2-BFD-6-PROT_SERVER_INIT_SUCCESS

Successfully initialized protect server

Explanation After failing to initialize itself as PFI fast protect server, PROT_SERVER_BFD, once or more, BFD was able to successfully complete initialization.

Recommended Action No action is required.

Error Message %L2-BFD-6-SESSION_BUNDLE_ALL_MEMBER_OFF

BFD session [chars] is not running in all member mode

Explanation The specified BFD session is not running in all member mode.

Recommended Action No action is required.

Error Message %L2-BFD-6-SESSION_BUNDLE_ALL_MEMBER_ON

BFD session [chars] is running in all member mode

Explanation The specified BFD session is now running in all member mode.

Recommended Action No action is required.

Error Message %L2-BFD-6-SESSION_BUNDLE_NO_ECHO

No resources for session [chars] to run echo mode, continuing with async mode

Explanation This BFD over bundle session cannot run echo mode due to lack of PPS resources. The session will continue to run in async mode until PPS is available. Once PPS resources have been cleared up, then disable and enable echo mode on this interface via configuration to startup up the echo mode.

Recommended Action Remove other BFD sessions to free resources for this session

Error Message %L2-BFD-6-SESSION_BUNDLE_NO_ECHO_CLR

Lack of resources condition has cleared for session [chars] to run echo

Explanation Resources are now available for this BFD over bundle session to run echo mode.

Recommended Action No action is required.

Error Message %L2-BFD-6-SESSION_DAMPENING_CLR

Dampening for BFD session to neighbor [chars] on interface [chars] has been cleared

Explanation Exponential backoff dampening for BFD session has been cleared for specified BFD session. When/if same session gets created by application(s), only calculated initial wait time will be applied.

Recommended Action If this behavior is not desired, it should be disabled by unconfiguring following BFD configuration. (config)#no bfd dampening bundle-member l3-only-mode

Error Message %L2-BFD-6-SESSION_INHERIT_OFF

BFD session [chars] is not inheriting state from session over [chars]

Explanation The specified BFD session is no longer inheriting BFD state from another BFD session.

Recommended Action No action is required.

Error Message %L2-BFD-6-SESSION_INHERIT_ON

BFD session [chars] is inheriting state from session over [chars]

Explanation The specified BFD session is now inheriting BFD state from another BFD session.

Recommended Action No action is required.

Error Message %L2-BFD-6-SESSION_NO_RESOURCES

No resources for session [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 [chars]

Explanation Resources are now available for this session.

Recommended Action No action is required.

Error Message %L2-BFD-6-SESSION_REMOVED

BFD session [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 [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 [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 [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.

BGP_AD Messages

Error Message %L2-BGP_AD-3-OUT_OF_LABEL

Failed to allocate a label block

Explanation ’This error happens when the system had failed to allocate a label block ’ ’as it may be running out of the label blocks. ’ ’Note that when label blocks are freed, they go to zombie state for ’ ’30 minutes. During this period, repeated addition/removal of the same ’ ’configuration will result in allocating different label blocks each time. ’ ’This can lead to running out of label blocks quickly ’

Recommended Action ’Please remove l2vpn config and wait for 30 minutes until the zombie ’ ’pool is cleared and put back the config. ’

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_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_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 bundle Manager 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_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_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-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-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-BASE_MAC

Unable to obtain base MAC address

Explanation LRd returned a NULL MAC address to be used as the base MAC address for the system and bundle MAC addresses.

Recommended Action Check the VT topology definition file to ensure a Host MAC Address is specified. Check the LRd stub library and VT IO code to see if there is a bug in accessing the defined value.

Error Message %L2-BM_PD-4-ERR_ADJ_CMPL_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_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_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_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_ADJ_DLL_INIT

Failure during intialization of [chars]. Error: [chars]

Explanation A failure occurred during the initialization of the bundlemgr adjacency process. This resulted in the restart of the process.

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

Error Message %L2-BM_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.

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.

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.

BM Messages

Error Message %L2-BM-3-ERR_BMI_DECODE

Unable to deocde BMI attribute for bundle ([chars]). Error: [chars]

Explanation Updates to bundle membership parameteers have been ignored because the received data could not be decoded.

Recommended Action The operation will be retried automatically and thus no action should be required. If the problem persists the ERR_OP_RETRY_THRESHOLD message will be seen within 30 minutes. If this occurs, restarting the Bundle Manager Distrib process on the dSDRSC (process restart bundlemgr_distrib) may resolve the issue. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-BM-4-ERR_ACTIVATE

Failure during activation of [chars]. Error: [chars]

Explanation A failure occurred during the activation of the process. Activation occurs when the card transitions to ACTIVE state. This error resulted in the restart of the process.

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

Error Message %L2-BM-4-ERR_BDL_DATA

Unable to interpret member or load balance data specified by IM for [dec] [chars] interfaces (out of batch of [dec]). Sample error, on CH[hex]: [chars]

Explanation The data specified in the IM attribute notification cannot be interpretted. The information is invalid and the result is that adjacencies for these bundles or subs cannot be programmed in hardware.

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

Error Message %L2-BM-4-ERR_DB_CHKPT_RECOVER

Unable to recreate object ID [unsigned int] after restart. Error: [chars]

Explanation When recovering data from checkpoint, an error occurred and the data is lost.

Recommended Action Verify that bundle parameters and bundle membership are as expected. Copy the error message exactly as it appears on the console or in the system log. Issue the show interface command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show interface output, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log. Issue the show bundle command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show bundle output, call your Cisco technical support representative and provide the representative with the gathered information. If the data is as expected in the output of both commands then no further action is required, otherwise unconfigure and reconfigure any missing parameters.

Error Message %L2-BM-4-ERR_ERRDIS_NOTSUPPORTED

Could not error-disable interface [chars]; driver returned [chars]

Explanation A member interface could not be error-disabled as the driver claims not to support this feature. If the member is running in Ether/POSChannel mode, traffic may still be received on this member - this may breach configured QoS policies and will prevent an mLACP brute-force switchover from taking place.

Recommended Action Shut and no-shut the member interface may clear the condition. If the error persists, manually shutting the member interface will prevent any QoS breaches.

Error Message %L2-BM-4-ERR_EVM_EVENT_BLOCK

Unrecoverable error in event loop. Error: [chars]

Explanation An error (other than EINTR) occured in the event loop. The process has exited and restarted.

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

Error Message %L2-BM-4-ERR_GLOBAL_OP_RETRY_THRESHOLD

Exceeded threshold for the number of retries for [unsigned int] global operations. First error [chars], retries performed for [chars]

Explanation After attempting to resend or query information a number of times, the retry threshold has been hit and no more attempts will be made for any global operations. The effect of the message will therefore be lost. The impact will depend on the message which was lost, but the error will give an indication as to the failure. Further information may also be found in show bundle.

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

Error Message %L2-BM-4-ERR_GROUP_CREATE

Unable to create GSP group ([chars]). Error: [chars]

Explanation Creation of the group used to communicate between Bundle Manager processes failed. This resulted in the restart of the process.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show gsp groups command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show gsp groups output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-BM-4-ERR_IIR_OP

Unable to report IIR op failure for b_ifh [hex], m_ifh [hex] (op [chars], state [chars]). Error: [chars]

Explanation An error occurred processing the IIR event and the bundle EA process was unable to report this error back to IIR. This may lead to some inconsistency with the bundle membership in the data plane not matching what is intended according to the control plane.

Recommended Action The failure to report the error back to IIR suggests a problem in the connection to IIR. This may have been a transient problem, but restarting ifmgr and/or the bundlemgr_ea process on the location of the error might be necessary. The error that should have been reported also needs to be dealt with. This error may have come from some lower layer platform component, possibly a resource allocation error. If the error code provides some information as to the failure then take action appropriate to the error. If the error code is not specific then take action according to whether the event was a link activation or a link deactivation/deletion. For activation problems unconfigure and reconfigure the member link - if this fails try restarting the bundlemgr_ea process after unconfiguring the member link. For deactivation/deletion failures try restarting the improxy process to trigger a complete resync by the bundlemgr EA.

Error Message %L2-BM-4-ERR_INIT

Failure during intialization of [chars]. Error: [chars]

Explanation A failure occurred during the initialization of the process. This resulted in the restart of the process.

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

Error Message %L2-BM-4-ERR_LINK_ATTACHED

Link [chars] is attached to [chars] that is thought to have no attached members.

Explanation This process believes that there are no aggregatable links, but this link is marked as attached. This error is most likely caused by failing to attach or detach a link correctly.

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

Error Message %L2-BM-4-ERR_MEM_ALLOC

Unable to allocate [unsigned int] bytes of memory.

Explanation Memory allocation failed.

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

Error Message %L2-BM-4-ERR_MIB_CLEANUP

Failure during cleanup of [chars] in the dot3ad MIB DLL. Error: [chars]

Explanation A failure occurred during the cleanup of the DLL. This may result in the DLL not being completely cleaned up, possibly causing errors in a subsequent re-initialization of the DLL.

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

Error Message %L2-BM-4-ERR_MIB_INIT

Failure during intialization of [chars] in the dot3ad MIB DLL. Error: [chars]

Explanation A failure occurred during the initialization of the DLL. This resulted in the DLL not being loaded into the SNMP agent, and thus the MIB services will not be available.

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

Error Message %L2-BM-4-ERR_NETIO_INIT

Failure [chars] in the bundle NetIO DLL during [chars]. Error: [chars]

Explanation A failure occurred during the initialization of the bundle NetIO DLL. If this occured during an upgrade operation then it will cause the NetIO process to reload. Otherwise this will cause the capsulation to be unloaded, and an error returned to the user. One possible reason for the error is a low memory condition, particularly if the failure was in allocating trace buffers.

Recommended Action If the error message indicates the failure is low memory condition, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Otherwise, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-BM-4-ERR_OP_RETRY_THRESHOLD

Exceeded threshold for the number of retries for [unsigned int] operations on [chars]. First (and error) [chars] ([chars]), retries performed for [chars]

Explanation After attempting to resend or query information a number of times for a set of objects, the retry threshold has been exceeded and no more attempts will be made for any in this set. The effect of the message will therefore be lost. The impact will depend on the message which was lost, but the error will give an indication as to the failure. Further information may also be found in show bundle.

Recommended Action Check that the item(s) still exist. Make a minor change to the settings of the object experiencing the problem. This will trigger another attempt to send an update. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-BM-4-ERR_PAKMAN

Unable to handle pakman corruption error: [chars]. Process exiting

Explanation A packet manager corruption has been reported and the Bundle Manager process has failed to cleanup to recover from the problem. The process will exit and be automatically restarted to recover from this situation.

Recommended Action It is expected that restarting the process will fix this problem. This is done automatically so no action should be required. If the problem recurs, then there is a problem in packet manager. A drastic solution would be to reload the linecard.

Error Message %L2-BM-4-ERR_RECREATE_BUNDLE

Unable to recreate bundle CH[hex]. Error: [chars]

Explanation When recovering the checkpointed data for a bundle, an error occurred and the data is lost.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show interface bundle name command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show interface bundle name output, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log. Issue the show bundle bundle name command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show bundle bundle name output, call your Cisco technical support representative and provide the representative with the gathered information. Copy the error message exactly as it appears on the console or in the system log. Issue the show adjacency bundle name detail hardware location loc of error command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show adjacency bundle name detail hardware location loc of error output, call your Cisco technical support representative and provide the representative with the gathered information. If the bundle appears correctly in the output of all three commands then no further action is required, otherwise unconfigure and reconfigure the bundle.

Error Message %L2-BM-4-ERR_REPAIR_BUNDLE

Unable to repair bundle CH[hex] checkpoint structures. Error: [chars]

Explanation When repairing the checkpoint structures for the bundle database an error occurred for named bundle and the bundle was not checkpointed. The next time an attempt is made to checkpoint the bundle it will fail and the checkpoint table will be reconstructed again, perhaps more successfully.

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

Error Message %L2-BM-4-ERR_REPAIR_DATABASE

Unable to repair [chars] database. Failure during checkpoint [chars]. Error: [chars]

Explanation When repairing the checkpoint structures for the named database an error occurred in the database checkpoint registration. As a result the process was intentionally restarted.

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

Error Message %L2-BM-4-ERR_REPLICATE

Replication failed for [chars], to [unsigned int] node(s). First node: [chars]. Error: [chars]

Explanation When attempting to replicate the bundle to one or more new interface locations, the replication operation failed. This probably happened because some hardware resource on the specified LC(s) was exhausted. The record of the new member(s) which triggered this replication will be removed from the bundle process on the RP but will still be referenced by the bundle process on the LC.

Recommended Action Determine whether the hardware resources for the LC(s) have been oversubscribed, e.g. more VLANs on the LC(s) and on the bundle that the LC(s) can support. If this is the case, reduce the number of allocated VLANs. Then remove the member configuration and reapply.

Error Message %L2-BM-4-ERR_RESYNC_EXCEED_IIR

Exceeded the IIR resync limit for [chars]. Process exiting.

Explanation The maximum number of attempts to resync with IIR have been exceeded for this bundle. The safest course of action is to restart the process and this has been done.

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

Error Message %L2-BM-4-ERR_RESYNC_SCHED_IIR

Unable to schedule an IIR resync for [chars]. Process exiting.

Explanation An attempt to schedule a resync with IIR has failed for this bundle. The safest course of action is to restart the process and this has been done.

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

Error Message %L2-BM-4-ERR_RETRY_EXCEED

Exceeded maximum number of retries for [chars]

Explanation After attempting to resend or query information a number of times, the retry limit has been exceeded and no more attempts will be made. The effect of the message will therefore be lost. The impact will depend on the message which was lost. If the message refers to a global error then the process will exit and be restarted.

Recommended Action If the message referred to a global error then check that the process has restarted successfully. If the message referred to a bundle or bundle member then check that the object is still configured and still exists. Make a minor change to the settings of the object experiencing the problem. This will trigger another attempt to send an update. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-BM-4-ERR_RETRY_EXCEED_GSP

Retry limit for GSP initialization exceeded: [chars]

Explanation After attempting to create the GSP group used for communications with the Bundle Manager process on another node a number of times, the retry limit has been exceeded. The cause of the failure is very likely to be some external communication failure - so check for evidence of this. The process will exit and be restarted automatically so no futher action is needed for Bundle Manager to retry.

Recommended Action Check that other processes are not reporting similar communication errors, as this is likely to be a general communication problem. The Bundle Manager process has exited and will be restarted, so no action is needed, though unless the communication problem is resolved the process will still not be able to startup.

Error Message %L2-BM-4-ERR_RETRY_EXCEED_IMP

Exceeded the retry limit for IMP events.

Explanation The maximum number of attempts to retry an IMP message has been exceeded. An error has occurred in the clean up of a bundle, so there may be residual data for the bundle in the linecard components which could cause subsequent problems. Restart the process that reported the error to recover.

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

Error Message %L2-BM-4-ERR_RETRY_EXCEED_PROTECT

Retry limit for Protect initialization exceeded: [chars]

Explanation After attempting to initialize the Protect module a number of times, the retry limit has been exceeded. The cause of the failure is very likely to be some external communication failure - so check for evidence of this. The process will exit and be restarted automatically so no futher action is needed for Bundle Manager to retry.

Recommended Action Check that other processes are not reporting communication errors, as this is likely to be a general communication problem. The Bundle Manager process has exited and will be restarted, so no action is needed, though unless the root problem is resolved the process will still not be able to startup.

Error Message %L2-BM-4-ERR_RETRY_EXCEED_SYSTEM_MAC

Retry limit for system MAC address query exceeded: [chars]

Explanation After attempting to query the system MAC address from SDRd a number of times, the retry limit has been exceeded. The cause of the failure is likely to be an issue with SDRd or Shelfmgr - so check for evidence of this. The process will exit and be restarted automatically so no futher action is needed for Bundle Manager to retry.

Recommended Action The Bundle Manager process has exited and will be restarted, so no action is needed. Check that the board (EEPROM etc.) is correctly programmed since this is the source of the MAC address information and therefore one possible cause of the problem.

Error Message %L2-BM-4-ERR_SUB_PARENT

Unable to retrieve the control parent from IM for a subinterface or satellite (CH[hex])

Explanation IM could not provide information on the control parent for a given subinterface. This means that adjacencies for this subinterface cannot be programmed in hardware.

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

Error Message %L2-BM-4-ERR_SYSMGR

Failure communicating readiness to System Manager. Error: [chars]

Explanation The process was initialized successfully but was unable to inform System Manager of the success.

Recommended Action Check on the status of the sysmgr process on the node from which the error was reported. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-BM-4-ERR_SYSTEM_MAC_RESET

Existing system MAC address not found in allocation. System MAC address for bundles is being reset

Explanation After a resync has occurred between Bundle Manager and the MAC allocation process, the MAC address assigned for use as the system MAC has not been found in the addresses allocated to bundle manager. Bundle manager will choose a new MAC address for use for this purpose. A flap will be seen on bundle links running LACP.

Recommended Action The Bundle Manager process will select a new address automatically, so no further action is needed to resolve this error.

Error Message %L2-BM-4-ERR_TX_HEAP_LOOKUP

Failed to create non-existent entry for interface CH[hex] while attempting to [chars]: [chars]

Explanation An attempt to create a new database entry for a port failed. In addition to indicating that the line card is running low on system resources, this suggests that the shared-memory database is out-of-sync with the main database. Once some system resources have been released, the bundlemgr_local process should be restarted to retry the timer creation.

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

Error Message %L2-BM-4-ERR_TX_TIMER

Failed to [chars] periodic timer for interface CH[hex]: [chars]

Explanation An attempt to create or start a timer for periodic sending failed. Regular LACPDUs will NOT be sent out. This suggests that the line card is running low on system resources. Once some system resources have been released, the bundlemgr_local process should be restarted to retry the timer creation.

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

Error Message %L2-BM-4-ERR_UNREPLICATE

Unreplication failed for [chars], to [unsigned int] node(s). First node: [chars]. Error: [chars]

Explanation When attempting to unreplicate the bundle from the specified location(s), the unreplication operation failed. Some hardware resources may continue to be used for the bundle on the specified location(s). It is also possible that there could be a problem replicating the bundle to those locations again if a new member is added.

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

Error Message %L2-BM-4-ERR_VLAN_TAGS

Unable to generate Ethernet header data for interface [chars]. Error: [chars]

Explanation The LACP protocol will not be able to run on this interface. This may be because the interface has a complex encapsulation configured, which is not supported in conjunction with LACP. Complex encapsulations include: - Matching on source or destination MAC addresses - Matching on payload ethertype - Matching on VLAN tags using the ’any’ keyword. In these cases, it cannot be determined how to format the ethernet header for sending LACP packets, and hence LACP is not supported in these scenarios.

Recommended Action Ensure the encapsulation on the interface does not use any of the ’complex’ matching criteria.

Error Message %L2-BM-4-LINK_ORDER_MISMATCH

Prolonged mismatch between Link Ordering Numbers and maximum active links settings on [chars]%s

Explanation A locally or partner-allocated Link Ordering Number which is larger than the maximum active links value has been detected. The link order signaling feature has been disabled until the mismatch is rectified.

Recommended Action Check the maximum active links settings on both ends of the bundle and ensure that the same value is in use.

Error Message %L2-BM-4-LINK_ORDER_NOT_CONVERGED

Could not form consistent set of partner-supplied Link Order Numbers on [chars] within [unsigned int] seconds

Explanation The local system has been unable to form a consistent set of Link Order Numbers from the data supplied by the LACP partner. This means that the links may not be ordered identically on the two ends of the bundle.

Recommended Action Shut and no-shut the bundle interface may clear the condition. If the error persists, shutting down all member interfaces and the bringing them up individually may clear the condition.

Error Message %L2-BM-4-LRD_RESYNC

Bundle member [chars] is being referenced from a non-existent node [hex]

Explanation When resyncing with LRd, bundlemgr has unexpectedly found that a bundle member is on a card that no longer exists. The member will be cleaned up.

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

Error Message %L2-BM-4-SELECTION

Selection Logic for bundle [chars]: [chars]

Explanation There has been a misconfiguration resulting in the problem described being hit in the Selection Logic operation for the bundle.

Recommended Action Correct the misconfiguration.

Error Message %L2-BM-5-ACTOR_CHURN

Interface [chars] in [chars] [chars] on actor system

Explanation Actor churn has either been detected (due to the failure of a link to synchronize soon enough) or has been cleared. If the link is in Standby state, then actor churn will be detected after the churn timeout; this is expected behavior. Otherwise, this indicates a possible misconfiguration.

Recommended Action If actor churn has been declared and the link is not marked as Standby, check that the configuration for the link allows it to aggregate, and fix as appropriate. Check for misconfigurations between the two ends of the link which is reporting churn. The output of the show bundle command may help identify the problem.

Error Message %L2-BM-5-BUNDLE_COMPATIBILITY

Incompatible configuration [chars]for [chars]%s

Explanation A configuration change has meant that a bundle now has incompatible configuration. All links have been disabled. The reason for the incompatibility at the time of raising the alarm is supplied in the message.

Recommended Action No action is required; however, the bundle will remain inoperative until the configuration incompatibility is cleared.

Error Message %L2-BM-5-ERR_MAC_RELEASE

Could not release reserved MAC addresses from allocation

Explanation After a resync with the MAC address allocation server, the Bundle Manager process found that it had more MAC addresses than required by the bundle configuration settings and tried to release some to the server. However, this operation failed, so these extra MACs were kept in the Bundle Manager allocation. This is not an issue unless there is a shortage of MAC addresses for another feature (e.g. Interflex).

Recommended Action If there is no other feature that is short of MAC addresses, no action is required. Otherwise, try adding and deleting an additional Bundle-Ether interface (with no members). Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-BM-5-ERR_TX_ENQUEUE

Unable to queue LACP packet for ingress processing on interface CH[hex] (reason: [chars]). Processing will resume with next received LACP packet.

Explanation An attempt to queue a received packet for processing failed. An occasional message of this type indicates that bundlemgr_local has temporarily been blocked from processing the queue leading to this harmless condition.

Recommended Action If this message appears more than once, the bundlemgr_local process should be restarted to try to recover the situation. An occasional message of this type will be harmless.

Error Message %L2-BM-5-LACP_PKT_DELAYED

Possible dropped or delayed packet on [chars]: Received partner seq: [unsigned int], Expected: [unsigned int] or [unsigned int]

Explanation The received partner sequence number is too far behind the last sent actor sequence number. This indicates either that one or more LACPDUs sent to the partner device have been dropped, or there is a long delay on the partner device in processing the LACPDUs.

Recommended Action This message indicates one of two possibilities. Either LACPDUs sent by this device have been dropped before delivery on the partner, or the partner device is unable to process incoming LACPDUs in a timely fashion. Check packet counters on both devices for drops, and for rate limited LACPDUs on the partner device (using show lacp counters if it is an XR device). Check also for high CPU load on the partner device.

Error Message %L2-BM-5-LACP_PKT_DROPPED

Possible dropped packet on [chars]: Received actor seq: [unsigned int], Expected: [unsigned int]

Explanation There has been a jump in the received actor sequence number, indicating that a LACPDU from the partner has been dropped. Note that rate limiting on transmission takes place before the sequence numbers are incremented, so the warning will not be related to rate limiting on transmission. However, it is possible that rate limiting on receipt will cause a sequence number discrepancy.

Recommended Action This message indicates that a gap in incoming LACPDUs has been detected, possibly as the result of packet loss or rate limiting of incoming LACPDUs. Check packet counters on both devices for drops, and for locally rate limited LACPDUs using show lacp counters.

Error Message %L2-BM-5-LACP_PKT_DROPPED_PTNR

Possible dropped packet detected by partner on [chars]: Received actor seq: [unsigned int], Received partner seq: [unsigned int]

Explanation There has been a jump in the actor sequence numbers received by the partner, indicating that a LACPDU from this device to the partner has been dropped. This condition has been signalled from the partner to this device. Note that rate limiting on transmission takes place before the sequence numbers are incremented, so the warning will not be related to rate limiting on transmission. However, it is possible that rate limiting on receipt will cause a sequence number discrepancy.

Recommended Action This message indicates that a gap in incoming LACPDUs has been detected by the partner device, possibly as the result of packet loss or rate limiting of incoming LACPDUs. Check packet counters on both devices for drops, and for rate limited incoming LACPDUs on the partner device using show lacp counters.

Error Message %L2-BM-5-MBR_BFD_NEIGHBOR_UNCONFIGURED

The BFD session on link [chars] in [chars] has indicated that its neighbor session has been unconfigured. [chars]

Explanation The BFD session on the member has transitioned to NBR_CONFIG_DOWN state, indicating that the configuration has been removed from the neighbor. The member will continue to transmit packets for as long as the message specifies, at which point, if the session has not gone back UP, the member will be brought down.

Recommended Action To stop the member from being brought down, rectify the inconsistency between the BFD sessions of the two neighboring routers within the specified time. EITHER, configure BFD sessions per-member on both routers OR remove the configuration from both routers.

Error Message %L2-BM-5-MBR_BFD_SESSION_DOWN

The BFD session on link [chars] in [chars] has timed out. The member will be removed from the active members of the bundle.

Explanation There are 3 possible reasons for the BFD session to time out: - the session did not transition to state UP within the given time period after initial start-up. - the BFD session transitioned to state DOWN. - the BFD session timed out after receiving a message indicating that the neighbor’s BFD session was unconfigured.

Recommended Action Ensure that the bundle and its members are configured correctly on the neighboring router, and that all the interfaces are up. Ensure that BFD is running on the member interfaces on the neighboring router.

Error Message %L2-BM-5-MIN_MAX

[chars] [chars]has conflicting configuration and is [chars]held down: Maximum-active links [unsigned int], minimum-active links [unsigned int]

Explanation This is an informational message reporting that a bundle is operationally down because the configuration for minimum active links and maximum active links conflicts. The number of active links required for the bundle to come up is greater than the number of links permitted to be active in the bundle, and there are at least enough links held in standby state for the bundle to come up if the maximum active link criteria were removed.

Recommended Action If this situation is not intended then either reduce the minimum active link threshold or increase the maximum links permitted in the bundle.

Error Message %L2-BM-5-MLACP_BUFFER_PARSE_FAILED

Failed to parse the mLACP message for a [chars] event from [chars]. Reason: [chars]

Explanation There was an error reading a message sent by the specified mLACP peer device from the ICCP RX buffer. This message will now be lost.

Recommended Action Ensure that the ICCP Group is running as expected.

Error Message %L2-BM-5-MLACP_CANNOT_SWITCHOVER

Could not perform mLACP switch[chars] requested by user for bundle [chars]: [chars]

Explanation A switchover or switchback was requested by the user, but this could not be performed because the bundle is not in an appropriate state or is not configured in the required manner.

Recommended Action If the message indicates that the switch could not be performed because the router being switched to is already active, no action is required - the command is extraneous. If it indicates that the router being switched to is currently down, action must be taken to recover the bundle on that router before retrying the command. Otherwise, the message indicates a configuration-based issue. Correct the configuration before retrying the command.

Error Message %L2-BM-5-MLACP_CONNECT_FAILED

Failed to connect to another mLACP device in ICCP Group [unsigned int]. Reason: [chars]

Explanation It was not possible to connect to the specific to a peer device in the specified ICCP Group. mLACP will not be running over the specified ICCP Group.

Recommended Action If the reason message indicates that the failure is because the application is not in the ICCP Group, ensure that mLACP is configured for the ICCP Group on a peer router. Otherwise, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-BM-5-MLACP_CORE_ISOLATION

[chars] [chars] as isolated due to [chars] [chars] able to connect to the core

Explanation Core network connectivity status for the ICCP Group has changed, affecting the bundle. If the bundle is isolated then it cannot be active for MC-LAG.

Recommended Action Ensure that the backbone interface is able to carry traffic to the core.

Error Message %L2-BM-5-MLACP_DEVICE_MISCONFIGURATION

[chars]

Explanation There is a misconfiguration between a peer device and the local device.

Recommended Action Ensure that the configuration (on both local and peer device) is as expected. The message indicates the initial area to check.

Error Message %L2-BM-5-MLACP_ITEM_LOCAL_MISCONFIGURATION

[chars] [chars].

Explanation If there is a misconfiguration for an item that may be resolved without user intervention, then the item will be temporarily ignored. Once the misconfiguration is resolved, either by a resync of mLACP data or by the user, the item will no longer be ignored.

Recommended Action If the alarm does not clear, ensure that the configuration (on both local and peer device) is as expected.

Error Message %L2-BM-5-MLACP_ITEM_PEER_MISCONFIGURATION

[chars] [chars].

Explanation If there is a misconfiguration for an item that may be resolved without user intervention, then the item and its children will be temporarily ignored. Once the misconfiguration is resolved, either by a resync of mLACP data or by the user, the item will no longer be ignored. Note that peer data which is rejected will be deleted from the local database so the information which caused the issue may not be visible in show commands.

Recommended Action Check show mlacp after a short while to see if the problem has cleared and all expected items are present. If the problem does not clear, ensure that the configuration (on both local and peer device) is as expected.

Error Message %L2-BM-5-MLACP_RESYNC_INCONSISTENCY_DISCONNECT

Disconnecting from [chars] due to an inconsistency in the mLACP data that could not be resolved with a resynchronization. Reason: [chars]

Explanation A resync failed to solve an inconsistency and so the local device has disconnected.

Recommended Action Disable and re-enable mLACP on either the local or the peer device.

Error Message %L2-BM-5-MLACP_ROID_MISMATCH

The ROID ([unsigned long long int]) received from [chars] for [chars], does not match that expected ([unsigned long long int]). Please ensure that the ROID for the bundle is the same on both devices

Explanation The peer device has transmitted a different Redundancy Object ID for the bundle to that expected.

Recommended Action Ensure that the ROID of the bundle (on both local and peer device) is as expected.

Error Message %L2-BM-5-MLACP_UNRESOLVABLE_MISCONFIG_DISCONNECT

Disconnecting from [chars] due to an unresolvable misconfiguration: [chars]

Explanation The misconfiguration supplied could not be resolved by arbitration and so the mLACP system disconnected from the peer node on the given ICCP Group.

Recommended Action Remove the mLACP ICCP Group configuration from both routers and apply the correct configuration.

Error Message %L2-BM-5-PARTNER_CHURN

Interface [chars] in [chars] [chars] on partner system

Explanation Partner churn has either been detected (due to the failure of the partner to be marked as synchronized on this link soon enough) or has now cleared. If the link is in Standby state on the peer router, then partner churn will be detected after the churn timeout; this is expected behavior. Otherwise, this indicates a possible misconfiguration.

Recommended Action If partner churn has been declared and the link is not marked as Standby on the peer router, check that the configuration for the link allows it to aggregate, and fix as appropriate. Check for misconfigurations between the two ends of the link which is reporting churn. The output of the show bundle command may help identify the problem.

Error Message %L2-BM-5-RED_MGMT

Redundancy Management for bundle [chars]: [chars]

Explanation There has been a misconfiguration resulting in the problem described being hit in the redundancy handling for the bundle.

Recommended Action Correct the misconfiguration.

Error Message %L2-BM-6-ACTIVE

[chars] [chars] Active as part of [chars]%s

Explanation This is an informational message reporting that a link has entered or left Active state as part of a bundle interface. The link configuration may have just been changed or there may be an operational reason for the event such as a state change or LACP protocol update.

Recommended Action Nothing, this is not an error.

Error Message %L2-BM-6-MBR_BFD_SESSION_UP

The BFD session on link [chars] in [chars] has gone UP.[chars]

Explanation The BFD session on the link has indicated that it is UP state. The link has fast-protect BFD protection on it until further notice.

Recommended Action No action is required.

Error Message %L2-BM-6-MBR_BFD_STARTING

The BFD session on link [chars] in [chars] is starting. [chars]

Explanation BFD sessions have been started on all the members of the given bundle. If the BFD session has not gone UP by the time specified in the message, the BFD session on the member of the bundle will be marked as DOWN, which may impact traffic.

Recommended Action Ensure that the bundle and its members are configured correctly on the neighboring router, and that all the interfaces are up. Ensure that BFD is configured on the member interfaces on the neighboring router.

Error Message %L2-BM-6-MEMBER_COMPATIBILITY

Interface [chars] in [chars] is [chars]incompatible with the bundle operational state[chars]

Explanation A configuration change has meant that a link is now incompatible (or compatible) with the other members of the bundle, or the bundle is operating in a mode that is incompatible with the member’s configuration. The reason for the incompatibility at the time of raising the alarm is supplied in the message.

Recommended Action No action is required; however, any link that is incompatible will not be used in the bundle. In order to make the link compatible, refer to the reason given in the message. Check the configured mode of operation (LACP active/passive or disabled, i.e. mode ’on’) and bandwidth of all the links within the bundle or the bundle configuration to resolve the incompatibility.

Error Message %L2-BM-6-MLACP_BDL_SYSID_IGNORED

The configured system id for [chars] has no effect as the bundle is running mLACP.

Explanation When running mLACP on a bundle, the system ID must be common on both devices, so cannot be configured on a per-bundle basis.

Recommended Action Remove the system id configuration, as it has no effect when running mLACP.

Error Message %L2-BM-6-MLACP_BUNDLE_ACTIVE

This device is [chars] the active device for [chars]

Explanation The role of the mLACP device for this bundle has changed.

Recommended Action No action is required.

Error Message %L2-BM-6-MLACP_BUNDLE_MAC_ARBITRATION

The MAC address for [chars] [chars]

Explanation Each mLACP peer specifies a MAC address for a bundle. If the MAC addressess are different, arbitration must occur. However, if the peer that has supplied the value selected through arbitration disconnects, there will be a flap in the bundle state.

Recommended Action If the alarm is set, the user should ensure that all peers have the same MAC address for the bundle.

Error Message %L2-BM-6-MLACP_BUNDLE_PEERING

[chars] is [chars]peering with [chars].[chars]%s

Explanation The mLACP peer device for the bundle has changed.

Recommended Action No action is required.

Error Message %L2-BM-6-MLACP_CONNECT

Connected to [chars]

Explanation An mLACP connection has been established to the specified device.

Recommended Action No action is required.

Error Message %L2-BM-6-MLACP_DISCONNECT

Disconnected from [chars]

Explanation mLACP has disconnected from the specified devices.

Recommended Action No action is required.

Error Message %L2-BM-6-MLACP_INVALID_PRIORITY_REQUEST

An invalid mLACP port priority [chars] has been received for [chars] on [chars]. [chars]Reason: [chars]

Explanation An mLACP peer device has requested that the priority of the specified member be changed. This is currently an invalid operation due to the reason specified. If the message indicates that the priority request has been ignored, then the peer will be notified that the priority change has not been made.

Recommended Action Check that the configuration of all the mLACP peer devices is consistent.

Error Message %L2-BM-6-MLACP_SYSTEM_ID_ARBITRATION

The system id for ICCP Group [unsigned int] has been established by [chars]

Explanation Each mLACP peer specifies a system id for the ICCP group. If the system id’s are different, arbitration must occur. However, if the peer that has supplied the values selected through arbitration disconnects, there will be a flap in the bundle state.

Recommended Action If the alarm is set, the user should ensure that all peers have the same system id for the ICCP Group.

Error Message %L2-BM-6-SATELLITE_COMPATIBILITY

[chars] [chars] a Satellite fabric uplink, configuration incompatiblity [chars]

Explanation This is an informational message reporting that a bundle has or had configuration present that could not be applied while it was a Satellite fabric uplink. The configuration would be ignored but the bundle would otherwise operate normally.

Recommended Action Ensure no configuration is present on the bundle that cannot be applied when acting as a Satellite fabric uplink.

Error Message %L2-BM-7-MLACP_TLV_CAPTURE_STOPPED

Buffers full for TLV capture on ICCP group [unsigned int]. TLV capture halted.

Explanation TLV capture has been halted on the specified ICCP group due to lack of buffer space. If further capture is required, the current TLVs must be cleared (using the clear mlacp tlv-capture command) and TLV capture explicitly restarted. Captured TLVs may be viewed using the show mlacp tlv-capture command.

Recommended Action No action is required.

BVI_MA Messages

Error Message %L2-BVI_MA-3-BAG_REG_ERR

[chars]: [chars]

Explanation An error has happened while registering bags

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

Error Message %L2-BVI_MA-3-EVENT_ERR

[chars]: [chars]

Explanation An invalid message has been 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.

Error Message %L2-BVI_MA-3-INIT_ERR

[chars]: [chars]

Explanation An error has happened while initializing bvi ma

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

Error Message %L2-BVI_MA-3-SYSDB_ERR

[chars]: [chars]

Explanation An error has happened while initializing sysdb connection from vif ma

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

C_SHIM_PARTNER Messages

Error Message %L2-C_SHIM_PARTNER-3-AIB_INIT_FAILED

Failed during AIB initialization, err: [chars]

Explanation The C-shim Partner initialization failed while trying to connect to AIB.

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

Error Message %L2-C_SHIM_PARTNER-3-AIB_INIT_FAILED

Failed during AIB initialization, err: [chars]

Explanation The C-shim Partner initialization failed while trying to connect to AIB.

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

Error Message %L2-C_SHIM_PARTNER-3-CAP_ADD_ERR

Fatal Error: Adding batched channelized interface caps failed. ifh [hex],Reason: [chars].

Explanation ’There is an error when adding batched channelized interface caps.’

Recommended Action Please try to reload that particular SPA or restart the SPA process associated with that SPA. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-C_SHIM_PARTNER-3-CAP_ADD_ERR

Fatal Error: Adding batched channelized interface caps failed. Reason: [chars]

Explanation ’There is an error when adding batched channelized interface caps.’

Recommended Action Please try to reload that particular SPA or restart the SPA process associated with that SPA. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-C_SHIM_PARTNER-3-CAP_CNTL_ERR

Fatal Error: Failed to modify channelized interface caps. Reason: [chars]

Explanation ’There is an error when modifying channelized interface caps.’

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

Error Message %L2-C_SHIM_PARTNER-3-CAP_CNTL_ERR

Fatal Error: Failed to modify channelized interface caps. Reason: [chars]

Explanation ’There is an error when modifying channelized interface caps.’

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

Error Message %L2-C_SHIM_PARTNER-3-CAP_LKP_ERR

Fatal Error: Channelized caps definition file is missing. Reason: [chars]

Explanation ’The Channelized Caps definition file is missing. There may have a packaging issue or someone just accidently removed that file.’

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

Error Message %L2-C_SHIM_PARTNER-3-CAP_LKP_ERR

Fatal Error: Channelized caps definition file is missing. Reason: [chars]

Explanation ’The Channelized Caps definition file is missing. There may have a packaging issue or someone just accidently removed that file.’

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

Error Message %L2-C_SHIM_PARTNER-3-ECM_INIT_FAILED

Failed during create ECM initialization, Err: [chars]

Explanation ’There is a software error when creating ECM connection.’

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

Error Message %L2-C_SHIM_PARTNER-3-ECM_INIT_FAILED

Failed during create ECM initialization, Err: [chars]

Explanation ’There is a software error when creating ECM connection.’

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

Error Message %L2-C_SHIM_PARTNER-3-SET_CALLBACK_ERR

Fatal Error: Setting call-back to IM failed. Reason: [chars]

Explanation ’There is a software error when trying to set call-back to IM.’

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

Error Message %L2-C_SHIM_PARTNER-3-SET_CALLBACK_ERR

Fatal Error: Setting call-back to IM failed. Reason: [chars]

Explanation ’There is a software error when trying to set call-back to IM.’

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

Error Message %L2-C_SHIM_PARTNER-3-SVR_UBIND_ERR

Fatal Error: Failed to unbind to IM. Reason: [chars]

Explanation ’There is a software error when trying to unbind to IM.’

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

Error Message %L2-C_SHIM_PARTNER-3-SVR_UBIND_ERR

Fatal Error: Failed to unbind to IM. Reason: [chars]

Explanation ’There is a software error when trying to unbind to IM.’

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

Error Message %L2-C_SHIM_PARTNER-4-SVR_BIND_ERR

Warning: Failed to bind to IM. Reason: [chars]

Explanation ’There is a software error when trying to bind to IM.’

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

Error Message %L2-C_SHIM_PARTNER-4-SVR_BIND_ERR

Warning: Failed to bind to IM. Reason: [chars]

Explanation ’There is a software error when trying to bind to IM.’

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

Error Message %L2-C_SHIM_PARTNER-7-IFH_ERR

Warning: Wrong if-handle [hex] [chars]

Explanation ’Receive a message with wrong interface handle. This may be ignored.’

Recommended Action Ignore

Error Message %L2-C_SHIM_PARTNER-7-IFH_ERR

Warning: Wrong if-handle [hex] [chars]

Explanation ’Receive a message with wrong interface handle. This may be ignored.’

Recommended Action Ignore

Error Message %L2-C_SHIM_PARTNER-7-IM_CALLBACK_ERR

Warning: [chars] failed. Reason: [chars]

Explanation ’There is a software error when handling messages from IM.’

Recommended Action Ignore

Error Message %L2-C_SHIM_PARTNER-7-IM_CALLBACK_ERR

Warning: [chars] failed. Reason: [chars]

Explanation ’There is a software error when handling messages from IM.’

Recommended Action Ignore

C12000_FR Messages

Error Message %L2-C12000_FR-3-SUBIF_COUNT

FR Subinterface counter is not initialised

Explanation Initialisation of subinterface counter in the shared memory failed

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

CCL Messages

Error Message %L2-CCL-3-INIT_ERROR

Initialization failed: ([chars]%s)

Explanation The classification control list (ccl) DLL failed to initialize. This DLL does a generalization of an Access Control List to include matching on MQC match criteria like QOS group, MPLS EXP, etc. If the ccl DLL fails to initialize, the access control list cannot be programmed into the hardware. %s - indicates the reason for the initialization failure. %s - is the decoded error reason.

Recommended Action The failure should be handled by the process that is loading the DLL. The calling process should retry the initialization. Collect all debug information if the DLL is continually failing: ’debug ccl ace error location 0/x/cpu0’ ’debug ccl api detail location 0/x/cpu0’

CDP Messages

Error Message %L2-CDP-3-ERR_CONN

Connection error on [chars]: [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_NO_MEM

Out of memory (failed attempt to reserve [unsigned int] bytes)

Explanation CDP was not able to allocate the memory that it needed to complete the operation. CDP 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-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.

CEM_PLATFORMS Messages

Error Message %L2-CEM_PLATFORMS-2-ERR

[chars] - [dec]: [chars]

Explanation Error in cem operation.

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

Error Message %L2-CEM_PLATFORMS-2-ERR_HEX

[chars] - [dec]: [chars] ([hex])

Explanation Error in cem operation.

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

Error Message %L2-CEM_PLATFORMS-2-ERR_IFH_STS

[chars] - [dec]: [chars] ifh equals [hex] rc equals [hex]

Explanation Error in cem operation.

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

Error Message %L2-CEM_PLATFORMS-2-ERR_INT

[chars] - [dec]: [chars] ([dec])

Explanation Error in cem operation.

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

Error Message %L2-CEM_PLATFORMS-2-ERR_STR

[chars] - [dec]: [chars] ([chars])

Explanation Error in cem operation.

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

Error Message %L2-CEM_PLATFORMS-2-ERR_STS

[chars] - [dec]: [chars] (rc equals [hex])

Explanation Error in cem operation.

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

CEM Messages

Error Message %L2-CEM-3-INIT

[chars] [chars] Initialization failed - Reason [chars]

Explanation Failure occured during the initialization of CEM component Logs the reason for failure.

Recommended Action Collect the component logs

Error Message %L2-CEM-6-CLASS_ERROR

[chars]. Reason: ([chars])

Explanation An API or a functiona call in cem_class process failed.

Recommended Action Not Action requirements.

Error Message %L2-CEM-6-CNTRLR_INHERITED

Inherited CEM params from class [chars] attached to parent controller

Explanation Inherited values from the class attached to the parent controller.

Recommended Action Not action requirements.

Error Message %L2-CEM-6-PARAM_NOT_COMPATIBLE

Payload [dec] is not compatible with Dejitter [dec] for interface [chars]. Value ignored

Explanation A value in class attach onto interface or controller not inherited.

Recommended Action Not Action requirements.

Error Message %L2-CEM-6-PARAM_NOT_IN_RANGE

[chars] [dec] is not in range [dec]-[dec] for interface [chars]. Value ignored

Explanation A value in class attach onto interface or controller not inherited.

Recommended Action Not Action requirements.

Error Message %L2-CEM-6-PAYLOAD_NOT_MULTIPLE

Payload [dec] is not multiple of 8*N (N:channels) for interface [chars]. Value ignored

Explanation A value in class attach onto interface or controller not inherited.

Recommended Action Not Action requirements.

Error Message %L2-CEM-6-STATS_CALLOC_FAILED

Calloc failed for stats array. Please restart the g_spa process

Explanation Due to calloc failure for stats array, g_spa process needs to be restarted.

Recommended Action Restart the g_spa process.

Error Message %L2-CEM-6-WAVL_DELETE_FAILED

Wavl deletion failed for [chars]. Please restart the g_spa process

Explanation Due to wavl deletion failure, g_spa process needs to be restarted.

Recommended Action Restart the g_spa process.

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-3-UNSUPPORTED_ERR

CEMA Unsupported Feature Error: [chars]

Explanation A request was made for information on a feature that is unsupported on the device specified in the request. This error may affect the usability of the device if the feature is necessary for proper operation.

Recommended Action Check to see if the device on which the feature has failed is performing correctly for all necessary functionality.

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.

CFM Messages

Error Message %L2-CFM-3-AIS_GEN_ERROR

Failed to [chars] the generation of AIS for [unsigned int] local MEPs as a result of configuration or network change: [chars]

Explanation A failure occurred when attempting to generate or disable AIS messages for a number of local MEPs. This event was triggered by either a change within the network (e.g. to a remote MEP or to an EFP state) or a change in configuration (e.g. a CoS bit or AIS transmission interval change). This may result in AIS being sent at the wrong level or interval, no AIS being sent at all, or AIS being sent when it should not be. If the error persists, CFM may not operate correctly.

Recommended Action If the error is the result of a configuration change, remove and reapply the configuration. If this does not work, or the error was triggered by a change in the network, the error may be cleared by restarting the cfmd process on the node where the error is occurring, or shutting down and re-enabling any affected interfaces.

Error Message %L2-CFM-3-AIS_GEN_TIMER

Failed to start AIS generation timer in [chars]%s[chars]%s with timeout [unsigned int]ms, jitter [unsigned int]ms: [chars]

Explanation An error occurred while starting or restarting the AIS generation timer. No further AIS messages will be sent for MEPs/EFPs in this service/bridge domain.

Recommended Action Unconfigure AIS generation on the service or EFP, then reconfigure it. If the problem persists, it may be possible to recover by restarting the ’cfmd’ process on the node where the problem occurs.

Error Message %L2-CFM-3-CCI_TIMER

Failed to start CCM generation timer in domain [chars], service [chars] with timeout [unsigned int]ms, jitter [unsigned int]ms: [chars]

Explanation An error occurred while starting or restarting the CCM generation timer. No further CCM messages will be sent for MEPs in this domain/service.

Recommended Action Unconfigure CCM generation for this service, commit the configuration, then reconfigure it. If the problem persists, it may be possible to recover by restarting the ’cfmd’ process on the node where the problem occurs.

Error Message %L2-CFM-3-CCM_GEN_ERROR

Failed to update or disable the generation of CCM messages for a number of local MEPs as a result of [chars]: [chars]

Explanation A failure occurred when attempting to generate or disable CCM messages for a number of local MEPs. This may result in outgoing CCM messages containing incorrect flags, interface state information or CoS bits, no CCMs being sent at all, or CCMs being sent when they should cease. If the error persists, CFM may not operate correctly. The regeneration event that has failed was triggered by the protocol event mentioned in the message description.

Recommended Action If the error is the result of a configuration change, remove and reapply the configuration. If this does not work, or the error was the result of interface state changes or an attempt to set/clear the RDI bit, the error may be cleared by restarting the cfmd process on the node where the error is occurring, or shutting down and re-enabling any affected interfaces.

Error Message %L2-CFM-3-CCM_SEND_ERROR

Failed to send CCMs for [unsigned int] local MEPs. First failed MEP - domain: [chars], service: [chars], MEP ID: [unsigned int], interface: CH[hex], error : [chars]

Explanation A failure occurred when attempting to send CCM messages for a number of local MEPs, some CCMs will not have been sent. If the error persists, CFM may not operate correctly. The failure was triggered by the protocol event mentioned in the message description. Further errors of this nature will be supressed for the next 30 minutes.

Recommended Action If the error is the result of a configuration change, remove and reapply the configuration. If this does not work, the error may be cleared by restarting the cfmd process on the node where the error is occurring, or shutting down and re-enabling any affected interfaces.

Error Message %L2-CFM-3-CFG_APPLY_FAILED

[chars] failed to apply new CFM Configuration. It is likely that the protocol will not operate as intended: [chars]

Explanation The CFM Global Manager or the CFM Daemon on the specified node was unable to enact a set of valid configuration changes. Future configuration changes may be adversely affected and the protocol is likely not to operate as intended. The problem could be caused by a system resource issue.

Recommended Action Attempt to resolve any memory issues before attempting to solve this problem. After system resource isses have been resolved, issue ’process restart cgm’ or ’process restart cfmd’ on the affected 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-CFM-3-CFG_ATTR_UPDATE_FAILED

Error processing [chars] changes for [unsigned int] interfaces. Outgoing CCMs may contain incorrect information: [chars]

Explanation CFM was unable to update internal state following a change to an interface attribute on a group of interfaces.

Recommended Action Restarting the CFM Daemon on the node where the problem has occurred may help to resynchronize the system state. This error may occur as a result of memory exhaustion; attempt to resolve any memory issues before attempting to solve this problem. After system resource isses have been resolved, issue ’process restart cfmd 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-CFM-3-CFG_DELETED_INTF_OP

Received new configuration for an interface that is not expected to exist. Configuration operation: [chars]. Interface CH[hex]

Explanation A notification from another part of the system indicates that some operation should be performed on an interface that does not exist in Interface Manager. The CFM Daemon’s internal state will be updated in accordance with the requested operation, but no Maintenance Points will be created on the affected interface. This indicates an inconsistency between the Interface Manager and other infrastructure components.

Recommended Action Removing and re-applying the configuration responsible for the failed operation may help to resynchronize system state. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-CFG_MP_CREATE_FAILED

Failed to create Maintenance Points following a change to CFM configuration: [chars]

Explanation CFM encountered an error while trying to create new Maintenance Points and retrying the operation has not resolved the problem. This situation could indicate that system resources are low. The operational state of CFM will now be out-of-sync with configuration as some Maintenance Points will not have been created.

Recommended Action Restarting the CFM Daemon on the node where the problem has occurred may help to resynchronize the system state. This error may occur as a result of memory exhaustion; attempt to resolve any memory issues before attempting to solve this problem. After system resource isses have been resolved, issue ’process restart cfmd 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-CFM-3-CFG_MP_UPDATE_INCONSISTENCY

Failed to update MP config on interface CH[hex]: [chars]

Explanation CFM encountered an error while trying to delete and/or create Maintenance Points on the specified interface and retrying the operation has not resolved the problem. This situation could indicate that system resources are low. The operational state of CFM will now be out-of-sync with configuration as some Maintenance Point deletes and/or creates have failed.

Recommended Action Restarting the CFM Daemon on the node where the problem has occurred may help to resynchronize the system state. This error may occur as a result of memory exhaustion; attempt to resolve any memory issues before attempting to solve this problem. After system resource isses have been resolved, issue ’process restart cfmd 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-CFM-3-CFG_SLA_INST_FAILED

The creation of an SLA operation failed: [chars]

Explanation CFM encountered an error while trying to create new SLA operations. This situation could indicate that system resources are low. The operational state of CFM will now be out-of-sync with configuration as some SLA operations will not have been created.

Recommended Action Restarting the CFM Daemon on the node where the problem has occurred may help to resynchronize the system state. This error may occur as a result of memory exhaustion; attempt to resolve any memory issues before attempting to solve this problem. After system resource isses have been resolved, issue ’process restart cfmd 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-CFM-3-CFG_XC_MEP_CREATE_FAILED

Failed to create cross-check MEPs following a change to CFM configuration on interface CH[hex]: [chars]

Explanation CFM encountered an error while trying to create new cross-check MEPs This situation could indicate that system resources are low. The operational state of CFM will now be out-of-sync with configuration as some cross-check MEPs will not have been created.

Recommended Action Restarting the CFM Daemon on the node where the problem has occurred may help to resynchronize the system state. This error may occur as a result of memory exhaustion; attempt to resolve any memory issues before attempting to solve this problem. After system resource isses have been resolved, issue ’process restart cfmd 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-CFM-3-DB_DELETE_FAILED

Failed to delete [chars] object (ID [chars]) from the [chars] database, because the object wasn’t found

Explanation A user requested that an object be removed from a database in which it was not present. The process should recover from this event, but it may indicate an internal inconsistency which could cause other problems.

Recommended Action *SUPPORT*

Error Message %L2-CFM-3-DB_INCONSISTENT

An error condition that indicates an internal inconsistency in a database was encountered: [chars]

Explanation An internal inconsistency was identified while performing some operation on the database. The process will attempt to recover a consistent state, and should be able to continue operating. It is possible that some parts of CFM may become out of sync.

Recommended Action If additional problems are observed then restarting the process may help to restore the system to a consistent state. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-DB_LOCK_ERROR

Failed to perform [chars] operation on [chars] lock in database: [chars]

Explanation An error was encountered while trying to perform an operation on a lock. The thread will continue without retrying the operation. In most cases, no further adverse behaviour should be observed.

Recommended Action *SUPPORT*

Error Message %L2-CFM-3-EA_ERROR

CFM EA failed to process the new CFM configuration on interface CH[hex]. [chars]

Explanation CFM encountered an error while trying to update the hardware packet handling after a configuration update, and retrying the operation has not resolved the problem. This situation could indicate that system resources are low, or a problem with another part of the system. It is possible that CFM will not receive packets that it should be processing, or packet processing may operate more slowly than expected.

Recommended Action Restarting cfmd or cfm_ea processes on the affected node may help to update the packet handling correctly. This error may occur as a result of memory exhaustion; attempt to resolve any memory issues before attempting to solve this problem. After system resource isses have been resolved, issue ’process restart cfmd’ on the affected node. If that has no effect, issue ’process restart cfm_ea’ on the node with the affected interfaces. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-ECM_RETRY_ERROR

Failed to schedule a retry attempt using the Event Connection Manager library: [chars]

Explanation CFM encountered an error while attempting to schedule a retry for a failed operation. The operation will not be retried. It is likely that some Maintenance Points will not be created. This may indicate that system resources are low.

Recommended Action Attempt to resolve any memory issues before attempting to solve this problem. After system resource isses have been resolved, issue ’process restart cfmd’ on the affected 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-CFM-3-ELO_LB_STATE

Failed to retrieve the 802.3 Ethernet Link OAM loopback state of some physical interfaces. [chars]

Explanation CFM encountered an error while trying to retrieve the 802.3 Ethernet Link OAM loopback state of some physical interfaces, in order to report the state correctly in outgoing CCMs. This situation could indicate a problem in the Ethernet Link OAM daemon (elod) process, or that system resources are low, or a problem with another part of the system. It is likely that the interworking state reported in outgoing CCM messages will be incorrect.

Recommended Action Restarting the CFM Daemon or Ethernet Link OAM Daemon may help to resynchronize the loopback state. This error may occur as a result of memory exhaustion; attempt to resolve any memory issues before attempting to solve this problem. After system resource isses have been resolved, issue ’process restart cfmd’ and ’process restart elod’ on the node with the affect interfaces. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-ENCAP_ALLOC

Failed to process an encapsulation change. Error: [chars]

Explanation CFM was unable to process a change in interface encapsulation. As a result packets sent by CFM may be sent with the incorrect encapsulation. This indicates that either system resources are low, or that there is an internal problem with CFM.

Recommended Action Wait until any situation which is putting stress on system resources is resolved, and then try to delete and re-apply the encapsulation 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-CFM-3-ENGINE_TIMER

Failed to process engine timer: [chars]

Explanation An error occurred while processing the engine thread timer wheel. This may cause CCMs not to be sent, or peer MEPs not to time out after the configured loss time.

Recommended Action The process may recover after 60s. If the problem persists, it may be possible to recover by restarting the ’cfmd’ process on the node where the problem occurred.

Error Message %L2-CFM-3-FAULT_NOTIFICATION

Failed to generate a fault notification for a local MEP - domain: [chars], service: [chars], MEP ID: [unsigned int], interface: CH[hex]: [chars]

Explanation An error was encountered when trying to generate a fault notification for a local MEP, as a result of a defect detected from a peer MEP. This will mean that the corresponding SNMP trap will not be raised. If the error persists, CFM may not operate correctly.

Recommended Action If the error persists, it may be cleared by restarting the cfmd process on the node where the error is occurring.

Error Message %L2-CFM-3-IM_STATE_ERROR

Failed to reply to Interface Manager with states for [unsigned int] interfaces: [chars]

Explanation CFM encountered an error while trying send a state message to Interface Manager, and the error could not be recovered from by retrying. Interface Manager is likely to continue to wait for a response, and then shut down the affected interfaces.

Recommended Action The state operation is not essential to the operation of CFM, so if no ill effects are observed then no action is needed. If the Interface Manager shuts the interfaces down unexpectedly, then try issuing ’no shutdown’ for each affected interface, to refresh the state. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-INV_DEBUG_FLTR

Failed to enable the requested debugging. Invalid debug filter string: [chars]

Explanation The CFM debug library was notified about the creation of a debug item in SysDB which had an unexpected number of filter parameters. The corresponding debugging flag has not been enabled in CFM, which may lead to some debug not being printed as expected.

Recommended Action If any problems are observed, then try removing the debug filter using the ’no debug ethernet cfm’ command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-L2FIB_ERROR

Failed to communicate with the L2FIB Infrastructure: [chars]

Explanation The L2FIB Infrastructure reported an error which could not be handled. The operation will not be retried - the internal state of CFM may not match the global system state.

Recommended Action If any problems are observed, then check the status of the l2fib and l2vpn processes for any obvious errors. If necessary, try restarting the process that encountered the error using the ’process restart’ command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-LWM_ERROR

Failed to send a [chars] LWM message from [chars] to [chars] thread in the CFM Daemon - message type: [chars]: [chars]

Explanation The LWM subsystem indicated an error when trying to send a message between threads in the CFM Daemon, which could not be handled. The operation will not be retried - the internal state of CFM may not match the global system state.

Recommended Action If any problems are observed, then try restarting the CFM Daemon using the ’process restart’ command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-MEPS_DELETE_CCM_GEN

Attempt to delete [unsigned int] MEPs while some MEPs are having CCM generation enabled/disabled.

Explanation The CFM MA tried to delete a number of MEPs whilst some of those MEPs were scheduled to have CCM generation enabled or disabled. The CCM generation batches have been cleared, which may cause an inconsistency between CFM’s internal state and the requested configuration.

Recommended Action If any problems are observed, then try restarting the CFM Daemon using the ’process restart’ command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-MP_DB_ALLOC

Failed to create Maintenance Point [chars] in the database. Error [chars]

Explanation The CFM MA was unable to create a new Maintenance Point in the database. This indicates that either system resources are low, or that there is an internal problem with CFM. The set of Maintenance Points created by CFM will not match the requested configuration.

Recommended Action Wait until any situation which is putting stress on system resources is resolved, and then try to delete and re-apply the configuration for the affected Maintenance Points. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-PAK_ERROR

Failed while processing packet in [chars]: [chars]

Explanation An error occurred unexpectedly while calling the packet management infrastructure to handle a CFM packet during packet send.

Recommended Action The ’cfmd’ process will restart after this error is seen. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-RETRY_EXCEEDED

Reached the maximum number of retry attempts for [chars]. Failed updates for [unsigned int] interfaces will not be applied

Explanation The CFM MA attempted the maximum number of retrys for a failed operation. The operation will not be retried again. The MA will attempt to recover, but it is possible that the Maintenance Points created will not match those specified in configuration. The problem could be caused by a system resource issue.

Recommended Action Attempt to resolve any memory issues before attempting to solve this problem. After system resource isses have been resolved, issue ’process restart cfmd’ on the affected 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-CFM-3-STATE_UPDATE_DROPPED

Failed to update [unsigned int] interface states in CCMs.

Explanation There were insufficient system resources to provide the CFM Protocol Manager with interface state updates. The state update notifications will not be delivered, and the interface states in Continuity Check Messages will be incorrect for the affected interfaces. Other CFM functionality is unaffected.

Recommended Action Wait until any situation which is putting stress on system resources is resolved, and then issue the ’process restart cfmd’ command to resynchronize the Interface states within CFM. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-3-WL_QUEUE_FAILED

Failed to schedule Maintenance Point [chars] processing for [chars]. [chars]

Explanation The CFM MA failed to schedule an operation required to modify Maintenance Point configuration for an interface. This is likely to be a system resource issue.

Recommended Action Attempt to resolve any memory issues before attempting to solve this problem. After system resource isses have been resolved, issue ’process restart cfmd’ on the affected 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-CFM-4-AIS_EXPIRY_TIMER

Failed to restart AIS expiry timer for MEP in domain [chars], service [chars], local MEP ID [unsigned int] on interface CH[hex]: [chars]

Explanation An error occurred while restarting the AIS expiry timer for the local MEP specified in the error message. This could cause a received AIS or LCK signal to be incorrectly reported as having stopped.

Recommended Action If the error persists and the local MEP continually reports the received signal as starting and stopping, the problem may be corrected by restarting the cfmd process on the node where the problem is being reported.

Error Message %L2-CFM-4-BD_BATCH_DELETE_FAILED

Failed to allocate memory for batched delete of unused bridge domains.

Explanation Following a configuration change, CFM no longer needs to retain information about some bridge domains but has failed to delete the information from its database. The process will continue to operate correctly but is using more memory than is necessary.

Recommended Action No specific action is needed, though the warning could be a sign of low memory conditions. If other memory issues are seen, resolve those first and then reapply the configuration change.

Error Message %L2-CFM-4-CCM_PARSE_FAILED

Failed to process CCM received by MEP in domain [chars], service [chars], local MEP ID [unsigned int] on interface CH[hex], CCM received from [chars]: [chars]

Explanation An error occurred while processing a received CCM message - the error string gives more details. This error is not caused by malformed or invalid packets. If the error persists, CFM may not operate correctly.

Recommended Action If the error persists, it may be cleared by restarting the cfmd process on the node where the error is occurring.

Error Message %L2-CFM-4-CFG_INCONSISTENT

Configuration change requested is inconsistent with the current state: [chars]

Explanation CFM recieved a configuration update that can not be processed because it is not consistent with the current internal state. The requested update will be rejected.

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

Error Message %L2-CFM-4-EFD_SHUTDOWN_ERROR

Failed to shut down interface CH[hex]: [chars]

Explanation A failure occurred when attempting to shut down an interface using EFD after a fault condition was detected by one of the local MEPs on the interface. This event was triggered by either a change within the network (e.g. detecting a defect with a remote MEP) or a change in configuration that enabled EFD on a service. This will result in the interface remaining up, when it should be shut down.

Recommended Action If the error is the result of a configuration change, remove and reapply the configuration. If this does not work, or the error was triggered by a change in the network, the error may be cleared by restarting the cfmd process on the node where the error is occurring.

Error Message %L2-CFM-4-ELMI_UPDATE_FAILED

Failed to update E-LMI with EVC and remote UNI details: [chars]

Explanation A failure occured when attempting to update E-LMI. This event was triggered by either a change within the network (e.g. a remote MEP going missing), a change to local MEP or cross-check configuration or E-LMI starting up and requesting information. The result is that E-LMI will not have the most up to date information to report to the CE device.

Recommended Action To trigger a replay of information between E-LMI and CFM, try restarting the CFM Daemon using the ’process restart’ command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-4-ENCAP_CHANGE

[chars]: [chars] on Interface CH[hex] - CFM [chars] on this interface

Explanation Set: Packets cannot be sent by CFM from the interface mentioned in the message, for one of the following reasons: - The interface has no encapsulation configured. - The interface has a complex encapsulation configured, which is not supported in conjunction with CFM. Complex encapsulations include: - Matching on source or destination MAC addresses - Matching on payload ethertype - Matching on VLAN tags using the ’any’ keyword. In these cases, it cannot be determined how to format the ethernet header for sending CFM packets, and hence CFM is not supported in these scenarios. - The CoS bits configured for the MEP conflict with the CoS bits configured in the interface encapsulation. Clear: the error condition no longer holds; the interface has a supported encapsulation and CFM packets can be sent.

Recommended Action If the problem relates to the encapsulation, then either configure the encapsulation on the interface, without using the above types of ’complex’ matching criteria, or deconfigure any CFM MEPs on the interface. If the problem is a conflict in the CoS bits, then either reconfigure either the MEP or the encapsulation, so that the CoS bits specified for the MEP fall within the CoS bits specified in the encapsulation, if any.

Error Message %L2-CFM-4-ERR_CONFIG

Unsupported CFM config detected on interface handle [hex]. Total packets dropped [dec]

Explanation Ethernet OAM CCMs are configured for an Layer 2 VPN interface over an unsupported pseudowire encapuslation

Recommended Action Ethernet OAM CCMs upward MEP/MIP configuration is not supported for VPLS/L2TPv3 based L2VPN Attachment Circuits. Please review ethernet CFM configuration attached to the L2VPN interfaces and remove the unsupported Ethernet CFM upward MEP/MIP configuration.

Error Message %L2-CFM-4-EXIT_FAILED

Failed to notify SysMgr that [chars] is exiting: [chars]

Explanation The specified process failed to notify the system manager that it was exiting. In very rare cases, this could result in the process not being restarted when it ought to be.

Recommended Action If the process in not running and it ought to be (ie, there is CFM configuration remaining), then remove all CFM configuration, commit this change, then re-apply the configuration.

Error Message %L2-CFM-4-INIT_FAILED

Failed to initialize [chars]: [chars]%s

Explanation An error was encountered while the specified process was initializing. The error message contains details about the source of the error.

Recommended Action The process will exit and will be restarted. If the problem persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-CFM-4-LOSS_TIMER_FAILED

Failed to restart loss timer for MEP in domain [chars], service [chars], local MEP ID [unsigned int] on interface CH[hex], peer MAC [chars], peer MEP ID [unsigned int]: [chars]

Explanation An error occurred while restarting the loss timer for the peer MEP specified in the error message. This could cause the peer MEP to incorrectly be timed out some time later.

Recommended Action If the error persists and peer MEPs continually flap as a result, the problem may be corrected by restarting the cfmd process on the node where the problem is being reported.

Error Message %L2-CFM-4-LOST_EVENT

[chars] lost event: [chars]

Explanation The specified process failed to receive an event that was sent to it.

Recommended Action If any problems are seen, they may be rectified by restarting the process using the ’process restart’ command.

Error Message %L2-CFM-4-MIB_CHKPT_BATCH_ERROR

Failed to manage the checkpointed state: [chars]. [chars]

Explanation CFM encountered an error while trying to maintain its checkpoint database. The checkpoint database is used to manage persistent MIB index values for accessing Domains and Services over SNMP. If an error was encountered then CFM has been unable to guarantee that MIB index values will be correctly maintained across process restarts, and existing database objects may have their MIB indices re-assigned.

Recommended Action CFM should continue to operate normally, except for possible re-ordering of MIB index values for any configured Domains and Services. CFM will have tried to correct any errors it encountered in the checkpoint database. If additional problems with CFM configuration are observed, then restarting the CGM Global Manager may help to resolve the problem. The CFM Global Manager can be restarted by issuing ’process restart cgm’ on the affected 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-CFM-4-MIB_CHKPT_ITEM_ERROR

Failed to manage the checkpointed state for a single item: [chars]. [chars]

Explanation CFM encountered an error while trying to maintain its checkpoint database, for a single item in the database. The checkpoint database is used to manage persistent MIB index values for accessing Domains and Services over SNMP. If an error was encountered then CFM has been unable to guarantee that MIB index values will be correctly maintained across process restarts, and existing database objects may have their MIB indices re-assigned.

Recommended Action CFM should continue to operate normally, except for possible re-ordering of MIB index values for the affected items. CFM will have tried to correct any errors it encountered in the checkpoint database. If additional problems with CFM configuration are observed, then restarting the CGM Global Manager may help to resolve the problem. The CFM Global Manager can be restarted by issuing ’process restart cgm’ on the affected 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-CFM-4-NOTIFY_AIS_FAILED

Failed to relay information about [chars] for MEP in domain [chars], service [chars], local MEP ID [unsigned int]: [chars]

Explanation The CFM packet handling module has detected that an AIS signal has changed (started or expired), but has failed to notify the management module. As a result, the proper handling for this event (eg generating log messages) will not take place.

Recommended Action If the error persists, the problem may be corrected by restarting the cfmd process on the node where the problem is being reported.

Error Message %L2-CFM-4-NOTIFY_LOSS_FAILED

Failed to relay information about loss of connectivity for MEP in domain [chars], service [chars], local MEP ID [unsigned int], peer MEP ID [unsigned int], peer MAC [chars]: [chars]

Explanation The CFM packet handling module has detected that a peer MEP has timed out (ie that no CCM has been received for the loss time), but has failed to notify the management module. As a result, the proper handling for this event (eg generating log messages and SNMP traps) will not take place.

Recommended Action If the error persists, the problem may be corrected by restarting the cfmd process on the node where the problem is being reported.

Error Message %L2-CFM-4-PACKET_DECODE_FAILED

Failed to decode [unsigned int] ethernet packets. First failed interface: CH[hex], first error: [chars]

Explanation An error occurred while attempting to decode a batch of ethernet frames which had been received. The source of the error is the Ethernet Packet Infrastructure. The received packets will be dropped as a result of this error. This could cause peer MEPs to time out, or ping/traceroute operations to fail.

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

Error Message %L2-CFM-4-PACKET_DECODE_UNEXPECTED_TLV

A packet of type [chars] was received on interface CH[hex] from source MAC [chars] in domain [chars] (level [unsigned int]) service [chars], with an unexpected TLV of type [unsigned int]. The unexpected TLV was ignored and the packet was processed.

Explanation A packet containing an unexpected TLV was received on the given interface. The packet has been processed normally and the unexpected TLV has been ignored. This message indicates that the device from which this packet originated is creating packets which deviate from the expected format of packets of this type according to the IEEE specification (IEEE 802.1ag-2007 or ITU-T Y.1731 02/2008). While the message is harmless, the user may wish to check the standards compliance of the remote device, which is indicated by the provided source MAC address.

Recommended Action None.

Error Message %L2-CFM-4-RCV_REGISTER

Failed to re-register to receive packets on [unsigned int] interfaces. First error: [chars]

Explanation After a system event, CFM was requested to re-register to receive packets on all the interfaces where it is enabled, but this failed for some interfaces. CFM packets may no longer be received on the affected interfaces.

Recommended Action If the error persists, it may be cleared by restarting the cfmd process on the node where the error is occurring.

Error Message %L2-CFM-4-SLR_FAILED

Failed to send SLR in response to SLM received by MEP in domain [chars], service [chars], local MEP ID [unsigned int] on interface CH[hex], SLM recieved from [chars]: [chars]

Explanation An error occurred while processing a received SLM message, resulting in a failure to send a SLR reply. - the error string gives more details. This is a problem because the SLR is needed in order for the sender to correctly calculate packet loss measurements. This error is not caused by malformed or invalid packets. The SLM test session will now be invalid.

Recommended Action If the error reason given at the end of the message indicates that the SLM database has reached its entry limit, then no more new SLM sessions can be supported. The system can support 16,000 SLM sessions in progress simulataneously, this message will be seen if more than that number are being attempted (per linecard). This message may also be seen if there are inactive SLM sessions still stored in the database, taking the total entries above the limit. Any inactive session entries will be cleared by the database within 5 minutes. To resolve the issue urgently, the database may also be cleared by restarting the cfmd process on the node where the error is occurring. This action will result in all existing test sessions reporting a small number of lost packets. Otherwise, the error reason will either indicate memory exaustion on the LC, or some other unexpected condition. If this error occurred as a result of memory exhaustion; attempt to resolve any memory issues before attempting to solve this problem. As we have failed to respond to an SLM, it may be useful to restart the test from the source device once the issue is resolved.

Error Message %L2-CFM-4-SPIO_WARNING

Internal SPIO Error : [chars]

Explanation SPIO PD software error has occured. Exact reason given by the error string

Recommended Action Collect SPIO PI and PD traces along with console logs. show spio trace cfm location sh spio ifhcache cfm/elo ifhandle

Error Message %L2-CFM-6-AIS_LCK_CHANGE

[chars] on local MEP in domain [chars], service [chars] with MEP ID [unsigned int] on interface CH[hex][chars]

Explanation A new AIS or LCK signal was received by a local MEP or an existing signal expired. This message appears because the service to which the local MEP belongs has AIS logging configured.

Recommended Action None.

Error Message %L2-CFM-6-CC_ERROR

Peer MEP error change: [chars] - domain [chars], service [chars], local MEP ID [unsigned int], local interface CH[hex], peer MEP ID [unsigned int], peer MAC address [chars], errors [chars]

Explanation A change in the errors reported by a CCM message from a peer MEP was detected. This message appears because the service which the local MEP belongs to has continuity-check error change logging configured.

Recommended Action None.

Error Message %L2-CFM-6-EFD_CHANGE

Interface CH[hex] [chars] by MEP ID [unsigned int] in domain [chars], service [chars]

Explanation An interface was shut down or brought up by a local MEP after a fault condition was detected or cleared. The action is taken because the service to which the local MEP belongs has EFD configured; this message appears because the service has EFD logging configured.

Recommended Action None.

Error Message %L2-CFM-6-MEP_CHANGE

Peer MEP change: [chars] - domain [chars], service [chars], local MEP ID [unsigned int], local interface CH[hex], peer MEP ID [unsigned int], peer MAC address [chars], errors [chars]

Explanation A CCM message was received from a new peer MEP, or a previously-known peer MEP timed out (i.e. its configured loss threshold was exceeded). This message appears because the service which the local MEP belongs to has continuity-check state change logging configured.

Recommended Action None.

Error Message %L2-CFM-6-SHMWIN_RESET

Resetting CFM shared memory data: [chars]

Explanation The CFM shared memory window is being reset. All shared memory data will be lost. This means that all per-interface, per-MEP and per-peer-MEP counters are reset to zero.

Recommended Action None.

Error Message %L2-CFM-6-TOO_MANY_TLVS

More than the supported number of TLVs were found while processing [chars] (total length [unsigned int])

Explanation While processing a received CFM PDU, more than the supported number (32) of TLVs were found. This is very unlikely to occur in normal operation, and may therefore indicate a denial-of-service attack.

Recommended Action Use CFM debugging (’debug ethernet cfm packets’) to determine from where the problematic packets are originating. If the packets are from a trusted source and are expected, modify the configuration on that host to reduce the number of organisation-specific or otherwise unknown TLVs contained in the packet (ie TLVs not defined in the CFM standard, IEEE 802.1ag).

Error Message %L2-CFM-6-XC_ERROR

Cross-check error change for local MEP in domain [chars], service [chars] with MEP ID [unsigned int] on interface CH[hex] for configured cross-check MEP ID [unsigned int][chars]: [chars]

Explanation A change in the cross-check status of a peer MEP was detected. This may indicate an expected peer MEP configured by cross-check is missing, or a CCM message has been received unexpectedly from a peer MEP which was not configured for cross-check, or that one of the above errors has been cleared. This message appears because the service which the peer MEP belongs to has cross-check error change logging configured.

Recommended Action None.

CFMMIB Messages

Error Message %L2-CFMMIB-3-NO_DEBUG

Unable to register for DOT1AG MIB debug. No further debugging will occur: [chars]

Explanation In the initialisation of the DOT1AG MIB DLL an error occurred whilst attempting to register for debugging. Consequently there will be no debug output from the DOT1AG MIB DLL.

Recommended Action Continue working with the DOT1AG MIB DLL without any debugging taking place or restart the DLL such that during initialisation there is another attempt register for debugging.

Error Message %L2-CFMMIB-3-NO_STACK

Unable to set up Dot1agCfmStackEntryTable filtered view. Items in the Dot1agCfmStackEntryTable will not be accessible: [chars]

Explanation In the initialisation of the DOT1AG MIB DLL an error occurred whilst trying to set up a filtered interface table for stack entry lookups. As such, items in the Dot1agCfmStackEntryTable will not be accessible via SNMP requests.

Recommended Action Continue working with the DOT1AG MIB DLL without any the ability to query the Dot1agCfmStackEntryTable, or restart the mibd_interface process in an attempt to clear the error.

Error Message %L2-CFMMIB-3-NO_TRAP

Unable to register for SNMP traps. Traps will not be sent regardless of trap events occurring: [chars]

Explanation In the initialisation of the DOT1AG MIB DLL an error occurred whilst trying to register a callback function for the enabling of SNMP traps. Alternatively whilst trying to enable traps there was a failure in binding to SysDB for trap notifications.

Recommended Action Continue working with the DOT1AG MIB DLL without any the ability to send traps when events occur or restart the DLL such that there is another attempt to register for traps.

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_IMC_MULTIPLE_NTFCNS

CH[hex]: Multiple [chars] notifications received in a single batch from IM

Explanation A batch from IM 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_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-4-ERR_PKT_API_HANDLER

Failure during the handling of an event received from the packet thread in [chars]: [chars].

Explanation A failure occured whilst handling an event received from the packet thread.

Recommended Action *RECUR*

Error Message %L2-CHDLC_MA-4-ERR_PKT_HANDLER

Failure during the handling of a packet event in [chars]: [chars].

Explanation A failure occured whilst handling a packet event.

Recommended Action *RECUR*

Error Message %L2-CHDLC_MA-4-ERR_THREAD

Failure during a cross thread operation in [chars]: [chars].

Explanation A failure occured during thread handling.

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

CHNLZD_EFCM Messages

Error Message %L2-CHNLZD_EFCM-3-ERROR_CFG_BUFF_MAP_MEMORY

Error mapping to SPA bridge controller configuration buffer

Explanation An error has occurred in the Extended Flow Control Manager. EFCM was unable to map shared memory for debug.

Recommended Action *RECUR*

Error Message %L2-CHNLZD_EFCM-3-ERROR_CFG_BUFF_OPEN_MEMORY

Error opening SPA bridge controller configuration buffer.

Explanation An error has occurred in the Extended Flow Control Manager. EFCM was unable to open shared memory for debug.

Recommended Action *RECUR*

Error Message %L2-CHNLZD_EFCM-3-ERROR_COMM_ERR_SET_EFC_ENTRY

Unable to set extended flow control calendar entry : bay([dec]) interface handle([hex]), [chars]

Explanation An error has occurred in the Extended Flow Control Manager. An attempt to set an entry in the Flow Control calendar failed. This error indicates that messaging between the SPA process and the Jacket process failed.

Recommended Action *RECUR*

Error Message %L2-CHNLZD_EFCM-3-ERROR_COMM_SPA_CLIENT_INIT

SPA client initialization failed during extended flow control calendar initialization, [chars]

Explanation An error has occurred in the Extended Flow Control Manager. An attempt to set an entry in the Flow Control calendar failed. This error indicates that messaging between the SPA process and the Jacket process failed.

Recommended Action *RECUR*

Error Message %L2-CHNLZD_EFCM-3-ERROR_EINVAL_SET_CALENDAR_ENTRY

Invalid parameters while setting extended flow control manager entry. Channel [dec] bay [dec]

Explanation An error has occurred in the Extended Flow Control Manager. This is caused by an out of bounds Flow Control channel number or bay number trying to be used during the configuration of Flow Control for the SPA.

Recommended Action *RECUR*

COMMS Messages

Error Message %L2-COMMS-3-MSG_DROPPED

Unexpected error has lead to an incoming message being dropped: [chars]

Explanation An incoming control message could not be fully processed due to an unexpected error.

Recommended Action Restarting the process in question should result in a full resync of all data. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-COMMS-3-MY_ID_MISMATCH

Checkpoint data for this connection (id %hu) has invalid id (%hu)

Explanation The Checkpoint table contained unexpected data. This is unexpected, and could indicate memory corruption of some sort.

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

Error Message %L2-COMMS-3-MY_SAVE_FAILED

Failed to save Checkpoint sequence information for connection [chars]

Explanation The client failed to save its own sequence data to Checkpoint. If the process restarts before the save is successfully retried, remote clients may get out of sync, and data loss could occur.

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

Error Message %L2-COMMS-3-SAVE_FAILED

Failed to save Checkpoint entry [hex]/[hex] on connection [chars]

Explanation The client failed to save data to Checkpoint. If the process restarts before the save can be retried, then data loss could occur.

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

Error Message %L2-COMMS-4-DUPLICATE_ENTRY

Duplicate Checkpoint entry for ID %hu on node [hex]

Explanation The Checkpoint table contained a duplicate entry. This is unexpected, and likely indicates a software fault.

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

CPP_EXMEM Messages

Error Message %L2-CPP_EXMEM-6-THRESHOLD_CLEAR

CPP [dec] [chars] memory recovered - [dec] percent depleted

Explanation Exmem resource cross under its threshold

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

Error Message %L2-CPP_EXMEM-6-THRESHOLD_DECLARE

CPP [dec] [chars] memory low - [dec] percent depleted

Explanation Exmem resource cross over its threshold

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

cpp_sbs Messages

Error Message %L2-cpp_sbs-3-FATAL_ERR

[chars]: Err equals [hex]

Explanation A fatal error occurred in CPP Infra Stats Block Service 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.

CPP_TCAM_RM Messages

Error Message %L2-CPP_TCAM_RM-3-FATAL_ERR

Fatal error: [chars]: Err equals [dec]

Explanation A fatal error occurred in CPP 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-CPP_TCAM_RM-3-MSG_SEND_FAILED

cpp_tcam_rm: msg: [dec], retried: [dec] time(s), failed to send, errno: [chars]

Explanation Unable to send a message to the CPP 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-CPP_TCAM_RM-3-NONFATAL_ERR

Nonfatal error: [chars]: Err equals [dec]

Explanation This is a error message in the CPP 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-CPP_TCAM_RM-6-INFO_MSG

Info: [chars]

Explanation This is an informational message in the CPP TCAM RM.

Recommended Action No action is required.

CPPHA Messages

Error Message %L2-CPPHA-3-CDMDONE

CPP [dec] microcode crashdump creation completed

Explanation CDM has completed crashdump creation.

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-CPPHA-3-FAILURE

CPP [dec] failure [chars] detected

Explanation A CPP failure has been detected.

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-CPPHA-3-FAULT

CPP [dec] fault:[chars] det:[chars] class:[chars] sev:[chars] idx:[dec] cppstate:[chars] res:[chars] flags:[hex] cdmflags:[hex]

Explanation A CPP failure has been detected.

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-CPPHA-3-FAULTCRASH

CPP [dec] unresolved fault detected, initiating crash dump.

Explanation A CPP failure has been detected.

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-CPPHA-3-FAULTRATE

CPP [dec] fault:[chars] det:[chars] class:[chars] sev:[chars] idx:[dec] cppstate:[chars] res:[chars] flags:[hex] cdmflags:[hex]

Explanation A CPP fault has occurred

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-CPPHA-3-INITFAIL

CPP [dec] initialization failed - [chars] ([hex])

Explanation A CPP initialization failed.

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-CPPHA-3-NOCDM

CPP [dec] CDM not running.

Explanation A CPP failure has been detected.

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.

cpposlib Messages

Error Message %L2-cpposlib-3-CLEAN_NOTIFY

Failed to cleanup: ([chars]).

Explanation A function failed to cleanup.

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

Error Message %L2-cpposlib-3-ERROR_NOTIFY

[chars] encountered an error

Explanation A process encountered 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-cpposlib-3-INIT_NOTIFY

Failed to initialize: ([chars]).

Explanation A function failed to initialize.

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

CRS_PAK_BUFHDR Messages

Error Message %L2-CRS_PAK_BUFHDR-3-PACKET_LENGTH_EXCEED_FABRIC_LIMIT

packet will be dropped due to its length ([unsigned int]) exceeds fabric limit ([unsigned int])

Explanation The client is requesting to set packet length to a value that exceeds CRS fabric limit. Such a packet will be dropped. This may be caused by an internal software error or by the router’s receiving of malformed packets.

Recommended Action If the error messages persist, please collect the console log, software version, running configuration (show running-config), platform hardware inventory list (show platform), diagnostic information of RP or LC card in question (show diag location), and report to it CISCO engineering.

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.

DATAPATH_FPGA_API Messages

Error Message %L2-DATAPATH_FPGA_API-7-ERR

[chars] Reason:[chars]

Explanation TDatapath FPGA API generated errors.

Recommended Action No action is required.

Error Message %L2-DATAPATH_FPGA_API-7-ERROR

[chars]

Explanation TDatapath FPGA API generated errors.

Recommended Action No action is required.

DIV2_DM Messages

Error Message %L2-DIV2_DM-3-INFO

driver manager: service degrading error, reason equals [chars]

Explanation Driver manager encountered an error that would lead to degraded service.

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

Error Message %L2-DIV2_DM-3-INIT

Driver manager: init. error encountered, reason equals [chars]

Explanation Driver manager encountered an error and is not able recover frm it. A reason text will be supplied. Call support with this text.

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

Error Message %L2-DIV2_DM-3-NO_MEM

Driver manager: memory allocation error for %zd bytes

Explanation Driver manager encountered a fatal memory allocation error

Recommended Action Reduce other system activity (e.g. by killing non-essential processes) to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

DRIVERS_UTIL Messages

Error Message %L2-DRIVERS_UTIL-3-TUPLE_READ_ERROR

[chars]: Tuple read failed with error [hex] [chars]

Explanation An error occured when trying to read the tuple from sysdb.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

DWDM Messages

Error Message %L2-DWDM-3-FATAL

dwdm: fatal error encountered, reason 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.

Error Message %L2-DWDM-4-FORCED_MAINTENANCE

Port id: [chars], Forced Maintenance: [chars], Reason: [chars]

Explanation If Forced Maintenance has started at a port, it means that the port was put into Transport Admin State of ’maintenance’ when this activity was actually disallowed for it. Forced Maintenance ends when, either maintenance at the port is allowed again by the administrator, or when the Transport Admin State is changed back to some other rather than ’maintenance’.

Recommended Action A forced maintenance activity implies that there may be loss of traffic. A port should not be put into maintenance state (unless its absolutely necessary) if maintenance is disabled by the administrator. That status can be checked using show interfaces CLI.

Error Message %L2-DWDM-5-MAINTENANCE_DISABLED

Port id: [chars], [chars]

Explanation When optical layer maintenance for an interface is disabled by the administrator, an hourly syslog notification is logged regarding this, until maintenance is enabled back again. One should not put the port into OOS-MT state when maintenance is disabled, otherwise it will lead to a forced maintenance activity and there might be loss of traffic.

Recommended Action Do not change the transport admin state of the port to maintenance unless absolutely required.

Error Message %L2-DWDM-5-SRLG_OVERFLOW

Port id: [chars], The number of SRLGs for this port is too high - only the first [dec] have been recorded

Explanation Maximum 100 SRLGs can be configured per DWDM port at the CRS. If some application like CTC has more than this number to configure, it indicates this situation by configuring the 101st value with a positive integer. The above ios_msg gets logged in this scenario.

Recommended Action It is just a notification.

Error Message %L2-DWDM-6-CLEAR_COUNTERS

Cleared counters on [chars]

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

Recommended Action None.

Error Message %L2-DWDM-7-SET_WAVELENGTH

[chars] Wavelength Channel [dec] on [chars]

Explanation DWDM Controller has provisioned optics to [HW Default | Configured | GMPLS Signaled] wavelength.

Recommended Action None.

Error Message %L2-DWDM-7-STALE_WAVELENGTH

GMPLS Signaled Wavelength Channel [dec] is stale on [chars]

Explanation DWDM Controller Interface owner has lost contact with GMPLS Client. The controller shall continue to operate on the existing wavelength, resync to happen after reconnect with GMPLS Client. This is an informational message.

Recommended Action None.

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-4-MEM_INVALID_MQS_COUNTER_MAXTHR

MQS max threshold [dec] is not in supported limit (1 - 2048)

Explanation The new multicast counter max-threshold is crossing platform supported limit.

Recommended Action Re-configure with different max-threshold satisfying supported limit.

Error Message %L2-E3EGRESSQ-4-MEM_INVALID_MQS_COUNTER_MINTHR

MQS min threshold [dec] is not in supported limit (1 - 2048)

Explanation The new multicast counter min-threshold is crossing platform supported limit.

Recommended Action Re-configure with different min-threshold satisfying supported limit.

Error Message %L2-E3EGRESSQ-4-MEM_MQS_MAXTHR_NOT_MATCHING_CURR_MINTHR

MQS max-th [dec] is lesser than current min-th [dec]

Explanation The new multicast counter max-threshold is lesser than current min-threshold.

Recommended Action Re-configure with different max-threshold greater than current min-threshold.

Error Message %L2-E3EGRESSQ-4-MEM_MQS_MINTHR_NOT_MATCHING_CURR_MAXTHR

MQS min-th [dec] is greater than current max-th [dec]

Explanation The new multicast counter min-threshold is greater than current max-threshold.

Recommended Action Re-configure with different min-threshold less than current max-threshold.

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-4-MEM_INVALID_MQS_COUNTER_MAXTHR

MQS max threshold [dec] is not in supported limit (1 - 16384)

Explanation The new multicast counter max-threshold is crossing platform supported limit.

Recommended Action Re-configure with different max-threshold satisfying supported limit.

Error Message %L2-E5EGRESSQ-4-MEM_INVALID_MQS_COUNTER_MINTHR

MQS min threshold [dec] is not in supported limit (1 - 16384)

Explanation The new multicast counter min-threshold is crossing platform supported limit.

Recommended Action Re-configure with different min-threshold satisfying supported limit.

Error Message %L2-E5EGRESSQ-4-MEM_MQS_MAXTHR_NOT_MATCHING_CURR_MINTHR

MQS max-th [dec] is lesser than current min-th [dec]

Explanation The new multicast counter max-threshold is lesser than current min-threshold.

Recommended Action Re-configure with different max-threshold greater than current min-threshold.

Error Message %L2-E5EGRESSQ-4-MEM_MQS_MINTHR_NOT_MATCHING_CURR_MAXTHR

MQS min-th [dec] is greater than current max-th [dec]

Explanation The new multicast counter min-threshold is greater than current max-threshold.

Recommended Action Re-configure with different min-threshold less than current max-threshold.

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.

edge_l2fwd_rewrite Messages

Error Message %L2-edge_l2fwd_rewrite-2-FM_ADD_FEAT_ERR

[chars], Failed to add feature for [chars], err: [chars]

Explanation edge_l2fwd_rewrite failed to add specific feature in FM.

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

Error Message %L2-edge_l2fwd_rewrite-2-FM_DEL_FEAT_ERR

[chars], Failed to del feature for [chars], err: [chars]

Explanation edge_l2fwd_rewrite failed to delete specific feature in FM.

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

Error Message %L2-edge_l2fwd_rewrite-2-FWD_FEAT_NOT_SUPPORTED

[chars]: [chars] is not supported on E3 Linecards

Explanation The feature is not supported on E3 Linecards

Recommended Action Please contact the TAC representative for hardware information on which this feature is supported

Error Message %L2-edge_l2fwd_rewrite-2-FWD_MEMMGR_READ_ERR

[chars], Failed to read [chars] from FWD MemMgr, err: [chars]

Explanation edge_l2fwd_rewrite failed to read adj counters/PLU/TLU through FWD Memory manager.

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

Error Message %L2-edge_l2fwd_rewrite-2-HFA_CREATE_ERR

[chars],Failed to create gather index in HFA

Explanation edge_l2fwd_rewrite failed to create gather index in HFA

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

Error Message %L2-edge_l2fwd_rewrite-2-HFA_PROG_ERR

[chars],Failed to program [chars] ucast in HFA

Explanation edge_l2fwd_rewrite failed to program feature specific ucast in HFA

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

Error Message %L2-edge_l2fwd_rewrite-2-HFA_REGISTER_ERR

[chars],Unable to open connection with HFA

Explanation edge_l2fwd_rewrite Connection open with the HFA 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-edge_l2fwd_rewrite-2-INSERT_ENCAP_STRING_ERR

[chars], Insert encap string failed for Ifhandle equals [hex] err:[chars]

Explanation edge_l2fwd_rewrite failed while removing the encap string

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

Error Message %L2-edge_l2fwd_rewrite-2-MEM_REG_ERR

[chars], Error while registering with Forwarding Memory Manager

Explanation edge_l2fwd_rewrite Registration with the forwarding Memmgr 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-edge_l2fwd_rewrite-2-PLU_FREE_ERR

[chars],PLU free failed, error:[chars]

Explanation edge_l2fwd_rewrite Failed to free PLU though the forwarding Memory Manager

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

Error Message %L2-edge_l2fwd_rewrite-2-PLU_MALLOC_ERR

[chars], Failed to allocate memory for the PLU Leaf

Explanation edge_l2fwd_rewrite Forwarding memory module failed to allocate memory for the PLU leaf

Recommended Action Pls get the information specified under the component required_info and call your Cisco technical support representative and provide the representative with the gathered information with this error message text

Error Message %L2-edge_l2fwd_rewrite-2-PLU_WRITE_ERR

[chars],[dec],PLU write error:[chars]

Explanation edge_l2fwd_rewrite Failed while writing into the PLU though the forwarding Memory Manager

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

Error Message %L2-edge_l2fwd_rewrite-2-REMOVE_ENCAP_STRING_ERR

[chars], remove encap string failed OI equals [hex] err:[chars]

Explanation edge_l2fwd_rewrite failed while removing the encap string

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

Error Message %L2-edge_l2fwd_rewrite-2-RM_INIT_ERR

[chars], [dec] error, reason:[chars]

Explanation edge_l2fwd_rewrite Encap Resource Manager Initialisation error

Recommended Action Pls get the information specified under the component required_info and call your Cisco technical support representative and provide the representative with the gathered information with this error message text.

Error Message %L2-edge_l2fwd_rewrite-2-TLU_FREE_ERR

[chars],TLU free error:[chars]

Explanation edge_l2fwd_rewrite Failed to free TLU through forwarding Memory manager.

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

Error Message %L2-edge_l2fwd_rewrite-2-TLU_MALLOC_ERR

[chars], Failed to allocate memory for the TLU Leaf

Explanation edge_l2fwd_rewrite Forwarding memory module failed to allocate memory for the TLU leaf

Recommended Action Pls get the information specified under the component required_info and call your Cisco technical support representative and provide the representative with the gathered information with this error message text

Error Message %L2-edge_l2fwd_rewrite-2-TLU_SIZE_ERR

[chars], Invalid TLU write size, TLU size:[dec], Write Size:[dec]

Explanation edge_l2fwd_rewrite failed to write to TLU as the write size is not less than the actual TLU size

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

Error Message %L2-edge_l2fwd_rewrite-2-TLU_WRITE_ERR

[chars],[dec],TLU write error:[chars]

Explanation edge_l2fwd_rewrite Failed while writing into the TLU though the forwarding Memory manager.

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

Error Message %L2-edge_l2fwd_rewrite-2-UIDB_READ_ERR

[chars],Uidb read failed - err: [chars]

Explanation edge_l2fwd_rewrite Uidb read 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-edge_l2fwd_rewrite-2-UIDB_SET_ERR

[chars],Uidb set failed for xconnid:[dec], err: [chars]

Explanation edge_l2fwd_rewrite Uidb set 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-edge_l2fwd_rewrite-2-XBMA_ADD_ERR

[chars], Failed to add mcast entry, err: [chars]

Explanation edge_l2fwd_rewrite failed to add mcast entry in XBMA.

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

Error Message %L2-edge_l2fwd_rewrite-2-XBMA_CONN_ERR

[chars], Failed to connect to XBMA server, err: [chars]

Explanation edge_l2fwd_rewrite failed to connect to XBMA 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-edge_l2fwd_rewrite-2-XBMA_DEL_ERR

[chars], Failed to del mcast entry, err: [chars]

Explanation edge_l2fwd_rewrite failed to delete mcast entry in XBMA.

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

Error Message %L2-edge_l2fwd_rewrite-2-XBMA_INIT_ERR

[chars], Failed to initialize XBMA library, err: [chars]

Explanation edge_l2fwd_rewrite failed to initialize XBMA lib.

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

edge_l2fwd_table Messages

Error Message %L2-edge_l2fwd_table-2-FAD_DEL_ERR

[chars], Failed to delete [chars] for [chars] in FAD

Explanation edge_l2fwd_table failed to delete l2fwd lookup entry in FAD

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

Error Message %L2-edge_l2fwd_table-2-FAD_INIT_ERR

[chars], Failed to initialize FAD, reason:[chars]

Explanation edge_l2fwd_table FAD module failed to get initialized.

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

Error Message %L2-edge_l2fwd_table-2-FAD_INSERT_ERR

[chars], Failed to insert lookup entry for [chars] in FAD

Explanation edge_l2fwd_table failed to insert l2fwd lookup entry in FAD

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

Error Message %L2-edge_l2fwd_table-2-FAD_REGION_PROG_ERR

[chars], Failed to program [chars] region in FAD

Explanation edge_l2fwd_table failed to program TCAM region in FAD. The region is specific to feature(L2TPv3/VPLS etc)

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

Error Message %L2-edge_l2fwd_table-2-FAD_TCAM_FORMAT_PROG_ERR

[chars], Failed to program [chars] TCAM format in FAD

Explanation edge_l2fwd_table failed to program feature specific TCAM format in FAD layer.

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

Error Message %L2-edge_l2fwd_table-2-FAD_UPDATE_ERR

[chars], Failed to update lookup entry for [chars] in FAD

Explanation edge_l2fwd_table failed to update l2fwd lookup entry in FAD

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

Error Message %L2-edge_l2fwd_table-2-FM_CONFIG_ERR

[chars], Failed to set [chars] feature config in FM

Explanation edge_l2fwd_table failed to set feature specific config processing in FM.

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

Error Message %L2-edge_l2fwd_table-2-PLU_MALLOC_ERR

[chars], Failed to allocate memory for the PLU Leaf

Explanation edge_l2fwd_rewrite Forwarding memory module failed to allocate memory for the PLU leaf

Recommended Action Pls get the information specified under the component required_info and call your Cisco technical support representative and provide the representative with the gathered information with this error message text

Error Message %L2-edge_l2fwd_table-2-PLU_WRITE_ERR

[chars],[dec],PLU write error:[chars]

Explanation edge_l2fwd_rewrite Failed while writing into the PLU though the Forwarding Memory Manager

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

Error Message %L2-edge_l2fwd_table-2-reg_err

[chars],[dec] Table registeration failed ! Table type:[chars], direction:[dec]

Explanation edge_l2fwd_table failed to register the memory requirement and populate the memory 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-edge_l2fwd_table-2-TABLE_MALLOC_ERR

[chars], Failed to allocate memory for the Table: [chars]

Explanation edge_l2fwd_rewrite Forwarding memory module failed to allocate memory for the Table

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

Error Message %L2-edge_l2fwd_table-2-TLU_MALLOC_ERR

[chars], Failed to allocate memory for the TLU Leaf

Explanation edge_l2fwd_rewrite Forwarding memory module failed to allocate memory for the TLU leaf

Recommended Action Pls get the information specified under the component required_info and call your Cisco technical support representative and provide the representative with the gathered information with this error message text

Error Message %L2-edge_l2fwd_table-2-TLU_WRITE_ERR

[chars],[dec],TLU write error:[chars]

Explanation edge_l2fwd_rewrite Failed while writing into the TLU though the forwarding memory manager

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

Error Message %L2-edge_l2fwd_table-3-ERR

[chars], [dec] error, reason:[chars]

Explanation edge_l2fwd_table generic error

Recommended Action Pls get the information specified under the component required_info and call your Cisco technical support representative and provide the representative with the gathered information with this error message text

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-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 state: [chars], queue length: [dec] bytes, DFLT Q: [chars], HPQ: [chars]), group [dec] (dflt group: [chars]), port [dec]

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

Tor 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 No action is required. The driver will perform asic recovery. If the message recurs, copy the error message exactly as it appears on 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-IMDR_MAP_ERROR

IMDR Mapping error: ([chars]# [dec]) [chars]

Explanation There is a discrepancy between the egressq configuration before and after IMDR. The egressq configuration after IMDR should normally be the same as before. This could indicate an internal software error.

Recommended Action Watch for potential drop in the egress traffic. If the router misbehaves or traffic is dropped, please collect the information from the following commands for the line card that reported the error: show tech show controller egressq trace all show controller egressq interface all show controller egressq port all show controller egressq group all show controller egressq queue all show qos ea trace all Call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-EGRESSQ_HW_DLL-3-IO_ERROR

[chars] [chars] access error. [chars]

Explanation Egressq ASIC encountered a read or write access error or its Host Processor Interface block has gone down and come back up. The access error is classified into two classes - software or hardware. Hardware access error refers to an error at the PCI link used to connect the ASIC to the host processor. Software access error refers to the error, caused by a un-discovered software bug, which makes software to perform un-supported access to an ASIC location, like writing to a read-only location.

Recommended Action If the message indicated this is a hardware access error, software will have automatically taken action to recover from the error. If harware access error does not recur, no other action is required. If the hardware access error persists or it is a software access error, copy the System Message exactly as it appears on the console or in the system log, enter command ’show tech-support controller egressq location ’, report the error to 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], link trained: [chars], Port [dec], Group [dec], Queue [dec], Queue state: [chars])

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

ASIC Tor status: [chars]

Explanation Log the key asic registers when a queue stuck condition was detected.

Recommended Action No action is required. The driver will perform asic recovery. If the message recurs, copy the error message exactly as it appears on 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-RLDRAM_BIST_FAILURE

RLDRAM BIST test failed

Explanation Egress queueing ASIC encountered a failure when doing BIST testing on its external Redunced-Latency-DRAM (RLDRAM). Possible cause for this error condition is a faulty hardware.

Recommended Action No action is required. The linecard is automatically reloaded. If the error persists, replace the Modular Service Card (MSC).

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 present in unallocated egress queue [dec]. (queue state: [chars], queue length: [dec] bytes, DFLT Q: [chars], HPQ: [chars]), group [dec] (dflt group: [chars]), port [dec]

Explanation Egressq driver detected that packets were present in 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-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-6-INFO_MSG

[chars]

Explanation This is an informational message in the Egressq/Sharq Driver to indicate an operation.

Recommended Action No action is required.

Error Message %L2-EGRESSQ_HW_DLL-6-INFO_MSG

[chars]

Explanation This is an informational message in the Egressq/Tor Driver to indicate an operation.

Recommended Action No action is required.

Error Message %L2-EGRESSQ_HW_DLL-6-QDR_BIST_FAILURE

QDR BIST failed, [chars]

Explanation Egress Queue Manager encountered a QDR 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-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_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-3-QUEUE_STUCK

EgressQ Stuck condition detected (PLIM link [dec], Port [dec], Group [dec], Queue [dec], Len [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-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.

ELMI Messages

Error Message %L2-ELMI-4-AIPC

Unexpected AIPC error encountered while [chars]: [chars]

Explanation ELMI encountered an error using the AIPC infrastructure. The error message describes what operation has failed and why it failed. This is most likely to be due to a low memory condition but may also be an internal programming error.

Recommended Action Consider restarting the ELMI 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-ELMI-4-BAG

Unexpected bag error encountered while [chars]: [chars]

Explanation ELMI 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 ELMI’s ability to provide operational management data, but won’t otherwise affect ELMI’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-ELMI-4-DEBUG

Unexpected debug error encountered while [chars]: [chars]

Explanation ELMI 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, ELMI 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-ELMI-4-EVENT

Unexpected Event Manager error while [chars]: [chars]

Explanation ELMI encountered an error using the Event Manager library. The error message describes what operation has failed and why it failed. The most likely reason for this is a low memory resources or programming error.

Recommended Action Consider restarting the ELMI 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-ELMI-4-IM

Unexpected IM error encountered while [chars]: [chars]

Explanation ELMI 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, ELMI 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-ELMI-4-LTRACE

Unexpected ltrace error encountered while [chars] the [chars] buffer: [chars]

Explanation ELMI 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 ELMI 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-ELMI-4-MEM_ALLOC

Failed to allocate [unsigned int] bytes

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-ELMI-4-MGD_TIMER

Unexpected managed timer error encountered while [chars]: [chars]

Explanation ELMI 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 ELMI process. *RECUR*.

Error Message %L2-ELMI-4-MTU_WARNING

[chars] has a payload MTU of [unsigned int] which is smaller than the minimum value ([unsigned int]) required for correct operation

Explanation The E-LMI specification assumes that the MTU of the media that it is running over is exactly 1500 bytes. However, the protocol can run on lower values than this so long as the MTU is large enough to include a header, the report type IE, the sequence numbers IE, the data instance IE and a maximum length UNI IE. The message has been issued because the configured MTU is too small to meet this condition. The protocol will continue to run assuming that the MTU is this minimal required value and so may not operate correctly.

Recommended Action Reconfigure the interface’s MTU to a larger value.

Error Message %L2-ELMI-4-PROTOCOL_GENERIC

E-LMI protocol error occured on CH[hex]: [chars]

Explanation The entire PDU, or one or more IEs in the PDU, were ignored due to the given error. This indicates that the last PDU sent by the peer device was not formatted correctly.

Recommended Action Check that E-LMI is configured on the peer device and that the link to the peer device is functionining correctly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message %L2-ELMI-4-PROTOCOL_INVALID_IE

E-LMI protocol error occured on CH[hex]: [chars] [chars]

Explanation The entire PDU, or one or more IEs in the PDU, were ignored due to the given error. This indicates that the last PDU sent by the peer device was not formatted correctly.

Recommended Action Check that E-LMI is configured on the peer device and that the link to the peer device is functionining correctly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message %L2-ELMI-4-PROTOCOL_INVALID_MSG_TYPE

E-LMI protocol error occured on CH[hex]: [chars]: [unsigned int]

Explanation The entire PDU was ignored due to an unexpected message type being received. This indicates that the last PDU sent by the peer device was not formatted correctly.

Recommended Action Check that E-LMI is configured on the peer device and that the link to the peer device is functionining correctly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message %L2-ELMI-4-PROTOCOL_INVALID_PROTO_VER

E-LMI protocol error occured on CH[hex]: [chars]: [unsigned int]

Explanation The entire PDU was ignored due to an invalid protocol version being requested. This indicates that the last PDU sent by the peer device was not formatted correctly.

Recommended Action Check that E-LMI is configured on the peer device and that the link to the peer device is functionining correctly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message %L2-ELMI-4-RELIABILITY_INVALID_REPORT_TYPE

E-LMI reliability error occured on CH[hex]: [chars]. Report type received: [unsigned int].

Explanation The report type of the message received was inappropriate relative to the interface’s protocol state. For example, receiving an ’E-LMI Check’ while processing a ’Full’ STATUS report. This indicates that the last PDU sent to the peer device was not received.

Recommended Action Check that E-LMI is configured on the peer device and that the link to the peer device is functionining correctly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message %L2-ELMI-4-RELIABILITY_INVALID_SEQ_NUM

E-LMI reliability error occured on CH[hex]: Invalid received sequence number. Received [unsigned int], expected [unsigned int].

Explanation The sequence number received does not match the last sequence number sent. This indicates that the last PDU sent to the peer device was not received.

Recommended Action Check that E-LMI is configured on the peer device and that the link to the peer device is functionining correctly. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message %L2-ELMI-4-RELIABILITY_STATUS_ENQ_TIMEOUT

E-LMI reliability error occured on CH[hex]: Polling Verification Timer has expired.

Explanation The Polling Verification Timer has timed out because no STATUS ENQUIRY message has been received in the configured interval.

Recommended Action Check the Polling Verification Timer value configured is greater than the Polling Timer value configured on the peer device. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message %L2-ELMI-4-SYSDB

Unexpected SysDB error encountered while [chars]: [chars]

Explanation ELMI 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 ELMI 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-ELMI-4-SYSMGR

Unexpected SysMgr error encountered while [chars]: [chars]

Explanation ELMI encountered an error while communicating with SysMgr. The error message describes what operation has failed and why it failed. This is a fatal error and the ELMI 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-ELMI-4-WAVL_INIT

Error initializing the WAVL tree used to store ELMI IDBs: [chars].

Explanation ELMI 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-ELMI-5-EVC_ENCAP_CONFLICT

The EVC for CH[hex] will not be reported because the subinterface’s encapsulation of ’[chars]’ conflicts with that of subinterface CH[hex]. The total number of EVCs not reported due to conflicts is [unsigned int].

Explanation The Ethernet LMI protocol is unable to report EVCs for subinterfaces which have conflicting encapsulations. In this context, two subinterfaces have conflicting encapsulations if they belong to the same parent interface and any of the following conditions are true: they have at least one VLAN ID in common in the outermost tag; one matches untagged packets while the other matches priority-tagged packets; one is configured to match any VLAN ID in the outermost tag while the other is configured as the default match.

Recommended Action Re-configure the subinterface to use a different encapsulation. There may be more subinterfaces with conflicting encapsulation.

Error Message %L2-ELMI-5-EVC_IGNORED

The EVC for [chars] will not be reported because the subinterface number ([dec]) is larger than 65535. Including this one, [unsigned int] such EVCs will not be reported.

Explanation The E-LMI protocol can report at most 65535 EVCs per interface. Subinterfaces with numbers above this value are not reported to the peer device.

Recommended Action Re-configure the subinterface to use a subinterface number of 65535 or below.

Error Message %L2-ELMI-6-PROTOCOL_START_STOP

E-LMI protocol [chars] on CH[hex]

Explanation The operational status of the E-LMI protocol on the interface has changed. If undesired, the notification of protocol events can be turned off by configuring ’log events disable’ on the 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-ELMI-6-PROTOCOL_STATE_CHANGE

E-LMI operational status on CH[hex] has changed to [chars]

Explanation The operational status of the E-LMI protocol on the interface has changed. If undesired, the notification of protocol events can be turned off by configuring ’log events disable’ on the 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.

ELO_COMMON Messages

Error Message %L2-ELO_COMMON-3-SYSMGR_FAIL

Unable to signal that process is exiting: [chars]

Explanation The process has failed to inform System Manager that it is shutting down. The process will exit anyway, but it is possible that any configuration entered will not cause SysMgr to restart the process. In this case, a timeout will occur when committing configuration, and the config will fail to apply.

Recommended Action If configuration fails to apply, recommitting it should correct the issue. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ELO_COMMON-4-BLOCK_UNTIL_ACTIVE

Unable to block on sysmgr on the node which is in standby role: [chars]

Explanation The process failed to block on System Manager on a node which is in standby role and wait for the node to go active.

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

Error Message %L2-ELO_COMMON-4-PROC_READY_FAILED

Unable to signal process ready: [chars]

Explanation The process failed to inform System Manager that it is ready, and will be 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-ELO_COMMON-4-VERIFY_CLEANUP_FAILED

Failed to cleanup common verification module: [chars]

Explanation Whilst exiting, an error was encountered cleaning up a common module. The process will exit anyway, and no further errors should be 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-ELO_COMMON-4-VERIFY_INIT_FAILED

Failed to initialize common verification module: [chars]

Explanation The process has failed to initialize a module, and will be 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.

ELO Messages

Error Message %L2-ELO-3-BAD_CONFIG

Invalid configuration values applied: [chars]

Explanation Invalid configuration has been incorrectly applied. This can potentially indicate a recent change in acceptable configuration values, or an internal fault.

Recommended Action Check that all configuration is within the acceptable ranges for the current version of the software and the installed hardware. If the error persists, and all values are within range, copy and save this message, and call your technical support representative for assistance.

Error Message %L2-ELO-3-COULD_NOT_GET_NODEID

Ethernet Link OAM Daemon failed to determine the node it is running on: [chars]

Explanation The Ethernet Link OAM Daemon failed to determine the ID of the node on which it is running. It will exit, and should be restarted by 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-ELO-3-COULD_NOT_REMOVE_CAPS

Failed to remove PFI caps from interface ’CH[hex]’: [chars]

Explanation The Ethernet Link OAM Daemon failed to clean up a caps entry in PFI for the named interface. This error is not fatal in itself, although it may prevent OAM from being re-enabled on the given interface until the problem is resolved.

Recommended Action Read the error message, and attempt to resolve any issue that may have caused it. Restarting the Ethernet Link OAM Daemon will then allow it to resynchronise with PFI and cleanup the dangling caps. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ELO-3-DAEMON_INIT_FAILED

Ethernet Link OAM Daemon failed to initialize [chars]: [chars]

Explanation The Ethernet Link OAM Daemon failed to initialize correctly, and will now exit. It should be restarted by SysMgr.

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

Error Message %L2-ELO-3-ERRDIS_FAILED

CH[hex]: failed to Error-Disable the port: [chars]

Explanation The port should have been Error Disabled, but an unexpected error has prevented it from being shut down. The port is still up, and will not be disabled.

Recommended Action Shutdown the port manually if it is still desirable to bring it down. Otherwise, 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-ELO-3-EXITING

Ethernet Link OAM Daemon failed to process events: [chars]

Explanation The Ethernet Link OAM Daemon failed to process an event, and will now exit. It should be restarted by SysMgr, allowing it to resynchronise its internal 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-ELO-3-INTF_CAPABILITIES_LOOKUP_FAILED

Unable to lookup platform capabilities for interface ’CH[hex]’ : [chars]

Explanation The ethernet_link_oam_daemon has failed to determine the capabilities of a particular interface. 802.3 OAM configuration will be verified according to the global card capabilities. For certain interface types, this may result in configuration for a particular feature such as UDLF being incorrectly applied to an interface that does not support it. Operation of the protocol is unaffected and any unsupported configuration will be ignored.

Recommended Action This issue indicates that there was a problem retrieving interface capabilities for a specific card. This may affect your configuration. Attempt to remove and reapply any configuration changes you have made, if this fails call your technical support representative for assistance.

Error Message %L2-ELO-3-INTF_INIT_FAIL

[chars]: Failed to initialise the interface: [chars]

Explanation The Ethernet Link OAM Daemon was unable to initialise the specified interface. This is likely caused by a memory resource allocation error. The exact error can be found in the ’show ethernet oam interface’ command.

Recommended Action Un-configure and re-configure the interface. If that does not resolve the problem, restarting the process will cause a retry of the initialisation. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ELO-3-LOOPBACK_SET_FAILED

[chars]: Failed to change Loopback state in the platform: [chars]

Explanation An attempt to change the Loopback state of an interface failed. This will either be in response to a local command to change the remote peer’s Loopback state, or a command on the remote peer to put this interface in slave loopback mode.

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

Error Message %L2-ELO-3-LWM_REPLY_ERROR

Failed to send an LWM reply message in the Ethernet Link OAM Daemon: [chars]

Explanation The LWM subsystem indicated an error when trying to send a reply from the packet thread to the main thread in the Ethernet Link OAM Daemon. The operation will not be retried - the internal state of Ethernet Link OAM may not match the global system state.

Recommended Action Try restarting the Ethernet Link OAM Daemon using the ’process restart’ command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ELO-3-PACKET_LOCK_ERROR

Failed to perform a [chars] operation: [chars]

Explanation An error was encountered while trying to perform an operation on a lock. The thread will continue without retrying the operation. In most cases, no further adverse behaviour should be observed.

Recommended Action *SUPPORT*

Error Message %L2-ELO-3-PFI_CLEANUP_FAILED_ATTR_UNREGISTER

Failed to unegister with IMC for attribute notifications. Error message: [chars]

Explanation The Ethernet Link OAM daemon was unable to unregister for interface notifications with IM. The Ethernet Link OAM daemon may continue to receive notifications for interfaces it is not longer configured on.

Recommended Action Restart the Ethernet Link OAM daemon process. This should cause a re-registration with IM, ensuring the correct interfaces are registered for notifications. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ELO-3-RECEIVE_OAMPDU_FAILED

Failed to successfully receive an OAMPDU from SPIO: [chars]

Explanation The Ethernet Link OAM Daemon was unable to receive an OAMPDU successfully from SPIO. This could be due to the OAMPDU not being received properly or being corrupt such that the OAMPDU can’t be properly processed.

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

Error Message %L2-ELO-3-RESYNC_END_ERROR

Failed to signal the end of a resync with SPIO: [chars]

Explanation The Ethernet Link OAM Daemon failed to resync with SPIO upon startup or a process restart. This is due to an LWM failure when sending a message between the main and packet threads within Ethernet Link OAM daemon. The operation will not be retried - the internal state of Ethernet Link OAM may not match the global system state.

Recommended Action Try restarting the Ethernet Link OAM Daemon using the ’process restart’ command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ELO-3-SPIO_MODULE_INIT

Failed to register for packet IO on initialisation: [chars]

Explanation The Ethernet Link OAM Daemon was unable to register the module to send and receive packets. This is likely caused by a memory resource allocation 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-ELO-4-CHKPT_SAVE_FAILED

CH[hex]: failed to save checkpoint entry: [chars]

Explanation The Ethernet Link OAM Daemon failed to save the checkpoint entry for the given interface. Although this error is not immediately fatal, information will be lost if the process restarts before successfully saving its checkpoint data.

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

Error Message %L2-ELO-4-DAEMON_CLEANUP_FAILED

Ethernet Link OAM Daemon failed to cleanup [chars]: [chars]

Explanation The Ethernet Link OAM Daemon failed to cleanup correctly. It will exit anyway, and no further errors should be 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-ELO-4-EFD_SHUTDOWN_ERROR

Failed to shut down interface CH[hex]: [chars]

Explanation A failure occurred when attempting to shut down an interface using EFD after a fault condition was detected on the interface. This event was triggered by either a change in stateful condition of the link, a process restart or a change in configuration that enabled EFD on a particular action. This will result in the interface remaining up, when it should be shut down.

Recommended Action If the error is the result of a configuration change, remove and re-apply the configuration. If this does not work the error may be cleared by restarting the ethernet_link_oam_daemon process on the node where the error is occurring. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ELO-4-INVALID_PLATFORM_EVENT_IFH

Platform event triggered on interface ’CH[hex]’ for which OAM is not configured

Explanation The platform has triggered an event for an interface that has not been configured for Ethernet Link OAM. This indicates a bug in the software.

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

Error Message %L2-ELO-4-INVALID_PLATFORM_EVENT_TYPE

An unknown event of type ’[hex]’ has been triggered by the platform

Explanation The platform has triggered an event that is not recognized. This is most likely due to a bug in the platform layers.

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

Error Message %L2-ELO-4-LOOPBACK_FAILED

Etherenet Link OAM Daemon has failed to initiate loopback mode with a remote peer

Explanation The Ethernet Link OAM Damon has failed to initiate loopback mode. Loopback mode is unavailable until the issue is resolved.

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

Error Message %L2-ELO-4-NOT_IN_LOOPBACK

[chars]: Unable to exit Slave Loopback mode as requested, because we’re not currently in loopback mode

Explanation A requset has been made by the remote peer to stop Slave loopback mode. However, we are not currently in Slave loopback mode. This indicates that the remote peer is out of sync with our current state.

Recommended Action Start slave Loopback mode before attempting to stop it.

Error Message %L2-ELO-4-PFI_ERROR

CH[hex]: [chars] notification received from PFI, but interface does not have OAM configured

Explanation Unexpected updates have been received by the Ethernet Link OAM Daemon regarding interfaces on which OAM is not configured. This indicates that a resync is required between the OAM process and PFI.

Recommended Action Restart the Ethernet Link OAM Daemon on the affected node. This will force a resync of the state with PFI. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ELO-4-SEND_FAILED

[chars]: Failed to send a [chars] message: [chars]

Explanation Failed to send a message out of the given interface. The message has been lost, and will not be delievered to the remote peer.

Recommended Action Resynchonrisation mechanisms should ensure subsequent messages are correctly sent. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ELO-4-UNEXPECTED_OAMPDU_RECEIVED

Unexpected OAMPDU received on interface CH[hex].

Explanation The Ethernet Link OAM Daemon received an OAMPDU on an interface that was not configured with Ethernet Link OAM. The OAMPDU has been ignored. This message is harmless.

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

Error Message %L2-ELO-6-CPU_STARVED

Ethernet Link OAM Daemon has been unable to send heartbeats for [unsigned long long int] ms

Explanation The Ethernet Link OAM Daemon has been blocked or starved of CPU time. As a result, it will not have been able to send out periodic heartbeats regularly, potentially causing OAM sessions to drop. The problem is likely due to unusually high load on the system.

Recommended Action Identify any potential high CPU users, and reduce their impact. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ELO-6-EFD_CHANGE

Interface CH[hex] [chars] using EFD due to [chars]

Explanation An interface was shut down or brought up using EFD after a fault condition was detected or cleared, or due to a change in configuration. This has occurred because EFD is the configured action for this fault condition.

Recommended Action None - this message is for information only and does not indicate an error.

Error Message %L2-ELO-6-INTF_CAPABILITIES_CONFLICT

[chars]: Configuration conflict

Explanation Discovery mode cannot complete due to a conflict in the required configuration of the remote peer.

Recommended Action Ensure that the configuration requirements on this interface match the configuration of the remote OAM peer.

Error Message %L2-ELO-6-INTF_DISCOVERY_TIMEOUT

[chars]: OAM discovery failed to complete in the specified time

Explanation Discovery mode has been ongoing for the configured timeout, but no suitable response has been received from the remote peer.

Recommended Action Ensure the remote OAM peer is correctly configured and that the link is up.

Error Message %L2-ELO-6-INTF_REMOTE_CRITICAL_EVENT

[chars]: Remote critical event detected

Explanation The remote peer has indicated a critical event.

Recommended Action No specific IOS-XR action needs to be performed.

Error Message %L2-ELO-6-INTF_REMOTE_DYING_GASP

[chars]: Remote dying gasp detected, with reason: [chars]

Explanation The remote peer has indicated a dying gasp. This means that the remote peer is coming down.

Recommended Action Restart the remote peer.

Error Message %L2-ELO-6-INTF_REMOTE_LINK_FAULT

[chars]: Remote link fault detected

Explanation The remote peer has indicated that a link fault has occurred. This indicates a uni-directional link.

Recommended Action Check the wiring between the two interfaces.

Error Message %L2-ELO-6-INTF_REMOTE_LOOPBACK

[chars]: OAM [chars] loopback has been [chars] on the interface

Explanation The OAM session has either entered or exited local or remote loopback. If loopback has been entered then traffic flow will be disrupted until it is exited at which point normal functionality will resume.

Recommended Action None. This is an informational message.

Error Message %L2-ELO-6-INTF_SESSION_DOWN

[chars]: OAM session has gone down

Explanation The OAM session has ended. Either it has been deconfigured, or no response has been received from the OAM peer in the configured time interval.

Recommended Action Check that the remote peer is correctly configured still. If it is, then a large number of packets may be being dropped on the link.

Error Message %L2-ELO-6-INTF_SESSION_UP

[chars]: OAM session has come up

Explanation The OAM session has been fully established, and regular heartbeat messages are being sent and received.

Recommended Action None. This is an informational message.

Error Message %L2-ELO-6-INTF_THRESHOLD_BREACHED

[chars]: [chars] [chars] threshold breached - Window size: [unsigned int], Errors: [unsigned int], Threshold: [unsigned int], Total errors: [unsigned int]

Explanation A threshold has been breached in the hardware. This is an indication of a deteriorating link.

Recommended Action No specific IOS-XR action needs to be performed.

Error Message %L2-ELO-6-LOOPBACK_CANCEL

[chars]: Cancelling loopback mode as our MAC is lower than the remote MAC

Explanation An attempt has been made to start loopback mode from both peers simultaneously. As per the IEEE 802.3 OAM specification, this OAM client has cancelled the request as the local MAC address is lower than the remote MAC address.

Recommended Action Retry the Loopback operation from this peer once the remote loopback session on the remote peer has been terminated.

Error Message %L2-ELO-6-MISCONFIGURED_INTERFACE

The profile configuration from profile ’[chars]’ cannot be applied as the platform does not support all the configured values: [chars]

Explanation A profile can be configured that has configuration parameters that are not supported for all interfaces on the router. If that profile is later attached to an interface for which not all its values are supported, this message is generated. The interface will use the default values for any parameter that is out of range. The configuration parameters that may not be supported are support for remote loopback and support for link monitoring events. Further, the window size of a link monitor event must be a multiple of the interface’s statistics’ poll interval.

Recommended Action Nothing need be done if the default values are acceptable for the invalid parameters. Otherwise, modify the profile to contain only configuration that is supported for the interfaces to which it is attached, or use an alternate profile for this interface.

Error Message %L2-ELO-6-MISWIRED

[chars]: Mis-wiring detected

Explanation The Mis-Wiring Detection feature of Ethernet Link OAM has detected a mis-wiring situation. Mis-wiring occurs when the TX wire of an interface is not connected to the same remote interface as the RX wire.

Recommended Action Check the wiring of the specified interface. By setting the mis-wiring action to ’log’, and using the packet debugging facility of Ethernet Link OAM (’debug ethernet oam packets’), the MAC addresses of the source of packets can be used to identify where the links are.

Error Message %L2-ELO-6-NO_PROFILE

Profile ’[chars]’ is not configured, but has been attached to an interface

Explanation A profile has been attached to an interface. However, that profile has not yet been configured. Until the named profile is created, the interface will use the default profile configuration.

Recommended Action Create the specified profile, or remove the configuration associating the profile with the interface.

Error Message %L2-ELO-6-REMOTE_MASTER_LEFT_LOOPBACK

[chars]: Local client in Slave Loopback, and remote Master has abruptly left Loopback mode. Exiting Slave loopback locally

Explanation While running the link in OAM Loopback mode, with the local peer as the Slave, the Master peer abruptly ended Loopback mode without first informing this peer to end it. This may indicate a problem with the remote peer.

Recommended Action No corrective action is required. This peer has exited Loopback mode also, and the link is now back to normal operational status.

Error Message %L2-ELO-6-REMOTE_SLAVE_LEFT_LOOPBACK

[chars]: Remote client has abruptly left Slave loopback mode. Exiting loopback state

Explanation While running the link in OAM Loopback mode, with the local peer as the Master, the Slave peer abruptly ended Loopback mode without being told to do so by this peer. This may indicate a problem with the remote peer.

Recommended Action No corrective action is required. This peer has exited Loopback mode also, and the link is now back to normal operational status.

Error Message %L2-ELO-6-UNEXPECTED_LOOPBACK_STATE

[chars]: An unexpected multiplexer and parser state have been received from the remote peer.

Explanation While running the link in OAM Loopback mode the local peer received an unexpected multiplexer and parser state combination from the remote peer. This may indicate a problem with the remote peer.

Recommended Action No corrective action is required. This peer has exited Loopback mode also, and the link is now back to normal operational status.

Error Message %L2-ELO-6-UNEXPECTED_STATE

A variable response from the remote peer contained invalid state.

Explanation Whilst parsing a variable response packet an invalid state was found. This could be an indication of a faulty implementation on remote peer.

Recommended Action No specific IOS-XR action needs to be performed.

ELOGM Messages

Error Message %L2-ELOGM-4-DEBUG_CLEANUP_FAILED

Ethernet Link OAM Global Manager failed to cleanup debug: [chars]

Explanation Whilst exiting, the Global Manager failed to cleanup the debug module. The process will exit anyway, and no further errors should be 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-ELOGM-4-DEBUG_INIT_FAILED

Ethernet Link OAM Global Manager failed to initialize debug: [chars]

Explanation During initialization, the Global Manager failed to initialize the debug module and will now exit. It should be restarted by System Manager and resynchronize it’s internal 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-ELOGM-4-EXITING

Ethernet Link OAM Global Manager failed to process events: [chars]

Explanation The process failed to process incoming events, and will exit. It should be restarted by System Manager and resynchronize its internal 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-ELOGM-4-INIT_FAILED

Ethernet Link OAM Global Manager failed to initialize: [chars]

Explanation During initialization, an unexpected error was encountered. The process will exit and be restarted by 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.

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.

Error Message %L2-EMA-4-WARN_INVALID_RANGE

Range of available MAC addresses retrieved is invalid: [dec] MACs starting from Base MAC [hex]%2.2x.[hex]%2.2x.[hex]%2.2x

Explanation The range of available MAC addresses supplied by the platform is invalid. A zero size range will be used, resulting in any MAC address requests from client features being rejected.

Recommended Action *DDTS*

Error Message %L2-EMA-4-WARN_RANGE_RETRIEVAL

Unable to retrieve values of available MAC addresses. Error: [chars]

Explanation A repeated failure occurred when requesting the range of available MAC addresses. A zero size range will be used, resulting in any MAC address requests from client features being rejected.

Recommended Action *DDTS*

EPI Messages

Error Message %L2-EPI-3-ATTR_NOTIFY_FAILED

Failed to notify a client of a change to interface attributes - out of memory

Explanation The EPI library was unable to notify a client of a change to some interface attributes because it was unable to allocate memory. This may result in the client of the EPI library attempting to send invalid packets.

Recommended Action This message will be seen as a result of a configuration change if the system is low on memory. Attempt to free up some memory and reapply the configuration change that caused this message to be displayed. If the problem persists, try restarting the process using this library. If this does not help, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-EPI-3-INIT_FAILED

Failed to initialize, [chars] failed [unsigned int]: [chars]

Explanation An error was encountered while the EPI library was initializing. The error message contains details about the source of the error.

Recommended Action The process will exit and will be restarted. If the problem persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-EPI-3-PAK_FREE_FAILED

Failed to free packet buffer: [chars]

Explanation An error was encountered while the EPI library was attempting to free a packet buffer. The error message contains details about the source of the error.

Recommended Action This message should be harmless, but it is possible that there is an inconsistency that may lead to a memory leak. If the problem persists, try restarting the process. If this does not help, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-EPI-3-PKT_OVERFLOW

The maximum number of packets being stored for interface: CH[hex] has been exceeded

Explanation The EPI library has been asked to create a packet for an interface which already has the maximum number of supported packets in storage. EPI has created the packet, but may have difficulty updating packets on this interface in future.

Recommended Action This message is likely to indicate an internal error in the process that means it is not freeing its old packet information correctly. If the process is not restarted then a future configuration change for the interface in question may not be reflected in the generated packets. Try restarting the process and, if the problem persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

eth_gl Messages

Error Message %L2-eth_gl-4-EVENT_BLOCK

An error was received while waiting for an event: (error: [chars])

Explanation The indicated 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-eth_gl-4-INIT_FAILED

Initialization failed: [chars] (error: [chars])

Explanation The indicated process failed to initialize. Previous messages may give the reason. The process will automatically restart and retry. Until it succeeds, Ethernet functionality may be impacted.

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

Error Message %L2-ether_spa_dwdm-3-DWDM_ERROR

[chars] [dec]

Explanation SPA driver detected an error in the DWDM init routine

Recommended Action No action is required.

Error Message %L2-ether_spa_dwdm-3-MALLOC_FAILED

[chars]

Explanation The SPA driver detected a memory error on the SPA card

Recommended Action No action is required.

Error Message %L2-ether_spa_dwdm-3-PLL_NOT_LOCKED

[chars] not locked after [dec] retries [hex]

Explanation The SPA driver failed to initialize the PLL

Recommended Action No action is required.

Error Message %L2-ether_spa_dwdm-3-UT2_SPA

[chars] [dec]

Explanation The SPA driver did not detect a UT2 transponder module

Recommended Action No action is required.

ether_spa_intr Messages

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

Error Message %L2-ether_spa_mac_error-1-RECOVERY_FAILED

A Maximum MAC Error recovery retries has occurred for [dec]/[dec]/[dec]. PORT DISABLED after exceeding maximum retries. LINK force DOWN. Manual intervention required to bring port back into operation. Issue shutdown and no-shutdown on the interface to bring port into operation.

Explanation A MAC Frame Corruption occurred on the interface, concern port is in error condition after maximum recovery retries. The concern port has been permanently disabled. Manual intervention required to re-enable the port.

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

A Maximum MAC ECC Auto Error recovery retries has occurred in bay [dec]. SPA is shutting down

Explanation MAC TX/RX FIFO ECC errors have occured. Auto-recovery attempts have also failed to recover the SPA. This is indicative of a hardware issue. Manual intervention is required.

Recommended Action Try reseating the SPA, if the problem persists, replace the SPA.

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]/[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-1-CONFIGERROR

Ethernet: Invalid configuration, [chars] is not supported by this interface

Explanation Invalid configuration

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

Error Message %L2-ETHER-1-IMERROR

Ethernet: [chars]() line [dec]: interface manager call [chars] failed: [chars]

Explanation The call to im failed for some reason.

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

Error Message %L2-ETHER-2-DEVCTLFAILED

Ethernet: [chars]: devctl failed with code [hex]

Explanation A devctl call failed.

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

Error Message %L2-ETHER-2-OUTOFMEMORY

Ethernet: [chars]() line [dec]: out of memory, unable to create [chars]

Explanation Card has no more memory available.

Recommended Action Verify that the card is not out of memory. Contact your Cisco technical support representative if the problem persists.

Error Message %L2-ETHER-2-SYSDBREGISTERFAILED

Ethernet: Sysdb registration failed ([chars])

Explanation The driver failed to initialize communication with sysdb.

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

Error Message %L2-ETHER-3-BADASYNCEVENT

Ethernet: Unknown asynchronous event [dec] in [chars]

Explanation An invalid asynchronous event was received by the driver.

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

Error Message %L2-ETHER-3-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-3-DILBFAILED

Ethernet: [chars]() line [dec]: failed to [chars].

Explanation A dilb call failed, preventing communication between threads/processes.

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

Error Message %L2-ETHER-3-DPCFAILED

Ethernet: [chars]() line [dec]: DPC call to [chars] failed.

Explanation A direct procedure call failed.

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

Error Message %L2-ETHER-3-EDMERROR

Ethernet: [chars]() line [dec]: Bad sysdb call for tuple [chars]: [chars]

Explanation An edm sysdb call was improperly formed.

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

Error Message %L2-ETHER-3-INITFAILED

Ethernet: [chars]() line [dec]: init failed in function [chars]: [chars]

Explanation Basic initialization failed due to problem in a called function.

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

Error Message %L2-ETHER-3-INVALIDARGSIZE

Ethernet: Incompatible structure definition for [chars] in [chars]

Explanation A structure passed is the wrong size due most likely to compilation problem.

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

Error Message %L2-ETHER-3-INVALIDTIMER

Ethernet: [chars](): Invalid timer type [dec]

Explanation An invalid timer type was found in an expired timer.

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

Error Message %L2-ETHER-3-RESTARTFAILED

Ethernet: [chars]() line [dec]: [chars]: [dec]

Explanation Restarting the driver failed for some reason.

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

Error Message %L2-ETHER-3-TIMERINITFAILED

Ethernet: Failure initializing asynchronous timers: [chars]() - [chars]

Explanation A failure occured while creating or initializing the timers for the driver.

Recommended Action Make sure there is enough memory available. Contact your representative if the problem persists.

Error Message %L2-ETHER-3-UNSUPPORTEDSTATS

Ethernet: Unsupported stats request [dec] in [chars]

Explanation A driver has requested an unsupported stats type.

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

Error Message %L2-ETHER-4-ERR_EVM_EVENT_BLOCK

Failure during receipt of message. Error: [chars]

Explanation A failure occurred handling a message arriving at one of the Ethernet capsulation processes. Under normal circumstances the process restarts with no impact to functionality. If this error message is seen repeatedly then Ethernet services may be affected on all Ether type interfaces on the given node.

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

Error Message %L2-ETHER-4-INIT

Failure during intialisation of [chars] in a Ether basecaps process. Error: [chars]

Explanation A failure occurred during the initialisation of one of the Ethernet capsulation processes. Under normal circumstances the process restarts with no impact to functionality. If this error message is seen repeatedly then Ethernet services may be affected on all Ether type interfaces on the given node.

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

ETHERNET Messages

Error Message %L2-ETHERNET-3-INTERFACE_INITIAL

Failed to initialize interface [chars], due to error: [chars]

Explanation It was not possible to initialize the physical interface due to a driver error or a system error. The interface’s config may not have been restored and the interface will not be usable.

Recommended Action Restart the driver process that reported the error. If the error is reported again then reloading the linecard may allow it to recover, but it will impact all traffic on that node. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ETHERNET-3-MAC_ACC_STATS_REGISTRATION

Failed to register for MAC accounting stats collection, error: [chars]

Explanation It was not possible to register for statistics collection due to a error reported by the statistics infrastructure.

Recommended Action If the error is reported again then reloading the linecard may allow it to recover, but it will impact all traffic on that node. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ETHERNET-3-MIB_ERROR

Unable to fetch requested Etherlike MIB data for interface [hex]: [chars]

Explanation An error occured while trying to collect MIB data requested by the SNMP infrastructure. The data for which an error was encountered will not be presented in SNMP ’get’ request results.

Recommended Action Such errors are not expected, and probably indicate an out-of-resource condition, or an inconsistency in the system state. Wait for any likely transient root problems to subside, and attempt to repeat the operation. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ETHERNET-3-MIB_INIT_ERROR

Error initializing Etherlike MIB: [chars]

Explanation An error occured while trying to initialize the etherlikemib DLL with the SNMP infrastructure. The error may result in the inability to retrieve data from the ETHERLIKE-MIB.

Recommended Action Such errors are not expected, and probably indicate an an inconsistency in the system state or loaded IF-MIB and ETHERLIKE-MIB DLLs. Determine if there is an initialization issue with the IF-MIB as well. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ETHERNET-3-MTU_IMPOSE_FAILED

Failed to set MTU of [unsigned int] on [chars]

Explanation The specified MTU could not be applied on this interface.

Recommended Action Choose a more appropriate MTU to configure on the interface considering the MTU requirements of any L3 protocols that are configured on the interface.

Error Message %L2-ETHERNET-3-STATE_FSM

Port state FSM operation failed [chars] on [chars], due to error: [chars]

Explanation An operational error occured when handling a port state event in the port state machine, and the internal state may be left in an inconsistent state without user intervention.

Recommended Action ’shutdown’ and ’no shutdown’ the affected interface, this should allow the state machine to recover its operational state. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ETHERNET-3-TX_DISABLE

Interface [chars], link [chars]forced down due to remote signalling

Explanation L2VPN Mgr has signalled at the remote AC has changed state. Due to this the local interface has been enabled/disabled in the TX direction if supported, or enabled/disabled in both directions otherwise.

Recommended Action If the remote AC has changed state then this message is expected. If the remote AC hasn’t changed state and this condition isn’t expected then this may indicate a problem, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ETHERNET-4-BER_ALARM

interface: [chars], alarm: [chars], status: [chars]

Explanation The specified Bit Error Rate Alarm has been declared or released. interface: interface on which alarm is set/cleared alarm: alarm being asserted e.g: SF-BER or SD-BER status: set/cleared

Recommended Action If SF/SD-BER alarm is seen: Link quality degraded beyond configured threshold. Check if the peer device is injecting error frames or otherwise check if the cable is faulty.

Error Message %L2-ETHERNET-4-INITIALIZATION

Initialization of the G-Ether library failed at stage ’[chars]’, due to error: [chars]

Explanation A error occurred during the initialization of the common Ethernet driver library.

Recommended Action The driver process is restarted automatically, hence no user intervention should be required. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ETHERNET-4-INTERFACE_CREATE

Interface creation failed due to error: [chars]

Explanation It was not possible to create some or all physical ethernet interfaces due to a driver error or a system error.

Recommended Action The driver process will attempt to recover automatically, hence no user intervention should be required. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ETHERNET-6-MAC_ACC_NOT_PROGRAMMED

Interface [chars]%s[chars]%s, [chars] addresses for MAC accounting

Explanation Some MAC addresses have not been programmed for MAC accounting in the hardware. This means that MAC accounting statistics will not be collected for these MAC addresses. This is most likely due to a lack of hardware resources due to a large number of MAC addresses being programmed for MAC accounting.

Recommended Action This condition will only affect statistics collection for some MAC addresses on this interface. If the number of MAC accounting addresses programmed, which can be checked using ’show mac-accounting’, seems small and this issue is still hit this may indicate a system error, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-ETHERNET-6-MTU_NEAR_HW_LIMIT

The configured MTU of [unsigned int] on [chars] is close to the H/W limit, and hence large [chars] frames may be dropped as oversized frames

Explanation The configured MTU is close the maximum frame size allowed on the interface. Hence large 802.1Q or QinQ frames bigger than the maximum frame size supported on the interface may be dropped.

Recommended Action If 802.1Q or QinQ support is required on the interface, then it is recommended that either the configured interface MTU is reduced by 4 or 8 bytes, or the sub-interface MTU is reduced by 4 or 8 bytes to ensure that all frames are within the H/W limits.

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.

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.

FHRP_COMMS Messages

Error Message %L2-FHRP_COMMS-3-MSG_DROPPED

Unexpected error has lead to an incoming message being dropped: [chars]

Explanation An incoming control message could not be fully processed due to an unexpected error.

Recommended Action Restarting the process in question should result in a full resync of all data. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-FHRP_COMMS-3-MY_ID_MISMATCH

Checkpoint data for this connection (id %hu) has invalid id (%hu)

Explanation The Checkpoint table contained unexpected data. This is unexpected, and could indicate memory corruption of some sort.

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

Error Message %L2-FHRP_COMMS-3-MY_SAVE_FAILED

Failed to save Checkpoint sequence information for connection [chars]

Explanation The client failed to save its own sequence data to Checkpoint. If the process restarts before the save is successfully retried, remote clients may get out of sync, and data loss could occur.

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

Error Message %L2-FHRP_COMMS-3-SAVE_FAILED

Failed to save Checkpoint entry [hex]/[hex] on connection [chars]

Explanation The client failed to save data to Checkpoint. If the process restarts before the save can be retried, then data loss could occur.

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

Error Message %L2-FHRP_COMMS-4-DUPLICATE_ENTRY

Duplicate Checkpoint entry for ID %hu on node [hex]

Explanation The Checkpoint table contained a duplicate entry. This is unexpected, and likely indicates a software fault.

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

FIB_IPV4 Messages

Error Message %L2-FIB_IPV4-3-ADJ_ERROR

[chars] ifh: [hex], [chars]

Explanation A runtime error occurred in ASR9K adjiacency module. The reason for the failure is also displayed. Please call Cisco Support with the error information.

Recommended Action Please collect the console log and following traces: show cef trace loc slot number show cef platform trace [common|ipv4] all loc slot number show adjacency hardware trace loc slot number show bundle trace all loc slot number show im trace loc slot number Most of the time, these are harmless transient messages, caused by the delay in FIB and AIB processes learning about new interface. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ADJ_ERROR

[chars] ifh: [hex], [chars]

Explanation Platform IPv4 FIB, adjacency error

Recommended Action Please collect the console log and following traces: show cef trace loc show cef platform trace [common|ipv4] all loc show adjacency hardware trace loc show bundle trace all loc show im trace loc Most of the time, these are harmless transient messages, caused by the delay in FIB and AIB processes learning about new interface. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ADJ_ERROR

[chars] ifh: [hex], [chars]

Explanation A runtime failure occurred in FIB engine layer while processing/updating adjacency information. The message string indicates the reason for the This message also provides a string interpretation of the error code and the interface handle.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv4 all location show im trace location show bundle trace location show adjacency hardware trace location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ADJ_ERROR

[chars] ifh: [hex], [chars]

Explanation A runtime error occurred in ASR9K adjiacency module. The reason for the failure is also displayed. Please call Cisco Support with the error information.

Recommended Action Please collect the console log and following traces: show cef trace loc slot number show cef platform trace [common|ipv4] all loc slot number show adjacency hardware trace loc slot number show bundle trace all loc slot number show im trace loc slot number Most of the time, these are harmless transient messages, caused by the delay in FIB and AIB processes learning about new interface. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ADJ_ERROR

[chars] ifh: [hex], [chars]

Explanation A runtime failure occurred in FIB engine layer while processing/updating adjacency information. The message string indicates the reason for the This message also provides a string interpretation of the error code and the interface handle.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv4 all location show im trace location show bundle trace location show adjacency hardware trace location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERR_INFO

[chars] [dec]

Explanation A runtime error occurred in ASR9K IPv4 FIB module. The reason for the failure is also displayed. Please call Cisco Support with the error information.

Recommended Action Please collect the console log, FIB traces (show cef trace loc slot number), FIB platform trace (show cef platform trace [common|ipv4] all loc slot number). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERR_INFO

[chars] [unsigned int]

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv4 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERR_INFO

[chars] [dec]

Explanation A runtime error occurred in ASR9K IPv4 FIB module. The reason for the failure is also displayed. Please call Cisco Support with the error information.

Recommended Action Please collect the console log, FIB traces (show cef trace loc slot number), FIB platform trace (show cef platform trace [common|ipv4] all loc slot number). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERR_INFO

[chars] [dec]

Explanation Platform IPv4 FIB, error information

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|ipv4] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERR_INFO

[chars] [unsigned int]

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv4 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERR_STR

[chars], [chars] ([unsigned int])

Explanation A runtime error occurred in ASR9K IPv4 FIB module. The reason for the failure is also displayed. Please call Cisco Support with the error information.

Recommended Action Please collect the console log, FIB traces (show cef trace loc slot number), FIB platform trace (show cef platform trace [common|ipv4] all loc slot number). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERR_STR

[chars], [chars] ([unsigned int])

Explanation Platform IPv4 FIB, error information

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|ipv4] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERR_STR

[chars], [chars] ([unsigned int])

Explanation A runtime error occurred in ASR9K IPv4 FIB module. The reason for the failure is also displayed. Please call Cisco Support with the error information.

Recommended Action Please collect the console log, FIB traces (show cef trace loc slot number), FIB platform trace (show cef platform trace [common|ipv4] all loc slot number). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERR_STR

[chars], [chars] ([unsigned int])

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv4 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERR_STR

[chars], [chars] ([unsigned int])

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv4 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERROR

[chars]

Explanation A runtime error occurred in ASR9K IPv4 FIB module. The reason for the failure is also displayed. Please call Cisco Support with the error information.

Recommended Action Please collect the console log, FIB traces (show cef trace loc slot number), FIB platform trace (show cef platform trace [common|ipv4] all loc slot number). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERROR

[chars]

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card whee the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv4 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERROR

[chars]

Explanation A runtime error occurred in ASR9K IPv4 FIB module. The reason for the failure is also displayed. Please call Cisco Support with the error information.

Recommended Action Please collect the console log, FIB traces (show cef trace loc slot number), FIB platform trace (show cef platform trace [common|ipv4] all loc slot number). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERROR

[chars]

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card whee the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv4 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV4-3-ERROR

[chars]

Explanation Platform IPv4 FIB, error

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|ipv4] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV4-3-GEN_ERR

FIB IPV4 internal error: [chars]

Explanation An internal software error occurred

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

Error Message %L2-FIB_IPV4-5-RECURSIVE_LOOP

FIB IPv4 Recursive loop: [chars]

Explanation Recursive loop was detected. The route update will be dropped

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

Error Message %L2-FIB_IPV4-6-INFO

[chars]

Explanation This is an information message in the ASR9K platform FIB specific code software. The message is for debug purposes only and not an error.

Recommended Action The message is just for information. No action is needed.

Error Message %L2-FIB_IPV4-6-INFO

[chars]

Explanation This is an information message in the ASR9K platform FIB specific code software. The message is for debug purposes only and not an error.

Recommended Action The message is just for information. No action is needed.

FIB_IPV6 Messages

Error Message %L2-FIB_IPV6-3-ADJ_ERROR

[chars] ifh: [hex], [chars]

Explanation Platform IPv6 FIB, adjacency error

Recommended Action Please collect the console log and following traces: show cef trace loc show cef platform trace [common|ipv6] all loc show adjacency hardware trace loc show bundle trace all loc show im trace loc Most of the time, these are harmless transient messages, caused by the delay in FIB and AIB processes learning about new interface. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ADJ_ERROR

[chars] ifh: [hex], [chars]

Explanation Platform IPv6 FIB, adjacency error

Recommended Action Please collect the console log and following traces: show cef trace loc show cef platform trace [common|ipv6] all loc show adjacency hardware trace loc show bundle trace all loc show im trace loc Most of the time, these are harmless transient messages, caused by the delay in FIB and AIB processes learning about new interface. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERR_INFO

[chars] [dec]

Explanation Platform IPv6 FIB, error information

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|ipv6] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERR_INFO

[chars] [unsigned int]

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv6 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERR_INFO

[chars] [dec]

Explanation Platform IPv6 FIB, error information

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|ipv6] all loc). Also notice if the error message is transient or persistent. If errros persist, report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERR_INFO

[chars] [dec]

Explanation Platform IPv6 FIB, error information

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|ipv6] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERR_INFO

[chars] [unsigned int]

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv6 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERR_INFO_VERBOSE

[chars] [chars] [chars] [dec]

Explanation Platform IPv6 FIB, error information

Recommended Action *SUPPORT*

Error Message %L2-FIB_IPV6-3-ERR_INFO_VERBOSE

[chars] [chars] [chars] [dec]

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code. It provides more verbose information. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv6 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERR_INFO_VERBOSE

[chars] [chars] [chars] [dec]

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code. It provides more verbose information. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv6 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERR_STR

[chars], [chars] ([unsigned int])

Explanation Platform IPv6 FIB, error information

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|ipv6] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERR_STR

[chars], [chars] ([unsigned int])

Explanation Platform IPv6 FIB, error information

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|ipv6] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERR_STR

[chars], [chars] ([unsigned int])

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv6 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERR_STR

[chars], [chars] ([unsigned int])

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv6 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERROR

[chars]

Explanation Platform IPv6 FIB, error

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|ipv6] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERROR

[chars]

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv6 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERROR

[chars]

Explanation Platform IPv6 FIB, error

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|ipv6] all loc). Also notice if the error message is transient or persistent. If errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERROR

[chars]

Explanation Platform IPv6 FIB, error

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|ipv6] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_IPV6-3-ERROR

[chars]

Explanation A runtime failure occurred in FIB engine layer. Typically, this is an internal error. The message string indicates the reason for the failure. Here is a list of possible reasons for this message (not all-inclusive). - Failed to retrieve information from FIB objects. This condition indicates a problem with the software on the card where the error is seen. - Failed to initialize objects. This condition indicates a problem with the software on the card. Typically, this occurs when the software tries to initialize invalid objects. - Unexpected events. This condition indicates a problem where an event is triggered in the software unexpectedly on the card. - Invalid objects. This condition indicates a problem where the object being processed by the software is invalid.

Recommended Action Please collect the console log and the CLI output. CLI RP show cef /RP LC show cef location show cef trace location show cef platform trace common all location show cef platform trace ipv6 all location /LC TECH show tech cef show version show install summary /TECH /CLI Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message %L2-FIB_IPV6-3-GEN_ERR

FIB IPV6 internal error: [chars]

Explanation An internal software error occurred

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

Error Message %L2-FIB_IPV6-5-RECURSIVE_LOOP

FIB IPv6 Recursive loop: [chars]

Explanation Recursive loop was detected. The route update will be dropped

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

Error Message %L2-FIB_IPV6-6-INFO

[chars]

Explanation PLATFORM IPv6 FIB, Information

Recommended Action The message is just for information. No action is needed.

Error Message %L2-FIB_IPV6-6-INFO

[chars]

Explanation PLATFORM IPv6 FIB, Information

Recommended Action The message is just for information. No action is needed.

FIB_MPLS Messages

Error Message %L2-FIB_MPLS-3-ERR_INFO

[chars] [dec]

Explanation Platform MPLS FIB, error information

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|mpls] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_MPLS-3-ERR_INFO

[chars] [dec]

Explanation Platform MPLS FIB, error information

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|mpls] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_MPLS-3-ERR_STR

[chars], [chars] ([unsigned int])

Explanation Platform MPLS FIB, error information

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|mpls] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_MPLS-3-ERR_STR

[chars], [chars] ([unsigned int])

Explanation Platform MPLS FIB, error information

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|mpls] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_MPLS-3-ERROR

[chars]

Explanation Platform MPLS FIB, error

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|mpls] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message %L2-FIB_MPLS-3-ERROR

[chars]

Explanation Platform MPLS FIB, error

Recommended Action Please collect the console log, FIB traces (show cef trace loc), FIB platform trace (show cef platform trace [common|mpls] all loc). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

FR_EDM Messages

Error Message %L2-FR_EDM-2-INIT

[chars] : [chars]

Explanation Init error.

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

Error Message %L2-FR_EDM-3-NO_STATS

unable to get stats for vc [hex], [dec]

Explanation The statistics manager returned null data for vc

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

Error Message %L2-FR_EDM-3-NOMEM

unable to allocate [dec] bytes of memory

Explanation The system is low on memory and not enough was available to complete the request

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

FR_INARP Messages

Error Message %L2-FR_INARP-2-CONNECT_IM

failure on IM connection: [chars]

Explanation This error indicates a problem with InARP/IM interaction.

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

Error Message %L2-FR_INARP-2-INIT

failed to initialize: [chars]

Explanation During process start up an unrecoverable error occurred. The component will exit and should be restarted by the System Manager.

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

Error Message %L2-FR_INARP-3-IF_VC_CLASS

unable to apply class [chars] to interface [chars]: [chars]

Explanation A vc-class was configured on an interface but couldn’t be applied for the given reason

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

Error Message %L2-FR_INARP-3-INVALID_FD

received an event on unknown fd [dec]

Explanation An event was received with an unknown fd

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

Error Message %L2-FR_INARP-3-NOMEM

unable to allocate [dec] bytes of memory

Explanation The system is low on memory and not enough was available to complete the request

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

Error Message %L2-FR_INARP-3-PVC_VC_CLASS

unable to apply class [chars] to interface [chars].[dec]: [chars]

Explanation A vc-class was configured on an interface but couldn’t be applied

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

Error Message %L2-FR_INARP-3-SOCKET_SEND

could not send on socket: [chars]

Explanation Socket returned an error, not EAGAIN or EINTR

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

Error Message %L2-FR_INARP-3-UNKNOWN_EVENT

received an unknown event [hex]

Explanation An unknown event was received

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

Error Message %L2-FR_INARP-3-UNKNOWN_IDB

received information about an unrecognised interface

Explanation A set of IDBs are kept with information on each InARP interface. Somehow this information has become inconsistent with the system.

Recommended Action Restart the main process (containing the InARP DLL) If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-FR_INARP-4-UNKNOWN_INTFTYPE

received an event for an unknown interface type: [dec]

Explanation The system sent a messages which wasn’t expected. It will be ignored.

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

Error Message %L2-FR_INARP-4-UNKNOWN_MSG

received an unknown message: [dec]

Explanation An unknown InARP message was received - it will be ignored

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

FR_LMI Messages

Error Message %L2-FR_LMI-2-INIT

LMI failed to initialize: [chars]

Explanation During process start up an unrecoverable error occurred. The component will exit and should be restarted by the System Manager.

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

Error Message %L2-FR_LMI-3-CODEP_ERROR

Configured values of [chars] and [chars] conflict during application. Changing [chars] to [dec] to maintain consistency

Explanation LMI parameters N392 and N393 are co-dependent - they must obey the rule N392 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_NETIO Messages

Error Message %L2-FR_NETIO-3-MEMORY

Failed to allocate [unsigned int] bytes

Explanation The DLL has failed to acquire the required amount of memory.

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

Error Message %L2-FR_NETIO-6-DEBUG_REG

Debug registration failed: [chars]

Explanation Debug message registration failed

Recommended Action No action is required.

FR_SFRAR Messages

Error Message %L2-FR_SFRAR-2-INIT

SFRAR failed to initialize: [chars]

Explanation During process start up an unrecoverable error occurred. The component will exit and should be restarted by the System Manager.

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

Error Message %L2-FR_SFRAR-3-SYSMGR

SFRAR process ready call failed: [chars]

Explanation The call to inform the System Manager that SFRAR is running failed.

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

FR_SOCKET Messages

Error Message %L2-FR_SOCKET-2-INIT

Socket failed to initialize: [chars]

Explanation During process start up an unrecoverable error occurred. The component will exit and should be restarted by the System Manager.

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

Error Message %L2-FR_SOCKET-3-CONN

Failed to setup fr socket EVM connection: [chars]

Explanation The fr_socket process failed to connect to the event manager.

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

Error Message %L2-FR_SOCKET-3-DPC_FAIL

Failed to register [chars] protocol in netio

Explanation The fr_socket process failed to send dpc message to Netio

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

Error Message %L2-FR_SOCKET-3-NETIO_OUTPUT_FAIL

Failed to send packet out to Netio: [chars]

Explanation The fr_socket process failed to send packet out to Netio.

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

Error Message %L2-FR_SOCKET-3-NOMEM

unable to allocate [dec] bytes of memory

Explanation The system is low on memory and not enough was available to complete the request

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

Error Message %L2-FR_SOCKET-3-PACKET_CONN

Failure in packet manager connection: [chars]

Explanation The fr_socket process failed to connect to packet manager

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

Error Message %L2-FR_SOCKET-3-RESMGR_ATTACH

Failed to setup fr socket as a resource manager: [chars]

Explanation The fr_socket process failed to advertise itself to the system as a resource manager.

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

Error Message %L2-FR_SOCKET-3-SEND_ASYNC

Failed to send async pulse [dec]: [chars]

Explanation The fr_socket process failed to send async pulse to FR socket EVM

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

Error Message %L2-FR_SOCKET-3-SYSMGR

SysMgr process ready call failed: [chars]

Explanation The call to inform the System Manager that the FR socket is running failed.

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

FR_UV Messages

Error Message %L2-FR_UV-3-ERR_ABORT_ENCAP_FAIL

[dec] encap aborts failed: The system may now be in an inconsistant state.

Explanation The FR Uberverifier has detected a misconfiguration. It was not able to cleanup its internal DB while handling encap abort creates.

Recommended Action The misconfiguration can be corrected by restarting fr_uv process on the specific location on which this error message is seen. 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-FR_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 FR 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-FR_UV-3-EVENT

Unrecoverable error in event loop. Error: [chars]

Explanation An error (other than EINTR) occured in the event loop. The process must exit.

Recommended Action Identify the location of the card where there error was reported. Copy the error message exactly as it appears on the console or in the system log. Issue the show memory location 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-FR_UV-3-INIT

Failure during intialization of [chars]. Error: [chars]

Explanation A failure occurred during the initialization of the process. This resulted in the restart of the process.

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

Error Message %L2-FR_UV-3-SYSMGR

Failure communicating readiness to System Manager. Error: [chars]

Explanation The process was initialized successfully but was unable to inform System Manager of the success.

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

FR_VCM_EA Messages

Error Message %L2-FR_VCM_EA-2-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.

FRMIB Messages

Error Message %L2-FRMIB-3-SYSDB

FR MIB: [chars]: [chars]: [chars]

Explanation This message indicates the FR MIB library fails to perform a SYSDB operation. *DDTS*

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

FSYNC Messages

Error Message %L2-FSYNC-3-COMMS_ERROR

Communications error for node [chars]: [chars]%s

Explanation A error occurred in the communication between Frequency Synchronization processes. Frequency Synchronization information may be out of sync.

Recommended Action Restarting fsyncmgr on the card on which this message was seen may fix the problem. If the message continues to be seen, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-FSYNC-3-ESMC_SEND_TIMER

Failed to re-arm the ESMC SSM send timer: [chars]

Explanation An error occurred when attempting to re-arm the ESMC SSM send timer. No further SSMs will be sent from interfaces on the card on which this message was seen.

Recommended Action Restarting fsyncmgr on the card on which this message was seen may fix the problem. If the message continues to be seen, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-FSYNC-4-COMMS_RETRY_FAILED

Communications retry failed: [chars]%s

Explanation A Frequency Synchronization process has failed to send a message and attempts to retry the send have also failed.

Recommended Action The process will exit and will be restarted. If the problem persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-FSYNC-4-ESMC_RECEIVE_TIMER

Failed to re-arm the ESMC SSM receive timer for [chars]: [chars]

Explanation An error occurred when attempting to re-arm the ESMC SSM receive timer for the specified interface. Any SSMs received on the interface will continue to be handled, but any future peer timeouts (i.e. loss of SSMs) on the interface will go undetected.

Recommended Action Restarting fsyncmgr on the card on which this message was seen may fix the problem. If the message continues to be seen, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-FSYNC-4-INIT_FAILED

Failed to initialize: [chars]%s

Explanation An error was encountered while the specified process was initializing. The error message contains details about the source of the error.

Recommended Action The process will exit and will be restarted. If the problem persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-FSYNC-4-INPUT_PROGRAMMING_FAILED

Failed to program the inputs for selection point [chars]: [chars]

Explanation The Frequency Synchronization manager that generated the message failed to program the inputs for the specified selection point into the platform. Any changes to the inputs (for example, if an input is no longer available or if it’s QL has changed) will not take effect.

Recommended Action If the error message indicates an out-of-resource condition, then resolve the underlying resource issue, and restart the Frequency Synchronization manager on the affected node using the following command: process restart fsyncmgr location node 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-FSYNC-4-INTF_IM_ERROR

Interface manager failed to [chars] for [chars]: [chars]

Explanation *SUPPORT*

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

Error Message %L2-FSYNC-4-INTF_STATUS_ERROR

Failed to handle interface status change for [chars]: [chars]

Explanation *SUPPORT*

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

Error Message %L2-FSYNC-4-LOST_EVENT

[chars] lost event: [chars]

Explanation The specified process failed to receive an event that was sent to it.

Recommended Action If any problems are seen, they may nbe rectified by restarting the process using the ’process restart’ command.

Error Message %L2-FSYNC-4-QLT_TIMER

Failed to [chars] the [chars] timer for [chars]: [chars]

Explanation *SUPPORT*

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

Error Message %L2-FSYNC-4-SELECTION_ERROR

Failed to handle selection update for selection point [chars]: [chars]

Explanation The Frequency Synchronization manager that generated the message encountered an error during handling of an update to the inputs selected at the specified selection point. The message contains more details of the error. The change to which inputs are selected, or to the QL or priority of the selected input, may not take effect.

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

Error Message %L2-FSYNC-4-SHUTDOWN_CHECK_FAILED

Could not determine whether to exit: [chars]

Explanation A Frequency Synchronization process could not determine whether all Frequency Synchronization configuration has been removed and so cannot exit safetly. Frequency Synchronization processes may be running despite no Frequency Synchronization configuration existing.

Recommended Action No action is required. If the message continues to be seen, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-FSYNC-4-SIGNAL_UPDATE_FAILED

Failed to create object representing signal from [chars] to local Selection Point [chars]: [chars]

Explanation The Frequency Synchronization manager that generated the message failed to update its database, either in response to a message received from a remote Frequency Synchronization manager on another node, or after a change to the selected inputs in another selection point on this node. This is most likely due to an out-of-resource condition. The corresponding frequency signal will not be used.

Recommended Action Resolve the underlying resource issue, then restart the Frequency Synchronization manager on the affected node using the following command: process restart fsyncmgr location node

Error Message %L2-FSYNC-4-TIMER_FAILED

Failed to process a timer event: [chars]

Explanation A Frequency Synchronization process has failed to process a timer event.

Recommended Action The process will exit and will be restarted. If the problem persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-FSYNC-6-SELECTION_CHANGE

New selection for selection point [chars]: [unsigned int] inputs selected[chars]

Explanation A new set of inputs has been selected at the specified selection point, to drive the output of the selection point.

Recommended Action This message is for information only, no further action is required.

Error Message %L2-FSYNC-6-SELECTION_FALLBACK

Selection point [chars] is no longer externally synchronized: [chars]

Explanation There is no longer a line or external source available for the specified selection point, so it has fallen back to the internal oscillator if available, or otherwise disabled the outputs.

Recommended Action This message is for information only, no further 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_ADJ_NULL

Adjacency HW pointer is NULL for path [dec] fwd_type [dec]

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. path %d - indicates the path index fwd_type %d - the forward type

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %L2-FWD_EDGE_COMMON-3-EDGE_IP_ERR

fib ip engine layer internal error [chars] : [chars]

Explanation A runtime failure occurred in fib ip engine layer resulting in a failure to provide some system service as indicated in the message text. This is most likely an internal error. %s - indicates the reason for the failure. %s - is the decoded error reason.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

G709 Messages

Error Message %L2-G709-4-ALARM

[chars] : [chars] [chars]

Explanation The specified G709 Alarm has been declared or released.

Recommended Action Recommended action is to repair the source of the alarm.

Error Message %L2-G709-4-ERROR

[chars] Failed - Reason [chars]

Explanation The dwdm encountered an error that would lead to degraded service.

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

Error Message %L2-G709-4-log_overflow

On Port [dec], read Index [dec] write Index [dec]

Explanation The logging buffers have overflowed, and reached a point were there is no buffers available.

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

Error Message %L2-G709-6-INFO

[chars] [chars]

Explanation This is an informational message in the G709 PI component to indicate an operation.

Recommended Action No action is required.

Error Message %L2-G709-7-DEBUG_MSG

Debug: [chars]: [chars] value [dec]

Explanation This is an debug message in the G709 PI component to indicate an operation.

Recommended Action No action is required.

G8032 Messages

Error Message %L2-G8032-3-APS_CHANNEL_INACTIVE

No longer receiving R-APS messages for ethernet ring [chars] instance [dec]

Explanation A ring node has not received R-APS messages on the APS channel for an extended period of time. A properly functioning ring will have an R-APS message transmitted nominally every 5 seconds. This indicates that the requesting (transmitting) remote node on the ring, such as the RPL owner, has gone down or there is a network connectivity problem with the APS channel.

Recommended Action Confirm the remote node is transmitting R-APS messages and that there is network connectivity on the APS channel between the remote node and this node.

Error Message %L2-G8032-3-PORT_STATE_ACK_TIMEOUT

Port state updates may have failed for ring [chars] instance [dec]

Explanation Updates to the port states have errored for the indicated ring instance. Any further state updates on these ports cannot be sent until the error is cleared, potentially blocking important updates. It is also possible that the current state has not been correctly implemented.

Recommended Action Restarting the l2vpn_mgr and erp_ctrl process should resolve any network disruption due to the issue, but support should be contacted so the issue can be investigated.

Error Message %L2-G8032-4-EXIT_FAILED

Failed to notify SysMgr that [chars] is exiting: [chars]

Explanation The specified process failed to notify the system manager that it was exiting. In very rare cases, this could result in the process not being restarted when it ought to be.

Recommended Action If the process in not running and it ought to be (ie, there is G.8032 configuration remaining), then remove all G.8032 configuration, commit this change, then re-apply the configuration.

Error Message %L2-G8032-4-FOP_PM_LOWER_LEVEL

Node received an R-APS message with Node Id [chars], level [dec] which is lower than configured level [dec] for Ethernet ring [chars] instance [dec]

Explanation A ring node detects an R-APS message with a lower level than the configured G.8032 instance level for that APS Channel. This is a Failure of Protocol - Provisioning Mismatch - Level due to a misconfiguration of the APS level of nodes in the ring.

Recommended Action Identify the other node with Node Id and reconfigure it with a matching APS level.

Error Message %L2-G8032-4-FOP_PM_MULTIPLE_RPL_OWNER

RPL Owner node received an R-APS(NR,RB) message from another RPL Owner with Node Id [chars] for Ethernet ring [chars] instance [dec]

Explanation RPL Owner node detects a No Request R-APS message with the RPL Blocked status flag set, and the Node Id differs from its own. This is a Failure of Protocol - Provision Mismatch due to a misconfiguration where there are multiple RPL Owner nodes configured in the ring.

Recommended Action Identify the other RPL Owner node with Node Id and reconfigure it to be a non-RPL Owner node.

Error Message %L2-G8032-4-INIT_FAILED

Failed to initialize [chars]: [chars], [chars]

Explanation An error was encountered while the specified process was initializing. The error message contains details about the source of the error.

Recommended Action The process will exit and will be restarted. If the problem persists, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-G8032-4-INVALID_TCN_CONFIG

Invalid TCN propagation configured [chars]-[chars], ring [chars] is not a valid [chars] of TCN

Explanation The configuration specifies a topology change notification (TCN) propagation which is not valid, and consequently, the system will ignore this propagation path. A ring configured as a source of TCN propagation must not have port1 configured as a regular protected interface (i.e. port1 must be None or virtual channel). A ring referenced as a destination of TCN propagation must have port1 configured as a regular protected interface (i.e. port1 must not be None nor virtual channel)

Recommended Action Correct the configuration to adhere with the consistency checks between TCN propagation and port1.

Error Message %L2-G8032-6-CLEAR_REMINDER

Non-revertive ethernet ring [chars] instance [dec] is ready to be cleared by user

Explanation Faults have disappeared from a non-revertive ethernet ring instance, so now it is ready to be cleared by the user. A non-revertive ring instance by definition requires user action because it does not revert automatically. The act of clearing the ring will cause the location of the block to move to the RPL link and the state to transition to Idle.

Recommended Action Once ready to move the block to the RPL link, the ring instance can be cleared with the ethernet ring g8032 clear command.

Error Message %L2-G8032-6-STATE_CHANGED

Ethernet ring [chars] instance [dec] changed state to [chars]

Explanation Informational message to notify the state transitions for a ring instance.

Recommended Action None. This is informational message to indicate an event may have triggered some ring protection action.

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

Error Message %L2-GSR_aib-3-RES_ERROR

Error: [chars]: Err equals [chars]

Explanation A error occurred in GSR aib Driver resulting in a failure to provide some system service as indicated in the message text. This is most likely any internal error. %s - reason for the failure. %s - dll causing the error.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %L2-GSR_aib-6-INFO_MSG

Info: [chars]

Explanation This is a Informational message in the GSR aib driver to indicate an operation.

Recommended Action No action is required.

GSR_edge_fwd_lib Messages

Error Message %L2-GSR_edge_fwd_lib-3-RES_ERROR

[chars]: Err equals [chars]

Explanation An error occurred in Edge fowarding lib resulting in a failure to provide some system service as indicated in the message text. %s - indicates the reason for the failure. %s - is the decoded error reason. This error indicates there is problem in LC Forwarding resources

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

GSR Messages

Error Message %L2-GSR-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 may not boot up successfully and will not be able to participate in data forwarding.

Recommended Action Reload the LC using ’hw-module’ command. If problem persists, 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.

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-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 Collect output of following commands. show version show install active show dll show memory summary The exact error message seen show tech-support shelf-management show logging LC can not operate if this error persists. Try the following recovery attempts. 1. Reload the card using ’hw-module’ command. 2. Physically OIR the card out and insert back. 3. Upgrade firmwares and retry loading the card. Call your Cisco technical support representative and provide the following information if the problem persists.

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.You need not take any action.

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 a debugging information collection has faced a problem.

Recommended Action If the card is currently not used in service, reload using ’hw-module’ command can clear the error condition. If the card is already in service this message may be ignored.

Error Message %L2-GSR-6-PCDS_STATS_TIMESTAMP_FAILURE

pcds_get_timestamp failed for fishstick stats

Explanation This is a message indicating FIA PCDS a debugging information collection has faced a problem in getting the time stamp to be associated with the statistics collected.

Recommended Action If the card is currently not used in service, reload using ’hw-module’ command can clear the error condition. If the card is already in service this message may be ignored.

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.

GT64115 Messages

Error Message %L2-GT64115-2-PCI_CONFIG

Fatal error: [chars]: [dec]

Explanation A fatal error occurred during GT64115 PCI Driver cofiguration %s - error message %d - data

Recommended Action If the message recurs, copy the error message exactly as it appears on 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 %s - PCI init 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-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. %s - Info message %d - Interrupt %d - Interrupt mask

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

Error Message %L2-HALE_MQS-3-ERR_MEM_ALLOC

[chars], [chars]

Explanation This message indicates a failure in allocating memory for MQS extension. The causes for this error could be lack of memory or a hardware resource.

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. If the message recurs, copy the error message exactly as 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.

Error Message %L2-HALE_QOS-3-ERR_MEM_ALLOC

[chars], [chars]

Explanation This message indicates a failure in allocating memory for QOS extension. The causes for this error could be lack of memory or a hardware resource limitation.

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. If the message recurs, copy the error message exactly as 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_REPLICORD Messages

Error Message %L2-HALE_REPLICORD-3-ERR_MEM_ALLOC

[chars], [chars]

Explanation This message indicates a failure in allocating memory for replicorder extension. The causes for this error could be lack of memory or a hardware resource limitation.

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. If the message recurs, copy the error message exactly as 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-ERR_MEM_ALLOC

[chars], [chars]

Explanation This message indicates a failure in allocating memory for TCAM extension. The causes for this error could be lack of memory or a hardware resource limitation.

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. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

HALE_TLU Messages

Error Message %L2-HALE_TLU-3-ERR_MEM_ALLOC

[chars], [chars]

Explanation This message indicates a failure in allocating memory for TLU extension. The causes for this error could be lack of memory or a hardware resource limitation.

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. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

HFA_COMMON Messages

Error Message %L2-HFA_COMMON-3-FATAL_ERR

Fatal error: [chars]: Err 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

HFA BLWM message failure

Explanation Software exception. Quite probably a SW bug.

Recommended Action Please collect the logs mentioned in the required_info and contact support team.

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.Will not be able to send any BLWM mesages from HFA.

Recommended Action Please collect the logs mentioned in the required_info and contact support team.

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. Will not be able to send any BLWM mesages from HFA.

Recommended Action Please collect the logs mentioned in the required_info and contact support team.

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 Please collect the logs mentioned in the required_info and contact support team.

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 BLWM might be processed completely but the return code in the reply message indicates failure. The application should install its own handler to handle the replies to batched requests.

Recommended Action If the message recurs, copy the error message exactly as it appears on 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 Please collect the logs mentioned in the required_info and contact support team.

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 If the message recurs, copy the error message exactly as it appears on 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-ERR_LOCK

[chars] error on [chars], rc equals [dec]

Explanation An error occurred when un/locking HFA HW. Some of the Harware programming may be inconsistent.

Recommended Action If the message recurs, copy the error message exactly as it appears on 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 Debug message only. 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.

IGMPSN_POLICY Messages

Error Message %L2-IGMPSN_POLICY-3-ORA_INSTBUILD

Failed to build [chars]: [chars] ([chars])

Explanation Internal error in the routing policy library.

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

Error Message %L2-IGMPSN_POLICY-3-ORA_ORABUILD

Failed to build ORA[chars]: [chars] ([chars])

Explanation There was an internal error in the routing policy library.

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

Error Message %L2-IGMPSN_POLICY-3-ORA_RUN

Could not apply policy operation [chars] to attribute [chars] because [chars]

Explanation Internal error in the routing policy 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.

IGMPSN Messages

Error Message %L2-IGMPSN-3-DP_CONGESTION

Layer 2 multicast data plane programming congestion

Explanation Applications are providing state change to the layer 2 multicast data plane hardware faster than the hardware can be programmed. Internal message to the hardware have been dropped such that IGMP snooping state is now out of sync with the hardware. The user must slow the rate of IGMP state change being received by the system. The system will automatically recover from this condition once the rate of IGMP state change has been reduced.

Recommended Action The user must slow the rate of IGMP state change being received by the system. The system will automatically recover from this condition once the rate of IGMP state change has been reduced.

Error Message %L2-IGMPSN-3-ERR_INIT

Initialization failed: [chars], [chars]

Explanation An error occurred during initialization.

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

Error Message %L2-IGMPSN-3-INIT

Initialization failed: [chars]

Explanation An error occurred during initialization.

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

Error Message %L2-IGMPSN-3-NET_ERR

[chars] : [chars]

Explanation Internal 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-IGMPSN-3-SOCK_ERR

[chars] : [chars]

Explanation Internal 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-IGMPSN-3-SYSDBINIT

Error initializing the system database: [chars]

Explanation An error occurred when initializing the system database.

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

Error Message %L2-IGMPSN-5-DP_CONGESTION_CLEAR

Layer 2 multicast data plane programming congestion cleared

Explanation The layer 2 multicast data plane hardware programming has been resynced with the state in the IGMP snooping application.

Recommended Action The system is attempting to recover from a layer 2 multicast data plane programming congestion condition. No user action is required.

IMA Messages

Error Message %L2-IMA-3-INCORRECT_BW_UPDATE

IMA Group [chars] with bandwidth [dec]. Link ifh [hex] with bandwidth [dec]

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

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

Error Message %L2-IMA-3-LINK_GROUP_FAILURE

Failed to add/remove member link [chars] into ima group [chars]

Explanation The link addition/removal from a IMA Group has failed due to a software error.

Recommended Action No action is required.

Error Message %L2-IMA-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-IMA-4-ALARM

[chars]: [chars] [chars]

Explanation The specified IMA Alarm has been declared or released.

Recommended Action Recommended action is to repair the source of the alarm.

IMACTRLR Messages

Error Message %L2-IMACTRLR-2-NOMEM

[chars]([dec]): not enough memory for [chars]

Explanation The process is out of memory.

Recommended Action Check process list for source of memory loss. Check if h/w memory requirements are met.

Error Message %L2-IMACTRLR-3-ERROR

[chars]([dec]): [chars] failed ([chars]) - [chars]

Explanation A general failure occured while executing the function in question. The message contains info about the location and cause of the failure and possibly anticipated actions/effects.

Recommended Action Verify continued correct operation of IMACTRLR.

Error Message %L2-IMACTRLR-4-ALARM

[chars]: [chars] [chars]

Explanation The specified IMACTRLR Alarm has been declared or released.

Recommended Action Recommended action is to repair the source of the alarm.

Error Message %L2-IMACTRLR-4-UPDOWN

[chars]: [chars] [chars]

Explanation The specified IMACTRLR is operationally down due to alarm. Check alarm status using show controller Mlt command on the cli.

Recommended Action Recommended action is to repair the source of the alarm.

Error Message %L2-IMACTRLR-4-WARNING

[chars]([dec]): [chars] - [chars]

Explanation A non-fatal error occured while executing the function in question. The message contains info about the location and cause of the failure and possibly anticipated actions/effects.

Recommended Action Verify continued correct operation of IMACTRLR.

IOB Messages

Error Message %L2-IOB-3-INTR

IOB Intr: [chars]

Explanation The IOB FPGA has been interrupted due to an access fault %s - 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-IOB-5-UNKNOWN_INTR

Unknown IOB Intr: [chars]: [dec]: [dec]

Explanation This is a message in the IOB FPGA driver to indicate that it has detected an unknown interruption %s - description %d - level %d - mask

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

IXP2800_FWD Messages

Error Message %L2-IXP2800_FWD-3-IPCP_FAILURE

Function [chars] failure errno [chars]

Explanation IPCP communication failure.

Recommended Action None

Error Message %L2-IXP2800_FWD-3-NONFATAL_ERROR

Nonfatal error: [chars] error code [dec]

Explanation This is a error message of the IXP2800 forwarding driver to indicate either anomalies which are not fatal. Some of the messages may indicate a failure to allocate resources needed by applications.

Recommended Action None

Error Message %L2-IXP2800_FWD-7-LOG_FILE_ERROR

Test DLL failed to open log file [chars] ([chars])

Explanation The NPU test DLL failed to open the log file

Recommended Action None

Error Message %L2-IXP2800_FWD-7-UNEXPECTED_FUNC_INVOC

Function [chars] invoked

Explanation An unexpected function invocation occured

Recommended Action None

IXP2800_HW Messages

Error Message %L2-IXP2800_HW-2-NOMEM

ixp2800 HW driver Could not allocate memory

Explanation ’ixp2800 HW driver has failed to aquire the required amount of memory.’

Recommended Action *REDUCE*

Error Message %L2-IXP2800_HW-3-FATAL_ERROR

[chars]()[[dec]]: [chars]: [chars] ([dec])

Explanation A fatal error occurred in IXP2800_HW Driver which involves exiting the process.

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

Error Message %L2-IXP2800_HW-4-WARNING

[chars]()[[dec]]: [chars]: [chars] ([dec])

Explanation A warning condition occurred in IXP2800_HW Driver which involves exiting the process.

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

Error Message %L2-IXP2800_HW-6-INFO

[chars]

Explanation SERVICE card ixp2800_hw driver informational message

Recommended Action NONE : Informational message only

Error Message %L2-IXP2800_HW-7-LOG_FILE_ERROR

ixp2800 HW driver DLL failed to open log file [chars] ([chars])

Explanation The NPU HW driver DLL failed to open the log file

Recommended Action None

IXP2800_SERVICE Messages

Error Message %L2-IXP2800_SERVICE-2-NOMEM

ixp2800 service Could not allocate memory

Explanation ’ixp2800 service has failed to aquire the required amount of memory.’

Recommended Action *REDUCE*

Error Message %L2-IXP2800_SERVICE-3-FATAL_ERROR

[chars]()[[dec]]: [chars]: [chars] ([dec])

Explanation A fatal error occurred in IXP2800_SERVICE Driver which involves exiting the process.

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

Error Message %L2-IXP2800_SERVICE-3-HOST_SPU_ERROR

[chars] Fatal error - [chars]

Explanation A fatal error occurred in SPU common Driver

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

Error Message %L2-IXP2800_SERVICE-3-IPCP_FAILURE

Function [chars] failure errno [chars]

Explanation IPCP communication failure.

Recommended Action None

Error Message %L2-IXP2800_SERVICE-4-WARNING

[chars]()[[dec]]: [chars]: [chars] ([dec])

Explanation A warning condition occurred in IXP2800_SERVICE Driver which involves exiting the process.

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

Error Message %L2-IXP2800_SERVICE-6-INFO

[chars]

Explanation SERVICE card ixp2800_service driver informational message

Recommended Action NONE : Informational message only

Error Message %L2-IXP2800_SERVICE-7-LOG_FILE_ERROR

ixp2800 service DLL failed to open log file [chars] ([chars])

Explanation The NPU service DLL failed to open the log file

Recommended Action None

JACKET Messages

Error Message %L2-JACKET-2-SPA_FPGA_IMG_ERR

[chars] FPGA is running rollback image, no SPA in jacket will be UP before the FPGA is upgraded to the correct version

Explanation The FPGA is running rollback image, this could be caused by previous FPD failure. %s - device name, Rx MAC or Tx MAC.

Recommended Action Check if the previous FPD failed. Upgrade the FPGA with FPD CLI.

Error Message %L2-JACKET-2-SPA_FPGA_SW_REV_MISMATCH

FPGA software revision mismatch, the FLEX-PLIM may not be fully functional, to upgrade fpga Use the upgrade hw-module fpd CLI in admin mode

Explanation The FPGA software revision is different with the one supported by the running software, this could be caused by software upgrade which supports the new FPGA software revision.

Recommended Action Upgrade the FPGA with FPD CLI.

Error Message %L2-JACKET-3-API_ERROR

Failed to [chars] to jacket process

Explanation Client to the SPA THOR jacket process had a communications failure

Recommended Action Report this error.

Error Message %L2-JACKET-3-CPU_CTRL_INIT

Failed to initiliaze CPU Ctrl: err [chars]

Explanation Unable to initialize CPU Ctrl device.

Recommended Action Report this error.

Error Message %L2-JACKET-3-CPU_CTRL_INTS

Failed to [chars] CPU Ctrl register id [dec]: err [chars]

Explanation Unable to enable/disable/clear a CPU Ctrl interruprt register.

Recommended Action Report this error.

Error Message %L2-JACKET-3-CPU_CTRL_REG_ACCESS

Failed to [chars] CPU Ctrl register id [dec]: err [chars]

Explanation Unable to read/write to a CPU Ctrl register.

Recommended Action Report this error.

Error Message %L2-JACKET-3-CPU_CTRL_REG_LOCK

Failed to enable CPU Ctrl register lock: err [chars]

Explanation Unable to obtain register access lock for CPU Ctrl.

Recommended Action Report this error.

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

[chars]

Explanation SPA Jacket error

Recommended Action When errors occur in jacket, it is very likely the jacket process will restart itself.

Error Message %L2-JACKET-3-IMDR

[chars]: [chars] failed

Explanation Error encountered during iMDR SIP upgrade

Recommended Action Reload Line Card and report this error. jacket process will restart itself.

Error Message %L2-JACKET-3-INTERNAL_ERR

Internal error with [chars] in [chars](), at line [dec]

Explanation Internal error has occured

Recommended Action Report this error.

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_REMOVE

SPA [dec] is being reset due to spa bus error

Explanation This message indicates an error on spa bus for which internal recovery action (i.e., SPA reset) has been initiated.

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-3-SPABRG_BAY

SPAQFP Bridge error in SPA [dec]: [chars]

Explanation SPAQFP bridge has encounted an error in SPA related operation

Recommended Action Reinsert the SPA and fasten it tightly, if error persistent, replace this SPA with same type, report error with all error messages.

Error Message %L2-JACKET-3-SPABRG_INIT

SPA QFP Bridge [dec] init failed: [chars]

Explanation SPAQFP Bridge has encounted an error during initialization

Recommended Action Report Error

Error Message %L2-JACKET-4-QFP_ERROR_BRIDGE_BIND

Failed to bind to the QFP SPA bridge controller server: [chars]

Explanation Failed multiple attempts to bind to QFP SPA bridge controller server

Recommended Action Report this error

Error Message %L2-JACKET-4-QFP_ERROR_GIC_BIND

Failed to bind to the QFP generic interface client library: [chars]

Explanation Failed to bind to the QFP Generic Interface Client

Recommended Action Report this error

Error Message %L2-JACKET-4-QFP_ERROR_HA_ACK

Failed to acknowledge a requested from the QFP high availability server: [chars]

Explanation After servicing a request from the QFP high availability server, the acknowledgement of the request failed

Recommended Action Report this error

Error Message %L2-JACKET-4-QFP_ERROR_HA_BIND

Failed to bind to the QFP high availability server: [chars]

Explanation Failed to bind with the QFP high availability infrastructure

Recommended Action Report this error

Error Message %L2-JACKET-4-QFP_ERROR_MEM_ALLOC

Failed to allocate [unsigned int] bytes for ’[chars]’

Explanation The process failed to allocate memory for the specified resource

Recommended Action When errors occur in jacket, it is very likely the jacket process will restart itself

Error Message %L2-JACKET-4-QFP_ERROR_NO_CONNECTION

SPA bridge controller [unsigned int] failed to find [chars] QFP connection: [chars]

Explanation Failed to find existing QFP connection

Recommended Action If this problem persists, reload the line card

Error Message %L2-JACKET-4-QFP_ERROR_SPA_BRIDGE_CONFIG

Failed to configure the SPA bridge controller: [chars]

Explanation Failed to configure attributes on a SPA bridge controller

Recommended Action Report this error

Error Message %L2-JACKET-4-QFP_ERROR_SPA_BRIDGE_PRESENCE

Failed to notify the QFP about SPA bridge controller [unsigned int]: [chars]

Explanation The line card initialization sequence failed to discover a SPA bridge controller

Recommended Action Report this error

Error Message %L2-JACKET-4-QFP_ERROR_SPA_BRIDGE_REMOVAL

Failed to remove SPA bridge controller [unsigned int]: [chars]

Explanation Failed to remove a SPA bridge controller

Recommended Action Report this error

Error Message %L2-JACKET-4-QFP_ERROR_SPA_BRIDGE_UPDATE

Failed to update the QFP about SPA bridge controller [unsigned int]: [chars]

Explanation Failed to update the QFP SPA bridge controller client about the SPA bridge controller initialization

Recommended Action When errors occur in jacket, it is very likely the jacket process will restart itself

Error Message %L2-JACKET-4-QFP_ERROR_SPA_DISCOVERY

Failed to inform QFP about [chars] of SPA from bay [unsigned int]: [chars]

Explanation Failed to propagate information about SPA insertion or removal

Recommended Action Report this error

Error Message %L2-JACKET-4-QFP_ERROR_SPA_UPDATE_NULL_BAY

Invalid internal structure for bay on SPA [chars]

Explanation Null pointer to data structure when attempting to update SPA status

Recommended Action Try to recover from this error by reloading the SPA or reloading the line card. If this problem persists, please report it.

Error Message %L2-JACKET-4-QFP_ERROR_SPI_RX_PHY_RESET

SPA bridge controller [unsigned int] failed SP4I RX PHY reset on QFP SPI4 link [unsigned int]: [chars]

Explanation Failed enable/disable interrupts on the specified SPI link

Recommended Action If this problem persists, reload the line card

Error Message %L2-JACKET-4-QFP_ERROR_SPI4_CNTRL

SPA bridge controller [unsigned int] failed to [chars] on QFP SPI4 link [unsigned int], direction [chars]: [chars]

Explanation Failed enable/disable specified SPI4 link

Recommended Action If this problem persists, reload the line card

Error Message %L2-JACKET-4-QFP_ERROR_SPI4_INTERRUPT_CNTRL

Failed to [chars] SPI4 [chars] interrupts for SPA bridge controller [unsigned int]: [chars]

Explanation Failed to enable/disable interrupts on the specified SPI4 link

Recommended Action If this problem persists, reload the line card

Error Message %L2-JACKET-4-QFP_ERROR_SPI4_SYNC

Failed to synchronize SPI4 bus between SPA bridge controller [unsigned int] and QFP

Explanation Failed to synchronize SPI4 bus between SPA bridge controller and packet processing engine

Recommended Action If this problem persists, reload the line card

Error Message %L2-JACKET-4-QFP_ERROR_SPI4_SYNC_CHECK

SPA Bridge controller [unsigned int] QFP-SPI4 synchronization check failed in [chars] direction: [chars]

Explanation The SPA bridge controller detected a SPI4 error between itself and QFP

Recommended Action If this problem persists, reload the line card

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-6-SPARULE

SPA [chars] is not allowed in bay [dec]: [chars]

Explanation Either an unsupported SPA was inserted, or an error occurred when a full rate SPA and another SPA tried to use the same SPA bridge controller resources. This is not allowed due to bandwidth limitations. SPA bays 0 and 2 share one controller, and SPA bays 1 and 3 share a second controller.

Recommended Action Both in the case of unsupported SPA type and exceeding bandwidth resources, the newly inserted SPA should be physically removed.

Error Message %L2-JACKET-6-UPGRADE_FPGA

[chars]

Explanation Upgrade SPA FPGA message

Recommended Action none

Error Message %L2-JACKET-7-DEBUG_MSG

Debug: [chars]: [chars] errno [dec]

Explanation This is a debug message in the jacket driver to indicate anomolies which are not critical. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.

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

JDAM Messages

Error Message %L2-JDAM-3-FATAL_ERROR

Fatal error: [chars]: [chars]: [dec]

Explanation A fatal error occurred in JDAM Driver which involves exiting the PLIM process.

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

Error Message %L2-JDAM-6-INFO_MSG

[chars] [chars] [dec]

Explanation This is a Informational message in the JDAM driver to indicate an operation.

Recommended Action No action is required.

Error Message %L2-JDAM-7-DEBUG_MSG

Debug: [chars]: [chars] errno [dec]

Explanation This is a debug message in the JDAM driver to indicate anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.

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

L2C Messages

Error Message %L2-L2C-3-ERR_MISCONFIG

Misconfiguration: Item [chars] on interface [chars] is incompatible with other configuration. The system may now be in an 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-2-OOR_PROC_RESTART

’L2FIB cannot handle updates, because a necessary process is restarting. ’ ’Normal operation will resume on this node once the process has restarted’

Explanation The l2fib_mgr process on the node has detected that a process required to handle updates is restarting. Normal operation will resume once the process has restarted.

Recommended Action Normal operation should resume automatically, once all resources are declared available again; to know the current status of l2fib_mgr’s resources, use the command ’show l2vpn forwarding resource location ’.

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.

Error Message %L2-L2FIB_LIB-6-BDXC_SEND

[chars]

Explanation An IPC between L2FIB and its client process failed; the message will be retried. 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_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_FREE_ERR

[chars] failed due to version mismatch: [hex]

Explanation An attempt done by PD layer to free shared memory has failed. Each shared memory area allocated by L2FIB has a signature or version number in it. The version check for PD layer does not match. 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-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-5-SECURITY_DAI_VIOLATION_AC

Dynamic ARP inspection in AC [chars] detected violated packet - source MAC: [chars], destination MAC: [chars], sender MAC: [chars], target MAC: [chars], sender IP: [chars], target IP: [chars]

Explanation The dynamic arp inspection in attachment circuit has detected violated packet. This might be a security attack. The packet failed dynamic arp inspection has been dropped.

Recommended Action None.

Error Message %L2-L2FIB-5-SECURITY_IPSG_VIOLATION_AC

IP source guard in AC [chars] detected violated packet - source MAC: [chars], destination MAC: [chars], source IP: [chars], destination IP: [chars]

Explanation The IP source guard in attachment circuit has detected violated packet. This might be a security attack. The packet failed IP source guard inspection has been dropped.

Recommended Action None.

Error Message %L2-L2FIB-5-SECURITY_MAC_SECURE_VIOLATION_AC

MAC secure in AC [chars] detected violated packet - source MAC: [chars], destination MAC: [chars]; action: [chars]

Explanation The MAC secure in attachment circuit has detected violated packet. This might be a security attack. A relearn attempt had been made on the attachment circuit for a MAC address which had been already learned by another secure port. One of following action might be configured and will be taken on this attachment circuit: - Restrict: drop the packet and disable the learn attempt - None: forward the packet and allow the MAC to be relearned - Shutdown: shutdown the port on which the learn attempt was made If no action has been configured, the restrict action will be taken by default and packet has been dropped.

Recommended Action None.

Error Message %L2-L2FIB-5-SECURITY_MAC_SECURE_VIOLATION_PW

MAC secure in PW neighbor: [chars], ID: [unsigned long int] detected violated packet - source MAC: [chars], destination MAC: [chars]; action: [chars]

Explanation The MAC secure in the pseudowire has detected violated packet. This might be a security attack. A relearn attempt had been made on the attachment circuit for a MAC address which had been already learned by another secure port. One of following action might be configured and will be taken on this attachment circuit: - Restrict: drop the packet and disable the learn attempt - None: forward the packet and allow the MAC to be relearned - Shutdown: shutdown the port on which the learn attempt was made If no action has been configured, the restrict action will be taken by default and packet has been dropped.

Recommended Action None.

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

The resynchronization of the MAC address table is complete [chars]

Explanation The command to resynchronize the MAC address table may take a while to complete. This message indicates that resynchronization is complete and the MAC address table can be displayed..

Recommended Action No particular action is required.

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.

L2TP Messages

Error Message %L2-L2TP-2-INIT

L2TP initialization failure: [chars] [chars]

Explanation L2TP initialization failed

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

Error Message %L2-L2TP-3-DIFF_L2TP_CLASS

Invalid l2tp-class [chars] for new session; expecting [chars]

Explanation A new session maps to an existing L2TP tunnel, but the session references a L2TP class different than what this tunnel is using.

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

Error Message %L2-L2TP-3-ERRMSG

[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-L2TP-3-GEN_ERR

L2TP internal error: [chars]

Explanation An internal software error occurred

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

Error Message %L2-L2TP-3-IPC_ERR

L2TP IPC transport error: [chars] [chars]

Explanation An IPC transport software error occurred

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

Error Message %L2-L2TP-3-L2TP_CC_ACCT_NO_ACK

No acknowledgement for transmission of L2TPv2 tunnel accounting records

Explanation L2TP has not received acknowledgements, either positive or negative, for tunnel accounting records it sends to Radius in an extended period of time.

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

Error Message %L2-L2TP-3-NO_SRCIP

L2TP has no source IP for [chars]

Explanation CEF lookup has returned no suitable source IP for L2TP to use

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

Error Message %L2-L2TP-6-PACKET

L2TP [chars] received an L2TP [chars] packet

Explanation A packet is delivered to local L2TP stack, but it is meant for a different version of L2TP protocol

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

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

Error Message %L2-L2VPN_MA_PWHE-3-EVENT_ERR

[chars]: [chars]

Explanation An invalid message has been 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.

Error Message %L2-L2VPN_MA_PWHE-3-INIT_ERR

[chars]: [chars]

Explanation An error has happened while initializing l2vpn ma

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

Interface replication failure; interface name: [chars]; error code: [chars].

Explanation An interface replication failed with the error code displayed in the message. The error might have been caused by a misconfiguration or a lack of resources. The replication might have failed for more than one interface; only one interface name and one error code are included in each instance of this message.

Recommended Action Verify the replication status of the PseudoWire Head-End interfaces using the CLI ’show l2vpn xconnect detail’. Refer to the L2VPN section of the Cisco IOS XR Documentation to verify the configuration.

Error Message %L2-L2VPN_MA_PWHE-3-REPLICATION_SUCCESSFUL

Replication done for interface [chars].

Explanation The interface mentioned in the message has been successfully replicated; a previous attempt had failed.

Recommended Action None.

L2VPN_MA Messages

Error Message %L2-L2VPN_MA-3-EVENT_ERR

[chars]: [chars]

Explanation An invalid message has been 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.

Error Message %L2-L2VPN_MA-3-INIT_ERR

[chars]: [chars]

Explanation An error has happened while initializing l2vpn ma

Recommended Action Copy the error message exactly as 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-INVALID

Error [chars]

Explanation AToM getting invalid provision

Recommended Action This is not expected and fatal.

Error Message %L2-L2VPN_PW-3-NOPRIMARY

Pseudowire with address [chars], id [chars], [chars]

Explanation The L2VPN Backup Pseudowire couldn’t find it’s primary PW.

Recommended Action This is not expected and fatal.

Error Message %L2-L2VPN_PW-3-UPDOWN

Pseudowire with address [chars], id [chars], 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.

Error Message %L2-L2VPN_PW-4-ATOM_MERGE_ERR

An existing PW configured with same pw-id [chars] and neighbor with LDP router-id [chars] (Cfg Dest [chars]) is moved to UR state.

Explanation The system is configured with multiple PWs with same pw-id and with neighbor addresses that are owned by the same LDP peer. This configuration is invalid and the last configured PW is maintained.

Recommended Action Remove all the PWs pointing to same neighbor and with same pw-id and readd the one that is correct.

Error Message %L2-L2VPN_PW-6-STANDBY

Pseudowire with address [chars], id [chars], state is standby

Explanation The L2VPN Pseudowire became standby.

Recommended Action If the state change was unexpected, confirm the configuration settings for the cross-connect.

Error Message %L2-L2VPN_PW-6-STANDBY_READY

Pseudowire with address [chars], id [chars], state is standby ready

Explanation The L2VPN Pseudowire became standby ready.

Recommended Action If the state change was unexpected, confirm the configuration settings for the cross-connect.

L2VPN_PWHE Messages

Error Message %L2-L2VPN_PWHE-3-EA_NOMEM

PWHE EA failed to allocate [unsigned int] bytes of memory: ’[chars]’

Explanation The PWHE EA process could not allocate memory needed to update tunnel interface

Recommended Action Check the box for processes with excessive memory

Error Message %L2-L2VPN_PWHE-3-EA_RETRY_FAILED

PWHE EA failed to program interface CH[hex] after [unsigned int] retries: [chars].

Explanation The PWHE EA has failed to program a pwhe interface after 1 or more retries.

Recommended Action Shut/no-shut the pwhe interface, or if needed, remove and re-create the pwhe interface.

Error Message %L2-L2VPN_PWHE-3-EA_STATE

PWHE EA process failed to update the state of interface [unsigned int]: ’[chars]’

Explanation The PWHE EA process failed to update the state of a tunnel interface.

Recommended Action Collect debugging information, shut/no-shut tunnel interface. If the above action doesn’t fix the problem, remove tunnel interface, re-create tunnel interface.

Error Message %L2-L2VPN_PWHE-4-EA_ERR_INIT

PWHE EA process failed to initialize [chars]: ’[chars]’

Explanation The PWHE EA process failed to initialize a critical component. The process cannot proceed and will restart to recover.

Recommended Action Contact Cisco support

Error Message %L2-L2VPN_PWHE-4-EA_RETRY

PWHE EA has retried [unsigned int] times to update interface CH[hex].

Explanation The PWHE EA process has retried programming PWHE interface(s) because other processes are not ready.

Recommended Action If the retry does not succeeded in some time, remove and re-create the PWHE Interface.

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 [chars]: [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-BD_BVI_VMAC

Bridge-domain [chars]: [chars] virtual MAC ([chars]) conflicts with another interface static mac address

Explanation The HSRP or VRRP MAC conflicts with that of another interface in the bridge-domain.

Recommended Action Reconfigure the HSRP or VRRP MAC.

Error Message %L2-L2VPN-4-BD_MST_LOOP

Potential MST forwarding loop in Bridge Domain [chars] (BD ID: [unsigned int]) for interface [chars] and msti: [unsigned int]

Explanation A potential mis-configuration with more than one sub-interfaces in this bridge domain from the same main port and having the same msti value.

Recommended Action To recover from this fault it is recommended to delete from the bridge domain the extra sub-interfaces belonging to the same main port and in the same msti.

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

L2VPN manager is unable to re-connect with peers via ENS/GSP for class [unsigned int], ens_handle [hex], [chars]

Explanation ’L2VPN manager is unable to re-connect with peers via ENS/GSP due to ENS API failures. Will retry.’

Recommended Action To recover from this state, one may try ’process restart’ command. For examples, - proc restart gsp - proc restart l2vpn_mgr OR Copy the error message exactly as it appears on 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-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], [chars]’ 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-NSR_SYNC_SESSION_FAILURE

LDP session [chars] has failed to synchronize

Explanation That is due to NSR being enabled and L2VPN not able to synchronize the L2VPN LDP session.

Recommended Action To recover from this fault, it is recommended to do one of the following: 1- Unconfigure and reconfigure mpls ldp nsr 2- Process restart l2vpn_mgr on standby RP 3- Process restart mpls_ldp on standby RP 4- Reload standby RP

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

State of Bridge Domain [chars] (BD ID: [unsigned int]) has been changed to [chars]

Explanation The state of specified BD, with the BD ID, has been changed. The possible states are: - up - down - admin down The trigger of the BD state change are: - Shut/No Shut BD from CLI - BD operational state changed

Recommended Action None. To suppress this IOS message, please unconfig ’l2vpn logging bridge-domain status’.

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-5-NSR_STATE_CHANGED

Changed state to [chars]

Explanation The NSR state of L2VPN application. The possible states are: - NSR-Disabled (L2VPN NSR is not enabled) - Not NSR-Ready (L2VPN synchronization in progress) - NSR-ready (L2VPN synchronization complete) - Declared NSR-Ready (Declared NSR-Ready to Redundancy Management Framework)

Recommended Action None. To suppress this IOS message, please unconfig ’l2vpn logging nsr’.

Error Message %L2-L2VPN-5-VFI_STATE_CHANGED

State of VFI [chars] under Bridge Domain [chars] (BD ID: [unsigned int]) has been changed to [chars]

Explanation The state of specified VFI, under the BD with BD ID, has been changed. The possible states are: - up - down - admin down The trigger of the VFI state change are: - Shut/No Shut BD from CLI - Shut/No Shut VFI from CLI - BD operational state changed

Recommended Action None. To suppress this IOS message, please unconfig ’l2vpn logging vfi status’.

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

Global L2VPN capabilities have been [chars]

Explanation Global L2VPN capabilities indicate the maximum number of L2VPN service instances which are programmed on all nodes and are computed by default as the minimum capability among the LCs, or as the maximum if ’l2vpn capability high-mode’ is configured. This message indicated that the global L2VPN capabilities have been upgraded/downgraded and an extended ID pool has been activated/deactivated. Use ’show l2vpn capability’ to check the new capabilities in use. UPGRADE The upgrade can happen either if a LC OIR occurred and the remaining LCs in the box support higher global L2VPN capabilities, or if ’l2vpn capability high-mode’ is configured and at least one LC in the box supports higher global L2VPN capabilities. DOWNGRADE The downgrade can happen if ’l2vpn capability high-mode’ is configured and all inserted LCs become low-scale or if a low-scale LC is inserted in an empty chassis.

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], [chars]’ 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], [chars]’ 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.

LI_EA Messages

Error Message %L2-LI_EA-3-ERR_IM_CAPS

[chars] li ea failed on interface CH[hex]. [chars]

Explanation 1) Li MD 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. This error can happen when a new bundle member is added and the MD can not be programmed successfully.

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

Error Message %L2-LI_EA-7-INIT

[chars] failed due to [chars]

Explanation Initialization of lawful intercept ea 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 subscriber li TAP and MD table. 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 TCAM entries needed for security ACL programming in hardeare. 9) Failed to initialize callback function from Feature EA DLL to handle reprogramming of RLB source prefix compression table request from TCAM manager. 10) Failed to initialize feature checkpoint info. This is needed for checkpointing subscriber li md programmed in hardware. 11) event_block failed. This indicates process has encountered unexpected error while waiting for events.

Recommended Action No action is required. Process will be restarted. If not recovered, it’s a fatal condition. If the message recurs, copy the error message exactly as 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*

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.

METRO_STATS_API Messages

Error Message %L2-METRO_STATS_API-7-DEBUG_MSG

Debug Msg : [chars]: [chars]

Explanation This is a debug message in the Hardware Stats Manager Library to indicate anomalies. In most cases these messages will stop once the temporary condition is resolved. Examples of when this error occurs are: 1. The client connection handle received is NULL 2. The arguments to the bind message are incorrect 3. Unable to bind to the hardware IPC driver 4. Error while trying to initialize debug event. 5. Not enough memory to bind to the client

Recommended Action No action is required. These are Debug messages. An error was returned by Stats Manager APIs to applications. Applications receiving this error will report the error.

Error Message %L2-METRO_STATS_API-7-ERR_DLL_INIT

DLL INIT : [chars]: [chars]

Explanation This error indicates that there was an error while initializing the stats dll.

Recommended Action No action is required. The process is restarted automatically.

Error Message %L2-METRO_STATS_API-7-ERR_THREAD

Locking issues: [chars]: [chars]

Explanation This error indicates that the Hardware Stats Manager Library is unable to initialize/destroy locking for client’s attributes and tables.

Recommended Action An error was returned by Stats Manager APIs to applications. Applications receiving this error will report it. Take recommended actions specified in the application’s error message. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-METRO_STATS_API-7-RESERVE_LMT_MSG

Stats Counters Exhausted Msg : [chars] [dec] [chars] [dec] [chars] [chars]

Explanation This is a debug message in the Hardware Stats Manager Library to indicate the stats reserve limit is reached. In most cases these messages will stop once the temporary condition is resolved. Examples of when this error occurs are: 1. The client tries more counters than that are free for that type

Recommended Action No action is required. These are Debug messages. An error was returned by Stats Manager APIs to applications. Applications receiving this error will report the error.

METRO_STATS Messages

Error Message %L2-METRO_STATS-7-ERR_EXHAUST

Stats Exhausted: [chars] [chars] [chars] [dec] [chars] [dec] [chars] [dec]

Explanation This is a debug message in the Hardware Stats Manager to indicate the stats counters of the particular stat type is exhausted. In most cases these messages will stop once the temporary condition is resolved. Examples of when this error occurs are: 1. The client tries more counters than that are free for that type

Recommended Action No action is required. These are Debug messages. An error was returned by Stats Manager to applications. Applications receiving this error will report the error.

Error Message %L2-METRO_STATS-7-ERR_INIT

[chars]: [chars]

Explanation These errors are encountered at mstats process initialization time. The types of errors are: 1 Unable to determine hardware version. 2 Unable to create event manager. This will prevent stats process from receiving events. 3 Unable to create timer. 4 Unable to initialize client database. This will result in clients not being able to register with stats server to collect stats. 5 Unable to allocate Ingress/Egress stats. This will result in Stats manager not being able to maintain/update any hardware stats. 6 Unable to register with debug. This will prevent stats process from logging debug messages. 7 Unable to initialize or register with checkpoint service. This will prevent stats manager from restoring the information required at restart. 8 Unable to connect with SYSDB. This includes failure to connect, bind, register with SYSDB. 9 Unable to Initialize hardware packet service.

Recommended Action No action is required. Process will be restarted. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-METRO_STATS-7-ERR_MEM

Memory error: [chars]: [chars]

Explanation An error occurred in Hardware Stats Manager during shared memory operations. This may be because the system is running low on memory. The types of errors are: 1 Cannot open/reset/close shared memory window 2 Cannot allocate/free shared memory. This will cause Stats Server to not be able to have a shadow copy of stats for all clients.

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

MFR_EA_LTRACE_DLL Messages

Error Message %L2-MFR_EA_LTRACE_DLL-3-OPER_FAIL

ltrace dll : [chars]

Explanation MFR EA ltrace dll operation failure

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

MFR_EA_LTRACE Messages

Error Message %L2-MFR_EA_LTRACE-3-ERROR_INIT_FAIL

ltrace initialization operation failed for error traces: [chars]

Explanation The MFR EA ltrace lib failed to initialize the error ltrace

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

Error Message %L2-MFR_EA_LTRACE-3-EVENT_INIT_FAIL

ltrace initialization operation failed for events: [chars]

Explanation The MFR EA ltrace lib failed to initialize the events ltrace

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

Error Message %L2-MFR_EA_LTRACE-3-INTERNAL_INIT_FAIL

ltrace initialization operation failed for internal traces: [chars]

Explanation The MFR EA ltrace lib failed to initialize the internal ltrace

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

MFR_EA Messages

Error Message %L2-MFR_EA-2-DPC_CALL_FAILED

MFR EA failed handling a DPC [chars]

Explanation Internal error.

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

Error Message %L2-MFR_EA-2-INTERNAL_ERR

[chars]

Explanation Internal error.

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

Error Message %L2-MFR_EA-3-AIB_INIT_FAILED

Failed during AIB initialization, err: [chars]

Explanation The MFR EA process initialization failed whilst trying to connect to AIB.

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

Error Message %L2-MFR_EA-3-INTERFACE_OPERATION_FAILED

Interface [chars] operation failed for ifhandle [hex] err: [chars]

Explanation The MFR EA process failed whilst trying to change interface state.

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

Error Message %L2-MFR_EA-3-MALLOC

Memory allocation failed: [chars]

Explanation A call to malloc failed.

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

Error Message %L2-MFR_EA-3-MEMBER_AIB_REMOVE_FAILED

Failed during AIB remove, err: [chars]

Explanation The MFR EA process failed whilst trying to remove entry from AIB.

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

Error Message %L2-MFR_EA-3-MEMBER_AIB_SET_FAILED

Failed during AIB set, err: [chars]

Explanation The MFR EA process failed whilst trying to insert entry to AIB.

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

Error Message %L2-MFR_EA-3-MEMBER_CAPS_ADD_FAILED

Failed during caps set, err: [chars]

Explanation The MFR EA process failed whilst trying to set caps.

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

Error Message %L2-MFR_EA-3-MEMBER_CAPS_REMOVE_FAILED

Failed during caps remove, err: [chars]

Explanation The MFR EA process failed whilst trying to remove caps.

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

Error Message %L2-MFR_EA-3-MEMBER_ENCAP_REMOVE_FAILED

Failed during encaps remove, err: [chars]

Explanation The MFR EA process failed whilst trying to remove encaps.

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

Error Message %L2-MFR_EA-3-MEMBER_ENCAP_SET_FAILED

Failed during encaps set, err: [chars]

Explanation The MFR EA process failed whilst trying to set encaps.

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

Error Message %L2-MFR_EA-3-MEMBER_INFO_COLLECT_FAILED

Failed to collect member link inforamtion, err: [chars]

Explanation The MFR EA process failed whilst trying to collect member link info.

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

Error Message %L2-MFR_EA-3-NO_STATS

Failed to initialize MFR interface stats collection, err: [chars]

Explanation The MFR EA interface stats collection initialization failed.

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

Error Message %L2-MFR_EA-3-STATE_CHANGE_FAILED

Failed during interface state change, err: [chars]

Explanation The MFR EA process failed whilst trying to change interface state.

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

MFR_MA Messages

Error Message %L2-MFR_MA-2-FAIL

MFR MA failed to [chars]. Thread id is [dec]. [chars]

Explanation During process start up an unrecoverable error occurred. The component will exit and should be restarted by the System Manager.

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

Error Message %L2-MFR_MA-3-DPC_ERROR

[chars] [hex] [chars]

Explanation An error occurred during an operation.

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

Error Message %L2-MFR_MA-3-ENCAP

Unable to process mfr encapsulation request

Explanation An error occurred processing a request to set mfr encapsulation on an interface.

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

Error Message %L2-MFR_MA-3-ERR_MEMBER_ADD

Cannot add [chars] to bundle with nodeid [hex] and group [dec]

Explanation Could not find the bundle interface with the nodeid and group. Hence cannot add the member interface to bundle.

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

Error Message %L2-MFR_MA-3-ERR_MUTEX_LOCK

Mutex lock failed. [chars]

Explanation Locking the mutex governing the access to MFR MA IDB database failed.

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

Error Message %L2-MFR_MA-3-ERR_PULSE

Received unexpected Async Event [hex] for ifhandle [hex]

Explanation IPC thread received an async event pulse for which there is no handler.

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

Error Message %L2-MFR_MA-3-ERROR

[chars] [chars]

Explanation An error occurred during an operation.

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

Error Message %L2-MFR_MA-3-MALLOC

Memory allocation failed: [chars]

Explanation A call to malloc failed.

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

Error Message %L2-MFR_MA-3-RECVFROM

An error occurred receiving a packet: [chars]

Explanation The socket call recvfrom returned an error.

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

Error Message %L2-MFR_MA-3-THREAD_ERROR

[chars]. Thread id is [dec]. [chars]

Explanation An error occurred during an operation.

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

Error Message %L2-MFR_MA-4-ERR_CHKPT

Unexpected error encountered whilst [chars]: [chars]

Explanation MFR 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-MFR_MA-4-ERR_CHKPT_CORRUPT

Corrupt [chars] checkpoint record found: [chars]

Explanation Whilst restoring one of its checkpoint tables MFR MA found a corrupt checkpoint entry. The entry will be ignored and so the relevant interface’s MFR 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-MFR_MA-4-ERR_CHKPT_DUPLICATE

Duplicate [chars] checkpoint record found for [chars]

Explanation Whilst restoring one of its checkpoint tables MFR MA found multiple entries for the same interface. MFR 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-MFR_MA-4-ERR_EVC_ERROR

Error resetting ’[chars]’ connection: [chars]

Explanation After detecting an error with the connection to the specified service, MFR MA failed to reset that connection. This is an internal error. It requires a restart of the process for recovery.

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

Error Message %L2-MFR_MA-4-ERR_MEM_ALLOC

Failed to allocate [unsigned int] bytes for ’[chars]’

Explanation The process failed to allocate memory for the specified resource.

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

Error Message %L2-MFR_MA-4-ERR_MGD_TIMER

Unexpected error encountered whilst [chars]: [chars]

Explanation MFR MA encountered an unexpected error using the Managed Timer library. This is most likely due to a low memory condition but may also be an internal programming error. The error message should provide more information about the cause.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Consider restarting the MFR MA process. *RECUR*.

Error Message %L2-MFR_MA-4-ERR_THREAD_CREATE

Failed to create ’[chars]’ thread: [chars]

Explanation MFR MA encountered an unexpected error creating a new thread. The process will restart to attempt to recover. This is possibly due to a low memory condition but may also be an internal programming error. The error message should provide more information about the cause.

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

Error Message %L2-MFR_MA-6-SENDTO

Packet send attempt timed out: [chars]

Explanation The socket call to send a control packet timed out.

Recommended Action If the message recurs, copy the error message exactly as 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. %s - Error message %d - Interrupt %d - Mask

Recommended Action If the message recurs, copy the error message exactly as it appears on 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

Unknown Mickey Intr: [chars]: [dec]: [dec]

Explanation This message indicates the Mickey FPGA has detected an unknown interrupt. %s - Error message %d - Status register %d - Interrupt mask

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

MLCTRLR Messages

Error Message %L2-MLCTRLR-2-NOMEM

[chars]([dec]): not enough memory for [chars]

Explanation The process is out of memory.

Recommended Action Check process list for source of memory loss. Check if h/w memory requirements are met.

Error Message %L2-MLCTRLR-3-ERROR

[chars]([dec]): [chars] failed ([chars]) - [chars]

Explanation A general failure occured while executing the function in question. The message contains info about the location and cause of the failure and possibly anticipated actions/effects.

Recommended Action Verify continued correct operation of MLCTRLR.

Error Message %L2-MLCTRLR-4-ALARM

[chars]: [chars] [chars]

Explanation The specified MLCTRLR Alarm has been declared or released.

Recommended Action Recommended action is to repair the source of the alarm.

Error Message %L2-MLCTRLR-4-FEAC

[chars] [chars]

Explanation New Far End Alarm Code received.

Recommended Action None.

Error Message %L2-MLCTRLR-4-LOOPSTATUS

[chars] [chars]

Explanation A configurable controller loopback status.

Recommended Action None.

Error Message %L2-MLCTRLR-4-UPDOWN

[chars]: [chars] [chars]

Explanation The specified MLCTRLR is operationally down due to alarm. Check alarm status using show controller Mlt command on the cli.

Recommended Action Recommended action is to repair the source of the alarm.

Error Message %L2-MLCTRLR-4-WARNING

[chars]([dec]): [chars] - [chars]

Explanation A non-fatal error occured while executing the function in question. The message contains info about the location and cause of the failure and possibly anticipated actions/effects.

Recommended Action Verify continued correct operation of MLCTRLR.

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. %s - Error message %d - Interrupt %d - Interrupt Mask

Recommended Action If the message recurs, copy the error message exactly as it appears on 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

Unknown Mouse Intr: [chars]: [dec]: [dec]

Explanation This message indicates the Mouse FPGA has detected an unknown interrupt. %s - Error Description %d - Status register %d - Interrupt mask

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

MRP_MAD Messages

Error Message %L2-MRP_MAD-3-INVALID_MRPDU

CH[hex]: Received an MRPDU which could not be decoded. Stage: [chars]

Explanation An MRPDU packet has been received which MRP could not decode.

Recommended Action *RECUR*

Error Message %L2-MRP_MAD-3-INVALID_MRPDU_RC

CH[hex]: Received an MRPDU which could not be decoded. Stage: [chars]: [chars]

Explanation An MRPDU packet has been received which MRP could not decode.

Recommended Action *RECUR*

Error Message %L2-MRP_MAD-3-MALLOC_FAILURE

A memory allocation failure has occured from which MRP could not recover

Explanation A memory allocation has failed in a situation where MRP cannot continue without possibly being in the wrong state.

Recommended Action Restart the MRP application.

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

Failed to add/remove serial link [chars] into multilink bundle [chars]

Explanation The link addition/removal from a Multilink bundle has failed due to a software error.

Recommended Action No action is required.

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.

MVRP Messages

Error Message %L2-MVRP-4-INITIALISATION_FAILURE

Failed to initialise [chars] in [chars] process: [chars]

Explanation A failure occurred during the initialization of the process. This resulted in the restart of the process.

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

Error Message %L2-MVRP-4-L2VPN_FLUSH

MVRP failed to initiate VLAN ID flush with L2VPN after one second of retrying: [chars]

Explanation The MVRP IO process has failed to initiate VLAN ID flush with L2VPN after five seconds of retrying. Further retries will be attempted every 3 seconds. Until the flush succeeds the currently registered VLAN IDs may be inconsistent.

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

Error Message %L2-MVRP-4-MAD_INIT_FAILED

MVRP failed to reinitialise with the MAD following a change in bridging configuration: [chars]

Explanation The MVRP IO process has failed to reinitialise with the MAD following a change in bridging configuration. Periodic retries will occur to successfully reinitialise with the MAD. Until the MAD is initialised the protocol will not run.

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

Error Message %L2-MVRP-4-PROBLEM_EXITING

Failed to notify SysMgr of intention to exit: [chars]

Explanation A failure occurred during shutdown of the MVRP process, and it was unable to notify the System Manager that it was about to exit. In rare cases, this could result in a failure by the System Manager to restart the process when it ought to do so.

Recommended Action If the process ought to be running and is not, then attempt to restart it using the ’process restart’ command. If this fails, deconfigure the process and re-enter the configuration.

ND Messages

Error Message %L2-ND-3-INIT

Process initialisation failed. [chars]: [chars] ([hex])

Explanation There was a software error during process startup.

Recommended Action The process will restart and try to recover. If this message is not seen again and no other adverse effects are observed then there is no need to take any action. Otherwise, check whether the error code contained in the message indicates that there was a failure to allocate the necessary memory and take the following action. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If resource allocation was not the problem and it hasn’t been fixed by a subsequent restart, then take the following action. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. If the process does not restart automatically, restart it manually. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

OAMMIB Messages

Error Message %L2-OAMMIB-3-NO_DEBUG

Unable to register for OAM MIB debug. No further debugging will occur: [chars]

Explanation In the initialization of the OAM MIB DLL an error occurred whilst attempting to register for debugging. Consequently there will be no debug output from the OAM MIB DLL.

Recommended Action Continue working with the OAM MIB DLL without any debugging taking place or restart the DLL such that during initialization there is another attempt register for debugging.

Error Message %L2-OAMMIB-3-NO_IFTABLE

Unable to create the OAM MIB interface table. All MIB items will be unavailable: [chars]

Explanation In the initialization of the OAM MIB DLL an error occurred while trying to create the internal interface table used for identifying interfaces running ethernet link OAM.

Recommended Action Since this error renders most uses of the OAM MIB impossible, the suggestion is to restart the mibd_interface process to trigger a fresh creation attempt.

Error Message %L2-OAMMIB-3-NO_TRAP

Unable to register for SNMP traps. Traps will not be sent regardless of trap events occurring: [chars]

Explanation In the initialization of the OAM MIB DLL an error occurred while trying to register a callback function for the enabling of SNMP traps. Alternatively whilst trying to enable traps there was a failure in binding to SysDB for trap notifications.

Recommended Action Continue working with the OAM MIB DLL without any the ability to send traps when events occur or restart the DLL such that there is another attempt to register for traps.

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.

OTN_DRIVER Messages

Error Message %L2-OTN_DRIVER-2-HW_ERR

[chars]

Explanation Driver HW error interrupt occurs, it will cause HW reset.

Recommended Action Check if the linecard reported any other errors and/or traffic loss was observed.

Error Message %L2-OTN_DRIVER-3-INIT

[chars]

Explanation Driver initialization error

Recommended Action Check if the linecard reported any other errors and/or traffic loss was observed.

Error Message %L2-OTN_DRIVER-3-SW_ERR

[chars]

Explanation Driver software error

Recommended Action Check if the linecard reported any other errors and/or traffic loss was observed.

Error Message %L2-OTN_DRIVER-6-INTERRUPT

[chars]

Explanation HW interrupt occurs.

Recommended Action Check if the linecard reported any other errors and/or traffic loss was observed.

PAL_CGM Messages

Error Message %L2-PAL_CGM-3-INIT_ERROR

Initialization failed: ([chars]%s)

Explanation The PAL ACL CGM DLL failed to initialize because of memory alloc failure. This DLL does a generalization of an Access Control List to include matching on MQC match criteria If the ccl DLL fails to initialize, the access control list cannot be programmed into the hardware.

Recommended Action The failure should be handled by the process that is loading the DLL. The calling process should retry the initialization.

PAL_IPHC Messages

Error Message %L2-PAL_IPHC-2-EA_CRIT_ERR

[chars]: [chars]: rc equals [hex] ([chars])

Explanation IPHC pal ea critical error

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support iphc 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-PAL_IPHC-3-EA_ERR

[chars]: [chars] equals [hex] [chars]

Explanation IPHC pal ea error

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support iphc 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-PAL_IPHC-6-EA_INFO

[chars] : [chars] : [hex]

Explanation IPHC pal ea informational message

Recommended Action NONE : Informational message only

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

[chars] acl [chars] v4 [dec] 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) IPv6 address compression table is full. c) The ACL doesn’t exist (invalid acl). 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-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-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*

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.

PLAT_L2FIB_VPLS Messages

Error Message %L2-PLAT_L2FIB_VPLS-7-DEBUG_ERROR

PLATFORM-L2FIB-VPLS: Error - [chars] [chars] [chars] [dec]

Explanation Failed to initialize the debugging module in the platform L2FIB VPLS component.

Recommended Action None, platform software will correct itself if this happens.

Error Message %L2-PLAT_L2FIB_VPLS-7-INIT_ERROR

PLATFORM-L2FIB-VPLS: Error - [chars]

Explanation Failed to initialize the VPLS module in the platform L2FIB VPLS component.

Recommended Action None, platform software will correct itself if this happens.

Error Message %L2-PLAT_L2FIB_VPLS-7-LTRACE_ERROR

PLATFORM-L2FIB-VPLS: Error - [chars] [dec] [chars] [dec]

Explanation Failed to initialize the ltrace module in the platform L2FIB VPLS component.

Recommended Action None, platform software will correct itself if this happens.

PLATFORM_ATM_OAM Messages

Error Message %L2-PLATFORM_ATM_OAM-3-PACKET_RX

ATM OAM PKT RX error:[chars]

Explanation There was a software error while processing received OAM cell

Recommended Action No action required if the message is displayed just a few times and stops after that. If the message repeats continously, collect the System Messages displayed on the console and provide them to cisco support. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-PLATFORM_ATM_OAM-3-PACKET_RX

ATM OAM PKT RX error:[chars]

Explanation There was a software error while processing received OAM cell

Recommended Action No action required if the message is displayed just a few times and stops after that. If the message repeats continously, collect the System Messages displayed on the console and provide them to cisco support. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

plim_4p_oc12 Messages

Error Message %L2-plim_4p_oc12-3-ALLOC_FAILED

Process failed to allocate memory [chars]

Explanation Physical Layer Interface Module(PLIM) driver failed to initialized due to unavailable memory and will be restarted. It may affect traffic passing through the ports located on the PLIM. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller,...

Recommended Action The System Manager process (sysmgr) will automatically restart this process up to a fixed number of times when this error is encountered. Execute ’show process pl_e48_pos_4p_oc12 location 0/slot/cpu0’ to verify that the process is up and running. If the process is not operational attempt ’process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0’ where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-plim_4p_oc12-3-CREATE_THREAD_ERROR

Process init failed [chars]

Explanation Physical Layer Interface Module(PLIM) driver failed to initialize. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller,... %s - error code

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

Error Message %L2-plim_4p_oc12-3-DEBUG_INIT_ERROR

Debugging subsystem initialization failed

Explanation Physical Layer Interface Module(PLIM) driver failed to initialize it’s debug subsystem. As result plim debug commands will not work on the PLIM module in question. The rest of functionality of the PLIM driver remains unaffected by the failure. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller.

Recommended Action Restart the process using ’process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0’. Process restart may affect traffic on all 4 oc12 interfaces located on the line card. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-plim_4p_oc12-3-ERR_EVM_CREATE

Interface module driver initialization failed

Explanation Physical Layer Interface Module(PLIM) driver failed to initialize. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller. As result of such failure no trafiic may pass on all 4 oc12 ports located on the 4 port linecard. The interfaces associated with failed PLIM will not come up.

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

Error Message %L2-plim_4p_oc12-3-ERR_EVM_EVENT_BLOCK

process received invalid event [chars]

Explanation Physical Layer Interface Module(PLIM) driver experience an errorr while awaiting for event arrival. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller. As result of the error the PLIM process will be restarted. Traffic may be interrupted on all affected interfaces. %s - error code

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

Error Message %L2-plim_4p_oc12-3-ERR_PORT_INIT

PLIM port init failed [dec] stage-[chars]

Explanation Physical Layer Interface Module(PLIM) driver failed to initialize port. As result of the failure affected interfaces will not come up. %d - failed port number %s - specific stage of port initialization that failed PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer and Packet Over Sonet(POS) controller.

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

Error Message %L2-plim_4p_oc12-3-FWD_REGISTER_ERROR

Process initialization error [chars]

Explanation Physical Layer Interface Module(PLIM) driver failed to initialized and will be restarted. It will affect traffic passing through the ports located on the PLIM. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller,... %s - error code

Recommended Action The System Manager process (sysmgr) will automatically restart this process up to a fixed number of times when this error is encountered. Execute ’show process pl_e48_pos_4p_oc12 location 0/slot/cpu0’ to verify that the process is up and running. If the process is not operational attempt ’process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0’ where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-plim_4p_oc12-3-PORT_AVAILABLE_FAILED

Port failed to become available [chars] [dec]

Explanation Physical Layer Interface Module(PLIM) driver failed to make port available for forwarding. The interface in question will not forward packets. %s - error code %d - port number

Recommended Action Restart the process using ’process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0’. Process restart may affect traffic on all 4 oc12 interfaces located on the line card. Reload the line card using ’hw-module location 0/slot/cpu0 reload’ if the process restart failed to solve the problem.. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-plim_4p_oc12-3-RESET_FAILED

PLIM reset failed [chars]

Explanation The Physical Layer Interface Module(PLIM) driver failed to reset PLIM hardware. %s - error code PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller.

Recommended Action If the error occurred during user command execution retry the command and if the error persist consider restarting plim process ( ’process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0’. PLIM process restart may affect traffic on all 4 oc12 ports. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-plim_4p_oc12-3-STATS_COLLECT_REGISTER_FAILED

Statistics collector registration error [chars] [chars]

Explanation Physical Layer Interface Module(PLIM) driver failed to register PLIM interface statistics collector. No interface statistics such as sonet counters and packet counters will be available on the specified interface. %s - contains interface name %s - contains error code

Recommended Action Restart the process using ’process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0’. Process restart may affect traffic on all 4 oc12 interfaces located on the line card. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-plim_4p_oc12-3-STATSD_COLL_INIT_ERROR

Process initialization error [chars]

Explanation Physical Layer Interface Module(PLIM) driver failed to initialized and will be restarted. It will affect traffic passing through the ports located on the PLIM. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller,... %s - error code

Recommended Action The System Manager process (sysmgr) will automatically restart this process up to a fixed number of times when this error is encountered. Execute ’show process pl_e48_pos_4p_oc12 location 0/slot/cpu0’ to verify that the process is up and running. If the process is not operational attempt ’process restart pl_e48_pos_4p_oc12 location 0/slot/cpu0’ where slot - is slot number in question. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message %L2-plim_4p_oc12-3-TIMER_INIT_FAILED

Process init failed [chars]

Explanation Physical Layer Interface Module(PLIM) driver failed to initialize. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet(POS) controller,... %s - error code

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

Error Message %L2-plim_4p_oc12-3-TX_CLK_GET_INVALID_PORT_CTX

Failed to retrieve tx clock source

Explanation Physical Layer Interface Module(PLIM) driver was unable to determine transmit clock source for the sonet port. The error may appear during show or configuration of the sonet port.

Recommended Action If the error occurred during user command execution retry the command and if the error persist contact technical support.

Error Message %L2-plim_4p_oc12-3-TX_CLK_SET_INVALID_PORT_CTX

Failed to configure tx clock source for sonet port

Explanation Physical Layer Interface Module(PLIM) driver failed to make configure transmit clock source for the sonet port. The sonet port hardware configuration is invalid and may result in traffic being dropped or high error count on the port. This error may appear during attempt to configure clock source for the sonet port.

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

Error Message %L2-plim_4p_oc12-4-INVALID_TIMER

Invalid timer [dec]

Explanation Physical Layer Interface Module(PLIM) driver received unknown timer event. %d - timer type

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