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 unknown 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-551
Layer 2 Messages
10GE_PLIM Messages
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
[dec].
An XGXS RX lane failed to synchronize for port
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
[dec].
An XGXS TX lane failed to synchronize for port
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
off
Port [dec], XFP unable to reach ready state, powering
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
reason : [chars]
An Optic Interface Module error occurred at port [dec],
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-552
OL-23348-01
Layer 2 Messages
10GE_PLIM Messages
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], Detected Remote Fault
Explanation The PLIM received a remote fault on the given interface which will result in a link flap.
Recommended Action No action is required.
Error Message
%L2-10GE_PLIM-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_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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-553
Layer 2 Messages
ACCT_SVR Messages
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.
ACCT_SVR Messages
Error Message
%L2-ACCT_SVR-3-ERR_INIT
init error: [chars] - restarting process to recover.
Explanation The process acct_svr encountered a software error while initializing. The process is
exiting and will be restarted. System will not be affected.
Recommended Action No action is required.
Error Message
%L2-ACCT_SVR-3-ERR_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_INTERNAL
process to recover.
software internal error: [chars] - restarting
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-3-ERR_INTERNAL
process to recover.
software internal error: [chars] - restarting
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-554
OL-23348-01
Layer 2 Messages
ACCT_SVR Messages
Error Message
%L2-ACCT_SVR-4-HFA_CLK_DELTA_FAIL
[dec] out of [dec] total times.
HFA get clock delta has failed consecutively
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-4-HFA_CLK_DELTA_FAIL
[dec] out of [dec] total times.
HFA get clock delta has failed consecutively
Explanation The process acct_svr has failed to get the HFA clock delta for the given consecutive
times. The flow report uses the forwarding asic clock which may be slightly off from the system
clock. To correct the timestamp, the HFA clock delta is retrieve and on failure, the previously
recorded delta is used. This log is printed out after so many consecutive failures to retrieve the clock
delta, which may lead to skewed timestamps in the flow report.
Recommended Action No action is required.
Error Message
%L2-ACCT_SVR-7-ISR_FIFO_USAGE_FLAG ISR FIFO ring buffer usage is [chars]
threshold ([dec]). direction: [dec] num_items equals [dec]
Explanation The process acct_svr detected the condition of ISR FIFO ring buffer usage above or
below the threshold. If the usage is above the threshold, the process acct_svr will bring the ISR FIFO
ring buffer usage back to below the threshold after a while. Traffic will not be affected by this
condition.
Recommended Action No action is required.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-555
Layer 2 Messages
ALPHA_TCAM Messages
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 programmable 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 anomalies 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-556
OL-23348-01
Layer 2 Messages
ALPHA Messages
Error Message
%L2-ALPHA-6-VERSION_WARNING
[chars] [chars] error [hex]
Explanation This is an informational message in the programmable switching Engine driver to
indicate 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 programmable 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 programmable 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]
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-557
Layer 2 Messages
ASIC_ERRORS Messages
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 programmable 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*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-558
OL-23348-01
Layer 2 Messages
ASIC_ERRORS Messages
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 notification 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 notification 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 notification 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
[chars].
ASIC Error library failed to [chars]. Reason:
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
[chars].
ASIC Error library failed to [chars]. Reason:
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*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-559
Layer 2 Messages
ASIC_ERRORS Messages
Error Message
%L2-ASIC_ERRORS-7-ERR_SYSDB
[chars].
ASIC Error library failed to [chars]. Reason:
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
EDM. Reason: [chars].
ASIC Error library has failed to register an
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*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-560
OL-23348-01
Layer 2 Messages
ASIC_SCAN_EXEC Messages
Error Message
%L2-ASIC_ERRORS-7-ERR_SYSDB_EDM_REG
EDM. Reason: [chars].
ASIC Error library has failed to register an
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
EDM. Reason: [chars].
ASIC Error library has failed to register an
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
completion mesaage
[chars]: Scan in progress... Please wait for
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-EXIT
ASIC Scan Server exits after a successful scan
Explanation ASIC scan server exits, expected behavior.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-561
Layer 2 Messages
ASIC_SCAN_SERVER Messages
Error Message
%L2-ASIC_SCAN_SERVER-2-NODE_BRINGDOWN
[chars]
Explanation This is a message in the Asic Scan Server to indicate that it has triggered a critical alarm
and will result in node bringdown. The reason for the failure and the status of the scan operation is
reported.
Recommended Action Run the board diagnostics.
Error Message
%L2-ASIC_SCAN_SERVER-7-ERR_EVM_CREATE
manager: Reason equals [chars].
ASIC Scan Server failed to create the event
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
type: Reason equals [chars].
ASIC Scan Server failed to get the card
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
Reason equals [chars].
ASIC Scan Server encountered error [[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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-562
OL-23348-01
Layer 2 Messages
ATM_ILMI Messages
Error Message
%L2-ASIC_SCAN_SERVER-7-ERR_IO
[chars].
ASIC Scan Server failed to [chars]: Reason equals
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 error 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
initialization/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 with regard to 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-563
Layer 2 Messages
ATM_INARP Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-564
OL-23348-01
Layer 2 Messages
ATM_NETIO Messages
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
--
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-565
Layer 2 Messages
ATM_OAM Messages
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
configuration and change it according to the error.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-566
OL-23348-01
Layer 2 Messages
ATM_RM Messages
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
to reserve [unsigned int]
[chars] : Bandwidth available [unsigned int] : Failed
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 bandwidth 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-567
Layer 2 Messages
ATM_SAAR Messages
ATM_SAAR Messages
Error Message
%L2-ATM_SAAR-2-INIT
Failed to initialize ATM SAAR: [chars] ([chars])
Explanation There was an error initializing 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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-568
OL-23348-01
Layer 2 Messages
ATM_SOP Messages
Error Message
%L2-ATM_SOCKET-3-RESMGR_ATTACH
[chars]
Failed to setup atm socket as a resource manager:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-569
Layer 2 Messages
atmdrv Messages
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 occurred %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
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
[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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-570
OL-23348-01
Layer 2 Messages
atmdrv Messages
Error Message
%L2-atmdrv-2-ERR_ENCAP
[dec] key equals [hex]
[chars] - [dec]: [chars] rc equals [hex] connid equals
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_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_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_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 occurrence 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-571
Layer 2 Messages
ATMGCMGR Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-572
OL-23348-01
Layer 2 Messages
BFD Messages
BFD Messages
Error Message
%L2-BFD-3-CHANGE_ECHO_SOURCE_ADDRESS_FAILED BFD session to neighbor [chars] on
interface [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
error ’[chars]’
Failed to initialize protect server with
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 to neighbor [chars] on
interface [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-573
Layer 2 Messages
BFD Messages
Error Message
%L2-BFD-3-REVERT_ECHO_SOURCE_ADDRESS_SUCCESS BFD session to neighbor [chars] on
interface [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 for
neighbor [chars] interface [chars] even when async pkt received within timer
duration, timer_duration equals [unsigned int] ms, [unsigned int] ms elapsed since
last async pkt received
Explanation BFD Async Detect timer expired even when async pkt received within timer duration,
timer_duration
Recommended Action No action is required.
Error Message
%L2-BFD-4-RATE_LIMIT_WARNING_HIGH_WATERMARK
percent of maximum.
BFD PPS allocation exceeds 90
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
percent of maximum.
BFD PPS allocation now less 85
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-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 personnel
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-574
OL-23348-01
Layer 2 Messages
BFD Messages
Error Message
%L2-BFD-6-ADJACENCY_DELETE
was deleted
Adjacency for neighbor [chars] on interface [chars]
Explanation The adjacency for neighbor ip address was deleted.
Recommended Action No action is required.
Error Message
%L2-BFD-6-FIB_NOT_READY
[chars]
Forwarding is not ready for neighbor [chars] on interface
Explanation The forwarding for session is not ready.
Recommended Action No action is required.
Error Message
%L2-BFD-6-MAX_AGENT_SESSIONS_EXCEEDED
limit [dec]
Number of requested sessions has exceeded
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 Hessians 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 to neighbor [chars] on
interface [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-575
Layer 2 Messages
BFD Messages
Error Message
%L2-BFD-6-SESSION_BUNDLE_ALL_MEMBER_ON BFD session to neighbor [chars] on
interface [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 to neighbor [chars] on
interface [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 to neighbor [chars] on interface [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_INHERIT_OFF BFD session to neighbor [chars] on interface
[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 to neighbor [chars] on interface [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-576
OL-23348-01
Layer 2 Messages
BFD Messages
Error Message
%L2-BFD-6-SESSION_NO_RESOURCES No resources for session to neighbor [chars] on
interface [chars], interval equals [unsigned int] ms[chars]
Explanation The BFD session can not be created or modified due to lack of resources.
Recommended Action Remove other BFD sessions to free resources for this session
Error Message
%L2-BFD-6-SESSION_NO_RESOURCES_CLR Lack of resources condition has cleared for
session to neighbor [chars] on interface [chars]
Explanation Resources are now available for this session.
Recommended Action No action is required.
Error Message
%L2-BFD-6-SESSION_REMOVED
has been removed
BFD session to neighbor [chars] on interface [chars]
Explanation The BFD session has been removed. This is due to the application(s) removing the BFD
session. This can happen as a result of BFD being unconfigured under the application(s) or as a
result of the application(s) adjacency being removed.
Recommended Action No action is required.
Error Message
%L2-BFD-6-SESSION_STATE_DOWN BFD session to neighbor [chars] on interface [chars]
has gone down. Reason: [chars]
Explanation The BFD session has gone down. This may be as a result of the forwarding path being
down.
Recommended Action Determine if the forwarding path to the neighbor has gone down.
Error Message
%L2-BFD-6-SESSION_STATE_UP
is up
BFD session to neighbor [chars] on interface [chars]
Explanation The BFD session is now up.
Recommended Action No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-577
Layer 2 Messages
BGP_AD Messages
Error Message
%L2-BFD-6-SESSION_VERSION_CHANGE BFD session to neighbor [chars] on interface
[chars] is administratively down due to version change from version [unsigned int]
to version [unsigned int]
Explanation The BFD session has been brought administratively down to change protocol version.
Recommended Action No action is required.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-578
OL-23348-01
Layer 2 Messages
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_INIT
Failure during initialization 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-579
Layer 2 Messages
BM_PD Messages
Error Message
%L2-BM_PD-3-DLL_INIT
Failure during initialization 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 initialization 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 initialization 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 initialization 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 initialization 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-580
OL-23348-01
Layer 2 Messages
BM_PD Messages
Error Message
%L2-BM_PD-3-DLL_TRACE
[chars]
Failure initializing tracing ([chars] buffer). Error:
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
[chars]
Failure initializing tracing ([chars] buffer). Error:
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
[chars]
Failure initializing tracing ([chars] buffer). Error:
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
[chars]
Failure initializing tracing ([chars] buffer). Error:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-581
Layer 2 Messages
BM_PD Messages
Error Message
%L2-BM_PD-3-DLL_TRACE
[chars]
Failure initializing tracing ([chars] buffer). Error:
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
[chars]
Failure initializing tracing ([chars] buffer). Error:
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 -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
Error: [chars]
Failure during initialization of [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-582
OL-23348-01
Layer 2 Messages
BM_PD Messages
Error Message
%L2-BM_PD-4-ERR_ADJ_DLL_INIT
[chars]
Failure during initialization of [chars]. Error:
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_ADJ_DLL_INIT
[chars]
Failure during initialization of [chars]. Error:
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
[chars]
Failure during initialization of [chars]. Error:
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
[chars]
Failure during initialization of [chars]. Error:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-583
Layer 2 Messages
BM Messages
Error Message
%L2-BM_PD-4-ERR_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-BM_PD-4-ERR_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-BM_PD-4-ERR_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.
BM Messages
Error Message
%L2-BM-3-ERR_IIR_MEMBERSHIP
[chars].
Link [chars] in [chars] reported by IIR in bundle
Explanation When synchronizing with IIR during restart the link was reported to be in a different
bundle from the checkpoint records of the process. This should never happen and is not recoverable.
The information from IIR was discarded and the process is now out of step with IIR, possibly
leading to further problems.
Recommended Action Delete the checkpoint data for the Bundle Manager process that reported the
error (run rm /tmp/chkpt_bundlemgr_distrib*) and restart the process.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-584
OL-23348-01
Layer 2 Messages
BM Messages
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_DB_CHKPT_RECOVER
restart. Error: [chars]
Unable to recreate object ID [unsigned int] after
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
driver returned [chars]
Could not error-disable interface [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) occurred 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-585
Layer 2 Messages
BM Messages
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_BDL_DATA
int]
Invalid [chars] specified by IIR for CH[hex]: [unsigned
Explanation The data specified in the IIR notification is not one of the recognized values for that
type. The information is invalid and the result is that adjacencies for this bundle cannot be
programmed in hardware.
Recommended Action Delete and recreate the bundle. If the message recurs, copy the error message
exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-BM-4-ERR_IIR_BDL_HANDLE Invalid (NULL) interface handle supplied for a bundle
by IIR
Explanation The interface handle specified in the IIR notification was NULL. The information is
invalid and will be ignored.
Recommended Action If this event can be associated with changes to a particular bundle then delete
and recreate the bundle. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-BM-4-ERR_IIR_MBR_DATA
CH[hex]: [unsigned int]
Invalid [chars] specified by IIR for CH[hex] member
Explanation The data specified in the IIR notification is not one of the recognized values for the type.
The information is invalid and will be ignored.
Recommended Action Delete and recreate the bundle. If the message recurs, copy the error message
exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-586
OL-23348-01
Layer 2 Messages
BM Messages
Error Message
%L2-BM-4-ERR_IIR_MBR_HANDLE Invalid (NULL) interface handle supplied by IIR for a
member of <<CH%08x>>
Explanation The interface handle specified in the IIR notification was NULL. The information is
invalid and will be ignored.
Recommended Action Delete and recreate the bundle. If the message recurs, copy the error message
exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-BM-4-ERR_IIR_OP Unable to report IIR op failure for b_ifh [hex], m_ifh [hex]
(op [chars], state [chars]). Error: [chars]
Explanation An error occurred processing the IIR event and the bundle EA process was unable to
report this error back to IIR. This may lead to some inconsistency with the bundle membership in
the data plane not matching what is intended according to the control plane.
Recommended Action The failure to report the error back to IIR suggests a problem in the connection
to IIR. This may have been a transient problem, but restarting ifmgr and/or the bundlemgr_ea
process on the location of the error might be necessary. The error that should have been reported
also needs to be dealt with. This error may have come from some lower layer platform component,
possibly a resource allocation error. If the error code provides some information as to the failure then
take action appropriate to the error. If the error code is not specific then take action according to
whether the event was a link activation or a link deactivation/deletion. For activation problems
unconfigure and reconfigure the member link - if this fails try restarting the bundlemgr_ea process
after unconfiguring the member link. For deactivation/deletion failures try restarting the improxy
process to trigger a complete resync by the bundlemgr EA.
Error Message
%L2-BM-4-ERR_IIR_SUB_HANDLE Invalid (NULL) interface handle supplied by IIR for a
sub-interface of <<CH%08x>>
Explanation The interface handle specified in the IIR notification was NULL. The information is
invalid and will be ignored.
Recommended Action Delete and recreate the bundle. If the message recurs, copy the error message
exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-BM-4-ERR_INIT
Failure during 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-587
Layer 2 Messages
BM Messages
Error Message
%L2-BM-4-ERR_INIT_ENS
Failure to initialize ENS - retry scheduled. Error: [chars]
Explanation A failure occurred during the initialization of ENS library in the process. This probably
indicates an underlying more severe problem. A retry will be attempted.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-BM-4-ERR_LINK_ATTACHED Link [chars] is attached to [chars] that is thought
to have no attached members.
Explanation This process believes that there are no aggregated 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
Error: [chars]
Failure during cleanup of [chars] in the dot3ad MIB DLL.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-588
OL-23348-01
Layer 2 Messages
BM Messages
Error Message
%L2-BM-4-ERR_MIB_INIT
DLL. Error: [chars]
Failure during initialization of [chars] in the dot3ad MIB
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
Error: [chars]
Failure [chars] in the bundle NetIO DLL during [chars].
Explanation A failure occurred during the initialization of the bundle NetIO DLL. If this occurred
during an upgrade operation then it will cause the NetIO process to reload. Otherwise this will cause
the capsulation to be unloaded, and an error returned to the user. One possible reason for the error
is a low memory condition, particularly if the failure was in allocating trace buffers.
Recommended Action If the error message indicates the failure is low memory condition, reduce other
system activity to ease memory demands. If conditions warrant, upgrade to a larger memory
configuration. Otherwise, Copy the error message exactly as it appears on the console or in the
system log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%L2-BM-4-ERR_PAKMAN
exiting
Unable to handle pakman corruption error: [chars]. Process
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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-589
Layer 2 Messages
BM Messages
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
structures. Error: [chars]
Unable to repair bundle CH[hex] checkpoint
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-590
OL-23348-01
Layer 2 Messages
BM Messages
Error Message
%L2-BM-4-ERR_RESYNC_EXCEED_IIR
exiting.
Exceeded the IIR resync limit for [chars]. Process
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
Process exiting.
Unable to schedule an IIR resync for [chars].
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-591
Layer 2 Messages
BM Messages
Error Message
%L2-BM-4-ERR_RETRY_EXCEED_BDL Exceeded maximum number of retries for [unsigned
int] bundles. First bundle (and error) [chars] ([chars])
Explanation After attempting to resend or query information for a set of bundles a number of times,
the retry limit has been exceeded and no more attempts will be made for the failed set of bundles.
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 bundle(s) still exist(s). Make a minor change to the settings of
the bundle(s) 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
[chars]
Retry limit for GSP initialization exceeded:
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 further 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_IG Exceeded maximum number of retries for [unsigned
int] ICCP Groups (IGs). First IG (and error) [unsigned int] ([chars])
Explanation After attempting to resend or query information at an ICCP Group level for a number
of times, the retry limit has been exceeded and no more attempts will be made for the failed set of
IGs. 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 IG(s) still exist(s). Note that IG 0 is the local IG, and contains
all non-mLACP bundles. 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-592
OL-23348-01
Layer 2 Messages
BM Messages
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_MBR Exceeded maximum number of retries for [unsigned
int] members. First member (and error) [chars] ([chars])
Explanation After attempting to resend or query information for a set of bundle members a number
of times, the retry limit has been exceeded and no more attempts will be made for the failed set of
members. 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 member(s) still exist(s). Make a minor change to the settings of
the member(s) 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_NODE Exceeded maximum number of retries for [unsigned
int] nodes. First node (and error) [chars] ([chars])
Explanation After attempting to resend or query information for a set of nodes a number of times,
the retry limit has been exceeded and no more attempts will be made for the failed set of nodes. 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 node(s) still exist(s). Note that the nodes may be physical local
LCs, or may refer to mLACP peers. 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-593
Layer 2 Messages
BM Messages
Error Message
%L2-BM-4-ERR_RETRY_EXCEED_SYSTEM_MAC
exceeded: [chars]
Retry limit for system MAC address query
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 further
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_SYSMGR
[chars]
Failure communicating readiness to System Manager. Error:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-594
OL-23348-01
Layer 2 Messages
BM Messages
Error Message
%L2-BM-4-ERR_TX_TIMER
[chars]
Failed to [chars] periodic timer for interface CH[hex]:
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 unreplicated 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-LRD_RESYNC
node [hex]
Bundle member [chars] is being referenced from a non-existent
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-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-595
Layer 2 Messages
BM Messages
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-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-596
OL-23348-01
Layer 2 Messages
BM Messages
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_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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-597
Layer 2 Messages
BM Messages
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
able to connect to the core
[chars] [chars] as isolated due to [chars] [chars]
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_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_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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-598
OL-23348-01
Layer 2 Messages
BM Messages
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
to an unresolved misconfiguration: [chars]
Disconnecting from [chars] due
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
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-599
Layer 2 Messages
BM Messages
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
UP.[chars]
The BFD session on link [chars] in [chars] has gone
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
[chars]
The BFD session on link [chars] in [chars] is starting.
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 active bundle members [chars]
Explanation A configuration change has meant that a link is now incompatible (or compatible) with
the other members of the bundle. 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, check the activity and bandwidth configurations
of all the links within the bundle.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-600
OL-23348-01
Layer 2 Messages
BM Messages
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 addressees 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-601
Layer 2 Messages
C_SHIM_PARTNER Messages
Error Message
%L2-BM-6-MLACP_SYSTEM_ID_ARBITRATION
has been established by [chars]
The system id for ICCP Group [unsigned int]
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.
C_SHIM_PARTNER Messages
Error Message
%L2-C_SHIM_PARTNER-3-AIB_INIT_FAILED
[chars]
Failed during AIB initialization, err:
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
[chars]
Failed during AIB initialization, err:
Explanation The C-shim Partner initialization failed while trying to connect to AIB.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-C_SHIM_PARTNER-3-CAP_ADD_ERR Fatal Error: Adding batched channelized
interface caps failed. Reason: [chars]
Explanation ’There is an error when adding batched channelized interface caps.’
Recommended Action Please try to reload that particular SPA or restart the SPA process associated
with that SPA. Copy the error message exactly as it appears on the console or in the system log, call
your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-602
OL-23348-01
Layer 2 Messages
C_SHIM_PARTNER Messages
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_CNTL_ERR
interface caps. Reason: [chars]
Fatal Error: Failed to modify channelized
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
interface caps. Reason: [chars]
Fatal Error: Failed to modify channelized
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
is missing. Reason: [chars]
Fatal Error: Channelized caps definition file
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-603
Layer 2 Messages
C_SHIM_PARTNER Messages
Error Message
%L2-C_SHIM_PARTNER-3-CAP_LKP_ERR
is missing. Reason: [chars]
Fatal Error: Channelized caps definition file
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
Err: [chars]
Failed during create ECM initialization,
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
Err: [chars]
Failed during create ECM initialization,
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
failed. Reason: [chars]
Fatal Error: Setting call-back to IM
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-604
OL-23348-01
Layer 2 Messages
C_SHIM_PARTNER Messages
Error Message
%L2-C_SHIM_PARTNER-3-SET_CALLBACK_ERR
failed. Reason: [chars]
Fatal Error: Setting call-back to IM
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
[chars]
Fatal Error: Failed to unbind to IM. Reason:
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
[chars]
Fatal Error: Failed to unbind to IM. Reason:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-605
Layer 2 Messages
C12000_FR Messages
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 initialized
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-606
OL-23348-01
Layer 2 Messages
CCL Messages
CCL Messages
Error Message
%L2-CCL-3-INIT_ERROR
Initialization failed: ([chars]%s)
Explanation The classification control list (ccl) DLL failed to initialize. This DLL does a
generalization of an Access Control List to include matching on MQC match criteria like QOS
group, MPLS EXP, etc. If the ccl DLL fails to initialize, the access control list cannot be
programmed into the hardware. %s - indicates the reason for the initialization failure. %s - is the
decoded error reason.
Recommended Action The failure should be handled by the process that is loading the DLL. The
calling process should retry the initialization. Collect all debug information if the DLL is continually
failing: ’debug ccl ace error location 0/x/cpu0’ ’debug ccl api detail location 0/x/cpu0’
CDP Messages
Error Message
%L2-CDP-3-ERR_CONN
Connection error on [chars]([pointer]): [chars]
Explanation An error occurred on one of the event connections managed by CDP which CDP could
not recover automatically.
Recommended Action Try restarting CDP. If the message recurs, copy the error message exactly as it
appears on the console or in the system log, call your Cisco technical support representative and
provide the representative with the gathered information.
Error Message
%L2-CDP-3-ERR_IM_ATTR_REGISTRATION
notifications: [chars]
Unable to register for duplex change
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-607
Layer 2 Messages
CDP Messages
Error Message
%L2-CDP-3-ERR_IM_CAPS_ADD
[chars]
Failed to add the CDP capsulation to interface [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
[chars]: [chars]
Failed to remove the CDP capsulation on interface
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
interface [chars]: [chars]
Failed to register for MTU size changes on
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
[chars]: [chars]
Failed to register for state changes on interface
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-608
OL-23348-01
Layer 2 Messages
CDP Messages
Error Message
%L2-CDP-3-ERR_INTF_INIT
[chars].
Initialisation of CDP on interface [chars] failed:
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
[chars]
No CDP protocol statistics can be collected on [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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-609
Layer 2 Messages
CDP Messages
Error Message
%L2-CDP-3-ERR_IPV6_ADDRESS_SCAN [chars]: Failed to scan the IPv6 addresses for
this interface: [chars]. This means that IPv6 information will be missing from
outgoing CDP packets
Explanation A scan of the IPv6 addresses on this interface has failed. This means that IPv6 address
information for this interface will not be included in outgoing CDP packets. The neighboring device
will not see the IPv6 address information for this interface.
Recommended Action Restarting CDP as the address consumer, or the ipv6_ma as the address
provider on this node may rectify the problem. proc restart cdp location location of failure or proc
restart ipv6_ma location location of failure
Error Message
%L2-CDP-3-ERR_IPV6_REGISTRATION Unable to register for IPv6 address
notifications: [chars]. This means that IPv6 information will be missing from
outgoing CDP packets.
Explanation CDP registration with the IP address library has failed. This means that IPv6 address
information for interfaces local to this node will not be included in outgoing CDP packets. The
neighboring devices will not see the IPv6 address information for this router’s interfaces.
Recommended Action Restarting CDP as the address consumer, or the ipv6_ma as the address
provider on this node may rectify the problem. proc restart cdp location location of failure or proc
restart ipv6_ma location location of failure
Error Message
%L2-CDP-3-ERR_STATS
[chars]
No per-interface CDP protocol statistics can be collected:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-610
OL-23348-01
Layer 2 Messages
CDP Messages
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
[chars] (media [chars]): [chars]
Error setting up the CDP multicast address on
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
neighbor entries
The CDP cache on this node is full. It contains [dec]
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-611
Layer 2 Messages
CDP Messages
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
[chars]
Initialization warning, module: [chars], operation: [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
[chars]
Termination warning, module: [chars], operation: [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-612
OL-23348-01
Layer 2 Messages
CEMA Messages
Error Message
%L2-CDP-6-DELETED_NEIGHBOR CDP Neighbor [chars] on interface [chars] has been
deleted, remote interface [chars]
Explanation An entry has been removed from the CDP neighbors table. Notification of deleted CDP
neighbors requested through ’cdp log adjacency changes’.
Recommended Action No action is required.
Error Message
%L2-CDP-6-NEW_NEIGHBOR New CDP neighbor [chars] detected on interface [chars],
remote interface [chars]
Explanation A new entry has been added to the CDP neighbors table. Notification of new CDP
neighbors requested through ’cdp log adjacency changes’.
Recommended Action No action is required.
CEMA Messages
Error Message
%L2-CEMA-3-FATAL_ERR
CEMA Fatal Error: [chars]
Explanation An internal fatal error was detected in CEMA module operation
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-CEMA-3-MISMATCH_ERR
CEMA Mismatch Error: [chars]
Explanation A process on the line card that manages a SPA was restarted. As a part of restart, a
mismatch was detected between user specified configuration and the actual configuration of SPA
hardware.
Recommended Action The mismatch can be service affecting in certain cases. Please check if the
entity specified in the error log and all it’s children are functioning correctly. Contact Cisco TAC for
further assistance.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-613
Layer 2 Messages
CFM Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-614
OL-23348-01
Layer 2 Messages
CFM Messages
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 an interface state change or
changes in configuration: [chars]
Explanation A failure occurred when attempting to generate or disable CCM messages for a number
of local MEPs. This event was triggered by either an EFP state change or a change in configuration
(e.g. CoS bit changes or CCM interval changes). This may result in outgoing CCM messages
containing incorrect 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.
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 an EFP state changes, 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-615
Layer 2 Messages
CFM Messages
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_MAC_ADDR_UPDATE_FAILED Error processing MAC address changes for
[unsigned int] interfaces. Outgoing CCMs will contain incorrect source MAC
addresses: [chars]
Explanation CFM was unable to update internal MAC address state following a change to the MAC
addresses on a group of interfaces. CCMs will now be being sent on the affected interfaces with an
incorrect MAC address.
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_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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-616
OL-23348-01
Layer 2 Messages
CFM Messages
Error Message
%L2-CFM-3-CFG_MP_UPDATE_INCONSISTENCY
CH[hex]: [chars]
Failed to update MP config on interface
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-617
Layer 2 Messages
CFM Messages
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
database: [chars]
Failed to perform [chars] operation on [chars] lock in
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 behavior 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-618
OL-23348-01
Layer 2 Messages
CFM Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-619
Layer 2 Messages
CFM Messages
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
filter string: [chars]
Failed to enable the requested debugging. Invalid debug
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-620
OL-23348-01
Layer 2 Messages
CFM Messages
Error Message
%L2-CFM-3-L2FIB_ERROR
[chars]
Failed to communicate with the L2FIB Infrastructure:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-621
Layer 2 Messages
CFM Messages
Error Message
%L2-CFM-3-MP_DB_ALLOC
Error [chars]
Failed to create Maintenance Point [chars] in the database.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-622
OL-23348-01
Layer 2 Messages
CFM Messages
Error Message
%L2-CFM-3-STATE_UPDATE_DROPPED
in CCMs.
Failed to update [unsigned int] interface states
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-623
Layer 2 Messages
CFM Messages
Error Message
%L2-CFM-4-BD_BATCH_DELETE_FAILED
unused bridge domains.
Failed to allocate memory for batched delete of
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
the current state: [chars]
Configuration change requested is inconsistent with
Explanation CFM received 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-624
OL-23348-01
Layer 2 Messages
CFM Messages
Error Message
%L2-CFM-4-ENCAP_CHANGE
this interface
[chars]: [chars] on Interface CH[hex] - CFM [chars] on
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 encapsulation
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 (i.e., there is CFM configuration
remaining), then remove all CFM configuration, commit this change, then re-apply the
configuration.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-625
Layer 2 Messages
CFM Messages
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
[chars]. [chars]
Failed to manage the checkpointed state:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-626
OL-23348-01
Layer 2 Messages
CFM Messages
Error Message
%L2-CFM-4-MIB_CHKPT_ITEM_ERROR
single item: [chars]. [chars]
Failed to manage the checkpointed state for a
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 (e.g. 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 (i.e. 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 (e.g. 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-627
Layer 2 Messages
CFM Messages
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-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-SPIO_WARNING
Internal SPIO Error : [chars]
Explanation SPIO PD software error has occurred. 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-628
OL-23348-01
Layer 2 Messages
CFM Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-629
Layer 2 Messages
CFMMIB Messages
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 organization-specific or otherwise
unknown TLVs contained in the packet (i.e. 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-630
OL-23348-01
Layer 2 Messages
CHDLC_EA Messages
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
EA process will restart
Error receiving an event: [chars]. The cHDLC
Explanation An error occurred 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 occurred 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
received in a single batch from IM
CH[hex]: Multiple [chars] notifications
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*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-631
Layer 2 Messages
CHDLC_MA Messages
CHDLC_MA Messages
Error Message
%L2-CHDLC_MA-3-ERR_IIR_BDL_OP The cHDLC MA failed to process a bundle IIR [chars]
message on CH[hex], error: [chars]
Explanation The chdlc_ma process failed to process a bundle IIR notification message. Further it is
not able to propagate the message back to the virtual interface owner, and hence it is possible that
the basecaps is out of step with the bundle configuration.
Recommended Action *SUPPORT*
Error Message
%L2-CHDLC_MA-3-ERR_INTF_UP_DOWN An error has occurred 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
has unexpectedly failed: [chars]
Startup of the cHDLC Socket feature
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
MA process will restart
Error receiving an event: [chars]. The cHDLC
Explanation An error occurred in the event loop. The process will restart which should recover the
situation.
Recommended Action *RECUR*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-632
OL-23348-01
Layer 2 Messages
CHDLC_MA Messages
Error Message
%L2-CHDLC_MA-4-ERR_INIT Failure during initialization of the [chars]. Error
[chars]. The process will restart
Explanation A failure occurred 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 occurred whilst handling an event received from the packet thread.
Recommended Action *RECUR*
Error Message
%L2-CHDLC_MA-4-ERR_PKT_HANDLER
[chars]: [chars].
Failure during the handling of a packet event in
Explanation A failure occurred whilst handling a packet event.
Recommended Action *RECUR*
Error Message
%L2-CHDLC_MA-4-ERR_THREAD
[chars].
Failure during a cross thread operation in [chars]:
Explanation A failure occurred 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*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-633
Layer 2 Messages
CHDLCDLL Messages
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
type-code [hex]
Encapsulation of HDLC packet failed. Packet
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
infrastructure: [chars]
Could not register with tracing
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-634
OL-23348-01
Layer 2 Messages
CHNLZD_EFCM Messages
CHNLZD_EFCM Messages
Error Message
%L2-CHNLZD_EFCM-3-ERROR_CFG_BUFF_MAP_MEMORY
controller configuration buffer
Error mapping to SPA bridge
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
configuration buffer.
Error opening SPA bridge controller
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*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-635
Layer 2 Messages
COMMS Messages
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
dropped: [chars]
Unexpected error has lead to an incoming message being
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
invalid id (%hu)
Checkpoint data for this connection (id %hu) has
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
connection [chars]
Failed to save Checkpoint sequence information for
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-636
OL-23348-01
Layer 2 Messages
CPP_EXMEM Messages
Error Message
%L2-COMMS-3-SAVE_FAILED
[chars]
Failed to save Checkpoint entry [hex]/[hex] on connection
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
percent depleted
CPP [dec] [chars] memory recovered - [dec]
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
depleted
CPP [dec] [chars] memory low - [dec] percent
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-637
Layer 2 Messages
cpp_sbs Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-638
OL-23348-01
Layer 2 Messages
CPPHA Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-639
Layer 2 Messages
CPPHA Messages
Error Message
%L2-CPPHA-3-FAULTCRASH
dump.
CPP [dec] unresolved fault detected, initiating crash
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-640
OL-23348-01
Layer 2 Messages
cpposlib Messages
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.
d1qnetio Messages
Error Message
%L2-d1qnetio-3-CHAIN_BUILDER_FAILED
’[chars]’ (error: [chars])
The chain build function failed because
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-641
Layer 2 Messages
d1qnetio Messages
Error Message
%L2-d1qnetio-3-IDB_NOT_FOUND
be found
The Netio IDB associated with handle [hex] could not
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
during capsulation initialization
Unable to create the protocol registries
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
err: [chars]
A error occurred during trace initialization,
Explanation The 802.1Q NetIO component encountered 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-642
OL-23348-01
Layer 2 Messages
d1qnetio Messages
Error Message
%L2-d1qnetio-4-CHAIN_UNBUILDER_FAILED
’[chars]’ (error: [chars])
The chain unbuild function failed because
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
(error: [chars])
An error occurred during debug initialization
Explanation The 802.1Q NetIO component encountered 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
(error: [chars])
802.1Q NetIO termination failed because ’[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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-643
Layer 2 Messages
DIV2_DM Messages
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 from 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 [dec] 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]
[chars]: Tuple read failed with error [hex]
Explanation An error occurred 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-644
OL-23348-01
Layer 2 Messages
DWDM Messages
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
equals [dec]
dwdm: fatal error encountered, reason equals [chars], errno
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-645
Layer 2 Messages
DWDM Messages
Error Message
%L2-DWDM-4-FORCED_MAINTENANCE
Reason: [chars]
Port id: [chars], Forced Maintenance: [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-646
OL-23348-01
Layer 2 Messages
E3EGRESSQ Messages
E3EGRESSQ Messages
Error Message
%L2-E3EGRESSQ-3-ERR_MEM_ALLOC
([chars])
Failed to allocate [dec] bytes from [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-647
Layer 2 Messages
E3EGRESSQ Messages
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
([chars])
Failed to open shared memory window [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
exceeds the high threshold of [dec]
MQS counter utilization [dec]
Explanation The multicast counter utilization has exceeded the high threshold. This may impact the
delay and/or jitter of multicast 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-648
OL-23348-01
Layer 2 Messages
E3EGRESSQ Messages
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
([chars])
Failed to obtain platform info for [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-649
Layer 2 Messages
E3EGRESSQ Messages
Error Message
%L2-E3EGRESSQ-4-MEM_INVALID_MQS_COUNTER_MAXTHR
supported limit (1 - 2048)
MQS max threshold [dec] is not in
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
supported limit (1 - 2048)
MQS min threshold [dec] is not in
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
lesser than current min-th [dec]
MQS max-th [dec] is
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
greater than current max-th [dec]
MQS min-th [dec] is
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
within the low threshold of [dec]
MQS counter utilization [dec]
Explanation The multicast counter utilization has eased off to below the low threshold.
Recommended Action No action required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-650
OL-23348-01
Layer 2 Messages
E3INGRESSQ Messages
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
exceeds the high threshold of [dec]
MQS counter utilization [dec]
Explanation The multicast counter utilization has exceeded the high threshold. This may impact the
delay and/or jitter of multicast 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-651
Layer 2 Messages
E5EGRESSQ Messages
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
supported limit (1 - 16384)
MQS max threshold [dec] is not in
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
supported limit (1 - 16384)
MQS min threshold [dec] is not in
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
lesser than current min-th [dec]
MQS max-th [dec] is
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-652
OL-23348-01
Layer 2 Messages
E5INGRESSQ Messages
Error Message
%L2-E5EGRESSQ-4-MEM_MQS_MINTHR_NOT_MATCHING_CURR_MAXTHR
greater than current max-th [dec]
MQS min-th [dec] is
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
within the low threshold of [dec]
MQS counter utilization [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-653
Layer 2 Messages
edge_l2fwd_rewrite Messages
edge_l2fwd_rewrite Messages
Error Message
%L2-edge_l2fwd_rewrite-2-FM_ADD_FEAT_ERR
[chars], err: [chars]
[chars], Failed to add feature for
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], err: [chars]
[chars], Failed to del feature for
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
supported on E3 Linecards
[chars]: [chars] is not
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
from FWD MemMgr, err: [chars]
[chars], Failed to read [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-654
OL-23348-01
Layer 2 Messages
edge_l2fwd_rewrite Messages
Error Message
%L2-edge_l2fwd_rewrite-2-HFA_CREATE_ERR
HFA
[chars],Failed to create gather index in
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
HFA
[chars],Failed to program [chars] ucast in
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
HFA
[chars],Unable to open connection with
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
failed for Ifhandle equals [hex] err:[chars]
[chars], Insert encap string
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-655
Layer 2 Messages
edge_l2fwd_rewrite Messages
Error Message
%L2-edge_l2fwd_rewrite-2-MEM_REG_ERR
Forwarding Memory Manager
[chars], Error while registering with
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
the PLU Leaf
[chars], Failed to allocate memory for
Explanation edge_l2fwd_rewrite Forwarding memory module failed to allocate memory for the PLU
leaf
Recommended Action Please 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
failed OI equals [hex] err:[chars]
[chars], remove encap string
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-656
OL-23348-01
Layer 2 Messages
edge_l2fwd_rewrite Messages
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
the TLU Leaf
[chars], Failed to allocate memory for
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
size:[dec], Write Size:[dec]
[chars], Invalid TLU write size, TLU
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-657
Layer 2 Messages
edge_l2fwd_rewrite Messages
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
err: [chars]
[chars],Uidb set failed for xconnid:[dec],
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]
[chars], Failed to add mcast entry, err:
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
server, err: [chars]
[chars], Failed to connect to XBMA
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-658
OL-23348-01
Layer 2 Messages
edge_l2fwd_table Messages
Error Message
%L2-edge_l2fwd_rewrite-2-XBMA_DEL_ERR
[chars]
[chars], Failed to del mcast entry, err:
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
library, err: [chars]
[chars], Failed to initialize XBMA
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
in FAD
[chars], Failed to delete [chars] for [chars]
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
reason:[chars]
[chars], Failed to initialize FAD,
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-659
Layer 2 Messages
edge_l2fwd_table Messages
Error Message
%L2-edge_l2fwd_table-2-FAD_INSERT_ERR
[chars] in FAD
[chars], Failed to insert lookup entry for
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
region in FAD
[chars], Failed to program [chars]
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] TCAM format in FAD
[chars], Failed to program
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] in FAD
[chars], Failed to update lookup entry for
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-660
OL-23348-01
Layer 2 Messages
edge_l2fwd_table Messages
Error Message
%L2-edge_l2fwd_table-2-FM_CONFIG_ERR
config in FM
[chars], Failed to set [chars] feature
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
PLU Leaf
[chars], Failed to allocate memory for the
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
type:[chars], direction:[dec]
[chars],[dec] Table registration failed ! Table
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-661
Layer 2 Messages
edge_l2fwd_table Messages
Error Message
%L2-edge_l2fwd_table-2-TABLE_MALLOC_ERR
the Table: [chars]
[chars], Failed to allocate memory for
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
TLU Leaf
[chars], Failed to allocate memory for the
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-662
OL-23348-01
Layer 2 Messages
EGRESSQ_HW_DLL Messages
EGRESSQ_HW_DLL Messages
Error Message
%L2-EGRESSQ_HW_DLL-3-ENQ_PKT_LOGIC_ERROR
shq_enq_reg_debug_mux [hex]
Sharq ENQ packet logic error occurred,
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-663
Layer 2 Messages
EGRESSQ_HW_DLL Messages
Error Message
%L2-EGRESSQ_HW_DLL-3-FAIL_TO_GET_BP_MAP_FROM_PLIM_AISC
backpressure map from Plim ASIC [dec]. reason [chars]
Failed to get
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
count: [dec], error_addr: [hex]
FCRAM BIST failed, channel: [dec],
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)
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 10 MB) 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
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-664
OL-23348-01
Layer 2 Messages
EGRESSQ_HW_DLL Messages
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-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 hardware 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
Illegal queue (counter value [hex])
EgressQ detected packets sent to
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-665
Layer 2 Messages
EGRESSQ_HW_DLL Messages
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
Reduced-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
configured high threshold value: [chars]
Single Bit Error rate exceeded
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)
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 10 MB) 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-666
OL-23348-01
Layer 2 Messages
EGRESSQ_HW_DLL Messages
Error Message
%L2-EGRESSQ_HW_DLL-3-UNALLOCATED_QUEUE_NOT_EMPTY
egress queue [dec]. (queue size [dec] bytes)
Packets sent to unallocated
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 10 MB) 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-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 incompatible
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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-667
Layer 2 Messages
EGRESSQ Messages
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 incompatible
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
[chars]
LWM message send failed: [chars] reason:
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)
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-668
OL-23348-01
Layer 2 Messages
EGRESSQ Messages
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 incompatible
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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-669
Layer 2 Messages
ELO_COMMON Messages
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.
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
is in standby role: [chars]
Unable to block on sysmgr on the node which
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-670
OL-23348-01
Layer 2 Messages
ELO Messages
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
module: [chars]
Failed to cleanup common verification
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
module: [chars]
Failed to initialize common verification
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-671
Layer 2 Messages
ELO Messages
Error Message
%L2-ELO-3-COULD_NOT_GET_NODEID
node it is running on: [chars]
Ethernet Link OAM Daemon failed to determine the
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
’CH[hex]’: [chars]
Failed to remove PFI caps from interface
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 resynchronize 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
[chars]: [chars]
Ethernet Link OAM Daemon failed to initialize
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-672
OL-23348-01
Layer 2 Messages
ELO Messages
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 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-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
platform: [chars]
[chars]: Failed to change Loopback state in the
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
Link OAM Daemon: [chars]
Failed to send an LWM reply message in the Ethernet
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-673
Layer 2 Messages
ELO Messages
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 behavior should be
observed.
Recommended Action *SUPPORT*
Error Message
%L2-ELO-3-PFI_CLEANUP_FAILED_ATTR_UNREGISTER Failed to unregister 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
SPIO: [chars]
Failed to successfully receive an OAMPDU from
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
[chars]
Failed to signal the end of a resync with SPIO:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-674
OL-23348-01
Layer 2 Messages
ELO Messages
Error Message
%L2-ELO-3-SPIO_MODULE_INIT
[chars]
Failed to register for packet IO on initialisation:
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
[chars]: [chars]
Ethernet Link OAM Daemon failed to cleanup
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-675
Layer 2 Messages
ELO Messages
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
triggered by the platform
An unknown event of type ’[hex]’ has been
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 Ethernet 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 request 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-676
OL-23348-01
Layer 2 Messages
ELO Messages
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 delivered to the remote peer.
Recommended Action Resynchronization 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-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-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-677
Layer 2 Messages
ELO Messages
Error Message
%L2-ELO-6-INTF_DISCOVERY_TIMEOUT
specified time
[chars]: OAM discovery failed to complete in the
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
reason: [chars]
[chars]: Remote dying gasp detected, with
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
the interface
[chars]: OAM [chars] loopback has been [chars] on
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-678
OL-23348-01
Layer 2 Messages
ELO Messages
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
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
than the remote MAC
[chars]: Cancelling loopback mode as our MAC is lower
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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-679
Layer 2 Messages
ELO Messages
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
to an interface
Profile ’[chars]’ is not configured, but has been attached
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-680
OL-23348-01
Layer 2 Messages
ELOGM Messages
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
invalid state.
A variable response from the remote peer contained
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
cleanup debug: [chars]
Ethernet Link OAM Global Manager failed to
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-681
Layer 2 Messages
EMA Messages
Error Message
%L2-ELOGM-4-DEBUG_INIT_FAILED
initialize debug: [chars]
Ethernet Link OAM Global Manager failed to
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
[chars]
Ethernet Link OAM Global Manager failed to process events:
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
[chars]
Ethernet Link OAM Global Manager failed to initialize:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-682
OL-23348-01
Layer 2 Messages
EPI Messages
Error Message
%L2-EMA-4-ERR_EVM_EVENT_BLOCK
Unrecoverable error in event loop. Error: [chars]
Explanation An error (other than EINTR) occurred 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 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-EMA-4-ERR_SYSMGR
[chars]
Failure communicating readiness to System Manager. Error:
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.
EPI Messages
Error Message
%L2-EPI-3-ATTR_NOTIFY_FAILED
attributes - out of memory
Failed to notify a client of a change to interface
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-683
Layer 2 Messages
EPI Messages
Error Message
%L2-EPI-3-INIT_FAILED
[chars]
Failed to initialize, [chars] failed [unsigned int]:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-684
OL-23348-01
Layer 2 Messages
ESPI Messages
ESPI Messages
Error Message
%L2-ESPI-3-ERR_MEM_ALLOC
Memory allocation failed for internal data structures
Explanation Memory was not available for an internal data structure. The requested operation could
not be accomplished because of a low memory condition. The LC will not boot up successfully and
will not be able to participate in data forwarding.
Recommended Action Run the debug show commands, gather data and contact tac. Also ensure the
LC is populated with the minimum amount of memory required for proper operation. If the message
recurs, copy the error message exactly as it appears on the console or in the system log, call your
Cisco technical support representative and provide the representative with the gathered information.
Error Message
%L2-ESPI-3-RX_ERR
[chars]: [chars] [hex]
Explanation This error usually indicates an internal hardware/software problem on the FPGA. This
affects communication bus between adjacent ASICs on the hardware datapath. The LC may not be
able to forward data packets and traffic loss may be observed due to this error. The From CPP or To
CPP direction, the detailed error string and the slot number are provided as part of the message.
Recommended Action ESPI Interface is Reset and Recovered
Error Message
%L2-ESPI-3-TX_ERR
[chars]: [chars] [hex]
Explanation This error usually indicates an internal hardware/software problem on the FPGA. The
affects the communication bus between adjacent ASICs on the hardware datapath. The LC may not
be able to forward data packets and traffic loss may be observed due to this error. The From CPP or
To CPP direction, the detailed error string and the slot number are provided as part of the message.
Recommended Action ESPI Interface is Reset and Recovered
eth_gl Messages
Error Message
%L2-eth_gl-4-EVENT_BLOCK
(error: [chars])
An error was received while waiting for an event:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-685
Layer 2 Messages
ETH_OUTPUT Messages
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.
ETH_OUTPUT Messages
Error Message
%L2-ETH_OUTPUT-3-ERR_EVM_CREATE
[chars]
Failed to create event connection manager:
Explanation The ethernet output process was unable to obtain an event connection manager. Ethernet
Output process client functionality on the affected node may be reduced until the problem 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-ETH_OUTPUT-3-ERR_NO_MEM
int] bytes)
Out of memory (failed attempt to reserve [unsigned
Explanation The Ethernet Output process was not able to allocate the memory that it needed to
complete the operation. Ethernet Output process client 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.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-686
OL-23348-01
Layer 2 Messages
ether_spa_intr Messages
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.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-687
Layer 2 Messages
ETHER Messages
Error Message
%L2-ether_spa_plugin-6-LINK_EVENT
[chars]
Interface TenGige [dec]/[dec]/[dec]/[dec],
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
[dec]
An Optics is [chars] for bay [dec] and port
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
failed . Disable
[chars] port [dec] security check
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-688
OL-23348-01
Layer 2 Messages
ETHER Messages
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
create [chars]
Ethernet: [chars]() line [dec]: out of memory, unable to
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-689
Layer 2 Messages
ETHER Messages
Error Message
%L2-ETHER-3-BDL_IIR_OP_FAILED The basecaps failed to process a bundle IIR [chars]
message on [chars], error: [chars]
Explanation The ethernet driver failed to process a bundle IIR notification message. Further it is not
able to propagate the message back to the virtual interface owner, and hence it is possible that the
Ether basecaps is out of step with the bundle configuration.
Recommended Action Restart the ether_caps_partner process in an attempt to recover, or if this fails,
detach and re-attach the physical member interface that the error was reported on by unconfiguring
and reconfiguring the bundle member id.
Error Message
%L2-ETHER-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
[chars]: [chars]
Ethernet: [chars]() line [dec]: Bad sysdb call for tuple
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
[chars]: [chars]
Ethernet: [chars]() line [dec]: init failed in function
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-690
OL-23348-01
Layer 2 Messages
ETHER Messages
Error Message
%L2-ETHER-3-INVALIDARGSIZE
[chars] in [chars]
Ethernet: Incompatible structure definition for
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
[chars]() - [chars]
Ethernet: Failure initializing asynchronous timers:
Explanation A failure occurred 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
[chars]
Ethernet: Unsupported stats request [dec] in
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-691
Layer 2 Messages
ETHERNET Messages
Error Message
%L2-ETHER-4-ERR_EVM_EVENT_BLOCK
[chars]
Failure during receipt of message. Error:
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
error: [chars]
Failed to initialize interface [chars], due to
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-692
OL-23348-01
Layer 2 Messages
ETHERNET Messages
Error Message
%L2-ETHERNET-3-MIB_ERROR
interface [hex]: [chars]
Unable to fetch requested Etherlike MIB data for
Explanation An error occurred 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 occurred 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
to error: [chars]
Port state FSM operation failed [chars] on [chars], due
Explanation An operational error occurred 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-693
Layer 2 Messages
ETHERNET Messages
Error Message
%L2-ETHERNET-3-TX_DISABLE
remote signalling
Interface [chars], link [chars]forced down due to
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-BDL_IIR_OP_FAILED The driver failed to process a bundle IIR
[chars] message on [chars], error: [chars]
Explanation The ethernet driver failed to process a bundle IIR notification message. Further it is not
able to propagate the message back to the virtual interface owner, and hence it is possible that the
driver is out of step with the bundle configuration.
Recommended Action Recovery will be attempted automatically. If this error message is seen
repeatedly, restart the driver process that is generating the message and it will automatically recover.
If the message recurs, copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-ETHERNET-4-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-694
OL-23348-01
Layer 2 Messages
ETHERNET Messages
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
addresses for MAC accounting
Interface [chars]%s[chars]%s, [chars]
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-695
Layer 2 Messages
FB_PLIM Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-696
OL-23348-01
Layer 2 Messages
FB_SHIM_ENCAP Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-697
Layer 2 Messages
FIB_IPV4 Messages
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-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-698
OL-23348-01
Layer 2 Messages
FIB_IPV4 Messages
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_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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-699
Layer 2 Messages
FIB_IPV4 Messages
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-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-700
OL-23348-01
Layer 2 Messages
FIB_IPV4 Messages
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-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-701
Layer 2 Messages
FIB_IPV6 Messages
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-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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-702
OL-23348-01
Layer 2 Messages
FIB_IPV6 Messages
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_INFO_VERBOSE
[chars] [chars] [chars] [dec]
Explanation Platform IPv6 FIB, error information
Recommended Action *SUPPORT*
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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-703
Layer 2 Messages
FIB_IPV6 Messages
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-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 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-704
OL-23348-01
Layer 2 Messages
FIB_MPLS Messages
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-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.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-705
Layer 2 Messages
FR_EDM Messages
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.
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 -Recommended Action Copy the error message exactly as it appears on 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-706
OL-23348-01
Layer 2 Messages
FR_INARP Messages
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
[chars]
unable to apply class [chars] to interface [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-707
Layer 2 Messages
FR_INARP Messages
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
[chars].[dec]: [chars]
unable to apply class [chars] to interface
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-708
OL-23348-01
Layer 2 Messages
FR_LMI Messages
Error Message
%L2-FR_INARP-4-UNKNOWN_INTFTYPE
[dec]
received an event for an unknown interface type:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-709
Layer 2 Messages
FR_LMI Messages
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
Interface [chars]
FSM in STOPPED state while timer is running:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-710
OL-23348-01
Layer 2 Messages
FR_LMI Messages
Error Message
%L2-FR_LMI-3-INVALID_VC An error occurred 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
state: [chars]
An error occurred informing the VC Manager of the line
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-711
Layer 2 Messages
FR_LMI Messages
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
the VC Manager: [chars]
An error occurred sending the updated VC states to
Explanation The VC Manager returned an error after receiving 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-712
OL-23348-01
Layer 2 Messages
FR_NETIO Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-713
Layer 2 Messages
FR_SOCKET Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-714
OL-23348-01
Layer 2 Messages
FR_SOCKET Messages
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
[chars]
Failed to setup fr socket as a resource manager:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-715
Layer 2 Messages
FR_UV Messages
FR_UV Messages
Error Message
%L2-FR_UV-3-ERR_ABORT_ENCAP_FAIL
be in an inconsistent state.
[dec] encap aborts failed: The system may now
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 inconsistent
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) occurred 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-716
OL-23348-01
Layer 2 Messages
FR_VCM_EA Messages
Error Message
%L2-FR_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-FR_UV-3-SYSMGR
[chars]
Failure communicating readiness to System Manager. Error:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-717
Layer 2 Messages
FR_VCM_EA Messages
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
collection, err: [chars]
Failed to initialize FR VCM subinterface stats
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-718
OL-23348-01
Layer 2 Messages
FR_VCM Messages
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
[chars]: [chars]
Unable to specify [chars] encaps type for interface
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-719
Layer 2 Messages
FR_VCM Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-720
OL-23348-01
Layer 2 Messages
FR_VCM Messages
Error Message
%L2-FR_VCM-3-PTP_VC
one PVC is allowed
FR PVC create (dlci [dec]) on PTP subinterface failed - only
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-721
Layer 2 Messages
FRMIB Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-722
OL-23348-01
Layer 2 Messages
FSYNC Messages
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
[chars]: [chars]
Failed to re-arm the ESMC SSM receive timer for
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
point [chars]: [chars]
Failed to program the inputs for selection
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-723
Layer 2 Messages
FSYNC Messages
Error Message
%L2-FSYNC-4-INTF_IM_ERROR
[chars]
Interface manager failed to [chars] for [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
[chars]: [chars]
Failed to handle interface status change for
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
[chars]: [chars]
Failed to handle selection update for selection point
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-724
OL-23348-01
Layer 2 Messages
FSYNC Messages
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 safely. 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-725
Layer 2 Messages
FWD_EDGE_COMMON Messages
Error Message
%L2-FSYNC-6-SELECTION_FALLBACK
synchronized: [chars]
Selection point [chars] is no longer externally
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
[chars]
adj engine layer internal error [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_ERR
[chars]
adj engine layer internal error [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
--
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-726
OL-23348-01
Layer 2 Messages
G709 Messages
Error Message
%L2-FWD_EDGE_COMMON-3-EDGE_IP_ERR
[chars]
fib ip engine layer internal error [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.
Error Message
%L2-FWD_EDGE_COMMON-3-EDGE_IP_ERR
[chars]
fib ip engine layer internal error [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-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-727
Layer 2 Messages
GATM Messages
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.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-728
OL-23348-01
Layer 2 Messages
GDO Messages
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*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-729
Layer 2 Messages
GE_ASIC_PRP3 Messages
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 management 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 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 management 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 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 management 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 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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-730
OL-23348-01
Layer 2 Messages
GE Messages
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
[chars]/[chars]
PRP Gigabit Ethernet execution agent initialization failed.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-731
Layer 2 Messages
GSR_edge_fwd_lib Messages
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 forwarding 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.
Recommended Action
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-732
OL-23348-01
Layer 2 Messages
GSR Messages
Error Message
%L2-GSR-3-ERR_THREAD_CREATE
[chars]
Internal OS call to create additional threads failed,
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
[chars]
Internal OS call to create additional threads failed,
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-733
Layer 2 Messages
GSR Messages
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 checkpoint info does not exist.
The driver is coming up in restart mode, but
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-734
OL-23348-01
Layer 2 Messages
GSR Messages
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 indicates 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-735
Layer 2 Messages
GSR Messages
Error Message
%L2-GSR-3-FIA_STARTUP_DATA
structure
([chars]), Illegal size of input for FIA startup 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_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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-736
OL-23348-01
Layer 2 Messages
GSR Messages
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 indicates 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.’
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-737
Layer 2 Messages
GSR Messages
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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-738
OL-23348-01
Layer 2 Messages
GSR Messages
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]
[chars] failed, slot equals [dec], error info equals
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
stats
pcds_get_timestamp failed for fishstick
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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-739
Layer 2 Messages
GT64115 Messages
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 configuration %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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-740
OL-23348-01
Layer 2 Messages
gulf Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-741
Layer 2 Messages
HALE_MQS Messages
Error Message
%L2-gulf-7-DEBUG_MSG
Debug: [chars]: [chars]: [dec]
Explanation This is a debug message in the gulf driver 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.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-742
OL-23348-01
Layer 2 Messages
HALE_REPLICORD Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-743
Layer 2 Messages
HALE_TLU Messages
Error Message
%L2-HALE_TCAM-3-ERROR
[chars]: [chars]
Explanation A SW exception occurred in TCAM extension Library
Recommended Action If TCAM memory is the issue, reduce other system activity to ease memory
demands. If conditions warrant and minimum memory requirements not met, upgrade to a larger
memory configuration.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-744
OL-23348-01
Layer 2 Messages
HFA_LIB Messages
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
error: [hex] [chars]
hfa: blwm client configuration failed,
Explanation Unable to configure BLWM client functionality. Will not be able to send any BLWM
messages 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
[hex] [chars]
hfa: blwm client rebind failed, error:
Explanation Unable to rebind with BLWM client functionality after a connection reconnect. Will not
be able to send any BLWM messages from HFA.
Recommended Action Please collect the logs mentioned in the required_info and contact support
team.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-745
Layer 2 Messages
HFA_LIB Messages
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
batched request, reply code: [dec]
hfa: Received a failure reply code for a
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
send, errno: [chars]
hfa: msg: [dec], retried: [dec] time(s), failed to
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-746
OL-23348-01
Layer 2 Messages
if_discovery Messages
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 hardware 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 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-747
Layer 2 Messages
IGMPSN_POLICY Messages
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
[chars] because [chars]
Could not apply policy operation [chars] to attribute
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-748
OL-23348-01
Layer 2 Messages
IGMPSN Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-749
Layer 2 Messages
IOB Messages
Error Message
%L2-IGMPSN-5-DP_CONGESTION_CLEAR
congestion cleared
Layer 2 multicast data plane programming
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.
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 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*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-750
OL-23348-01
Layer 2 Messages
IPV6_EA Messages
Error Message
%L2-IPV6_EA-3-INIT
Failed to initialize [chars], because of [chars]
Explanation Initialization process such as getting an evm failed.
Recommended Action sysmgr will retry to start the ipv6_ea. If not recovered, it’s a fatal condition. If
the message recurs, copy the error message exactly as it appears on the console or in the system log,
call your Cisco technical support representative and provide the representative with the gathered
information. *REDUCE*
Error Message
%L2-IPV6_EA-3-NOMEM
IPv6 EA failed to program ’[chars]’ due to low memory
Explanation The IPv6 EA process could not allocate memory needed to program some IPv6 feature.
Recommended Action Check memory status.
Error Message
%L2-IPV6_EA-3-PLAT_UPD_FAILED
Platform update failed: [chars] - [chars](CH[hex])
Explanation Platform update failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-IPV6_EA-3-PLAT_UPD_FAILED_GL
[chars] - [chars]
Platform update failed for [dec] interface:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-751
Layer 2 Messages
IXP2800_FWD Messages
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
([chars])
Test DLL failed to open log file [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 occurred
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 acquire the required amount of memory.’
Recommended Action *REDUCE*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-752
OL-23348-01
Layer 2 Messages
IXP2800_SERVICE Messages
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
[chars] ([chars])
ixp2800 HW driver DLL failed to open log file
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 acquire the required amount of memory.’
Recommended Action *REDUCE*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-753
Layer 2 Messages
IXP2800_SERVICE Messages
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
[chars] ([chars])
ixp2800 service DLL failed to open log file
Explanation The NPU service DLL failed to open the log file
Recommended Action None
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-754
OL-23348-01
Layer 2 Messages
JACKET Messages
JACKET Messages
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 initialize CPU Ctrl: err [chars]
Explanation Unable to initialize CPU Ctrl device.
Recommended Action Report this error.
Error Message
%L2-JACKET-3-CPU_CTRL_INTS
[chars]
Failed to [chars] CPU Ctrl register id [dec]: err
Explanation Unable to enable/disable/clear a CPU Ctrl interrupt register.
Recommended Action Report this error.
Error Message
%L2-JACKET-3-CPU_CTRL_REG_ACCESS
err [chars]
Failed to [chars] CPU Ctrl register id [dec]:
Explanation Unable to read/write to a CPU Ctrl register.
Recommended Action Report this error.
Error Message
%L2-JACKET-3-CPU_CTRL_REG_LOCK
[chars]
Failed to enable CPU Ctrl register lock: err
Explanation Unable to obtain register access lock for CPU Ctrl.
Recommended Action Report this error.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-755
Layer 2 Messages
JACKET Messages
Error Message
%L2-JACKET-3-CRITICAL_ERROR
[chars]: [chars]: [hex]
Explanation A critical error occurred in jacket driver which involves exiting the process. The jacket
driver will restart and unless the same error occurs on the next attempt the driver will function
normally. If the error is persistent, it indicates the system error or HW error which needs further
investigation.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-JACKET-3-ERROR
[chars]
Explanation SPA THOR Jacket error
Recommended Action When errors occur in jacket, it is very likely the 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 occurred
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-756
OL-23348-01
Layer 2 Messages
JACKET Messages
Error Message
%L2-JACKET-3-RULES_CRITICAL_ERROR
SPA subslot [dec]: FAILED: [chars] for [chars]
Explanation A critical error occurred in jacket driver rules validation for a SPA which results in the
SPA not being enabled. This does not affect the other slots on the jacket card. Please check the SW
support for the SPA slot for which this message is seen.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-JACKET-3-SPA_DISABLE
[dec] requests to disable SPA [dec] due to spa bus error
Explanation This is an error message indicating a Hardware access error for a SPA and disable the
SPA to avoid LC reload
Recommended Action No action is required.
Error Message
%L2-JACKET-3-SPA_PIO_ERROR SPA subslot [dec]: had [chars] error when accessing
address [hex] with fault code [dec]
Explanation This is an error message indicating a Hardware access error for a SPA. If this is a
recurrent message, it usually is due to faulty hardware, loose connection at the SPA connector on
the jacket card. Try reseating the SPA and see if the issue is resolved. If not, please check with TAC.
Recommended Action No action is required.
Error Message
%L2-JACKET-3-SPA_SELF_DESTRUCT
spa bus error
[chars] has requested to disable SPA [dec] due to
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 encountered 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-757
Layer 2 Messages
JACKET Messages
Error Message
%L2-JACKET-3-SPABRG_INIT
SPA QFP Bridge [dec] init failed: [chars]
Explanation SPAQFP Bridge has encountered an error during initialization
Recommended Action Report Error
Error Message
%L2-JACKET-4-QFP_ERROR_BRIDGE_BIND
controller server: [chars]
Failed to bind to the QFP SPA bridge
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
client library: [chars]
Failed to bind to the QFP generic interface
Explanation Failed to bind to the QFP Generic Interface Client
Recommended Action Report this error
Error Message
%L2-JACKET-4-QFP_ERROR_HA_ACK
availability server: [chars]
Failed to acknowledge a requested from the QFP high
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
server: [chars]
Failed to bind to the QFP high availability
Explanation Failed to bind with the QFP high availability infrastructure
Recommended Action Report this error
Error Message
%L2-JACKET-4-QFP_ERROR_MEM_ALLOC
’[chars]’
Failed to allocate [unsigned int] bytes for
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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-758
OL-23348-01
Layer 2 Messages
JACKET Messages
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
controller: [chars]
Failed to configure the SPA bridge
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
bridge controller [unsigned int]: [chars]
Failed to notify the QFP about SPA
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
[unsigned int]: [chars]
Failed to remove SPA bridge controller
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
from bay [unsigned int]: [chars]
Failed to inform QFP about [chars] of SPA
Explanation Failed to propagate information about SPA insertion or removal
Recommended Action Report this error
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-759
Layer 2 Messages
JACKET Messages
Error Message
%L2-JACKET-4-QFP_ERROR_SPA_UPDATE_NULL_BAY
SPA [chars]
Invalid internal structure for bay on
Explanation -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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-760
OL-23348-01
Layer 2 Messages
JACKET Messages
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 anomalies 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 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-761
Layer 2 Messages
JDAM Messages
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 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.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-762
OL-23348-01
Layer 2 Messages
L2FIB_DEBUG Messages
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 persistent 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-763
Layer 2 Messages
L2FIB_LIB Messages
L2FIB_LIB Messages
Error Message
%L2-L2FIB_LIB-2-OOR L2FIB has run out of [chars] resource memory. No more updates
will be handled by the L2FIB. Please delete ACs to resume normal operation on this
node
Explanation The l2fib_mgr process on the node has detected an out of resource condition for the
indicated resource. Normal operation cannot resume until routes are deleted.
Recommended Action Run show l2vpn forwarding resource command and check which resource(s)
are running low on memory. Significant ACs will have to be deleted on the affected node to resume
normal l2fib operation.
Error Message
%L2-L2FIB_LIB-3-ERR
[chars]
Explanation Some error occurred in operations related to L2FIB API area. The text of the message
displays the failed operation and the related error code. The traceback can be used to get the
function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-L2FIB_LIB-3-SHM_ERR
[chars] failed: [chars]
Explanation Some error occurred in operations related to Shared Memory area. The text of the
message displays the failed operation and the related error code. The traceback can be used to get
the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-L2FIB_LIB-4-RSRC_LOW L2FIB running low on [chars] resource memory. L2FIB will
now begin resource constrained forwarding. Only route deletes will be handled in
this state, which may result in mismatch between L2VPN mgr/AIB/L2FIB and L2FIB.
Traffic loss on certain ACs can be expected. The L2FIB will automatically resume
normal operation, once the resource utilization returns to normal level
Explanation The l2fib_mgr process has detected that average utilization for specified resource has
risen above a predefined high watermark value, and has entered resource constrained forwarding
mode. In this mode, the l2fib will only handle route deletes which may potentially free up some
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-764
OL-23348-01
Layer 2 Messages
L2FIB_SHM Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-765
Layer 2 Messages
L2FIB Messages
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
[unsigned int]
L2FIB thread [chars] received an invalid message: [chars]
Explanation L2FIB thread got an invalid message so it is exiting
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-L2FIB-2-SHM_INIT
L2FIB shared memory initialization failed: [chars]
Explanation Initialization of L2FIB failed. The traceback can be used to get the function/line number
of error generating code.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-L2FIB-3-SHM_ERR
[chars] failed: [chars]
Explanation Some error occurred in operations related to Shared Memory area. The text of the
message displays the failed operation and the related error code. The traceback can be used to get
the function/line number of error generating code.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-766
OL-23348-01
Layer 2 Messages
L2FIB Messages
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-MAC_TABLE_RESYNC_COMPLETE
table is complete [chars]
The resynchronization of the MAC address
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-GEN_INFO_CERR
[chars]: [chars]
Explanation An internal software error occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-L2FIB-6-GEN_INFO_ERR
[chars]
Explanation An internal software error occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-L2FIB-6-XC_MOD
XC/BP delete-and-create: [chars]
Explanation The L2VPN provision message is handled by deleting old XC/BP, and creating a new
one.
Recommended Action None.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-767
Layer 2 Messages
L2TP Messages
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-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.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-768
OL-23348-01
Layer 2 Messages
L2VPN_PW Messages
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
[chars]
Pseudowire with address [chars], id [chars], state is
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-6-STANDBY
standby
Pseudowire with address [chars], id [chars], state is
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
is standby ready
Pseudowire with address [chars], id [chars], state
Explanation The L2VPN Pseudowire became standby ready.
Recommended Action If the state change was unexpected, confirm the configuration settings for the
cross-connect.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-769
Layer 2 Messages
L2VPN Messages
L2VPN Messages
Error Message
%L2-L2VPN-2-CRIT_MEM_SHUT
state.
[chars] process shutting down due to ’Critical’ memory
Explanation The system has notified a process that it is critically short of memory and the process is
shutting down.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-L2VPN-2-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 unconfigure ’l2vpn logging vfi
status’.
Error Message
%L2-L2VPN-3-BAG_REG_ERR
bag(s) registration failed: [chars]
Explanation Some error occurred 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 occurred 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-770
OL-23348-01
Layer 2 Messages
L2VPN Messages
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 occurred 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 occurred 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-771
Layer 2 Messages
L2VPN Messages
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
of [dec]
[chars] mtu of [dec] does not match bridge mtu
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 pseudowire 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-772
OL-23348-01
Layer 2 Messages
L2VPN Messages
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-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-773
Layer 2 Messages
L2VPN Messages
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 unconfigure ’l2vpn logging
bridge-domain status’.
Error Message
%L2-L2VPN-5-NO_LICENSE
[chars]
L2VPN AC manager could not get a license for node [chars],
Explanation License is required for L2VPN feature to work, but AC manager could not get a license
for the node from License manager.
Recommended Action Install license for the feature.
Error Message
%L2-L2VPN-6-BRIDGE_MTU_MISMATCH_CLEAR
[chars] mtu of [dec] now matches bridge mtu
Explanation The interface MTU now matches the bridge payload MTU.
Recommended Action No particular action is required.
Error Message
%L2-L2VPN-6-ENCAP_REMOVED_PW_CLEAR
resolved for pw-class ’[chars]’
Unresolved pseudowire encapsulation has been
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-774
OL-23348-01
Layer 2 Messages
L2VPN Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-775
Layer 2 Messages
LACP_LITE Messages
LACP_LITE Messages
Error Message
%L2-LACP_LITE-3-ERR_LL_DLL_ASYNC_SEND_FAIL
fails; Error [chars]
Send async pulse to lacp lite process
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
process; Error [chars]
Cannot connect to lacp lite
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
[chars]
Cannot open shmem file [chars]; Error
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-776
OL-23348-01
Layer 2 Messages
LC Messages
Error Message
%L2-LACP_LITE-3-ERR_SHMEM_TRNC_FAIL
Error [chars]
Cannot truncate file [chars] to [dec] bytes;
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
records (request for [dec] records)
LACP lite SHMEM can accommodate only [dec]
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
flag (request for [dec])
LACP lite API is called with unsupported
Explanation BM-Local has called LACP lite API with unsupported flag
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Issue the show tech-support command to gather data that may provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text
or from the show tech-support output, call your Cisco technical support representative and provide
the representative with the gathered information.
LC Messages
Error Message
%L2-LC-0-TESTEMERG
[chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-777
Layer 2 Messages
LC Messages
Error Message
%L2-LC-1-TESTALERT
[chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message
%L2-LC-2-TESTCRIT
[chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message
%L2-LC-3-BMA_CHKPT
Call to [chars] failed, chkpt_status equals [hex]
Explanation The library call failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-LC-3-BMA_CHKPT_NOINIT
Error initializing checkpointing table.
Explanation The driver was not able to initialize a table to store checkpointed data.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-LC-3-BMA_CHKPT_NORESTORE
checkpointed data.
The driver was not able to restore ’[chars]’ from
Explanation No checkpointing record was found in the table.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-778
OL-23348-01
Layer 2 Messages
LC Messages
Error Message
%L2-LC-3-BMA_CHKPT_NOSAVE
checkpointed data.
The driver was not able to save ’[chars]’ in
Explanation BMA buffer carve information could not be saved in the checkpoint record.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-LC-3-BMA_CHKPT_RECOVERY_NODATA The driver is coming up in RECOVERY_MODE, but
the checkpoint info does not exist.
Explanation When a driver comes up in RECOVERY_MODE, checkpointing data should have
already been saved to the checkpointing record by the previous life of the driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-LC-3-BMA_DI_INVALID_MODE
DI started the driver in an invalid mode: [hex]
Explanation The Driver Infrastructure (DI) started the driver in an invalid or unsupported mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-LC-3-BMA48ERR [chars] BMA error: stat_reg [hex] adr [hex] data [hex] qm [hex]
plim [hex] l3 [hex] ms [hex] sdram [hex]
Explanation There is an error in the BMA (reg. information).
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-BMA48ERRS
[chars] BMA48 [chars] error [hex]
Explanation There is an error in the BMA48.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-779
Layer 2 Messages
LC Messages
Error Message
%L2-LC-3-BMA48FIM [chars] BMA48 [chars] error fim_cf_status [hex]; fim_df0: adr
[hex] data [hex]; fim_df1: adr [hex] data [hex]; fim_df2: adr [hex] data [hex];
fim_df3: adr [hex] data [hex]
Explanation There is an error in the BMA.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-BMABUFF [chars] BMA has [unsigned int] buffers in queue [unsigned int]
when maximum of [unsigned int] are allowed
Explanation Number of buffers in one of the BMA queues has overflowed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-BMACMDFTCH
BMA
Problem in BMA command fetching, status equals [dec] [chars]
Explanation The BMA encountered problems while trying to fetch the given command. If appears
more than once we may have a HW problem. The GRP should recognize a lost of communication
with the LC and reload it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-BMACMDLOST
[chars] BMA has lost a command
Explanation The given BMA has lost a command. If appears more than once we may have a HW
problem. The GRP should recognize a lost of communication with the LC and reload it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-BMACMDRPLY Problem in BMA reply to command type [dec] [chars] BMA
sequence no equals [dec]
Explanation There was a problem in the reply to the given BMA command. If appears more than once
we may have a HW problem. The GRP should recognize a lost of communication with the LC and
reload it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-780
OL-23348-01
Layer 2 Messages
LC Messages
Error Message
%L2-LC-3-BMAERR [chars] error: msstat [hex] dma0 [hex] dma1 [hex] dma2 [hex] qm
[hex] plim [hex] fia [hex] l3 [hex] ms [hex] sdram [hex]
Explanation There is an error in the BMA (reg. information).
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-BMAERRS
[chars] [chars] error [hex]
Explanation There is an error in the BMA.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-BMAERRSS
[chars] [chars] error [hex] [chars] [hex]
Explanation There is an error in the BMA.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-BMAMEM
[chars] SDRAM data error [hex] in address [hex]
Explanation Packet memory parity error. Each bit (0-15) set in data error word represents a parity
error in one byte of the errored location in memory. Bits 16 and 17 of data error word, if either is
set, indicate the error happened during CPU access to the packet memory, otherwise it is during
normal operation. Address represents the offset of the memory location being accessed from the
beginning of packet memory on the side mentioned (to or from fabric.) This error indicates a
possibly temporary problem in either the packet memory device or the BMA.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-781
Layer 2 Messages
LC Messages
Error Message
%L2-LC-3-BMASDRAM_BADCAS_LATENCY
got [hex]
[chars] DIMMs do not support CAS latency needed.
Explanation SDRAM DIMM modules installed in BMA SDRAM DIMM sockets do not support
CAS latency needed. CAS latency is specified in the DIMM EEPROM as a number. When converted
to a binary number, each bit corresponds to one CAS latency. Bit 2 must be set to 1, indicating that
a CAS latency of 3 is supported.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-BMASDRAM_BADSIZE [chars] DIMMs are of unsupported size. Read this: rows
[dec], cols [dec], DIMM banks [dec], SDRAM Device banks [dec]
Explanation SDRAM DIMM modules installed in BMA SDRAM DIMM sockets are of unsupported
size.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-BMASDRAM_BADWIDTH
[dec], got [dec]
[chars] DIMMs have unsupported data width, expected
Explanation SDRAM DIMM modules installed in BMA SDRAM DIMM sockets have unsupported
data width.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-BMASDRAM_NOTMATCH
[chars] SDRAM DIMMs do not match
Explanation SDRAM DIMM modules installed in to Fabric or from Fabric BMA DIMM0 and
DIMM1 sockets do not match. While the DIMMs on one side (to Fabric) could be different from the
DIMMs on the other side (from Fabric), the two DIMMs on the same side have to be identical. Also,
all four DIMMs need to be mounted and making proper contact.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-782
OL-23348-01
Layer 2 Messages
LC Messages
Error Message
%L2-LC-3-BMAUCODE_GET [chars] BMA: feature [chars], line card type [chars], could
not get [chars] BMA microcode
Explanation For the BMA microcode download command, failed to get the given BMA microcode
bundled in the image.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-BMAUCODE_LCTYPE [chars] BMA: feature [chars], specified linecard
type(s) ([hex]) ! equals current ([hex])
Explanation For the BMA microcode download command, there was a mismatch between what was
specified in the BMA microcode file and the current type of line card
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-BMAUCODE_NULL
--
Explanation -Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-CARVE_BUFHDRS
[chars] BMA: out of SDRAM buffer headers
Explanation Ran out of available SDRAM buffer headers while attempting to carve buffers. This
could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-CARVE_BUFSIZE [chars] BMA: illegal specified/real SDRAM buffer size(s)
equals ([unsigned long int],[unsigned long int]). Range equals ([dec],[dec])
Explanation The calculated SDRAM buffer size (in bytes and including header and data portions), is
not within the given range. This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-783
Layer 2 Messages
LC Messages
Error Message
%L2-LC-3-CARVE_EXBUFS
int])
[chars] BMA: [unsigned int] SDRAM buffers max ([unsigned
Explanation The maximum number of SDRAM buffer headers is limited to a maximum number
which has been exceeded. This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-CARVE_EXFREEQS
int])
[chars] BMA: [unsigned int] free queues max ([unsigned
Explanation Number of free queues allowed for SDRAM buffer carving has been exceeded. This
could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-CARVE_EXPCT
[chars] BMA: [unsigned int] sum SDRAM buffer percentages 100
Explanation The sum of percentages per SDRAM buffer size has exceeded 100. This could be a
cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-CARVE_EXSDRAM [chars] BMA: used SDRAM ([unsigned long long int] bytes)
available for carve ([unsigned long int] bytes)
Explanation The calculated sum of SDRAM to be carved is larger than the available SDRAM for
carving. This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-CARVE_NOFREEQS
[chars] BMA: no more free queues
Explanation There are no more available free queues which can be used for SDRAM buffer carve.
This could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-784
OL-23348-01
Layer 2 Messages
LC Messages
Error Message
%L2-LC-3-CARVE_PARMS
0
[chars] BMA: equals 1 SDRAM bufmem parameters equals equals
Explanation This is an internal parameter error with one or more SDRAM buffer memory
parameters: maximum buffer header count or SDRAM sizes (total, not available for carve, and
available for carve
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-CARVE_QELEM
([unsigned int])
[chars] BMA: [unsigned int] Queue Manager SRAM elements max
Explanation Ran out of Queue Manager elements, which are used for SDRAM buffer carving. This
could be a cause of SDRAM buffer carve failure.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-CARVE_QMREAD
BMA address [hex]: Queue Manager SRAM [hex], read error(s)
Explanation This happened during Queue Manager SRAM initialization. Reading one or more
zeroed Queue Manager SRAM locations gave a non-zero result. Possible errors are in head, tail,
length, length threshold, buffer address, next queue element, or scratch RAM locations.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-DOWNREV
BMA is an old version.
Explanation The system software detected an old version of the BMA.
Recommended Action Call your technical support for an upgraded version.
Error Message
%L2-LC-3-IICDEV_NOTACKADDR
IIC Device [dec] failed to ack address
Explanation BMA SDRAM DIMM failed to acknowledge address. This is an SDRAM IIC bus
protocol error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-785
Layer 2 Messages
LC Messages
Error Message
%L2-LC-3-IICDEV_NOTACKREAD
IIC Device [dec] failed to ack read command
Explanation BMA SDRAM DIMM failed to acknowledge read command. This is an SDRAM IIC
bus protocol error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-IICDEV_NOTRESPOND
IIC Device [dec] does not respond, perhaps absent
Explanation BMA SDRAM DIMM does not respond, perhaps absent.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-INIT_CARD_TYPE
Unknown card type ([hex])
Explanation A card was either manufactured improperly, has failed, or is newer than the software
Recommended Action Replace the card or upgrade the software
Error Message
%L2-LC-3-INIT_MEM
Memory failure, addr [hex], read [hex]%08x, not [hex]%08x
Explanation Initialization of the memory address failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-INIT_READ
Error reading memory at [hex]
Explanation Failed to read the given memory location.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-INIT_RESET
Failed to take line card out of reset
Explanation Initialization of the line card IO registers failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-786
OL-23348-01
Layer 2 Messages
LC Messages
Error Message
%L2-LC-3-INIT_ZERO
No bytes to write to location [hex]
Explanation No bytes were written to the given location.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-INVQ
Invalid local output queue: [hex] [hex] [hex] [hex] [hex] [hex]
Explanation The above packet was routed to an invalid queue. The data shown is the packet header.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-L3FEERR L3FE error: rxbma [hex] addr [hex] txbma [hex] addr [hex] dram
[hex] addr [hex] io [hex] addr [hex]
Explanation There was an error in the line card’s L3FE ASIC (reg. information).
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-L3FEERRS
L3FE [chars] error [hex] address [hex]
Explanation There was an error in the line card’s L3FE ASIC.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-LC_CODE_DLD_ALLOC
Failed buffer allocation for code download
Explanation Could not allocate a data buffer to contain contents of the given linecard downloaded
file. There may be insufficient DRAM.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-787
Layer 2 Messages
LC Messages
Error Message
%L2-LC-3-LC_CODE_DLD_CHKSUM
code download IPC data checksum error
Explanation For the GLC code download command, failed the checksum verification.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-LC_CODE_PROG
no downloaded code to program
Explanation For the GLC code program command, no downloaded code to program.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-LOOKUP_ERROR
Hardware assist lookup error [hex] in memory encountered
Explanation Memory corruption detected.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-MACSTR
string
Adj/midb ([chars]) has incorrect high word ([hex]) in its mac
Explanation The line card CEF/MDS received an adjacency/midb with the incorrect mac rewrite
string. Packets forwarded to that adjacency/midb will be dropped.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-3-OUTINFO
equals [dec]
Adj/midb([chars]): incorrect output_info equals [hex] maclen
Explanation The line card CEF/MDS received an adjacency/midb with the incorrect output_info
field. Packets forwarded to that adjacency/midb will be dropped.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-788
OL-23348-01
Layer 2 Messages
LC Messages
Error Message
%L2-LC-3-PARITYERRTTM48
Parity error in memory encountered
Explanation One bit memory corruption detected.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-SELECTOR
[dec]: unknown BMA selector value
Explanation An unknown BMA selector value was encountered.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative
Error Message
%L2-LC-3-TESTERR
[chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message
%L2-LC-4-CARVE_JVMASK
quiesce-for-carve
[chars] BMA: suspect return value [dec] on
Explanation The BMA quiesce-for-carve algorithm retrieved a bad jump vector mask return value.
This could indicate an error in the quiesce.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Error Message
%L2-LC-4-CARVE_TIME [chars] BMA: quiesce-for-carve exceeded timeout ([dec] ms)
in [chars] loop, [dec] times
Explanation The BMA quiesce-for-carve algorithm waits an allotted time for line card queues to
flush. One or more waits exceeded this allotted time. These queues are specific to the line card’s
ASICs. This error message might not actually indicate an error - the allotted time might not be
sufficient and should be increased.
Recommended Action Copy the error message exactly as it appears, and report it to your technical
support representative.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-789
Layer 2 Messages
MARVEL Messages
Error Message
%L2-LC-4-TESTWARNING
[chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message
%L2-LC-5-TESTNOTICE
[chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message
%L2-LC-6-TESTINFO
[chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
Error Message
%L2-LC-7-TESTDEBUG
[chars]
Explanation Test message for software test.
Recommended Action Stop typing LC test logger.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-790
OL-23348-01
Layer 2 Messages
MARVEL Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-791
Layer 2 Messages
METRO_STATS_API Messages
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 -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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-792
OL-23348-01
Layer 2 Messages
METRO_STATS Messages
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
[dec] [chars] [dec] [chars] [chars]
Stats Counters Exhausted Msg : [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
[chars] [dec] [chars] [dec]
Stats Exhausted: [chars] [chars] [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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-793
Layer 2 Messages
MFR_EA_LTRACE_DLL Messages
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
error traces: [chars]
ltrace initialization operation failed for
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-794
OL-23348-01
Layer 2 Messages
MFR_EA Messages
Error Message
%L2-MFR_EA_LTRACE-3-EVENT_INIT_FAIL
events: [chars]
ltrace initialization operation failed for
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
for internal traces: [chars]
ltrace initialization operation failed
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-795
Layer 2 Messages
MFR_EA Messages
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
ifhandle [hex] err: [chars]
Interface [chars] operation failed for
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-796
OL-23348-01
Layer 2 Messages
MFR_EA Messages
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
[chars]
Failed during encaps remove, err:
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
information, err: [chars]
Failed to collect member link
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-797
Layer 2 Messages
MFR_MA Messages
Error Message
%L2-MFR_EA-3-NO_STATS
[chars]
Failed to initialize MFR interface stats collection, err:
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
[chars]
Failed during interface state change, err:
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-798
OL-23348-01
Layer 2 Messages
MFR_MA Messages
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
group [dec]
Cannot add [chars] to bundle with nodeid [hex] and
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-799
Layer 2 Messages
MFR_MA Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-800
OL-23348-01
Layer 2 Messages
MFR_MA Messages
Error Message
%L2-MFR_MA-4-ERR_CHKPT_DUPLICATE
[chars]
Duplicate [chars] checkpoint record found for
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*.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-801
Layer 2 Messages
MICKEY Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-802
OL-23348-01
Layer 2 Messages
MLCTRLR Messages
Error Message
%L2-MLCTRLR-3-ERROR
[chars]([dec]): [chars] failed ([chars]) - [chars]
Explanation A general failure occurred 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 occurred 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-803
Layer 2 Messages
MMSMLIB Messages
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*
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-804
OL-23348-01
Layer 2 Messages
MOUSE Messages
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 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.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-805
Layer 2 Messages
MRP_MAD Messages
MRP_MAD Messages
Error Message
%L2-MRP_MAD-3-INVALID_MRPDU
decoded. Stage: [chars]
CH[hex]: Received an MRPDU which could not be
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
MRP could not recover
A memory allocation failure has occurred from which
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
inconstent 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-806
OL-23348-01
Layer 2 Messages
Multilink Messages
Error Message
%L2-MULTILINK_UV-3-EVENT
Unrecoverable error in event loop. Error: [chars]
Explanation An error (other than EINTR) occurred 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
Error: [chars]
Failure communicating readiness to System Manager.
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
ifh [hex] with bandwidth [dec]
Bundle [chars] with bandwidth [dec]. Link
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-807
Layer 2 Messages
MVRP Messages
Error Message
%L2-Multilink-3-ML_GROUP_FAILURE
multilink bundle [chars]
Failed to add/remove serial link [chars] into
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
process: [chars]
Failed to initialize [chars] in [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-808
OL-23348-01
Layer 2 Messages
ND Messages
Error Message
%L2-MVRP-4-MAD_INIT_FAILED MVRP failed to reinitialize with the MAD following a
change in bridging configuration: [chars]
Explanation The MVRP IO process has failed to reinitialize with the MAD following a change in
bridging configuration. Periodic retries will occur to successfully reinitialize with the MAD. Until
the MAD is initialized 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-809
Layer 2 Messages
OAMMIB Messages
OAMMIB Messages
Error Message
%L2-OAMMIB-3-NO_DEBUG
will occur: [chars]
Unable to register for OAM MIB debug. No further debugging
Explanation In the initialisation 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 initialisation there is another attempt register for
debugging.
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 initialisation of the OAM 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 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-810
OL-23348-01
Layer 2 Messages
OPTICS Messages
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 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.
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 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-811
Layer 2 Messages
PAL_CGM Messages
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 allocation 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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-812
OL-23348-01
Layer 2 Messages
PFILTER_EA Messages
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 occurred 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 occurred 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-813
Layer 2 Messages
PFILTER_EA Messages
Error Message
%L2-PFILTER_EA-3-INIT_ERROR
Process initialization failed: ([chars]%s)
Explanation The pfilter_ea process failed to initialize. This pfilter_ea process programs the ’packet
filter’ security access control list in the hardware. If the pfilter_ea process fails to initialize, the
access control list cannot be programmed into the hardware. %s - indicates the reason for the
initialization failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this
process, up to a fixed number of times when this error is encountered, to recover. Execute ’show
process pfilter_ea location 0/x/cpu0’ to verify that the process is up and running. If it is still
non-operational, try doing ’process restart pfilter_ea location 0/x/cpu0’. Collect all debug
information if the process is continually restarting ’debug pfilter-ea all’ (during the process restart).
If the message recurs, copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PFILTER_EA-7-EVENT_ERROR
Event Failure: ([chars])
Explanation The pfilter_ea process received a bad event. This pfilter_ea process programs the
’packet filter’ security access control list in the hardware. %s - is the decoded error reason.
Recommended Action Monitor the event messages. The pfilter_ea process will handle the failure
gracefully but if they continually appear on the console, try doing ’process restart pfilter_ea location
0/x/cpu0’. If the message recurs, copy the error message exactly as it appears on the console or in
the system log, call your Cisco technical support representative and provide the representative with
the gathered information.
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
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-814
OL-23348-01
Layer 2 Messages
PFILTER_EA Messages
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 hardware. 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 hardware. 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*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-815
Layer 2 Messages
PLAOC768_API Messages
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
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.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-816
OL-23348-01
Layer 2 Messages
PLATFORM_ATM_OAM Messages
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 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.
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 continuously, 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-817
Layer 2 Messages
plim_4p_oc12 Messages
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-818
OL-23348-01
Layer 2 Messages
plim_4p_oc12 Messages
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 traffic 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 error 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-819
Layer 2 Messages
plim_4p_oc12 Messages
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
[dec]
Port failed to become available [chars]
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-820
OL-23348-01
Layer 2 Messages
plim_4p_oc12 Messages
Error Message
%L2-plim_4p_oc12-3-STATS_COLLECT_REGISTER_FAILED
registration error [chars] [chars]
Statistics collector
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-821
Layer 2 Messages
PLIM_4P_OC192 Messages
Error Message
%L2-plim_4p_oc12-3-TX_CLK_GET_INVALID_PORT_CTX
source
Failed to retrieve tx clock
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
source for sonet port
Failed to configure tx clock
Explanation Physical Layer Interface Module (PLIM) driver failed to make configure transmit clock
source for the sonet port. The sonet port hardware configuration is invalid and may result in traffic
being dropped or high error count on the port. This error may appear during attempt to configure
clock source for the sonet port.
Recommended Action Retry the sonet port configuration. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-plim_4p_oc12-4-INVALID_TIMER
Invalid timer [dec]
Explanation Physical Layer Interface Module (PLIM) driver received unknown timer event. %d -
timer type
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
PLIM_4P_OC192 Messages
Error Message
%L2-PLIM_4P_OC192-3-DEVICE_INTR_CLEAR
excessive interrupts
No Framer/RAC devices are generating
Explanation The previously reported excessive interrupts condition has been cleared. Interrupt rate
limiting has been disabled.
Recommended Action none
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-822
OL-23348-01
Layer 2 Messages
PLIM_4P_OC192 Messages
Error Message
%L2-PLIM_4P_OC192-3-DEVICE_INTR_DISABLE
device of port [hex]
Excessive interrupts from the [chars]
Explanation The specified device is generating excessive interrupts. This message indicates that we
are rate limiting the interrupt coming from this device. This indicates a potential HW issue, traffic
forwarding (protection switching) may be impacted.
Recommended Action Check the fiber or the peer connection. If the problem persist after checking
fiber and peer router, please contact support.
Error Message
%L2-PLIM_4P_OC192-3-DRV_INIT_ERR
rc equals [chars] ; exiting...
Initialization of PLIM driver failed: [chars] :
Explanation PLIM driver encountered the annunciated error during the driver initialization. The
System Manager process (sysmgr) will automatically respawn the (plim_4P_oc192) process, up to
a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will
trigger node reload. After a certain number of node reloads, the shelf manager will permanently
shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PLIM_4P_OC192-3-ERR
[chars]
Explanation fail to init debug service event manager fails to provide its service
Recommended Action sysmgr will respawn plim_4p_oc192 ’show logging’ to look for the errors from
event manager
Error Message
%L2-PLIM_4P_OC192-3-GENERIC_ERROR
Error: [chars] [chars] [hex]
Explanation The message is used to report generic errors.
Recommended Action Contact support.
Error Message
%L2-PLIM_4P_OC192-3-GET_NODEID_ERR
[chars] : rc equals [chars]
Explanation PLIM driver failed to obtain either its node ID or extract rack/slot/instance information
(having obtained the node ID).
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-823
Layer 2 Messages
PLIM_ASIC_API Messages
Error Message
%L2-PLIM_4P_OC192-3-MEM_ERR
[chars]
Explanation fail to allocate memory.
Recommended Action sysmgr would restart the process. show process memory to find out whether
there is potential memory leak show memory to confirm system memory goes low
PLIM_ASIC_API Messages
Error Message
%L2-PLIM_ASIC_API-7-ERR
[chars] Reason:[chars]
Explanation BAMBI API generated errors.
Recommended Action No action is required.
PLIM_ASIC Messages
Error Message
%L2-PLIM_ASIC-1-REQUEST_RELOAD_BOARD
from fault so reload is requested.
PLIM ASIC instance [dec] has not recovered
Explanation An ASIC error has occurred multiple times and has failed to recover despite power on
reset. The board has been requested to be reloaded in an attempt to clear the problem.
Recommended Action The output message is warning board reload request.
Error Message
%L2-PLIM_ASIC-2-EIO_TRAIN
PLASPA: [chars]
Explanation EIO training errors. The EIO link to the PLASPA failed to train. This will result in
traffic loss through this PLIM.
Recommended Action Check seating of both the PLIM and the MSC and then reload the MSC. If the
message recurs, copy the error message exactly as it appears on the console or in the system log, call
your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-824
OL-23348-01
Layer 2 Messages
PLIM_ASIC Messages
Error Message
%L2-PLIM_ASIC-3-ERR
[chars]
Explanation Plim asic driver errors. Typically these errors indicate failure in system services or bad
programming of the hardware.
Recommended Action Check whether process ’plaspa_server’ is up and running. Check if the linecard
reported any other errors and/or traffic loss was observed. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PLIM_ASIC-3-HEALTH_MONITOR_PON_RECOVERY
recovery for Beluga ASIC instance [dec]
Health Monitor Power On Reset
Explanation An Beluga SW error has occurred and requires pon-reset to recover. The Beluga ASIC
was in a Halt state for and extended period.
Recommended Action This informational message indicating that the required error recovery action
took place.
Error Message
%L2-PLIM_ASIC-3-HW_ERR
plaspa instance [dec] [chars], [chars]
Explanation Plim Asic errors. Typically these indicate errors detected by the ASIC. Too many of
these errors might indicate problem with the board, and can trigger a reload of the LC.
Recommended Action Check whether process ’plaspa_server’ is up and running. Check if the linecard
reported any other errors and/or traffic loss was observed. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PLIM_ASIC-3-LTRACE_INIT
Ltrace init for file [chars] failed [chars]
Explanation -Recommended Action Typically these indicate that ltrace is out of service. check at other processes
using ltrace and see whether the problem happens to them.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-825
Layer 2 Messages
PLIM_ASIC Messages
Error Message
%L2-PLIM_ASIC-3-PIO_ERROR A [chars] error occurred during PIO [chars] operation
on PLIM ASIC instance [dec] port [dec] at address [hex]_[hex]. Error detail:
[chars]. Software action: [chars].
Explanation The PIO operation on PLIM ASIC failed due to a hardware or software error. %s description of the error. %s - description of the operation. %d - PLIM ASIC instance number %d port number. %08x_%08x - address of the operation %s - description of the error details.
Recommended Action Check if the linecard reported any other errors and/or traffic loss was observed.
If the message recurs, copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PLIM_ASIC-3-SW_ERR
Software action: Abort
Instance [dec]. Operation: [chars]. Error: [chars].
Explanation The operation is failed due to an internal software error. %d - instance. %s - description
of the operation. %s - description of the error.
Recommended Action Check if the linecard reported any other errors. May need to restart process.
Error Message
%L2-PLIM_ASIC-4-HW_WARNING
plaspa instance [dec]: [chars]
Explanation Plim Asic errors. Typically these indicate errors detected by the ASIC. Too many of
these errors might indicate problem with the board, and may trigger packet loss.
Recommended Action Check if spa is seating properly Check whether process ’plaspa_server’ is up
and running. Check if the linecard reported any other errors and/or traffic loss was observed. If the
message recurs, copy the error message exactly as it appears on the console or in the system log, call
your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PLIM_ASIC-6-RESET_REJECT
because [chars]
PLIM ASIC instance [dec] [chars] is not proceeded
Explanation An ASIC error has occurred and requires pon-reset or hard-reset, the reset will not
happen due to the other critical activity is ongoing.
Recommended Action This is an informational message indicating that the required error recovery
action not being taken is expected.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-826
OL-23348-01
Layer 2 Messages
PLIM_CLKSEL Messages
PLIM_CLKSEL Messages
Error Message
%L2-PLIM_CLKSEL-3-ERR_INIT PLIM process is restarted because of a failure in
Clock Selection Library initialization: ([chars]/[chars]).
Explanation The initialization of the Clock Selection Library failed. The Clock Selection Library is
used by the physical layer interface module (PLIM) driver on the linecard. The PLIM driver creates
the SONET controller and POS interface, handling the all the SONET event, applying SONET/POS
configuration to the layer-1 device hardware. If the PLIM driver fails to initialize, no traffic will
pass, therefore no higher level protocol will work. %s - indicates the reason for the failure %s - is
the decoded error reason
Recommended Action The System Manager process (sysmgr) will automatically respawn the PLIM
process, up to a fixed number of times when this error is encountered, to recover. Execute ’show
process process name location 0/x/cpu0’ to verify that the process is up and running, where process
name equals ’pl_e48_pos_4p_oc12’ for OC12 linecard; ’pl_e48_pos_1p_oc48’ for OC48 linecard;
If it is still non-operational, try to do a manually process restart with CLI: ’process restart process
name location 0/x/cpu0’. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PLIM_CLKSEL-4-ERR_DEBUG
Debug initialization failed with [chars].
Explanation Debug message initialization failed.
Recommended Action This error has no effect on any feature except that debug information cannot be
turned on by CLI ’debug plim-clksel location 0/x/CPU0’. Restarting the process with the CLI below,
process restart will not affect traffic. ’process restart process name location 0/x/CPU0’ may resolve
the problem.
PLIM_ETHER Messages
Error Message
%L2-PLIM_ETHER-2-RX_LOSS
Interface [chars], Detected Rx Loss of Signal
Explanation The PLIM received an Rx LOS or LF on the given interface which will result in a link
down.
Recommended Action Correct the far end or fiber to this interface.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-827
Layer 2 Messages
PLIM_ETHER Messages
Error Message
%L2-PLIM_ETHER-2-RX_RF
Interface [chars], Detected Remote Fault
Explanation The PLIM received a Remote Fault on the given interface which will result in a link
down.
Recommended Action Correct the far end interface.
Error Message
%L2-PLIM_ETHER-2-RX_UNKNOWN
Interface [chars], Detected Rx Unknown Fault
Explanation The PLIM received an unknown fault on the given interface which will result in a link
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-PLIM_ETHER-2-XGXS_DTE_SYNC_ERROR_RECOVERED Port [dec] Rx data path issues
between PLA and PHY, software recovery complete
Explanation The PLA MAC xgxs DTE layer went down due to loss of sync or lane alignment.
Recommended Action Copy the error message exactly as it appears on 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_ETHER-2-XGXS_DTE_SYNC_ERROR_RECOVERY_FAILED
issues between PLA and PHY, port disabled
Port [dec] Rx data path
Explanation The PLA MAC xgxs DTE layer went down due to loss of sync or lane alignment. The
link could not be recovered so the port was disabled
Recommended Action Copy the error message exactly as it appears on 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_ETHER-2-XGXS_DTE_SYNC_ERROR_THRESHOLD
between PLA and PHY, threshold: port disabled
Port [dec] Rx data path issues
Explanation The PLA MAC xgxs DTE layer went down due to loss of sync or lane alignment. The
daily event threshold was crossed so the serdes was reset
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-828
OL-23348-01
Layer 2 Messages
PLIM_ETHER Messages
Error Message
%L2-PLIM_ETHER-2-XGXS_DTE_SYNC_POST_RECOVERY
recovered
Port [dec],RX XGXS lost sync: link
Explanation The PLA MAC xgxs DTE layer went down due to loss of sync or lane alignment.
Recommended Action Copy the error message exactly as it appears on 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_ETHER-2-XGXS_DTE_SYNC_POST_RECOVERY_FAILED
sync: link recovery failed
Port [dec],RX XGXS lost
Explanation The PLA MAC xgxs DTE layer went down due to loss of sync or lane alignment. The
link could not be recovered so the port was disabled
Recommended Action Copy the error message exactly as it appears on 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_ETHER-3-SW_INIT
INIT Error: [chars]
Explanation Internal software error in initialization.
Recommended Action Check if the linecard reported any other errors and/or traffic loss was observed.
Error Message
%L2-PLIM_ETHER-3-SW_INTERFACE
Link [chars] went down but software reason is up
Explanation Internal software error in interface state.
Recommended Action Check if the linecard reported any other errors and/or traffic loss was observed.
Error Message
%L2-PLIM_ETHER-6-MODE_CHANGE
Interface [chars] changed to [chars] mode
Explanation PLIM interface mode changed to ’LAN’ or ’WAN’ from CLI.
Recommended Action No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-829
Layer 2 Messages
PLIM_FPGA Messages
PLIM_FPGA Messages
Error Message
%L2-PLIM_FPGA-3-CRITICAL_ERROR
[chars]: [chars]: [hex]
Explanation PLIM FPGA ASIC Driver encountered a critical error as described in the error message.
This error causes PLIM OC768 process to exit.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PLIM_FPGA-3-PIO_CRITICAL_ERROR Asic PIO failure : [chars], instance [dec]:
rc [dec] cerr [chars] errno [dec] data1 [hex] data2 [hex]
Explanation A critical error occurred in PLIM FPGA Driver which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PLIM_FPGA-6-INFO
[chars]: [chars]
Explanation This is a informational message from PLIM FPGA driver to indicate an operation.
Recommended Action No action is required.
Error Message
%L2-PLIM_FPGA-7-DEBUG_MSG
Debug: [chars]: [chars] value [dec]
Explanation This is a debug message in PLIM FPGA driver to indicate 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-830
OL-23348-01
Layer 2 Messages
PLIM_IOX_4P_GE Messages
PLIM_IOX_4P_GE Messages
Error Message
%L2-PLIM_IOX_4P_GE-3-INIT_ERR
Initialization error: [chars]: [chars]
Explanation The 4 port Gigabit Ethernet (GE) driver failed to initialize properly. This driver provides
the system access to the hardware. A failure during initialization of this process may render the
interfaces provided by the hardware unusable. %s - indicates the reason for the failure %s - is the
decoded error reason
Recommended Action The System Manager process (sysmgr) will automatically respawn this
process, up to a fixed number of times when this error is encountered, to recover. Execute ’show
process plim_iox_4p_ge location 0/x/cpu0’ to verify that the process is up and running. If it is still
non-operational, try doing ’process restart plim_iox_4p_ge location 0/x/cpu0’ If the message recurs,
copy the error message exactly as it appears on the console or in the system log, call your Cisco
technical support representative and provide the representative with the gathered information.
Error Message
%L2-PLIM_IOX_4P_GE-6-INFO_MSG
[chars] [dec]
Explanation This is an Informational message in the plim_iox_4p_ge driver to indicate operation
that may be of interest to the user.
Recommended Action No action is required.
Error Message
%L2-PLIM_IOX_4P_GE-6-RXLOS_INT
[dec]
SFP Rx LOS Interrupt: port: [dec], count equals
Explanation This is an informational message in the gigE driver driver to indicate a Loss of Signal
(LOS) has occurred on the indicated port.
Recommended Action 1. Ensure the equipment at the far end of the link is functioning and
configurations are correct. 2. Ensure the cable are installed correctly Rx plugged into far-end Tx &
Tx plugged into far-end Rx 3. Check SFP and cable compatibility. If the message recurs, copy the
error message exactly as it appears on the console or in the system log, call your Cisco technical
support representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-831
Layer 2 Messages
PLIM_LIB Messages
PLIM_LIB Messages
Error Message
%L2-PLIM_LIB-2-ERR_FM_REPLY Physical layer interface module library failed to
reply to the Fault Manager for error recovery: [chars]
Explanation The PLIM driver soft error recovery failed because the PLIM library function failed
with replying to the Fault Manager request. If the PLIM soft error recovery failed, the PLIM
hardware state may not be in the correct state, and the traffic may be affected. %s - is the decoded
error reason
Recommended Action The Fault Manager will reset the linecard if the error recovery failed, search
through the event logs, if there is no any message indicating that the Fault Manager has reset the
linecard, try to do a manually reset with CLI: ’hw-module location 0/x/cpu0 reload’ If the message
recurs, copy the error message exactly as it appears on the console or in the system log, call your
Cisco technical support representative and provide the representative with the gathered information.
Error Message
%L2-PLIM_LIB-2-ERR_FM_REQUEST The Fault Manager cannot send message to physical
layer interface module driver to start soft error recovery: [chars]/[chars]
Explanation When a soft error is detected with any ASIC on the datapath, the Fault Manager will
start the soft error recovery on the datapath. If the Fault Manager cannot send request to the PLIM
driver, the soft error recovery will not be completed, therefore the traffic will not go through the
datapath. %s - indicates the reason for the failure %s - is the decoded error reason
Recommended Action The Fault Manager will reset the linecard if sending message failed, search
through the event logs, if there is no any message indicating that the Fault Manager has reset the
linecard, try to do a manually reset with CLI: ’hw-module location 0/x/cpu0 reload’ If the message
recurs, copy the error message exactly as it appears on the console or in the system log, call your
Cisco technical support representative and provide the representative with the gathered information.
Error Message
%L2-PLIM_LIB-3-ERR_INIT Physical layer interface module library initialization
failed: ([chars]/[chars]).
Explanation The physical layer interface module (PLIM) library on the linecard failed to initialize.
The PLIM library is used by PLIM driver which creates the SONET controller, POS interface,
handling the all the SONET event and applying SONET/POS configuration to the layer1 devices. If
the PLIM driver failed to initialize, no traffic will pass, therefore no higher level protocol will work.
%s - indicates the reason for the failure %s - is the decoded error reason
Recommended Action The System Manager process (sysmgr) will automatically respawn the PLIM
process, up to a fixed number of times when this error is encountered, to recover. Execute the
following command to verify that the process is up and running. ’show process process name
location 0/x/cpu0’ where process name equals ’e48_plim_oc3’ for OC3 linecard;
’pl_e48_pos_4p_oc12’ for OC12 linecard; ’pl_e48_pos_1p_oc48’ for OC48 linecard; If it is still
non-operational, try to do a manually process restart with CLI: ’process restart process name
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-832
OL-23348-01
Layer 2 Messages
PLIM_LIB Messages
location 0/x/cpu0’. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Error Message
%L2-PLIM_LIB-3-ERROR
error: [chars]: [chars]: [hex]
Explanation A fatal error occurred in the plim library driver which involves exiting the process.
Recommended Action collect the info from ’show diag’, ’show hfr’, ’show inv’ If the message recurs,
copy the error message exactly as it appears on the console or in the system log, call your Cisco
technical support representative and provide the representative with the gathered information.
Error Message
%L2-PLIM_LIB-4-ERR_MSG_RCV Physical layer interface module library failed in
receiving the message: [chars]
Explanation The PLIM library detects a failure condition when receiving the message. The message
is used only for error recovery, the process should not receive the message in normal case. This error
means a error condition is detected while the process is waiting for a message, it can be ignored if
the error does not persist. Otherwise, if the error persists, it is recommended to restart the process,
restarting process will not affect the traffic.
Recommended Action If the error persists, execute the following command to restart the process.
’process restart process name location 0/x/cpu0’ where process name equals ’e48_plim_oc3’ for
OC3 linecard; ’pl_e48_pos_4p_oc12’ for OC12 linecard; ’pl_e48_pos_1p_oc48’ for OC48
linecard; If the message recurs, copy the error message exactly as it appears on the console or in the
system log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%L2-PLIM_LIB-7-DEBUG
[chars]: [chars] errno [dec]
Explanation This is a debug message in the PLIM library driver to indicate 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 ’show logging’ to confirm sysdb errors
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-833
Layer 2 Messages
plim_oc48 Messages
plim_oc48 Messages
Error Message
%L2-plim_oc48-3-ALLOC_FAILED
Process failed to allocate memory [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to initialized due to unavailable
memory and will be restarted. It may affect traffic passing through the ports located on the PLIM.
PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet
Over Sonet (POS) controller, optical transceiver. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically restart this process
up to a fixed number of times when this error is encountered. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If the process
is not operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0’ where slot - is
slot number in question. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-plim_oc48-3-ALLOC_FAILED
Process failed to allocate memory [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to initialized due to unavailable
memory and will be restarted. It may affect traffic passing through the ports located on the PLIM.
PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet framer, Packet
Over Sonet (POS) controller, optical transceiver. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically restart this process
up to a fixed number of times when this error is encountered. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If the process
is not operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0’ where slot - is
slot number in question. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-plim_oc48-3-CREATE_THREAD_ERROR
Process init failed [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet
(POS) controller, optical transceiver %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process
up to a fixed number of times when this error is encountered. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If the process
is not operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0’ where slot - is
slot number in question. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-834
OL-23348-01
Layer 2 Messages
plim_oc48 Messages
Error Message
%L2-plim_oc48-3-CREATE_THREAD_ERROR
Process init failed [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet
(POS) controller, optical transceiver %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process
up to a fixed number of times when this error is encountered. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If the process
is not operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0’ where slot - is
slot number in question. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-plim_oc48-3-E3_BW_CHNG_REJ
supported
DSU bandwidth change for E3 controller is not
Explanation This is a known hardware limitation. The bandwidth will be defaulted to 34010 kbps.
Recommended Action Remove the configuration which changes DSU bandwidth of E3 controller.
Error Message
%L2-plim_oc48-3-ERR_EVM_CREATE
Interface module driver initialization failed
Explanation Physical Layer Interface Module (PLIM) driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet
(POS) controller. As result of such failure no traffic may pass on the oc48 port located on the
linecard. The interfaces associated with failed PLIM will not come up.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process
up to a fixed number of times when this error is encountered to recover. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If it’s not
operational attempt to restart the process using command ’process restart pl_e48_pos_1p_oc48
location 0/slot/cpu0’ If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-plim_oc48-3-ERR_EVM_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 traffic may pass on the oc48 port located on the
linecard. The interfaces associated with failed PLIM will not come up.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process
up to a fixed number of times when this error is encountered to recover. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If it’s not
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-835
Layer 2 Messages
plim_oc48 Messages
operational attempt to restart the process using command ’process restart pl_e48_pos_1p_oc48
location 0/slot/cpu0’ If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-plim_oc48-3-ERR_EVM_EVENT_BLOCK
process received invalid event [chars]
Explanation Physical Layer Interface Module (PLIM) driver experience an error while awaiting for
event arrival. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet
framer, Packet Over Sonet (POS) controller. As result of the error the PLIM process will be
restarted. Traffic may be interrupted on all affected interfaces. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process
up to a fixed number of times when this error is encountered to recover. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If it’s not
operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0 If the message recurs,
copy the error message exactly as it appears on the console or in the system log, call your Cisco
technical support representative and provide the representative with the gathered information.
Error Message
%L2-plim_oc48-3-ERR_EVM_EVENT_BLOCK
process received invalid event [chars]
Explanation Physical Layer Interface Module (PLIM) driver experience an error while awaiting for
event arrival. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet
framer, Packet Over Sonet (POS) controller. As result of the error the PLIM process will be
restarted. Traffic may be interrupted on all affected interfaces. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process
up to a fixed number of times when this error is encountered to recover. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If it’s not
operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0 If the message recurs,
copy the error message exactly as it appears on the console or in the system log, call your Cisco
technical support representative and provide the representative with the gathered information.
Error Message
%L2-plim_oc48-3-ERR_MBUS_OP
Optical parameter measurement error [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to measure laser bias or optical
receive power. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet
framer, Packet Over Sonet (POS) controller, optical transceiver. PLIM driver performs periodic
measurements of the laser bias and received signal optical power. The results of such measurements
are represented in the ’show controller pos 0/slot/0/0’ command under the ’optical power
monitoring’ section. %s - error code
Recommended Action If the error persist reset the linecard using ’hw-module location 0/slot/CPU0
reload’ command. The line card restart may affect traffic passing on the oc48 interface. If the
message recurs, copy the error message exactly as it appears on the console or in the system log, call
your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-836
OL-23348-01
Layer 2 Messages
plim_oc48 Messages
Error Message
%L2-plim_oc48-3-ERR_MBUS_OP
Optical parameter measurement error [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to measure laser bias or optical
receive power. PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet
framer, Packet Over Sonet (POS) controller, optical transceiver. PLIM driver performs periodic
measurements of the laser bias and received signal optical power. The results of such measurements
are represented in the ’show controller pos 0/slot/0/0’ command under the ’optical power
monitoring’ section. %s - error code
Recommended Action If the error persist reset the linecard using ’hw-module location 0/slot/CPU0
reload’ command. The line card restart may affect traffic passing on the oc48 interface. If the
message recurs, copy the error message exactly as it appears on the console or in the system log, call
your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-plim_oc48-3-ERR_PORT_INIT
PLIM port init failed [dec] stage-[chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to initialize port. As result of the
failure affected interfaces will not come up. %d - failed port number %s - specific stage of port
initialization that failed PLIM driver is responsible for initializing/configuring PLIM hardware such
as sonet framer and Packet Over Sonet (POS) controller.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process
up to a fixed number of times when this error is encountered. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If the process
is not operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0’ where slot - is
slot number in question. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-plim_oc48-3-ERR_PORT_INIT
PLIM port init failed [dec] stage-[chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to initialize port. As result of the
failure affected interfaces will not come up. %d - failed port number %s - specific stage of port
initialization that failed PLIM driver is responsible for initializing/configuring PLIM hardware such
as sonet framer and Packet Over Sonet (POS) controller.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process
up to a fixed number of times when this error is encountered. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If the process
is not operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0’ where slot - is
slot number in question. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-837
Layer 2 Messages
plim_oc48 Messages
Error Message
%L2-plim_oc48-3-FWD_REGISTER_ERROR
Process initialization error [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to initialized and will be
restarted. It will affect traffic passing through the ports located on the PLIM. PLIM driver is
responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet
(POS) controller, optical transceiver. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically restart this process
up to a fixed number of times when this error is encountered. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If the process
is not operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0’ where slot - is
slot number in question. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-plim_oc48-3-FWD_REGISTER_ERROR
Process initialization error [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to initialized and will be
restarted. It will affect traffic passing through the ports located on the PLIM. PLIM driver is
responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet
(POS) controller, optical transceiver. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically restart this process
up to a fixed number of times when this error is encountered. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If the process
is not operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0’ where slot - is
slot number in question. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-plim_oc48-3-PORT_AVAILABLE_FAILED
[dec]
Port failed to become available [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to make port available for
forwarding. The interface in question will not forward packets. %s - error code %d - port number
Recommended Action Restart the process using ’process restart pl_e48_pos_1p_oc48 location
0/slot/cpu0’. Process restart may affect traffic on the oc48 interface located on the line card. Reload
the line card using ’hw-module location 0/slot/cpu0 reload’ if the process restart failed to solve the
problem. If the message recurs, copy the error message exactly as it appears on the console or in the
system log, call your Cisco technical support representative and provide the representative with the
gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-838
OL-23348-01
Layer 2 Messages
plim_oc48 Messages
Error Message
%L2-plim_oc48-3-PORT_AVAILABLE_FAILED
[dec]
Port failed to become available [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to make port available for
forwarding. The interface in question will not forward packets. %s - error code %d - port number
Recommended Action Restart the process using ’process restart pl_e48_pos_1p_oc48 location
0/slot/cpu0’. Process restart may affect traffic on the oc48 interface located on the line card. Reload
the line card using ’hw-module location 0/slot/cpu0 reload’ if the process restart failed to solve the
problem. If the message recurs, copy the error message exactly as it appears on the console or in the
system log, call your Cisco technical support representative and provide the representative with the
gathered information.
Error Message
%L2-plim_oc48-3-RESET_FAILED
PLIM reset failed [chars]
Explanation The Physical Layer Interface Module (PLIM) driver failed to reset PLIM hardware. %s
- error code PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet
framer, Packet Over Sonet (POS) controller.
Recommended Action If the error occurred during user command execution retry the command and if
the error persist consider restarting plim process ( ’process restart pl_e48_pos_1p_oc48 location
0/slot/cpu0’. PLIM process restart may affect traffic on the oc48 port located on the line card. If the
message recurs, copy the error message exactly as it appears on the console or in the system log, call
your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-plim_oc48-3-RESET_FAILED
PLIM reset failed [chars]
Explanation The Physical Layer Interface Module (PLIM) driver failed to reset PLIM hardware. %s
- error code PLIM driver is responsible for initializing/configuring PLIM hardware such as sonet
framer, Packet Over Sonet (POS) controller.
Recommended Action If the error occurred during user command execution retry the command and if
the error persist consider restarting plim process ( ’process restart pl_e48_pos_1p_oc48 location
0/slot/cpu0’. PLIM process restart may affect traffic on the oc48 port located on the line card. If the
message recurs, copy the error message exactly as it appears on the console or in the system log, call
your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-839
Layer 2 Messages
plim_oc48 Messages
Error Message
%L2-plim_oc48-3-STATS_COLLECT_REGISTER_FAILED
error [chars] [chars]
Statistics collector registration
Explanation Physical Layer Interface Module (PLIM) driver failed to register PLIM interface
statistics collector. No interface statistics such as sonet counters and packet counters will be
available on the specified interface. %s - contains interface name %s - contains error code
Recommended Action Restart the process using ’process restart pl_e48_pos_1p_oc48 location
0/slot/cpu0’. Process restart may affect traffic on the oc48 interface located on the line card. If the
message recurs, copy the error message exactly as it appears on the console or in the system log, call
your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-plim_oc48-3-STATSD_COLL_INIT_ERROR
Process initialization error [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to initialized and will be
restarted. It will affect traffic passing through the ports located on the PLIM. PLIM driver is
responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet
(POS) controller, optical transceiver %s - error code
Recommended Action The System Manager process (sysmgr) will automatically restart this process
up to a fixed number of times when this error is encountered. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If the process
is not operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0’ where slot - is
slot number in question. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-plim_oc48-3-TIMER_INIT_FAILED
Process init failed [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet
(POS) controller, optical transceiver. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process
up to a fixed number of times when this error is encountered. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If the process
is not operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0’ where slot - is
slot number in question. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-840
OL-23348-01
Layer 2 Messages
plim_oc48 Messages
Error Message
%L2-plim_oc48-3-TIMER_INIT_FAILED
Process init failed [chars]
Explanation Physical Layer Interface Module (PLIM) driver failed to initialize. PLIM driver is
responsible for initializing/configuring PLIM hardware such as sonet framer, Packet Over Sonet
(POS) controller, optical transceiver. %s - error code
Recommended Action The System Manager process (sysmgr) will automatically respawn this process
up to a fixed number of times when this error is encountered. Execute ’show process
pl_e48_pos_1p_oc48 location 0/slot/cpu0’ to verify that the process is up and running. If the process
is not operational attempt ’process restart pl_e48_pos_1p_oc48 location 0/slot/cpu0’ where slot - is
slot number in question. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-plim_oc48-3-TX_CLK_GET_INVALID_PORT_CTX
Failed to retrieve tx clock source
Explanation Physical Layer Interface Module (PLIM) driver was unable to determine transmit clock
source for the sonet port. The error may appear during show or configuration of the sonet port.
Recommended Action If the error occurred during user command execution retry the command and if
the error persist contact technical support.
Error Message
%L2-plim_oc48-3-TX_CLK_GET_INVALID_PORT_CTX
Failed to retrieve tx clock source
Explanation Physical Layer Interface Module (PLIM) driver was unable to determine transmit clock
source for the sonet port. The error may appear during show or configuration of the sonet port.
Recommended Action If the error occurred during user command execution retry the command and if
the error persist contact technical support.
Error Message
%L2-plim_oc48-3-TX_CLK_SET_INVALID_PORT_CTX
for sonet port
Failed to configure tx clock source
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-841
Layer 2 Messages
PLIM_OC768 Messages
Error Message
%L2-plim_oc48-3-TX_CLK_SET_INVALID_PORT_CTX
for sonet port
Failed to configure tx clock source
Explanation Physical Layer Interface Module (PLIM) driver failed to make configure transmit clock
source for the sonet port. The sonet port hardware configuration is invalid and may result in traffic
being dropped or high error count on the port. This error may appear during attempt to configure
clock source for the sonet port.
Recommended Action Retry the sonet port configuration. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-plim_oc48-4-INVALID_TIMER
Invalid timer [dec]
Explanation Physical Layer Interface Module (PLIM) driver received unknown timer event. %d -
timer type
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-plim_oc48-4-INVALID_TIMER
Invalid timer [dec]
Explanation Physical Layer Interface Module (PLIM) driver received unknown timer event. %d -
timer type
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
PLIM_OC768 Messages
Error Message
%L2-PLIM_OC768-3-CRITICAL_ERROR
[chars]: [chars]: [hex]
Explanation PLIM OC768 driver encountered a critical error as described in the error message. This
error causes PLIM OC768 process to exit.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-842
OL-23348-01
Layer 2 Messages
PLIM Messages
Error Message
%L2-PLIM_OC768-6-INFO
[chars]: [chars]
Explanation This is an informational message from PLIM OC768 driver to indicate an operation.
Recommended Action No action is required.
Error Message
%L2-PLIM_OC768-7-DEBUG_MSG
Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the plim_oc768 driver to indicate 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.
PLIM Messages
Error Message
%L2-PLIM-1-ERR_HW_RELOAD_NODE
action: [chars]
Device: [chars]%s. Error: [chars]. Software
Explanation A hardware error is detected on the PLIM. Software will take action as described in the
error message to try to recover from the error. The hardware error and the software recovery action
will cause linecard reload. Device: %s%s - indicates the device on which the error is detected. Error:
%s - description of the hardware error. Software action: %s - the action that software will take to try
to recover from the error.
Recommended Action If the message recurs, diagnostics should be executed on the PLIM and MSC.
Error Message
%L2-PLIM-1-ERR_HW_RELOAD_NODE
action: [chars]
Device: [chars]%s. Error: [chars]. Software
Explanation A hardware error is detected on the PLIM. Software will take action as described in the
error message to try to recover from the error. The hardware error and the software recovery action
will cause linecard reload. Device: %s%s - indicates the device on which the error is detected. Error:
%s - description of the hardware error. Software action: %s - the action that software will take to try
to recover from the error.
Recommended Action If the message recurs, diagnostics should be executed on the PLIM and MSC.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-843
Layer 2 Messages
PLIM Messages
Error Message
%L2-PLIM-1-ERR_HW_THRESHOLD_RELOAD_NODE Device: [chars]%s. Error: [chars].
Threshold of [chars] has been crossed. Software action: [chars]
Explanation A hardware error is detected on the PLIM, and the error threshold has been crossed.
Software will take action as described in the error message to try to contain or recover from the error.
The hardware error and the software recovery action will cause linecard reload. Device: %s%s indicates the device on which the error is detected. Error: %s - description of the hardware error.
Threshold of %s - the defined threshold for this error. Software action: %s - the action that software
will take to try to contain or recover from the error.
Recommended Action If the message recurs, diagnostics should be executed on the PLIM and MSC.
Error Message
%L2-PLIM-1-ERR_HW_THRESHOLD_RELOAD_NODE Device: [chars]%s. Error: [chars].
Threshold of [chars] has been crossed. Software action: [chars]
Explanation A hardware error is detected on the PLIM, and the error threshold has been crossed.
Software will take action as described in the error message to try to contain or recover from the error.
The hardware error and the software recovery action will cause linecard reload. Device: %s%s indicates the device on which the error is detected. Error: %s - description of the hardware error.
Threshold of %s - the defined threshold for this error. Software action: %s - the action that software
will take to try to contain or recover from the error.
Recommended Action If the message recurs, diagnostics should be executed on the PLIM and MSC.
Error Message
%L2-PLIM-2-EIO_TRAIN
PLA: [chars], [chars]
Explanation EIO training errors. The PLA EIO failed to train... this will result in traffic loss and the
MSC will fail to send traffic through the PLIM.
Recommended Action Currently, the only recovery is for an MSC reload. Once the Fault-Mgr is
available, the ASIC will be reset in order to retrain the EIO. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PLIM-2-ERR_HW_HARD_RESET
[chars]
Device: [chars]%s. Error: [chars]. Software action:
Explanation A hardware error is detected on the PLIM. Software will take action as described in the
error message to try to recover from the error. The hardware error and the software recovery action
will cause hard reset of a device in the data path and will impact traffic. Device: %s%s - indicates
the device on which the error is detected. Error: %s - description of the hardware error. Software
action: %s - the action that software will take to try to recover from the error.
Recommended Action No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-844
OL-23348-01
Layer 2 Messages
PLIM Messages
Error Message
%L2-PLIM-2-ERR_HW_HARD_RESET
[chars]
Device: [chars]%s. Error: [chars]. Software action:
Explanation A hardware error is detected on the PLIM. Software will take action as described in the
error message to try to recover from the error. The hardware error and the software recovery action
will cause hard reset of a device in the data path and will impact traffic. Device: %s%s - indicates
the device on which the error is detected. Error: %s - description of the hardware error. Software
action: %s - the action that software will take to try to recover from the error.
Recommended Action No action is required.
Error Message
%L2-PLIM-2-ERR_HW_THRESHOLD_HARD_RESET Device: [chars]%s. Error: [chars].
Threshold of [chars] has been crossed. Software action: [chars]
Explanation A hardware error is detected on the PLIM, and the error threshold has been crossed.
Software will take action as described in the error message to try to contain or recover from the error.
The hardware error and the software recovery action will cause hard reset of a device in the data path
and will impact traffic. Device: %s%s - indicates the device on which the error is detected. Error:
%s - description of the hardware error. Threshold of %s - the defined threshold for this error.
Software action: %s - the action that software will take to try to contain or recover from the error.
Recommended Action No action is required.
Error Message
%L2-PLIM-2-ERR_HW_THRESHOLD_HARD_RESET Device: [chars]%s. Error: [chars].
Threshold of [chars] has been crossed. Software action: [chars]
Explanation A hardware error is detected on the PLIM, and the error threshold has been crossed.
Software will take action as described in the error message to try to contain or recover from the error.
The hardware error and the software recovery action will cause hard reset of a device in the data path
and will impact traffic. Device: %s%s - indicates the device on which the error is detected. Error:
%s - description of the hardware error. Threshold of %s - the defined threshold for this error.
Software action: %s - the action that software will take to try to contain or recover from the error.
Recommended Action No action is required.
Error Message
%L2-PLIM-2-HW_INIT_ERR
Hardware initialization failed. Reason: [chars]
Explanation The PLIM process failed to spawn due to failure in the PLIM hardware initialization
process. The PLIM process is the driver for all PLIM hardware devices. %s - indicates the reason
for the failure.
Recommended Action Check if the linecard reported any other errors during the boot process as this
error might be associated with larger system issues. The error is most likely due to a hardware failure
on the PLIM or MSC. Diagnostics should be executed on the PLIM and MSC.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-845
Layer 2 Messages
PLIM Messages
Error Message
%L2-PLIM-2-PHY_CLOCK_PERSIST
disabling the port.
Port [dec], Distributed clock unable to recover,
Explanation The PHY device experienced a distributed clocking failure and software could not
recover the problem. The port has been disabled.
Recommended Action Copy the error message exactly as it appears on 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-2-PHY_XAUI_THRESH Port [dec], Tx data path failure between the PHY and
PLA devices, disabling port.
Explanation The XAUI bus between the PLA ASIC and PHY device experienced a synchronization
problem resulting in a lane failure causing a link flap. Software could not recover the problem and
the port has been disabled.
Recommended Action Copy the error message exactly as it appears on 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-2-PPS_ACCESS_PERSIST
Software cannot access the PLIM protection switch.
Explanation Software could not access the PPS device during initialization.
Recommended Action Recommended to reload the PLIM at the next maintenance window. Copy the
error message exactly as it appears on 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-2-XFP_ALARM_THRESH Port [dec], XFP alarm condition exceeds threshold of
[chars], disabling interrupt.
Explanation XFP alarm condition interrupt exceeded the defined threshold. Software will disable the
interrupt. It is recommended to replace the XFP module.
Recommended Action Replace the XFP module.
Error Message
%L2-PLIM-2-XFP_NPOWER_THRESH
Port [dec], XFP lost power ok state, powering off.
Explanation The XFP device lost its power OK state causing the link to flap. Software tried to
recover the issue by resetting the XFP device but the problem persisted and the XFP device has been
powered off. It is recommended to replace the XFP module.
Recommended Action Replace the XFP module.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-846
OL-23348-01
Layer 2 Messages
PLIM Messages
Error Message
%L2-PLIM-3-CHK_ERR
PLA: [chars], [chars]
Explanation Checkpoint Initialization Failure. The pla_server process failed to initialize its
checkpointing data. The process cannot continue and needs to be restarted.
Recommended Action None, the process should recover. If it does not, the system will most likely be
in an unrecoverable state and will take appropriate action. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PLIM-3-ERR
[chars]
Explanation fail to init debug events; sysdb fails to provide services; event mgr fails to provides its
services;
Recommended Action pla_server would be restarted by sysmgr. check out whether there is any
problems with sysdb check out whether there is any problems with the event mgr there should be
error messages from sysdb or event msg. ’show logging’ could confirm this sh plim pla trace info sh
plim pla trace error
Error Message
%L2-PLIM-3-ERR_HW_SHUTDOWN_PORT Device: [chars]%s. Error: [chars]. Software
action: [chars]. Recommended user action: [chars]
Explanation A hardware error is detected on the PLIM. Software will take action as described in the
error message to try to recover from the error. The hardware error and the software recovery action
will cause shutting down the port. Device: %s%s - indicates the device on which the error is
detected. Error: %s - description of the hardware error. Software action: %s - the action that software
will take to try to recover from the error. Recommended user action: %s - recommended action to
the user. Possible values: ’none’ ’replace XFP’ ’PLEASE MANUALLY RELOAD THE LC AT
NEXT MAINTENANCE WINDOW’
Recommended Action Take the recommended user action as it is described in the error message.
Error Message
%L2-PLIM-3-ERR_HW_SHUTDOWN_PORT Device: [chars]%s. Error: [chars]. Software
action: [chars]. Recommended user action: [chars]
Explanation A hardware error is detected on the PLIM. Software will take action as described in the
error message to try to recover from the error. The hardware error and the software recovery action
will cause shutting down the port. Device: %s%s - indicates the device on which the error is
detected. Error: %s - description of the hardware error. Software action: %s - the action that software
will take to try to recover from the error. Recommended user action: %s - recommended action to
the user. Possible values: ’none’ ’replace CFP’ ’PLEASE MANUALLY RELOAD THE LC AT
NEXT MAINTENANCE WINDOW’
Recommended Action Take the recommended user action as it is described in the error message.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-847
Layer 2 Messages
PLIM Messages
Error Message
%L2-PLIM-3-ERR_HW_THRESHOLD_SHUTDOWN_PORT Device: [chars]%s. Error: [chars].
Threshold of [chars] has been crossed. Software action: [chars]. Recommended user
action: [chars]
Explanation A hardware error is detected on the PLIM, and the error threshold has been crossed.
Software will take action as described in the error message to try to contain or recover from the error.
The hardware error and the software recovery action will cause shutting down the port. Device:
%s%s - indicates the device on which the error is detected. Error: %s - description of the hardware
error. Threshold of %s - the defined threshold for this error. Software action: %s - the action that
software will take to try to contain or recover from the error. Recommended user action: %s recommended action to the user. Possible values: ’none’ ’replace CFP’ ’PLEASE MANUALLY
RELOAD THE LC AT NEXT MAINTENANCE WINDOW’
Recommended Action Take the recommended user action as it is described in the error message.
Error Message
%L2-PLIM-3-ERR_HW_THRESHOLD_SHUTDOWN_PORT Device: [chars]%s. Error: [chars].
Threshold of [chars] has been crossed. Software action: [chars]. Recommended user
action: [chars]
Explanation A hardware error is detected on the PLIM, and the error threshold has been crossed.
Software will take action as described in the error message to try to contain or recover from the error.
The hardware error and the software recovery action will cause shutting down the port. Device:
%s%s - indicates the device on which the error is detected. Error: %s - description of the hardware
error. Threshold of %s - the defined threshold for this error. Software action: %s - the action that
software will take to try to contain or recover from the error. Recommended user action: %s recommended action to the user. Possible values: ’none’ ’replace XFP’ ’PLEASE MANUALLY
RELOAD THE LC AT NEXT MAINTENANCE WINDOW’
Recommended Action Take the recommended user action as it is described in the error message.
Error Message
%L2-PLIM-3-HW_ERR
asic error: [chars]
Explanation Plim Asic errors. Typically these indicate errors detected by the ASIC. Too many of
these errors might indicate problem with the board, and can trigger a reload of the LC.
Recommended Action Check whether process ’pla_server’ is up and running. Check if the linecard
reported any other errors and/or traffic loss was observed. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-848
OL-23348-01
Layer 2 Messages
PLIM Messages
Error Message
%L2-PLIM-3-HW_INIT_ERR
Hardware Initialization Failed, Reason: [chars]
Explanation The PLIM process failed to spawn as it could not access PLIM hardware during the
initialization process. The process will not be re-spawned. The PLIM process is the driver for all
PLIM hardware devices. %s - indicates the reason for the failure.
Recommended Action Check if the linecard reported any other errors during the boot process as this
error might be associated with larger system issues but its likely due to a hardware failure on the
PLIM. Diagnostics should be executed on the PLIM.
Error Message
%L2-PLIM-3-INCONSISTENT_CONFIG
[chars]
Explanation As part of trying to configure dot1q vlan with vlan id same as that of outer vlan of QinQ
configuration or vice versa on another sub-interface, then error has to be reported to remove the
inconsistent configuration.
Recommended Action Upon seeing this message, delete the subinterface that has just been created.
Otherwise the system will be in inconsistent state.
Error Message
%L2-PLIM-3-INTERRUPT_ERR
Interrupt handling error.
Explanation The PLIM process failed to handle an interrupt.
Recommended Action Check if the linecard reported any other errors and/or traffic loss was observed.
The most common type of failure is an XFP OIR.
Error Message
%L2-PLIM-3-MEM_ERR
[chars]
Explanation fail to allocate memory.
Recommended Action show process memory to find out whether there is potential memory leak show
memory to confirm system memory goes low sh plim pla trace info sh plim pla trace error
Error Message
%L2-PLIM-3-PHY_ACCESS_PERSIST
disabling port.
Port [dec], Access to the PHY device failed,
Explanation Software could not access the PHY device during port initialization.
Recommended Action The physical port has been disabled and cannot be used. Copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-849
Layer 2 Messages
PLIM Messages
Error Message
%L2-PLIM-3-SQUID_ERR
[chars]
Explanation squid fails to find the device
Recommended Action 1. reseat the plim. 2. if the problem is still there after reseating, run diag on the
plim
Error Message
%L2-PLIM-3-SW_ERR
action: Abort
Port [dec]. Operation: [chars]. Error: [chars]. Software
Explanation The operation is failed due to an internal software error. %d - port number. %s description of the operation. %s - description of the error.
Recommended Action Check if the linecard reported any other errors. May need to restart process.
Error Message
%L2-PLIM-3-SW_INIT_ERR
Software initialization failed. Reason: [chars]
Explanation The PLIM process failed to spawn due to an internal software problem during the
initialization process. The process will automatically respawn up to a fixed number of times to try
and recover. The PLIM process is the driver for all PLIM hardware devices. %s - indicates the reason
for the failure.
Recommended Action Check if the linecard reported any other errors during the boot process as this
error is normally associated with larger system issues. If the message recurs, copy the error message
exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PLIM-3-SW_INIT_ERR
Software Initialization Failed, Reason: [chars]
Explanation The PLIM process failed to spawn due to an internal software problem during the
initialization process. The process will automatically respawn up to a fixed number of times to try
and recover. The PLIM process is the driver for all PLIM hardware devices. %s - indicates the reason
for the failure.
Recommended Action Check if the linecard reported any other errors during the boot process as this
error is normally associated with larger system issues. If the message recurs, copy the error message
exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-850
OL-23348-01
Layer 2 Messages
PLIM Messages
Error Message
%L2-PLIM-3-XFP_ACCESS_PERSIST
off.
Port [dec], Software cannot access XFP, powering
Explanation Software could not access the optics module during initialization.
Recommended Action Replace the XFP.
Error Message
%L2-PLIM-3-XFP_HOTSWAP_PERSIST
powering off.
Port [dec], XFP failed to reach power ok state,
Explanation The inserted XFP failed to power on correctly.
Recommended Action Replace the XFP.
Error Message
%L2-PLIM-4-CFP_INFO Port [dec]. Operation: [chars]. Warning: [chars].
Information: [chars].
Explanation An issue is detected during operation on Optic interface module. %d - port number. %s
- description of the operation. %s - description of the issue. %s - reason for the issue
Recommended Action Copy the error message exactly as it appears on 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-4-ERR_HW Device: [chars]%s. Error: [chars]. Software action: [chars].
Recommended user action: [chars]
Explanation A hardware error is detected on the PLIM. Software will take action as described in the
error message, if not none, to try to recover from the error. The hardware error and the software
recovery action will not impact traffic. Device: %s%s - indicates the device on which the error is
detected. Error: %s - description of the hardware error. Software action: %s - the action that software
will take to try to recover from the error. Recommended user action: %s - recommended action to
the user. Possible values: ’none’ ’replace CFP’ ’PLEASE MANUALLY RELOAD THE LC AT
NEXT MAINTENANCE WINDOW’
Recommended Action Take the recommended user action as it is described in the error message.
Error Message
%L2-PLIM-4-ERR_HW Device: [chars]%s. Error: [chars]. Software action: [chars].
Recommended user action: [chars]
Explanation A hardware error is detected on the PLIM. Software will take action as described in the
error message, if not none, to try to recover from the error. The hardware error and the software
recovery action will not impact traffic. Device: %s%s - indicates the device on which the error is
detected. Error: %s - description of the hardware error. Software action: %s - the action that software
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-851
Layer 2 Messages
PLIM Messages
will take to try to recover from the error. Recommended user action: %s - recommended action to
the user. Possible values: ’none’ ’replace XFP’ ’PLEASE MANUALLY RELOAD THE LC AT
NEXT MAINTENANCE WINDOW’
Recommended Action Take the recommended user action as it is described in the error message.
Error Message
%L2-PLIM-4-ERR_HW_THRESHOLD Device: [chars]%s. Error: [chars]. Threshold of
[chars] has been crossed. Software action: [chars]. Recommended user action:
[chars]
Explanation A hardware error is detected on the PLIM, and the error threshold has been crossed.
Software will take action as described in the error message, if not none, to try to contain or recover
from the error. The hardware error and the software recovery action will not impact traffic. Device:
%s%s - indicates the device on which the error is detected. Error: %s - description of the hardware
error. Threshold of %s - the defined threshold for this error. Software action: %s - the action that
software will take to try to contain or recover from the error. Recommended user action: %s recommended action to the user. Possible values: ’none’ ’replace CFP’ ’PLEASE MANUALLY
RELOAD THE LC AT NEXT MAINTENANCE WINDOW’
Recommended Action Take the recommended user action as it is described in the error message.
Error Message
%L2-PLIM-4-ERR_HW_THRESHOLD Device: [chars]%s. Error: [chars]. Threshold of
[chars] has been crossed. Software action: [chars]. Recommended user action:
[chars]
Explanation A hardware error is detected on the PLIM, and the error threshold has been crossed.
Software will take action as described in the error message, if not none, to try to contain or recover
from the error. The hardware error and the software recovery action will not impact traffic. Device:
%s%s - indicates the device on which the error is detected. Error: %s - description of the hardware
error. Threshold of %s - the defined threshold for this error. Software action: %s - the action that
software will take to try to contain or recover from the error. Recommended user action: %s recommended action to the user. Possible values: ’none’ ’replace XFP’ ’PLEASE MANUALLY
RELOAD THE LC AT NEXT MAINTENANCE WINDOW’
Recommended Action Take the recommended user action as it is described in the error message.
Error Message
%L2-PLIM-4-PHY_ACCESS
recovery complete.
Port [dec], Access to the PHY device failed, software
Explanation Software could not access the PHY device during port initialization.
Recommended Action None. Software corrected the issue by power cycling the PHY device and the
PLIM FPGA.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-852
OL-23348-01
Layer 2 Messages
PLIM Messages
Error Message
%L2-PLIM-4-PHY_CLOCK
complete.
Port [dec], Distributed clock failure, software recovery
Explanation The PHY device experienced a distributed clocking failure which resulted in a link flap.
A reset of the PHY device corrected the issue.
Recommended Action Software corrected the issue by power cycling the PHY device. If any
loopbacks have been configured on the port, they may need to be re-configured.
Error Message
%L2-PLIM-4-PHY_XAUI Port [dec], Tx data path failure between the PHY and PLA
devices, software recovery complete.
Explanation The XAUI bus between the PLA ASIC and PHY device experienced a synchronization
problem resulting in a lane failure causing a link flap. A reset of the PHY device corrected the issue.
Recommended Action Software corrected the issue by power cycling the PHY device. If any
loopbacks have been configured on the port, they may need to be re-configured.
Error Message
%L2-PLIM-4-PPS_ACCESS
recovery complete.
Access to the PLIM protection switch failed, software
Explanation Software could not access the PPS device during initialization.
Recommended Action None. Software corrected the issue by power cycling the PPS device.
Error Message
%L2-PLIM-4-XFP_ACCESS
complete.
Port [dec], Access to XFP failed, software recovery
Explanation Software reset the optics module as it could not read or write to it during initialization.
Recommended Action None. Software corrected the issue by power cycling the XFP.
Error Message
%L2-PLIM-4-XFP_ALARM
Port [dec], XFP hit alarm condition.
Explanation XFP hit alarm condition and raised interrupt.
Recommended Action None. Software will dampen the interrupt for 5 seconds to attempt recovery.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-853
Layer 2 Messages
PLIM Messages
Error Message
%L2-PLIM-4-XFP_HOTSWAP
recovery complete.
Port [dec], XFP failed to reach power ok state, software
Explanation The inserted XFP failed to power on correctly during initialization.
Recommended Action None. Software corrected the issue by power cycling the XFP.
Error Message
%L2-PLIM-4-XFP_NPOWER
complete.
Port [dec], XFP lost power ok state, software recovery
Explanation The XFP device lost its power OK state causing the link to flap. A reset of the XFP
device corrected the issue.
Recommended Action None. Software corrected the issue by power cycling the XFP device.
Error Message
%L2-PLIM-5-CFP_OIR
Port [dec]: Optic interface module is [chars]
Explanation The Optic Module (CFP) for the specified port has either been inserted or removed. %s
- either ’inserted’ or ’removed’ %d - port number.
Recommended Action No action is required.
Error Message
%L2-PLIM-6-NO_POWER_XFP
powering off.
Port [dec], Not enough power available to power XFP,
Explanation There is not enough available power on the PLIM to power on the XFP.
Recommended Action Remove the XFP from the given port.
Error Message
%L2-PLIM-6-UNSUPPORTED_XFP
Port [dec], Unsupported XFP inserted, powering off.
Explanation The XFP inserted in the given port is not supported on this PLIM.
Recommended Action Verify the XFP is supported in the CRS-1 installation manuals. Replace this
XFP with a Cisco supported XFP.
Error Message
%L2-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-854
OL-23348-01
Layer 2 Messages
pm5315 Messages
pm5315 Messages
Error Message
%L2-pm5315-3-FATAL_ERROR
Fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in karachi Driver which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-pm5315-6-INFO_MSG
Info: [chars]: [chars]
Explanation This is a Informational message in the karachi driver to indicate an operation.
Recommended Action No action is required.
Error Message
%L2-pm5315-7-DEBUG_MSG
Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the karachi driver to indicate 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.
pm5316 Messages
Error Message
%L2-pm5316-3-FATAL_ERROR
[chars](): fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in plim Driver which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-855
Layer 2 Messages
PM622 Messages
Error Message
%L2-pm5316-4-WARNING
[chars](): warning: [chars]: [chars]: [dec]
Explanation A warning condition occurred in plim Driver which involves exiting the process.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
PM622 Messages
Error Message
%L2-PM622-2-error
[chars]
Explanation A high severity error has occurred in PLIM FPGA. This might result in the PLIM being
reset. %s - Error message indicating reason for 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.
PMSAR Messages
Error Message
%L2-PMSAR-2-CFG_ERR
: [chars]: [dec]
Explanation A fatal error occurred during PM SAR Driver configuration while creating or modifying
a VC or VP.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-2-CHAN_STATS_ERR [chars]() [dec], chan:[dec],[dec],[dec]; cid:[dec],
sar:[dec] reason:[chars] status:[dec], ack:[hex], [hex], [hex], [hex]
Explanation A fatal error occurred when PM SAR Driver collects the VC Stats from SAR hardware.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-856
OL-23348-01
Layer 2 Messages
PMSAR Messages
Error Message
%L2-PMSAR-2-CLOSE_VC_COSQ_ERR [chars]() [dec], close cosq failure. rsar:[dec],
ssar:[dec], queue:[dec], cosq_id:[dec] reason:[chars]; status:[dec] ack:[hex],
[hex], [hex], [hex]
Explanation A fatal error occurred when PM SAR Driver tried to create a COSQ.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-2-CLOSE_VC_ERR [chars]() [dec], close vc failure. rsar:[dec],
ssar:[dec], vpi:[dec], vci:[dec] reason:[chars]; status:[dec] ack:[hex], [hex],
[hex], [hex]
Explanation A fatal error occurred when PM SAR Driver tries to delete or modify the VC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-2-CMD_ACK_ERR
[chars]
[chars]() [dec], SAR:[dec] poll incomplete cmd ack,
Explanation A fatal error detected when Parsing the command acknowledgement from SAR.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-2-CMD_ERR
[chars]
Explanation This error indicates unsupported traffic parameters are applied and indicates a
configuration issue.
Recommended Action This error normally points to configuration issue. If the configs are valid and
still the error message is 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-857
Layer 2 Messages
PMSAR Messages
Error Message
%L2-PMSAR-2-CMD_POLL_TIMEOUT
[chars]
[chars]() [dec], SAR:[dec] cmd poll timed out,
Explanation A fatal error occurred during a SAR Command Execution.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-2-CMD_POST_ERR [chars]() [dec], SAR:[dec] post cmd failure.
status:[dec], [chars] [dec] ack:[hex], [hex], [hex], [hex]
Explanation A fatal error occurred when posting command to SAR. This might occur if the SAR is
busy at times. In that case, this error can 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-PMSAR-2-INITERR
Fatal error: [chars]: [hex]
Explanation SAR device cx27470 initialization failed. The failure could be at chip level or some
internal data structure level.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. If you cannot determine the nature of the error from the error message text, call your Cisco
technical support representative and provide the representative with the gathered information.
Error Message
%L2-PMSAR-2-MUTEX_TIMEOUT
timed out, [chars]
[chars]() [dec], Get SAR:[dec], thread_id:[dec] mutex
Explanation A fatal error occurred while trying to lock SAR semaphore.
Recommended Action This normally indicates a transient 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-858
OL-23348-01
Layer 2 Messages
PMSAR Messages
Error Message
%L2-PMSAR-2-OPEN_VC_ERR [chars]() [dec], open vc failure. rsar:[dec],
ssar:[dec], vpi:[dec], vci:[dec] reason:[chars]; status:[dec], ack:[hex], [hex],
[hex], [hex]
Explanation A fatal error occurred when PM SAR Driver configuration tried to create a new VC.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-2-OPEN_VP_ERR [chars]() [dec], open vp failure. sar:[dec] vpi:[dec],
reason:[chars]; ack:[hex], [hex], [hex], [hex]
Explanation A fatal error occurred when PM SAR Driver tries to open a VP tunnel.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-2-PORT_STATS_ERR [chars]() [dec], port stats failure. sar:[dec]
reason:[chars]; status:[dec], ack:[hex], [hex], [hex], [hex]
Explanation A fatal error occurred when PM SAR Driver collects the Port Stats from SAR hardware.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-3-ESYS_ERR
[chars] [dec]: reason [chars] errno:[dec]
Explanation CX27470 esys generic fatal error during memory allocation.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-3-ESYS_LOAD_ELF
[chars] [dec]: file [chars] [chars] [chars]
Explanation CX27470 esys load elf input file symbol not found.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-859
Layer 2 Messages
PMSAR Messages
Error Message
%L2-PMSAR-3-EVENT_INDICATE [chars]() [dec], reason:[chars]; sar:[dec],
log_entry_index:[dec], type:[dec], status:[dec]
Explanation An event raised PM SAR Driver, check the event type
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-3-UNKNOWN_EVENT
log_entry_index:[dec]
[chars]() [dec], reason:[chars]; sar:[dec],
Explanation An unknown event raised PM SAR Driver
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-4-WARNING
[chars]
Explanation PM622 TSP CX27470 warning condition
Recommended Action Debug message only. No action is required.
Error Message
%L2-PMSAR-6-event_dump [chars]() [dec], sar:[dec], event type:[dec],
status:[dec]; hex dump:[hex], [hex], [hex], [hex]
Explanation An unknown event raised PM SAR Driver.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PMSAR-6-INFO
[chars] [hex]
Explanation PM622 TSP CX27470 information
Recommended Action No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-860
OL-23348-01
Layer 2 Messages
POS Messages
Error Message
%L2-PMSAR-7-DEBUG
[chars]
Explanation PM622 TSP CX27470 debug information
Recommended Action Debug message only. No action is required.
POS Messages
Error Message
%L2-POS-3-MTU_IMPOSE_FAILED
Failed to set MTU of [unsigned int] on [chars]
Explanation The specified MTU could not be applied on this interface.
Recommended Action No action is required.
PPP_EA Messages
Error Message
%L2-PPP_EA-3-INIT_ERROR
Process Initialization Failed: ([chars]%s)
Explanation The PPP execution agent process failed to initialize. PPP execution agent programs the
Physical Layer Interface Module (PLIM) for handling PPP encapsulation on a POS link and also add
capsulation for slowpath packet processing. The reason of the failure could be that the interface
manager could not set the interface and returned an error, or could be due to unavailability of
memory resources. This can happen when the linecard is coming up, or when the encapsulation is
changed to PPP. The effect is that the interface will not come up using PPP encapsulation. %s indicates the reason for the failure. %s - is the error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this
process, up to a fixed number of times when this error is encountered, to recover. Execute ’show
process ppp_ea location 0/x/cpu0’ to verify that the process is up and running. If it is still
non-operational, try doing ’process restart ppp_ea location 0/x/cpu0’ Also try reapplying the
configuration. If the message recurs, copy the error message exactly as it appears on the console or
in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Error Message
%L2-PPP_EA-4-ERR_BATCH_ALLOC
Failed to allocate batch for ’[chars]’
Explanation The process failed to allocate memory to handle the event described in the message.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. The ppp_ea process should be restarted to recover using
the command ’process restart ppp_ea location R/S/I’.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-861
Layer 2 Messages
PPP_EA Messages
Error Message
%L2-PPP_EA-4-ERR_EVM_EVENT_BLOCK
The PPP EA process will restart
Error encountered in the event loop: [chars].
Explanation An error occurred in the event loop. The process will restart which should recover the
situation.
Recommended Action *RECUR*
Error Message
%L2-PPP_EA-4-ERR_INIT Failure during initialization of the [chars]. Error
[chars]. The PPP EA process will restart
Explanation A failure occurred during the initialization of the process. The process will restart which
should recover the situation.
Recommended Action *RECUR*
Error Message
%L2-PPP_EA-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. The ppp_ea process should be restarted to recover using
the command ’process restart ppp_ea location R/S/I’.
Error Message
%L2-PPP_EA-4-ERR_RWMGR
Unexpected error whilst [chars]: [chars]
Explanation PPP EA encountered an error communicating with Rewrite 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 Rewrite Manager Server process, but the error could also be caused by
low memory resource or programming error.
Recommended Action In many cases, PPP EA 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-862
OL-23348-01
Layer 2 Messages
PPP_FSM Messages
Error Message
%L2-PPP_EA-4-ERR_RWMGR_IF
CH[hex]: Unexpected error whilst [chars]: [chars]
Explanation PPP EA encountered an error communicating with Rewrite 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 Rewrite Manager Server process, but the error could also be caused by
low memory resource or programming error.
Recommended Action In many cases, PPP EA will recover by itself. If it does not then restarting the
process may help. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Error Message
%L2-PPP_EA-6-ERR_IM_MULTIPLE_NTFCNS
received in a single batch from IM
CH[hex]: Multiple [chars] notifications
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 PPP EA. No problems should be seen
as a result.
Recommended Action *NONE*
PPP_FSM Messages
Error Message
%L2-PPP_FSM-3-ERR_SOCKET
[chars]: Socket [chars] failed; [chars]
Explanation There is a communication problem with the PPP socket.
Recommended Action Restart the ppp_socket process on the node where the error is reported. If the
message recurs, copy the error message exactly as it appears on the console or in the system log, call
your Cisco technical support representative and provide the representative with the gathered
information.
PPP_GBL_CFG Messages
Error Message
%L2-PPP_GBL_CFG-4-ERR_INIT
[chars]
Failure during initialization of [chars]. Error:
Explanation The PPP GBL CFG process failed to initialize correctly.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-863
Layer 2 Messages
PPP_LCP Messages
PPP_LCP Messages
Error Message
%L2-PPP_LCP-3-AAA_SESSION_CLEANUP_FAILED
session has failed: [chars]
CH[hex]: Cleanup of a subscriber
Explanation A call to AAA to remove subscriber session state has failed. The error may cause the
LCP session on the subscriber interface to be left permanently in what should be a transient
unnegotiated state.
Recommended Action To remove the stale sessions, run clear subscriber for this interface.
Error Message
%L2-PPP_LCP-3-MTU_UNUSABLE [chars] has an interface MTU of [unsigned int] which
is smaller than the PPP packet header size ([unsigned int]) and so PPP cannot run
on the interface
Explanation PPP has been informed that the lower-layer MTU has been set to a value smaller than
the PPP header size, which makes it impossible for PPP to operate.
Recommended Action Reconfigure the interface’s MTU to a larger value. In order to ensure correct
operation with peers, values which provide a layer 2 payload capacity (after allowing for 4 bytes of
PPP header) of 1500 bytes or greater are required.
Error Message
%L2-PPP_LCP-4-ERR_AAA_IEDGE_SESSION
[chars]
Unexpected error encountered whilst [chars]:
Explanation PPP MA encountered an error using the AAA iEDGE service. The error message
describes what operation has failed and why it failed. The most likely reason for this is that the AAA
iEDGE server is unavailable. It may also be caused by low memory resource or a programming error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. In many cases, PPP MA will recover by itself. If it does
not then restarting the process should help. If the message recurs, copy the error message exactly as
it appears on the console or in the system log, call your Cisco technical support representative and
provide the representative with the gathered information.
Error Message
%L2-PPP_LCP-4-L2_NOT_SUPPORTED
L2 mode is not supported on CH[hex]
Explanation L2transport has been configured on an interface that does not support it. The interface
will not enter L2 mode, and will remain in whichever mode it was in before. This will occur if the
interface capabilities do not support L2 mode, or if L2 mode is configured on a multilink bundle
member.
Recommended Action Reconfigure the interface so that l2transport is not enabled.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-864
OL-23348-01
Layer 2 Messages
PPP_LCP Messages
Error Message
%L2-PPP_LCP-4-MISSING_AUTHENTICATION_LIST
defined for PPP
AAA authentication list [chars] is not
Explanation One or more PPP interfaces have been configured to authenticate the peer using the
authentication list identified in the error message, but this authentication list has not been configured
in AAA itself. As a result PPP will be unable to authenticate the peer and the line protocol on the
relevant interface or interfaces will not come up.
Recommended Action Configure ’aaa authentication ppp listname ...’
Error Message
%L2-PPP_LCP-4-MTU_WARNING [chars] has a PPP MTU of [unsigned int] which is
smaller than the minimum value ([unsigned int]) required for correct operation
Explanation RFC 1661 requires that the media that PPP is running over is always able to receive PPP
packets of sizes up to 1500 bytes (where this value excludes the 4 bytes of PPP header). This is to
ensure that the peer can always send control protocol packets up to this size if they ever need to
renegotiate. IOS-XR routers set their MRU to the same value as the MTU, and this message has been
issued because the configured MTU is too small to meet the above condition.
Recommended Action Reconfigure the interface’s MTU to a larger value. In order to ensure correct
operation with peers, values which provide a layer 2 payload capacity (after allowing for 4 bytes of
PPP header) of 1500 bytes or greater are required. Note that as most Control Protocol packets are
much smaller than 1500 bytes, it is unlikely that MTU values which are smaller than 1500 bytes will
actually cause problems, but this cannot be guaranteed.
Error Message
%L2-PPP_LCP-4-UNEXPECTED_AAA_RESPONSE CH[hex]: A response with unexpected
properties has been received from AAA: [chars]
Explanation AAA has sent a response which is unexpected or malformed in the way explained in the
message. The error may cause the interface to be left in what should be a transient state permanently.
Recommended Action Check the output of ’show ppp interface’ for the interface with the problem. If
the interface has been left permanently in an unauthenticated state, then it can be manually cleared
using the ’clear subscriber’ command. Note that if the interface has come up successfully then the
unexpected AAA response will probably not have caused problems.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-865
Layer 2 Messages
PPP_LCP Messages
Error Message
%L2-PPP_LCP-4-UNRECOGNIZED_PROTO
(caps equals [chars])
Unrecognized IfMgr protocol [chars] on CH[hex]
Explanation Interface Manager notified LCP about a protocol that it doesn’t recognize, either by
sending a request to LCP to adopt this node or by informing LCP that it exists. This is a
programming error as LCP needs to recognized all of the protocols which run above it in order to
be able to run the relevant CP.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PPP_LCP-5-MTU_NEGOTIATED The PPP MTU for [chars] has been negotiated to be
[unsigned int]. This is less than the configured PPP MTU of [unsigned int]
Explanation The PPP MTU is reduced when the PPP MRU of the peer is less than the PPP MTU
derived from the locally configured interface MTU. The reduced value will be used until LCP is
renegotiated (such as when the interface goes down and comes back up, or a new MTU is
configured), or if the PPP encapsulation is removed from the interface. The MTU then returns to the
configured value and another message will indicate if a value less than the configured value is
negotiated again. The reduced MTU is a normal part of PPP operation and is not indicative of any
problems.
Recommended Action No action is required.
Error Message
%L2-PPP_LCP-6-LOCAL_MTU_TOO_SMALL CH[hex]: Unable to complete LCP negotiations.
Interface MTU on CH[hex] needs to be reconfigured taking into account the L2
headers to give an L3 MTU of at least [unsigned int]
Explanation The peer has sent a NAK in response to the local MRRU value. The value it is
suggesting for the MRRU is larger than the local bundle admin MTU, so it cannot be accepted.
However, suggesting a smaller value will almost certainly lead to repeated NAKs (since the peer
should be suggesting its minimum possible MRRU value), so the LCP session will be closed for a
short time and then negotiations will be retried.
Recommended Action Reconfigure the interface’s MTU to a larger value, taking into account the
Layer 2 headers. Once these headers have been subtracted, the Layer 3 MTU needs to be at least the
value suggested in the message.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-866
OL-23348-01
Layer 2 Messages
PPP_lite Messages
PPP_lite Messages
Error Message
%L2-PPP_lite-3-ERR_PL_DLL_ASYNC_SEND_FAIL
fails; Error [chars]
Send async pulse to ppp lite process
Explanation Attempt to send pulse to PPP lite process fails
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Issue the show tech-support command to gather data that may provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text
or from the show tech-support output, call your Cisco technical support representative and provide
the representative with the gathered information.
Error Message
%L2-PPP_lite-3-ERR_PL_DLL_CHAN_CONNECT_FAIL
Error [chars]
Cannot connect to ppp lite process;
Explanation Attempt to connect to PPP lite process channel fails
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Issue the show tech-support command to gather data that may provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text
or from the show tech-support output, call your Cisco technical support representative and provide
the representative with the gathered information.
Error Message
%L2-PPP_lite-3-ERR_SHMEM_MMAP_FAIL
Cannot mmap file [chars]; Error [chars]
Explanation Attempt to mmap the shared memory fails
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Issue the show tech-support command to gather data that may provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text
or from the show tech-support output, call your Cisco technical support representative and provide
the representative with the gathered information.
Error Message
%L2-PPP_lite-3-ERR_SHMEM_OPEN_FAIL
Cannot open shmem file [chars]; Error [chars]
Explanation Attempt to open the shared memory fails
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Issue the show tech-support command to gather data that may provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text
or from the show tech-support output, call your Cisco technical support representative and provide
the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-867
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_lite-3-ERR_SHMEM_TRNC_FAIL
Error [chars]
Cannot truncate file [chars] to [dec] bytes;
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-PPP_lite-3-ERR_SHMEM_UNAVAILABLE
records (request for [dec] records)
PPP lite SHMEM can accommodate only [dec]
Explanation PPP MA has requested transfer of more interface records than shared memory can
accommodate
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Issue the show tech-support command to gather data that may provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text
or from the show tech-support output, call your Cisco technical support representative and provide
the representative with the gathered information.
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_AAA
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the AAA service. The error message describes what
operation has failed and why it failed. The most likely reason for this is a temporary problem
communicating with the AAA server, but the error could also be caused by low memory resource or
programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the
process may help. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-868
OL-23348-01
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_AAA_ATTR
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the AAA attribute service. The error message
describes what operation has failed and why it failed. The most likely reason for this is low memory
resource or a programming error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. In many cases, PPP MA will recover by itself. If it does
not then restarting the process should help. If the message recurs, copy the error message exactly as
it appears on the console or in the system log, call your Cisco technical support representative and
provide the representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_AAA_ATTR_IF
[chars]: [chars]
CH[hex]: Unexpected error encountered whilst
Explanation PPP MA encountered an error using the AAA attribute service for the interface
specified. The error message describes what operation has failed and why it failed. The most likely
reason for this is low memory resource or a programming error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. In many cases, PPP MA will recover by itself. If it does
not then restarting the process should help. If the message recurs, copy the error message exactly as
it appears on the console or in the system log, call your Cisco technical support representative and
provide the representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_AAA_SESSION
[chars]
Unexpected error encountered whilst [chars]:
Explanation PPP MA encountered an error using the AAA iEDGE service. The error message
describes what operation has failed and why it failed. The most likely reason for this is that the AAA
iEDGE server is unavailable. It may also be caused by low memory resource or a programming error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. In many cases, PPP MA will recover by itself. If it does
not then restarting the process should help. If the message recurs, copy the error message exactly as
it appears on the console or in the system log, call your Cisco technical support representative and
provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-869
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_AAA_SESSION_IF
[chars]: [chars]
CH[hex]: Unexpected error encountered whilst
Explanation PPP MA encountered an error using the AAA iEDGE service for the interface specified.
The error message describes what operation has failed and why it failed. The most likely reason for
this is that the AAA iEDGE server is unavailable. It may also be caused by low memory resource or
a programming error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. In many cases, PPP MA will recover by itself. If it does
not then restarting the process should help. If the message recurs, copy the error message exactly as
it appears on the console or in the system log, call your Cisco technical support representative and
provide the representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_AIB
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error communicating with the AIB server. The error message
describes what operation has failed and why it failed. The most likely reason for this is a temporary
connection problem with the AIB server, but the error could also be caused by low memory resource
or programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the
process may help. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_ATTR
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error communicating with the infrastructure. The error
message describes what operation has failed and why it failed. The most likely reason for this is a
temporary connection problem, but the error could also be caused by low memory resource or
programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the
process may help. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-870
OL-23348-01
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_BACKEND
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the Backend service related to use of either SysDB
or SubDB. The error message describes what operation has failed and why it failed. The most likely
reason for this is low memory resources or a programming error.
Recommended Action Consider restarting the PPP MA process. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_BAG
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the Bag Client library. The error message describes
what operation has failed and why it failed. The most likely reason for this a low memory condition
but the error could also be caused by a programming error. The error will affect PPP MA’s ability to
provide operational management data, but won’t otherwise affect PPP MA’s operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*.
Error Message
%L2-PPP_MA-4-ERR_CHKPT
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the Checkpoint Service. The error message
describes what operation has failed and why it failed. The most likely reason for this a low memory
condition but the error could also be caused by a programming error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*.
Error Message
%L2-PPP_MA-4-ERR_CHKPT_CORRUPT
Corrupt [chars] checkpoint record found: [chars]
Explanation Whilst restoring one of its checkpoint tables PPP MA found a corrupt checkpoint entry.
The entry will be ignored and so the relevant interface’s PPP session will be renegotiated after the
restart and as a result there may be a short period where traffic is lost.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-871
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_CHKPT_DUPLICATE
[chars]
Duplicate [chars] checkpoint record found for
Explanation Whilst restoring one of its checkpoint tables PPP MA found multiple entries for the
same interface. PPP MA will use the first checkpoint entry it finds for each interface and ignore any
subsequent duplicates. This is caused by a programming error.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PPP_MA-4-ERR_CLOCK Unexpected error encountered whilst retrieving the value
of the [chars] clock: [chars]
Explanation PPP MA encountered an error whilst retrieving the value of the real-time clock. The
error message includes details of the reason for the error. This is a fatal error and the PPP MA
process will abort and be restarted to recover.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PPP_MA-4-ERR_DAPS
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the DAPS address pool service. The error message
describes what operation has failed and why it failed. The most likely reason for this is a connection
problem with the DAPS service, but the error could also be caused by low memory resources or
programming error.
Recommended Action Consider restarting the PPP MA process. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_DAPS_IF
[chars]
CH[hex]: Unexpected error encountered whilst [chars]:
Explanation PPP MA encountered an error using the DAPS address pool service. The error message
describes what operation has failed and why it failed. The most likely reason for this is a connection
problem with the DAPS service, but the error could also be caused by low memory resources or
programming error.
Recommended Action Consider restarting the PPP MA process. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-872
OL-23348-01
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_DEBUG
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the debug service. The error message describes
what operation has failed and why it failed. The error could be caused by low memory resource or
programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the
process may help. Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*.
Error Message
%L2-PPP_MA-4-ERR_EVC_CLOSE
Error closing ’[chars]’ connection: [chars]
Explanation PPP MA failed to close a connection to an essential service. This is an internal error and
it requires a restart of the process for recovery.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_EVC_CREATE
Error creating ’[chars]’ connection: [chars]
Explanation PPP MA failed to create a connection to an essential service during initialization. This
is an internal error. It requires a restart of the process for recovery.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PPP_MA-4-ERR_EVC_ERROR
Error resetting ’[chars]’ connection: [chars]
Explanation After detecting an error with the connection to the specified service, PPP MA failed to
reset that connection. This is an internal error. It requires a restart of the process for recovery.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-873
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_EVC_EVM_HANDLER
connection: [chars]
Error registering for data events on ’[chars]’
Explanation During initialization, PPP MA failed to register for input or output notifications for the
specified service. This is an internal error. It requires a restart of the process for recovery.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PPP_MA-4-ERR_EVC_GET_FD
connection: [chars]
Error retrieving the Connection ID from the ’[chars]’
Explanation PPP MA failed to retrieve the file descriptor associated with the specified service. This
is an internal error.
Recommended Action Consider restarting the PPP MA process. Copy the error message exactly as it
appears on the console or in the system log, call your Cisco technical support representative and
provide the representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_EVC_NOTIFY
connection: [chars]
Error registering for critical events on ’[chars]’
Explanation During initialization, PPP MA failed to register for essential notifications regarding the
state of the connection for the specified service. This is an internal error. It requires a restart of the
process for recovery.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PPP_MA-4-ERR_EVC_OPEN
Error opening ’[chars]’ connection: [chars]
Explanation PPP MA failed to open a connection to an essential service during initialization. This is
an internal error. It requires a restart of the process for recovery.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-874
OL-23348-01
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_EVM_ATTACH
[chars]
Failed to register a handler for ’[chars]’ messages:
Explanation PPP MA failed to register a handler for the specified class of event. This is an
initialization error and implies that PPP MA will not be able to operate correctly. The PPP MA
process will abort and be restarted in an attempt to recover. The cause may be a resource starvation
problem but is most likely to be an internal programming error. The error message should give more
details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Restart the PPP MA process. *RECUR*
Error Message
%L2-PPP_MA-4-ERR_EVM_CREATE
Error creating the PPP MA Event Manager: [chars]
Explanation PPP MA failed to create its Event Manager which is a critical resource for the operation
of the process. This error may be caused by low memory resources. The process will abort and be
restarted in an attempt to recover.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *SUPPORT*
Error Message
%L2-PPP_MA-4-ERR_EVM_SEND
Failed to send ’[chars]’: [chars]
Explanation PPP MA failed to send the specified message. The cause may be a resource starvation
problem but is most likely to be an internal programming error. The error message should give more
details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Restart the affected PPP MA process. *RECUR*
Error Message
%L2-PPP_MA-4-ERR_EVQ_CREATE
Error creating event queue for ’[chars]’: [chars]
Explanation This is an unexpected error. The PPP MA process will attempt to recover by restarting.
The cause may be a resource starvation problem. The error message should provide more details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-875
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_EVQ_DEQUEUE
Error dequeuing event for ’[chars]’: [chars]
Explanation This is an unexpected error. The PPP MA process will attempt to recover by restarting.
The cause may be a resource starvation problem. The error message should provide more details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*
Error Message
%L2-PPP_MA-4-ERR_EVQ_ENQUEUE
Error queuing event for ’[chars]’: [chars]
Explanation This is an unexpected error. The PPP MA process will attempt to recover by restarting.
The cause may be a resource starvation problem. The error message should provide more details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*
Error Message
%L2-PPP_MA-4-ERR_IMC
Unexpected IfMgr error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error communicating with Interface Manager. The error
message describes what operation has failed and why it failed. The most likely reason for this is a
temporary connection problem with the Interface Manager Control Server, but the error could also
be caused by low memory resource or programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the
process may help. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_IMC_IF
[chars]: [chars]
CH[hex]: Unexpected IfMgr error encountered whilst
Explanation PPP MA encountered an error on a particular interface whilst communicating with
Interface Manager. The error message describes what operation has failed and why it failed. The
most likely reason for this is a temporary connection problem with the Interface Manager Control
Server, but the error could also be caused by low memory resource or programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the
process may help. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-876
OL-23348-01
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_IP_ARM
Failed to [chars] [chars]: [chars]
Explanation IPCP encountered an error using the IP-ARM API. The error message describes what
operation failed. This may be a resource starvation problem or an internal programming error.
Recommended Action Restart the local ipv4_ma process and/or the ppp_ma process. Reduce other
system activity to ease memory demands. If conditions warrant, upgrade to a larger memory
configuration. *RECUR*.
Error Message
%L2-PPP_MA-4-ERR_IPCP_OPTS_INCONSISTENT
inconsistent options: [chars]
CH[hex]: IPCP has negotiated
Explanation PPP MA has negotiated inconsistent IPCP options. The message details which options
are inconsistent. IPCP will be brought up, but the inconsistencies could cause problems. The most
likely reason for this is a misconfiguration, either locally or on the peer.
Recommended Action Consider changing the relevant configuration either locally or on the peer.
Error Message
%L2-PPP_MA-4-ERR_IPCP_SCAN_IF
continuing: [chars]
CH[hex]: Failed to scan for configuration,
Explanation PPP MA encountered an error when scanning for IPCP configuration. The error
message describes what operation has failed and why it failed. The most likely reason for this is a
connection problem with the SubDB service, but the error could also be caused by low memory
resources or programming error.
Recommended Action Consider restarting the PPP MA process. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_IPHC
Unexpected IPHC error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error communicating with IPHC MA. The error message
describes what operation has failed and why it failed. The most likely reason for this is a temporary
connection problem with the IPHC MA, but the error could also be caused by low memory resource
or programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the
process may help. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-877
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_IPHC_CONFIG
CH[hex]: Invalid IPHC config received: [chars]
Explanation PPP MA received invalid or unsupported IPHC config for this interface. The error
message describes which piece of config is invalid. The most likely reason for this is incorrect IPHC
user configuration.
Recommended Action Check that the IPHC user configuration is valid and supported.
Error Message
%L2-PPP_MA-4-ERR_L2VPN
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error communicating with the L2VPN server. The error
message describes what operation has failed and why it failed. The most likely reason for this is a
temporary connection problem with the L2VPN server, but the error could also be caused by low
memory resource or programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the
process may help. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_LAS
Failed to [chars] [chars]: [chars]
Explanation IPV6CP encountered an error using the LAS API. The error message describes what
operation failed. This may be a resource starvation problem or an internal programming error.
Recommended Action Restart the local ipv6_ma process and/or the ppp_ma process. Reduce other
system activity to ease memory demands. If conditions warrant, upgrade to a larger memory
configuration. *RECUR*.
Error Message
%L2-PPP_MA-4-ERR_LTRACE
buffer: [chars]
Unexpected error encountered whilst [chars] the [chars]
Explanation PPP MA encountered an error using the Lightweight Tracing service. The error message
describes what operation has failed and why it failed. This is a fatal error and the PPP MA process
cannot continue. It will abort and subsequently be restarted by SysMgr in an attempt to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-878
OL-23348-01
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_MEM_ALLOC
Failed to allocate [unsigned int] bytes for ’[chars]’
Explanation The process failed to allocate memory for the specified resource.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
Error Message
%L2-PPP_MA-4-ERR_MGD_TIMER
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an unexpected error using the Managed Timer library. This is
most likely to be due to a low memory condition but may also be an internal programming error. The
error message should provide more information about the cause.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Consider restarting the PPP MA process. *RECUR*.
Error Message
%L2-PPP_MA-4-ERR_PAK
exiting.
Error handling pakman corruption problem: [chars]. Process
Explanation The connection to packet manager was errored and the attempt to recover failed.
Restarting the process should resolve the problem.
Recommended Action Restart the ppp_ma process. If the message recurs, copy the error message
exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_PLAT_PROPS
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error communicating with the Platform Properties DLL. The
error message describes what operation has failed and why it failed. This will either have occurred
because the Platform DLL failed to be properly initialized, or because of some error occurring in the
platform dependent code.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the
process may help. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-879
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_RIB
Unexpected error encountered whilst [chars]
Explanation PPP MA encountered an error using the RIB client library. The error message describes
what operation has failed and why it failed. The most likely reason for this is a connection problem
with the RIB, but the error could also be caused by low memory resources or programming error.
Recommended Action Consider restarting the PPP MA process. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_SSO_ALERT
[chars]
CH[hex]: Incompatible SSRP replicated state received:
Explanation PPP MA received replicated SSRP state for this interface for either which is
incompatible with the local config, as identified in the error message. This means the replicated state
will not be used to preprogram the session.
Recommended Action Check that the configuration on the Active and Standby sides of the SSRP
channel is consistent. The error message should indicate which particular piece of config there may
be problems with.
Error Message
%L2-PPP_MA-4-ERR_SSRP
Unexpected SSRP error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error communicating with SSRP. 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 SSRP, but the error could also be caused by low memory resource or programming
error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the
process may help. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_SUBDB
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the SubDB service. The error message describes
what operation has failed and why it failed. The most likely reason for this is a connection problem
with the SubDB server, but the error could also be caused by low memory resources or programming
error.
Recommended Action Consider restarting the PPP MA process. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-880
OL-23348-01
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_SUBDB_IF
[chars]
CH[hex]: Unexpected error encountered whilst [chars]:
Explanation PPP MA encountered an error using the SubDB service. The error message describes
what operation has failed and why it failed. The most likely reason for this is a connection problem
with the SubDB server, but the error could also be caused by low memory resources or programming
error.
Recommended Action Consider restarting the PPP MA process. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_SYSDB
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the SysDB service. The error message describes
what operation has failed and why it failed. The most likely reason for this is a connection problem
with the SysDB server, but the error could also be caused by low memory resources or programming
error.
Recommended Action Consider restarting the PPP MA process. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_SYSMGR
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error whilst communicating with SysMgr. The error message
describes what operation has failed and why it failed. This is a fatal error and the PPP MA process
will abort and be restarted to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PPP_MA-4-ERR_SYSMGR_MDR
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error whilst communicating with SysMgr. The error message
describes what operation has failed and why it failed. Sysmgr will take action to recover if
appropriate. It is possible that this error has occurred after MDR. If so then the recovery may require
a cold reload of the card
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-881
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_THREAD Unexpected pthread error encountered for ’[chars]’
thread whilst [chars]: [chars]
Explanation PPP MA encountered an unexpected error performing a pthread operation. The process
will restart to attempt to recover. This is possibly due to a low memory condition but may also be
an internal programming error. The error message should provide more information about the cause.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*.
Error Message
%L2-PPP_MA-4-ERR_THREAD_COND
[chars]: [chars]
Unexpected condition error encountered whilst
Explanation PPP MA encountered an unexpected error performing a condition operation. The
process may restart to attempt to recover. This is possibly due to a low memory condition but may
also be an internal programming error. The error message should provide more information about
the cause.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*.
Error Message
%L2-PPP_MA-4-ERR_THREAD_CREATE
Failed to create ’[chars]’ thread: [chars]
Explanation PPP MA encountered an unexpected error creating a new thread. The process will restart
to attempt to recover. This is possibly due to a low memory condition but may also be an internal
programming error. The error message should provide more information about the cause.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*.
Error Message
%L2-PPP_MA-4-ERR_THREAD_MUTEX
[chars]
Unexpected mutex error encountered whilst [chars]:
Explanation PPP MA encountered an unexpected error performing a mutex operation. The process
may restart to attempt to recover. This is possibly due to a low memory condition but may also be
an internal programming error. The error message should provide more information about the cause.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-882
OL-23348-01
Layer 2 Messages
PPP_MA Messages
Error Message
%L2-PPP_MA-4-ERR_UNSUPPORTED_PROTOCOL
protocol [hex]
[chars] received packet with unsupported
Explanation PPP MA received a packet with a protocol id, and was not recognized by the receiving
control protocol. This error message indicates that a subsystem is incorrectly delivering packets to
an inappropriate PPP control protocol, the packets are dropped.
Recommended Action In many cases, the message will indicate that an unsupported protocol is not
being handled correctly and PPP is not protocol rejecting the given protocol. Generally this won’t
cause problems if the mishandled and dropped packet is for a protocol that isn’t running anyway. If
the message recurs, copy the error message exactly as it appears on the console or in the system log,
call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PPP_MA-4-ERR_WAVL_INIT
IDBs: [chars].
Error initializing the WAVL tree used to store PPP MA
Explanation PPP MA encountered an unexpected error which prevents it from functioning. This
error may be caused by low memory resources. The process will abort and be restarted in an attempt
to recover.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*
Error Message
%L2-PPP_MA-6-ERR_EVC_DESTROY
Error destroying ’[chars]’ connection: [chars]
Explanation During process termination PPP MA failed to destroy a connection to a service provided
by another process. This is an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PPP_MA-6-ERR_EVM_EVENT_BLOCK
[chars]
Error blocking waiting for an event to process:
Explanation This is an unexpected error. The PPP MA process may recover by itself, or it may need
to be restarted to recover.
Recommended Action Restart the affected PPP MA process. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-883
Layer 2 Messages
PPP_NETIO Messages
Error Message
%L2-PPP_MA-6-ERR_EVQ_DESTROY
Error destroying event queue for ’[chars]’: [chars]
Explanation During process termination PPP MA failed to destroy an event queue. The process will
terminate regardless so there should be no lasting problems.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
PPP_NETIO Messages
Error Message
%L2-PPP_NETIO-3-ERR_INTF_INIT
CH[hex]: [chars]%s
Failure initializing the PPP NetIO datapath for
Explanation The PPP NetIO DLL failed to initialize the datapath for processing PPP packets on a
particular interface because of an unexpected error. The message includes the exact cause of the
failure. As a result, the capsulation will be unloaded from the interface and the interface will not be
able to send or receive any PPP packets. One possible reason for the error is a low memory
condition, particularly if the failure was in creating the interface descriptor.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration., and then remove and reconfigure the PPP encapsulation
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-PPP_NETIO-4-ERR_INIT
Failure [chars] in the PPP NetIO DLL: [chars]
Explanation A failure occurred during an initialization operation in the PPP NetIO DLL. If this
occurred 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 Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-884
OL-23348-01
Layer 2 Messages
PPP_SOCK Messages
Error Message
%L2-PPP_NETIO-4-PAK_DROP
Dropping [chars] packet on [chars] ([chars])
Explanation The PPP NetIO DLL has been forced to drop a packet because of an unexpected error.
The error message describes the reason for the drop.
Recommended Action The system may recover by itself. If it doesn’t then the error message will recur.
In this case consider restarting the NetIO process on the affected linecard. If the error messages
continue after restarting NetIO 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-PPP_NETIO-5-SUBBLOCK_VERSION Incompatible subblock version during upgrade.
Data has version [unsigned int], but the version supported is [unsigned int]
Explanation When the PPP NetIO DLL was upgraded the existing data version was incompatible
with the new software. NetIO will be restarted to recover the appropriate state.
Recommended Action This is not a problem, the message is just to explain why NetIO has restarted.
PPP_SOCK Messages
Error Message
%L2-PPP_SOCK-3-ERR_MEM_ALLOC
Unable to allocate [unsigned int] bytes
Explanation Not enough memory was available for the operation to complete.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
Error Message
%L2-PPP_SOCK-3-ERR_SYSMGR
Error: [chars]
Failure communicating readiness to System Manager.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-885
Layer 2 Messages
PPP_SOCK Messages
Error Message
%L2-PPP_SOCK-4-ERR_EVM_EVENT_BLOCK
Error in event loop: [chars]
Explanation An error occurred in the event loop. The process will restart which should recover the
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-PPP_SOCK-4-ERR_LTRACE_INIT
[chars]
Failed to initialize the ltrace buffer. Error:
Explanation The buffer used for tracing could not be allocated. The process will be restarted.
Recommended Action The most likely cause of a problem is not enough memory. Reduce other
system activity to ease memory demands. If conditions warrant, upgrade to a larger memory
configuration.
Error Message
%L2-PPP_SOCK-4-ERR_PAKMAN Could not clean up and restart pakman connection.
Error: [chars]. Control packet I/O will fail so restarting the socket process.
Explanation An unknown error occurred after a pakman disconnect event. Restarting the socket
process should have resolved the problem.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PPP_SOCK-4-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-886
OL-23348-01
Layer 2 Messages
PPPOE_EA Messages
PPPOE_EA Messages
Error Message
%L2-PPPOE_EA-4-ERR_EVC_ERROR
Error resetting IMP connection: [chars]
Explanation After detecting an error with the IMP connection, PPPoE EA failed to reset that
connection. This is an internal error. It requires a restart of the process for recovery.
Recommended Action *SUPPORT*
Error Message
%L2-PPPOE_EA-4-ERR_EVM_EVENT_BLOCK
The PPPoE EA process will restart
Error encountered in the event loop: [chars].
Explanation An error occurred in the event loop. The process will restart which should recover the
situation.
Recommended Action *RECUR*
Error Message
%L2-PPPOE_EA-4-ERR_INIT Failure during initialization of the [chars]. Error
[chars]. The PPPoE EA process will restart
Explanation A failure occurred during the initialization of the process. The process will restart which
should recover the situation.
Recommended Action *RECUR*
Error Message
%L2-PPPOE_EA-4-ERR_MEM_ALLOC
’[chars]’
Failed to allocate [unsigned int] bytes for
Explanation The process failed to allocate memory for the specified resource.
Recommended Action *REDUCE*
Error Message
%L2-PPPOE_EA-4-ERR_PLATFORM_INIT Failure during initialization of the platform
DLL. Error [chars]. PPPoE EA needs to be restarted to recover from this error.
Explanation The PPPoE EA Platform DLL failed to initialize. This means that PPPoE will be unable
to program the hardware. This error requires a restart of the process for recovery.
Recommended Action *RECUR*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-887
Layer 2 Messages
PPPOE_GBL_CFG Messages
Error Message
%L2-PPPOE_EA-4-ERR_RWMGR
Unexpected error whilst [chars]: [chars]
Explanation PPPoE EA encountered an error communicating with Rewrite 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 Rewrite Manager Server process, but the error could also be
caused by low memory resource or programming error.
Recommended Action In many cases, PPPoE EA 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-PPPOE_EA-6-ERR_IMP_MULTIPLE_NTFCNS CH[hex]: Multiple [chars] notifications
received in a single batch from improxy
Explanation A batch from IMProxy contained multiple notifications for a single interface. This
should not occur but the situation has been recovered successfully by the PPPoE EA. No problems
should be seen as a result.
Recommended Action *NONE*
PPPOE_GBL_CFG Messages
Error Message
%L2-PPPOE_GBL_CFG-4-ERR_DBG_TRACE
trace: [chars]
Failed to initialize the PPPoE GBL debug and
Explanation PPPoE MA encountered an error initializing its Debug and Trace The error message
describes what operation has failed and why it failed. This is a fatal error and the PPPoE GBL
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-PPPOE_GBL_CFG-4-ERR_EVM_CREATE
[chars]
Error creating the PPPoE GBL Event Manager:
Explanation PPPoE GBL failed to create its Event Manager which is a critical resource for the
operation of the process. This error may be caused by low memory resources. The process will abort
and be restarted in an attempt to recover.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *SUPPORT*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-888
OL-23348-01
Layer 2 Messages
PPPOE_MA Messages
PPPOE_MA Messages
Error Message
%L2-PPPOE_MA-2-ERR_INVALID_CB
Invalid [chars] callback: [chars]
Explanation PPPoE MA received an invalid callback from another process. The error message
describes why it is invalid. This is most likely to be a programming error, either in PPPoE or in one
of the processes it interacts with.
Recommended Action PPPoE MA should recover by itself.
Error Message
%L2-PPPOE_MA-2-ERR_UNEXPECTED_CB
[chars] state
Unexpected [chars] callback, when session in
Explanation PPPoE MA received an asynchronous callback from another process when the session
was in an incorrect state. The error message describes which callback was received. This is most
likely to be a programming error, either in PPPoE or in one of the processes it interacts with.
Recommended Action PPPoE MA should recover by itself.
Error Message
%L2-PPPOE_MA-2-ERR_UNEXPECTED_CLEANUP
[chars] state
Unexpected [chars], when session in
Explanation PPPoE MA is trying to cleanup a session when it is in an unexpected state. The error
message describes which state it was in, and what was triggering the cleanup. This is most likely to
be a programming error, either in PPPoE or in one of the processes it interacts with.
Recommended Action PPPoE MA should recover by itself.
Error Message
%L2-PPPOE_MA-4-ERR_AAA_ATTR
Unexpected error encountered whilst [chars]: [chars]
Explanation PPPoE MA encountered an error using AAA attribute APIs. 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*.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-889
Layer 2 Messages
PPPOE_MA Messages
Error Message
%L2-PPPOE_MA-4-ERR_AAA_CONN_DOWN
connection down
Unexpected [chars] received while AAA
Explanation PPPoE MA received a notification from AAA while the connection was down. The most
likely reason for this 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-PPPOE_MA-4-ERR_AAA_SESSION
[chars]
Unexpected error encountered whilst [chars]:
Explanation PPPoE MA encountered an error using AAA session APIs. 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-PPPOE_MA-4-ERR_AAA_STALE_SESSION Disconnecting subscriber session with
sub_label [hex] failed. The session should be cleared manually using the ’clear
subscriber’ command: [chars]
Explanation PPPoE MA failed to call AAA to disconnect a session. The session may now need to be
cleared manually using the ’clear subscriber’ CLI command. The most likely reason for this a low
memory condition but the error could also be caused by a programming error.
Recommended Action Run ’clear subscriber’ for the specified session.
Error Message
%L2-PPPOE_MA-4-ERR_ATTR
Unexpected error encountered whilst [chars]: [chars]
Explanation PPPoE MA encountered an error using vAccess Attribute APIs. 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*.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-890
OL-23348-01
Layer 2 Messages
PPPOE_MA Messages
Error Message
%L2-PPPOE_MA-4-ERR_BBA_CONFIG
BBA-Group config item
Unexpected config-value received for the ’[chars]’
Explanation PPPoE MA received an unexpected config-value for a piece of BBA-group config
through SysDB. The error message describes which config item was invalid. The most likely reason
for this a programming error in the verifier for the config item.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-PPPOE_MA-4-ERR_CHKPT
Unexpected error encountered whilst [chars]: [chars]
Explanation PPPoE 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-PPPOE_MA-4-ERR_CHKPT_CORRUPT
[chars]
Corrupt [chars] checkpoint record found:
Explanation Whilst restoring one of its checkpoint tables PPPoE MA found a corrupt checkpoint
entry. The entry will be ignored and so the relevant PPPoE session will be 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-PPPOE_MA-4-ERR_CHKPT_DUPLICATE
CH[hex]
Duplicate [chars] checkpoint record found for
Explanation Whilst restoring one of its checkpoint tables PPPoE MA found multiple entries for the
same interface. PPPoE 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-891
Layer 2 Messages
PPPOE_MA Messages
Error Message
%L2-PPPOE_MA-4-ERR_DBG_TRACE
[chars]
Failed to initialize the PPPoE MA debug and trace:
Explanation PPPoE MA encountered an error initializing its Debug and Trace The error message
describes what operation has failed and why it failed. This is a fatal error and the PPPoE MA process
cannot continue. It will abort and subsequently be restarted by SysMgr in an attempt to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PPPOE_MA-4-ERR_DEBUG
Unexpected error encountered whilst [chars]: [chars]
Explanation PPPoE MA encountered an error using the debug service. The error message describes
what operation has failed and why it failed. The error could be caused by low memory resource or
programming error.
Recommended Action In many cases, PPPoE MA will recover by itself. If it does not then restarting
the process may help. Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*.
Error Message
%L2-PPPOE_MA-4-ERR_EVC_ERROR
Error resetting IMC connection: [chars]
Explanation After detecting an error with the connection to the specified service, PPPoE 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-PPPOE_MA-4-ERR_EVM_ATTACH
messages: [chars]
Failed to register a handler for ’[chars]’
Explanation PPPoE MA failed to register a handler for the specified class of event. This is an
initialization error and implies that PPPoE MA will not be able to operate correctly. The PPPoE MA
process will abort and be restarted in an attempt to recover. The cause may be a resource starvation
problem but is most likely to be an internal programming error. The error message should give more
details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Restart the PPPoE MA process. *RECUR*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-892
OL-23348-01
Layer 2 Messages
PPPOE_MA Messages
Error Message
%L2-PPPOE_MA-4-ERR_EVM_CREATE
Error creating the PPPoE MA Event Manager: [chars]
Explanation PPPoE MA failed to create its Event Manager which is a critical resource for the
operation of the process. This error may be caused by low memory resources. The process will abort
and be restarted in an attempt to recover.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *SUPPORT*
Error Message
%L2-PPPOE_MA-4-ERR_EVM_EVENT_BLOCK
The PPPoE MA process will restart
Error encountered in the event loop: [chars].
Explanation An error occurred in the event loop. The process will restart which should recover the
situation.
Recommended Action *RECUR*
Error Message
%L2-PPPOE_MA-4-ERR_EVM_SEND
Failed to send ’[chars]’: [chars]
Explanation PPPoE MA failed to send the specified message. The cause may be a resource starvation
problem but is most likely to be an internal programming error. The error message should give more
details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Restart the affected PPPoE MA process. *RECUR*
Error Message
%L2-PPPOE_MA-4-ERR_IMC
Unexpected error encountered whilst [chars]: [chars]
Explanation PPPoE MA encountered an error using vAccess IMC APIs. 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-PPPOE_MA-4-ERR_INSERT_GLOBAL
tree
Interface CH[hex] already in global session
Explanation PPPoE MA tried to insert an interface into the global session tree which was already
there. The error is probably caused by a programming error.
Recommended Action PPPoE MA should recover by itself.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-893
Layer 2 Messages
PPPOE_MA Messages
Error Message
%L2-PPPOE_MA-4-ERR_MEM_ALLOC
’[chars]’
Failed to allocate [unsigned int] bytes for
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-PPPOE_MA-4-ERR_MGD_TIMER
[chars]
Unexpected error encountered whilst [chars]:
Explanation PPPoE MA encountered an unexpected error using the Managed Timer library. This is
most likely to be due to a low memory condition but may also be an internal programming error. The
error message should provide more information about the cause.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Consider restarting the PPPoE MA process. *RECUR*.
Error Message
%L2-PPPOE_MA-4-ERR_REGCOMP
[chars]
Failed to compile regular expression ’[chars]’ for
Explanation The process failed to compile the given regular expression.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
Error Message
%L2-PPPOE_MA-4-ERR_SUBDB
Unexpected error encountered whilst [chars]: [chars]
Explanation PPPoE MA encountered an error using SubDB 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-PPPOE_MA-4-ERR_SYSDB
Unexpected error encountered whilst [chars]: [chars]
Explanation PPPoE MA encountered an error using vAccess SysDB APIs. 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*.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-894
OL-23348-01
Layer 2 Messages
PPPOE_MA Messages
Error Message
%L2-PPPOE_MA-4-ERR_TEST_ONLY
testing: [chars]
An event was hit that should only occur during
Explanation PPPoE MA hit some code that it shouldn’t be possible to hit except during testing. This
must be related to 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-PPPOE_MA-4-ERR_TIMER_WHEEL
[chars]
Unexpected error encountered whilst [chars]:
Explanation PPPoE MA encountered an unexpected error using the Timer Wheel 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 PPPoE MA process. *RECUR*.
Error Message
%L2-PPPOE_MA-4-ERR_TUPLE
Failed to unpack tuple for ’[chars]’
Explanation The process failed to unpack a tuple.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
Error Message
%L2-PPPOE_MA-4-ERR_VACCESS
Unexpected error encountered whilst [chars]: [chars]
Explanation PPPoE MA encountered an error using vAccess APIs. 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*.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-895
Layer 2 Messages
PRECAM Messages
PRECAM Messages
Error Message
%L2-PRECAM-2-HW_RESOURCE_FAILURE Failed to allocate hardware resources for
feature [chars] on ifh [hex], subtype [dec], stage [chars], instance [chars], loc
[dec], error: [dec] ([chars])
Explanation A runtime error occurred while trying to allocate hardware resources for configuring a
feature. The reason for the failure is also displayed.
Recommended Action Please call Cisco Support with the error information and provide running
configuration, configuration steps performed before the message was observed, linecard version and
output of commands under: ’show controller pse [ingress|egress] precam ... ’ Copy the error message
exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
PSE_UIDB Messages
Error Message
%L2-PSE_UIDB-7-ERR_INIT
[chars] failed due to [chars]
Explanation Initialization of uidb_svr process has failed due to one of the following reasons: 1)
Failed to create server context. 2) Failed to get scheduler parameters. 3) Failed to initialize event
manager. This would prevent process from receiving events. 4) Failed to register with debug. This
would prevent process from logging debug messages. 5) Failed to bind UIDB server with MIPC
server. This is needed to program features in hardware. 6) Failed to connect to PLIM asic processes.
This is needed to program features in hardware. 7) Failed to initialize checkpoint. This is needed to
checkpoint UIDB data to restore on process restart. 8) Failed to allocate, initialize and checkpoint
shadow memory. This is needed to store and restore UIDB internal data. 9) Failed to get metro asic
version. 10) Failed to attach event handlers needed to handle LWM messages. This is needed to
enable/disable various features in hardware. 11) Various Sysdb or EDM failures 12) event_block
failed. This indicates process has encountered unexpected error while waiting for events.
Recommended Action No action is required. Process will be restarted. If not recovered, it’s a fatal
condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to
a larger memory configuration.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-896
OL-23348-01
Layer 2 Messages
PSE Messages
PSE Messages
Error Message
%L2-PSE-2-CRIT_EXIT
Exit on error: [chars]: Caused by [chars]
Explanation An critical error occurred in PSE Driver which requires exiting (and, hence, restarting)
the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PSE-2-CRIT_EXIT
Exit on error: [chars]: Caused by [chars]
Explanation An critical error occurred in PSE Driver which requires exiting (and, hence, restarting)
the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PSE-2-MIPC_STUCK
[chars] direction. Data: ([chars])
Explanation Inter-processor communication to the Metro is stuck.
Recommended Action *None*
Error Message
%L2-PSE-2-NODE_BRINGDOWN
[chars] device: Caused by [chars]
Explanation The PSE driver was unable to perform a critical function and must trigger a node
bringdown to effect recovery.
Recommended Action No action is required.
Error Message
%L2-PSE-2-NODE_BRINGDOWN
[chars] device: Caused by [chars]
Explanation The PSE driver was unable to perform a critical function and must trigger a node
bringdown to effect recovery.
Recommended Action No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-897
Layer 2 Messages
PSE Messages
Error Message
%L2-PSE-3-DMA_ERROR_MSG
Instance [dec]: [chars] [chars] [hex]
Explanation This is a error message in the PSE Driver to indicate DMA operation failed
Recommended Action No action is required.
Error Message
%L2-PSE-3-ERROR_MSG
[chars]
Explanation This is a debug message in the PSE Driver to indicate an operation or condition.
Recommended Action No action is required.
Error Message
%L2-PSE-3-HEALTH_MONITOR_ERROR_MSG
[chars]
Explanation PSE driver health monitor detected error conditions
Recommended Action No action is required.
Error Message
%L2-PSE-3-INIT_ERROR_MSG
Instance [dec]: [chars]
Explanation This is a debug message in the PSE Driver to indicate an operation or condition.
Recommended Action No action is required.
Error Message
%L2-PSE-3-INTERNAL_ERR
Error: [chars]: Err equals [dec]
Explanation A driver internal error occurred which involves exiting the process. %s - indicates the
reason for the failure. %d - is the error condition.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-898
OL-23348-01
Layer 2 Messages
PSE Messages
Error Message
%L2-PSE-3-INVALID_COUNT
Error: [chars]: count equals [dec]
Explanation This is a error message in the PSE Driver to indicate either anomalies which are not
service impacting. Some of the messages may indicate a failure to allocate resources needed by
applications. In many cases these messages must not keep appearing after the temporary situation is
resolved. %s - indicates the reason for the failure. %d - is the count.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PSE-4-COLD_RESET_FAILED
[chars] device: Caused by [chars]
Explanation This is an error message in the PSE Driver to indicate that it failed to perform cold reset
of specified pse instance due to the specified reason.
Recommended Action No action is required.
Error Message
%L2-PSE-4-COLD_RESET_FAILED
[chars] device: Caused by [chars]
Explanation This is an error message in the PSE Driver to indicate that it failed to perform cold reset
of specified pse instance due to the specified reason.
Recommended Action No action is required.
Error Message
%L2-PSE-4-ERRRATE_EXCEED_FAST
[chars]
[chars] device: High rate of ASIC errors of type:
Explanation This is an error message in the PSE Driver to indicate that a high rate of specified errors
is being detected.
Recommended Action No action is required.
Error Message
%L2-PSE-4-ERRRATE_EXCEED_FAST
[chars]
[chars] device: High rate of ASIC errors of type:
Explanation This is an error message in the PSE Driver to indicate that a high rate of specified errors
is being detected.
Recommended Action No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-899
Layer 2 Messages
PSE Messages
Error Message
%L2-PSE-4-ERRRATE_EXCEED_GLACIAL
type: [chars]
[chars] device: High rate of ASIC errors of
Explanation This is an error message in the PSE Driver to indicate that a high rate of specified errors
is being detected.
Recommended Action No action is required.
Error Message
%L2-PSE-4-ERRRATE_EXCEED_GLACIAL
type: [chars]
[chars] device: High rate of ASIC errors of
Explanation This is an error message in the PSE Driver to indicate that a high rate of specified errors
is being detected.
Recommended Action No action is required.
Error Message
%L2-PSE-4-PROTO_HW_VERSION [chars] PSE ASIC prototype hardware detected. This
version ([unsigned int]) is not supported.
Explanation This message indicates that the version of the PSE ASIC is a prototype, and it is not
supported by the s/w release.
Recommended Action No action is required.
Error Message
%L2-PSE-4-PROTO_HW_VERSION [chars] PSE ASIC prototype hardware detected. This
version ([unsigned int]) will be unsupported in future releases.
Explanation This message indicates that the version of the PSE ASIC is a prototype, and will be
unsupported in future s/w releases.
Recommended Action No action is required.
Error Message
%L2-PSE-4-WARM_RESET_FAILED
[chars] device: Caused by [chars]
Explanation This is an error message in the PSE Driver to indicate that it failed to perform warm
reset of specified pse instance due to the specified reason.
Recommended Action No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-900
OL-23348-01
Layer 2 Messages
PSE Messages
Error Message
%L2-PSE-4-WARM_RESET_FAILED
[chars] device: Caused by [chars]
Explanation This is an error message in the PSE Driver to indicate that it failed to perform warm
reset of specified pse instance due to the specified reason.
Recommended Action No action is required.
Error Message
%L2-PSE-5-ERR_CONT
Continuing execution: [chars]: Caused by [chars]
Explanation This message indicates an error occurred beyond which execution of the pse_driver may
continue, attempting to effect recovery or work-around internally, minimizing loss of
information/functionality.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PSE-5-ERR_CONT
Continuing execution: [chars]: Caused by [chars]
Explanation This message indicates an error occurred beyond which execution of the pse_driver may
continue, attempting to effect recovery or work-around internally, minimizing loss of
information/functionality.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PSE-5-TCAM_MISMATCH_COMPLETED
[chars]
[chars]: troubleshooting data [chars]saved:
Explanation This message indicates completion of the automatic correction following the detection
of a mismatch between the LC CPU software view of TCAM content, and what was actually found
in hardware. The system attempts to collect troubleshooting information concerning the mismatch;
however, should there be insufficient line card memory to do so, this information is not collected.
The text of the message indicates whether information was collected, along with the location of the
file containing the information.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-901
Layer 2 Messages
PSE Messages
Error Message
%L2-PSE-5-TCAM_MISMATCH_DETECTED
initiated
[chars] TCAM[dec]: mismatch detected, recovery
Explanation This message indicates the detection of an inconsistency between the LC CPU software
view of TCAM content, and what is actually found in hardware. Recovery is initiated automatically
upon detection of such a mismatch. Once recovery completes, troubleshooting information is
collected. Further messages, namely ’TCAM_MISMATCH_REPAIRED’ and then
’TCAM_MISMATCH_COMPLETED’, follow when the recovery and the data collection are
completed, respectively.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PSE-5-TCAM_MISMATCH_REPAIRED [chars] TCAM[dec]: mismatch corrected,
collecting troubleshooting information
Explanation This message indicates the completion of the automatic correction following the
detection of a mismatch between the LC CPU software view of TCAM content, and what was
actually found in hardware. It also marks the start of troubleshooting data collection, the end of
which will be indicated by a further ’TCAM_MISMATCH_COMPLETED’ log 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-PSE-6-INFO_MSG
[chars]
Explanation This is a informational message in the PSE Driver to indicate an operation.
Recommended Action No action is required.
Error Message
%L2-PSE-6-INFO_MSG
Info: [chars]
Explanation This is a Informational message in the PSE Driver to indicate an operation. %s indicates the informational message.
Recommended Action Debug message only. No action is required.
Error Message
%L2-PSE-6-INFO_MSG
[chars]
Explanation This is a informational message in the PSE Driver to indicate an operation.
Recommended Action No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-902
OL-23348-01
Layer 2 Messages
PSE Messages
Error Message
%L2-PSE-6-MP_INFO
[chars] [chars]
Explanation This is an informational message in the PSE Driver to indicate an event on maintenance
processor.
Recommended Action No action is required.
Error Message
%L2-PSE-7-DEBUG_MSG
[chars]
Explanation This is a debug message in the PSE Driver to indicate an operation or condition.
Recommended Action No action is required.
Error Message
%L2-PSE-7-DEBUG_MSG
[chars]
Explanation This is a debug message in the PSE Driver to indicate an operation or condition.
Recommended Action No action is required.
Error Message
%L2-PSE-7-ERR_EXIT
Exit on error: [chars]: Caused by [chars]
Explanation An error occurred in PSE Driver which requires exiting (and, hence, restarting) the
process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PSE-7-ERR_EXIT
Exit on error: [chars]: Caused by [chars]
Explanation An error occurred in PSE Driver which requires exiting (and, hence, restarting) the
process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-903
Layer 2 Messages
PSELIB Messages
Error Message
%L2-PSE-7-MP_CORE
MP Core File saved in [chars].
Explanation An error occurred in PSE MP Microcode Driver which required exiting (and, hence,
restarting) the process. This message records the location of the MP Core File.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-PSE-7-MP_CORE
MP Core File saved in [chars].
Explanation An error occurred in PSE MP Microcode Driver which required exiting (and, hence,
restarting) the process. This message records the location of the MP Core File.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
PSELIB Messages
Error Message
%L2-PSELIB-4-EXIT_ON_ERR
[chars]. Reason: [chars]
Explanation An error occurred in the PSE ASIC client library after which the client code cannot
continue. This error is encountered when a client module (e.g. cli command) has difficulty retrieving
information from the PSE driver. The root cause may be located in either hardware or software.
Recommended Action *RECUR*
QFP_ACL_EA Messages
Error Message
%L2-QFP_ACL_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 cpp_acl_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*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-904
OL-23348-01
Layer 2 Messages
QFP_BQS Messages
QFP_BQS Messages
Error Message
%L2-QFP_BQS-6-SRTMEMLOW_CLEAR CPP [dec] HW [chars]:[chars] schedule resources
recover from depletion - [dec]% available
Explanation CPP BQS HW schedule resources have recovered from critical 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-QFP_BQS-6-SRTMEMLOW_DECLARE
depleted - [dec]% available
CPP [dec] HW [chars]:[chars] schedule resources
Explanation CPP BQS HW schedule resources have dropped below critical 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.
QFP_DRIVER Messages
Error Message
%L2-QFP_DRIVER-2-HALT
[chars]([dec]) Interrupt : [chars] Seq:[dec] Halt bit set.
Explanation A Serious CPP hardware error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-3-ALLOCATE_NOTIFY
CPP[dec]: Failed to allocate data: ([chars]).
Explanation A function failed to allocate 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-905
Layer 2 Messages
QFP_DRIVER Messages
Error Message
%L2-QFP_DRIVER-3-CLEANUP_NOTIFY
Failed to cleanup data: ([chars]).
Explanation A function failed to cleanup 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-QFP_DRIVER-3-DESTROY_NOTIFY
Failed to destroy connection: ([chars]).
Explanation A function failed to destroy a connection.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-3-FATAL_ACQUIRE_LOCK
[chars].
([hex]) Failed to acquire memory lock -
Explanation Driver SW failed to acquire shared memory lock.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-3-FATAL_ATTACH
CPP[dec]: ([hex]) - Failed to attach [chars].
Explanation Device Failed to attach.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-3-FATAL_CREATE
[chars].
CPP[dec]: ([hex]) - Failed to create [chars] -
Explanation Driver failed to get device details.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-906
OL-23348-01
Layer 2 Messages
QFP_DRIVER Messages
Error Message
%L2-QFP_DRIVER-3-FATAL_ERR
Fatal error: [chars]: ErrCode equals [dec]
Explanation A fatal error occurred in CPP 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-QFP_DRIVER-3-FATAL_GET_DETAILS
details - [chars].
CPP[dec]: ([hex]) - Failed to get device
Explanation Driver failed to get device details.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-3-FATAL_INIT
[chars].
CPP[dec]: ([hex]) - Failed to initialize [chars] -
Explanation Driver failed to initialize a device.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-3-FATAL_INTERNAL
[chars].
CPP[dec]: ([hex]) Failed: internal SW error-
Explanation Driver failed to initialize a device.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-3-FATAL_MEM_CLEAR
[chars].
CPP[dec]: ([hex]) Failed to clear memory -
Explanation Driver failed to clear memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-907
Layer 2 Messages
QFP_DRIVER Messages
Error Message
%L2-QFP_DRIVER-3-FATAL_MEM_SIZE
- [chars].
CPP[dec]: ([hex]) Failed to acquire memory size
Explanation Driver SW failed to acquire the size of a block of memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-3-FATAL_MEM_WRITE
[chars].
CPP[dec]: ([hex]) Failed to write to memory
Explanation Driver failed to write to memory.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-3-FATAL_PLAT_DB
[chars].
CPP[dec]: ([hex]) - Platform failure accessing
Explanation Platform DB query 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-QFP_DRIVER-3-FATAL_RELEASE_LOCK
[chars]
([hex]) Failed to release memory lock -
Explanation Driver SW failed to release shared memory lock.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-3-FATAL_UNSUPPORT
TYPE:[dec]
CPP[dec]: ([hex]) Unsupported CPP type: CPP
Explanation Unsupported CPP 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-908
OL-23348-01
Layer 2 Messages
QFP_DRIVER Messages
Error Message
%L2-QFP_DRIVER-3-HOT [chars]([dec]) Interrupt : [chars] Seq:[dec] repeating
interrupt has been disabled.
Explanation A repeating hardware interrupt has been 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-QFP_DRIVER-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.
Error Message
%L2-QFP_DRIVER-3-INIT_NOTIFY_ID
CPP[dec]: 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.
Error Message
%L2-QFP_DRIVER-3-LOCKDOWN
[chars]([dec]) CPP Driver LOCKDOWN due to fatal error.
Explanation A fatal error has caused the driver to LOCKDOWN.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-3-TCAM_PERR
at offset [hex].
[chars]([dec]) TCAM Parity error TCAM device #[dec]
Explanation A Parity error has occurred in a TCAM device.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-909
Layer 2 Messages
QFP_DRIVER Messages
Error Message
%L2-QFP_DRIVER-3-TCAM_PERR_FAILURE [chars]([dec]) Failed to correct TCAM Parity
error. Parity error detection disabled.
Explanation Failed to correct a TCAM Parity error and further detection has been 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-QFP_DRIVER-3-WARN_ERR
Warning: [chars]: ErrCode equals [dec]
Explanation A non-fatal condition occurred in the CPP driver that may affect the functionality of
CPP.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_DRIVER-4-ADRSPC_LIMIT Address space limit [unsigned int] KB reached,
mapping block [chars] size [unsigned int] dynamically, over limit space: [unsigned
int] KB
Explanation The process indicated tried to map more of the Forwarding Engine’s address space than
was allocated for it. A slower access method will be used instead. This will lower the performance
of some operations which require accesses to the Forwarding Engine
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-QFP_DRIVER-6-ACCTRC128B Access CPP [dec] address [hex] (Blk/Off:[dec]/[hex])
[chars] [dec] bytes [hex]_[hex] flags [hex]
Explanation A CPP access was traced
Recommended Action No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-910
OL-23348-01
Layer 2 Messages
QFP_EXMEM Messages
Error Message
%L2-QFP_DRIVER-6-ACCTRC64B Access CPP [dec] address [hex] (Blk/Off:[dec]/[hex])
[chars] [dec] bytes [hex] flags [hex]
Explanation A CPP access was traced
Recommended Action No action is required.
Error Message
%L2-QFP_DRIVER-6-INTR
[chars]([dec]) Interrupt: [chars]
Explanation A CPP hardware interrupt has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
QFP_EXMEM Messages
Error Message
%L2-QFP_EXMEM-3-FATAL_ERROR
[chars]: [chars]
Explanation A fatal error occurred in CPP external memory manager 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-QFP_EXMEM-7-DEBUG_MSG
[chars]
Explanation This is a debug 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-911
Layer 2 Messages
QFP_FM Messages
QFP_FM Messages
Error Message
%L2-QFP_FM-6-FIELD_IGNORED Matching on field type [unsigned int] ([chars] value
[unsigned int] ([hex])) not supported for client [chars] ([unsigned int]), rule
oid: [chars], seqnos: [unsigned long long int], [unsigned long long int],
[unsigned long long int]: RULE *IGNORED*
Explanation User is trying to use a classification criterion not supported by the feature. For example,
user is trying to apply a with a class matching matched on an IPv6 ACL that contains a match on
flow-label. The entire rule (e.g. ACE) containing the unsupported criterion is ignored. In our
example, only the ACEs containing match on flow label are ignored. All other ACEs are still
downloaded to CPP.
Recommended Action No action is required.
QFP_IFM Messages
Error Message
%L2-QFP_IFM-3-FATAL_ERR
Fatal error: [chars]: ErrCode equals [dec]
Explanation A fatal error occurred in the CPP IFM Library.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-QFP_IFM-3-WARN_ERR
Warning: [chars]: ErrCode equals [dec]
Explanation A non-fatal condition occurred in the CPP IFM Library that may affect the functionality
of CPP.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-912
OL-23348-01
Layer 2 Messages
QFP_LPTS_EA Messages
QFP_LPTS_EA Messages
Error Message
%L2-QFP_LPTS_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 cpp_lpts_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*
QFP_MDM Messages
Error Message
%L2-QFP_MDM-3-FATAL_ERR
[chars]: Err equals [hex]
Explanation A fatal error occurred in CPP Infra Metadata Mgr 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-QFP_MDM-7-DEBUG_MSG
[chars]
Explanation This is a debug 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.
QFP_PFILTER_EA Messages
Error Message
%L2-QFP_PFILTER_EA-3-MSG_SEND_FAILED cpp_pfilter_ea: msg: [dec], retried: [dec]
time(s), failed to send, errno: [chars]
Explanation Unable to send a message to the CPP Pfilter 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-913
Layer 2 Messages
QFP_SBS Messages
QFP_SBS Messages
Error Message
%L2-QFP_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.
QFP_TCAM_RM Messages
Error Message
%L2-QFP_TCAM_RM-6-HIGH_WATER_MARK
limited.
CPP [dec] TCAM resources in the system is
Explanation The TCAM device has limited number of free cells left to allocate.
Recommended Action No action is required.
Error Message
%L2-QFP_TCAM_RM-6-LOW_WATER_MARK
CPP [dec] TCAM resource is sufficient.
Explanation The TCAM device has sufficient number of free cells left.
Recommended Action No action is required.
QFP_UIDB Messages
Error Message
%L2-QFP_UIDB-3-FATAL_ERROR
[chars]: [chars]
Explanation A fatal error occurred in uidb manager 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-914
OL-23348-01
Layer 2 Messages
QFP_XCONNECT Messages
Error Message
%L2-QFP_UIDB-7-DEBUG_MSG
[chars]
Explanation This is a debug 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.
QFP_XCONNECT Messages
Error Message
%L2-QFP_XCONNECT-3-XCONNECT_CONFIG_ERR Cannot configure xconnect port-forwarding
on [chars] if there are subinterfaces present with VLAN encaps. Remove all
subinterface configurations before configuring xconnect port-forwarding.
Explanation A main interface cannot be configured for xconnect port-forwarding if subinterfaces
with VLAN encaps are present.
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.
QM_E5 Messages
Error Message
%L2-QM_E5-3-SANITY_HEAD_DUMP
Dumping head: [chars]
Explanation To print packet dump.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information. This message is to dump head tail QELEM content in
error cases
Error Message
%L2-QM_E5-3-SANITY_RELOAD
[chars] : Card will be reset
Explanation There is buffer depletion of FreeQs.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information. This error message is just a warning message for
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-915
Layer 2 Messages
QM_E5 Messages
Buffer Depletion. The card will be reloaded after the time specified in the message, if the problem
persists. The dumped Queues and Queue Elements need to be evaluated to find the root-cause of the
problem
Error Message
%L2-QM_E5-3-SANITY_TAIL_DUMP
Dumping tail: [chars]
Explanation To print packet dump.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information. This message is to dump head tail QELEM content in
error cases
Error Message
%L2-QM_E5-3-SANITY_WARNING
QM Buffer Depletion: [chars]
Explanation There is buffer depletion of FreeQs.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information. This error message is just a warning message. The
dumped Queues and Queue Elements need to be evaluated to find the root-cause of the problem
Error Message
%L2-QM_E5-4-INTERRUPT
[chars]: [chars] : reg value [hex]
Explanation The queueing asic experienced an interrupt, and will be reset. After reset, normal
operation should resume.
Recommended Action Log the error. If the error persists after reset, contact support.
Error Message
%L2-QM_E5-4-INTERRUPT2
[chars]: [chars] : reg1 [hex]: reg2 [hex]
Explanation The queueing asic experienced an interrupt, and will be reset. After reset, normal
operation should resume.
Recommended Action Log the error. If the error persists after reset, contact support.
Error Message
%L2-QM_E5-7-INTERRUPT3
[chars]: [chars]: error_reg: [hex] error_info: [hex]
Explanation The queueing asic experienced an interrupt, and is non-fatal. In some cases its corrected
by software and remaining cases its occurrences logged.
Recommended Action Log the error.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-916
OL-23348-01
Layer 2 Messages
QM Messages
Error Message
%L2-QM_E5-7-INTERRUPT4
[chars]: [chars]: error_reg: [hex]
Explanation The queueing asic experienced an interrupt, and is non-fatal. In some cases its corrected
by software and remaining cases its occurrences logged.
Recommended Action Log the error.
Error Message
%L2-QM_E5-7-INTERRUPT5
[chars]: [chars]: error: [hex] error_reg: [hex]
Explanation The queueing asic experienced an interrupt, and is non-fatal. In some cases its corrected
by software and remaining cases its occurrences logged.
Recommended Action Log the error.
Error Message
%L2-QM_E5-7-INTERRUPT6 [chars]: [chars]: error: [hex] error_reg: [hex]
error_info: 0x[unsigned int]llx
Explanation The queueing asic experienced an interrupt, and is non-fatal. In some cases its corrected
by software and remaining cases its occurrences logged.
Recommended Action Log the error.
QM Messages
Error Message
%L2-QM-3-SANITY_RELOAD
[chars] : Card will be reset
Explanation There is buffer depletion of FreeQs.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information. This error message is just a warning message for
Buffer Depletion. The card will be reloaded after the time specified in the message, if the problem
persists. The dumped Queues and Queue Elements need to be evaluated to find the root-cause of the
problem
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-917
Layer 2 Messages
QUEUEING Messages
Error Message
%L2-QM-3-SANITY_WARNING
QM Buffer Depletion: [chars]
Explanation There is buffer depletion of FreeQs.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information. This error message is just a warning message. The
dumped Queues and Queue Elements need to be evaluated to find the root-cause of the problem
Error Message
%L2-QM-4-INTERRUPT
[chars]: [chars] : reg value [hex]
Explanation The queueing asic experienced an interrupt, and will be reset. After reset, normal
operation should resume.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
QUEUEING Messages
Error Message
%L2-QUEUEING-3-FATAL_ERR
[chars]: Err equals [dec]
Explanation A fatal error occurred in QUEUEING ASIC Driver which involves exiting the process.
The process will be respawned, but if it continues to fail the linecard will be reset, as the linecard
cannot operate without this process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
RSMLIB Messages
Error Message
%L2-RSMLIB-4-EXIT_ON_ERR
[chars]. Reason: [chars]
Explanation An error occurred in the PSE ASIC client library after which the client code cannot
continue. This error is encountered when a client module (e.g. cli command) has difficulty retrieving
information from the PSE driver. The root cause may be located in either hardware or software.
Recommended Action *RECUR*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-918
OL-23348-01
Layer 2 Messages
Serial Messages
Error Message
%L2-RSMLIB-4-EXIT_ON_ERR
[chars]. Reason: [chars]
Explanation An error occurred in the PSE ASIC client library after which the client code cannot
continue. This error is encountered when a client module (e.g. cli command) has difficulty retrieving
information from the PSE driver. The root cause may be located in either hardware or software.
Recommended Action *RECUR*
Serial Messages
Error Message
%L2-Serial-3-MTU_IMPOSE_FAILED
Failed to set MTU of [unsigned int] on [chars]
Explanation The specified MTU could not be applied on this interface.
Recommended Action No action is required.
Error Message
%L2-Serial-3-NULL_HW_FUNC
--
Explanation Failed to program the hardware.
Recommended Action No action is required.
Error Message
%L2-Serial-4-ALARM
[chars]: [chars] [chars]
Explanation The specified Serial Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
SLARP_LITE Messages
Error Message
%L2-SLARP_LITE-3-ERR_CSL_DLL_ASYNC_SEND_FAIL
process fails; Error [chars]
Send async pulse to slarp lite
Explanation Attempt to send pulse to SLARP lite process fails
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Issue the show tech-support command to gather data that may provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text
or from the show tech-support output, call your Cisco technical support representative and provide
the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-919
Layer 2 Messages
SLARP_LITE Messages
Error Message
%L2-SLARP_LITE-3-ERR_CSL_DLL_CHAN_CONNECT_FAIL
process; Error [chars]
Cannot connect to slarp lite
Explanation Attempt to connect to slarp lite process channel fails
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Issue the show tech-support command to gather data that may provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text
or from the show tech-support output, call your Cisco technical support representative and provide
the representative with the gathered information.
Error Message
%L2-SLARP_LITE-3-ERR_SHMEM_MMAP_FAIL
Cannot mmap file [chars]; Error [chars]
Explanation Attempt to mmap the shared memory fails
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Issue the show tech-support command to gather data that may provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text
or from the show tech-support output, call your Cisco technical support representative and provide
the representative with the gathered information.
Error Message
%L2-SLARP_LITE-3-ERR_SHMEM_OPEN_FAIL
[chars]
Cannot open shmem file [chars]; Error
Explanation Attempt to open the shared memory fails
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Issue the show tech-support command to gather data that may provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text
or from the show tech-support output, call your Cisco technical support representative and provide
the representative with the gathered information.
Error Message
%L2-SLARP_LITE-3-ERR_SHMEM_TRNC_FAIL
bytes; Error [chars]
Cannot truncate file [chars] to [dec]
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-920
OL-23348-01
Layer 2 Messages
SLOGIC Messages
Error Message
%L2-SLARP_LITE-3-ERR_SHMEM_UNAVAILABLE SLARP lite SHMEM can accommodate only
[dec] records (request for [dec] records)
Explanation cHDLC MA has requested transfer of more interface records than shared memory can
accommodate
Recommended Action Copy the error message exactly as it appears on the console or in the system
log. Issue the show tech-support command to gather data that may provide information to determine
the nature of the error. If you cannot determine the nature of the error from the error message text
or from the show tech-support output, call your Cisco technical support representative and provide
the representative with the gathered information.
SLOGIC Messages
Error Message
%L2-SLOGIC-4-ANOMALY
[chars]
Explanation A SW exception occurred in SLOGIC Library
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
SONET_APS Messages
Error Message
%L2-SONET_APS-4-WARNING
[chars] - [chars]
Explanation A non-fatal error occurred while executing the function in question. The message
contains info about the cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of SONET APS.
Error Message
%L2-SONET_APS-4-WP_INFO
Connection to [chars]%s [chars]
Explanation State change in the APS group internal communication system detected. Expected
during transitory conditions at config changes, OIR, etc. The message contains info about the WP
communication components affected.
Recommended Action Verify continued correct operation of SONET APS.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-921
Layer 2 Messages
SONET_APS Messages
Error Message
%L2-SONET_APS-6-CONFLICT
[chars] ([chars]) - [chars]
Explanation A conflict failure occurred The message contains info about the cause of the failure and
possibly anticipated actions/effects.
Recommended Action Fix the configuration error for proper operation of SONET APS.
Error Message
%L2-SONET_APS-6-CONTACT
[chars] [chars] [dec] [chars] [dec] [chars]
Explanation Debug messages for APS.
Recommended Action No Action requirements.
Error Message
%L2-SONET_APS-6-REQUEST_PREEMPTED
APS group [dec] [chars] [dec]: preempted
Explanation The user external request is preempted.
Recommended Action Not Action requirements.
Error Message
%L2-SONET_APS-6-SWITCH_INFO
to [chars] [chars]
Group [dec] Channel [dec] [chars] switch of [chars]
Explanation Debug messages for APS.
Recommended Action No Action requirements.
Error Message
%L2-SONET_APS-6-UPDOWN
[chars] [chars] [dec] [chars] [dec] [chars]
Explanation Debug messages for APS.
Recommended Action No Action requirements.
Error Message
%L2-SONET_APS-7-ERROR
[chars] failed ([chars]) - [chars]
Explanation A general failure occurred while executing the function in question. The message
contains info about the cause of the failure and possibly anticipated actions/effects.
Recommended Action Verify continued correct operation of SONET APS.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-922
OL-23348-01
Layer 2 Messages
SONET_LOCAL Messages
Error Message
%L2-SONET_APS-7-NOMEM
Not enough memory for [chars]
Explanation The process is out of memory.
Recommended Action Check process list for source of memory loss. Check if h/w memory
requirements are met.
SONET_LOCAL Messages
Error Message
%L2-SONET_LOCAL-3-ERROR
[chars]([dec]): [chars] failed ([chars]) - [chars]
Explanation A general failure occurred while executing the function in question. The message
contains info about the location and cause of the failure and possibly anticipated actions/effects.
Recommended Action This error indicates a problem in the code and cannot be easily recovered from.
Copy the error message exactly as it appears on the console or in the system log, call your Cisco
technical support representative and provide the representative with the gathered information.
Error Message
%L2-SONET_LOCAL-4-ALARM
[chars]: [chars] [chars]
Explanation The specified SONET Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
Error Message
%L2-SONET_LOCAL-5-AIS_PWFAULT
[chars] [chars]
Explanation L-AIS insertion/removal notification messages.
Recommended Action No action is required.
Error Message
%L2-SONET_LOCAL-6-CLEAR_COUNTERS
Clear counters on [chars]
Explanation Counters on a sonet controller has been cleared by the user. This message is for
information only.
Recommended Action None.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-923
Layer 2 Messages
SPA_192 Messages
SPA_192 Messages
Error Message
%L2-SPA_192-3-ERR_SPA_UNSUPPORTED Inserted node [chars] is not supported by Cisco
12000 Series SPA Interface Processor-601 line card. Please remove to prevent
damages to the hardware.
Explanation A SPA identified by nodeid %s above is not supported by Cisco 12000 Series SPA
Interface Processor-601 line card. The SPA should be remove immediately to prevent damages to
the hardware.
Recommended Action Physically remove the SPA module from the line card.
Error Message
%L2-SPA_192-3-ERR_SPA_UNSUPPORTED Inserted node [chars] is not supported by Cisco
12000 Series SPA Interface Processor-600 line card. Please remove to prevent
damages to the hardware.
Explanation A SPA identified by nodeid %s above is not supported by Cisco 12000 Series SPA
Interface Processor-600 line card. The SPA should be remove immediately to prevent damages to
the hardware.
Recommended Action Physically remove the SPA module from the line card.
Error Message
%L2-SPA_192-3-JACKET_ERROR
[chars]
Explanation SPA 192 Jacket error
Recommended Action When errors occur in jacket, it is very likely the jacket process will restart
itself.
Error Message
%L2-SPA_192-3-JACKET_V2_ERROR
[chars]
Explanation SPA 192 Jacket V2 error
Recommended Action When errors occur in jacket, it is very likely the jacket process will restart
itself.
Error Message
%L2-SPA_192-3-SPARULE_INT_ERROR
[chars]
Explanation SPA 192 Jacket V2 SPA rule internal error
Recommended Action This would indicate an internal error in SPA rule module affecting our ability
to insert/remove new SPA. This may require jacket process restart.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-924
OL-23348-01
Layer 2 Messages
SPA_ATM_V2 Messages
Error Message
%L2-SPA_192-6-SPARULE_ERROR
[chars]
Explanation SPA 192 Jacket V2 SPA rule error
Recommended Action This would indicate an error during insertion/removal of SPA. If error occurs
during OIR than it is likely that problem could be due to invalid combination or SPA type used as
indicated by additional text.
Error Message
%L2-SPA_192-6-UPGRADE_FPGA
[chars]
Explanation Upgrade SPA FPGA message
Recommended Action none
Error Message
%L2-SPA_192-6-UPGRADE_FPGA
[chars]
Explanation Upgrade SPA FPGA message
Recommended Action none
SPA_ATM_V2 Messages
Error Message
%L2-SPA_ATM_V2-3-DRIVER_ERR
[chars] [chars]
Explanation ATM SPA OC3/OC12 driver error messages
Recommended Action *NONE*
Error Message
%L2-SPA_ATM_V2-6-INFO
[chars] [chars]
Explanation ATM SPA OC3/OC12 informational message
Recommended Action *NONE*
Error Message
%L2-SPA_ATM_V2-7-DEBUG
[chars] [chars]
Explanation ATM SPA OC3/OC12 debug message
Recommended Action *NONE*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-925
Layer 2 Messages
SPA_C_SHIM Messages
SPA_C_SHIM Messages
Error Message
%L2-SPA_C_SHIM-3-GET_SHIM_INFO_FAIL
Could not get shim info for ifh [hex]
Explanation Could not get shim info for given interface handle
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SPA_C_SHIM-3-GET_SHIM_INFO_FAIL
Could not get shim info for ifh [hex]
Explanation Could not get shim info for given interface handle
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SPA_C_SHIM-3-NULL_SHIM_INFO
--
Explanation -Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SPA_C_SHIM-3-NULL_SHIM_INFO
--
Explanation -Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SPA_C_SHIM-3-NULL_SHIM_INFO
Null shim info structure for ifh [hex]
Explanation Null shim info encountered for given interface handle
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-926
OL-23348-01
Layer 2 Messages
SPA_CHIN Messages
Error Message
%L2-SPA_C_SHIM-3-QUERY_FAIL
c-shim query failed for ifh [hex]
Explanation Unexpected c-shim query failure for given interface handle
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SPA_C_SHIM-3-QUERY_FAIL
c-shim query failed for ifh [hex]
Explanation Unexpected c-shim query failure for given interface handle
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
SPA_CHIN Messages
Error Message
%L2-SPA_CHIN-3-BAY_ERROR
[chars]:[dec] [chars] for bay [dec] : [chars]
Explanation SPA Jacket 384 error for a given bay
Recommended Action When errors occur in jacket, it is very likely the jacket process will restart
itself.
Error Message
%L2-SPA_CHIN-3-CLIENT_ERROR
[chars]
Explanation SPA Jacket 384 client error
Recommended Action When errors occur in jacket, it is very likely the jacket process will restart
itself.
Error Message
%L2-SPA_CHIN-3-CPP_SPI_SYNC_ERR
[chars]
[chars]:[dec] [chars] on spa-bridge [dec] -
Explanation SPA Jacket 384 CPP interface error
Recommended Action Report the error
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-927
Layer 2 Messages
SPA_CHIN Messages
Error Message
%L2-SPA_CHIN-3-INTR_ERROR
[chars]:[dec] [chars] [unsigned int] : [chars]
Explanation SPA Jacket 384 interrupt error
Recommended Action Report error
Error Message
%L2-SPA_CHIN-3-JACKET_ERROR
[chars]:[dec] [chars] : [chars]
Explanation SPA Jacket 384 error
Recommended Action When errors occur in jacket, it is very likely the jacket process will restart
itself.
Error Message
%L2-SPA_CHIN-3-QFP_ERR
[chars]:[dec] [chars] - [chars]
Explanation SPA Jacket 384 CPP interface error
Recommended Action Report the error
Error Message
%L2-SPA_CHIN-3-SPA_UNSUPPORTED Inserted node [chars] is not supported by Cisco
12000 Series SPA Interface Processor-701 line card. Please remove to prevent
damages to the hardware.
Explanation A SPA identified by nodeid %s above is not supported by Cisco 12000 Series SPA
Interface Processor-701 line card. The SPA should be remove immediately to prevent damages to
the hardware.
Recommended Action Physically remove the SPA module from the line card.
Error Message
%L2-SPA_CHIN-3-SPARULE_INT_ERROR
[chars]
Explanation SPA Jacket 384 SPA rule internal error
Recommended Action This would indicate an internal error in SPA rule module affecting our ability
to insert/remove new SPA. This may require jacket process restart.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-928
OL-23348-01
Layer 2 Messages
SPA_CHOC_DSX Messages
Error Message
%L2-SPA_CHIN-6-SPARULE_ERROR
[chars]
Explanation SPA Jacket 384 SPA rule error
Recommended Action This would indicate an error during insertion/removal of SPA. If error occurs
during OIR than it is likely that problem could be due to invalid combination or SPA type used as
indicated by additional text.
Error Message
%L2-SPA_CHIN-6-UPGRADE_FPGA
[chars]
Explanation Upgrade SPA FPGA message
Recommended Action none
SPA_CHOC_DSX Messages
Error Message
%L2-SPA_CHOC_DSX-3-HDLC_ERR_CHNL_QUE_OV_STAT
events on HDLC Controller were encountered.
SPA [dec]/[dec]: [dec] [chars]
Explanation The SPA driver detected an error event on the HDLC Controller
Recommended Action The SPA driver has encountered an error event on the SPA card. If the condition
persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue
using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at
http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case
with the Technical Assistance Center via the Internet at
http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical
support representative. Be sure to provide the information you have gathered and a ’show
tech-support’ to your support representative, or attach it to your case in non-zipped, plain text format
(.txt).
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-929
Layer 2 Messages
SPA_ETHER Messages
SPA_ETHER Messages
Error Message
%L2-SPA_ETHER-1-LTRACE_INIT_ERR
[chars]
Explanation Jacket process spawns the SPA process and waits for the initialization to complete. But
initialization fails putting SPA into FAILED state. As a part of the above, we find the message Ltrace
init failed message.
Recommended Action If the issue occurs, Check the SPA state. If it is not OK, then collect the
following traces 1) show plim jacket all location 2) show hw-module traces infra detailed location
3) show plim ether trace info/error location 4) console logs
Error Message
%L2-SPA_ETHER-2-LTRACE_RETRY_ERR
[chars]
Explanation Jacket process spawns the SPA process and waits for the initialization to complete. But
initialization fails putting SPA into FAILED state. As part of retry mechanism, the above message
is seen.
Recommended Action If the issue occurs, Check the SPA state. If it is not OK, then collect the
following traces 1) show plim jacket all location 2) show hw-module traces infra detailed location
3) show plim ether trace info/error location 4) console logs
Error Message
%L2-SPA_ETHER-2-MODE_CHANGE
power-cycled.
To complete the mode change the SPA must be
Explanation SPA WAN mode changed to lan/wan from CLI. To complete the mode change the SPA
must be power-cycled.
Recommended Action Power-cycle the SPA.
Error Message
%L2-SPA_ETHER-2-SPA_CTX_ERR
[chars]
Explanation The spa_ether_ctx context data cannot be set.
Recommended Action collect the trace log via ’show plim ether trace error location ’ ’show plim ether
trace info location ’ ’show tech-support ethernet ’ ’show plim jacket trace all location ’ and collect
console logs and send them to the Engineering team.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-930
OL-23348-01
Layer 2 Messages
SPA_ETHER Messages
Error Message
%L2-SPA_ETHER-2-SPA_JKT_ERR
[chars] [chars]
Explanation The Jacket driver failed to parse spa driver argument.
Recommended Action --
Error Message
%L2-SPA_ETHER-2-SPA_MAC_ERR
[chars]
Explanation The internal SPA MAC got out of sync. SW needs to reset the device in order to clear
the issue
Recommended Action If resetting the MAC device fixes the issue, nothing needs to be done. If the
reset does not work, the SPA will need to be SW OIR’d. This can be easily checked by doing ’top’
on the LC with the issue. If the CPU is very high, the reset did not work.
Error Message
%L2-SPA_ETHER-3-INCONSISTENT_CONFIG
[chars]
Explanation As part of trying to configure dot1q vlan with vlan id same as that of outer vlan of QinQ
configuration on other sub-interface, then error has to be reported to remove the inconsistent config.
Recommended Action Upon seeing this message, delete the subinterface that has just been created.
Otherwise the system will be in inconsistent state.
Error Message
%L2-SPA_ETHER-3-PORT_DEL_TIMEOUT
[chars] [dec]
Explanation Port deletion failed to complete within the timeout period.
Recommended Action Upon seeing this message collect the trace log via ’show plim ether trace error
location ’ ’show plim ether trace info location ’ ’show tech-support ethernet ’ and send them to the
Engineering team.
Error Message
%L2-SPA_ETHER-4-INVALID_MAC Failed to get MAC address for port [dec], Interface
assigned random MAC address.
Explanation PLIM driver was unable to get a MAC address for the interface.
Recommended Action Check if the process ’shelfmgr’ is up and running on the RP. Try to reload the
LC to see if that helps. Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-931
Layer 2 Messages
SPA_FPD Messages
Error Message
%L2-SPA_ETHER-4-PORT_DEL_WARNING
[chars] [dec] [chars]
Explanation Port deletion is taking longer time as there is large config to be deleted and so SPA
driver prints out message every 2 min regarding the same.
Recommended Action This is a warning message. Upon seeing this message, collect the following
trace log via CLI ’show plim ether info location ’ ’show plim ether error location ’ ’show
tech-support ethernet location ’ ’show im trace location ’ ’show cfgmgr trace location ’ ’show vlan
trace location all’ Send them to the engineering team.
Error Message
%L2-SPA_ETHER-4-WAIT_CONFIG
[chars]
Explanation During bringup of Wanphy SPA, the config has to be restored before init. With this we
can decide whether to get SPA in LAN or WAN mode. This message indicates that config restore of
wanphy is getting delayed
Recommended Action No explicit action is required, if it gets delayed, SPA state machine would
timeout and reload the SPA.
Error Message
%L2-SPA_ETHER-6-PORT_DEL_INFO
[chars] [dec] [chars]
Explanation Port deletion happened after the threshold time.
Recommended Action This is an informational message. Upon seeing this message collect the trace
log via ’show plim ether trace error location ’ ’show plim ether trace info location ’ ’show
tech-support ethernet ’ and send them to the Engineering team.
SPA_FPD Messages
Error Message
%L2-SPA_FPD-3-FATAL_ERROR
[chars]
Explanation An internal system software error has occurred. This type of errors are in general SW
bugs that are caused by providing wrong information to SPA FPD API.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-932
OL-23348-01
Layer 2 Messages
SPA_FPD Messages
Error Message
%L2-SPA_FPD-3-GET_IMG_ERROR
[chars][[dec]]: [chars]
Explanation An image for an FPD could not be obtained so that it could be updated. The cause of the
failure is indicated in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SPA_FPD-3-GET_VERSION_ERROR
information.
[chars][[dec]]: Failed to get FPD version
Explanation The version of the FPD could not be obtained from the specified SPA. The FPD
information will not be available for the specified SPA. System processing will continue normally.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SPA_FPD-3-SW_ERROR
[chars][[dec]]: [chars]
Explanation An internal software error has occurred on the specified SPA.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SPA_FPD-3-UPDATE_FAILED
[chars][[dec]]: Failed to update FPD ’[chars]’ image
Explanation The update operation for the specified FPD image has failed.
Recommended Action Retry the operation to update the image. If the retry operation fails, copy the
message exactly as it appears on the console or in the system log. Research and attempt to resolve
the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages,
these tools and utilities will supply clarifying information. Search for resolved software issues using
the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still
require assistance, open a case with the Technical Assistance Center via the Internet at
http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical
support representative and provide the representative with the information you have gathered.
Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of
the show logging and show tech-support commands and your pertinent troubleshooting logs.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-933
Layer 2 Messages
SPA_FPD Messages
Error Message
%L2-SPA_FPD-3-WRONG_OIR_STATE [chars][[dec]]: Cannot perform FPD image update on
’[chars]’ OIR state, it should be in ’[chars]’ OIR state
Explanation The FPD image update operation could not be performed because the specified SPA is
not in the correct state. The correct OIR state for the SPA is specified in the message text.
Recommended Action Do not perform the update operation while the SPA is in the middle of a reload
operation or while it is being initialized. Wait until the specified SPA is in the correct OIR state and
retry the operation.
Error Message
%L2-SPA_FPD-5-OFFLINE_NOTICE [chars][[dec]]: Changing operational status to
offline for update of FPD image
Explanation An attempt has been made to temporarily change the operational status of the SPA from
online to offline before the image for the FPD could be updated on the target SPA. For some SPA
types, this operation is required.
Recommended Action Ensure that you have redirected the traffic of the target SPA before performing
this action, since the target SPA will require a power cycle operation after the image update for the
FPD on the target SPA has been performed.
Error Message
%L2-SPA_FPD-5-RELOAD_NOTICE
image(s) to take effect
[chars][[dec]]: Reloading the SPA for the updated FPD
Explanation Indicates the reloading operation of the SPA after the completion of the FPD image
update operation.
Recommended Action No action is required.
Error Message
%L2-SPA_FPD-6-UPDATE_PASSED
image
[chars][[dec]]: Successfully updated FPD ’[chars]’
Explanation The FPD image was updated successfully.
Recommended Action No action is required.
Error Message
%L2-SPA_FPD-6-UPDATE_START
image
[chars][[dec]]: Starting update of FPD ’[chars]’
Explanation The FPD update operation has started for the specified image.
Recommended Action No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-934
OL-23348-01
Layer 2 Messages
SPA_OC3_OC12 Messages
SPA_OC3_OC12 Messages
Error Message
%L2-SPA_OC3_OC12-3-DRV_INIT_ERR Initialization of SPA driver failed: [chars] :
reason equals [chars] ; exiting...
Explanation SPA driver encountered the annunciated error during the driver initialization. The
System Manager process (sysmgr) will automatically respawn the (spa_oc3_oc12) process, up to a
fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will
trigger node reload. After a certain number of node reloads, the shelf manager will permanently
shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SPA_OC3_OC12-3-ERR_IF
[chars]
Explanation The SPA driver on the linecard failed to call SONET control or POS interface related
system function. The issue may affect the creation of SONET controller or POS interface while the
SPA is booting, reloading or SFP OIR with different optics rate. %s - error message indicating
location and the reason of the error
Recommended Action - Try to do the SFP OIR for a few more times; - If the issue persists, reload the
SPA with the command: hw-module subslot 0/x/x reload then check if all the POS interface are
created, if not, reload LC. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SPA_OC3_OC12-3-ERR_IF
[chars]
Explanation The SPA driver on the linecard failed to call SONET control or POS interface related
system function. The issue may affect the creation of SONET controller or POS interface while the
SPA is booting, reloading or SFP OIR with different optics rate. %s - error message indicating
location and the reason of the error
Recommended Action - Try to do the SFP OIR for a few more times; - If the issue persists, reload the
SPA with the command: hw-module subslot 0/x/x reload then check if all the POS interface are
created, if not, reload LC. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-935
Layer 2 Messages
SPA_OC3_OC12 Messages
Error Message
%L2-SPA_OC3_OC12-3-ERR_PLUGIN
[chars]
Explanation The operation on SPA object failed. The SPA driver controls all the hardware on the
SPA. If the operation on SPA fails, the SPA may not be able to boot or work properly, and the traffic
may be affected. %s - error message indicating location and the reason of the error
Recommended Action The SPA infra will automatically restart the SPA driver up to a fixed number of
times if the failure happens during SPA is booting. If the failure doesn’t happen with SPA booting,
manually SPA reload may be needed. Execute ’show platform’ to verify the SPA is in READY state,
if not, try to reload the SPA with command: hw-module subslot 0/x/x reload or if the system has no
response to the command above, force to reload the SPA with following sequence under config
mode: hw-module subslot 0/x/x shutdown commit no hw-module subslot 0/x/x shutdown commit If
the message recurs, copy the error message exactly as it appears on the console or in the system log,
call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SPA_OC3_OC12-3-ERR_PLUGIN
[chars]
Explanation The operation on SPA object failed. The SPA driver controls all the hardware on the
SPA. If the operation on SPA fails, the SPA may not be able to boot or work properly, and the traffic
may be affected. %s - error message indicating location and the reason of the error
Recommended Action The SPA infra will automatically restart the SPA driver up to a fixed number of
times if the failure happens during SPA is booting. If the failure doesn’t happen with SPA booting,
manually SPA reload may be needed. Execute ’show platform’ to verify the SPA is in READY state,
if not, try to reload the SPA with command: hw-module subslot 0/x/x reload or if the system has no
response to the command above, force to reload the SPA with following sequence under config
mode: hw-module subslot 0/x/x shutdown commit no hw-module subslot 0/x/x shutdown commit If
the message recurs, copy the error message exactly as it appears on the console or in the system log,
call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SPA_OC3_OC12-3-ERR_RESTART
[chars]
Explanation There is an error detected during SPA process restart. During the process restart, the
software will do: checking the hardware config compatibility; re-creating SONET controller and
POS interface; restoring configurations. Any failure in above will cause restart failed. The traffic
may or may not be affected after restart failed, but the further operation on SPA, e.g. changing
configuration, may not be carried out properly. %s - error message indicating location and the reason
of the error
Recommended Action The system will try to restart the process again for a few times, If the issue
persists, reload the SPA with the command: hw-module subslot 0/x/x reload If the message recurs,
copy the error message exactly as it appears on the console or in the system log, call your Cisco
technical support representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-936
OL-23348-01
Layer 2 Messages
SPA_OC3_OC12 Messages
Error Message
%L2-SPA_OC3_OC12-3-ERR_RESTART
[chars]
Explanation There is an error detected during SPA process restart. During the process restart, the
software will do: checking the hardware config compatibility; re-creating SONET controller and
POS interface; restoring configurations. Any failure in above will cause restart failed. The traffic
may or may not be affected after restart failed, but the further operation on SPA, e.g. changing
configuration, may not be carried out properly. %s - error message indicating location and the reason
of the error
Recommended Action The system will try to restart the process again for a few times, If the issue
persists, reload the SPA with the command: hw-module subslot 0/x/x reload If the message recurs,
copy the error message exactly as it appears on the console or in the system log, call your Cisco
technical support representative and provide the representative with the gathered information.
Error Message
%L2-SPA_OC3_OC12-3-ERR_SFP
[chars]
Explanation There is an error detected during SFP initialization. SFP is the pluggable optics on the
SPA, SFP initialization may happen when linecard boots up, SFP OIR and SPA process restart. SFP
error is for any possible error during the initialization. The optics will not work if SFP OIR operation
failed, therefore no traffic will be affected. %s - error message indicating location and the reason of
the error
Recommended Action - Check the SFP, make sure it is CISCO certified; - Try to do the SFP OIR for
a few more times; - If the issue persists, reload the SPA with the command: hw-module subslot 0/x/x
reload then test SFP OIR after SPA comes up. If the message recurs, copy the error message exactly
as it appears on the console or in the system log, call your Cisco technical support representative
and provide the representative with the gathered information.
Error Message
%L2-SPA_OC3_OC12-3-ERR_SFP
[chars]
Explanation There is an error detected during SFP initialization. SFP is the pluggable optics on the
SPA, SFP initialization may happen when linecard boots up, SFP OIR and SPA process restart. SFP
error is for any possible error during the initialization. The optics will not work if SFP OIR operation
failed, therefore no traffic will be affected. %s - error message indicating location and the reason of
the error
Recommended Action - Check the SFP, make sure it is CISCO certified; - Try to do the SFP OIR for
a few more times; - If the issue persists, reload the SPA with the command: hw-module subslot 0/x/x
reload then test SFP OIR after SPA comes up. If the message recurs, copy the error message exactly
as it appears on the console or in the system log, call your Cisco technical support representative
and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-937
Layer 2 Messages
SPA_OC3_OC12 Messages
Error Message
%L2-SPA_OC3_OC12-3-GENERIC_ERROR
[chars] : reason equals [chars]
Explanation SPA OC3/OC12 driver error messages
Recommended Action *NONE*
Error Message
%L2-SPA_OC3_OC12-3-GET_NODEID_ERR
[chars] : reason equals [chars]
Explanation SPA driver failed to obtain either its node ID or extract rack/slot/instance information
(having obtained the node ID).
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SPA_OC3_OC12-6-INFO
[chars] [chars]
Explanation SPA OC3/OC12 informational message
Recommended Action *NONE*
Error Message
%L2-SPA_OC3_OC12-6-INFO
[chars]
Explanation information message %s - message
Recommended Action none
Error Message
%L2-SPA_OC3_OC12-6-INFO
[chars]
Explanation This is an informational message which indicates, Sonetmib Perf monitoring is not
properly initialized. So, performance stats will not be collected. This does not cause any traffic loss
or cause any issue for normal operation of SPA. %s - error message indicating
pm_create_sonet_service failed
Recommended Action This problem shouldn’t be seen under normal circumstances, but if observed,
do SPA OIR/Reload using following command, and verify if the problem goes, hw-module subslot
R/S/I reload
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-938
OL-23348-01
Layer 2 Messages
SPA_OC48 Messages
Error Message
%L2-SPA_OC3_OC12-6-OPTICS_OIR
[chars]
Explanation Optics module has inserted %s - message related to the SFP insertion event
Recommended Action none
Error Message
%L2-SPA_OC3_OC12-7-DEBUG
[chars] [chars]
Explanation SPA OC3/OC12 debug message
Recommended Action *NONE*
SPA_OC48 Messages
Error Message
%L2-SPA_OC48-3-DRV_INIT_ERR
equals [chars] ; exiting...
Initialization of SPA driver failed: [chars] : reason
Explanation SPA driver encountered the annunciated error during the driver initialization. The
System Manager process (sysmgr) will automatically respawn the (spa_oc48) process, up to a fixed
number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger
SPA reload. After a certain number of SPA reloads, the shelf manager will permanently shutdown
the SPA.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SPA_OC48-3-ERR_INIT
([chars]/[chars]).
SPA driver initialization failed in bay [dec]:
Explanation The SPA driver on the linecard failed to initialize. The SPA driver controls all the
hardware on the SPA. If the SPA driver fails to initialize, no traffic will pass, no SPA related
infrastructure will work. %d - SPA bay number %s - indicates the reason for the failure %s - is the
decoded error reason
Recommended Action The SPA infra will automatically restart the SPA driver, up to a fixed number
of times when this error is encountered, to recover. Execute ’show platform’ to verify the SPA is in
READY state, if not, try to reload the SPA with command: hw-module subslot 0/x/x reload or if the
system has no response to the command above, force to reload the SPA with following sequence
under config mode: hw-module subslot 0/x/x shutdown commit no hw-module subslot 0/x/x
shutdown commit If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-939
Layer 2 Messages
SPA_OC48 Messages
Error Message
%L2-SPA_OC48-3-ERR_INIT
([chars]/[chars]).
SPA driver initialization failed in bay [dec]:
Explanation The SPA driver on the linecard failed to initialize. The SPA driver controls all the
hardware on the SPA. If the SPA driver fails to initialize, no traffic will pass, no SPA related
infrastructure will work. %d - SPA bay number %s - indicates the reason for the failure %s - is the
decoded error reason
Recommended Action The SPA infra will automatically restart the SPA driver, up to a fixed number
of times when this error is encountered, to recover. Execute ’show platform’ to verify the SPA is in
READY state, if not, try to reload the SPA with command: hw-module subslot 0/x/x reload or if the
system has no response to the command above, force to reload the SPA with following sequence
under config mode: hw-module subslot 0/x/x shutdown commit no hw-module subslot 0/x/x
shutdown commit If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Error Message
%L2-SPA_OC48-3-ERR_SFP_OIR
SFP OIR error in bay [dec]: ([chars]/[chars]).
Explanation There is an error detected during SFP OIR. SFP is the pluggable optics on the SPA, SFP
OIR can cause some operation in sw, e.g. create/delete optics object, SFP authentication. ’SFP OIR
error’ is for any possible error during the operation. The optics will not work if SFP OIR operation
failed, therefore no traffic can pass. %d - SPA bay number %s - indicates the reason for the failure
%s - is the decoded error reason
Recommended Action - Check the SFP, make sure it is CISCO certified; - Try to do the SFP OIR for
a few more times; - If the issue persists, reload the SPA with the command: hw-module subslot 0/x/x
reload then test SFP OIR after SPA comes up. If the message recurs, copy the error message exactly
as it appears on the console or in the system log, call your Cisco technical support representative
and provide the representative with the gathered information.
Error Message
%L2-SPA_OC48-3-ERR_SFP_OIR
SFP OIR error in bay [dec]: ([chars]/[chars]).
Explanation There is an error detected during SFP OIR. SFP is the pluggable optics on the SPA, SFP
OIR can cause some operation in sw, e.g. create/delete optics object, SFP authentication. ’SFP OIR
error’ is for any possible error during the operation. The optics will not work if SFP OIR operation
failed, therefore no traffic can pass. %d - SPA bay number %s - indicates the reason for the failure
%s - is the decoded error reason
Recommended Action - Check the SFP, make sure it is CISCO certified; - Try to do the SFP OIR for
a few more times; - If the issue persists, reload the SPA with the command: hw-module subslot 0/x/x
reload then test SFP OIR after SPA comes up. If the message recurs, copy the error message exactly
as it appears on the console or in the system log, call your Cisco technical support representative
and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-940
OL-23348-01
Layer 2 Messages
SPA_OC48 Messages
Error Message
%L2-SPA_OC48-3-GENERIC_ERROR
[chars] : reason equals [chars]
Explanation SPA OC48 driver error messages
Recommended Action *NONE*
Error Message
%L2-SPA_OC48-3-GET_NODEID_ERR
[chars] : reason equals [chars]
Explanation SPA driver failed to obtain either its node ID or extract rack/slot/instance information
(having obtained the node ID).
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SPA_OC48-6-INFO
[chars] [chars]
Explanation SPA OC48 informational message
Recommended Action *NONE*
Error Message
%L2-SPA_OC48-6-OPTICS_INSERTION
port [dec]
Optics module inserted into SPA in bay [dec],
Explanation Optics module has inserted %d - bay number %d - port number
Recommended Action none
Error Message
%L2-SPA_OC48-6-OPTICS_INSERTION
port [dec]
Optics module inserted into SPA in bay [dec],
Explanation Optics module has inserted %d - bay number %d - port number
Recommended Action none
Error Message
%L2-SPA_OC48-6-OPTICS_REMOVAL
[dec]
Optics module removed from SPA in bay [dec], port
Explanation Optics module has removed %d - bay number %d - port number
Recommended Action none
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-941
Layer 2 Messages
SPA_PLIM_SB Messages
Error Message
%L2-SPA_OC48-6-OPTICS_REMOVAL
[dec]
Optics module removed from SPA in bay [dec], port
Explanation Optics module has removed %d - bay number %d - port number
Recommended Action none
Error Message
%L2-SPA_OC48-7-DEBUG
[chars] [chars]
Explanation SPA OC48 debug message
Recommended Action *NONE*
SPA_PLIM_SB Messages
Error Message
%L2-SPA_PLIM_SB-3-FPD_GETVER_FAIL
version for [chars]
[chars][[dec]]: Failed to get FPD image
Explanation The FPD image version could not be retrieved from the SPA for the programmable
device that is specified in the message text. This condition can occur if the system attempts to
retrieve the version information while the SPA is not in the correct operational state.
Recommended Action Try to reload the affected SPA or physically remove and then insert the SPA to
correct the problem. If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SPA_PLIM_SB-3-FPD_IMG_DNLD_ERROR
error ([chars])
[chars][[dec]]: [chars] image download
Explanation The FPD image download operation for the indicated device has failed. The cause of the
error is also indicated in the message.
Recommended Action Retry the image update operation and if it fails again, copy the error message
exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-942
OL-23348-01
Layer 2 Messages
SPA_PLIM_SB Messages
Error Message
%L2-SPA_PLIM_SB-3-FPD_IMG_UPD_ERROR
([chars])
[chars][[dec]]: [chars] image update error
Explanation The FPD image update operation for the indicated device has failed. The cause of the
error is also indicated in the message.
Recommended Action Retry the image update operation and if it fails again, copy the error message
exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-SPA_PLIM_SB-3-MSG_REPLY_FAIL
([chars])
[chars][[dec]]: Failed to reply a message
Explanation A message to the specified SPA did not receive a reply. The reason for the failure is
specified in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SPA_PLIM_SB-3-MSG_SEND_FAIL
after retries: [[dec]]
[chars][[dec]]: Failed to send message ([chars])
Explanation A message to the specified SPA could not be sent. The reason for the failure is specified
in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SPA_PLIM_SB-3-OPEN_CH_FAIL
([chars])
[chars][[dec]]: Open channel for [chars] failed
Explanation A communication channel could not be opened with the specified SPA. The reason for
the failure is specified in the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-943
Layer 2 Messages
SPA_T3E3 Messages
Error Message
%L2-SPA_PLIM_SB-3-SPA_FW_ERR
[chars][[dec]] ([chars])
Explanation The error message in parentheses is generated by SPA firmware for reason as mentioned
in the error message. This error, and the message is logged by the plim holding the SPA.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SPA_PLIM_SB-3-SW_ERROR
[chars][[dec]]: [chars]
Explanation An internal software error has occurred for the specified SPA.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
SPA_T3E3 Messages
Error Message
%L2-SPA_T3E3-6-SPA_RELOAD_INFO
[chars] [dec] [chars] [chars] [chars] [chars]
Explanation When the card type of T3E3 SPA is changed to T3 from E3 or vice versa, it undergoes
a reload. A SPA reload is mandatory to have the newly configured card type in effect.
Recommended Action This is an informational message indicating the T3E3 SPA will undergo a
reload.
SPA Messages
Error Message
%L2-SPA-3-BUS_FAILURE
SPA ERR_L interrupt is asserted on subslot [unsigned int]
Explanation SPA ERR_L interrupt is asserted by SPA when SPA bus protocol violation happens.
This error happens mostly when there is an issue with hardware itself. The SPA reset is not going to
recover the problem, hence SPA put into FAILED state.
Recommended Action Replace SPA hardware or contact TAC to diagnose the problem.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-944
OL-23348-01
Layer 2 Messages
SPA Messages
Error Message
%L2-SPA-3-IPSEC_SPA_CRASH
No Heartbeat from IPSec SPA. Reloading the SPA
Explanation IPsec SPA crashed, has to be reloaded.
Recommended Action None.
Error Message
%L2-SPA-3-PLIM_HEARTBEAT_ERR [chars]: bay [dec] heartbeat missed, expected seq#
[unsigned int] received seq# [unsigned int], Time since last message [dec]s
Explanation The IPC communication between local CPU and host in the specified slot indicated in
the message is not functional. If the problem persists the SPA will be reloaded to recover from the
failure.
Recommended Action If the problem persists, try to reseat the SPA. If reseating does not help, copy
the message exactly as it appears on the console or in the system log. Research and attempt to
resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying information. Search for resolved software
issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical
support representative and provide the representative with the information you have gathered.
Error Message
%L2-SPA-3-PM_ERR
Failed to create pm_service in bay: [dec]
Explanation This is an error condition which should not occur in normal conditions. If this message
is seen, the sonetmib stats will not be updated. %d - indicates the bay number
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-SPA-3-POWER_FAILURE
[unsigned int]
SPA_OK and PWR_OK signal is deasserted on subslot
Explanation SPA_OK and PWR_OK signal is asserted after the SPA is powered on by LC. These
signals are deasserted when there is power failure on SPA and this failure indicates that it is SPA
hardware issue. The SPA is put into FAILED state.
Recommended Action Contact TAC to diagnose the problem.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-945
Layer 2 Messages
SPA Messages
Error Message
%L2-SPA-3-SYSDB_ERROR
[chars]
Explanation SPA Infrastructure SysDb error
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SPA-4-CERR_REGISTRATION_FAILURE
error [hex]
Registration of error strings failed with
Explanation Error string registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SPA-5-APPS_IMAGE_DOWNLOADING
Downloading SPA Application Image ([chars])...
Explanation Downloading SPA Application image as indicated in the message
Recommended Action none.
Error Message
%L2-SPA-5-APPS_IMAGE_ERROR
Download SPA Application Image failed.
Explanation Failed to download the SPA Application image.
Recommended Action none.
Error Message
%L2-SPA-5-APPS_IMAGE_SIZE_ERR SPA Application image exceeds RAM size: Image size
([dec]) Shared mem size ([dec])
Explanation The size of the SPA Application image is too big.
Recommended Action none.
Error Message
%L2-SPA-5-DOWNLOAD_METHOD_ERR
SPA Download method [dec] not supported
Explanation The specified download method is not supported
Recommended Action none.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-946
OL-23348-01
Layer 2 Messages
SPA Messages
Error Message
%L2-SPA-5-FILE_SIZE_ERR
([dec])
SPA File exceeds Rdisk size: File size ([dec]) Rdisk size
Explanation The size of the SPA File is too big.
Recommended Action none.
Error Message
%L2-SPA-5-OIR_ERROR
[chars]
Explanation SPA related error as indicated in the msg
Recommended Action none.
Error Message
%L2-SPA-5-OIR_INSERTED
SPA discovered in bay [dec]
Explanation For displaying SPA OIR.
Recommended Action none.
Error Message
%L2-SPA-5-OIR_REMOVED
SPA removed from bay [dec]
Explanation For displaying SPA OIR.
Recommended Action none.
Error Message
%L2-SPA-5-OS_IMAGE_DOWNLOADING
Downloading SPA OS Image ([chars])...
Explanation Downloading SPA OS image as indicated in the message
Recommended Action none.
Error Message
%L2-SPA-5-OS_IMAGE_ERROR
Download SPA OS Image failed
Explanation Failed to download the SPA OS image.
Recommended Action none.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-947
Layer 2 Messages
SPA Messages
Error Message
%L2-SPA-5-OS_IMAGE_SIZE_ERR
Shared mem size ([dec])
SPA OS image exceeds RAM size: Image size ([dec])
Explanation The size of the SPA OS image is too big.
Recommended Action none.
Error Message
%L2-SPA-5-PLIM_EVENT_INIT_ERR
SPA Init Event Server failed
Explanation Creating SPA event handling server failed.
Recommended Action none.
Error Message
%L2-SPA-5-PLIM_KA_INIT_ERR
SPA Init SPA Keepalive Handler failed
Explanation Creating SPA keepalive server failed.
Recommended Action none.
Error Message
%L2-SPA-5-PLIM_RELOADING
heartbeat failure ...
Reloading [chars] in subslot [unsigned int] after
Explanation Reloading SPA because of heartbeat failure.
Recommended Action none.
Error Message
%L2-SPA-5-STATE_CHANGE
SPA in bay [dec] type [chars] [chars]
Explanation For displaying state of a SPA
Recommended Action none.
Error Message
%L2-SPA-6-OPTICS_INSERTION
Optics module inserted into SPA in bay [dec]
Explanation Optics module has been inserted. %d - indicates the bay number
Recommended Action None. This is an informational message only.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-948
OL-23348-01
Layer 2 Messages
SPABRG_384 Messages
Error Message
%L2-SPA-6-OPTICS_REMOVAL
Optics module removed from SPA in bay [dec]
Explanation Optics module has been removed. %d - indicates the bay number
Recommended Action None. This is an informational message only.
Error Message
%L2-SPA-6-PM_ERR
Failed to create pm_service in bay: [dec]
Explanation This is an error condition which should not occur in normal conditions. %d - indicates
the bay number
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.
SPABRG_384 Messages
Error Message
%L2-SPABRG_384-2-FAULT_CRIT
[chars]:[dec] [chars]: [hex] on spa-bridge [dec]
Explanation Critical error on spa bridge, LC will reset.
Recommended Action Report the error
Error Message
%L2-SPABRG_384-3-CHAN_ERROR
[dec]
[chars]:[dec] [chars] for SPI4 channel [dec] on bay
Explanation Error on a SPI4 Channel for bay
Recommended Action Report Error
Error Message
%L2-SPABRG_384-3-DEV_ERROR
[chars]:[dec] [chars] [dec]
Explanation Device error related to spa bridge
Recommended Action Report Error
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-949
Layer 2 Messages
SPABRG Messages
Error Message
%L2-SPABRG_384-3-DEV_OBJ_ERROR
[dec]
[chars]:[dec] Device object not found for [chars]
Explanation Device object not found for marmot (instance) or SPA (bay no)
Recommended Action Report Error
Error Message
%L2-SPABRG_384-3-GEN_ERROR
[chars]:[dec] [chars]
Explanation General error related to spa bridge
Recommended Action Report Error
Error Message
%L2-SPABRG_384-3-INTR_ERROR
[chars]:[dec] [chars] interrupt for [chars] [dec]
Explanation Interrupt related error for spa bridge or spa
Recommended Action Report Error
Error Message
%L2-SPABRG_384-3-SPA_ERROR
[chars]:[dec] [chars] for bay [dec]
Explanation Error in bay
Recommended Action Report Error
SPABRG Messages
Error Message
%L2-SPABRG-3-HW_ERR
[chars] : [chars] : [hex]
Explanation Marmot 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.’
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-950
OL-23348-01
Layer 2 Messages
SPAMSG Messages
Error Message
%L2-SPABRG-6-HW_INFO1
[chars] : [chars] : [hex]
Explanation Marmot spabrg driver informational message
Recommended Action NONE : Informational message only
Error Message
%L2-SPABRG-6-HW_INFO2
[chars] : [chars] : [hex], [hex]
Explanation Marmot spabrg driver informational message
Recommended Action NONE : Informational message only
Error Message
%L2-SPABRG-6-HW_INFO3
[chars] : [chars] : [hex], [hex], [hex]
Explanation Marmot spabrg driver informational message
Recommended Action NONE : Informational message only
SPAMSG Messages
Error Message
%L2-SPAMSG-3-ERR
[chars]
Explanation SPA related error msg
Recommended Action none.
Error Message
%L2-SPAMSG-6-INFO
[chars]
Explanation SPA related info
Recommended Action none.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-951
Layer 2 Messages
SPAN Messages
SPAN Messages
Error Message
%L2-SPAN-4-CHKPT_HW_ERROR
[chars]
Failed to restore hardware state from checkpoint:
Explanation The SPAN EA encountered an error while trying to recover hardware programming
information based on checkpointed records. The records are used to ensure hardware resources are
cleaned up correctly; if an error has been encountered then it is possible that traffic will continue to
replicated from sources or to destinations on the affected node even after configuration has been
removed. Standard forwarding will not be affected.
Recommended Action If it appears that traffic is being replicated incorrectly, then re-enabling, and
then disabling traffic replication for the affected interface may help to resolve 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-SPAN-4-CHKPT_SESSID_ERROR
[chars]
Failed to restore Session IDs from checkpoint:
Explanation The SPAN Manager encountered an error while trying to restore its database from
checkpoint. The checkpoint database is used to ensure that internal session IDs are persistent across
process restarts. This failure indicates that there is a problem with the table. The table will be
deleted, potentially leading to a brief interruption to replicated-traffic-flow when the process
restarts, but SPAN should otherwise continue to operate as normal. Standard forwarding will 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-SPAN-4-DB_DELETE_FAILED
database
Failed to remove an object ([chars]) from the
Explanation SPAN was unable to remove an object from its database. The process will attempt to
recover, but it is possible that traffic will not be replicated correctly, or some traffic will not be
replicated to the correct interfaces. Standard forwarding will not be affected.
Recommended Action This is likely to indicate an internal inconsistency in SPAN. The problem may
be resolved by issuing ’process restart’ for the affected process on the node that emitted the message.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-952
OL-23348-01
Layer 2 Messages
SPAN Messages
Error Message
%L2-SPAN-4-DST_UPDATE_FAILED Failed to record new updated destination for
monitor-session [chars]: [chars]
Explanation The SPAN MA was unable to record a change to the destination interface for the
specified session. It is likely that traffic will not be replicated to the desired destination. Standard
forwarding will not be affected. Use ’show monitor-session status’ to identify the set of affected
interfaces and to provide more information about their current state.
Recommended Action This message is likely to indicate a system resource issue, or an internal
inconsistency within the SPAN MA. Attempt to resolve any resource constraint issues before
attempting to solve the problem. Once such constraints are resolved, issue ’process restart span_ma’
on the node with the affected source 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-SPAN-4-EXIT_FAILED
exiting: [chars]
Failed to inform the System Manager that [chars] is
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 (i.e., there is SPAN
configuration remaining), then remove all SPAN configuration, commit this change, then re-enter
and commit the configuration.
Error Message
%L2-SPAN-4-IM_MSG_FAILED Failed to send [unsigned int] [chars] messages to update
SPAN configuration: [chars]
Explanation The SPAN MA was not able to send a message to update monitor-session configuration
for a set of source interfaces. It is possible that traffic will not be replicated correctly at the affected
source interfaces. Standard forwarding will not be affected. Use ’show monitor-session status’ to
identify the set of affected interfaces and to provide more information about their current state.
Recommended Action This message may indicate a communication problem, or a problem with
programming the hardware. Attempt to resolve any memory issues before attempting to solve the
problem. If the error message indicates that there was a problem programming the hardware then
issue ’process restart span_ea’ on the node with the affected interfaces. Otherwise, issue ’process
restart span_ma’ on the node that emitted the 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-953
Layer 2 Messages
SPAN Messages
Error Message
%L2-SPAN-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-SPAN-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-SPAN-4-PD_RESYNC_FAILED
[chars]
Failed to update the hardware after connection loss:
Explanation The SPAN EA was not able to update traffic replication programming in the hardware.
It is possible that traffic will be replicated incorrectly at some source interfaces, and that hardware
resources will not be released. Use ’show monitor-session status’ to determine which interfaces are
affected. Standard forwarding will not be affected.
Recommended Action This message is likely to indicate a problem with programming the hardware.
Attempt to resolve any memory issues before attempting to solve the problem. If recently applied
configuration changes have not been enacted in the hardware, reverting and then re-applying the
configuration changes may help to resolve 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-SPAN-4-STATS_CLEAR_FAILED
[hex]: [chars]
Failed to clear statistics for source interface
Explanation The SPAN MA was unable to clear statistics for the specified source interface. The
SPAN MA would normally clear statistics at the point at which a source interface is removed from
a session. Traffic replication will continue to operate as normal, but statistics relating to traffic
replicated while the interface was in the session it has just been removed from will persist until they
are manually cleared.
Recommended Action The source interface counters can be cleared by running ’clear monitor-session
counters’. If the message recurs, copy the error message exactly as it appears on the console or in
the system log, call your Cisco technical support representative and provide the representative with
the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-954
OL-23348-01
Layer 2 Messages
SPU_LIB Messages
SPU_LIB Messages
Error Message
%L2-SPU_LIB-3-MSG_SEND_FAILED
send, errno: [chars]
spu: msg: [dec], retried: [dec] time(s), failed to
Explanation Unable to send a message to the SPU server.
Recommended Action *SUPPORT*
Error Message
%L2-SPU_LIB-6-INFO_WARNING
[chars]
Explanation This is an informational message in the SPU client LIB.
Recommended Action *NONE*
SPU Messages
Error Message
%L2-SPU-3-COREDUMP_END_NOTIF SPU fatal error occurred ... [chars] core dump is
created and [chars] stored on CP
Explanation A fatal error occurred in SPU h/w. Core dump process ended’ .
Recommended Action *SUPPORT*
Error Message
%L2-SPU-3-COREDUMP_FP_NOTIF SPU fatal error occurred ... Fast path ME are stopped
. Core dump will [chars] be stored on CP
Explanation A fatal error occurred in SPU h/w. Fast path ME’s are going to be stopped. No future
connection between service blade and RP will be possible. Default action is to reload board, but if
coredump is not stored on CP’s CF, reload may be prevented by appropriate CLI and core dump ,
which is always exists on XScale RAM disk may be accessed from IXP console.
Recommended Action *SUPPORT*
Error Message
%L2-SPU-3-COREDUMP_START_NOTIF
dump process
SPU fatal error occurred ... Started [chars] core
Explanation A fatal error occurred in SPU h/w. Core dump process started .
Recommended Action *SUPPORT*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-955
Layer 2 Messages
SPU Messages
Error Message
%L2-SPU-3-FATAL_ERR
Fatal error: [chars]: Err equals [dec]
Explanation A fatal error occurred in SPU Driver.
Recommended Action *SUPPORT*
Error Message
%L2-SPU-3-NONFATAL_ERR
Nonfatal error: [chars]: Err equals [dec]
Explanation A non fatal error occurred in SPU Driver.
Recommended Action *SUPPORT*
Error Message
%L2-SPU-3-SER_NOTIF
: [hex]
Soft error occurred... [chars] : status 1 : [hex], status 2
Explanation A fatal error occurred in SPU h/w.
Recommended Action *SUPPORT*
Error Message
%L2-SPU-6-INFO_MSG
[chars]
Explanation This is a Informational message in the SPU Driver.
Recommended Action *NONE*
Error Message
%L2-SPU-6-MINOR_SBE_NOTIF
status 2 : [hex]
Corrected soft error ... [chars] : status 1 : [hex],
Explanation Single bit DRAM error was successfully corrected on SPU h/w.
Recommended Action *SUPPORT*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-956
OL-23348-01
Layer 2 Messages
SRP Messages
SRP Messages
Error Message
%L2-SRP-2-FATAL
[chars] failed: [chars]
Explanation Some requested operation failed during initialization. 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-SRP-2-MUTEX
[chars] failed: [chars]
Explanation Thread synchronization failure has occurred. 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-SRP-3-ERR_DUP_MAC_ADDR
[chars]: Duplicate mac addresses in topology
Explanation Another node on the ring is using the same MAC address as this node. This can effect
traffic forwarding.
Recommended Action Correct the configuration of each node, where necessary, to ensure that each
node uses a unique MAC address. Use the ’show srp topology’ CLI to identify any nodes using the
same MAC address.
Error Message
%L2-SRP-3-ERR_MEDIA_SINGLE_RING
[chars] SRR usage changed ([chars])
Explanation SRR ring usage is changed using Inner, Outer or Both rings. There are/were multiple
faults (or user requests) on the ring causing potential loss of traffic/bandwidth.
Recommended Action Clear the cause of each fault/wrap on the ring. Use the ’show srp topology’ CLI
to identify which nodes are wrapped.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-957
Layer 2 Messages
SSRP Messages
Error Message
%L2-SRP-3-ERR_MEDIA_WRAP
[chars] [chars] on side [char] ([chars])
Explanation The specified side of the interface has wrapped or unwrapped for the given reason.
There is/was a fault (or user request) on the ring causing potential loss of traffic/bandwidth.
Recommended Action Clear the cause of the fault/wrap. Use the ’show srp ips’ and ’show srp failures’
CLI to determine the root cause of the fault (if still present).
Error Message
%L2-SRP-3-ERR_SRR_VER_MISMATCH
[chars] SRR version mismatch detected.
Explanation SRR has detected incompatible versions with other nodes on the ring and cannot
inter-operate.
Recommended Action Update the software image on all nodes of the ring to the same SRR version.
Error Message
%L2-SRP-6-INFO_SINGLE_NODE_TOPO
[chars]: Single node in topology
Explanation The topology discovery resulted in a single node being found. This is most likely a
transient condition during initial ring bring-up.
Recommended Action Verify that the condition is not transient by using ’show srp topology’ CLI.
Verify the interface is not physically looped back, meaning side A is connected to side B. Verify that
the other nodes are not in PassThru mode (ADMIN DOWN). Verify that neither of the adjacent
nodes have the same BIA address by using ’show interface srp’ CLI. If a duplicate BIA address is
found: Copy the error message exactly as it appears on the console or in the system log, call your
Cisco technical support representative and provide the representative with the gathered information.
SSRP Messages
Error Message
%L2-SSRP-3-ERR_INIT
Error initializing the SSRP subsystem: [chars]
Explanation An error was encountered whilst initializing the SSRP subsystem: %s.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Consider restarting the PPP MA process. *SUPPORT*.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-958
OL-23348-01
Layer 2 Messages
SSRP Messages
Error Message
%L2-SSRP-4-ERR_BACKEND
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the Backend service related to use of either SysDB
or SubDB. The error message describes what operation has failed and why it failed. The most likely
reason for this is low memory resources or a programming error.
Recommended Action Consider restarting the PPP MA process. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-SSRP-4-ERR_BAD_MAGIC The SSRP group [unsigned int] is receiving bad packets
from the peer. They contain the magic number [hex], should be [hex].
Explanation An SSRP keepalive message has been received containing a magic number which is
different from expected. This either indicates a problem on the peer router, or indicates that SSRP
has somehow begun receiving packets from a different router altogether.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information. Check that the SSRP configuration for the network is correct.
Error Message
%L2-SSRP-4-ERR_BAG
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the Bag Client library. The error message describes
what operation has failed and why it failed. The most likely reason for this a low memory condition
but the error could also be caused by a programming error. The error will affect PPP MA’s ability to
provide operational management data, but won’t otherwise affect PPP MA’s operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*.
Error Message
%L2-SSRP-4-ERR_CREATE_CHANNELS
group [unsigned int]: [chars]
An error has occurred creating channels for SSRP
Explanation SSRP was unable to create the TCP channels for this group.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Consider firstly unconfiguring then reconfiguring the
group. If this has no effect consider restarting the PPP MA process. Copy the error message exactly
as it appears on the console or in the system log, call your Cisco technical support representative
and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-959
Layer 2 Messages
SSRP Messages
Error Message
%L2-SSRP-4-ERR_DEBUG
Unexpected error encountered whilst [chars]: [chars]
Explanation PPP MA encountered an error using the debug service. The error message describes
what operation has failed and why it failed. The error could be caused by low memory resource or
programming error.
Recommended Action In many cases, PPP MA will recover by itself. If it does not then restarting the
process may help. Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*.
Error Message
%L2-SSRP-4-ERR_EVC_CLOSE
Error closing ’[chars]’ connection: [chars]
Explanation SSRP failed to close a connection to an essential service. This is an internal error and it
requires a restart of the process for recovery.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SSRP-4-ERR_EVC_CREATE
Error creating ’[chars]’ connection: [chars]
Explanation SSRP failed to create a connection to an essential service during initialization. This is
an internal error. It requires a restart of the process for recovery.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SSRP-4-ERR_EVC_ERROR
Error resetting ’[chars]’ connection: [chars]
Explanation After detecting an error with the connection to the specified service, SSRP 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-960
OL-23348-01
Layer 2 Messages
SSRP Messages
Error Message
%L2-SSRP-4-ERR_EVC_EVM_HANDLER
connection: [chars]
Error registering for data events on ’[chars]’
Explanation During initialization, SSRP failed to register for input or output notifications for the
specified service. This is an internal error. It requires a restart of the process for recovery.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SSRP-4-ERR_EVC_NOTIFY
connection: [chars]
Error registering for critical events on ’[chars]’
Explanation During initialization, SSRP failed to register for essential notifications regarding the
state of the connection for the specified service. This is an internal error. It requires a restart of the
process for recovery.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SSRP-4-ERR_EVC_OPEN
Error opening ’[chars]’ connection: [chars]
Explanation SSRP failed to open a connection to an essential service during initialization. This is an
internal error. It requires a restart of the process for recovery.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SSRP-4-ERR_EVM_ATTACH
[chars]
Failed to register a handler for ’[chars]’ messages:
Explanation SSRP failed to register a handler for the specified class of event. This is an initialization
error and implies that SSRP will not be able to operate correctly. The PPP MA process will abort
and be restarted in an attempt to recover. The cause may be a resource starvation problem but is most
likely to be an internal programming error. The error message should give more details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Restart the PPP MA process. *RECUR*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-961
Layer 2 Messages
SSRP Messages
Error Message
%L2-SSRP-4-ERR_EVM_SEND
Failed to send ’[chars]’: [chars]
Explanation SSRP failed to send the specified message. The cause may be a resource starvation
problem but is most likely to be an internal programming error. The error message should give more
details.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Restart the affected PPP MA process. *RECUR*
Error Message
%L2-SSRP-4-ERR_LOOPED The SSRP group [unsigned int] appears to be connected to
itself - the peer is using the same magic number [hex].
Explanation An SSRP message has been received containing the local magic number. This makes it
highly likely that the SSRP TCP channel is connected to itself. In the unlikely event that both ends
select the same magic number, a new random number is chosen locally, so the situation will recover
itself.
Recommended Action Check that the SSRP configuration for the network is correct. The most likely
problem is that the peer IPv4 address specified in the SSRP Profile configuration is a local IPv4
address - so the TCP packets that are being sent are simply arriving back on the same router.
Error Message
%L2-SSRP-4-ERR_LTRACE
buffer: [chars]
Unexpected error encountered whilst [chars] the [chars]
Explanation PPP MA encountered an error using the Lightweight Tracing service. The error message
describes what operation has failed and why it failed. This is a fatal error and the PPP MA process
cannot continue. It will abort and subsequently be restarted by SysMgr in an attempt to recover.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-SSRP-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-962
OL-23348-01
Layer 2 Messages
SSRP Messages
Error Message
%L2-SSRP-4-ERR_MGD_TIMER
Unexpected error encountered whilst [chars]: [chars]
Explanation SSRP encountered an unexpected error using the Managed Timer library. This is most
likely to be due to a low memory condition but may also be an internal programming error. The error
message should provide more information about the cause.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Consider restarting the PPP MA process. *RECUR*.
Error Message
%L2-SSRP-4-ERR_REQUEST Unable to process SSRP request for ’[unsigned int]’
sessions to client [chars]: [chars]
Explanation An error has occurred processing an incoming SSRP request for the client.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information. Consider restarting the PPP MA process.
Error Message
%L2-SSRP-4-ERR_SETSOCKOPT
[chars]
Error setting socket options on ’[chars]’ connection:
Explanation While creating a TCP socket, SSRP failed to set the correct options on the socket. This
socket will now not be established correctly.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information. Consider restarting the PPP MA process.
Error Message
%L2-SSRP-4-ERR_SOCKET_QUEUE_FULL
group [unsigned int] is full
The write queue for the TCP socket for SSRP
Explanation The queue for storing messages to write to the TCP socket is full for the specified SSRP
group. This means messages will be dropped.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. Consider restarting the PPP MA process. *SUPPORT*.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-963
Layer 2 Messages
SSRP Messages
Error Message
%L2-SSRP-4-ERR_STATE Unable to process SSRP state for ’[unsigned int]’ sessions
to client [chars]: [chars]
Explanation An error has occurred processing an incoming SSRP state for the client.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information. Consider restarting the PPP MA process.
Error Message
%L2-SSRP-4-ERR_SYSDB
Unexpected error encountered whilst [chars]: [chars]
Explanation SSRP encountered an error using the SysDB service. The error message describes what
operation has failed and why it failed. The most likely reason for this is a connection problem with
the SysDB server, but the error could also be caused by low memory resources or programming
error.
Recommended Action Consider restarting the PPP MA process. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-SSRP-6-ERR_EVC_DESTROY
Error destroying ’[chars]’ connection: [chars]
Explanation During process termination SSRP failed to destroy a connection to a service provided
by another process. This is an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-SSRP-6-SECOND_CONNECTION A second SSRP peer, [chars], has connected to the
TCP channel for SSRP group [unsigned int]. This has removed the previous connection
Explanation A second peer has connected to the Active TCP channel for the specified SSRP group,
while there was already a connection to the socket. This can validly occur if the SSRP peer has gone
away temporarily with being noticed (e.g. due to a process restart, or shutting the peer’s interface),
and has now come back and wants to reconnect. However, it can also occur if there is a
misconfiguration, meaning that more than one SSRP peer wishes to connect to the same SSRP TCP
channel. If this is the case, then SSRP will continually switch between using the two different peers,
and never reach a stable state.
Recommended Action Check that the SSRP configuration for the network is correct. If this message
is only seen once, it is most likely not a problem. However, if this message is seen repeatedly within
a short period of time, this is a strong indication that there is a misconfiguration of SSRP in the
network.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-964
OL-23348-01
Layer 2 Messages
STP_IO Messages
STP_IO Messages
Error Message
%L2-STP_IO-3-ATTACH_FAILED Process is restarting after failing to initialize IO
for [unsigned int] interfaces including CH[hex]: [chars]
Explanation STP was unable to initialize IO for one or more interfaces. BPDUs will not be sent or
received through these interfaces. The process has restarted to attempt to clear 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.
Error Message
%L2-STP_IO-3-BPDU_DROPPED
Stage: [chars]: [chars]
Received a BPDU but could not determine the port.
Explanation A BPDU has been received which STP is unable to read.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-STP_IO-3-BPDU_INCORRECT_DIRECTION
direction
BPDU punted to STP on port CH[hex] in TX
Explanation STP only expects to be punted RX packets, but has received a BPDU with the TX
direction.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-STP_IO-3-BPDU_INCORRECT_DMAC Received a packet on port CH[hex] with an
incorrect destination MAC address: [chars]
Explanation STP received a BPDU with the wrong MAC address, most likely belonging to a different
protocol.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-965
Layer 2 Messages
STP_IO Messages
Error Message
%L2-STP_IO-3-BPDU_INCORRECT_SAP
SAP
Received a BPDU on port CH[hex] with incorrect
Explanation STP received a BPDU with the wrong SAP, most likely belonging to a different
protocol.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-STP_IO-3-BPDU_UNREADABLE
[chars]
STP was unable to read a BPDU received on CH[hex]:
Explanation STP received a BPDU but was unable to read the contents via a call to the Ethernet
Packet Infrastructure.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-STP_IO-3-INVALID_BPDU
IEEE specification.
Received a BPDU on CH[hex] which did not conform to the
Explanation STP received a BPDU which would not be decoded in accordance with section 14.4 of
the IEEE 802.1Q specification.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-STP_IO-3-TIMER_FAILED
timers: [chars]
Restarting after failing to process one or more expired
Explanation An error has occurred processing one or more timer events driving the MSTP engine.
The process has restarted to correct this issue.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-966
OL-23348-01
Layer 2 Messages
STP_IO Messages
Error Message
%L2-STP_IO-4-CFG_FAILED
Failed to process [chars] of [chars] config: [chars]
Explanation The STP IO process has failed to process the indicated configuration event. This event
will not have taken effect.
Recommended Action If a transitory error is indicated then removing and reapplying the
configuration may result in the config being successfully applied. Otherwise, restarting the process
may allow the config to be successfully applied.
Error Message
%L2-STP_IO-4-ERR_PACKET_INVALID_MSTI Received an internal packet on port CH[hex]
referencing unknown MSTI [unsigned int]
Explanation A packet has been received referencing an unknown MSTI, despite the packet being
viewed as internal. This probably indicates an inconsistency on the other end.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-STP_IO-4-ERROR_DISABLING_PORT
disabling is ’[chars]’: [chars].
Error while disabling port CH[hex]. Reason for
Explanation The STP IO process failed an attempt to error-disable a port (in response to, for
example, a BPDU being received on a port with BPDU-guard configured).
Recommended Action STP has attempted to error-disable the port in order to avoid a potential loop in
the network. This port should be disabled until the problem is resolved.
Error Message
%L2-STP_IO-4-INITIALISATION_FAILURE
Failed to initialize [chars]: [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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-967
Layer 2 Messages
STP_IO Messages
Error Message
%L2-STP_IO-4-OOM The STP IO process is restarting due to an Out of Memory
condition. All state should be resynchronized after restart.
Explanation The STP IO process failed to allocate sufficient memory for one of its operations. In
order to recover from this situation, the process is restarting and will resync 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-STP_IO-4-PROBLEM_EXITING An error occurred while determining whether the IO
process should exit, or in exiting: [chars]
Explanation A failure occurred when either checking whether a shutdown of the STP IO process was
required, or in informing 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.
Error Message
%L2-STP_IO-4-PROVIDER_BRIDGE_MISMATCH
[chars] Mode BPDU on port CH[hex].
STP configured in [chars] Mode received a
Explanation STP on this router has been configured in provider-bridge mode, but has been connected
to a router sending BPDUs in non-provider-bridge mode (or vice versa). This is a misconfiguration
and could result in loops in the network.
Recommended Action Examine the STP configuration on this router and on the router to which it is
connects on this port. Ensure that both routers have the same provider bridge mode configuration.
Error Message
%L2-STP_IO-4-RECONNECT_FAILED
Interface Manager: [chars]
Restarting after failing to reset connection to
Explanation STP has encountered an error while attempting to resynchronize its data with Interface
Manager. The process will restart automatically to correct the problem.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-968
OL-23348-01
Layer 2 Messages
STP_IO Messages
Error Message
%L2-STP_IO-4-STANDBY_SYNC_FAILED Standby process is restarting after failing to
correctly synchronize with the active process: [chars]
Explanation STP running on a Standby card was unable to synchronize its state with STP on the
Active card. The Standby process will restart to attempt to resynchronize fully. This should only
impact the Standby node, and traffic should remain unaffected.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-STP_IO-4-UNEXPECTED_BPDU_RECEIVED
CH[hex]
A BPDU was received on portfast port:
Explanation A BPDU was received on a port that was configured for Portfast. This port will now
revert to a ’non-edge’ port.
Recommended Action Check network configuration. Should this port really be configured for
portfast? Has a new network device been added to the network?
Error Message
%L2-STP_IO-4-UNEXPECTED_SYSDB_MESSAGE
type [unsigned int], path ’[chars]’
Received an unexpected message from SysDB,
Explanation STP IO has received a message from SysDB of a form it does not recognize. The
message 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-STP_IO-7-BPDU_ON_UNPROTECTED_PORT
have MSTP configured on it: CH[hex]
Received a BPDU on a port that does not
Explanation A BPDU packet has been received on a port on which STP is not configured. The packet
will be dropped.
Recommended Action If the port in question is L3, then this warning is expected. Otherwise, If the
message recurs, copy the error message exactly as it appears on the console or in the system log, call
your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-969
Layer 2 Messages
STP_LIB Messages
STP_LIB Messages
Error Message
%L2-STP_LIB-3-PROTECT_STATE Failure during STP Protected state update. One or
more ports may not be placed in the correct STP state: [chars]
Explanation A failure occurred whilst notifying infrastructure that one or more ports are under STP
control. If this occurs, these ports may not take the correct STP state, in the worst case leading to
bridging loops forming in the network.
Recommended Action If new port configuration has been added, shut the newly configured ports
down. Remove all MSTP configuration and reapply.
STP Messages
Error Message
%L2-STP-3-PORT_STATE_UPDATES_BLOCKED Port state updates may have failed, and
further updates will be blocked, for [unsigned int] port instances, including
instance [unsigned int] on port [chars]
Explanation Updates to the port states have errored for the indicated instances. 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 stp_controller process should resolve any network disruption
due to the issue, but support should be contacted so the issue can be investigated.
Error Message
%L2-STP-4-ERR_CHKPT_SAVE
CH[hex]: Failed to save Checkpoint data: [chars]
Explanation An error occurred while checkpointing data for the indicated interface. Operational data
may have been lost resulting in an STP process restarts being more impactive.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-970
OL-23348-01
Layer 2 Messages
STP Messages
Error Message
%L2-STP-4-ERR_DB_BATCH_END Failed to checkpoint the latest data, updated after a
batch of operations: [chars] - restarting
Explanation Errors have been seen while attempting to save updates after processing a batch of
operations. The process is restarting to recover from 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.
Error Message
%L2-STP-4-ERR_PORT_ID_RECLAIM Port ID [unsigned int] is recorded as used by
interface [chars], but is also marked as used by another interface
Explanation When recovering the existing data from checkpoint following a restart of the MSTP
controller process, the indicated port ID has been found to be in use on two or more ports, including
that named. The indicated port will not be used by MSTP until the problem is cleared.
Recommended Action Removing and re-adding the indicated port from STP configuration should
result in the error being cleared.
Error Message
%L2-STP-4-INITIALISATION_FAILURE
Failed to initialize [chars]: [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-STP-4-INVALID_L2VPN_STATE
Invalid state received in L2VPN ACK: [unsigned int]
Explanation When acknowledging a state update, the L2VPN infrastructure sent an invalid value.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-971
Layer 2 Messages
STP Messages
Error Message
%L2-STP-4-LOOP_INCONSISTENT
STP moved port [chars] to Loop Inconsistent state
Explanation STP Loopguard feature moves a non-designated port to Loop inconsistent state when it
stops receiving bpdu’s on this port.
Recommended Action The problem might be due to software or hardware issues. Wait for a few
minutes to see if problem clears or the port gets UDLD err-disabled. If not, file ddts with relevant
info and continue. If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Error Message
%L2-STP-4-PORTFAST_CHANGES_PENDING
when ports are shutdown
Portfast state changes will only be enacted
Explanation The MSTP specification dictates that Portfast state changes should only be made whilst
a port is disabled. In order to enact the new portfast configuration, ports should be shutdown.
Recommended Action Shut and unshut any interfaces on which portfast configuration has been
updated.
Error Message
%L2-STP-4-PROBLEM_EXITING
Failed to notify SysMgr of intention to exit: [chars]
Explanation A failure occurred during shutdown of the STP 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.
Error Message
%L2-STP-4-RECONNECT_FAILED
Interface Manager: [chars]
Restarting after failing to reset connection to
Explanation STP has encountered an error while attempting to resynchronize its data with Interface
Manager. The process will restart automatically to correct the problem.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-972
OL-23348-01
Layer 2 Messages
STREE Messages
Error Message
%L2-STP-4-TIMER_FAILED
timers: [chars]
Restarting after failing to process one or more expired
Explanation An error has occurred processing one or more timer events driving the MSTP engine.
The process has restarted to correct this issue.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-STP-6-LOOP_CONSISTENT
STP moved port [chars] to Loop consistent state
Explanation STP Loop inconsistency has been removed due to normal reception of bpdu’s.
Recommended Action No action is required.
STREE Messages
Error Message
%L2-STREE-4-CONNECT_FAIL
STP Server not available
Explanation stp_process is most likely in a bad state or basic system services have failed. stp_process
error messages are generally indicative of health of control-ethernet which is critical for system
operation. Misbehavior of stp_process can cause instability in the system.
Recommended Action Sysmgr process will restart the stp_process if it encounters this error. Check if
the ’stp_process’ is up and running if this error is encountered. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-STREE-4-CREATE_FAIL
STP Create Failed : [chars]
Explanation stp_process ran into errors while creating the spanning tree instance for control
ethernet. stp_process error messages are indicative of health of control-ethernet which is critical for
system operation. Misbehavior of stp_process can cause instability in the system.
Recommended Action Sysmgr process will restart the stp_process if it encounters this error. Check if
the ’stp_process’ is up and running if this error is encountered. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-973
Layer 2 Messages
STREE Messages
Error Message
%L2-STREE-4-MSGSEND_FAIL
Message Send Failed : [chars]
Explanation stp_process is most likely in a bad state or basic system services have failed. stp_process
error messages are generally indicative of health of control-ethernet which is critical for system
operation. Misbehavior of stp_process can cause instability in the system.
Recommended Action Sysmgr process will restart the stp_process if it encounters this error. Check if
the ’stp_process’ is up and running if this error is encountered. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-STREE-4-PORT_CREATE_FAIL
Stp port creation fail : [chars]
Explanation Spanning tree port creation failed on the node. stp_process error messages are indicative
of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can
cause instability in the system.
Recommended Action Spanning tree port creation will be retried automatically. Check if the
’stp_process’ is up and running if this error is encountered. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-STREE-4-SET_MACADDR_FAIL
STP Set Mac Addr Failed : [chars]
Explanation MAC address assigned to the spanning tree was either invalid or was not able to be set
for the spanning tree instance. stp_process error messages are indicative of health of
control-ethernet which is critical for system operation. Misbehavior of stp_process can cause
instability in the system.
Recommended Action Sysmgr process will restart the stp_process if it encounters this error. Check if
the ’stp_process’ is up and running if this error is encountered. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%L2-STREE-4-START_FAIL
Failed to start STP instance : [chars]
Explanation Spanning tree could not be started on the control ethernet for the node. stp_process error
messages are indicative of health of control-ethernet which is critical for system operation.
Misbehavior of stp_process can cause instability in the system.
Recommended Action Sysmgr process will restart the stp_process if it encounters this error. Check if
the ’stp_process’ is up and running if this error is encountered. If the message recurs, copy the error
message exactly as it appears on the console or in the system log, call your Cisco technical support
representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-974
OL-23348-01
Layer 2 Messages
T1E1_LNM Messages
T1E1_LNM Messages
Error Message
%L2-T1E1_LNM-2-REMFAILEDPUBLISH
[chars] to registered features
Controller [chars], failed to report noise
Explanation Noise state on the link has changed for the controller identified in the message. An error
occurred while attempting to report an ’crossed’ threshold value or ’fallen below’ threshold value.
Due to this failure, any applications such as MLPPP registered for notification of these events were
not notified. If the error type is ’crossed’, then Voice quality may be affected.
Recommended Action The controller identified in the message requires administrative attention. If the
reported noise was of type ’crossed’, the administrator may want to remove/replace the link. If the
reported noise was of type ’fallen below’, the administrator may want to put this controller back into
service. Also, the administrator should copy the error message exactly as it appears and report it to
your technical support representative.
Error Message
%L2-T1E1_LNM-3-GENEVENT
[chars]
Explanation An error has occurred in the link noise monitoring.
Recommended Action Copy the error message exactly as it appears and report it to your technical
support representative.
Error Message
%L2-T1E1_LNM-3-MAJWARNNOISE
threshold
Controller [chars], noise [chars] major warning
Explanation Noise on the link identified in the message has either crossed or fallen below the
threshold value configured by the user for major warning level on this controller. Video or voice
quality may be affected if noise is above the configured threshold.
Recommended Action This link requires administrative attention. If noise is at or above the
configured threshold, this may require removing/replacing this controller from service. If noise is
below the configured threshold, the administrator may choose to put this link back into service or
wait until noise has fallen below minor-warning level threshold.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-975
Layer 2 Messages
T1E1_LNM Messages
Error Message
%L2-T1E1_LNM-3-MINWARNNOISE
threshold
Controller [chars], noise [chars] minor warning
Explanation Noise on the link identified in the message has either crossed or fallen below the
threshold value configured by the user for minor warning level on this controller. Video or voice
quality may be affected if noise is above the configured threshold.
Recommended Action This link requires administrative attention. If noise is at or above the
configured threshold, this may require removing/replacing this controller from service. If noise is
below the configured threshold, the administrator may choose to put this link back into service.
Error Message
%L2-T1E1_LNM-3-REMWARNNOISE
Controller [chars], noise [chars] removal threshold
Explanation Noise on the link has either crossed or fallen below the threshold value configured by
the user for link removal on the controller identified in the message. Video or voice quality may be
affected if noise is above the configured threshold.
Recommended Action This link requires administrative attention. If noise is at or above the
configured threshold, only applications such as MLPPP bundles support automatic removal of links
from bundles. For other applications, the administrator may need to remove/replace this controller
from service. If noise is below the configured threshold and was previously taken out of service by
the administrator, the administrator may choose to put this link back into service or wait until noise
has fallen below minor-warning level threshold. For an MLPPP link, this will be done automatically.
Error Message
%L2-T1E1_LNM-5-DISABLED
[chars]
Controller [chars], noise monitoring disabled for level
Explanation Link Noise Monitoring has been disabled for the level and T1/E1 controller specified in
the message.
Recommended Action This is an informational message to notify that Link Noise Monitoring has been
disabled on the T1/E1 controller identified in the message. No user action is required.
Error Message
%L2-T1E1_LNM-5-ENABLED
[chars]
Controller [chars], noise monitoring enabled for level
Explanation Link Noise Monitoring has been enabled for the warning level and T1/E1 controller
specified in the message.
Recommended Action This is an information message to notify that Link Noise Monitoring has been
enabled on the T1/E1 controller identified in the message. No user action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-976
OL-23348-01
Layer 2 Messages
T1E1 Messages
T1E1 Messages
Error Message
%L2-T1E1-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-T1E1-3-ERROR
[chars]([dec]): [chars] failed ([chars]) - [chars]
Explanation A general failure occurred 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 T1E1.
Error Message
%L2-T1E1-4-ALARM
[chars]: [chars] [chars]
Explanation The specified T1E1 Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
Error Message
%L2-T1E1-4-LOOPSTATUS
[chars] [chars]
Explanation A configurable controller loopback status.
Recommended Action None.
Error Message
%L2-T1E1-4-UPDOWN
[chars]: [chars] [chars]
Explanation The specified T1E1 is operationally down due to alarm. Check alarm status using show
controller t1 command on the cli.
Recommended Action Recommended action is to repair the source of the alarm.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-977
Layer 2 Messages
T3E3 Messages
Error Message
%L2-T1E1-4-WARNING
[chars]([dec]): [chars] - [chars]
Explanation A non-fatal error occurred 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 T1E1.
T3E3 Messages
Error Message
%L2-T3E3-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-T3E3-3-ERROR
[chars]([dec]): [chars] failed ([chars]) - [chars]
Explanation A general failure occurred 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 T3E3.
Error Message
%L2-T3E3-4-ALARM
[chars]: [chars] [chars]
Explanation The specified T3E3 Alarm has been declared or released.
Recommended Action Recommended action is to repair the source of the alarm.
Error Message
%L2-T3E3-4-FEAC
[chars] [chars]
Explanation New Far End Alarm Code received.
Recommended Action None.
Error Message
%L2-T3E3-4-LOOPSTATUS
[chars] [chars]
Explanation A configurable controller loopback status.
Recommended Action None.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-978
OL-23348-01
Layer 2 Messages
TCAM_RM_CARVE_VERIFY Messages
Error Message
%L2-T3E3-4-PM
[chars]([dec]): [chars]
Explanation Performance Monitoring Related Warnings/Errors.
Recommended Action None.
Error Message
%L2-T3E3-4-UPDOWN
[chars]: [chars] [chars]
Explanation The specified T3E3 is operationally down due to alarm. Check alarm status using show
controller t3 command on the cli.
Recommended Action Recommended action is to repair the source of the alarm.
Error Message
%L2-T3E3-4-WARNING
[chars]([dec]): [chars] - [chars]
Explanation A non-fatal error occurred 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 T3E3.
TCAM_RM_CARVE_VERIFY Messages
Error Message
%L2-TCAM_RM_CARVE_VERIFY-3-FATAL_ERR
Fatal error: [chars]: Err equals [dec]
Explanation A fatal error occurred in TCAM RM Carve Verify which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-TCAM_RM_CARVE_VERIFY-6-INFO_MSG
Info: [chars]
Explanation This is an informational message in the TCAM RM Carve for Engine3 linecard.
Recommended Action Informational message from the TCAM RM; currently seen for successful
re-carving of TCAM regions on E3 linecard. This should be harmless (by itself) and suggests user
to reload the linecard for TCAM re-carving to take effect.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-979
Layer 2 Messages
TCAM_RM Messages
TCAM_RM Messages
Error Message
%L2-TCAM_RM-3-BLWM_CLIENT_CONF_FAILED
error: [hex] [chars]
tcam_rm: blwm client configuration failed,
Explanation Unable to configure BLWM client functionality.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-TCAM_RM-3-BLWM_CLIENT_REBIND_FAILED
error: [hex] [chars]
tcam_rm: blwm client rebind failed,
Explanation Unable to rebind with BLWM client functionality after a connection reconnect.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-TCAM_RM-3-BLWM_FAILED_MSG_DUMP
REG-ID [dec]
vmrid [hex] vmrid_p 0x[pointer],
rc [chars][[dec]]
TCAM RM: [chars] [dec] REGN TYPE [chars]
Explanation Dump of the value, mask, result, stage, region-id of MSG sent to the TCAM_RM server.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-TCAM_RM-3-BLWM_FAILED_MSG_MASK_DUMP TCAM_RM MASK:
[hex]%02x[hex]%02x[hex]%02x[hex]%02x[hex]
Explanation Dump of the mask MSG sent to the TCAM_RM server.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-980
OL-23348-01
Layer 2 Messages
TCAM_RM Messages
Error Message
%L2-TCAM_RM-3-BLWM_FAILED_MSG_RESULT_DUMP TCAM_RM RESULT:
[hex]%02x[hex]%02x[hex]%02x[hex]%02x [hex]%02x[hex]%02x[hex]%02x[hex]%02x
Explanation Dump of the result MSG sent to the TCAM_RM server.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-TCAM_RM-3-BLWM_FAILED_MSG_VALUE_DUMP TCAM_RM VALUE:
[hex]%02x[hex]%02x[hex]%02x[hex]%02x[hex]
Explanation Dump of the value MSG sent to the TCAM_RM server.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-TCAM_RM-3-BLWM_MSG_SEND_FAILED tcam_rm: blwm msg send/flush: retried: [dec]
time(s), failed to send, error: [hex] [chars]
Explanation Unable to send/flush a BLWM message to the TCAM_RM server.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-TCAM_RM-3-BLWM_RECVD_REPLY_FAIL tcam_rm: Received a failure reply code for a
batched request type [dec], failed reason: [chars]
Explanation This is the message printed by the default handler installed by TCAM_RM to process
the replies received for batched requests. The default handler’s behavior is to just print this message.
The application should install its own handler to handle the replies to batched requests.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-981
Layer 2 Messages
TCAM_RM Messages
Error Message
%L2-TCAM_RM-3-FATAL_ERR
Fatal error: [chars]: Err equals [dec]
Explanation A fatal error occurred in TCAM RM which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-TCAM_RM-3-MSG_SEND_FAILED tcam_rm: msg: [dec], retried: [dec] time(s),
failed to send, errno: [chars]
Explanation Unable to send a message to the TCAM RM server.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-TCAM_RM-3-NONFATAL_ERR
Nonfatal error: [chars]: Err equals [dec]
Explanation This is a error message in the TCAM RM to indicate anomalies which are not FATAL.
Some of the messages may indicate a failure to allocate resources needed by applications. In many
cases these messages must not keep appearing after the temporary situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-TCAM_RM-3-RETURN_ERROR
[chars]
tcam_rm: TCAM returned [dec] ([chars]) because
Explanation This is the message printed by the default handler installed by TCAM_RM to process
the no memory reply received for batched requests. The default handler’s behavior is to just print
this message. The application should install its own handler to handle the replies to batched requests.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-982
OL-23348-01
Layer 2 Messages
TCAM_RM Messages
Error Message
%L2-TCAM_RM-3-TCAM_RM_RECVD_REPLY_NOMEM tcam_rm: TCAM could not satisfy
allocation request, the node may not function as expected.
Explanation This is the message printed by the default handler installed by TCAM_RM to process
the no memory reply received for batched requests. The default handler’s behavior is to just print
this message. The application should install its own handler to handle the replies to batched requests.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-TCAM_RM-4-BLWM_REPLAY_REQUEST tcam_rm: Replaying a batched request of type
[dec] that might have been partially processed before.
Explanation Due to a server restart, a batched request might have been partially processed. The
default handler installed by TCAM_RM simply replays the request. Applications that can not afford
to replay a request should install their own handler.
Recommended Action No action is required.
Error Message
%L2-TCAM_RM-4-CACHE_ERR_COUNT tcam_rm: Client Cache Insert warning: Error
Count:[dec] Cache Msg type:[dec] Request VMR id: [hex] Cache VMR id: [hex] VMR id
pointer: 0x[pointer]
Explanation If the error count is incrementing there is a discrepancy in the vmr_id pointer in the
shared memory. These entries which are being merged do not have the same vmr_id and this can
cause a potential memory leak.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-TCAM_RM-4-CACHE_UNSUPPORTED_OP_SEQUENCE
msg code :[dec] curr msg code :[dec]
tcam_rm: prep request warning: prev
Explanation If this error message is seen, the client of tcam_rm is attempting to send updates in an
unsupported sequence.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-983
Layer 2 Messages
UDLD Messages
Error Message
%L2-TCAM_RM-4-REPLY_HDLR_ERR_COUNT tcam_rm: Batch Reply Handler warning: Error
Count:[dec] Cache Msg type:[dec] Req VMR id: [hex] Expected VMR id: [hex] Resp VMR
id: [hex] Req VMR id pointer: 0x[pointer]
Explanation If the error count is incrementing there is a discrepancy in the vmr_id pointer in the
shared memory. These entries which are being merged do not have the same vmr_id and this can
cause a potential memory leak.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-TCAM_RM-5-PARITY_ERR Parity error corrected: ASIC Side equals [chars], TCAM
Type equals [chars] TCAM Dev equals [dec], TCAM Offset equals [hex]
Explanation This is an informational message from the TCAM RM to indicate that it received TCAM
parity error Interrupt notification message and corrected the corrupted tcam cell offset through its
shadow image.
Recommended Action Monitor system for additional parity errors. If parity error recurs on this device,
contact support.
Error Message
%L2-TCAM_RM-6-INFO_MSG
Info: [chars]
Explanation This is an informational message in the TCAM RM.
Recommended Action No action is required.
UDLD Messages
Error Message
%L2-UDLD-4-DISABLE_PORT
Port Disabled
UDLD protocol detected Uni-directional link on [chars],
Explanation UDLD protocol detects if a link is uni-directional and disables the port. Uni-directional
links can cause problems in ethernet networks and should be fixed.
Recommended Action Check the link on which the error happened. Try replacing/reconnecting the
GBIC/SFP/cable at either end of the link. Re-enable the port on the RP and see if the port comes up.
If the problem still exists the port will be disabled again with this message. If the message recurs,
copy the error message exactly as it appears on the console or in the system log, call your Cisco
technical support representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-984
OL-23348-01
Layer 2 Messages
UIDB_RM Messages
UIDB_RM Messages
Error Message
%L2-UIDB_RM-3-INIT_ERR
Process initialization failed: ([chars]%s)
Explanation The uidb-mgr-main process failed to initialize. A uidb is defined as a ’Micro
Information Data-Base’ used by the hardware ASIC’s in the forwarding path. The uidb-mgr-main
process is responsible for allocating/de-allocating the hardware uidb’s as configured by sw. If the
uidb manager fails to initialize, no interfaces can be created or deleted on the linecard. %s - indicates
the reason for the failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this
process, up to a fixed number of times when this error is encountered, to recover. Execute ’show
process uidb_mgr_main location 0/x/cpu0’ to verify that the process is up and running. If it is still
non-operational, try doing ’process restart uidb_mgr_main location 0/x/cpu0’. If the message
recurs, copy the error message exactly as it appears on the console or in the system log, call your
Cisco technical support representative and provide the representative with the gathered information.
VCM_EA Messages
Error Message
%L2-VCM_EA-2-INTERNAL_ERR
[chars]
Explanation Internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-VCM_EA-2-INTERNAL_ERR_2
[chars]: [chars]
Explanation Internal error with error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-985
Layer 2 Messages
VCM Messages
VCM Messages
Error Message
%L2-VCM-2-IM_ATTR_ERR
IM Attribute Error : [chars] : [dec]
Explanation Error in IM(Interface Manager) Attribute operation %s - Failure %s - Reason for the
failure
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information. Restart the fr_vcm/atm_vcm process depending on
whichever is appropriate. If it is a memory related error, LC reload only can resolve the issue.
Error Message
%L2-VCM-2-IM_ERR
[chars] : [chars]
Explanation Error in IM(Interface Manager) operation. We get this error if the connection with IM
does not exist or IM is not ready. This happens on the LC with ATM/FR 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. If it is a IM(Interface Manager) connection error, it will automatically recovered.
Nothing has to be done. If it is a PVC creation failure, try deleting and re-adding the pvc once again.
Error Message
%L2-VCM-2-IM_PROC_DOWN
IM process down: [chars]
Explanation IM(Interface Manager) did not come up before the timer expired
Recommended Action IM(Interface Manager) is down. Remove and reapply the config after the IM
comes up.
vlan_netio Messages
Error Message
%L2-vlan_netio-4-DEBUG_INIT_ERROR
(error: [chars])
An error occurred during debug initialization
Explanation The VLAN NetIO component encountered 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-986
OL-23348-01
Layer 2 Messages
vlea Messages
vlea Messages
Error Message
%L2-vlea-3-NATIVE_VLAN_NOTIF
VLAN (error: [chars])
Failed to generate a notification for the Native
Explanation The VLAN EA process encountered a problem while trying to send a Native VLAN
change notification. Native VLAN support for interfaces on the affected node may not function
correctly.
Recommended Action Restart the VLAN EA process on the affected node with process restart vlan_ea
location (node). If the message recurs, copy the error message exactly as it appears on the console
or in the system log, call your Cisco technical support representative and provide the representative
with the gathered information.
Error Message
%L2-vlea-3-NO_STATS
[chars])
VLAN EA failed to register with the statistics server (error:
Explanation The VLAN EA process encountered an error while registering with the statistics server
process. No VLAN sub-interface statistics will be gathered on the given linecard.
Recommended Action This error message indicates a problem with in the statistics server process on
the RP, or with the communications between the linecard and the RP. Copy the error message exactly
as it appears on the console or in the system log, call your Cisco technical support representative
and provide the representative with the gathered information.
Error Message
%L2-vlea-4-EVENT_BLOCK
[chars])
An error was received while waiting for an event (error:
Explanation The VLAN EA process encountered an error while listening for events. The process will
automatically restart and retry.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-987
Layer 2 Messages
vlma Messages
Error Message
%L2-vlea-4-IM_RESYNC_FAILURE Errors during resynchronization with the IM
infrastructure (error: [chars])
Explanation The VLAN EA process encountered an error during resynchronization with the IMP
process. This error message either indicates that the VLAN EA process never received an end of
replay message from IM, or it received an inconsistent dataset from IM.
Recommended Action The system will attempt to recover automatically. If this fails a restart of the
IM process on the affected node is recommended to aid 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-vlea-4-INIT_FAILED
VLAN EA initialization failed: [chars] (error: [chars])
Explanation The VLAN EA process failed to initialize. The process will automatically restart and
retry. Until it succeeds, VLAN functionality may not work on the affected node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-vlea-6-NO_MEM
Out of memory (failed attempt to reserve [unsigned int] bytes)
Explanation The VLAN EA process was not able to allocate the memory that it needed to complete
the operation. VLAN functionality on the affected node may be reduced until the problem is
resolved.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
vlma Messages
Error Message
%L2-vlma-3-IM_CONNECT_FAILED
Failed to connect to IM, err: [chars]
Explanation The VLAN MA process failed to connect to the IM server.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-988
OL-23348-01
Layer 2 Messages
vlma Messages
Error Message
%L2-vlma-3-L2VPN_DISCONNECT_FAILED The handling of a L2VPN Mgr disconnect
notification failed for [unsigned int] trunk interface(s). The first failure was
on [chars] (with error: [chars])
Explanation When the VLAN MA notices that it has lost its connection to the L2VPN Manager
process, it needs to update its database to reflect this. This error message indicates that this the
update failed. The only expected scenario that could cause the error is a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration. *RECUR*
Error Message
%L2-vlma-4-ASYNC_HANDLER
err: [chars]
Couldn’t install the default handler for async msgs,
Explanation The VLAN MA process couldn’t install the default event handler for async msgs.
Recommended Action No action is required.
Error Message
%L2-vlma-4-EVENT_BLOCK An error was received while waiting for an event on the
[chars] (error: [chars])
Explanation The VLAN MA process encountered an error while listening for events. The process
will automatically restart and retry.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-vlma-4-INIT_FAILED
VLAN MA initialization failed: [chars] (error: [chars])
Explanation The VLAN MA process failed to initialize. Previous messages may give the reason. The
process will automatically restart and retry. Until it succeeds, VLAN functionality may not work on
the affected node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-989
Layer 2 Messages
vlma Messages
Error Message
%L2-vlma-4-RECOVERY_FAILED_BATCH Failed to handle [chars] for [unsigned int]
interfaces ([unsigned int] failed, first failure [chars], last failure [chars]),
due to the [chars] error: [chars]
Explanation The VLAN MA failed to resynchronize its configuration with another component in the
system after an earlier failure, or process restart.
Recommended Action After gathering the information specified, it may help to restart the VLAN MA
process on the affected node, with proc restart vlan_ma location [location]. If this restart completes
without the message appearing again, the problem has been resolved. If the message recurs, copy
the error message exactly as it appears on the console or in the system log, call your Cisco technical
support representative and provide the representative with the gathered information.
Error Message
%L2-vlma-4-RECOVERY_FAILED_SINGLE
the error: [chars]
Failed to handle [chars] for [chars], due to
Explanation The VLAN MA failed to resynchronize its configuration with another component in the
system after an earlier failure, or process restart.
Recommended Action After gathering the information specified, it may help to restart the VLAN MA
process on the affected node, with proc restart vlan_ma location [location]. If this restart completes
without the message appearing again, the problem has been resolved. If the message recurs, copy
the error message exactly as it appears on the console or in the system log, call your Cisco technical
support representative and provide the representative with the gathered information.
Error Message
%L2-vlma-6-NO_MEM
Out of memory (failed attempt to reserve [unsigned int] bytes)
Explanation The VLAN MA process was not able to allocate the memory that it needed to complete
the operation. VLAN functionality on the affected node may be reduced until the problem is
resolved.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-990
OL-23348-01
Layer 2 Messages
VPA_1P_OC192 Messages
Error Message
%L2-vlma-6-UNKNOWN_NODE_VLAN_LIMIT Failed to determine the maximum number of VLAN
sub-interface that are allowed to be configured on the given node (error: [chars])
Explanation A failure occurred while trying to determine the maximum number of VLAN
sub-interfaces that can be supported on the given node. The system may allow configuration of more
VLAN sub-interfaces that can be supported, or may not allow the full number supported to be
configured.
Recommended Action After gathering the information specified, it may help to restart the VLAN MA
process on the affected node, with proc restart vlan_ma location [location]. If this restart completes
without the message appearing again, the problem has been resolved. If the message recurs, copy
the error message exactly as it appears on the console or in the system log, call your Cisco technical
support representative and provide the representative with the gathered information.
VPA_1P_OC192 Messages
Error Message
%L2-VPA_1P_OC192-3-DRV_INIT_ERR Initialization of SPA driver failed: [chars] :
reason equals [chars] ; exiting...
Explanation SPA driver encountered the annunciated error during the driver initialization. The
System Manager process (sysmgr) will automatically respawn the (vpa_1_oc192) process, up to a
fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will
trigger node reload. After a certain number of node reloads, the shelf manager will permanently
shutdown the node.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-VPA_1P_OC192-3-GENERIC_ERROR
[chars] : reason equals [chars]
Explanation SPA OC192 driver error messages
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-991
Layer 2 Messages
VPA_1P_OC192 Messages
Error Message
%L2-VPA_1P_OC192-3-GET_NODEID_ERR
[chars] : reason equals [chars]
Explanation SPA driver failed to obtain either its node ID or extract rack/slot/instance information
(having obtained the node ID).
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-VPA_1P_OC192-3-MEM_ERR
[chars]
Explanation fail to allocate memory
Recommended Action show process memory to find out whether there is potential memory leak show
memory to confirm system memory goes low
Error Message
%L2-VPA_1P_OC192-6-OPTICS_INSERTION
Optics module inserted into SPA in bay [dec]
Explanation Optics module has inserted
Recommended Action none
Error Message
%L2-VPA_1P_OC192-6-OPTICS_REMOVAL
Optics module removed from SPA in bay [dec]
Explanation Optics module has removed
Recommended Action none
Error Message
%L2-VPA_1P_OC192-6-PORT_DEL_INFO
[chars] [dec] [chars]
Explanation Port deletion happened after the threshold time.
Recommended Action This is an informational message. Upon seeing this message collect log via
’show tech-support pos’ and send it to the Engineering team.
Error Message
%L2-VPA_1P_OC192-7-DEBUG
[chars] [chars]
Explanation SPA OC192 debug message
Recommended Action *NONE*
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-992
OL-23348-01
Layer 2 Messages
VPA_8P_GE Messages
Error Message
%L2-VPA_1P_OC192-7-ERR
[chars]
Explanation fails to init debug event manager fails to provide its service
Recommended Action ’show logging’ to confirm there is any error from event mgr
Error Message
%L2-VPA_1P_OC192-7-INFO
[chars]: bay equals [dec] : [chars]
Explanation OC192VPA driver general info.
Recommended Action show asic-error plim asic .. loc
VPA_8P_GE Messages
Error Message
%L2-VPA_8P_GE-1-LTRACE_INIT_ERR
[chars]
Explanation Jacket process spawns the SPA process and waits for the initialization to complete. But
initialization fails putting SPA into FAILED state. As a part of the above, we find the message Ltrace
init failed message.
Recommended Action If the issue occurs, Check the SPA state. If it is not OK, then collect the
following traces 1) show plim jacket all location 2) show hw-module traces infra detailed location
3) show plim ether trace info/error location 4) console logs
Error Message
%L2-VPA_8P_GE-2-LTRACE_RETRY_ERR
[chars]
Explanation Jacket process spawns the SPA process and waits for the initialization to complete. But
initialization fails putting SPA into FAILED state. As part of retry mechanism, the above message
is seen.
Recommended Action If the issue occurs, Check the SPA state. If it is not OK, then collect the
following traces 1) show plim jacket all location 2) show hw-module traces infra detailed location
3) show plim ether trace info/error location 4) console logs
Error Message
%L2-VPA_8P_GE-2-SPA_CTX_ERR
[chars]
Explanation The spa_ether_ctx context data cannot be set.
Recommended Action collect the trace log via ’show plim ether trace error location ’ ’show plim ether
trace info location ’ ’show tech-support ethernet ’ ’show plim jacket trace all location ’ and collect
console logs and send them to the Engineering team.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-993
Layer 2 Messages
VPA_8P_GE Messages
Error Message
%L2-VPA_8P_GE-2-SPA_JKT_ERR
[chars] [chars]
Explanation The Jacket failed to parse spa driver arguments.
Recommended Action --
Error Message
%L2-VPA_8P_GE-2-SPA_MAC_ERR
[chars]
Explanation The internal SPA MAC got out of sync. SW needs to reset the device in order to clear
the issue
Recommended Action If resetting the MAC device fixes the issue, nothing needs to be done. If the
reset does not work, the SPA will need to be SW OIR’d. This can be easily checked by doing ’top’
on the LC with the issue. If the CPU is very high, the reset did not work.
Error Message
%L2-VPA_8P_GE-3-PORT_DEL_TIMEOUT
[chars] [dec]
Explanation Port deletion failed to complete within the timeout period.
Recommended Action Upon seeing this message collect the trace log via ’show plim ether trace error
location ’ ’show plim ether trace info location ’ ’show tech-support ethernet ’ and send them to the
Engineering team.
Error Message
%L2-VPA_8P_GE-4-INVALID_MAC Failed to get MAC address for port [dec], Interface
assigned random MAC address.
Explanation PLIM driver was unable to get a MAC address for the interface.
Recommended Action Check if the process ’shelfmgr’ is up and running on the RP. Try to reload the
LC to see if that helps. Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-VPA_8P_GE-6-PORT_DEL_INFO
[chars] [dec] [chars]
Explanation Port deletion happened after the threshold time.
Recommended Action This is an informational message. Upon seeing this message collect the trace
log via ’show plim ether trace error location ’ ’show plim ether trace info location ’ ’show
tech-support ethernet ’ and send them to the Engineering team.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-994
OL-23348-01
Layer 2 Messages
VPA_RULES Messages
VPA_RULES Messages
Error Message
%L2-VPA_RULES-4-DEBUG_INIT_ERR
[chars] [dec] [chars]
Explanation Internal error. SPA rules library debug library initialization 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.
VPLS Messages
Error Message
%L2-VPLS-3-VPLS_ID_CONFLICT
[chars]
Bridge domains [chars] and [chars], VPLS-ID conflict
Explanation ’The VPLS ID conflict happens when a configured VPLS-ID value of a ’ ’bridge domain
equals to default value of VPLS-ID of another bridge ’ ’domain. The consequent action in case of
conflict ’ ’is that the bridge domain with default VPLS-ID remains in the ’ ’state of ’NOT
Advertised’. ’
Recommended Action ’Use ’show l2vpn bridge-domain details’ to view the states of the ’ ’bridge
domain with conflicting VPLS-ID and the VPLS-ID value. ’ ’The conflict can be cleared by
changing the VPLS-ID or VPN-ID ’ ’of VFI with default VPLS-ID. ’
WAHOO Messages
Error Message
%L2-WAHOO-3-ERR_ACCESS
Memory access Error: [chars]: Err equals [dec]
Explanation A memory access error occurred in programmable switching engine (PSE) driver which
involves exiting the process. %s - indicates the reason for the failure. %d - is the decoded error
reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this
process, up to a fixed number of times when this error is encountered, to recover. If the message
recurs, copy the error message exactly as it appears on the console or in the system log, call your
Cisco technical support representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-995
Layer 2 Messages
WAHOO Messages
Error Message
%L2-WAHOO-4-INTERRUPT_WARNING
[chars] interrupt [chars]%s
Explanation This is an warning message in the programmable switching Engine driver to indicate an
operation during interrupt from programmable switching engine (PSE). %s - indicates the PSE
(RX/TX) information is about. %s - indicates the interrupt name. %s - indicates the warning
message.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-WAHOO-6-INFO_MSG
[chars] [chars] [chars]: [hex]
Explanation This is an informational message in the programmable switching Engine driver to
indicate an operation. %s - indicates the PSE (RX/TX) information is about. %s - indicates the
pipeline (0-3) information is about. %s - indicates the information message. %x - indicates the
register value.
Recommended Action Debug message only. No action is required.
Error Message
%L2-WAHOO-6-INTERRUPT_INFO
[chars]
Explanation This is an informational message in the programmable switching Engine driver to
indicate an operation during interrupt from programmable switching engine (PSE). %s - indicates
the PSE (RX/TX) information is about. %s - indicates the information message.
Recommended Action Debug message only. No action is required.
Error Message
%L2-WAHOO-6-STATS_INFO_MSG
WahooStats-Info: [chars]
Explanation This is an informational message in the stats collection logic of hfa_main.
Recommended Action These message are used to dump debugging data when an unexpected rollover
condition is hit for the QoS counters. There is some auto-correct logic using retrial mechanism
embedded to avoid any impact on counters. However, if the messages are seen too frequently or any
inconsistency is observed in QoS counters, the following logs need to be collected: show running
config For all interfaces of the LC that is throwing these msgs, * show imds interface ifname * show
policy-map interface ifname -- To be collected 3-4 times consecutively. If the message recurs, copy
the error message exactly as it appears on the console or in the system log, call your Cisco technical
support representative and provide the representative with the gathered information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-996
OL-23348-01
Layer 2 Messages
WAHOO Messages
Error Message
%L2-WAHOO-7-ERR_PIPE_STUCK
Pipe stuck error: [chars]: Err equals [dec]
Explanation An error occurred in programmable switching engine (PSE) driver during pausing and
resuming the pipe in PSE. %s - indicates the reason for the failure. %d - is the decoded error reason.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-WAHOO-7-PAIR_PCR_REG
[chars] [chars] PAIR’s PCR register status for pipe [dec]: [hex]
Explanation This is a debug message to display PAIR PCR registers of programmable switching
engine (PSE).
Recommended Action Debug message only. No action is required.
Error Message
%L2-WAHOO-7-PAIR_REG
[chars] [chars] PAIR registers for pipe [dec]:pcr [hex] plu_pirl [hex] pirm1 [hex]
pirm2 [hex] pirh [hex] mpls_label [hex] mpls_info [hex]
ip_header [hex] l4_port [hex] start_adr [hex] msq_info [hex]
ltr [hex] tlu_force [hex] pre_cam_prof [hex] lbl1_lo [hex]
lbl1_hi [hex] lbl2_lo [hex] lbl2_hi [hex] leaf1_word1 [hex]
leaf1_word2 [hex] leaf1_word3 [hex] leaf1_word4 [hex] leaf2_word1 [hex]
leaf2_word2 [hex] leaf2_word3 [hex] leaf2_word4 [hex] tcam_cont [hex]
ipv4/v6_dst_1 [hex] ipv4/v6_dst_2 [hex] ipv4/v6_dst_3 [hex] ipv4/v6_dst_4 [hex]
ipv4/v6_src_1 [hex] ipv4/v6_src_2 [hex] ipv4/v6_src_3 [hex] ipv4/v6_src_4 [hex]
mcast_info [hex] ipv6_info [hex] msq_data [hex]
Explanation This is a debug message to display PAIR registers of programmable switching engine
(PSE).
Recommended Action Debug message only. No action is required.
Error Message
%L2-WAHOO-7-PAIR_REG_LIST
[chars] [chars] PAIR registers for pipe [dec]:pcr [hex] plu_pirl [hex] pirm1 [hex]
pirm2 [hex] pirh [hex] mpls_label [hex] mpls_info [hex]
ip_header [hex] l4_port [hex] start_adr [hex] msq_info [hex]
ltr [hex] tlu_force [hex] pre_cam_prof [hex] lbl1_lo [hex]
lbl1_hi [hex] lbl2_lo [hex] lbl2_hi [hex] leaf1_word1 [hex]
leaf1_word2 [hex] leaf1_word3 [hex] leaf1_word4 [hex] leaf2_word1 [hex]
leaf2_word2 [hex] leaf2_word3 [hex] leaf2_word4 [hex] cam_cont [hex]
Explanation This is a debug message to display PAIR registers list of programmable switching
engine (PSE).
Recommended Action Debug message only. No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-997
Layer 2 Messages
WAHOO Messages
Error Message
%L2-WAHOO-7-PHB_DUMP
[hex]: [hex] [hex] [hex] [hex]
Explanation This is a debug message to display PHB dump of programmable switching engine
(PSE).
Recommended Action Debug message only. No action is required.
Error Message
%L2-WAHOO-7-REG_DUMP [chars]:
pipe0_interrupt_reg [hex] pipe1_interrupt_reg [hex] pipe2_interrupt_reg [hex]
pipe3_interrupt_reg [hex]
mask_of_int_enable [hex] cpu_latched_error_addr_reg [hex]
cpu100_control_reg [hex] cpu_150_control_reg [hex]
cpu_latched_error_data_hi_reg [hex] cpu_latched_error_data_lo_reg [hex]
cpu_latched_error_parity_reg [hex] pf_error_reg [hex] p0_fs_error_reg [hex]
p1_fs_error_reg [hex] p2_fs_error_reg [hex] p3_fs_error_reg [hex]
p0_imp_int_status_reg [hex] p1_imp_int_status_reg [hex] p2_imp_int_status_reg
[hex] p3_imp_int_status [hex]
p0_imp_pc [hex] p1_imp_pc [hex] p2_imp_pc [hex] p3_imp_pc [hex]
p0_prep_int_status [hex] p1_prep_int_status [hex] p2_prep_int_status [hex]
p3_prep_int_status [hex]
p0_prep_pc [hex] p1_prep_pc [hex] p2_prep_pc [hex] p3_prep_pc [hex]
p0_pc1_status [hex] p1_pc1_status [hex] p2_pc1_stats [hex] p3_pc1_status [hex]
p0_tlu_int_status [hex] p1_tlu_int_status [hex] p2_tlu_int_status [hex]
p3_tlu_int_status [hex]
p0_mip_int_status [hex] p1_mip_int_status [hex] p2_mip_int_status [hex]
p3_mip_int_status [hex]
p0_mip_pc [hex] p1_mip_pc [hex] p2_mip_pc [hex] p3_mip_pc [hex]
p0_pc2_status [hex] p1_pc2_status [hex] p2_pc2_status [hex] p3_pc2_status [hex]
class cam_status [hex]
p0_pop_int_status [hex] p1_pop_int_status [hex] p2_pop_int_status [hex]
p3_pop_int_status [hex]
p0_pop_pc [hex] p1_pop_pc [hex] p2_pop_pc [hex] p3_pop_pc [hex]
p0_ppc_ctl [hex] p1_ppc_ctl [hex] p2_ppc_ctl [hex] p3_ppc_ctl [hex]
p0_pl_aa_pak_avl_1_reg [hex] p1_pl_aa_pak_avl_1_reg [hex] p2_pl_aa_pak_avl_1_reg
[hex] p3_pl_aa_pak_avl_1_reg [hex]
p0_pl_aa_end_reg [hex] p1_pl_aa_end_reg [hex] p2_pl_aa_end_reg [hex]
p3_pl_aa_end_reg [hex]
p0_pl_aa_fatal_err_reg [hex] p1_pl_aa_fatal_err_reg [hex] p2_pl_aa_fatal_err_reg
[hex] p3_pl_aa_fatal_err_reg [hex]
p0_gather_int_stat_reg [hex] p1_gather_int_stat_reg [hex] p2_gather_int_stat_reg
[hex] p3_gather_int_stat_reg [hex]
xbm_err_reg [hex] ftc_status_reg [hex] ffc_status_error_reg [hex]
ffc_ecc_err_add_reg [hex] ffc_ecc_err_msb_data_reg [hex]
ffc_ecc_err_lsb_data_reg [hex]
ffc_invalid_address_err_reg [hex] ffc_fcram_addr_err_agent_reg [hex]
fsr_invalid_addr_err_reg [hex] fsr_controller_err_reg [hex]
csc_status_reg [hex] cam_status_reg [hex] nfc_status_reg [hex]
Explanation This is a debug message to display registers of programmable switching engine (PSE).
Recommended Action Debug message only. No action is required.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-998
OL-23348-01
Layer 2 Messages
WAN_INARP Messages
WAN_INARP Messages
Error Message
%L2-WAN_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-WAN_INARP-3-CONFIG
config error, [chars][[dec]]: [chars]
Explanation A configuration update has caused a problem inside the InARP code - InARP should
continue but may have ignored the latest config change
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
Error Message
%L2-WAN_INARP-3-NOMEM
possibly 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-WAN_INARP-3-UNKNOWN_EVENT
received an unknown event: [dec]
Explanation The system must be sending messages we didn’t register for. They 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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-999
Layer 2 Messages
WAN_INARP Messages
Error Message
%L2-WAN_INARP-3-UNKNOWN_FSMSTATE
The fsm state ([dec]) is invalid
Explanation The FSM has got into an invalid state
Recommended Action Restart the SFRAR/SAAR processes (contain 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-WAN_INARP-3-UNKNOWN_IDB
received information about an unrecognized interface
Explanation A set of IDBs are kept with information on each 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-WAN_INARP-3-UNKNOWN_IDBTYPE
The type ([dec]) of this IDB is invalid
Explanation Information about InARP interfaces has become corrupted.
Recommended Action Restart the main processes (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-WAN_INARP-3-UNKNOWN_IFSTATE
The if state ([dec]) is not handled
Explanation There is no action assigned to the if state change, and so nothing has been done when it
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-WAN_INARP-3-VCCLASS_IDB
The IDB is not in sync with the vc-class information
Explanation A set of IDBs are kept with information on each FR interface. A set of VC-CLASSes
are also kept and associated with the IDBs. Somehow this information has become inconsistent.
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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-1000
OL-23348-01
Layer 2 Messages
WAN_LIB_IFDB Messages
Error Message
%L2-WAN_INARP-4-UNKNOWN_INTF
failed lookup of interface: [chars]
Explanation The system must be sending messages we didn’t register for. They 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.
WAN_LIB_IFDB Messages
Error Message
%L2-WAN_LIB_IFDB-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-WAN_LIB_IFDB-3-UNKNOWN_IDBTYPE
unknown idb type: [dec]
Explanation The IDB type of this IDB is not recognized.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
WAN_LIB_VCC Messages
Error Message
%L2-WAN_LIB_VCC-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.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-1001
Layer 2 Messages
WANPHY Messages
Error Message
%L2-WAN_LIB_VCC-3-UNKNOWN_IDBTYPE
unknown idb type: [dec]
Explanation The IDB type of this IDB is not recognized.
Recommended Action If the message recurs, copy the error message exactly as it appears on the
console or in the system log, call your Cisco technical support representative and provide the
representative with the gathered information.
WANPHY Messages
Error Message
%L2-WANPHY-4-ALARM
interface: [chars], alarm: [chars], status: [chars]
Explanation The specified WANPHY 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 end is injecting error packets else check if the cable is faulty. Collect sh
controller wanphy all and verify if B2 errors are incrementing. If B2 count is incrementing the alarm
is seen because of peer end is injecting error packets or faulty link
XCONNECT Messages
Error Message
%L2-XCONNECT-3-ERROR
[chars] failed: [chars]
Explanation Some requested operation failed. The text of the message displays the failed operation
with error code.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Error Message
%L2-XCONNECT-3-init
[chars]
Explanation Some initialization function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-1002
OL-23348-01
Layer 2 Messages
XCONNECT Messages
Error Message
%L2-XCONNECT-6-GENERIC
[chars]
Explanation Some generic errors.
Recommended Action Copy the error message exactly as it appears on the console or in the system
log, call your Cisco technical support representative and provide the representative with the gathered
information.
Cisco IOS XR System Error Message Reference Guide, Release 4.0
OL-23348-01
EM-1003
Layer 2 Messages
XCONNECT Messages
Cisco IOS XR System Error Message Reference Guide, Release 4.0
EM-1004
OL-23348-01