-
Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.3
-
Overview
-
Preface
-
Diagnostic Messages
-
Driver Messages
-
Fabric Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 2 (L2) Messages
-
Media Messages
-
Manageability (MGBL) Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service (QOS) Messages
-
Routing Messages
-
Feedback
Table Of Contents
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. The following facility codes are represented in this module:
10GE_PLIM Messages
Error Message%L2-10GE_PLIM-3-OIM_ERR An Optic Interface Module error occurred at port [dec], reason : [chars]
Explanation A fatal error occurred in 10GE PLIM driver OIM rule validation.
Recommended Action 1. Remove the Xenpak and check if it is Cisco qualified Xenpak. 2. If it is Cisco qualified Xenpak, check DWDM Xenpak placement rule.
Error Message%L2-10GE_PLIM-4-INVALID_MAC Failed to get MAC address for [chars], 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-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.
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_REG ASIC Error library has failed to register a connection notification handler with the Event Connection Manager. Reason: [chars].
Explanation ASIC Error library encountered an error while setting up a SYSDB notofication handler with the event connection manager.
Recommended Action An error would be reported to the client application which should handle this condition appropriately. *None*
Error Message%L2-ASIC_ERRORS-7-ERR_SYSDB ASIC Error library failed to [chars]. Reason: [chars].
Explanation ASIC Error library encountered an error during the specified SYSDB operation.
Recommended Action An error would be reported to the client application which should handle this condition appropriately. *None*
Error Message%L2-ASIC_ERRORS-7-ERR_SYSDB_BAG_ENCODE ASIC Error library: Encountered SYSDB Bag encode error during [chars] operation.
Explanation ASIC error library encountered a SYSDB encode error while performing the indicated operation.
Recommended Action An error would be reported to the client application which should handle this condition appropriately. *None*
Error Message%L2-ASIC_ERRORS-7-ERR_SYSDB_EDM_REG ASIC Error library has failed to register an EDM. Reason: [chars].
Explanation The ASIC Error library was unable to become an external data manager despite having a connection to the SYSDB.
Recommended Action An error would be reported to the client application which should handle this condition appropriately. *None*
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 triggerred a critical alarm and will result in node bringdown. The reason for the failure and the status of the scan operation is reported.
Recommended Action Run the board diagnostics.
Error Message%L2-ASIC_SCAN_SERVER-7-ERR_EVM_CREATE ASIC Scan Server failed to create the event manager: Reason = [chars].
Explanation ASIC scan server has failed to create the event manager. This would result in the automatic restart of the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ASIC_SCAN_SERVER-7-ERR_INIT ASIC Scan Server encountered error [[chars]]: Reason = [chars].
Explanation ASIC scan server has failed the initialization sequence due to the specified reason. This would result in the automatic restart of the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-ASIC_SCAN_SERVER-7-ERR_IO ASIC Scan Server failed to [chars]: Reason = [chars].
Explanation ASIC scan server has failed the specified io operation.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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_INIT Failure during intialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the platform dependent adjacency programming DLL. This will result in the hosting process being restarted.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-BM_PD-3-DLL_INIT Failure during intialization of [chars]. Error: [chars]
Explanation A failure occurred during the initialization of the platform dependent adjacency programming DLL. This will result in the hosting process being restarted.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-BM_PD-3-DLL_TRACE Failure initializing tracing ([chars] buffer). Error: [chars]
Explanation A failure occurred during the initialization of tracing for the adjacency management DLL. This will cause the DLL to be unloaded, and adjacency programming will not happen.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-BM_PD-3-DLL_TRACE Failure initializing tracing ([chars] buffer). Error: [chars]
Explanation A failure occurred during the initialization of tracing for the adjacency management DLL. This will cause the DLL to be unloaded, and adjacency programming will not happen.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
EGRESSQ Messages
Error Message%L2-EGRESSQ-3-ERR_MEM_ALLOC Failed to allocate memory for [chars]
Explanation System failed to allocate memory. It's likely that the system is running low on memory. Following are some reasons: 1) Failed to allocate memory for Egressq client add. 2) Failed to allocate memory for Egressq mapping table. 3) Failed to allocate memory for Queue leaky bucket limit table Memory. 4) Failed to allocate memory for Queue leaky bucket limit table memory. 5) Failed to allocate memory for Group leaky bucket limit table memory. 6) Failed to allocate memory for Group leaky bucket limit table memory. 7) Failed to allocate memory for Port leaky bucket limit table memory. 8) Failed to allocate memory for PLIM Asic back pressure table memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%L2-EGRESSQ-3-FCRAM_BIST_FAILURE FCRAM BIST failed, channel: [dec], count: [dec], error_addr: [hex]
Explanation Egress Queue Manager encountered a FCRAM BIST failure error. Possible cause for this error condition is a faulty hardware.
Recommended Action No action is required. Process will be automatically restarted. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-EGRESSQ-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-3-SBE_THRESHOLD_EXCEED Single Bit Error rate exceeded configured high threshold value:
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-3-UNALLOCATED_QUEUE_NOT_EMPTY Egressq unallocated queue [dec] is not empty
Explanation Egress Queue Manager encountered an error condition. This error condition can be caused due to inconsistencies in internal data structures. 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-EGRESSQ-7-ERR_CLIENT_REG Client registration failed: [chars] reason: [chars]
Explanation An internal error was detected while clients are registering to Egressq process.
Recommended Action No action is required. Clients will automatically retry to connect to Egressq. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-EGRESSQ-7-ERR_EVM_FAIL EVM error : [chars] reason : [chars]
Explanation An internal error was detected when trying to create EVM connection. It can fail during following scenarios: 1) EDM registration/connect/notify. 2) BAG's rule registration failed.
Recommended Action No action is required. The process retries automatically. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-EGRESSQ-7-ERR_INTERNAL Internal error : [chars] reason : [chars]
Explanation An internal error was detected. There are several scenarios which can cause this error condition. Error message describes the cause. Some of these error conditions are serious and result in driver process restart, e.g. ASIC Init/remap, enable/disable failure. Following are some of the reasons for this internal error: 1) Obsolete API usage, it can be caused due to uncompatible component installed in the system. 2) Interface creation failed due to egressq port creation failure. 3) Can't map Interface handle to egressq port, it could be because of: a) Invalid interface handle passed. b) Internal interface to port mapping table is corrupted. 4) Egressq ASIC reinitialization failed, this is an irrecoverable situation, and Egressq driver will be restarted. 5) Egressq Group/Queue creation/ deletion failed. 6) ASIC enable /disable failed.
Recommended Action No action is required. The process will automatically retry. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-EGRESSQ-7-ERR_LWM_FAIL LWM message send failed: [chars] reason: [chars]
Explanation An internal error was detected when trying to send a LWM message. There are several scenarios which can cause this error condition. Error message describes the exact cause.
Recommended Action No action is required. The process retries automatically. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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-PIO_CRITICAL_ERROR Asic PIO failure : [chars], instance [dec]: rc [dec] cerr [chars] errno [dec] data1 [hex] data2 [hex]
Explanation A critical error occurred while accessing the hardware in jacket driver which involves exiting the process. The driver will restart and attempt normal functionality. If the error is transient, the jacket driver and the SPAs will continue normal operation. If the error is persistent, the jacket card hardware needs to be checked out for access failures.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-JACKET-3-RULES_CRITICAL_ERROR SPA subslot [dec]: FAILED: [chars] for [chars]
Explanation A critical error occurred in jacket driver rules validation for a SPA which results in the SPA not being enabled. This does not affect the other slots on the jacket card. Please check the SW support for the SPA slot for which this message is seen.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-JACKET-3-SPA_PIO_ERROR SPA subslot [dec]: had [chars] error when accessing address [hex]
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-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-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the jacket driver to indicate anomolies which are not critical. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
METRO_STATS_API Messages
Error Message%L2-METRO_STATS_API-7-DEBUG_MSG Debug Msg : [chars]: [chars]
Explanation This is a debug message in the Hardware Stats Manager Library to indicate anomalies. In most cases these messages will stop once the temporary condition is resolved. Examples of when this error occurs are: 1. The client connection handle received is NULL 2. The arguments to the bind message are incorrect 3. Unable to bind to the hardware IPC driver 4. Error while trying to initialize debug event. 5. Not enough memory to bind to the client
Recommended Action No action is required. These are Debug messages. An error was returned by Stats Manager APIs to applications. Applications receiving this error will report the error.
Error Message%L2-METRO_STATS_API-7-ERR_DLL_INIT DLL INIT : [chars]: [chars]
Explanation This error indicates that there was an error while initializing the stats dll.
Recommended Action No action is required. The process is restarted automatically.
Error Message%L2-METRO_STATS_API-7-ERR_THREAD Locking issues: [chars]: [chars]
Explanation This error indicates that the Hardware Stats Manager Library is unable to initialize/destroy locking for client's attributes and tables.
Recommended Action An error was returned by Stats Manager APIs to applications. Applications receiving this error will report it. Take recommended actions specified in the application's error message. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
METRO_STATS Messages
Error Message%L2-METRO_STATS-7-ERR_INIT [chars]: [chars]
Explanation These errors are encountered at mstats process initialization time. The types of errors are: 1 Unable to determine hardware version. 2 Unable to create event manager. This will prevent stats process from receiving events. 3 Unable to create timer. 4 Unable to initialize client database. This will result in clients not being able to register with stats server to collect stats. 5 Unable to allocate Ingress/Egress stats. This will result in Stats manager not being able to maintain/update any hardware stats. 6 Unable to register with debug. This will prevent stats process from logging debug messages. 7 Unable to initialize or register with checkpoint service. This will prevent stats manager from restoring the information required at restart. 8 Unable to connect with SYSDB. This includes failure to connect, bind, register with SYSDB. 9 Unable to Initialize hardware packet service.
Recommended Action No action is required. Process will be restarted. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-METRO_STATS-7-ERR_MEM Memory error: [chars]: [chars]
Explanation An error occurred in Hardware Stats Manager during shared memory operations. This may be because the system is running low on memory. The types of errors are: 1 Cannot open/reset/close shared memory window 2 Cannot allocate/free shared memory. This will cause Stats Server to not be able to have a shadow copy of stats for all clients.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
METRO_UIDB Messages
Error Message%L2-METRO_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 schedular 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.
MOTHRA Messages
Error Message%L2-MOTHRA-3-FATAL_ERROR Fatal error: [chars]: [chars]: [hex]
Explanation A fatal error occurred in mothra Driver which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MOTHRA-3-PIO_FATAL_ERROR Asic PIO failure : [chars], instance [dec]: rc [dec] cerr [chars] errno [dec] data1 [hex] data2 [hex]
Explanation A fatal error occurred in Santa Driver which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-MOTHRA-6-INFO_MSG Info: [chars]: [chars]
Explanation This is a Informational message in the mothra driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-MOTHRA-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the mothra driver to indicate anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
OC768_FRAMER_ASIC Messages
Error Message%L2-OC768_FRAMER_ASIC-3-CRITICAL_ERROR [chars]: [chars]: [hex]
Explanation OC768 Framer ASIC Driver encountered a critical error which causes the process to exit.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-OC768_FRAMER_ASIC-6-INFO [chars]: [chars]
Explanation This is a informational message from OC768 Framer ASIC driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-OC768_FRAMER_ASIC-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in OC768 Framer ASIC driver to indicate anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
OPTICS Messages
Error Message%L2-OPTICS-3-CRITICAL_ERROR Optical init failure: [chars]: [chars]: [hex]
Explanation A critical error occurred in OPTICS Driver which involves exiting the process.
Recommended Action Power cycle the plim.
Error Message%L2-OPTICS-6-INFO Info: [chars]: [chars]
Explanation This is an informational message in the OPTICS driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-OPTICS-7-DEBUG_MSG Debug: [chars]: [chars] value [dec]
Explanation This is a debug message in the optics driver to indicate anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PFILTER_EA Messages
Error Message%L2-PFILTER_EA-3-ERR_IM_CAPS [chars] acl failed on interface . [chars]
Explanation 1) An ACL could not be applied to hardware because of one of the following reasons: a) TCAM max limit has been reached. b) RLB resources are not available. c) IPv6 address compression table is full. This error can happen when a new bundle member is added and the ACL can not be programmed successfully. 2) An ACL could not be removed from hardware.
Recommended Action 1) When this error occurs the running-config will not be in sync with line card configuration. It is recommended that the bundle member on which the error occured be removed from the bundle. The ACL configuration may also be reduced until it can be successfully programmed on the new bundle member. 2) If the ACL could not be removed from hardware a line card reload is recommended.
Error Message%L2-PFILTER_EA-7-INIT [chars] failed due to [chars]
Explanation Initialization of packet filter process has failed due to one of the following reasons: 1) Failed to initialize event manager. This would prevent process from receiving events. 2) Failed to register with debug. This would prevent process from logging debug messages. 3) Failure to connect with SYSDB. 4) Failed initialize internal permit/deny entries for IPv4/IPv6. These entries are needed for programming/removal of hardware entries for IPv4/IPv6 security ACLs. 5) Failed to initialize connection with interface manager proxy service. 6) Failed to initialize RLB (range logic block) checkpoint. This is needed for checkpointing range logic block information for restore on process restart. 7) Failed to initialize Feature EA DLL API needed for programming of hardware resources. 8) Failed to initialize callback function from Feature EA DLL for compiling IPv4/IPv6 TCAM entries needed for security ACL programming in hardeare. 9) Failed to initialize callback function from Feature EA DLL to handle reprogramming of RLB and IPv6 source prefix compression table request from TCAM manager. 10) Failed to initialize feature checkpoint info. This is needed for checkpointing IPv4 and IPv6 security ACLs programmed in hardware. 11) Failed to initialize callback functions from ACL configuration manager to perform hardware resource checks and ACE resequencing. 12) event_block failed. This indicates process has encountered unexpected error while waiting for events. 13) Failed to initialize callback functions for receiving incremental updates for IPv4/IPv6 security ACL configuration.
Recommended Action No action is required. Process will be restarted. If not recovered, it's a fatal condition. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. *REDUCE*
PLAOC768_API Messages
Error Message%L2-PLAOC768_API-3-CRITICAL_ERROR [chars]: [chars]: [hex]
Explanation PLAOC768 system checkout Library encountered a critical error which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PLAOC768_API-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message from the PLAOC768 system checkout Library to indicate either anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temporary situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLAOC768 Messages
Error Message%L2-PLAOC768-3-ASIC_ERROR [chars] : block [dec] error [dec], [chars]
Explanation An ASIC error occurred in PLAOC768 ASIC which is reported here.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PLAOC768-3-CRITICAL_ERROR [chars]: [chars]: [dec]
Explanation PLAOC768 Driver encountered an critical error condition which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PLAOC768-3-PIO_CRITICAL_ERROR Asic PIO failure : [chars], instance [dec]: rc [dec] cerr [chars] errno [dec] data1 [hex] data2 [hex]
Explanation A critical error occurred in PLAOC768 Driver which involves exiting the process.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-PLAOC768-6-INFO [chars]: [chars]
Explanation This is a informational message in the PLAOC768 driver to indicate an operation.
Recommended Action No action is required.
Error Message%L2-PLAOC768-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message from the PLAOC768 driver to indicate anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLIM_4P_OC192 Messages
Error Message%L2-PLIM_4P_OC192-3-DEVICE_INTR_CLEAR No Framer/RAC devices are generating excessive interrupts
Explanation The previously reported excessive interrupts condition has been cleared. Interrupt rate limiting has been disabled.
Recommended Action none
Error Message%L2-PLIM_4P_OC192-3-DEVICE_INTR_DISABLE Excessive interrupts from the [chars] device of port [hex]
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-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-MEM_ERR [chars]
Explanation fail to allocate memory.
Recommended Action sysmgr would restart the process. show process memory to find out whehter 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]
Explanation BAMBI API generated errors.
Recommended Action No action is required.
PLIM_ASIC Messages
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 'bambi_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 Typcially these indicate that ltrace is out of service. check at other processes using ltrace and see whether the problem happens to them.
Error Message%L2-PLIM_ASIC-7-ERR [chars]
Explanation Plim asic driver errors. Typically these errors indicate failure in system services or bad programming of the hardware.
Recommended Action No action is required.
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 anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLIM_LIB Messages
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-7-DEBUG [chars]: [chars] errno [dec]
Explanation This is a debug message in the PLIM library driver to indicate anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
Recommended Action 'show logging' to confirm sysdb errors
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.
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 anomolies which are not FATAL. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLIM Messages
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.
Error Message%L2-PLIM-3-MEM_ERR [chars]
Explanation fail to allocate memory.
Recommended Action show process memory to find out whehter there is potential memory leak show memory to confirm system memory goes low
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-7-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 msgs from sysdb or event msg. 'show logging' could confirm this
PPP_EA Messages
Error Message%L2-PPP_EA-3-ERR_CAPS_ADD Failed to add ppp encapsulation in uidb: [chars]
Explanation PPP encapsulation could not be set on the interface. As a result the PPP link may not come up.
Recommended Action Attempt to apply the ppp encapsulation to the interface again. If the message recurs, copy the error message exactly as it appears on 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-3-ERR_CAPS_REMOVE Failed to remove ppp encapsulation: [chars]
Explanation PPP encapsulation could not be removed from the interface.
Recommended Action Try to remove the ppp encapsulation from the interface again. If the message recurs, copy the error message exactly as it appears on 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-3-ERR_DATAPATH_CONTROL Handling of a datapath control operation returned an error: [chars]
Explanation There are two types of datapath control operations: 1. Enable PPP encapsulation on the interface. 2. Disable PPP encapsulation on the interface. One of these operations have 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-PPP_EA-3-ERR_EVM_CREATE Failed to initialize event manager: [chars]
Explanation The process could not initialize event manager. This would prevent the process from receiving events.
Recommended Action No action is required. The process will restart automatically and will attempt to initialize event manger again. If the message recurs, copy the error message exactly as it appears on 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-3-ERR_IMP_INIT Failed to initialize a connection with IMP server: [chars]
Explanation The process cound not initialize a connection with the IMP server.
Recommended Action No action is required. The process will be restarted automatically and it will attempt to initialize the connection again. If the message recurs, copy the error message exactly as it appears on 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-3-ERR_IMP_REGISTER_CONTROL_HANDLER Failed to register control handler with IMP server: [chars]
Explanation --
Recommended Action No action is required. The connection will be re-attempted. If the message recurs, copy the error message exactly as it appears on 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-3-ERR_IMP_SERVER_BIND Failed to connect with IMP server: [chars]
Explanation The process could not connect with the interface manager proxy service. This service delivers information about PPP encapsulation on an interface. The process will not be able to receive events such as PPP encapsulation add/remove.
Recommended Action No action is required. The connection will be re-attempted. If the message recurs, copy the error message exactly as it appears on 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-3-ERR_LTRACE_INIT Failed to initialize the ltrace buffer: [chars]
Explanation The buffer used for tracing debug events could not be allocated.
Recommended Action No action is required. The process will automatically be restarted and will attempt to initialize the ltrace buffer again. If the message recurs, copy the error message exactly as it appears on 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-3-ERR_UIDB_CLIENT_CONN Failed to connect to UIDB server: [chars]
Explanation UIDB stores information about the encapsulation of the interfaces. The process could not establish a connection to the UIDB server.
Recommended Action No action is required. The process will restart automatically and attempt to establish a connection again. If the message recurs, copy the error message exactly as it appears on 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_EVM_EVENT_BLOCK event_block returned error: [chars]
Explanation The process encountered an unexpected error while waiting for an event.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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-7-ERR_DEBUG_ASSOC Conditional debug association failed: [chars]
Explanation PPP EA registers with the debug library for 'interface' conditions. This allows PPP EA debug messages to be filtered by interface. The process failed to enable conditional debug filtering.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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-7-ERR_DEBUG_COND_REGISTER Conditional debug registration failed: [chars]
Explanation PPP EA registers with the debug library for 'interface' conditions. This allows PPP EA debug messages to be filtered by interface. The process failed to enable conditional debug filtering.
Recommended Action If the message recurs, copy the error message exactly as it appears on 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-7-ERR_DEBUG_REGISTER Debug registration failed: [chars]
Explanation The process could not register for debug notifications. Debugging of PPP EA may not be possible.
Recommended Action If the message recurs, copy the error message exactly as 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 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-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-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] device: High rate of ASIC errors of type: [chars]
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 [chars] device: High rate of ASIC errors of type: [chars]
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]) 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.
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-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-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-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*
SPA_OC3_OC12 Messages
Error Message%L2-SPA_OC3_OC12-3-DRIVER_ERR [chars] [chars]
Explanation SPA OC3/OC12 driver error messages
Recommended Action *NONE*
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-7-DEBUG [chars] [chars]
Explanation SPA OC3/OC12 debug message
Recommended Action *NONE*
SPA48 Messages
Error Message%L2-SPA48-3-CRITICAL SPA48: Critical error: [chars]
Explanation SPA48, Critical alarm
Recommended Action *SUPPORT*
Error Message%L2-SPA48-3-MAJOR SPA48: Major error: [chars] [dec]
Explanation SPA48, Major alarm
Recommended Action *SUPPORT*
Error Message%L2-SPA48-3-MINOR SPA48: Minor error: [chars], [dec]
Explanation SPA48, Minor alarm
Recommended Action *SUPPORT*
Error Message%L2-SPA48-6-INFO [chars]: [chars]
Explanation SPA48, General INFO
Recommended Action *NONE*
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.
VPA_1P_OC192 Messages
Error Message%L2-VPA_1P_OC192-3-MEM_ERR [chars]
Explanation fail to allocate memory
Recommended Action show process memory to find out whehter 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-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]: [chars]
Explanation OC192VPA driver general info.
Recommended Action show asic-error plim asic .. loc
VPA_8P_GE Messages
Error Message%L2-VPA_8P_GE-3-FWD_DRV_ERR [chars]
Explanation The SPA driver could not communicate with the forwarder driver for notifying the state of the port.
Recommended Action Check if the interface is created and can come up on the SPA port. If the inteface cannot come up or ping, copy the message exactly as it appears in the system log and contact Cisco support representative with the information.
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.
VPA_RULES Messages
Error Message%L2-VPA_RULES-4-DEBUG_INIT_ERR [chars] [dec] [chars]
Explanation Internal error. SPA rules library debug library initilization 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.
