Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.4
Layer 2 Messages
Downloads: This chapterpdf (PDF - 426.0KB) The complete bookPDF (PDF - 1.84MB) | Feedback

Layer 2 Messages

Table Of Contents

Layer 2 Messages

port_cfg Messages

SLARP Messages

SLARP_EA Messages

SLARP_Lite Messages

SLOGIC Messages

SONET_APS Messages

SONET_LOCAL Messages

SPA_192 Messages

SPA_ETHER Messages

SPA_OC3_OC12 Messages

SPA_OC48 Messages

SPA Messages

SPAMSG Messages

SPU_LIB Messages

SPU Messages

SRP Messages

STREE 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:

port_cfg Messages

SLARP Messages

SLARP_EA Messages

SLARP_Lite Messages

SLOGIC Messages

SONET_APS Messages

SONET_LOCAL Messages

SPA_192 Messages

SPA_ETHER Messages

SPA_OC3_OC12 Messages

SPA_OC48 Messages

SPA Messages

SPAMSG Messages

SPU_LIB Messages

SPU Messages

SRP Messages

STREE Messages

port_cfg Messages

Error Message     
 
    
    
   

%L2-port_cfg-3-INIT failed to initialize [chars]: [chars]

Explanation    A submodule was unable to initialze due to the specified 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.

SLARP Messages

Error Message     
 
    
    
   

%L2-SLARP-1-CAPS_ADD [chars]: Could not add slarp capsulation : [chars]

Explanation    Could not add the slarp capsulation in IM

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-SLARP-1-CAPS_REMOVE [chars]: Could not remove slarp capsulation : [chars]

Explanation    Could not remove the capsulation in question.

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-SLARP-1-CLOCK_READ_ERROR Unable to read the clock: [chars]

Explanation    Unable to read the clock.

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-SLARP-1-CONN_ALLOC Failed to allocate event connection with [chars].

Explanation    An attempt to allocate a connection resource 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-SLARP-1-CONN_NOTIFY Failed to attach event connection handler for [chars].

Explanation    An attempt to attach a handler for an event connection 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-SLARP-1-DEBUG_REGISTER Could not register for debug events : [chars]

Explanation    An attempt ot register with the debug infrastructure failed. The failure cannot be handled, so the process will have exited and will be automatically 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-SLARP-1-EVENT_CONN Unable to initialize slarp timers

Explanation    Can not initialize the even channel used by slarp timers.

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-SLARP-1-EVENTBLOCK event_block returned early : [chars]

Explanation    An unexpected or erroneous return while waiting for events.

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-SLARP-1-IM_STATEQUERY Failed to query IM interface state: [chars]

Explanation    An attempt to query the interface state from IM 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-SLARP-1-INVTIMER invalid timer [dec]

Explanation    An error occurred attempting to transmit a SLARP packet.

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-SLARP-1-NO_INITIAL_CONFIG Failed to get the initial configuration: [chars]

Explanation    The initial configuration of the box was unable to be determined.

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-SLARP-1-NOIDB [chars]: Event which we do not have record of

Explanation    An internal software error occurred.

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-SLARP-1-NORESOURCE [chars] failed to allocate resource in [chars]

Explanation    An attempt to allocate a resource 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-SLARP-1-TIMER_ALLOC [chars]: Could not allocate a timer for SLARP : [chars]

Explanation    Could not allocate a timer. SLARP will not run on this 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-SLARP-1-TRACE_REGISTER Failed to register with tracing infrastructure: [chars]

Explanation    An attempt to register with the tracing infrastrucure failed. The failure cannot be handled, so the process will have exited and will be automatically restarted. The root cause of the problem is likely to be with the tracing infrastructure, rather than with this process in particular.

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-SLARP-1-TREE_INSERT [chars]: Could not insert interface into storage.

Explanation    We could not store information about this 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-SLARP-5-OLDSEQ [chars]: Outdated sequence number [dec], current [dec]

Explanation    A keepalive packet was received out of sequence with previous keepalives.

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-SLARP-5-PKTLENGTH Invalid packet length [dec] recv on [chars], should be [dec]

Explanation    An invalid SLARP packet was received.

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.

SLARP_EA Messages

Error Message     
 
    
    
   

%L2-SLARP_EA-2-EVENT_BLOCK Failure during receipt of message. Error: [chars]

Explanation    A failure occurred handling a message arriving at the SLARP capsulation EA 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-SLARP_EA-2-INIT Failure during intialisation of SLARP Caps EA. Error: [chars]

Explanation    A failure occurred during the initialisation of the SLARP capsulation EA 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-SLARP_EA-3-ADJ_UPDATE_FAIL [hex]: unable to update adjacency : [chars]

Explanation    Adjacency information was not able to be updated.

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

SLARP_Lite Messages

Error Message     
 
    
    
   

%L2 control-SLARP_Lite-3-ERR_CSL_DLL_ASYNC_SEND_FAIL Send async pulse to slarp lite process fails; Error [chars]

Explanation    Attempt to send pulse to SLARP 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-SLARP_Lite-3-ERR_CSL_DLL_CHAN_CONNECT_FAIL Cannot connect to slarp lite process; Error [chars]

Explanation    Attempt to connect to slarp 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-SLARP_Lite-3-ERR_SHMEM_MMAP_FAIL Cannot mmap file [chars]; Error [chars]

Explanation    Attempt to mmap the shared memory fails

Error Message    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.

SLOGIC Messages

Error Message     
 
    
    
   

%L2-SLOGIC-4-ANOMALY [chars]

Explanation    A SW exception occurred in SLOGIC Library

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.

SONET_APS Messages

Error Message     
 
    
    
   

%L2-SONET_APS-4-WARNING [chars] - [chars]

Explanation    A non-fatal error occured while executing the function in question. The message contains info about the cause of the failure and possibly anticipated actions/effects.

Recommended Action    Verify continued correct operation of SONET APS.

Error Message     
 
    
    
   

%L2-SONET_APS-4-WP_INFO Connection to [chars]%s [chars]

Explanation    State change in the APS group internal communication system detected. Expected during transitory conditions at config changes, OIR, etc. The message contains info about the WP communication components affected.

Recommended Action    Verify continued correct operation of SONET APS.

Error Message     
 
    
    
   

%L2-SONET_APS-6-CONFLICT [chars] ([chars]) - [chars]

Explanation    A conflict failure occured The message contains info about the cause of the failure and possibly anticipated actions/effects.

Recommended Action    Fix the confguration error for proper operation of SONET APS.

Error Message     
 
    
    
   

%L2-SONET_APS-6-CONTACT [chars] [chars] [dec] [chars] [dec] [chars]

Explanation    Debug messages for APS.

Recommended Action    No Action requirements.

Error Message     
 
    
    
   

%L2-SONET_APS-6-REQUEST_PREEMPTED APS group [dec] [chars] [dec]: preempted

Explanation    The user external request is preempted.

Recommended Action    Not Action requirements.

Error Message     
 
    
    
   

%L2-SONET_APS-6-UPDOWN [chars] [chars] [dec] [chars] [dec] [chars]

Explanation    Debug messages for APS.

Recommended Action    No Action requirements.

Error Message     
 
    
    
   

%L2-SONET_APS-7-ERROR [chars] failed ([chars]) - [chars]

Explanation    A general failure occured while executing the function in question. The message contains info about the cause of the failure and possibly anticipated actions/effects.

Recommended Action    Verify continued correct operation of SONET APS.

Error Message     
 
    
    
   

%L2-SONET_APS-7-NOMEM Not enough memory for [chars]

Explanation    The process is out of memory.

Recommended Action    Check process list for source of memory loss. Check if h/w memory requirements are met.

SONET_LOCAL Messages

Error Message     
 
    
    
   

%L2-SONET_LOCAL-4-ALARM [chars]: [chars] [chars]

Explanation    The specified SONET Alarm has been declared or released.

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

SPA_192 Messages

Error Message     
 
    
    
   

%L2-SPA_192-3-ERR_SPA_IPSEC_MIX_UNSUPPORTED Inserted node [chars] caused an unsupported configuration. SPA-IPSEC-2G-2 cannot coexist with another type of SPA in the same line card.

Explanation    SPA SPA-IPSEC-2G-2 cannot coexist with another type of SPA in the same line card. This configuration is not supported and can cause non-deterministic behaviors.

Recommended Action    Either physically remove all SPA-IPSEC-2G-2 SPAs or all non SPA-IPSEC-2G-2 SPAs.

Error Message     
 
    
    
   

%L2-SPA_192-3-ERR_SPA_UNSUPPORTED Inserted node [chars] is not supported by Cisco 12000 Series SPA Interface Processor-601 line card. Please remove to prevent damages to the hardwares.

Explanation    A SPA identified by nodeid %s above is not supported by Cisco 12000 Series SPA Interface Processor-601 line card. The SPA should be remove immediately to prevent damages to the hardwares.

Recommended Action    Physcially remove the SPA module from the line card.

Error Message     
 
    
    
   

%L2-SPA_192-3-ERR_SPA_UNSUPPORTED Inserted node [chars] is not supported by Cisco 12000 Series SPA Interface Processor-600 line card. Please remove to prevent damages to the hardwares.

Explanation    A SPA identified by nodeid %s above is not supported by Cisco 12000 Series SPA Interface Processor-600 line card. The SPA should be remove immediately to prevent damages to the hardwares.

Recommended Action    Physcially remove the SPA module from the line card.

Error Message     
 
    
    
   

%L2-SPA_192-3-JACKET_ERROR [chars]

Explanation    SPA 192 Jacket error

Recommended Action    When errors occur in jacket, it is very likely the jacket process will restart itself.

Error Message     
 
    
    
   

%L2-SPA_192-3-JACKET_V2_ERROR [chars]

Explanation    SPA 192 Jacket V2 error

Recommended Action    When errors occur in jacket, it is very likely the jacket process will restart itself.

Error Message     
 
    
    
   

%L2-SPA_192-3-SPARULE_INT_ERROR [chars]

Explanation    SPA 192 Jacket V2 SPA rule internal error

Recommended Action    This would indicate an internal error in SPA rule module affecting our ability to insert/remove new SPA. This may require jacket process restart.

Error Message     
 
    
    
   

%L2-SPA_192-6-SPARULE_ERROR [chars]

Explanation    SPA 192 Jacket V2 SPA rule error

Recommended Action    This would indicate an error during insertion/removal of SPA. If error occures during OIR than it is likely that problem could be due to invalid combination or SPA type used as indicated by additional text.

Error Message     
 
    
    
   

%L2-SPA_192-6-UPGRADE_FPGA [chars]

Explanation    Upgrade SPA FPGA message

Recommended Action    none

Error Message     
 
    
    
   

%L2-SPA_192-6-UPGRADE_FPGA [chars]

Explanation    Upgrade SPA FPGA message

Recommended Action    none

SPA_ETHER Messages

Error Message     
 
    
    
   

%L2-SPA_ETHER-2-SPA_MAC_ERR [chars]

Explanation    The internal SPA MAC got out of sync. SW needs to reset the device in order to clear the issue

Recommended Action    If reseting the MAC device fixes the issue, nothing needs to be done. If the reset does not work, the SPA will need to be SW OIR'd. This can be easily checked by doing 'top' on the LC with the issue. If the CPU is very high, the reset did not work.

Error Message     
 
    
    
   

%L2-SPA_ETHER-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.

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*

SPA_OC48 Messages

Error Message     
 
    
    
   

%L2-SPA_OC48-3-DRIVER_ERR [chars] [chars]

Explanation    SPA OC48 driver error messages

Recommended Action    *NONE*

Error Message     
 
    
    
   

%L2-SPA_OC48-6-INFO [chars] [chars]

Explanation    SPA OC48 informational message

Recommended Action    *NONE*

Error Message     
 
    
    
   

%L2-SPA_OC48-7-DEBUG [chars] [chars]

Explanation    SPA OC48 debug message

Recommended Action    *NONE*

SPA Messages

Error Message     
 
    
    
   

%L2-SPA-3-IPSEC_SPA_CRASH No Heartbeat from IPSec SPA. Reloading the SPA

Explanation    IPsec SPA crashed, has to be reloaded.

Recommended Action    None.

Error Message     
 
    
    
   

%L2-SPA-3-PLIM_HEARTBEAT_ERR [chars]: bay [dec] heartbeat failed, expected seq# [unsigned int] received seq# [unsigned int], Time since last message [dec]s

Explanation    The IPC communication between local CPU and host in the specified slot indicated in the message is not functional. If the problem persists the SPA will be reloaded to recover from the failure.

Recommended Action    If the problem persists, try to reseat the SPA. If reseating does not help, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message     
 
    
    
   

%L2-SPA-3-SYSDB_ERROR [chars]

Explanation    SPA Infrastructure SysDb 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-SPA-4-CERR_REGISTRATION_FAILURE Registration of error strings failed with error [hex]

Explanation    Error string reistration 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-SPA-5-APPS_IMAGE_DOWNLOADING Downloading SPA Application Image ([chars])...

Explanation    Downloading SPA Application image as indicated in the message

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-APPS_IMAGE_ERROR Download SPA Application Image failed.

Explanation    Failed to download the SPA Application image.

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-APPS_IMAGE_SIZE_ERR SPA Application image exceeds RAM size: Image size ([dec]) Shared mem size ([dec])

Explanation    The size of the SPA Application image is too big.

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-DOWNLOAD_METHOD_ERR SPA Download method [dec] not supported

Explanation    The specified download method is not supported

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-FILE_SIZE_ERR SPA File exceeds Rdisk size: File size ([dec]) Rdisk size ([dec])

Explanation    The size of the SPA File is too big.

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-OIR_ERROR [chars]

Explanation    SPA related error as indicated in the msg

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-OIR_INSERTED SPA discovered in bay [dec]

Explanation    For displaying SPA OIR.

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-OIR_REMOVED SPA removed from bay [dec]

Explanation    For displaying SPA OIR.

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-OS_IMAGE_DOWNLOADING Downloading SPA OS Image ([chars])...

Explanation    Downloading SPA OS image as indicated in the message

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-OS_IMAGE_ERROR Download SPA OS Image failed

Explanation    Failed to download the SPA OS image.

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-OS_IMAGE_SIZE_ERR SPA OS image exceeds RAM size: Image size ([dec]) Shared mem size ([dec])

Explanation    The size of the SPA OS image is too big.

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-PLIM_EVENT_INIT_ERR SPA Init Event Server failed

Explanation    Creating SPA event handling server failed.

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-PLIM_KA_INIT_ERR SPA Init SPA Keepavlie Handler failed

Explanation    Creating SPA keepalive server failed.

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-PLIM_RELOADING Reloading [chars] in subslot [unsigned int] after heartbeat failure ...

Explanation    Reloading SPA because of heartbeat failure.

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-5-STATE_CHANGE SPA in bay [dec] [chars]

Explanation    For displaying state of a SPA

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPA-6-OPTICS_INSERTION Optics module inserted into SPA in bay [dec]

Explanation    Optics module has been inserted. %d - indicates the bay number

Recommended Action    None. This is an informational message only.

Error Message     
 
    
    
   

%L2-SPA-6-OPTICS_REMOVAL Optics module removed from SPA in bay [dec]

Explanation    Optics module has been removed. %d - indicates the bay number

Recommended Action    None. This is an informational message only.

SPAMSG Messages

Error Message     
 
    
    
   

%L2-SPAMSG-3-ERR [chars]

Explanation    SPA related error msg

Recommended Action    none.

Error Message     
 
    
    
   

%L2-SPAMSG-6-INFO [chars]

Explanation    SPA related info

Recommended Action    none.

SPU_LIB Messages

Error Message     
 
    
    
   

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

Explanation    Unable to send a message to the SPU server.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%L2-SPU_LIB-6-INFO_WARNING [chars]

Explanation    This is an informational message in the SPU client LIB.

Recommended Action    *NONE*

SPU Messages

Error Message     
 
    
    
   

%L2-SPU-3-FATAL_ERR Fatal error: [chars]: Err=[dec]

Explanation    A fatal error occurred in SPU Driver.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%L2-SPU-3-NONFATAL_ERR Nonfatal error: [chars]: Err=[dec]

Explanation    A non fatal error occurred in SPU Driver.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%L2-SPU-3-SER_NOTIF Soft error occurred... [chars] : RDRAM error status 1 : [dec], RDRAM error status 2 : [dec]

Explanation    A fatal error occurred in SPU h/w.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%L2-SPU-6-INFO_MSG [chars]

Explanation    This is a Informational message in the SPU Driver.

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.

Error Message     
 
    
    
   

%L2-SRP-3-ERR_DUP_MAC_ADDR [chars]: Duplicate mac addresses in topology

Explanation    Another node on the ring is using the same MAC address as this node. This can effect traffic forwarding.

Recommended Action    Correct the configuration of each node, where necessary, to ensure that each node uses a unique MAC address. Use the 'show srp topology' CLI to identify any nodes using the same MAC address.

Error Message     
 
    
    
   

%L2-SRP-3-ERR_MEDIA_SINGLE_RING [chars] SRR usage changed ([chars])

Explanation    SRR ring usage is changed using Inner, Outer or Both rings. There are/were multiple faults (or user requests) on the ring causing potential loss of traffic/bandwidth.

Recommended Action    Clear the cause of each fault/wrap on the ring. Use the 'show srp topology' CLI to identify which nodes are wrapped.

Error Message     
 
    
    
   

%L2-SRP-3-ERR_MEDIA_WRAP [chars] [chars] on side [char] ([chars])

Explanation    The specified side of the interface has wrapped or unwrapped for the given reason. There is/was a fault (or user request) on the ring causing potential loss of traffic/bandwidth.

Recommended Action    Clear the cause of the fault/wrap. Use the 'show srp ips' and 'show srp failures' CLI to determine the root cause of the fault (if still present).

Error Message     
 
    
    
   

%L2-SRP-3-ERR_SRR_VER_MISMATCH [chars] SRR version mismatch detected.

Explanation    SRR has detected incompatible versions with other nodes on the ring and cannot inter-operate.

Recommended Action    Update the software image on all nodes of the ring to the same SRR version.

Error Message     
 
    
    
   

%L2-SRP-6-INFO_SINGLE_NODE_TOPO [chars]: Single node in topology

Explanation    The topology discovery resulted in a single node being found. This is most likely a transient condition during initial ring bring-up.

Recommended Action    Verify that the condition is not transient by using 'show srp topology' CLI. Verify the interface is not physically looped back, meaning side A is connected to side B. Verify that the other nodes are not in PassThru mode (ADMIN DOWN). Verify that neither of the adjacent nodes have the same BIA address by using 'show interface srp' CLI. If a duplicate BIA address is found: 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.

STREE Messages

Error Message     
 
    
    
   

%L2-STREE-4-CONNECT_FAIL STP Server not available

Explanation    stp_process is most likely in a bad state or basic system services have failed. stp_process error messages are generally indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. 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-STREE-4-CREATE_FAIL STP Create Failed : [chars]

Explanation    stp_process ran into errors while creating the spanning tree instance for control ethernet. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. 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-STREE-4-MSGSEND_FAIL Message Send Failed : [chars]

Explanation    stp_process is most likely in a bad state or basic system services have failed. stp_process error messages are generally indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. 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-STREE-4-PORT_CREATE_FAIL Stp port creation fail : [chars]

Explanation    Spanning tree port creation failed on the node. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Spanning tree port creation will be retried automatically. Check if the 'stp_process' is up and running if this error is encountered. 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-STREE-4-SET_MACADDR_FAIL STP Set Mac Addr Failed : [chars]

Explanation    MAC address assigned to the spanning tree was either invalid or was not able to be set for the spanning tree instance. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. 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-STREE-4-START_FAIL Failed to start STP instance : [chars]

Explanation    Spanning tree could not be started on the control ethernet for the node. stp_process error messages are indicative of health of control-ethernet which is critical for system operation. Misbehavior of stp_process can cause instability in the system.

Recommended Action    Sysmgr process will restart the stp_process if it encounters this error. Check if the 'stp_process' is up and running if this error is encountered. 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.

Recommended Action   

Error Message     
 
    
    
   

%L2 control-SLARP_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-SLARP_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-SLARP_Lite-3-ERR_SHMEM_UNAVAILABLE SLARP lite SHMEM can accommodate only [dec] records (request for [dec] records)

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