Cisco IOS XR System Error Reference Guide for XR12000 Series Platform Specific Messages, Release 3.4
Layer 1 Messages
Downloads: This chapterpdf (PDF - 335.0KB) The complete bookPDF (PDF - 2.64MB) | Feedback

Layer 1 Messages

Table Of Contents

Layer 1 Messages

PLIM_CLKSEL Messages

PLIM_LIB Messages

PLIM_OC3 Messages

PMENGINE Messages


Layer 1 Messages


This section contains all Layer 1 related System Error Messages.

PLIM_CLKSEL Messages

PLIM_LIB Messages

PLIM_OC3 Messages

PMENGINE Messages

PLIM_CLKSEL Messages

Error Message     
 
    
    
   

%L1-PLIM_CLKSEL-3-ERR_INIT PLIM process is restarted because of a failure in Clock Selection Library initialization: ([chars]/[chars]).

Explanation    The initilaization 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 location 0/x/cpu0' to verify that the process is up and running, where process name = '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 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     
 
    
    
   

%L1-PLIM_CLKSEL-4-ERR_DEBUG Debug initialization failed with [chars].

Explanation    Debug message initialzation 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 location 0/x/CPU0' may resolve the problem.

PLIM_LIB Messages

Error Message     
 
    
    
   

%L1-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     
 
    
    
   

%L1-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     
 
    
    
   

%L1-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 location 0/x/cpu0' where process name = '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 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     
 
    
    
   

%L1-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 location 0/x/cpu0' where process name = '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.

PLIM_OC3 Messages

Error Message     
 
    
    
   

%L1-PLIM_OC3-2-ERR_HW_RESTART Physical layer interface module hardware restart for error recovery failed: [chars]: [chars]

Explanation    The PLIM driver failed in soft error recovery. When a soft error is detected with any ASIC on the datapath, the Fault Manager will start the soft error recovery on the whole datapath. 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 - indicates the reason for the failure %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 resets 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     
 
    
    
   

%L1-PLIM_OC3-3-ERR_INIT Physical layer interface module driver initialization failed: ([chars]/[chars]).

Explanation    The physical layer interface module (PLIM) driver on the linecard failed to initialize. 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 this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process e48_plim_oc3 location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart e48_plim_oc3 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     
 
    
    
   

%L1-PLIM_OC3-3-ERR_TIMER Unknown timer type detected, the timer is stopped.

Explanation    The wrong timer type is detected while handling the timer event, the timer will be stopped. The POS interface counter will not work if the timer is stopped, but the traffic will not be affected.

Recommended Action    Execute 'show int pos 0/x/0/x' while the traffic is running on the interface to confirm if the counter is still working, if not, restart PLIM driver with CLI: 'process restart e48_plim_oc3 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     
 
    
    
   

%L1-PLIM_OC3-4-ERR_DEBUG Debug initialization failed with [chars].

Explanation    Debug message initialzation failed.

Recommended Action    This error has no effect on any feature except that debug information cannot be turned on by CLI 'debug plim location 0/x/CPU0'. Restarting the process with CLI: 'process restart e48_plim_oc3 location 0/x/CPU0' may resolve the problem.

PMENGINE Messages

Error Message     
 
    
    
   

%L1-PMENGINE-4-TCA Port [chars] reports [chars] [chars]([chars]) PM TCA with current value [unsigned long long int], threshold [unsigned long long int] in current [chars] interval window

Explanation    The specified PM TCA has been declared.

Recommended Action    Recommended action is to repair the source of the alarm.