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

Layer 2 Messages

Table Of Contents

Layer 2 Messages

ATM_SOP Messages

GT64115 Messages

if_discovery Messages

IOB Messages

OC768_FRAMER_ASIC Messages

OPTICS Messages

OSICP Messages

PFILTER_EA Messages

PLAOC768_API Messages

PLAOC768 Messages

PLIM_4P_OC192 Messages

PLIM_ASIC_API Messages

PLIM_ASIC Messages

PLIM_FPGA Messages

PLIM_IOX_4P_GE Messages

PLIM_LIB Messages

PLIM_OC768 Messages

PLIM Messages

POS Messages

PPP_EA Messages

PPP_FSM Messages

PPP_LCP Messages

PPP_lite Messages

PPP_MA Messages

PSE Messages

PSELIB Messages

QM_E5 Messages

QM Messages

QUEUEING Messages


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:

ATM_SOP Messages

GT64115 Messages

if_discovery Messages

IOB Messages

OC768_FRAMER_ASIC Messages

OPTICS Messages

OSICP Messages

PFILTER_EA Messages

PLAOC768_API Messages

PLAOC768 Messages

PLIM_4P_OC192 Messages

PLIM_ASIC_API Messages

PLIM_ASIC Messages

PLIM_FPGA Messages

PLIM_IOX_4P_GE Messages

PLIM_LIB Messages

PLIM_OC768 Messages

PLIM Messages

POS Messages

PPP_EA Messages

PPP_FSM Messages

PPP_LCP Messages

PPP_lite Messages

PPP_MA Messages

PSE Messages

PSELIB Messages

QM_E5 Messages

QM Messages

QUEUEING Messages

ATM_SOP Messages

Error Message     
 
    
    
   

%L2-ATM_SOP-3-INTR ATM SOP Intr: [chars]: [dec]: [chars]: [dec] [chars]

Explanation    The SOP FPGA has been interrupted due a hardware error

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

Error Message     
 
    
    
   

%L2-ATM_SOP-7-DEBUG ATM SOP DEBUG: [chars]: [hex]: [hex]: [hex]

Explanation    ATM SOP debug message

Recommended Action    No action is required.

GT64115 Messages

Error Message     
 
    
    
   

%L2-GT64115-2-PCI_CONFIG Fatal error: [chars]: [dec]

Explanation    A fatal error occurred during GT64115 PCI Driver cofiguration

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

Error Message     
 
    
    
   

%L2-GT64115-2-PCI_INIT Fatal error: [chars]

Explanation    A fatal error occurred during GT64115 PCI Driver initialization

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

Error Message     
 
    
    
   

%L2-GT64115-3-PCI_BRIDGE_INTR PCI Bridge Intr: [chars] [dec] [dec]

Explanation    This is an error message resulted from an interrupt from the PCI device.

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

if_discovery Messages

Error Message     
 
    
    
   

%L2-if_discovery-3-FATAL_ERROR Fatal error: [chars]: [chars]: [dec]

Explanation    A fatal error occurred in plim pos 4p oc12 Driver which involves exiting the process.

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

Error Message     
 
    
    
   

%L2-if_discovery-6-INFO_MSG Info: [chars]: [chars]

Explanation    This is a Informational message in the plim pos 4p oc12 driver to indicate an operation.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-if_discovery-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]

Explanation    This is a debug message in the plim pos 4p oc12 driver to indicate 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.

IOB Messages

Error Message     
 
    
    
   

%L2-IOB-3-INTR IOB Intr: [chars]

Explanation    The IOB FPGA has been interrupted due to an access fault

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

Error Message     
 
    
    
   

%L2-IOB-5-UNKNOWN_INTR IOB Intr: [chars]: [dec]: [dec]

Explanation    This is a message in the IOB FPGA driver to indicate that it has detected an unknown interrupt.

Recommended Action    If the message recurs, copy the error message exactly as 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.

OSICP Messages

Error Message     
 
    
    
   

%L2-OSICP-3-DEBUG_ASSOC Conditional debug association failed; [chars]

Explanation    An error has occurred upon attempting to associate conditional debugging with PPP debug commands. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.

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

Error Message     
 
    
    
   

%L2-OSICP-3-DEBUG_COND_REGISTER Conditional debug registration failed; [chars]

Explanation    An error has occurred upon attempting to register for conditional debugs. PPP debug messages will not be filtered by debug conditions such as 'debug condition interface'.

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

Error Message     
 
    
    
   

%L2-OSICP-3-DEBUG_REGISTER Debug registration failed; [chars]

Explanation    An error has occurred upon attempting to connect to the debug server. This may cause debug messages to not appear.

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_CONN Connection [chars] failed for [chars]; [chars]

Explanation    An failure in the reconnection software in the function.

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_EVENT Failed to [chars] [chars] event; [chars]

Explanation    An event handler has returned an error condition

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_EVENT_MGR_CREATE OSICP Failed to initialize event manager; [chars]

Explanation    Initialization of the event manager failed.

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_IM_STATE Failed to get basecaps state for [chars]; [chars]

Explanation    OSICP was unable to determine the state of the basecaps and has assumed it to be down. OSICP will remain closed until the interface is brought down and up again.

Recommended Action    Shut the interface and then bring it up again.

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_MBOX_ADD [chars] [chars] failed to add [chars]; [chars]

Explanation    An attribute has failed to be added to the message which was being constructed which has caused the message to be discarded.

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_MBOX_CREATE [chars] failed to create [chars]; [chars]

Explanation    An attempt to allocate a message failed. This may be due to lack of resources.

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_MBOX_INIT Failed to init [chars] message for [chars]; [chars]

Explanation    The initialization of a message failed, this results in a failure to communicate with the Link Control Protocol.

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_MBOX_SEND [chars] failed to send [chars]; [chars]

Explanation    A message failed in a send attempt to a particular mailbox.

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_MQ_OPEN Failed to open message queue [chars]; [chars]

Explanation    OSICP has failed to open a mailbox channel.

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_NETIO_RXQ Failed to support [chars] [chars]; [chars]

Explanation    OSICP has attempted to update the data component with the current status of the control protocol. The attempt has failed which will has the effect of leaving the data component with the previous set of information. This may result in an inability to negotiate OSICP.

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_SYSDB SysDB [chars] failed; [chars]

Explanation    OSICP cannot perform some SysDB operation.

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_SYSDB_NOTIFICATION Failed to [chars]register for SysDB notification of [chars]; [chars]

Explanation    OSICP cannot (un)register for SysDB notification.

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

Error Message     
 
    
    
   

%L2-OSICP-3-ERR_TIMER [chars] [chars] timer [chars]

Explanation    The manipulation of a timer had an abnormal side effect.

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

Error Message     
 
    
    
   

%L2-OSICP-3-LTRACE_INIT OSICP Failed to initialize the ltrace buffer; [chars]

Explanation    The buffer used for tracing could not be allocated. The process will be restarted.

Recommended Action    The most likely cause of a problem is not enough memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%L2-OSICP-4-ERR_EVENT_WAIT Error waiting for event; [chars]

Explanation    The event loop has received a message of a type it does not recognize. All events should be received by handlers.

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

Error Message     
 
    
    
   

%L2-OSICP-4-ERR_INTERFACE_NULL [chars]: Interface NULL

Explanation    A function was called with a NULL interface pointer.

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

Error Message     
 
    
    
   

%L2-OSICP-4-ERR_MEMORY Insufficient memory for [chars]

Explanation    OSICP failed to allocate memory for a structure.

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

Error Message     
 
    
    
   

%L2-OSICP-4-ERR_MQ_RECEIVE Error receiving from message queue; [chars]

Explanation    OSICP has failed to receive a message from its mailbox.

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

Error Message     
 
    
    
   

%L2-OSICP-4-ERR_NO_INTERFACE Interface [chars] not found

Explanation    A SysDB name lookup failed.

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

Error Message     
 
    
    
   

%L2-OSICP-4-ERR_NO_INTERFACE_STRUCT Structure for interface [chars] not created; [chars]

Explanation    OSICP failed to create an interface structure.

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

Error Message     
 
    
    
   

%L2-OSICP-6-ERR_IM_CONNECT Failed to [chars]bind [chars] IM; [chars]

Explanation    OSICP has failed to either bind to or unbind from the interface manager server.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-OSICP-6-ERR_IM_ENCAPS Failed to [chars] [chars] encapsulation; [chars]

Explanation    OSICP has failed an encapsulation operation with the interface manager.

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

Error Message     
 
    
    
   

%L2-OSICP-6-ERR_IM_EVENT Failed to [chars] event; [chars]

Explanation    OSICP has failed to either initialize or specify an event with the interface manager server.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-OSICP-6-ERR_IM_PROTO Failed to [chars] [chars] protocol; [chars]

Explanation    OSICP has failed a protocol operation with the interface manager.

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

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-3-INIT_ERROR Process initialization failed: ([chars]%s)

Explanation    The pfilter_ea process failed to initialize. This pfilter_ea process programs the 'packet filter' security access control list in the hardware. If the pfilter_ea process fails to initialize, the access control list cannot be programmed into the hardware. %s - indicates the reason for the initialization failure. %s - is the decoded error reason.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process pfilter_ea location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart pfilter_ea location 0/x/cpu0'. Collect all debug information if the process is continually restarting 'debug pfilter-ea all' (during the process restart). If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-PFILTER_EA-7-EVENT_ERROR Event Failure: ([chars])

Explanation    The pfilter_ea process received a bad event. This pfilter_ea process programs the 'packet filter' security access control list in the hardware. %s - is the decoded error reason.

Recommended Action    Monitor the event messages. The pfilter_ea process will handle the failure gracefully but if they continually appear on the console, try doing 'process restart pfilter_ea location 0/x/cpu0'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-PFILTER_EA-7-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_IOX_4P_GE Messages

Error Message     
 
    
    
   

%L2-PLIM_IOX_4P_GE-3-INIT_ERR Initialization error: [chars]: [chars]

Explanation    The 4 port Gigabit Ethernet (GE) driver failed to initialize properly. This driver provides the system access to the hardware. A failure during initialization of this process may render the interfaces provided by the hardware unusable. %s - indicates the reason for the failure %s - is the decoded error reason

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process plim_iox_4p_ge location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart plim_iox_4p_ge location 0/x/cpu0' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-PLIM_IOX_4P_GE-6-INFO_MSG [chars] [dec]

Explanation    This is an Informational message in the plim_iox_4p_ge driver to indicate operation that may be of interest to the user.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-PLIM_IOX_4P_GE-6-RXLOS_INT SFP Rx LOS Interrupt: port: [dec], count=[dec]

Explanation    This is an informational message in the gigE driver driver to indicate a Loss of Signal (LOS) has occurred on the indicated port.

Recommended Action    1. Ensure the equipment at the far end of the link is functioning and configurations are correct. 2. Ensure the cable are installed correctly Rx plugged into far-end Tx & Tx plugged into far-end Rx 3. Check SFP and cable compatability. If the message recurs, copy the error message exactly as 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

Error Message     
 
    
    
   

%L2-PLIM-7-LTRACE_ERR [chars] : [chars]

Explanation    failed to inititialize ltrace events;

Recommended Action    check out whether there is any problems with ltrace subsytem

POS Messages

Error Message     
 
    
    
   

%L2-POS-3-MTU_IMPOSE_FAILED Failed to set MTU of [unsigned int] on [chars]

Explanation    The specified MTU could not be applied on this interface.

Recommended Action    No action is required.

PPP_EA Messages

Error Message     
 
    
    
   

%L2-PPP_EA-3-INIT_ERROR Process Initialization Failed: ([chars]%s)

Explanation    The PPP execution agent process failed to initialize. PPP execution agent programs the Physical Layer Interface Module (PLIM) for handling PPP encapsulation on a POS link and also add capsulation for slowpath packet processing. The reason of the failure could be that the interface manager could not set the interface and returned an error, or could be due to unavailability of memory resources. This can happen when the linecard is coming up, or when the encapsulation is changed to PPP. The effect is that the interface will not come up using PPP encapsulation. %s - indicates the reason for the failure. %s - is the error reason.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process ppp_ea location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart ppp_ea location 0/x/cpu0' Also try reapplying the configuration. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-PPP_EA-4-ERR_EVM_EVENT_BLOCK Error encountered in the event loop: [chars]. The PPP EA process will restart

Explanation    An error occured in the event loop. The process will restart which should recover the situation.

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%L2-PPP_EA-4-ERR_INIT Failure during initialization of the [chars]. Error [chars]. The PPP EA process will restart

Explanation    A failure occured during the initialization of the process. The process will restart which should recover the situation.

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%L2-PPP_EA-6-ERR_IMP_MULTIPLE_NTFCNS : Multiple [chars] notifications received in a single batch from improxy

Explanation    A batch from IMProxy contained multiple notifications for a single interface. This should not occur but the situation has been recovered successfully by the PPP EA. No problems should be seen as a result.

Recommended Action    *NONE*

PPP_FSM Messages

Error Message     
 
    
    
   

%L2-PPP_FSM-3-ERR_SOCKET [chars]: Socket [chars] failed; [chars]

Explanation    There is a communication problem with the PPP socket.

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

PPP_LCP Messages

Error Message     
 
    
    
   

%L2-PPP_LCP-3-MTU_UNUSABLE [chars] has an interface MTU of [unsigned int] which is smaller than the PPP packet header size ([unsigned int]) and so PPP cannot run on the interface

Explanation    PPP has been informed that the interface MTU has been set to a value smaller than the PPP header size, which makes it impossible for PPP to operate.

Recommended Action    Reconfigure the interface's MTU to a larger value. In order to ensure correct operation with peers, values which provide a layer 2 payload capacity (after allowing for 4 bytes of PPP header) of 1500 bytes or greater are required.

Error Message     
 
    
    
   

%L2-PPP_LCP-4-MISSING_AUTHENTICATION_LIST AAA authentication list [chars] is not defined for PPP

Explanation    One or more PPP interfaces have been configured to authenticate the peer using the authentication list identified in the error message, but this authentication list has not been configured in AAA itself. As a result PPP will be unable to authenticate the peer and the line protocol on the relevant interface or interfaces will not come up.

Recommended Action    Configure 'aaa authentication ppp ...'

Error Message     
 
    
    
   

%L2-PPP_LCP-4-MTU_WARNING [chars] has a PPP MTU of [unsigned int] which is smaller than the minimum value ([unsigned int]) required for correct operation

Explanation    RFC 1661 requires that the media that PPP is running over is always able to receive PPP packets of sizes up to 1500 bytes (where this value excludes the 4 bytes of PPP header). This is to ensure that the peer can always send control protocol packets up to this size if they ever need to renegotiate. IOS-XR routers set their MRU to the same value as the MTU, and this message has been issued because the configured MTU is too small to meet the above condition.

Recommended Action    Reconfigure the interface's MTU to a larger value. In order to ensure correct operation with peers, values which provide a layer 2 payload capacity (after allowing for 4 bytes of PPP header) of 1500 bytes or greater are required. Note that as most Control Protocol packets are much smaller than 1500 bytes, it is unlikely that MTU values which are smaller than 1500 bytes will actually cause problems, but this cannot be guaranteed.

Error Message     
 
    
    
   

%L2-PPP_LCP-4-UNRECOGNIZED_PROTO Unrecognized IfMgr protocol [chars] on [chars] (caps=[chars])

Explanation    Interface Manager notified LCP about a protocol that it doesn't recognize, either by sending a request to LCP to adopt this node or by informing LCP that it exists. This is a programming error as LCP needs to recognized all of the protocols which run above it in order to be able to run the relevant CP.

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

Error Message     
 
    
    
   

%L2-PPP_LCP-5-MTU_NEGOTIATED The PPP MTU for [chars] has been negotiated to be [unsigned int]. This is less than the configured PPP MTU of [unsigned int]

Explanation    The PPP MTU is reduced when the PPP MRU of the peer is less than the PPP MTU derived from the locally configured interface MTU. The reduced value will be used until LCP is renegotated (such as when the interface goes down and comes back up, or a new MTU is configured), or if the PPP encapsulation is removed from the interface. The MTU then returns to the configured value and another message will indicate if a value less than the configured value is negotiated again. The reduced MTU is a normal part of PPP operation and is not indicative of any problems.

Recommended Action    No action is required.

PPP_lite Messages

Error Message     
 
    
    
   

%L2 control-PPP_lite-3-ERR_PL_DLL_ASYNC_SEND_FAIL Send async pulse to ppp lite process fails; Error [chars]

Explanation    Attempt to send pulse to PPP lite process fails

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2 control-PPP_lite-3-ERR_PL_DLL_CHAN_CONNECT_FAIL Cannot connect to ppp lite process; Error [chars]

Explanation    Attempt to connect to PPP lite process channel fails

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2 control-PPP_lite-3-ERR_SHMEM_MMAP_FAIL Cannot mmap file [chars]; Error [chars]

Explanation    Attempt to mmap the shared memory fails

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2 control-PPP_lite-3-ERR_SHMEM_OPEN_FAIL Cannot open shmem file [chars]; Error [chars]

Explanation    Attempt to open the shared memory fails

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2 control-PPP_lite-3-ERR_SHMEM_TRNC_FAIL Cannot truncate file [chars] to [dec] bytes; Error [chars]

Explanation    Attempt to truncate the shared memory file fails

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2 control-PPP_lite-3-ERR_SHMEM_UNAVAILABLE PPP lite SHMEM can accommodate only [dec] records (request for [dec] records)

Explanation    PPP MA has requested transfer of more interface records than shared memory can accommodate.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

PPP_MA Messages

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_AAA Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the AAA service. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary problem communicating with the AAA server, but the error could also be caused by low memory resource or programming error.

Recommended Action    In many cases, PPP MA will recover by itself. If it does not then restarting the process may help. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_AIB Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error communicating with the AIB server. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary connection problem with the NetIO server, but the error could also be caused by low memory resource or programming error.

Recommended Action    In many cases, PPP MA will recover by itself. If it does not then restarting the process may help. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_BAG Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the Bag Client library. The error message describes what operation has failed and why it failed. The most likely reason for this a low memory condition but the error could also be caused by a programming error. The error will affect PPP MA's ability to provide operational management data, but won't otherwise affect PPP MA's operation.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_CHKPT Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the Checkpoint Service. The error message describes what operation has failed and why it failed. The most likely reason for this a low memory condition but the error could also be caused by a programming error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_CHKPT_CORRUPT Corrupt [chars] checkpoint record found: [chars]

Explanation    Whilst restoring one of its checkpoint tables PPP MA found a corrupt checkpoint entry. The entry will be ignored and so the relevant interface's PPP session will be renegotiated after the restart and as a result there may be a short period where traffic is lost.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_CHKPT_DUPLICATE Duplicate [chars] checkpoint record found for [chars]

Explanation    Whilst restoring one of its checkpoint tables PPP MA found multiple entries for the same interface. PPP MA will use the first checkpoint entry it finds for each interface and ignore any subsequent duplicates. This is caused by a programming error.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_CLOCK Unexpected error encountered whilst retrieving the value of the [chars] clock: [chars]

Explanation    PPP MA encountered an error whilst retrieving the value of the realtime clock. The error message includes details of the reason for the error. This is a fatal error and the PPP MA process will abort and be restarted to recover.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_DEBUG Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the debug service. The error message describes what operation has failed and why it failed. The error could be caused by low memory resource or programming error.

Recommended Action    In many cases, PPP MA will recover by itself. If it does not then restarting the process may help. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_EVC_CLOSE Error closing '[chars]' connection: [chars]

Explanation    PPP MA failed to close a connection to an essential service. This is an internal error and it requires a restart of the process for recovery.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_EVC_CREATE Error creating '[chars]' connection: [chars]

Explanation    PPP MA failed to create a connection to an essential service during initialization. This is an internal error. It requires a restart of the process for recovery.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_EVC_ERROR Error resetting '[chars]' connection: [chars]

Explanation    After detecting an error with the connection to the specified service, PPP MA failed to reset that connection. This is an internal error. It requires a restart of the process for recovery.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_EVC_EVM_HANDLER Error registering for data events on '[chars]' connection: [chars]

Explanation    During initialization, PPP MA failed to register for input or output notifications for the specified service. This is an internal error. It requires a restart of the process for recovery.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_EVC_GET_FD Error retrieving the Connection ID from the '[chars]' connection: [chars]

Explanation    PPP MA failed to retrieve the file descriptor associated with the specified service. This is an internal error.

Recommended Action    Consider restarting the PPP MA process. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_EVC_NOTIFY Error registering for critical events on '[chars]' connection: [chars]

Explanation    During initialization, PPP MA failed to register for essential notifications regarding the state of the connection for the specified service. This is an internal error. It requires a restart of the process for recovery.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_EVC_OPEN Error opening '[chars]' connection: [chars]

Explanation    PPP MA failed to open a connection to an essential service during initialization. This is an internal error. It requires a restart of the process for recovery.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_EVM_ATTACH Failed to register a handler for '[chars]' messages: [chars]

Explanation    PPP MA failed to register a handler for the specified class of event. This is an initialization error and implies that PPP MA will not be able to operate correctly. The PPP MA process will abort and be restarted in an attempt to recover. The cause may be a resource starvation problem but is most likely to be an internal programming error. The error message should give more details.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Restart the PPP MA process. *RECUR*

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_EVM_CREATE Error creating the PPP MA Event Manager: [chars]

Explanation    PPP MA failed to create its Event Manager which is a critical resource for the operation of the process. This error may be caused by low memory resources. The process will abort and be restarted in an attempt to recover.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *SUPPORT*

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_EVM_SEND Failed to send '[chars]': [chars]

Explanation    PPP MA failed to send the specified message. The cause may be a resource starvation problem but is most likely to be an internal programming error. The error message should give more details.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Restart the affected PPP MA process. *RECUR*

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_IMC Unexpected IfMgr error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error communicating with Interface Manager. The error message describes what operation has failed and why it failed. The most likely reason for this is a temporary connection problem with the Interface Manager Control Server, but the error could also be caused by low memory resource or programming error.

Recommended Action    In many cases, PPP MA will recover by itself. If it does not then restarting the process may help. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information..

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_IP_ARM Failed to [chars] [chars]: [chars]

Explanation    IPCP encountered an error using the IP-ARM API. The error message describes what operation failed. This may be a resource starvation problem or an internal programming error.

Recommended Action    Restart the local ipv4_ma process and/or the ppp_ma process. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_LAS Failed to [chars] [chars]: [chars]

Explanation    IPV6CP encountered an error using the LAS API. The error message describes what operation failed. This may be a resource starvation problem or an internal programming error.

Recommended Action    Restart the local ipv6_ma process and/or the ppp_ma process. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*.

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_LTRACE Unexpected error encountered whilst [chars] the [chars] buffer: [chars]

Explanation    PPP MA encountered an error using the Lightweight Tracing service. The error message describes what operation has failed and why it failed. This is a fatal error and the PPP MA process cannot continue. It will abort and subsequently be restarted by SysMgr in an attempt to recover.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_MEM_ALLOC Failed to allocate [unsigned int] bytes for '[chars]'

Explanation    The process failed to allocate memory for the specified resource.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_MGD_TIMER Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an unexpected error using the Managed Timer library. This is most likely to be due to a low memory condition but may also be an internal programming error. The error message should provide more information about the cause.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. Consider restarting the PPP MA process. *RECUR*.

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_PAK Error handling pakman corruption problem: [chars]. Process exiting.

Explanation    The connection to packet manager was errored and the attempt to recover failed. Restarting the process should resolve the problem.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_SYSDB Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error using the SysDB service. The error message describes what operation has failed and why it failed. The most likely reason for this is a connection problem with the SysDB server, but the error could also be caused by low memory resources or programming error.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_SYSMGR Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error whilst communicating with SysMgr. The error message describes what operation has failed and why it failed. This is a fatal error and the PPP MA process will abort and be restarted to recover.

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_SYSMGR_MDR Unexpected error encountered whilst [chars]: [chars]

Explanation    PPP MA encountered an error whilst communicating with SysMgr. The error message describes what operation has failed and why it failed. Sysmgr will take action to recover if appropriate. It is possible that this error has occured after MDR. If so then the recovery may require a cold reload of the card

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

Error Message     
 
    
    
   

%L2-PPP_MA-4-ERR_WAVL_INIT Error initializing the WAVL tree used to store PPP MA IDBs: [chars].

Explanation    PPP MA encountered an unexpected error which prevents it from functioning. This error may be caused by low memory resources. The process will abort and be restarted in an attempt to recover.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.. *RECUR*

Error Message     
 
    
    
   

%L2-PPP_MA-6-ERR_EVC_DESTROY Error destroying '[chars]' connection: [chars]

Explanation    During process termination PPP MA failed to destroy a connection to a service provided by another process. This is an internal error.

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

Error Message     
 
    
    
   

%L2-PPP_MA-6-ERR_EVM_EVENT_BLOCK Error blocking waiting for an event to process: [chars]

Explanation    This is an unexpected error. The PPP MA process may recover by itself, or it may need to be restarted to recover.

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

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-3-INTERNAL_ERR Error: [chars]: Err=[dec]

Explanation    A driver internal error occurred which involves exiting the process. %s - indicates the reason for the failure. %d - is the error reason.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover If the message recurs, copy the error message exactly as it appears on 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-3-INVALID_COUNT Error: [chars]: Err=[dec]

Explanation    This is a error message in the PSE Driver to indicate either anomolies which are notservice impacting. Some of the messages may indicate a failure to allocate resources needed by applications. In many cases these messages must not keep appearing after the temperory situation is resolved. %s - indicates the reason for the failure. %d - is the error reason.

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

Error Message     
 
    
    
   

%L2-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 Info: [chars]

Explanation    This is a Informational message in the PSE Driver to indicate an operation. %s - indicates the informational message.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%L2-PSE-6-INFO_MSG [chars]

Explanation    This is a informational message in the PSE Driver to indicate an operation.

Recommended Action    No action is required.

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*

QM_E5 Messages

Error Message     
 
    
    
   

%L2-QM_E5-4-INTERRUPT [chars]: [chars] : reg value [hex]

Explanation    The queueing asic experienced an interrupt, and will be reset. After reset, normal operation should resume.

Recommended Action    Log the error. If the error persists after reset, contact support.

Error Message     
 
    
    
   

%L2-QM_E5-4-INTERRUPT2 [chars]: [chars] : reg1 [hex]: reg2 [hex]

Explanation    The queueing asic experienced an interrupt, and will be reset. After reset, normal operation should resume.

Recommended Action    Log the error. If the error persists after reset, contact support.

Error Message     
 
    
    
   

%L2-QM_E5-7-INTERRUPT3 [chars]: [chars]: error_reg: [hex] error_info: [hex]

Explanation    The queueing asic experienced an interrupt, and is non-fatal. In some cases its corrected by software and remaining cases its occurences logged.

Recommended Action    Log the error.

Error Message     
 
    
    
   

%L2-QM_E5-7-INTERRUPT4 [chars]: [chars]: error_reg: [hex]

Explanation    The queueing asic experienced an interrupt, and is non-fatal. In some cases its corrected by software and remaining cases its occurences logged.

Recommended Action    Log the error.

QM Messages

Error Message     
 
    
    
   

%L2-QM-4-INTERRUPT [chars]: [chars] : reg value [hex]

Explanation    The queueing asic experienced an interrupt, and will be reset. After reset, normal operation should resume.

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

QUEUEING Messages

Error Message     
 
    
    
   

%L2-QUEUEING-3-FATAL_ERR [chars]: Err=[dec]

Explanation    A fatal error occurred in QUEUEING ASIC Driver which involves exiting the process. The process will be respawned, but if it continues to fail the linecard will be reset, as the linecard cannot operate without this process.

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