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

Table of Contents

Layer 1 Messages

EAGLE Messages

PLIM_OC3 Messages

PMENGINE Messages

TREX_LIB Messages

TREX Messages

UT2 Messages

XENA Messages

Layer 1 Messages

This section contains all Layer 1 related System Error Messages.

EAGLE Messages

Error Message %L1-EAGLE-7-ERR_MSG

ERR: [chars]: cerrno [dec]

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

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.

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

Recommended Action *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-3-ERR_SPA_UNSUPPORTED

Inserted node [chars] is not supported by Cisco 12000 Series - Multi-Service Blade Controller. Results are unpredictable. Please remove the unsupported hardware.

Explanation Daughter board identified by above nodeid is not supported by Cisco 12000 Series - Multi-Service Blade Controller. The Daughter board should be removed immediately because results are unpredictable.

Recommended Action Physically remove the Daughter board from the service card.

Error Message %L1-XENA-5-NOTICE

[chars]

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

Recommended Action *NONE*