Cisco IOS XR System Error Message Reference Guide, Release 3.5
Layer 1 Messages
Downloads: This chapterpdf (PDF - 371.0KB) The complete bookPDF (PDF - 18.83MB) | Feedback

Layer 1 Messages

Table Of Contents

Layer 1 Messages

PLIM_CLKSEL Messages

PLIM_LIB Messages

PLIM_OC3 Messages

PMENGINE Messages

SPA_OC3_OC12 Messages

SPA_OC48 Messages

TREX_LIB Messages

TREX Messages

UT2 Messages

XENA Messages


Layer 1 Messages


This section contains all Layer 1 related System Error Messages. The following facility codes are represented in this module:

PLIM_CLKSEL Messages

PLIM_LIB Messages

PLIM_OC3 Messages

PMENGINE Messages

SPA_OC3_OC12 Messages

SPA_OC48 Messages

TREX_LIB Messages

TREX Messages

UT2 Messages

XENA 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 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 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 process name 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 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 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 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.

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.

SPA_OC3_OC12 Messages

Error Message     
 
    
    
   

%L1-SPA_OC3_OC12-3-ERR_IF [chars]

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

Recommended Action    - Try to do the SFP OIR for a few more times; - If the issue persists, reload the SPA with the command: hw-module subslot 0/x/x reload then check if all the POS interface are created, if not, reload LC. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L1-SPA_OC3_OC12-3-ERR_PLUGIN [chars]

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

Recommended Action    The SPA infra will automatically restart the SPA driver up to a fixed number of times if the failure happens during SPA is booting. If the failure doesn't happen with SPA booting, manually SPA reload may be needed. Execute 'show platform' to verify the SPA is in READY state, if not, try to reload the SPA with command: hw-module subslot 0/x/x reload or if the system has no response to the command above, force to reload the SPA with follwoing sequence under config mode: hw-module subslot 0/x/x shutdown commit no hw-module subslot 0/x/x shutdown commit If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

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

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

%L1-SPA_OC3_OC12-6-INFO [chars]

Explanation    information message %s - message

Recommended Action    none

Error Message     
 
    
    
   

%L1-SPA_OC3_OC12-6-OPTICS_OIR [chars]

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

Recommended Action    none

SPA_OC48 Messages

Error Message     
 
    
    
   

%L1-SPA_OC48-3-ERR_INIT SPA driver initialization failed in bay [dec]: ([chars]/[chars]).

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 follwoing sequence under config mode: hw-module subslot 0/x/x shutdown commit no hw-module subslot 0/x/x shutdown commit If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

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

%L1-SPA_OC48-6-OPTICS_INSERTION Optics module inserted into SPA in bay [dec], port [dec]

Explanation    Optics module has inserted %d - bay number %d - port number

Recommended Action    none

Error Message     
 
    
    
   

%L1-SPA_OC48-6-OPTICS_REMOVAL Optics module removed from SPA in bay [dec], port [dec]

Explanation    Optics module has removed %d - bay number %d - port number

Recommended Action    none

TREX_LIB Messages

Error Message     
 
    
    
   

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

Explanation    This error message indicates a s/w problem. The details of the problem and traceback are appended to the error msg. Contact support with this information.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%L1-TREX_LIB-7-DEBUG [chars]

Explanation    A harmless s/w problem occurred. The details of the problem and traceback are appended to the 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.

TREX Messages

Error Message     
 
    
    
   

%L1-TREX-2-HW_FATAL_ERROR fatal error encountered by h/w - [chars], [chars]

Explanation    An unrecoverable fatal error was detected by the service linecard h/w, which resulted in linecard reload. The exact cause is appended to the error message. Contact support with this information.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%L1-TREX-2-SW_FATAL_ERROR fatal s/w error encountered - [chars], [chars]

Explanation    An unrecoverable fatal s/w error was encountered, which resulted in process restart. The exact cause is appended to the error msg. Contact support with this information.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%L1-TREX-3-BOARD_PLL_ERROR board PLL error : IOFPGA register PLL_STATUS - [hex][[hex]]

Explanation    There is unexpected h/w state

Recommended Action    If the problem persists reload the linecard. If that doesn't 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     
 
    
    
   

%L1-TREX-3-HW_NONFATAL_ERROR nonfatal error encountered by h/w - [chars], [chars]

Explanation    A nonfatal error was detected by the service linecard h/w. The exact cause is appended to the error message. Contact support with this text.

Recommended Action    If the error message appears rapidly, or if it persists, reload linecard. If that doesn't 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     
 
    
    
   

%L1-TREX-3-PLL_ERROR [chars] i/f PLL is unlock : register PLS - [hex]

Explanation    There is unexpected h/w state

Recommended Action    If the problem persists reload the linecard. If that doesn't 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     
 
    
    
   

%L1-TREX-5-NOTICE [chars]

Explanation    Unexpected event occurred in the service linecard with no effect on functionality

Recommended Action    *NONE*

Error Message     
 
    
    
   

%L1-TREX-6-INFO [chars]

Explanation    Service linecard's driver informational message

Explanation    *NONE*

UT2 Messages

Error Message     
 
    
    
   

%L1-UT2-7-ERR_MSG ERR: [chars]: cerrno [dec]

Explanation    ut2 driver might run into an error that is not a FATAL.

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

XENA Messages

Error Message     
 
    
    
   

%L1-XENA-2-HW_FATAL_ERROR fatal error encountered by h/w - [chars]

Explanation    An unrecoverable fatal error was detected by service card h/w, which resulted in linecard reload. The exact cause is appended to the error msg. Contact support with this information.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%L1-XENA-2-SW_FATAL_ERROR fatal s/w error encountered - [chars], [chars]

Explanation    An unrecoverable fatal s/w error was encountered, which resulted in process restart. The exact cause is appended to the error msg. Contact support with this information.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%L1-XENA-5-NOTICE [chars]

Explanation    Unexpected event occurred in service linecard with no effect on functionality

Recommended Action    *NONE*