Downloads |
 Feedback
|
Table Of Contents
IUA Messages
Error Message%IUA-3-IP_ADDR_CFG_ERROR : Invalid IP address in IUA AS configuration for [chars]
Explanation The IP address used in the ISDN User Adaptation Layer Application Server configuration is not a valid local IP address. The IP address does not appear in the IP address configuration of an interface. The system will continue to attempt to complete initialization of the application server until a matching IP address is configured on a local interface.
Recommended Action Ensure that the IP address used in ISDN User Adaptation Layer Application Server configuration is a valid local IP address.
Error Message%IUA-4-IUA_AS_STATE_ACTIVE : IUA : AS [chars] new ASP [chars] active :old-state [chars] new-state [chars].
Explanation IUA has detected that the active AS has detected an ASP state change.
Recommended Action No action is required.
Error Message%IUA-4-IUA_AS_STATE_DOWN : IUA : AS [chars] active ASP [chars] going down :old-state [chars] new-state [chars].
Explanation IUA has detected that the active AS has detected an ASP state change.
Recommended Action No action is required.
Error Message%IUA-4-IUA_AS_STATE_PEND : IUA : AS [chars] active ASP [chars] going down :old-state [chars] new-state [chars].
Explanation IUA has detected that the active AS has detected an ASP state change.
Recommended Action No action is required.
Error Message%IUA-4-IUA_AS_STATUS_ASP_CHANGE : IUA : AS [chars] changing active asp from [chars] to [chars].
Explanation IUA has detected that the active ASP has changed due to a server switchover.
Recommended Action No action is required.
IVR Messages
Error Message%IVR-1-APP_PARALLEL : Cannot use dial-peer [dec] (parallel hunt-group) for a rotary or in a hunt-group call.
Explanation The dial-peer for parallel hunt-groups must have a unique pilot number.
Recommended Action Create a unique dial-peer destination-number for the parallel hunt-group.
Error Message%IVR-1-APP_PARALLEL_INVALID_LIST : Call terminated. Huntgroup '[dec]' does not contain enough valid SIP end-points to proceed with a parallel call.
Explanation The call to a parallel hunt-group was denied because less than two valid SIP end-points were found in the huntgroup list.
Recommended Action Check the hunt-group list's numbers. Remove any incorrect numbers or numbers that have a non-SIP dial-peer. If the numbers are from SIP phones, then verify whether the phones have registered to the system yet.
Error Message%IVR-1-APP_SEQ_HUNT : Pilot hunt-group '[chars]' found in hunt-group list. Nested hunt-groups are allowed only as the hunt-group's final number.
Explanation A nested sequential hunt-group was detected in the dial-peer rotary. Nested hunt-groups are not supported.
Recommended Action Do not create hunt-group lists that contain hunt-group pilot numbers.
Error Message%IVR-2-APP_CRIT : [chars]
Explanation A critical message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
Error Message%IVR-2-APP_CRIT_R : [chars]
Explanation A critical message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
Error Message%IVR-2-INVALID_DSAPP_DIALPEER : Service dsapp contains an invalid dial peer tag: [chars]
Explanation An invalid dial peer tag has been configured for the dsapp service. The tag either is not in the range from 1 to 2147483647, or it belongs to a non-existent dial-peer.
Recommended Action Enter the show running-config or the show dial-peer voice command to find a valid dial peer tag. Reconfigure the dial peer with a valid tag or remove the dial peer tag completely to allow the system to match from the system dial peers.
Error Message%IVR-3-ABNORMAL_EXIT : TCL IVR Process for this call with CallID [dec] exits , bad event: [chars] received
Explanation The TCL IVR call process exited for the specified call. The call process did not clear a prior call properly, so other events could not be handled. Only the specified call is affected.
Recommended Action If problem persists for subsequent calls,copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%IVR-3-APP_ERR : [chars]
Explanation An error message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
Error Message%IVR-3-APP_ERR_R : [chars]
Explanation An error message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
Error Message%IVR-3-BADSCRIPT : Could not parse malformed IVR script: [chars]
Explanation Could not parse malformed IVR script.
Recommended Action Check the script and fix the syntax error.
Error Message%IVR-3-BAD_IVR_VERSION : Script requires version %d.%d, image supports %d.%d
Explanation IVR Script requires a higher IVR infrastructure version
Recommended Action Upgrade IOS, or use a different script
Error Message%IVR-3-INVALID_MAX_PROMPTS : [chars]: This version of IOS does not support prompt playout for IVR applications.
Explanation An IVR application has been used on a gateway that does not support IVR prompt playout.
Recommended Action Ensure that this platform and Cisco IOS software version support the IVR feature set.
Error Message%IVR-3-INVALID_SCRIPT : App [chars]: Invalid IVR script to handle callID [dec]
Explanation The specified call will be dropped due to an invalid script.
Recommended Action Ensure that the script exists on the server, is readable, and is supported.
Error Message%IVR-3-LOW_CPU_RESOURCE : IVR: System experiencing high cpu utilization ([dec]/100). Call (callID=[dec]) is rejected.
Explanation System does not have enough CPU resources available to accept a new call
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway.
Error Message%IVR-3-LOW_MEMORY : IVR : Sytem running on low memory. Free memory: %l bytes. Call is rejected.
Explanation System does not have enough memory to accept calls
Recommended Action Check to see what is causing low system memory.
Error Message%IVR-3-LOW_MEMORY_RESOURCE : IVR: System running low on memory ([dec]/100 in use). Call (callID=[dec]) is rejected.
Explanation System does not have enough free memory to accept a new call.
Recommended Action Ensure that the gateway has the recommended amount of memory for this IOS feature set and version.
Error Message%IVR-3-NOPROMPT : Could not create IVR prompt %s errno=%d=%s
Explanation Could not read in the IVR prompt
Recommended Action Check that prompt exists on the server, and is readable.
Error Message%IVR-3-NOSCRIPT : Could not load IVR script %s errno=%d=%s
Explanation Could not read in the IVR script
Recommended Action Check that script exists on the server, and is readable.
Error Message%IVR-3-NO_INTERNAL_IDB : Unable to create internal interface descriptor
Explanation Insufficient resources are available to create a required data structure.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%IVR-3-NO_IO_MEMORY : [chars]: Failed to create pool_group [hex] buffer_pool [hex] platform_mc_buf_pool_count [dec]
Explanation There is not enough I/O memory to create the IVR private packet pool.
Recommended Action Ensure that there is enough I/O memory.
Error Message%IVR-4-APP_WARN : [chars]
Explanation A warning message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
Error Message%IVR-4-APP_WARN_R : [chars]
Explanation A warning message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
Error Message%IVR-4-INVALID_DSAPP_BLINDTIME : Blind-xfer-wait-time [dec] is invalid. Resetting to [dec] seconds.
Explanation The configured value for blind-xfer-wait-time was outside of the acceptable range (0-10) and has been reset to the indicated value.
Recommended Action If the new value for blind-xfer-wait-time is unacceptable, you can change it from the command line interface.
Error Message%IVR-4-INVALID_DSAPP_TOGGLE_TIME : Disc-toggle-time [dec] is invalid. Resetting to [dec] seconds.
Explanation The configured value for disc-toggle-time was outside of the acceptable range (10-30) and has been reset to the indicated value.
Recommended Action If the new value for disc-toggle-time is unacceptable, you can change it from the command line interface.
Error Message%IVR-5-APP_LOG_DUR_CALL_DETECTED : [chars]
Explanation A notification message was reported by an IVR application on detecting long duration call.
Recommended Action This is not a problem but notifying syslog about long duration call.
Error Message%IVR-5-APP_MED_INACT_DETECTED : [chars]
Explanation A notification message was reported by an IVR application on detecting media inactivity.
Recommended Action This is not a problem but notifying syslog about media inactivity.
Error Message%IVR-5-APP_MED_REACT_DETECTED : [chars]
Explanation A notification message was reported by an IVR application on detecting media activity.
Recommended Action This is not a problem but notifying syslog about media activity.
Error Message%IVR-6-APP_INFO : [chars]
Explanation An informational message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
Error Message%IVR-6-APP_INFO_R : [chars]
Explanation An informational message was reported by an IVR Tcl application.
Recommended Action The remedy of the problem is application specific.
Error Message%IVR-6-APP_PARALLEL : Cannot use dial-peer [dec] (parallel hunt-group) for a rotary or in a hunt-group call.
Explanation The dial-peer for parallel hunt-groups must have a unique pilot number.
Recommended Action Create a unique dial-peer destination-number for the parallel hunt-group.
Error Message%IVR-6-APP_SEQ_HUNT : Pilot hunt-group '[chars]' found in hunt-group list. Nested hunt-groups are allowed only as the hunt-group's final number.
Explanation Nested sequential hunt-group detected in dial-peer rotary. Nested hunt-groups is unsupported.
Recommended Action Do not create hunt-group lists that contain hunt-group pilot numbers.
Error Message%IVR_MSB-3-INVALID_MAX_PROMPTS : [chars]: This version of IOS does not support prompt playout for IVR applications.
Explanation This error will be displayed if an IVR application is used on a gateway that does not support IVR prompt playout.
Recommended Action Ensure that this platform and IOS version support the IVR feature set.
Error Message%IVR_MSB-3-NOPROMPT : Could not create IVR prompt [chars] errno=[dec]=[chars]
Explanation Could not read in the IVR prompt.
Recommended Action Check that prompt exists on the server, and is readable.
Error Message%IVR_MSB-3-NO_IO_MEMORY : [chars]: Failed to create pool_group [hex] buffer_pool [hex] platform_mc_buf_pool_count [dec]
Explanation No IO memory to create IVR private pak pool.
Recommended Action Check to see if there is enough IO memory.
Error Message%IVR_NOSIGNALING-3-LOW_CPU_RESOURCE : IVR: System experiencing high cpu utilization ([dec]/100). Application cannot be instantiated.
Explanation System does not have enough CPU capacity to spawn a new instance of IVR application
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway.
Error Message%IVR_NOSIGNALING-3-LOW_MEMORY_RESOURCE : IVR: System running low on memory ([dec]/100 in use). Application cannot be instantiated.
Explanation System does not have enough free memory to spawn a new instance of IVR application
Recommended Action Ensure that the gateway has the recommended amount of memory for this Cisco IOS software feature set and version.
IXP1200_CP Messages
Error Message%IXP1200_CP-1-CMDERR : [chars]: Command [hex] failed with status [hex]
Explanation A command was sent to the Encryption AIM, and it responded that the command had an error. The details of the failure depend upon the circumstances, but in all likelihood the Encryption AIM is faulty and should be replaced.
Recommended Action The CP will most likely need to be replaced. 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP1200_CP-1-FUTIL : Flash Utilities were downloaded instead of the RAM Application
Explanation FlashUtil was downloaded onto the Co-Processor instead of RAMApp, the flash can be updated on the Co-Processor but no traffic can be run.
Recommended Action Remove any ixp1200_cp_firmware binaries in the flash and remove the card. If this does not work, load a version of IOS that has RAMApp bundled and not FlashUtil.
Error Message%IXP1200_CP-1-HB_STOP : [chars] Heartbeats stopped due to IXP crash
Explanation The IXP1200 complex has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP1200_CP-1-HPRXERR : Unexpected error received from CP, status [hex]
Explanation An unexpected error occurred during packet processing.
Recommended Action This message can occur occasionally during normal operation of the system. However, if it happens frequently, or is associated with traffic disruption, then make a note of the status value and 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. The 1FE-CP will most likely need to be replaced.
Error Message%IXP1200_CP-1-HPRX_CTX_MEM_POOL : Out of resources for [chars]. Requested [dec] compression-connections, obtained [dec]
Explanation More contexts were allocated to cRTP interfaces than memory can accommodate.
Recommended Action This message indicates more contexts were allocated using the ip rtp compression-conection command than there are 1fe-cp memory resources to accommodate. Reduce the number of compression-connections on some of the interfaces so the sum for all interfaces does not exceed 6000.
Error Message%IXP1200_CP-1-INITFAIL : CP : Initialization failed at [chars]
Explanation The CP device would not reset properly. Indicative of a hardware failure.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. The CP will need to be replaced.
Error Message%IXP1200_CP-1-IXP_CRASH : [chars] IXP crashed due to [chars]
Explanation The IXP1200 complex has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP1200_CP-1-ME_FAIL : [chars] MicroEngines lost heart beat
Explanation The MicroEngines have failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP1200_CP-1-NOHW : One Port Fast Ethernet With Co-processor Assist not present in system
Explanation You have entered a command which involves a One Port Fast Ethernet With Co-processor Assist back card, but none is present in the system.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. The CP will most likely need to be replaced.
Error Message%IXP1200_CP-1-POSTFAIL : [chars]: Power On Self Test failed, alert status [hex]
Explanation The Power On Self Test (POST) for the CP failed.
Recommended Action The CP must be replaced.
Error Message%IXP1200_CP-1-SA_FAIL : [chars] StrongArm lost heart beat
Explanation The StrongArm processor has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP1200_CP-1-UNEXPCMD : [chars]: Invalid command reply: expected [hex] received 0x[chars]
Explanation A command was sent to the Encryption AIM, and it's reply contained an unexpected reply code. The details of the failure depend upon the circumstances, but in all likelihood the Encryption AIM is faulty and should be replaced.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. The CP will most likely need to be replaced.
Error Message%IXP1200_CP-1-UNEXPECTEDEVENT : Process received unknown event [hex]
Explanation This message indicates that a ixp1200 specific process received an event it did not know how to handle.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. .
Error Message%IXP1200_CP-3-DEACTIVATED : bay [[dec]] deactivated
Explanation The port adapter is being deactivated because it failed to successfully complete initialization. Other messages in the log specify the exact cause of the failure.
Recommended Action If possible, correct any errors indicated by the other messages occurring at the time of this message. Verify that the port adapter is properly seated in the bay.
Error Message%IXP1200_CP-3-HB_FAILURE : 1FE-CP HeartBeat Lost from slot [dec]
Explanation The IXP1200 Heartbeat has gone away.
Recommended Action This is normal functionality if the 1FE-CP backcard was removed. If other Heartbeat errors are seen, then 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP1200_CP-3-IXP1200_CP_DRIVERKILL : Unexpected request to terminate: 1FE-CP driver process ([chars])
Explanation Unexpected termination of the 1fe-cp driver process.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP1200_CP-3-IXP_CRASHINFO_FAIL : Failed to write IXP debug information.
Explanation IXP debugging information could not be written.
Recommended Action The device on which the write was attempted is likely out of free space, or the write has encounterd some other error.
Error Message%IXP1200_CP-6-MULTDEV : Cannot support more than one 1 FE/Co-Processor
Explanation A second FE/Co-Processor was discovered present in the system. The 1 FE/Co-Processor software only supports a single 1 FE/Co-Processor. All other FE/Co-Processors installed will be ignored.
Recommended Action Remove one of the 1 FE/Co-Processor installed in the system.
Error Message%IXP1200_CP-6-OUT_OF_RESOURCES : [chars] cannot utilize Co-Processor. Co-Processor limited to [dec] interfaces.
Explanation The 1 FE/Co-Processor can only perform a hardware assist function on the number of interfaces displayed in the error message.
Recommended Action Unavailable.
Error Message%IXP1200_CP-6-STARTUP : [chars]: starting up
Explanation The specified One Port FE/Co-Processor has initialized successfully.
Recommended Action Informational message only. It occurs in normal operation.
IXP_MAP Messages
Error Message The following are ESF Network Processor Client Mapper messages.Error Message%IXP_MAP-3-ACR : [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A software programming error for the ACR ESF Network Processor Client Mapper has been detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IXP_MAP-3-ATOM : %s error detected: %s %s 0x%x 0x%x
Explanation A software programming error for the ATOM ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. Record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-CEM : [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A software programming error for the CEM ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If this message recurs, reset the affected device. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Record the output from the commands show tech and show log and provide this information to your technical support representative.
Error Message%IXP_MAP-3-CEMOUDP: [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A software programming error was detected related to the extended super frame (ESF) Circuit Emulation (CEM) over UDP ESF NP Client Mapper.
Recommended Action This software programming error is not considered fatal to the operation of the ESF NPs. The software is designed to detect and report the error condition. If the error persists, reset the affected device and 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP_MAP-3-DROP_BLOCK : %s error detected - 0x%x 0x%x %d %d
Explanation Error detected processing ESF Network Processor drop block allocations.
Recommended Action This is a software programming error. Record the Output from the following show commands: show tech show and log Provide this information to your technical support representative.
Error Message%IXP_MAP-3-EXMEM : %s %s error detected - %s (%d)
Explanation Error detected managing the external memory of a Network Processor.
Recommended Action This is a software programming error. Record the Output from the following show commands: show tech show and log Provide this information to your technical support representative.
Error Message%IXP_MAP-3-FRR_VLAN : Error detected: [chars] [chars] [hex] [hex]
Explanation A software programming error for the FRR Vlan ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IXP_MAP-3-HQF : %s error detected: %s %s 0x%x 0x%x
Explanation A software programming error for the HQF ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. Record the output from the following commands: show tech and show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-INITFAIL : Initialization Failed - %s: %s %s
Explanation Memory needed to service one or more Network Processors could not be initialized.
Recommended Action Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the following commands: show tech, show log . Provide this information to your technical support representative.
Error Message%IXP_MAP-3-INTF : %s error detected: %s %s 0x%x 0x%x
Explanation A software programming error for the Interface ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. Record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-IPSESS : [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A configuration error for the IP Sessions ESF Network Processor Client Mapper was detected.
Recommended Action This configuration error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If this message recurs, reset the affected device. Record the output from the following commands:show tech show log. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP_MAP-3-L2SRC : [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A configuration error for the L2SRC ESF Network Processor Client Mapper was detected.
Recommended Action This configuration error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If this message recurs, record the output from the command show tech show log. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP_MAP-3-L2TPV3 : [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A software programming error for the L2TPV3 ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If this message recurs, reset the affected device. Record the output from the commands: show tech show log. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP_MAP-3-LOCK_BLOCK : %s error detected - 0x%x %d %d %d
Explanation Error detected processing ESF Network Processor lock bit allocations.
Recommended Action This is a software programming error. Record the Output from the following show commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-LOCK_LIST : %s error detected - 0x%x %d %d %d
Explanation Error detected processing ESF Network Processor lock bit list allocations.
Recommended Action This is a software programming error. Record the Output from the following show commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-MAXEXCEED : ESF NP Mapper Max Services Exceeded - %s: %s %d
Explanation The maximum number ESF Network Processor Client Mapper services have been exceeded.
Recommended Action Change the configuration to reduce the number of services configured. If the error persists, record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-MPLSOGRE : %s error detected: %s %s 0x%x 0x%x
Explanation A software programming error for the MPLSOGRE ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. Record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-MPLSOMGRE : [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A software programming error for the MPLSOGRE ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IXP_MAP-3-MPLSOMGRE : [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A software programming error for the MPLSOGRE ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%IXP_MAP-3-NOMEM : Memory Allocation Failure - %s : %s(0x%x)
Explanation Memory required to service one or more Network Processors could not be allocated.
Recommended Action This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-NOMEM_S : Memory Allocation Failure - %s: %s %s
Explanation Memory required to service one or more Network Processors could not be allocated.
Recommended Action This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-NOTFOUND : ESF NP Client Mapper - %s: %s 0x%x
Explanation The ESF Network Processor Client Mapper could not locate a required software element.
Recommended Action Try to reload the IOS image on the affected card or platform. If the error persists, record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-NPMEM : [chars] [chars] error detected
Explanation Error detected with external memory of a ESF Network Processor.
Recommended Action This is a software programming error. Copy the message exactly as it appears on the console or in the system log. Enter the show tech and show log commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP_MAP-3-NPUNKNOWN : Unsupported NP - %s: %s %s
Explanation An unsupported Network Processor has been detected.
Recommended Action Verify that the correct IOS image is loaded on the affected card or platform for the configured features. If the error persists, record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-PPPOESESS : [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A configuration error for the PPPOE Sessions ESF Network Processor Client Mapper was detected.
Recommended Action This configuration error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If this message recurs, record the output from the following commands: show tech show log. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP_MAP-3-QOS : %s error detected: %s %s 0x%x 0x%x
Explanation A software programming error for the QOS ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If the error persists, reset the affected device. Record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-QOS_CONFIG : %s error detected: %s %s 0x%x 0x%x
Explanation A configuration error for the QOS ESF Network Processor Client Mapper was detected.
Recommended Action This configuration error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. Change the configuration to correct the QOS ACL configuration problem. If the error persists, record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-SACL : [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A software programming error for the Security ACL ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If this message recurs, reset the affected device. Copy the message exactly as it appears on the console or in the system log. Enter the show tech and show log commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP_MAP-3-SACL_CONFIG : [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A configuration error for the Security ACL ESF Network Processor Client Mapper was detected.
Recommended Action This configuration error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. Change the configuration to correct the QOS ACL configuration problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech and show log commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP_MAP-3-STATS_BLOCK : %s error detected - 0x%x 0x%x %d %d %d
Explanation Error detected processing ESF Network Processor stats block allocations.
Recommended Action This is a software programming error. Record the Output from the following show commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-TCAM : [chars] error detected: [chars] [chars] [hex] [hex]
Explanation A software programming error for the NetLogic NSE TCAM was detected.
Recommended Action This configuration error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. Change the configuration to correct the QOS ACL configuration problem. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech and show log commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IXP_MAP-3-VPLS : Error detected: %s %s 0x%x 0x%x
Explanation A software programming error for the VPLS ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If the error persists, record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-3-WRED : %s error detected: %s %s 0x%x 0x%x
Explanation A software programming error for the WRED ESF Network Processor Client Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. If the error persists, record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-4-CONNECTION_EXCEED : The number of connections has reached the capacity of the line card ([dec]).
Explanation The total number of connections has reached the maximum number supported by the line card. The line card is running out of connection resources.
Recommended Action This warning is not fatal to the operation of the ESF Network Processors. It indicates that line card cannot handle more connections because it has reached a resource limitation.
Error Message%IXP_MAP-4-IPC_FAIL : ESF IPC Command failed - %s NP=%s (cmd=%d me=%d rc=%d)
Explanation An IPC command sent to the ESF Network Processor failed.
Recommended Action This error indicates a possible problem with the Network Processor hardware or microcode. Reload the affected HW to clear the condition.If the error persists, record the output from the following commands: show tech, show log. Provide this information to your technical support representative.
Error Message%IXP_MAP-4-QUEUE_LIMIT_EXCEED : Warning: Line card default queue-limit exceeds the maximum transmit packet buffers ([dec]). To ensure high priority traffic is not dropped, apply a QOS policy on each interface and adjust the queue-limit so that the total of the queue-limits on this line card is less than the maximum transmit packet buffers.
Explanation An error for the HQF ESF Network Processor Client Mapper was detected. The total of the default queue-limits exceeds the maximum transmit packet buffers for this line card. Under high traffic conditions, the line card might run out of packet buffers and drop high priority traffic.
Recommended Action This configuration error is not considered fatal to the operation of the ESF Network Processors. The software is designed to detect and report the error condition. Apply the QOS policy configuration in the output direction of each interface. Adjust the queue-limit so that the total of the queue-limits on this line card is less than the maximum transmit packet buffers. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show policy-map interface command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. KEYMAN Messages
Recommended Action The following are key string encryption messages.
Error Message%IXP_MAP-4-STUCK : Client ID([hex], [hex]) not ready on [chars]
Explanation During reset of the ESF Network Processor, one or more Network Processor Clients had not completed stop processing.
Recommended Action The system should still operate normally, however, statistics or state collected before the ESF Network Processor was reset might have been lost. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech and show log commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
KEYSTORE Messages
Error Message%KEYSTORE-3-BAD_MAGIC : Bad magic number [hex] in software keystore file "[chars]".
Explanation Keystore data file appears to have been corrupted. Keys can not be retrieved from persistent memory.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-1-HW_KS_DEFECTIVE : The CTS hardware keystore asic is defective and must be replaced.
To run CTS in the meantime, please configure "cts keystore emulation"
and re-configure cts credentials. If no action is taken, all CTS
authentication and authorization operations will fail.Explanation The CTS hardware keystore on the switch has failed. Since CTS credentials are stored in the keystore, this means that CTS authentication and authorization operations will fail. The supervisor card should be returned to Cisco for rework. If it is not convenient to do so at this time, you can configure the switch to use software keystore emulation. After you have enabled software keystore emulation, please re-configure cts credentials to populate the software keystore.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-IFS_OPEN_R : Failed to open file "[chars]" for reading software keystore. ([chars])
Explanation An error occurred while opening the keystore file for reading.CTS keys could not be retrieved.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-IFS_OPEN_W : Failed to open file "[chars]" for writing software keystore. ([chars])
Explanation An error occurred while opening a file for persistent storage.CTS keys could not be saved to persistent storage.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-IFS_READ : An error ([chars]) occurred while reading from the software keystore file.
Explanation CTS keys could not be retrieved from persistent storage.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-IFS_WRITE : An error occurred while writing to the software keystore file.
Explanation CTS keys could not be saved to persistent storage.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-IPCNOCONN : No IPC communication path to peer available for keystore [chars].
Explanation No IPC connection to the peer was available for keystore redundancy messages. This means that any updates made to the ACTIVE keystore cannot be pushed to the STANDBY keystore.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-IPC_NO_PROC : Could not create a process to receive keystore redundancy messages.
Explanation An error occurred while attempting to create a process to handle the incoming keystore redundancy messages. Updates made to the active keystore cannot be pushed to the standby keystore.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-IPCOPEN : Failed to open IPC port to peer for keystore redundancy: [chars]
Explanation An error occurred while trying to open an Inter-Process Communication port for keystore redundancy messages. Updates made to the active keystore cannot be pushed to the standby keystore.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-IPCPORT : Failed to create IPC port ([chars]) for keystore redundancy. [chars].
Explanation An error has occurred while attempting to create an Inter-Process Communication (IPC) port. Updates made to the active keystore cannot be pushed to the standby keystore.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-IPCSEND : IPC send error ([chars]) while sending [chars].
Explanation An error occurred while sending an Inter-Process Communication (IPC) message to the peer during a keystore redundancy operation. Updates made to the active keystore cannot be pushed to the standby keystore.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-ISSU_INCOMPAT : Standby incompatible for SSO.
Explanation The image on the standby failed ISSU message version negotiation. As a result, we will not be able to sync keystore updates to it and so it is disallowed from reaching "hot" standby status in SSO mode.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-NO_KEYSTORE : CTS hardware keystore is defective and software emulation is not enabled.
Explanation The Cisco TrustSec (CTS) hardware keystore on the switch must to be replaced. Until the replacement is complete, you can configure the switch to use a software keystore emulation and populate the software keystore by reconfiguring the CTS credentials.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KEYSTORE-3-UNEXPECTED_EOF : Unexpected end of file while reading software keystore "[chars]".
Explanation The keystore data file is truncated. One or more keys cannot be retrieved from persistent memory.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
JAGGER Messages
Error Message%JAGGER-2-ASIC_INIT : Failed to initialize [chars] ASIC
Explanation Most likely it is a hardware problem.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-2-BADPABAY : Out of range PCI Port Adaptor bay [dec]
Explanation The software specified an out-of-range port adapter bay.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-2-PCIERROR : Fatal PCI Error [chars] seen on PCI Bus [dec]
Explanation A Fatal PCI Error was detected on the PCI bus. Most likely it is a hardware problem.
Recommended Action If this message recurs, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-3-ERROR : [chars]
Explanation Informational message.
Recommended Action No action is required.
Error Message%JAGGER-3-IMAGESSAME : The rommon images are the same. No rommon upgrade is required.
Explanation Informing the user that a rommon upgrade is not carried out because the rommon images are the same.
Recommended Action Informational message only. No action is required.
Error Message%JAGGER-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The line card failed to allocate a buffer for communication with the Route Processor (Draco).
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-3-IPCPORTFAIL : Failed to open IPC port '[chars]' [chars]
Explanation The line card failed to open a port for communication with the Route Processor (Draco).
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The line card failed to send a message to the Route Processor (Draco).
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-3-LONGSTALL : Long bus stall ([int] ms), check for improperly seated cards
Explanation This message indicates that a stall was detected, but the backplane stall was longer than expected.
Recommended Action Ensure all cards are firmly seated. If the problem recurs, it may indicate a hardware failure. 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-3-MEDUSAFATAL : Medusa Fatal Error. Resetting ASIC.
Explanation The JAGGER Medusa ASIC received a FATAL ERROR.
Recommended Action No action is required if traffic recovers. Otherwise, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-3-MEMORYALLOCERR : unable to allocate memory
Explanation The memory allocation for the .srec file failed.
Recommended Action Ensure that there is enough memory available.
Error Message%JAGGER-3-NOFABRICPROCESS : No fabric process created
Explanation The JAGGER Santa Ana Fabric interface does not have a link process running: the system failed to create this process. This module will not support the fabric interface.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-3-OPENFILEERR : Unable to open file
Explanation The fopen failed to open the file for the rommon upgrade.
Recommended Action Ensure that the approporiate SREC file is present in bootflash.
Error Message%JAGGER-3-READFILEERR : Unable to read file
Explanation The read operation of the file failed.
Recommended Action Ensure that the approporiate SREC file is present in bootflash.
Error Message%JAGGER-3-SRECDECODEERR : unable to decode SREC file
Explanation The decode from the srec file to bin file failed.
Recommended Action Ensure that the approporiate SREC file is present in bootflash.
Error Message%JAGGER-3-UPGRADEFAILERR : Rommon upgrade failed.
Explanation The rommon upgrade has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-4-BUSSTALL : Constellation BUS Stall detected
Explanation This message indicates that a stall was detected on the Constellation Bus probably due to some OIR activity on the Bus.
Recommended Action Informational message only. No action is required.
Error Message%JAGGER-4-CMM_OUT_OF_BUFFERS : Out of Buffers: pool [chars] cache end [dec]
Explanation The Cisco Media Gateway Controller Manager has run out of buffers.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%JAGGER-4-FABRICCRCERRORS : [dec] Fabric crc error events in 100ms period
Explanation The JAGGER Medusa Fabric interface encountered more CRC errors than the Supervisor CRC error threshold allows.
Recommended Action The line card has notified the Supervisor and the fabric interface will be resynchronized. No action is required.
Error Message%JAGGER-4-FABRICSYNCERRS : [dec] Fabric sync error events in 100ms period
Explanation The JAGGER Santa Ana Fabric interface encountered more sync error events than the Supervisor sync error threshold allows.
Recommended Action The line card has notified the Supervisor and the fabric interface will be resynchronized. No action is required.
Error Message%JAGGER-4-LOGMSGTOOBIG : Logger message length exceeds max, [int] bytes
Explanation The line card attempted to send a large message to the Route Processor (Draco).
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-4-LYRAPATCH : Lyra Patch reset sequence invoked.
Explanation The Lyra patch reset sequence is being invoked.
Recommended Action No action is required if traffic recovers. Otherwise, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-4-LYRASEQERR : Lyra Sequence Error. Resetting port ASICS.
Explanation The Lyra ASIC detected a sequence error.
Recommended Action No action is required if traffic recovers. Otherwise, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JAGGER-4-UPGRADECOMPLETE : rommon upgrade completed. Please ensure that a host image is present in bootflash: and power cycle the CMM.
Explanation Informational message to inform the user that the rommon upgrade has been completed. The user has to power cycle the CMM.
Recommended Action Informational message only. No action is required.
Error Message%JAGGER-5-MEDUSAMODECHANGE : MEDUSA Mode changed to [chars]
Explanation The JAGGER Medusa device has changed the switching bus mode.
Recommended Action The Supervisor has changed the line card Medusa mode. No action is required.
Error Message%JAGGER-6-INFO : [chars]
Explanation Informational message.
Recommended Action No action is required.
JETFIRE Messages
Error Message%JETFIRE_SM-1-INITFAIL : NM slot [dec]: PCI device [dec] initialization failed
Explanation The initialization of the NAM Sensor network module has failed.
Recommended Action Power down, reseat the interface card, and reboot the system. If this message recurs, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JETFIRE_SM-1-INVALID_IFINDEX : ifIndex value [dec] is a four byte value which does not fit in 3 byte src mac field.
Explanation If ifIndex value is more than 3 bytes, should not encode this value into 3-byte SRC MAC field.This will give unpredictable results.
Recommended Action If this message recurs, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%JETFIRE_SM-1-MULTIPLEREGISTRATION : NM slot [dec]: PCI device [dec] multiple NAM service modules not allowed
Explanation Another NAM Sensor service module is already installed.
Recommended Action Power down, remove the extra cards, and reboot the system. If this message recurs, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KERBEROS-3-FORKFAIL : Failed to fork process for %s.
Explanation Quite likely, we ran out of memory. Other explanations are possible.
Recommended Action If this message recurs, call your technical support representative for assistance.
KEYMAN Messages
The following are Keystring encryption messages.
Error Message%KEYMAN-4-KEYSTR_BAD_CRYPTO : Bad encrypted keystring for key id [dec].
Explanation The system could not successfully decipher an encrypted keystring. The keystring could have been corrupted during system configuration.
Recommended Action Enter the key-string command again and reconfigure the keystring.
Error Message%KEYMAN-4-KEYSTR_CRYPTO_TYPE : Type [dec] encryption unknown. Interpreting keystring as literal
Explanation The format type indicated in the message text was not recognized by the system. A keystring format type value of 0 (unencrypted keystring) or 7 (hidden keystring), followed by a space, can precede the actual keystring to indicate its format. An unknown type value can be accepted, but the system considers the keystring as being unencrypted.
Recommended Action Use the correct format for the value type or remove the space following the value type.
KINEPAK Messages
Error Message%KINEPAK-3-BADCB : Unexpected DSIP data callback for voice channel
Explanation An unexpected software event has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%KINEPAK-3-CONTIGUOUS : Contiguous packet sent for transmit
Explanation A software error occurred resulting in an unexpected packet being set up for transmission and the packet was dropped.
Recommended Action If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KINEPAK-3-ERR_DSPWARE_DNLD : dsp%d cannot download dspware %s
Explanation A software error occurred resulting in failure to download a dspware component.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error MessageExplanation A software error occurred resulting in failure to download a dspware component.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KINEPAK-3-ERR_DSPWARE_IMG : Cannot find dspware [chars] component
Explanation A software error has occurred and has caused a failure to download a DSP component.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%KINEPAK-3-NODSPENTRY : No dsp entry in dsp list
Explanation The software structure that is used to maintain the DSP instance is missing.
Recommended Action If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KINEPAK-3-NOMAILELEMENTS : Cannot create message buffer
Explanation A software error occurred resulting in failure to create a message buffer to send messages among processes.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KINEPAK-3-NOPARTICLE : No particle available for ingress packet
Explanation A software error occurred resulting in failure to obtain a particle to hold an ingress packet from DSP.
Recommended Action If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KINEPAK-3-NOPARTICLEPOOL : Cannot create particle pool
Explanation A software error occurred resulting in failure to create a particle pool to receive packets from DSP.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%KINEPAK-3-NORXPAK : Static receive paktype unavailable
Explanation A software structure was found in an unexpected state during run-time for the indicated DSP.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
L2 MEssages
Error Message%L2-3-DUP_REG : L2 Forwarding Engine: [chars] Attempt to program duplicate MAC address
Explanation Attempt to program duplicate MAC address in the match registers.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2-4-NOBUF : Buffer alloc failed: [chars] [dec]
Explanation Buffer allocation has failed. The system is running out of buffers.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2-4-NOMEM : Malloc failed: [chars] [dec]
Explanation Memory allocation has failed. The system is running out of memory.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2-4-QUEERR : Que Full Error: [chars] [chars]
Explanation Can not enqueue due to lack of system resources
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. .
Error Message%L2CAC-5-VC_BW_NOT_ENOUGH : VC [dec]/[dec] bandwidth is not enough to add this Trunk port(channel). Total bandwidth is [dec] cps, but requires [dec] cps to add this Trunk port(chanel)
Explanation The VC bandwidth is not enough. The bandwidth should be increased.
Recommended Action To support this call, the VC bandwidh the sustained cell rate has to be increased to accomidate the new calls.
Error Message%L2CTRL-3-ADD_REGISTRY_FAILED : Subsystem [chars] fails to add callback function [chars]
Explanation Other subsystem must have mistakenly add its own callback functions. This syslog is for debugging purpose.
Recommended Action No action is required.
Error Message%L2MCAST_SNOOP-4-FORCE_MAC_FORWARDING : Force to do MAC-based forwarding becuase an IP multicast DMAC is configured while IP-based forwarding is enabled on this VLAN %d. Suggest to configure static multicast group instead.
Explanation Configuring multicast group address can avoid ddress aliasing problem
Recommended Action Either change to MAC-based forwarding using command 'multicast snooping lookup mac' or configure group ip address using command 'ip/ipv6 igmp/mld snooping static interface '.
Error Message%L2MCAST_SNOOP-4-VLAN_STATE_LIMIT_ALREADY_EXCEEDED : VLAN ([dec]) limit is already exceeded after decreasing the limit.L2 multicast snooping must be disabled and enabled for lowerlimit to take effect.
Explanation After the maximum state entry limit is decreased, the number of Layer 2 (L2) multicast snooping states has exceeded the upper limit. To make the smaller limit take effect, snooping must be disabled on the VLAN and then reenabled.
Recommended Action Disable and reenable L2 multicast snooping on the VLAN.
Error Message%L2MCAST_SNOOP-4-VLAN_STATE_LIMIT_DEC : VLAN (%d) limit changed from %d to %d. L2 multicast snooping must be disabled and enabled for this change to take effect.
Explanation When the maximum state entry limit is decreased, the number of L2 multicast snooping states might now be greater than the limit. In order to make the smaller limit take effect, snooping must be disabled on the VLAN and then re-enabled.
Recommended Action Disable and re-enable L2 multicast snooping on the VLAN.
Error Message%L2MCAST_SNOOP-4-VLAN_STATE_LIMIT_EXCEEDED : Failed creation of GIP/SIP entry, exceeded VLAN (%d) limit (%d) of IPv%d state entries.
Explanation Maximum state entry limit is exceeded and thus no new (*,G)/(S,G) state entries can be created by L2 multicast snooping. Receivers for these GIP/SIP entries may not be able to receive traffic
Recommended Action Reduce the number of (*,G)/(S,G) entries in this VLAN or increase the state limit. Another alternative is to configure static entries for those groups that should not be subjected to the state limit.
Error Message%L2MCAST_SNOOP-6-ETRACK_LIMIT_EXCEEDED : %s snooping on VLAN %d was trying to allocate more explicit-tracking entries than what allowed global limit (%d) or the limit on the VLAN (%d)
Explanation The allocation of explicit-tracking entries is bounded to avoid the IGMP/MLD snooping hogs the system resources
Recommended Action Reduce the number of (s,g) channelds or number of receivers. When explicit- tracking database is overflow, new membership for any channel will not be tracked and it may cause high leave latency when those members leave a channel. Another alternative is to increase the limit from the config mode through the CLI 'ip/ipv6 igmp/mld snooping explicit-tracking-limit ' globally and on the VLAN. But note increasing the value of max-entries could create crash due to high use of system resources.
Error Message%L2MCAST_SNOOP-6-RESTORE_IP_FORWARDING : IP-based forwarding is restored on VLAN %d
Explanation The static multicast MAC are all removed. Restore IP-based forwarding
Recommended Action The message is for information only.
Error Message%L2MC_QUERIER-4-NO_IP_ADDR_CFG : The [chars] querier cannot send out General Query messages in VLAN [dec] because there is no IP address configured on the system.
Explanation An IP address for the Internet Group Management Protocol (IGMP)/Multicast Listener Discovery (MLD) querier should be specified either at the global level or at the per-VLAN level.
Recommended Action Configure a source IP address for the IGMP/MLD querier.
Error Message%L2MC_QUERIER-4-PIM_ENABLED : The [chars] querier is operationally disabled in VLAN [dec] because PIM has been enabled on the SVI.
Explanation Protocol Independent Multicast (PIM) has been detected on the Smart Virtual Interface (SVI). The Internet Group Management Protocol (IGMP)/Multicast Listener Discovery (MLD) querier function should not be operational when PIM is enabled on the SVI.
Recommended Action Ensure that PIM is disabled on the SVI.
Error Message%L2MC_QUERIER-4-SNOOPING_DISABLED : The [chars] querier is operationally disabled in VLAN [dec] because [chars] snooping has been disabled in this VLAN.
Explanation The Internet Group Management Protocol (IGMP)/Multicast Listener Discovery (MLD) snooping has been disabled on this VLAN. The IGMP/MLD querier function should not be operational when IGMP/MLD snooping is disabled.
Recommended Action Ensure that IGMP/MLD snooping is enabled globally and on the VLAN specified in the message.
Error Message%L2MC_QUERIER-4-SNOOPING_DISABLED : The [chars] querier is operationally disabled in VLAN [dec] because [chars] snooping has been disabled in this VLAN.
Explanation The The Internet Group Management Protocol (IGMP)/Multicast Listener Discovery (MLD) snooping has been disabled on this VLAN. The IGMP/MLD querier function should not be operational when IGMP/MLD snooping is disabled.
Recommended Action Ensure that IGMP/MLD snooping is enabled globally and on the VLAN specified in the message.
Error Message%L2MC_QUERIER-6-SNOOPING_ENABLED : The [chars] querier is now operationally enabled in VLAN [dec] because [chars] snooping is no longer disabled.
Explanation The Internet Group Management Protocol (IGMP)/Multicast Listener Discovery (MLD) snooping has now been enabled and the IGMP/MLD querier function is now enabled.
Recommended Action No action is required.
Error Message%L2R-4-DROP_PAK : l2r uid %d drop packet (type %x) from/to uid %d when %s
Explanation drop packet.
Recommended Action contact your technical support representative.
Error Message%L2R-4-FRAGMENT_ERROR : fragmentation error (s_uid = %x) received
Explanation An internal software error occurred.
Recommended Action Contact your technical support representative.
Error Message%L2R-4-INVALIDMSG : Invalid L2R message (msg_type %x) received from UID %d at line %d
Explanation An internal software error occurred.
Recommended Action Contact your technical support representative.
Error Message%L2TM-3-ACCESS_ERR : Tcam access failed while [chars]
Explanation The system has failed to read from or write to TCAM.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2TM-7-INTERNAL_ERR : Internal error: [chars]
Explanation An internal error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2TP-3-CRITICAL : %s
Explanation An critical event has been processed by the L2TP subsystem.
Recommended Action No action is required.
Error MessageExplanation An illegal event has been processed by the L2TP subsystem.
Recommended Action No action is required.
Error Message%L2TP-3-ILLEGAL : [chars]: [chars]
Explanation An illegal event has been processed by the L2TP subsystem.
Recommended Action No action is required.
Error Message%L2TP-5-IGNOREICMPMTU : Ignoring received ICMP Type 3 Code 4, due to pmtu min or max setting
Explanation An ICMP Type 3 Code 4 (fragmentation needed and DF set) packet has been received. This packet has specified a Next-Hop MTU that is smaller or greater than the current minimum or maximum path MTU discovery mtu value. The ICMP packet has been ignored and the MTU has not been changed.
Recommended Action If you want the ICMP packet to be accepted and used to decrease or increase the MTU then use the vpdn pmtu min command to decrease the minimum MTU allowed and enter the vpdn pmtu max command to increase the maximum MTU that is allowed. The minimum value specified is the minimum MTU that is allowed, and the maximum value specified is the maximum MTU that is allowed.
Error Message%L2TPV3_NP_CLIENT-3-INFO : [chars]
Explanation L2TPv3 NP Client failed to initialize properly which will result in improper operation of l2tpv3 feature.
Recommended Action Try to reload the IOS image on the affected card or platform. If this message recurs, record the output from the following commands: show tech show log. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2TPV3_NP_CLIENT-3-NOMEM : [chars]
Explanation L2TPv3 NP Client failed to initialize properly which will result in improper operation of l2tpv3 feature.
Recommended Action This error might indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Try to reload the IOS image on the affected card or platform. If this message recurs, record the output from the following commands:show tech show log. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2TPV3_NP_CLIENT-4-WARN : [chars] [dec] [chars]
Explanation L2TPv3 Entry could not be added because Entry passed is invalid.
Recommended Action Try to reload the IOS image on the affected card or platform. If this message recurs, record the output from the following commands: show tech show log. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L2TP_HA-3-ISSU : [chars]: [chars]
Explanation A L2TP ISSU error has occurred.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2TP_HA-3-SYNC : [chars]: code [dec]
Explanation An error has occurred when syncing L2TP state to the Standby Route Processor. This may affect Non-Stop Forwarding capability on L2TP-based interfaces during and after switchover until the state is recovered through normal protocol operation.
Recommended Action Reset the standby processor to attempt the sync again.
Error Message%L2TUN-3-ILLEGAL : %s
Explanation An illegal event has been processed by the L2TUN subsystem.
Recommended Action No action is required.
Error Message%L2_AGING-0-CREATEQFAIL : Failed to create L2-AGING queue
Explanation The system failed to create the Layer 2 aging queue. Requests for aging MAC addresses are enqueued in this queue. Because of this condition, line cards might have inconsistent information. If the aging queue cannot be created, the supervisor (or line cards) will provide a crashdump and reload.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_AGING-2-DEC_EN_FAIL : Failed to initialize Distributed EtherChannel
Explanation One or more resources required for Distributed Etherchannel operation is in use
Recommended Action Please remove the monitor session reserved for service modules using the command 'no monitor session servicemodule' and try again.
Error Message%L2_AGING-2-SIG_INST_FAIL : %s: Failed to install signal handler
Explanation L2-AGING : A signal handler could not be installed for the process that involved Layer 2 aging
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_AGING-2-SPAWNFAIL : [chars] task spawn failed
Explanation An L2-aging task spawn has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_AGING-4-ENTRY_DNLDFAIL : Slot [dec]: Download entries failed, reason [chars]
Explanation The download of aging entries to the line card has failed. Because of this condition, line cards might have inconsistent information.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_AGING-4-INPROGRESS : Download already in progress to slot [dec]
Explanation An error has occurred in a Layer 2 aging download process. A download was requested while the Layer 2 aging download process was already in progress to the slot specified in the error message.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_AGING-4-INVSLOT : Download to invalid slot [dec] requested
Explanation An L2-aging internal error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_AGING-4-MISSING_SLOTNO : Cannot get the slot to download l2 entries
Explanation An L2-aging download process error has occurred. The slot number could not be obtaned, and the L2 entries could not be downloaded.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_AGING-4-UNKMESG : [chars]: received unknown message [dec]
Explanation An internal error has occurred. There might be a mismatch in image versions.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_API-5-INVADDR : Invalid static entry address computed. Base [hex], Offset [hex], rc [chars]
Explanation The system has detected an internal software error.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_API-5-INVOPER : Invalid operation [dec]
Explanation An invalid operation was requested.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_API-5-MAC_REPLACE : Mac [enet], Vlan [dec] replaced with Mac [enet], Vlan [dec]
Explanation A lower priority MAC entry had to be removed from the MAC table in order to add a higher-priority MAC entry.
Recommended Action No action is required.
Error Message%L2_API-5-RETADDR : Unsupported action.
Explanation An internal error has occurred. An unsupported API has been invoked.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_API-5-SENDFAIL : ICC Send failed. Reason [chars]
Explanation An L2-API message send to the line cards has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. L2_APPL Messages
Recommended Action The following are Layer 2 application messages.
Error Message%L2_APPL-0-TASK_SPAWN_FAIL : Failed to spawn task '[chars]'
Explanation The task indicated in the message has failed to spawn.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_APPL-4-MAC_MOVE : Host [enet] is flapping between port [chars] and port [chars]
Explanation A host has been flapping between ports.
Recommended Action Check the network for possible loops.
Error Message%L2_APPL-4-UNKMESG : Unknown received message [dec]
Explanation An internal error has occurred. There might be a mismatch between the actual and expected Cisco IOS image versions.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_APPL-5-MAC_USAGE : MAC usage for EARL %d is currently %d%%
Explanation The utilization of the L2 Forwarding table of the Enhanced Address Recognition Logic is greater than threshold set by the user. The EARL Forwarding Table exceeding the utilization threshold and the current utilization are specified in the error message text.
Recommended Action No action is required.
Error Message%L2_ASIC-0-FATAL_INTR : L2 Forwarding Engine: fatal interrupt: int status 0x%x, int mask 0x%x
Explanation Critical interrupts indicating EARL may not be functioning anymore
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_ASIC-1-SCP_Q_CREATE_FAIL : Failed to create L2 Forwarding Engine SCP queue
Explanation SCP queue creation failed.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_ASIC-1-TASK_CREATE_FAIL : Failed to create L2 Forwarding Engine fatal interrupt patch task
Explanation Task creation failed.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_ASIC-1-THRO_RES_ALLOC_FAIL : Failed to allocate throttle resource
Explanation throttle resource allocation failed.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_ASIC-2-L2L3_SEQ_ERR : L2 Seq #0x%x, L3 Seq #0x%x, L2L3 Mismatch seq #0x%x
Explanation L2 Forwarding Engine L2-L3 Seq. error occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_ASIC-2-PARITY_ERR : L2 Forwarding Engine: parity intr #%d: address 0x%x, Data: 0x%x, 0x%x, 0x%x, 0x%x
Explanation Parity error detected while accessing the Forwarding table
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_ASIC-2-RESET_LC : Resetting the linecard %d. Error code %d
Explanation Failed to receive SCP response or received with status not-ok
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_ASIC-2-SEQ_ERR : %s seq. error: Seq #%x, Intr. status #%x, Cntrl1 #%x, Cntrl2 #%x
Explanation L2 Forwarding Engine sequence error occurred
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_ASIC-4-INV_MSG : Received %s message from slot %d
Explanation Message received from invalid linecard
Recommended Action Please report this to the Cisco tech support
Error Message%L2_ASIC-4-INV_REG : L2 Forwarding Engine: Attempt to %s invalid register
Explanation Internal error. Attempt was made to read/write to invalid L2 Forwarding Engine register
Recommended Action File a ddts report or report the messages seen to the Cisco technical support representative.
Error Message%L2_CTRL-4-BLOCKFAIL : l2 throttle blocking task failed
Explanation A Layer 2 throttle blocking task has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_CTRL-4-UNKMESG : Unknown received message [dec]
Explanation An internal error has occurred. There might be a mismatch in the image versions.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_DIST_LRN-4-NO_INIT : Initialization failed: [chars]
Explanation The L2 distributed learning process could not be initialized.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_DIST_LRN-4-NO_MAC_RDRT : MAC redirect initialization failed: [chars]
Explanation Initialization of MAC redirection has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_DIST_LRN-4-NO_MEM : Malloc failed: [chars]
Explanation The system is running out of memory.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_DIST_LRN-4-PAK_BLD_FAIL : [chars] Unable to build L2 Dist Lrn packet
Explanation The system is unable to build the L2 distributed learning packet.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_DIST_LRN-6-BUFFER_OVERRUN : Buffer Overrun: [chars]
Explanation The L2 distributed learning process has overflowed the buffer.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_DIST_LRN-6-NO_LRN : Unable to propogate L2 new learn at addr [hex]
Explanation The system is temporarily unable to propagate a new Layer 2 table entry to other line cards.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_DIST_LRN-6-NO_PKT_SEND : Unable to send L2 Dist Lrn packet: [chars]
Explanation The system is unable to send the L2 distributed learning correction packet.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_MAC-4-ADDMACFAIL : User static MAC %e (vlan %d) cannot be installed. Reason: %s
Explanation A user requested static MAC address cannot be installed
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_MGR-2-MGR_SPAWNFAIL : Failed to spawn L2-MGR task -- DFC linecards will affected
Explanation The system failed to spawn the Layer 2 manager task, possibly causing the line cards to have inconsistent information.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_MGR-2-SPAWNFAIL : [chars] task spawn failed
Explanation An attempt to spawn the Layer 2 manager task has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_MGR-4-BADVLAN_DNLDFAIL : Slot [dec]: Download Bad vlan failed, reason [chars]
Explanation An attempt to download data to the line card has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_MGR-4-ENTRY_DNLDFAIL : Slot [dec]: Download entries failed, reason [chars], entries [dec]/[dec]
Explanation An attempt to download static Layer 2 entries to the line card has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_MGR-4-INPROGRESS : Download already in progress to slot [dec]
Explanation A processing error occurred during the download of Layer 2 manager.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_MGR-4-INVSLOT : Download to invalid slot [dec] requested
Explanation An internal error occurred during the download of Layer 2 manager.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_MGR-4-MISSING_SLOTNO : Cannot get the slot to download l2 entries
Explanation A processing error occurred during the download of Layer 2 manager.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_MGR-4-UNKMESG : Unknown received message [dec]
Explanation An internal error has occurred. There might be a mismatch in image versions.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_THROTTLE-4-BLOCKFAIL : l2 throttle blocking task failed
Explanation The L2-THROTTLE blocking task has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%L2_THROTTLE-4-UNKMESG : Unknown received message [dec]
Explanation An internal error has occurred. There might be a mismatch in image versions.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
L3MM Messages
Error Message%L3MM-4-AP_DB_ADD : Failed to add AP to DB { AP : %e, %i}
Explanation The L3MM failed to add the entry for the specified AP into the AP database
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L3MM-4-AP_DB_DEL : Failed to delete AP from DB { AP : %e, %i}
Explanation The L3MM failed to delete the entry for the specified AP from the AP database
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L3MM-4-DUP_AP_IPADDR : AP %e is requesting ip %i which is being used by another AP
Explanation The L3MM detected that an access point requested an IP address that is being used by another access point in the network.
Recommended Action Change the IP address of one of the two access points.
Error Message%L3MM-4-INIT_FAIL : Initialization failure; reason: %s
Explanation The L3MM failed to initialize due to the specified reason
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L3MM-4-MALLOC_FAIL : Memory allocation failure %s
Explanation The L3MM failed to allocate memory which was needed to perform a given operation and/or respond to an event
Recommended Action Increase the memory on the RP of the supervisor.
Error Message%L3MM-4-MN_IPDB_ADD : Failed to add MN to MN DB { MN : %e, %i}
Explanation The L3MM failed to add the entry for the specified MN into the MN IP database
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L3MM-4-MN_IPDB_DEL : Failed to delete MN from IP DB { MN : %e, %i}
Explanation The L3MM failed to delete the entry for the specified MN from the MN IP database
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L3MM-4-MN_MACDB_ADD : Failed to add MN to MAC DB { MN : %e, AP : %i }
Explanation The L3MM failed to add the entry for the specified MN into the MN MAC database
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L3MM-4-MN_MACDB_DEL : Failed to delete MN from MAC DB { MN : %e, %i, AP : %i, WNID : %d }
Explanation The L3MM failed to delete the entry for the specified MN from the MN MAC database
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%L3MM-5-WLAN : Wireless LAN Module in slot %d is %s
Explanation The L3MM detected a change in the state of the Wireless LAN module in the specified slot. If the module is now on line, L3MM starts accepting access-point and mobile-node registrations from the WDS on the module. If the module is now off line, L3MM purges all access points and mobile nodes received from the module.
Recommended Action No action is required.
Error Message%L3MM-5-WLAN_COMM_ABORT : Communication with Wireless LAN Module in slot %d aborted (%s)
Explanation The Layer 3 Mobility Manager detected communication failure with the Wireless LAN module specified in the error message above, and will respond as if the module went offline by purging its access point and mobile node databases. However, the module will not be reset by the Layer 3 Mobility Manager
Recommended Action No action is required.
Error Message%L3MM-5-WLAN_PWR_DN : Wireless LAN Module in slot %d will be powered down, another module is already active
Explanation The L3MM detected a Wireless LAN module trying to come online, while another module was already functional as the active Wireless LAN module. The L3MM does not support more than one Wireles LAN module online in the chassis at a given time, which is why this module will be powered down.
Recommended Action No action is required.
Error Message%L3TCAM-3-SIZE_CONFLICT : [chars] requires enabling extended routing
Explanation The TCAM entry has not been configured to enable extended routing. In order to support this feature, it is required that the TCAM entry be configured to enable extended routing.
Recommended Action Modify the Switch Database Management template so that the switch is enabled to support the 144 bit Layer 3 TCAM. Enter the sdm prefer extended-match, sdm prefer access extended-match, or sdm prefer routing extended-match command in global configuration mode, then reload the switch by entering the reload command in privileged EXEC mode.
Error Message%L3TCAM-3-TOO_MANY_VRF : Exceed the maximum number of VRF allowed
Explanation The number of VPNs has exceeded the maximum number of VPNs that are allowed in the VPN routing and forwarding table on this hardware platform.
Recommended Action Reconfigure your switch to limit the number of VRFs. Do not define more than seven VRFs when you are entering the ip vrf vrf-name command, with vrf-name being the name of the VRF instance, in global configuration mode.
Error Message%L3TCAM-4-WCCP_ENABLE : Both VRF and WCCP are enabled, please remove either WCCP or VRF configuration
Explanation Enabling both VRF and WCCP are not supported in this platform
Recommended Action Please remove VRF or WCCP configuration.
Error Message%L3_ASIC-1-ERR_NF_PARITY : Netflow table parity error can't be fixed by software.
Explanation Netflow table parity errors are too many to be fixed by software.
Recommended Action Try reloading the system. If the messages continue for the samemodule after a reload, contact the TAC and provide 'show module'information to obtain a replacement for that module.
Error Message%L3_ASIC-4-ERR_INTRPT : Interrupt %s occurring in L3 CEF Engine .
Explanation An error interrupt is occurring for the L3 CEF Engine .
Recommended Action Enter the show earl status command on the consoles of the switch supervisor and any DFC-enabled linecards. Contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L3_COMMON-3-ERROR : [chars]
Explanation An error condition.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L3_COMMON-4-NDE_VALLOC_ERR : Reserved vlan creation for NDE could not happen
Explanation This may happen due to system vlan exhausion or PM's retry state
Recommended Action Deallocate vlans, deconfigure the feature and reapply it, if the system is up (may be after reload or otherwise) and the vlan is not yet allocated.
Error Message%L3_COMMON-4-NDE_VRF_VALLOC_ERR : Reserved vlan creation for NDE_vrf_[dec] could not happen
Explanation This may happen due to system vlan exhausion or PM's error state
Recommended Action Deallocate vlans, deconfigure the feature and reapply it.
Error Message%L3_MGR-3-ERROR : [chars]: [chars]
Explanation An error condition.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%L3_MGR-3-FLUSH : L3 MGR flush error: %s
Explanation L3 Manager has encountered flush error
Recommended Action If error recures, call your technical support representative for help
Error Message%L3_MGR-3-ICC_ASYNC : L3 MGR aysnc request failed: %s
Explanation L3 Manager receives NULL pak
Recommended Action If error recures, call your technical support representative for help.
Error Message%L3_MGR-3-L2_FLUSH_ENTRY : L3 MGR install l2 flush entry: %s
Explanation L3 Manager receives bad status
Recommended Action If error recures, call your technical support representative for help.
Error Message%L3_MGR-3-NULL_SVI : L3 MGR svi allocation error: %s
Explanation L3 Manager can not allocate svi
Recommended Action If error recures, call your technical support representative for help.
Error MessageExplanation L3 Manager can not allocate vlan
Recommended Action If error recures, call your technical support representative for help.
Error Message%L3_MGR-3-NULL_VLAN : L3 MGR vlan allocation error: [chars]
Explanation The Layer 3 manager cannot allocate VLAN.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%L3_MGR-3-REQ_SEND : L3 MGR SEND error : %s
Explanation L3 Manager has problem to send out the request
Recommended Action If error recures, call your technical support representative for help.
Error Message%L3_MGR-3-RSP_RCVD : L3 MGR RCVD error: %s
Explanation L3 Manager has received error packet
Recommended Action If error recures, call your technical support representative for help.
Error Message%L3_MGR-3-SW_SHORTCUT : L3 MGR install sw shortcut: %s
Explanation L3 Manager receives bad status
Recommended Action If error recures, call your technical support representative for help.
Error Message%L3_MGR_ISSU-3-ERROR : [chars]: [chars]
Explanation An error condition has occurred.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error MessageL4F Messages
Error Message%L4F-2-INVALIDFLOW : Invalid L4F flow: [hex]
Explanation An invalid L4F flow entry was detected.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message%L4F-5-NOBUFFER : Cannot allocate buffer to send data on the flows [chars]:[dec] - [chars]:[dec]
Explanation A buffer could not be allocated while trying to send data on the indicated flow. The issue could be due to low or fragmented memory. If the memory issue doesn't resolve automatically, it could result in connection resets.
Recommended Action This is an informational message that potential points to low or fragmented memory, which could happen if the router is running beyond its resource limits. Check the number of flows and the traffic rate going through the router and contact your technical support representative, with that info, for assistance.
LANCE Messages
Error Message%LANCE-1-INITFAIL : msgtxt_initfail
Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message%LANCE-1-MEMERR : msgtxt_memoryerror
Explanation An Ethernet interface detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message%LANCE-3-BADCABLE : msgtxt_badcable
Explanation Ethernet cable is not connected.
Recommended Action Check Ethernet cable connection.
Error Message%LANCE-3-BADUNIT : msgtxt_badunit
Explanation An internal software error occurred.
Recommended Action If either message recurs, call your technical support representative for assistance.
Error Message%LANCE-3-OWNERR : msgtxt_ownerror
Explanation An Ethernet interface is malfunctioning, or an internal software error occurred.
Recommended Action Repair or replace the controller.
Error Message%LANCE-3-SPURIDON : Unit %d, spurious IDON interrupt, csr%d=0x%04x
Explanation An Ethernet interface generated a spurious Initialization Done interrupt.
Recommended Action Repair or replace the controller.
Error Message%LANCE-3-UNDERFLO : Unit %d, underflow error
Explanation The Ethernet hardware is requesting data faster than the system can supply it. This condition might indicate that the system is at the limit of its performance.
Recommended Action A small number of underflows might not be a cause for concern. You can monitor underflows with the show interface command. Reducing the load on the router or installing a higher-performance router should alleviate this problem.
Error Message%LANCE-4-BABBLE : Unit %d, babble error, csr0 = 0x%x
Explanation An Ethernet interface is malfunctioning.
Recommended Action Determine whether the malfunction stems from a software or hardware error by turning off all fastswitching. Error messages showing that the packet is too large for the link indicate a software error at a high level. Copy the error message exactly as it appears, and report it to your technical support representative. Receiving no error messages indicates a hardware error. Repair or replace the controller.
Error Message%LANCE-5-COLL : Unit %d, excessive collisions. TDR=%d
Explanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged. The time delay reflectometer (TDR) counter is an internal LANCE counter that counts the time (in ticks of 100 ns each) from the start of a transmission to the occurrence of a collision. Because a transmission travels about 35 feet per tick, this value is useful to determine the approximate distance to a cable fault.
Recommended Action If the transceiver appears to be properly terminated, repair or replace the Ethernet interface card.
Error Message%LANCE-5-LATECOLL : Unit %d, late collision error
Explanation An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.
Recommended Action Repair or replace the controller.
Error Message%LANCE-5-LOSTCARR : Unit %d, lost carrier. Transceiver problem?
Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
LANE Messages
Error Message%LANE-3-BADILMI : Unexpected ILMI event %d
Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-BADNAME : ELAN name must be 1-32 characters long
Explanation A name which is longer than 32 characters identifying a LANE component has been entered by the user.
Recommended Action Re-enter a shorter name.
Error Message%LANE-3-BADTYPE : Inappropriate LAN type
Explanation An unexpected LAN type has been specified for a LANE component. Only ethernet and token-ring elans are supported.
Recommended Action Specify a valid LAN type.
Error Message%LANE-3-LANE_ERROR : %s
Explanation An internal error has occured, which reflects an inconsistency in the system and needs attention.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LANE_SIG_ERR : %s
Explanation An internal error occurred while system routines were handling ATM signaling messages for LANE.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LECS_ERROR : %s
Explanation An internal consistency error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_BADAD : %s LEC unable to compute ATM address
Explanation The client cannot obtain an ATM address from the given configuration, or auto-assignment failed to get an ATM prefix from the switch.
Recommended Action If you expect the switch to assign the prefix to the router, check that the Interim Local Management Interface (ILMI) is functional and the switch has a prefix configured. Otherwise, confirm that the client has an address in the NVRAM configuration.
Error Message%LANE-3-LEC_BAD_CTL_DIST_TYPE : %s CTL DIST blli type wrong
Explanation Wrong BLLI value specified on the incoming circuit.
Recommended Action The originator of the circuit is not using the correct BLLI value for this type of circuit. LANE standard defines these values, and the originator is violating the standard.
Error Message%LANE-3-LEC_CFG : %s CFG_REQ failed, %s (LECS returned %d)
Explanation The master LECs refused the LECs configuration request.
Recommended Action Check your LECS configurations.
Error Message%LANE-3-LEC_CONTROL_MSG : Received bad control message on interface %s
Explanation The LANE client received an unexpected or inappropriate control message over one of its vc's.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_ERR : %s
Explanation A LANE client software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_JOIN : %s JOIN failed, %s (LES returned %d)
Explanation LANE client was rejected the Join request to join its elan.
Recommended Action This is usually because of user configuration errors: LANE client attempting to join an incorrect elan, or elan not configured in the LES, or validation failures with the LECS, etc.
Error Message%LANE-3-LEC_LISTEN : %s listen failed on %s
Explanation The LANE client could not register its address with ATM signalling to be able to accepts calls on that address.
Recommended Action Reconfigure the client ATM address. It may be conflicting with another component with the same ATM address.
Error Message%LANE-3-LEC_RD_REGISTER : %s RD REGISTER failed for Route Descriptor %x
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_REGISTER : %s REGISTER failed, %s (LES returned %d)
Explanation attempt to register a mac-atm address binding with LES failed.
Recommended Action The LES has already registered the requested mac addr - atm addr binding.
Error Message%LANE-3-LEC_SIGNAL : Unexpected SigAPI event %d
Explanation ATM signaling sent the LANE client an unexpected message type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_WRONG_ELAN_ID : %s: elan id mismatch: LECS indicates %u, LES indicates %u
Explanation The elan-id returned by LES does not match the value given by LECS or via the CLI
Recommended Action Check configuration of elan ids specified in the LECS database and the LES. The mismatch must be occuring as a result of misconfiguration.
Error Message%LANE-3-LES_ERROR : %s
Explanation A serious internal occured with LES/BUS.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-LSV_ADDR : [chars] elan [chars] unable to register LES/BUS ATM addr
Explanation The LANE server or BUS could not register its address with the ILMI.
Recommended Action Investigate why this error has occurred. The error may have occurred because a user-defined override address does not conform to the switch prefix or because there is a problem with the ATM switch with which the entity is registering.
Error Message%LANE-3-LSV_BADAD : %s elan %s unable to compute %s ATM address
Explanation Software was unable to compute an ATM address based on the ATM address template given. The characters in chars (see above display) will be either BUS (broadcast-and-unknown), server, or config server in the actual error message.
Recommended Action Enter a correct ATM address template for the LANE component (BUS, server, or config server) named in the error message.
Error Message%LANE-3-LSV_CRASH : %s elan %s unrecoverable error %s
Explanation A very serious LES/BUS internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-NAMECHG : A LANE Client is already running here using another elan name
Explanation Both the LANE client and the LANE server/BUS may have an emulated LAN name specified in the configuration via the lane server-bus and lane client commands. If both specify the emulated LAN name, then the name cannot be changed by re-entering just one of the commands.
Recommended Action Use the no lane server-bus command to delete the server-bus or the no lane client command to delete the client. Then, the other of the two commands can be re-entered with another emulated LAN name. Finally, re-enter the deleted command with the new emulated LAN name.
Error Message%LANE-3-NOILMI : ILMI service registration failed
Explanation The Interim Local Management Interface (ILMI) feature is either not included in the software image running on the router, or is having other problems.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-NOINT : %s still destroying old sub-interface
Explanation An attempt was made to create a new subinterface while a previous version of the subinterface was still being destroyed.
Recommended Action Wait a minute and try again. If failure still occurs, try shutting down the main interface. Rebooting may be required to recover in extreme cases.
Error Message%LANE-3-NOREGILMI : %s %s cannot register %Cj with ILMI
Explanation An attempt to register the given ATM address with the ATM switch failed. This failure can occur because the ATM switch is down or misconfigured. The registration will be retried.
Recommended Action If the situation persists after a number of attempts, and the switch is up, the configuration of the switch and router should be examined. A likely cause is that the ATM address being registered is not compatible with the parameters configured in the switch. Correct the configuration.
Error Message%LANE-3-TYPECHG : A LANE Client is already running here using another elan type
Explanation Both the LANE client and the LANE Server/BUS may have an ELAN type specified in the configuration via the lane server-bus and lane client commands as either Ethernet or Token Ring. If both, specify the type; the type cannot be changed by re-entering just one of the commands.
Recommended Action Use the no lane server-bus command to delete the server-bus or the no lane client command to delete the client. Then, the other of the two commands can be re-entered with a new type. Finally, re-enter the deleted command with the new type.
Error Message%LANE-4-LECS_WARNING : %s
Explanation The LANE Configuration Server address could not be registered with or de-registered from the switch, using Interim Local Management Interface (ILMI). Possible causes: The switch prefix is not available. The address is not acceptable to the switch (the prefix does not conform). The interface over which this operation should take place is down. The ILMI subsystem on the router is not completely initialized.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-4-LSV_ADDR : %s elan %s unable to register LES/BUS ATM addr
Explanation LANE Server or BUS could not register its address with ILMI.
Recommended Action Try and investigate why. Some of the reasons are: user defined override address does not conform to the switch prefix, or that there is a problem with the ATM switch with whom the entity is registering.
Error Message%LANE-4-LSV_LECID : %s elan %s LECIDs exhausted
Explanation The LANE server specified has 65279 clients. No more can be added.
Recommended Action Change the configurations to avoid trying to have more than 65279 LANE clients on this server. %LANE-5-UPDOWN : %s %s %s: %s changed state to %s
Explanation A LANE component changed state to up/down.
Recommended Action If this event is expected, then take no action. Otherwise, please contact a technical support representative.
Error Message%LANE-5-UPDOWN : [chars] [chars] [chars]: [chars] changed state to [chars]
Explanation A LANE component has changed state to up or down.
Recommended Action If this event is expected, take no action. Otherwise, contact a Cisco technical support representative.
Error Message%LANE-6-INFO : %s
Explanation LANE subsystem simple informational messages.
Recommended Action No action is required.
Error Message%LANE-6-LECS_INFO : %s
Explanation Simple informational LECS messages.
Recommended Action No action is required.
Error Message%LANE-6-LEC_INFO : %s
Explanation LANE client informational messages.
Recommended Action No action is required.
Error Message%LANE-6-LES_INFO : %s
Explanation Simple informational LES messages.
Recommended Action No action is required.
LANMGR Messages
Error Message%LANMGR-2-NOMEMORY : No memory available: %s
Explanation The requested operation failed because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%LANMGR-4-BADRNGNUM : Ring number mismatch on %s, shutting down the interface
Explanation The router detected a conflict in assigned ring numbers for the specified Token Ring. The Ring Parameter Server (RPS) function was shut down to prevent potentially incorrect information from being sourced onto the ring.
Recommended Action Check all bridges connected to this Token Ring and ensure that they are using the same assigned ring number.
Error Message%LANMGR-4-BADUPCALL : Unexpected call (%s) from LLC2 for Bridge %03x-%x-%03x
Explanation An internal software error occurred.
Recommended Action If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LANMGR-4-NORING : No ring info for %s
Explanation An internal software error occurred.
Recommended Action If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LANMGR-4-OLDTRAMON : Cannot run RPS on %s, Old TRAMON code.
Explanation The software on this interface cannot support the functions required for LAN Network Manager.
Recommended Action Call your Cisco technical support representative about a firmware upgrade for this interface card.
LAPB Messages
Error Message%LAPB-2-NOBUF : Interface %s, no buffer available to %s
Explanation There was insufficient memory for the LAPB protocol engine to send a message.
Recommended Action This message is acceptable if it occurs infrequently, because the LAPB protocol is designed to handle loss of frames. Frequent occurrences can cause disruption of service. The system can be configured to ease memory demands or, if conditions warrant, the system can be upgraded to a larger memory configuration.
Error Message%LAPB-3-BADPAYLOAD : Interface %s, Invalid payload value: %s
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%LAPB-3-CONTEXTERR : [chars]: [chars]
Explanation An internal software error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LAPB-3-NOINPIDB : Input idb not set
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%LAPB-3-NULLPAK : Interface %s, NULL packet ptr, rvr %d, vs %d, vr %d
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%LAPB-3-TIMERERR : LAPB timer task cannot be created
Explanation An internal software error occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LAPB-4-CTRLBAD : Interface %s, Invalid control field
Explanation A received FRMR reported a frame with an invalid control code.
Recommended Action Check the serial line and the devices attached to the line. %LAPB-4-FRAMEERR : Interface %s, Frame error: CF %#x, VS %d %c VR %d, Reason %#x
Explanation A FRMR frame was received, indicating that a protocol violation was detected. The Reason field will be interpreted by generating INFOBAD, CTRLBAD, N1TOOBIG, or INVNR messages immediately after this message; refer to the explanations for these messages for more information.
Recommended Action The protocol will recover by resetting the service. This will disrupt any network service on top of LAPB (for example, X.25 virtual circuits will be cleared). Follow the recommended action for any error message following the FRMR reports; if service becomes unacceptable, check the serial line and its attached devices.
Error Message%LAPB-4-FRAMEERR : Interface [chars], Frame error: CF [hex], VS [dec] [char] VR [dec], Reason [hex]
Explanation A FRMR frame was received, indicating that a protocol violation has been detected. The Reason field will be interpreted by generating INFOBAD, CTRLBAD, N1TOOBIG, or INVNR messages immediately after this message; refer to the explanations for these messages for more information.
Recommended Action The protocol will recover by resetting the service. Resetting the device will disrupt any network service on top of FRMR. For example, X.25 virtual circuits will be cleared. Follow the recommended action for any error message that follow the FRMR reports. If service becomes unacceptable, check the serial line and its attached devices.
Error Message%LAPB-4-INFOBAD : Interface %s, Info field not permitted
Explanation A received FRMR frame reported that an information field was present in a frame where no information field is allowed.
Recommended Action Check the serial line and the device attached to the line.
Error Message%LAPB-4-INVNR : Interface %s, Invalid NR value
Explanation A received FRMR reported a frame with an invalid N(R) value.
Recommended Action Verify that the equipment attached to the serial line is configured with the same K value (maximum number of outstanding I frames).
Error Message%LAPB-4-N1TOOBIG : Interface %s, N1 too large
Explanation A received FRMR reported an information frame that was too long.
Recommended Action Verify that the equipment attached to the serial line is configured with the same N1 value. N1 is in bits and includes the entire frame plus 16 bits of CRC. However, some equipment may require configuration in octets, the omission of the two CRC octets, or the omission of the three octets of LAPB control information.
LAPP_OFF Messages
Error Message%LAPP_OFF-1-NOMEMORY : msgtxt_nomemory
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%LAPP_OFF-2-INTERNAL_ERROR : Internal software error, %s
Explanation An internal software error occurred.
Recommended Action If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LAPP_OFF-2-LAPP_OFF_INTERNAL_ERROR : Internal software error, %s, cid=%d
Explanation An internal software error occurred.
Recommended Action If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LAPP_OFF-4-LAPP_OFF_BAD_MESSAGE : LAPP_OFF- Bad message received
Explanation An unexpected message was received.
Recommended Action If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LAPP_OFF-4-LAPP_OFF_NO_SMTP : mmsp- Can't connect to the SMTP server
Explanation No connection was created to the specified SMTP server.
Recommended Action If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LAPP_OFF-4-LAPP_OFF_NO_SMTP_SEND : FAXMAIL- Could notsend data to the SMTP server
Explanation A connection was made to the SMTP server, but no data can be sent.
Recommended Action If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LAPP_OFF-4-SMTP_NOT_CONNECTED : SMTP- failed %s, %d
Explanation A connection attempt to a remote mail server was not successful. This unexpected behavior.
Recommended Action No action is required.
Error Message%LAPP_OFF-6-LAPP_OFF_CAUSE_ABNORMAL : Call aborted (cause = [hex])
Explanation Call Aborted due to abnormal error
Recommended Action No action is required.
Error Message%LAPP_OFF-6-LAPP_OFF_CAUSE_NORMAL : Normal call clearing
Recommended Action No action is required.
Error Message%LAPP_OFF-6-LAPP_OFF_HANDOFF : T.37 Fax off-ramp call initiated
Recommended Action No action is required.
Error Message%LAPP_OFF-6-SMTP_OPEN : SMTP- opening %s, %d
Explanation A connection attempt ...
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_AUTH_FAILED : User authentication failed
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_DMSP_DISCONNECTED : Document Media Service (DMSP) disconnected
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_DMSP_DISCONNECTED_NO_ROUTE : DMSP - no route - likely - ESMTP client did not connect to remote server
Explanation Call aborted due to DMSP no route disconnect - likely reason being no ESMTP connection to remote server
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_FMSP_DISCONNECTED : Fax protocol (FMSP) disconnected
Explanation Call aborted due to Fax session(FMSP) disconnect
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_INTERNAL : Internal error occured
Explanation Call aborted due to an internal error
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_NORMAL : Normal call clearing
Explanation Call clearing occurred normally
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_NO_ESMTP_CONNECT : ESMTP client did not connect or lost connection to remote server
Explanation Call aborted due to loss of outbound ESMTP connection to remote server
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_NO_MEMORY : No memory available
Explanation Call aborted due to insufficient memory being available
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_CAUSE_VTSP_DISCONNECTED : Telephony interface (VTSP) disconnected
Explanation Call termination due to Telephony interface disconnect.
Recommended Action No action is required.
Error Message%LAPP_ON_MSGS-6-LAPP_ON_HANDOFF : T.37 Fax on-ramp call initiated
Recommended Action No action is required.
LAT Messages
Error Message%LAT-3-BADDATA : Tty%t, Data pointer does not correspond to current packet
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message%LAT-3-BUFFULL : Tty%t, data buffer full with count %d
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message%LAT-3-NOSYNC : Tty%t, Output data ptrs out of sync with byte count
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message%LAT-3-NULLIDB : Null IDB pointer with destination %e
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message%LAT-3-QBSPACED : Queue block at %x not found for HI connection
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message%LAT-3-REUSE : Tty%t, Attempt to re-use slot array, empty = %d, fill = %d
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
LB Messages
Error Message%LB-3-ACL_FCB_REG_ERROR : Failed to registered Link Bundle ACL feature control block
Explanation For the given interface, failed to register the ACL feature control block.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-CHUNK_CREATE_FAIL : %schannel: failed to create chunk
Explanation An internal data structure, called a chunk, and used for channel route processor - line card interprocess communications, failed to be created. Such interprocss communication may be impeded.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-ECHAN_ADDR_ALLOC_ERROR : Channel %d, error in MAC address allocation, configured MAC address %e, actual MAC address %d
Explanation For the given channel number, addition of the first member caused a failure in changing the MAC address of the channel to that of this first member.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-ECHAN_CMDREP_REG_FAILURE : Failed to register bundle interface %s for Command Replay service
Explanation For the given link bundle interface, failed to register it for the Command Replay service.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-ECHAN_FCB_ERROR : Bundle creation feature callback failed for %s
Explanation For the given link bundle interface, failed to create its feature callback.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-FEATURE_ACL_APPLY_ERROR : Failed to apply ACL %d to interface %s. Removing new ACL config, reapplying old ACL %d.
Explanation For the given member interface or subinterface, failed to apply the given ACL. This new ACL configuration is removed from the bundle and the old ACL configuration, if any, is reapplied to the bundle. The new ACL that failed to be applied is removed in order to maintain consistent state for the whole bundle.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-FEATURE_ACL_REG_ERROR : Failed to register ACL control block with Link Bundle subinterface module
Explanation For the given interface, failed to register the ACL feature control block. This happened during install ACL support for link bundling. ACL support installation for link bundling is aborted.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-FEATURE_INSTALL_ERROR : One or more NULL feature control block members
Explanation In installing link bundling feature support, there were one or more NULL function pointers used in a feature control block. Installation of the feature support is aborted.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-FEATURE_MODULE_INIT_ERROR : Failed to create Link Bundle Feature ListQ
Explanation In initializing link bundling feature support, an internal list queue failed to be created.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-FEATURE_REG_ERROR : One or more NULL feature callbacks in the passed in Feature Control Block
Explanation In registering a feature for services from link bundling feature support, there were one or more NULL function pointers used as function callbacks. Aborted the feature registration as a result.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-FUNCTION_VECTOR_EMPTY : Empty link bundling function vector(s)
Explanation One or more function vectors used in generic etherchannel and poschannel code was null i.e. not initialized. This is a severe error resulting from a coding error. Crash will happen because this error prevents the proper functioning of the ether or pos channel features.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-POSCHAN_CMDREP_REG_FAILURE : Failed to register bundle interface %s for Command Replay service
Explanation For the given link bundle interface, failed to register it for the Command Replay service.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-POSCHAN_FCB_ERROR : Bundle creation feature callback failed for %s
Explanation For the given link bundle interface, failed to create its feature callback.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-SUBINT_ERROR : %s %s
Explanation There was a subinterfce error for the given interface.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-SUBINT_INSTALL_SUPPORT_FAILURE : Failed to registered Link Bundle subinterface control block
Explanation In initializing link bundling subinterface feature support, could not register for notifications from the common link bundle infrastructure.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-3-SUBINT_NOTIF_INIT_FAILURE : Failed to create Link Bundle Subinterface ClientQ
Explanation In initializing link bundling subinterface feature support, an internal subinterface client queue failed to be created.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LB-3-SUBINT_NOTIF_REG_FAILURE : NULL notification callback
Explanation In registering a client for service from the Link Bundling subinterface module, the callback notification callback function was NULL.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LB-5-CHAN_MEMBER_ADD_PASSIVE : %s added as passive member to %schannel%d
Explanation The given interface was added as a passive member in the given channel number.
Recommended Action No action is required.
Error Message%LB-5-CHAN_MEMBER_IN : %s added as member-%d to %schannel%d
Explanation The given channel member interface was added to the given channel number.
Recommended Action No action is required.
Error Message%LB-5-CHAN_MEMBER_MOVED_ACTIVE : %s moved to active state as member-%d in %schannel%d
Explanation The given etherchannel member interface became an active member in the given channel number.
Recommended Action No action is required.
Error Message%LB-5-CHAN_MEMBER_MOVED_PASSIVE : %s moved to passive state in %schannel%d
Explanation The given channel member interface became a passive member in the given channel number.
Recommended Action No action is required.
Error Message%LB-5-CHAN_MEMBER_OUT : %s taken out of %schannel%d
Explanation The given channel member interface was taken out of the given channel number.
Recommended Action No action is required.
LC Messages
The followinga are the Line card messages.
Error Message%LC-2-BADIDB : LC interface idb incorrect, [hex]
Explanation The LCCB data structure indicates a zero IDB.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-2-BADINTERFACE : Out of range Line Card interface, [dec] on bay [dec]
Explanation The software specified an out-of-range line card interface.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-2-BADLCCB : LC interface lccb incorrect, [hex]
Explanation The LCCB data structure has been incorrectly set in the command data structure.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-2-BADLCSLOT : Out of range Line Card slot [dec]
Explanation The software specified an out-of-range line card slot.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-2-BADSUBSLOT : Out of range Line Card slot [dec] Sub Module slot [dec]
Explanation The software specified an out-of-range sub module slot.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-2-LCRECUR : Recursive loop while getting the daughtercard info for LC type [dec]
Explanation The platform's SNMP code went into a loop while getting the daughter card information for the chassis MIB.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-2-LCSYNC : Line Card type [dec] in slot [dec] serial link sync failed.
Explanation The line card serial link synchronization has failed in the specified slot.
Recommended Action Check to see that the card is properly seated. 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-2-LCWEDGED : Line Card type [dec] in slot [dec] wedged.
Explanation The line card serial link synchronization has failed in the specified slot.
Recommended Action Check that the card is properly seated properly. 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-2-UNDEFLC : Undefined Line Card type [dec] in slot [dec]
Explanation The software does not have a driver for the line card type that is in the specified slot.
Recommended Action Make sure the Cisco IOS image you are running supports this card. Check to see that the card is properly seated. If this message recurs, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-BRINGUPFAIL : line card in slot [[dec]] failed to reset.
Explanation An attempt to reset and initialize the line card has timed out.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-CIMUXERROR : CI-MUX: Serial Link [hex], Status [hex], [chars]
Explanation The cluster interconnect multiplexer FPGA on the RP has detected an error at the specified line card serial link. This error could be the result of line card logical errors on the FPGA. It could also be the line card software driver bringing up an incorrect line card serial link. The line card automatically deactivates and attempts to recover.
Recommended Action If line card recovery fails five times within an hour, the line card is deactivated without further attempts at recovery. Reactivate the line card using the hw-module slot slot-number start command. If this command fails to reactivate the line card, copy the error message exactly as it appears on the console and enter the show diag slot-number command to collect the output. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-CLFPGAERROR : Line card common logic fpga (slot [dec]) error: [chars]
Explanation The line card common logic FPGA in the specified slot has encountered an error. This error could be result of a line card FPGA error or by the line card software driver incorrectly performing the reset sequence. Based on the severity of the error, the line card automatically deactivates and attempts to recover.
Recommended Action If line card recovery fails five times within an hour, the line card deactivates without further attempts at recovery. Reactivate the line card using the hw-module slot slot-number start command. If this command fails to reactivate the line card, copy the error message exactly as it appears on the console and enter the command to collect the output. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-CONFIG : Recommended line card configuration exceeded
Explanation The aggregate throughput of the line cards has exceeded the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed aggregate throughput of the line cards for the system.
Error Message%LC-3-DEACTIVATED : line card in slot [[dec]] deactivated.
Explanation The specified line card is being deactivated.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-EMPTYSLOT : No line card in slot [[dec]].
Explanation There is no line card in the specified slot.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-EXCESSERRORS : Errors seen on the line card (slot [dec]) exceeds the error threshold
Explanation The software is attempting to recover the line card from certain fatal errors, such as a. A line card serial link error
Explanation b. A line card FPGA or device error
Explanation c. Excessive interrupts
Explanation d. A local processor firmware crash
Explanation e. The loss of a keep alive from the card local processor
Explanation f. IPC initialization failure of the card local processor firmware
Explanation The line card is reinitialized after this error, unless the error occurs five times in one hour. If a line card encounters five such errors in one hour, the line card deactivates without further attempts at recovery.
Recommended Action Try to reactivate the line card manually by entering the hw-module slot slot-number start command. The line card can also be reactived by removing and reinserting the line card; if you take this approach, first copy the error message as it appears on the console and collect the output from the show diag slot-number command before removing and reinserting the line card. If the error recurs, contact your Cisco technical support representative and provide the representative with the error message and the show diag slot-number command output.
Error Message%LC-3-FPGAREVNOTMATCH : [chars]([dec]) Line card fpga requires min h/w revision of ([dec].[dec])
Explanation A newer hardware revision level of the line card is required for the current FPGA to function properly on this chassis.
Recommended Action Upgrade your hardware level, or the downgrade the FPGA version.
Error Message%LC-3-FPGAREVNOTSUPPORTED : [chars]([dec]) Line card requires fpga revision of ([dec]).Current fpga revision is ([dec])
Explanation A newer FPGA revision of the line card is required for operation on this chassis.
Recommended Action Upgrade your FPGA version.
Error Message%LC-3-IOTIMEOUT : RP CI-MUX FPGA read timeout (Slot [dec], Serial Channel [dec])
Explanation The cluster interconnect multiplexer FPGA on the RP could not complete the line card I/O read transaction. This error could be the result of a timing error inside the line card FPGA or the result of an incorrect line card I/O access by the line card software driver. The line card automatically deactivates and recovers.
Recommended Action If line card recovery fails five times within an hour, the line card is deactivated without further attempts at recovery. Reactivate the line card using the hw-module slot slot-number start command. If this command fails to reactivate the line card, copy the error message exactly as it appears on the console and enter the command to collect the output. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-LCCREATE : Unable to create driver for Line Card type [dec] in slot [dec]
Explanation The system is unable to create a driver for the line card in the specified slot. This error could be caused by a memory shortage or a line card hardware error.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-LCI2C_ERROR : [chars] Linecard I2C bus access failed at slot [dec], status = [hex]
Explanation The line card in the specified slot experienced an I2C access failure. This problem often occurs when the I2C protocol fails to terminate the previous transaction gracefully. The failure to gracefully terminate could be the result of a hardware or software caveat. The line card automatically deactivates.
Recommended Action Reactivate the line card by entering the hw-module slot slot-number start command. If this command fails to reactivate the line card, copy the error message exactly as it appears on the console and collect the show diag slot-number command output. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-LC_CHUNK : Unable to [chars] for Linecard Slot [dec]
Explanation Possible memory shortage.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LC-3-LC_QUEUE : Unable to [chars] for Linecard Slot [dec]
Explanation Possible memory shortage.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LC-3-NOTSUPPORTED : LC in slot[dec] ([chars]) is not supported on this [chars]
Explanation The specified line card is not supported on this chassis or CPU card.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-PSALOADSHARE : MPLS loadsharing inconsistency for [IP_address][IP_network]
Explanation An unexpected inconsistency has occurred while programming the hardware forwarding engine for load sharing onto MPLS LSPs. The Packet Switching ASIC is used in Engine 2 line cards for IP and MPLS packet forwarding. It uses an mtrie-based lookup engine, micro-sequencers and other special hardware to assist in the packet forwarding process.
Recommended Action This message appears due to a transient condition that can happen in normal operation. It will be corrected automatically. No action is required.
Error Message%LC-3-RECOVERY : Line card (slot [dec]) recovery in progress
Explanation This informational message indicates that a line card is recovering from any one of the following fatal errors A line card serial link error
Explanation A line card FPGA or device error
Explanation An excessive amount of interrupts
Explanation A card local processor firmware crash
Explanation The loss of a keep alive from the card local processor
Explanation A card local processor firmware IPC initialization failure
Recommended Action Enter the show diag slot-number command. 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-REVNOTSUPPORTED : LC in slot[dec] with hw version ([dec].[dec]) is old. Requires base h/w
revision of ([dec].[dec]) for this line cardExplanation The hardware revision level of the line card is out of date.
Recommended Action Use a newer hardware revision level to enable this line card to work properly with the current Cisco IOS image. If this message recurs after migration to the latest Cisco IOS image, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-3-SANTAANA : Santa Ana Asic: [chars] [dec], Serial Channel [char] (slot [dec]), Error Status [hex] [chars][chars][chars]
Explanation The Santa Ana ASIC on the RP or the indicated line card detected an error at the associated serial link. This error could be caused by line card FPGA timing errors or by an incorrect line card serial link that was brought up by the line card software driver. The line card automatically deactivates and recovers.
Recommended Action If line card recovery fails five times within an hour, the line card is deactivated without further attempts at recovery. Reactivate the line card usingt he hw-module slot slot-number start command. If this command fails to reactivate the line card, copy the error message exactly as it appears on the console and enter the show diag slot-number command to collect the output. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show diag slot-number, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC-6-VIRTUALINIT : Line card (slot [dec]) - [chars]
Explanation Line card errors have occurred during an early stage of the system boot operation. Recovery logic has been activated, and the specified line card has been initialized in virtual mode. All hardware access to the line card has been disabled and the line card has been initialized to a state where the startup configuration that is relevant to the interfaces on the line card could be applied. After system boot is complete, an attempt will be made to recover and initialize the line card in the standard operating mode.
Recommended Action This is an informational message only. No action is required. When the line card recovers from the error, the line card will change from virtual mode to standard operating mode if the error encountered during system boot was transient.
LCB Messages
Error Message%LCB-3-LOCKFAILURE : Multiple LCB event processes scheduled
Explanation This message occurs when LCB event process fails to lock the semaphore which is used to prevent multiple LCB processes from running. This implies that multiple LCB processes have been scheduled to run which should not happen
Recommended Action Try executing the command again after a few minutes. If the problem persists contact Cisco Technical support
Error Message%LCB-3-QUEUEFAILURE : LCB process unable to create event queue
Explanation Unable to create LCB event queue. LCB process quit. The operating system was unable to allocate RAM space for the queue
Recommended Action Try executing the command again after a few minutes. If the problem persists it indicates a lack of RAM space. Most likely, the router image requires more system memory (RAM) than the router contains.
LCCEF Messages
Error Message%LCCEF-3-MACSTR : adjacency ([chars]) has incorrect high word ([hex]) in its mac string
Explanation The CEF line card has received an adjacency with an incorrect MAC rewrite string. Packets forwarded to that adjacency will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LCCEF-3-OUTINFO : adjacency ([chars]) has incorrect output_info ([hex]) field
Explanation The CEF line card has received an adjacency with an incorrect OUTPUT_INFO field. Packets forwarded to that adjacency will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
LCCOREDUMP Messages
The following are line card core dump subsystems messages.
Error Message%LCCOREDUMP-2-EOM : Cannot allocation memory for [chars]
Explanation The system cannot allocate memory for the core dump subsystem.
Recommended Action Add more memory.
Error Message%LCCOREDUMP-3-BADCLOSE : Can't close slave core socket for slot [dec]
Explanation The system has just finished dumping a core file from a line card. The system tried and failed to close the core file on the remote system.
Recommended Action Verify the network connections and user privileges.
Error Message%LCCOREDUMP-3-BADOPEN : Can't open slave core socket for slot [dec]
Explanation The system wants to dump a core file to a remote system, but the system is unable to open the remote file.
Recommended Action Ensure that the remote system is accessible and that the protocol is set up correctly.
Error Message%LCCOREDUMP-3-BADWRITE : Can't write [chars] to slave core socket for slot [dec]
Explanation The system is trying to write a core dump file to a remote system. The file was opened, and an error has occurred during a write to the file.
Recommended Action Verify that the network is functioning and that there is available disk space.
Error Message%LCCOREDUMP-3-ILLNVGEN : Illegal call to bflc_cfg_coredump_nvgen
Explanation The NVGEN routine was called, but NVGEN was not set.
Recommended Action Gather information about the processes running on this GSR, including the traceback, and contact your Cisco technical support representative.
Error Message%LCCOREDUMP-3-ILLPAK : Coredump packet received from slot [dec] (not in dump state) [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation The RP has received a core dump packet from a line card that should not be dumping core.
Recommended Action Gather information about the state of the line cards and contact your Cisco technical support representative.
Error Message%LCCOREDUMP-3-ILLTD : Testdump only valid on line cards (not allowed on RPs)
Explanation You cannot run a line card core dump test for an RP.
Recommended Action Do not try to run a line card core dump test for an RP.
Error Message%LCCOREDUMP-3-NOMCP : Cannot malloc memory for mbus core dump message to slot [dec]
Explanation The system is trying to write a core dump file to a remote system, but it could not allocate memory to create the message that starts the core dump process.
Recommended Action Add memory.
Error Message%LCCOREDUMP-3-NOPAK : No packet on queue ([hex] [dec])
Explanation The RP has received a core dump packet from a line card that should not be dumping core.
Recommended Action Gather information about the state of the line cards and contact your Cisco technical support representative.
Error Message%LCCOREDUMP-3-NOPROC : Unable to create data handler process
Explanation The system is attempting to write a core dump file to a remote system, but it is unable to start a process to dump the file.
Recommended Action Gather information about the number of processes running, including the amount of memory in the system, and contact your Cisco technical support representative.
Error Message%LCCOREDUMP-3-NOQUEUE : Cannot create queue to receive dump packets for slot [dec]
Explanation The system is trying to write a core dump file to a remote system. It could not create a queue to hold dump data coming from the line cards.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%LCCOREDUMP-4-NOMDD : [chars] core dump for slot [dec] (Cannot modify during dump)
Explanation The system is currently dumping a core file for this line card. You cannot modify core dump configuration during a core dump.
Recommended Action Wait for the core dump to finish.
Error Message%LCCOREDUMP-6-LERP : Cannot configure linecard exceptions for [chars] RP
Explanation The exception line card commands can be used only to configure exceptions on a line card. You cannot use an exception line card command to configure RP core dumps.
Recommended Action Use the exception command without a line card specified to configure RP core dumps.
Error Message%LCFE-3-FE_RX_MICE : [chars]
Explanation The LC Fast Ethernet Mice FPGA could not be loaded.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCFE-3-RX_TX_TRANS : [chars]
Explanation The LC Fast ethernet Rx and Tx translator FPGA could not be loaded.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
LCGE Messages
The following are Gigabit Ethernet line card driver messages.
Error Message%LCGE-3-RX_TRANS : [chars]
Explanation The LC Gigabit Ethernet Rx GigaTranslator FPGA could not be loaded.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCGE-3-RX_TRANS_PROG : [chars]
Explanation The LC Gigabit Ethernet Rx GigaTranslator FPGA has not been programmed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
LCINFO Messages
Error Message%LCINFO-3-CRASH : Line card in slot [int]/[int] crashed
Explanation The line card in the slot indicated crashed and sent a CRASH_START message to the PRE. The PRE is now waiting for the rest of the crash information from the line card to be sent via the BPE (stack trace, context, version, etc.). This should happen in a few milliseconds after receiving the CRASH_START message. The PRE software has not otherwise been notified of the line card crash — that will happen after all the crash information has been sent to the PRE. In the unlikely event that the subsequent crash information messages are not received by the PRE within a reasonable time limit (perhaps 10 secs), the PRE will print a TIMEOUT message indicating that and tell the rest of the PRE software that the line card has crashed.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCINFO-3-INVDEV : Invalid line card number in BPE callback (LC=[int]/[int])
Explanation The line card crash information subsystem on the PRE was called from the BPE subsystem with an invalid slot/subslot. The slot or subslot number is out of range. This indicates a software defect in the system.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCINFO-3-INVSTATE : Line card crash server in bad state (LC=[int]/[int],state=[int])
Explanation The line card crash information subsystem for the line card indicated it is in an unknown state. This is due to a software defect in that subsystem.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCINFO-3-NOBUF : Could not malloc line card crash structures on PRE (size=[int])
Explanation The PRE could not malloc data structures for line card crash data structures at startup time. This is not by itself a serious problem, but the underlying memory shortage at startup time will probably prevent the router from running well if at all.
Recommended Action Add more memory and/or debug the memory shortage problem.
Error Message%LCINFO-3-NOBUFLC : Could not malloc line card crash info buffer on PRE (bufnum=[int],size=[int])
Explanation The PRE could not malloc one or more buffers to hold line card crash information at startup time. This is not by itself a serious problem, but the underlying memory shortage at startup time will probably prevent the router from running well if at all.
Recommended Action Add more memory and/or debug the memory shortage problem. Possibly reduce the size of or the number of crash information buffers allocated per line card to hold crash information — currently, it is not known if either the size or number will be configurable.
Error Message%LCINFO-3-NOLCHANGPROC : Failed creating line card hang cure process
Explanation When creating the LC hang cure process for checking prolonged CLC down states, the create_process call failed. This should not happen. It is probably due to a software defect or hardware failure. This failure should only happen during initialization.
Recommended Action Rebooting the system should fix this. If this message recurs on subsequent reloads of the system, a bug should be filed and the system should be reloaded with a different image.
Error Message%LCINFO-3-NOPROCESS : Failed creating line card complete process
Explanation When creating the crash complete process for the crash information subsystem the create_process call failed. This should not happen. It is probably due to a software defect or hardware failure. This failure should only happen during initialization.
Recommended Action Rebooting the system should fix this. If this message recurs on subsequent reloads of the system, a bug should be filed and the system should be reloaded with a different image.
Error Message%LCINFO-3-TIMEOUT : Timeout waiting for crash info from slot [int]/[int]
Explanation The crash information complete timer expired. When a line card crashes, it sends information to the PRE for debugging and analysis. When the START OF CRASH message is recieved, a timer is set for approx 10 seconds. The line card has 10 seconds to send all the crash information to the PRE. This is not a crash dump — this is a small amount of information that usually includes context, stack trace, etc. It is less than 8K bytes of information. If an END OF CRASH information message is not received before the timer goes off, the crash information record is closed (contains partial information), this message is displayed, and the rest of the system is notified that the line card crashed (at which point it is probably reloaded). If the line card sends more crash information after the timer goes off and before the system resets the line card additional UNXMSG message might be displayed.
Recommended Action No action is required specifically because this message was displayed. Because the line card was crashing there might be other defects to report. If this message is seen without a line card crashing report, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Include the information for the show tech-support command on the PRE *AND* on the line card that did not crash but was mentioned in this error message.
Error Message%LCINFO-4-LCHUNG : Slot [[dec]/[dec]] down on last [dec] checks. HW RESET # [dec] ...
Explanation A line card can get hung in some IOS operation and will not be able to recover, or it can get stuck while initiating tftp bootload. This is the time when an external monitoring process on RP checks the condition of each line card. If the line card is found stuck for more than 150 seconds, a hardware reset is issued, for that subslot. And while issuing a hard reset this message is displayed on the console.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCINFO-4-TRUNC : Crash record ([int]=[chars]) truncated (expected=[int],actual=[int])
Explanation A line card crashed an was sending crash information to the PRE. The PRE received a CRASH RECORD START message that indicated the data would be 'expected' bytes long. Before that many bytes were received, the PRE received another CRASH RECORD START message indicating the start of another record. The current record is marked as truncated, and the next record is received, but the anomoly is noted in this message. This is a problem, but because what started this process was a line card crashing, this might only be a symptom of another underlying problem.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCINFO-4-UNXMSG : Unexpected crash info msg type ([chars]) in state [chars] (LC=[int]/[int])
Explanation The line card crash information subsystem received an unexpected message for the state it is in. The state and message type are given in the message. This does not have any adverse effect on the PRE since it ignores and/or recovers from this occurrence. Because the sender of these messages is a line card that is crashing, it is possible this might happen. The source of the crash on the line card is more interesting. If this occurs without a line card crashing, it is due to a stray/errant BPE message that should be persued. This could also be due to a dropped BPE message.
Recommended Action Find the source of the crash on the line card if one was crashing when the message occurred. If no line card was crashing, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. LCLOG Messages
Recommended Action The following are internet router line card logger messages.
Error Message%LCINFO-6-LCRESET : PRE switchover. Reset empty slot [[dec]/[dec]]
Explanation When the standby PRE becomes active, it resets all the slots which it thinks are empty. This prevents any line cards which were coming up during the PRE switchover from getting stuck.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCLOG-3-INVDEV : Invalid slot/subslot number in logger API callback (LC=[int]/[int])
Explanation The line card crash info subsystem on the PRE was called from the BPE subsystem with an invalid slot/subslot. This indicates a software defect in the system.
Recommended Action Report this defect with as much information about the subsystem as possible. There is no adverse effect to the PRE — it ignores the bad callback and continues. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCLOG-3-INVSTATE : LC logger in bad state (LC=[int]/[int],state=[chars],msg=[chars])
Explanation The line card logger subsystem for the line card indicated is not in the state expected for the message it received. This is probably due to a software defect in that subsystem. This could also be due to a dropped BPE message.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCLOG-3-MSGGIANT : LC log msg larger than max allowed (LC=[int]/[int],length=[int])
Explanation The PRE part of the line card logger server has received a log start message that is larger than the maximum log buffer allows. This is probably due to a software defect.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCLOG-3-MSGTOOBIG : LC log msg longer than expected (LC=[int]/[int],len=[int],exp=[int])
Explanation The PRE part of the line card logger server has received more text for a message than the start message indicated. This is probably due to a software defect.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LCLOG-3-OVERFLOW : LC log msg longer than msg buffer (LC=[int]/[int],len=[int],max=[int])
Explanation The PRE part of the line card logger server has received more text for a message than will fit in the message log buffer. This is probably due to a software defect.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. LCMDC Messages
Recommended Action The following are Cisco Optical Networking Systems (ONS) 15540 Extended Services Platform (ESP) messages.
Error Message%LCMDC-3-ACCESS_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The system has detected an alarm condition. The error message text provides more information on the nature of the alarm.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
LCMDC Messages
Error Message%LCMDC-3-CDL_HEC_ETX_ALM : CDL HEC Err count; [chars]
Explanation The maximum error count for CDL HEC has been exceeded.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-CDL_RFOF_IND : CDL Drop FIFO OvrFL; [chars]
Explanation An CDL drop FIFO overflow prealarm condition has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-DEBUG_INTF_CREATE_FAILED : Transparent Interface Creation Failed for slot [[dec]]
Explanation The interface data structure creation and initialization have failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-ECDRLK_ALM : Egress CDR Locking error; [chars]
Explanation The CDR cannot lock onto the signal.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-EOP_NOLG_ALM : Egress Loss of Light: [chars]
Explanation An egress loss-of-light alarm has been raised.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-EOP_NOLG_PALM : Egress Loss of Light Prealarm: [chars]
Explanation An egress loss-of-light alarm has been raised. The system has switched to the other side.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-EOP_TKSW_ALM : Egress Trunk Switch Mech. Failure; [chars]
Explanation An egress switch has failed to change position during autofailover.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-ESERDESLK_ALM : Egress Serdes Locking error; [chars]
Explanation SERDES has encountered problems while attempting to lock onto the signal.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-ESERPHERR_ALM : Egress Serdes Phase Error; [chars]
Explanation A phase error involving SERDES has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-ETH_DCC_LPBK_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The system has detected an alarm condition. The error message text provides more information on the nature of the alarm.
Recommended Action Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl . If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/ , or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-FH_ECETX_ALM : Egress Fiber Channel/ESCON Line Err; [chars]
Explanation The fiber channel or ESCON line code error count has exceeded the maximum level.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-FH_ELOSY_ALM : Egress FC/ESCON Loss of Sync; [chars]
Explanation Either a fiber channel or an ESCON synchronization error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-FH_ICETX_ALM : Ingress FC/ESCON Line Code err; [chars]
Explanation An ingress fiber channel or ESCON line code error count has exceeded the maximum level.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-FH_ILOSY_ALM : Ingress FC/ESCON Loss of Sync; [chars]
Explanation An synchronization error has occurred on the ingress side between the Fiber Channel and the ESCON.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-FPGA_ACCESS_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation An alarm has occurred. The message text provides additional details on the nature of the error.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-GE_ECETX : Egress GE Line Code Err count; [chars]
Explanation The Gigabit Ethernet line code error count has exceeded the maximum level.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-GE_ELOSY_ALM : Egress GE Loss of Sync; [chars]
Explanation Gigabit Ethernet has lost synchronization on the egress side.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-GE_ILOSY_ALM : Ingress GE Loss of Sync; [chars]
Explanation Gigabit Ethernet has lost synchronization on the ingress side.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-GH_ICETX_ALM : Ingress GE Line Code Err; [chars]
Explanation The ingress line code error count has exceeded the maximum level.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-ICDRLK_ALM : Ingress CDR Locking error; [chars]
Explanation The ingress CDR has failed to lock onto a signal.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-IDCKFAIL : LRC ID check failed [[chars]]
Explanation A read or write error occurred when the LRC ID register was being accessed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-IDPROMCRCFAIL : IDPROM CRC check failed [[chars]]
Explanation The IDPROM has failed to pass the CRC check.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-IDPROMMATCHFAIL : IDPROM mismatch read failed [[chars]]
Explanation The values from the read do not match.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-IDPROMRDFAIL : IDPROM read failed [[chars]].
The card may not be inserted correctly. Please ensure that card is
inserted completely and then please fasten the screws completely.Explanation A read error occurred when accessing the IDPROM.
Recommended Action Ensure the card is inserted completely and that the screws are fastened. If the card is properly inserted and the screws are fastened, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-IDPROM_ACCESS_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The alarm text describes the nature of the error.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-INTF_CREATE_FAILED : Interface Create Failed [[chars]]
Explanation The system was unable to create the interface data structure; initialization has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-INTF_DELETE_FAILED : Interface Delete Failed [[chars]]
Explanation An interface data structure was not deleted.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-INTRPENDING : Pending unexpected interrupt [addr [hex] = [hex]]
Explanation The system has detected one or more pending unexpected interrupts.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-INT_LPBK_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The alarm text describes the nature of the error.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-INVALIDCLKRATE : Non supported clock rate [dec] Khz
Explanation The entered clock rate in kHz is not supported.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-INVALIDSIGRATE : Non supported signal rate [dec]
Explanation The signal rate for ENUM is invalid.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-IOP_NOLG_ALM : Ingress Loss of Light; [chars]
Explanation An ingress loss-of-light alarm has been raised.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-ISERDESLK_ALM : Ingress Serdes Locking Error; [chars]
Explanation An ingress SERDES signal lock error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-ISERPHERR_ALM : Ingress Serdes Phase error; [chars]
Explanation An ingress SERDES out-of-phase error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-LASER_DEGRADE : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The alarm text describes the nature of the error.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-LASER_DEVIATION : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The alarm text describes the nature of the error.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-LINE_LASER_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The alarm text describes the nature of the error.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-LN_OFC_IND : Line OFC IND; [chars]
Explanation An indication of ingress OFC has been detected.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-LN_TX_ALM : Line Laser Failure; [chars]
Explanation A laser line failure has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-LPBK_THRU_PSC_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The alarm text describes the nature of the error.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-LRCMAGICREGRESET : Magic Register Reset Slot [dec]
Explanation Magic Register reset for line card in the specified slot. .
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MDSUBCARD_IDPROM_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The alarm text describes the nature of the error.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_CDL_HEC_ALM : CDL HEC Err count [chars] [chars] [chars]
Explanation The CDL HEC error count has exceeded the allowed maximum level.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_CDL_RFOF_IND : CDL Drop FIFO OvrFL [chars] [chars] [chars]
Explanation The system has detected a CDL drop FIFO overflow prealarm.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_ECDRLK_ALM : Egress CDR Locking error [chars] [chars] [chars]
Explanation The CDR cannot lock onto the signal.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_EOP_NOLG_ALM : Egress Loss of Light [chars] [chars] [chars]
Explanation An egress loss-of-light alarm has been raised.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_EOP_NOLG_PALM : Egress Loss of Light Prealarm [chars] [chars] [chars]
Recommended Action An egress loss-of-light alarm has been raised. The system has switched to the other side. 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_EOP_TKSW_ALM : Egress Trunk Switch Mech. Failure [chars] [chars] [chars]
Explanation The egress switch failed to switch position during autofailover.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_ESERDESLK_ALM : Egress Serdes Locking error [chars] [chars] [chars]
Explanation SERDES cannot lock onto the signal.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_ESERPHERR_ALM : Egress Serdes Phase Error [chars] [chars] [chars]
Explanation A phase error has occurred with the SERDES.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_FH_ECETX_ALM : Egress Fiber Channel/ESCON Line Err [chars] [chars] [chars]
Explanation The line error count involving communication between the Fiber Channel and the ESCON has exceeded the allowed maximum.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_FH_ELOSY_ALM : Egress FC/ESCON Loss of Sync [chars] [chars] [chars]
Explanation The fiber channel or ESCON synchronization error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_FH_ICETX_ALM : Ingress FC/ESCON Line Code err [chars] [chars] [chars]
Explanation The count for the ingress fiber channel or ESCON line code error has exceeded the maximum level.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_FH_ILOSY_ALM : Ingress FC/ESCON Loss of Sync [chars] [chars] [chars]
Explanation The ingress fiber channel or ESCON has lost synchronization.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_GE_ECETX : Egress GE Line Code Err count [chars] [chars] [chars]
Explanation The error count for the Gigabit Ethernet line code has exceeded the maximum level.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_GE_ELOSY_ALM : Egress GE Loss of Sync [chars] [chars] [chars]
Explanation The egress Gigabit Ethernet has lost synchronization.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_GE_ILOSY_ALM : Ingress GE Loss of Sync [chars] [chars] [chars]
Explanation The ingress Gigabit Ethernet has lost synchronization.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_GH_ICETX_ALM : Ingress GE Line Code Err [chars] [chars] [chars]
Explanation The ingress line code error count has exceeded the maximum level.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_ICDRLK_ALM : Ingress CDR Locking error [chars] [chars] [chars]
Explanation The ingress CDR has failed to lock onto a signal.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_IOP_NOLG_ALM : Ingress Loss of Light [chars] [chars] [chars]
Explanation An ingress loss-of-light condition has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_ISERDESLK_ALM : Ingress Serdes Locking Error [chars] [chars] [chars]
Explanation An ingress SERDES signal lock error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_ISERPHERR_ALM : Ingress Serdes Phase error [chars] [chars] [chars]
Explanation An ingress SERDES out of phase error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_LN_OFC_IND : Line OFC IND [chars] [chars] [chars]
Explanation An indication of ingress OFC has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_LN_TX_ALM : Line Laser Failure [chars] [chars] [chars]
Explanation The line laser has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_SH_EBIP_ALM : Egress SONET BIP Err count [chars] [chars] [chars]
Explanation The SONET BIP error count has exceeded the allowed maximum on the egress side.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_SH_ELOF_ALM : Egress SONET Loss of Frame [chars] [chars] [chars]
Explanation A SONET loss-of-frame error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_SH_ESEF_ALM : Egress SONET SEF Prealarm [chars] [chars] [chars]
Explanation The number of SONET severely-errored-frame errors on the egress side has exceeded the allowed maximum.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_SH_IBIP_ALM : Ingress SONET BIP error [chars] [chars] [chars]
Explanation The error count for the ingress SONET BIP has exceeded the allowed maximum.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_SH_ILOF_ALM : Ingress SONET Loss of Frame [chars] [chars] [chars]
Explanation A SONET loss-of-frame error has occurred on the ingress side.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_SH_ISEF_ALM : Ingress SONET SEF [chars] [chars] [chars]
Explanation The SONET severely-errored-frame error count on the ingress side has exceeded the allowed maximum.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_TK_OFC_IND : Trunk OFC IND [chars] [chars] [chars]
Explanation An indication of egress OFC has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_TK_TX_ALM : Transmit Failure [chars] [chars] [chars]
Explanation A transmission failure has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_TK_TX_LDGR : Laser Degrade Truk side [chars] [chars] [chars]
Explanation A laser degradation failure has occurred on the transmit side.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_TK_TX_WD : Wavelength Deviation [chars] [chars] [chars]
Explanation A wavelength deviation error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_TK_WDEGRADE_ALM : Trunk laser degrade: [chars] [chars] [chars]
Explanation A trunk laser has experienced a degrading of wavelength.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-MIB_TK_WDEVIATION_ALM : Trunk Laser wavelength deviation: [chars] [chars] [chars]
Explanation A trunk laser has experienced a wavelength deviation.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-OPT_SWITCH_0_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The system has detected an alarm condition. The error message text provides more information on the nature of the alarm.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-OPT_SWITCH_1_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The system has detected an alarm condition. The error message text provides more information on the nature of the alarm.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-OPT_SWITCH_2_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The system has detected an alarm condition. The error message text provides more information on the nature of the alarm.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-OPT_SWITCH_3_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The system has detected an alarm condition. The error message text provides more information on the nature of the alarm.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-OSC_HW_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The system has detected an alarm condition. The error message text provides more information on the nature of the alarm.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-PORTFAILASSERTED : Unexpected portfail asserted
Explanation One or more unexpected port failures have been asserted.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-PORT_CREATE_FAILED : Port Creation Failed [[chars]]
Explanation Creation or initialization of the port data structure has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-RDWRFAIL : Read/write failed [[chars]]
Explanation A read or write error occurred during an attempt to access the hardware.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-READYPRESENT : Card [slot [dec]] present but not ready
Explanation A card is present, but the system cannot communicate with it. A possible cause for this error is that the card is being reset.
Recommended Action Attempt to reset the card or, if the card is being reset, no action is required. If you require further assistance, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-SH_EBIP_ALM : Egress SONET BIP Err count; [chars]
Explanation The error count for SONET BIP has exceeded the maximum level.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-SH_ELOF_ALM : Egress SONET Loss of Frame; [chars]
Explanation A SONET loss-of-frame error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-SH_ESEF_ALM : Egress SONET SEF; [chars]
Explanation The SONET severely-errored-frame error count on the egress side has exceeded the allowed maximum level.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-SH_IBIP_ALM : Ingress SONET BIP error; [chars]
Explanation The ingress error count for the SONET BIP has exceeded the maximum level.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-SH_ILOF_ALM : Ingress SONET Loss of Frame; [chars]
Explanation Ingress SONET loss-of-frame errors have occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-SH_ISEF_ALM : Ingress SONET SEF; [chars]
Explanation The SONET severely-errored-frame error count on the egress side has exceeded the allowed maximum.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-STDBYOP_NOLG_ALM : Loss of Light on Standby: [chars]
Explanation The standby unit has no light.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-TK_OFC_IND : Trunk OFC IND; [chars]
Explanation The egress OFC is enabled.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-TK_TX_ALM : Transmit Failure; [chars]
Explanation A transmission failure has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-TK_TX_LDGR : Laser Degrade Trunk side; [chars]
Explanation A laser degradation failure has occurred on the transmitting side.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-TK_TX_WD : Wavelength Deviation; [chars]
Explanation A wavelength deviation error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-TK_WDEGRADE_ALM : Trunk laser degrade: [chars]
Explanation A trunk laser has experienced a degrading of wavelength.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-TK_WDEVIATION_ALM : Trunk Laser wavelength deviation: [chars]
Explanation A trunk laser wavelength deviation error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-TRUNK_LASER_DEGRADE : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The system has detected an alarm condition. The error message text provides more information on the nature of the alarm.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-TRUNK_LASER_DEVIATION : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The system has detected an alarm condition. The error message text provides more information on the nature of the alarm.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-WAVELENGTH_DEVIATION : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The system has detected an alarm condition. The error message text provides more information on the nature of the alarm.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-WAVELENGTH_MISMATCH : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The system has detected an alarm condition. The error message text provides more information on the nature of the alarm.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-WLENCKFAIL : Unexpected trunk laser wavelength: [chars]
Explanation The trunk laser wavelength is incorrect.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-3-XCVR_OIR_ALM : Transceiver OIR; [chars]
Explanation The pluggable transceiver has been hot swapped.
Recommended Action No action is required.
Error Message%LCMDC-4-RATEMISMATCH : Encap rate mismatched: [chars]
Explanation The entered encapsulation rate does not match the transceiver type.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCMDC-5-DEFWAVELEN : Default wavelength selected: [chars]
Explanation The inserted transponder can not support cached hardware subblocks pointing to the ITU number. Instead, the default wavelength is used.
Recommended Action No action is required.
Error Message%LCMDC-6-TX_ALARM_SOAK : [chars]
Explanation An alarm has occurred. The message text provides additional details on the nature of the error.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
LCR Messages
Error Message%LCR-6-FAILED : Failed to send exported registry request [dec]
Explanation A communication failure occurred while an exported registry request was being sent.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCR-6-NOMEM : No available memory for sending exported registry request [dec]
Explanation The line card registry subsystem could not obtain the memory it required.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
LCRED Messages
Error Message%LCRED-2-RECEIVE_SYNC_MESSAGE_FAILED : Checkpointing sync message was received on Standby RP, but it was corrupted or there was an error processing it.
Explanation A synchronization message was sent from the Active RP and received on the Standby RP. The message was either empty, corrupted, or could not be processed by the Standby client. If the system is NOT in bulk synchronization mode, then Standby RP will be reset.
Recommended Action This is an informational message only. The line card recovery infrastructure will take recovery actions. No action is required.
Error Message%LCRED-2-SEND_SYNC_MESSAGE_FAILED : Checkpointing sync message to client on Standby RP was not received.
Explanation A synchronization message was sent from the Active RP, but it was never received, or was received in corrupted form, on the Standby RP. The platform code has been notified, and platform-specific recovery actions will be taken.
Recommended Action This message is for informational purposes only. The line card recovery infrastructure will take recovery actions. No action is required.
Error Message%LCRED-2-SUBSYSTEM_INIT_FAILED : Subsystem failed during init phase with error [chars].
Explanation An unrecoverable error occurred during subsystem initialization for the Line Card Redundancy subsystem. The system will come up and run fine, but line card redundancy will not be available for configuration and will not come up if it was already configured in start-config.
Recommended Action You can continue to use the system without line card redundancy. Reloading the system might allow the line card redundancy subsystem to come up. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show running-config, show redundancy linecard history, show redundancy linecard all, show version, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-2-SYNC_FAILURE_NO_BUFFER : Could not get sync buffer to checkpoint data.
Explanation An attempt to get a synchronization buffer failed when trying to synchronization data from the active RP to standby. This is likely a system memory issue. The platform code has been notified to take possible corrective action.
Recommended Action This is an informational message only. The system will correct if possible.
Error Message%LCRED-3-CANT_SET_ROLE : Couldn't set or clear slot or port roles for Line card [dec]/[dec].
Explanation An attempt to set or clear the slot or port Active/Standby roles for a line card has failed. This message indicates that an error occurred during redundant linecard state progression.
Recommended Action Check the redundancy configuration and try to remedy by CLI if it is not correct. Check the configuration by entering the show redundancy linecard all and show redundancy linecard group all commands. If the redundancy configuration cannot be corrected, then copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard history, show version, and show running-config commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-COULDNT_ADD_REDUNDANT_IF : Error occurred while configuring redundant interface ([dec]/[dec]): [chars]
Explanation The specified error occurred during configuration of a redundant interface. The redundant configuration command was not successfully completed.
Recommended Action Verify that the command was correct. Verify the current redundancy configuration by entering the show redundancy linecard all and show redundancy linecard group all commands. If you think that the command was correct but failed anyway, copy the message exactly as it appears on the console or in the system log. Enter the show running-config, show redundancy linecard history, show redundancy linecard all, show processes memory, and show version commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-EREVENT1 : [chars] [hex]
Explanation This message is used for reporting invalid values for parameters or database members.
Recommended Action Check the redundancy configuration for the slot by entering the show redundancy linecard all and show redundancy linecard group all commands. Fix the configuration, if required, and re-execute the command, making sure that any command parameters are correct. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard history command to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-HWIDB_SUBBLOCK_CREATE_FAIL : Creation of hwidb subblock for [chars] i/f [dec]/[dec] failed.
Explanation Each redundant interface, whether active, standby, or virtual, has a hardware IDB subblock that stores redundancy information about that interface. If this subblock cannot be created, then creation of the redundant interface will fail.
Recommended Action Reenter the CLI that triggered the message. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard group all and show redundancy linecard all commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-INVALID_DEBUG : Invalid debug type parameter [int] specified.
Explanation The function responsible for turning debugging on or off was called with an invalid debug type code.
Recommended Action Verify that the debug command is available by entering the debug redundancy lc ? command and try it again.
Error Message%LCRED-3-IPC : [chars]
Explanation This is a general IPC error.
Recommended Action Check the redundancy configuration by entering the show redundancy linecard all command. If the configuration is not what you expected, repeat the commands. If the configuration is correct and this message recurs, try switching over the linecard if the standby LC is configured and ready. Otherwise, try resetting the linecard in the slot specified. If you still get the error, copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard all and show processes memory commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-IPCPORT : Can't Create IPC port ([chars]) error ([chars]) IPC err([chars]).
Explanation Cannot create an IPC to receive traffic from peer.
Recommended Action Check the redundancy configuration by entering the show redundancy linecard all command. If the configuration is not what you expected, repeat the commands. If the configuration is correct and this message recurs, try switching over the line card if the standby LC is configured and ready. Otherwise, try resetting the line card in the slot specified. If you still get the error, copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard all and show processes memory commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-LC_CANT_SET_TXRX : Unable to set Active/Standby Tx/Rx selection for Line Card [dec]/[dec].
Explanation The platform driver rejected a request to set the Tx/Rx selectors for a redundant linecard. The platform was unable to initialize the linecard Active/Standby states.
Recommended Action Check the redundancy configuration and try to remedy by CLI if it is not correct. Check the configuration by entering the show redundancy linecard all and show redundancy linecard group all commands. If the redundancy configuration cannot be corrected, then copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard history, show version, and show running-config commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-LC_NEG_DONE_WITH_ILLEGAL_ROLE : Illegal Line Card redundancy role assignments found following role negotiation.
Explanation When line card role negotiation was done, an illegal line card redundancy role was assigned to it and/or its peer. There are four kinds of roles that can be assigned to a line card: Active, Standby, Wait, or None. The only legal combination of roles for a slot and its peer are as follows: Active-NONE, Active-Standby, WAIT-NONE. The rest are all illegal.
Recommended Action This is an informational message only. The line card redundancy system will take recovery action. No action is required.
Error Message%LCRED-3-LC_PROG_RETURNED_ERROR : Progression attempt returned error for Line Card [dec]/[dec].
Explanation Attempt to complete progression has failed.
Recommended Action Check the redundancy configuration and try to remedy by CLI if it is not correct. Check the configuration by entering the show redundancy linecard all and show redundancy linecard group all commands. If the redundancy configuration cannot be corrected, then copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard history, show version, and show running-config commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-LC_PROG_TO_INIT_ERROR : Unable to reset progression to INIT for Line Card [dec]/[dec].
Explanation An attempt to reinitialize progression has failed.
Recommended Action Check the redundancy configuration and try to remedy by CLI if it is not correct. Check the configuration by entering the show redundancy linecard all and show redundancy linecard group all commands. If the redundancy configuration cannot be corrected, then copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard history, show version, and show running-config commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-LC_STATE_PROG_ERROR : Illegal event in redundant Line Card [dec]/[dec] state progression. Line Card will be reset.
Explanation An illegal event has occurred during redundant line card state progression.
Recommended Action This is an informational message only. The LCRED system will reset the line card to recover. No action is required unless the message recurs. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show redundancy linecard all, show redundancy linecard group all, show redundancy linecard history, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-LC_STATE_PROG_FAILED : Redundant Line Card [dec]/[dec] state progression failure. Line card will be reset.
Explanation Redundant line card state progression has failed.
Recommended Action This is an informational message only. The LCRED system will reset the line card to recover. No action is required unless the message recurs. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show redundancy linecard all, show redundancy linecard group all, show redundancy linecard history, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-LC_STATE_PROG_HARD_FAILURE : Redundant Line Card [dec]/[dec] state progression failed more than [dec] times in the past [dec] seconds. Line card is in a non-recoverable state.
Explanation Redundant line card state progression failure rate has exceeded the threshold.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard all, show redundancy linecard group all, show redundancy linecard history, show version, and show running-config commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-LC_UP_WITH_ILLEGAL_ROLE : Illegal Line Card redundancy role assignments during linecard up.
Explanation When a line card came up, an illegal line card redundancy role was assigned to it and/or its peer. There are four kinds of roles that can be assigned to a line card: Active, Standby, Wait, or None. The only legal combination of roles for a slot and its peer are as follows: Active-NONE, Active-Standby, WAIT-NONE. The rest are all illegal.
Recommended Action This is an informational message only. The system will reset both line cards in the redundant pair to recover.
Error Message%LCRED-3-MEMBERTWICE : LC : Request to add slot member [int] twice to group [int].
Explanation An attempt was made to add a member from the specified slot to a redundant interface group that already contains a member from that slot.
Recommended Action This is a user error. Double-check the configuration by entering the show redundancy linecard group all command and try the procedure again.
Error Message%LCRED-3-NOINITMEM : Subsystem Init ([chars]) Failed due to unavailability of memory of size([dec])
Explanation Initialization of the LCRED subsystem has failed due to insufficient memory. This is indicative of system memory shortage. The problem is likely unrelated to line card redundancy.
Recommended Action Initiate recovery procedures as you would for any system that does not have sufficient memory to perform actions.
Error Message%LCRED-3-NOIPCMEM : Cannot Allocate IPC memory to get message.
Explanation Cannot allocate memory to send redundancy control message. This is indicative of system memory shortage. The problem is likely unrelated to line card redundancy.
Recommended Action Initiate recovery procedures as you would for any system that does not have sufficient memory to perform actions.
Error Message%LCRED-3-NO_MORE_PREALLOCATED_SUBBLOCK_MEMORY : Could not allocate redundancy subblock. Pre-allocated memory for subblock creation of [int] is exhausted.
Explanation The platform pre-allocates a pool of memory for creating redundancy subblocks via registry plfm_get_max_redundancy_sb(). This pool has been exhausted so no more redundancy subblocks can be created. This means that no more redundant slots or ports can be configured. However, when redundant slots or ports are unconfigured from redundancy, the subblocks are freed, and then other slots or ports could be configured for redundancy to replace them.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config, show version, show hardware, and show processes memory commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-NO_SLOT_TO_DELETE : LC : Request to delete non-member slot [int] from redundancy group [int].
Explanation An attempt was made to delete a slot from a redundant line card group that does not contain the specified slot as a member.
Recommended Action Check the configuration by entering the show redundancy linecard group all command and try the procedure again.
Error Message%LCRED-3-REMOVE_SLOT_OR_IF_FAILURE : Removal of redundant interface caused an unexpected condition for i/f ([chars]).
Explanation While removing a redundant interface (possibly during redundant line card removal) a software bug was encountered. Line card redundancy is now in an unknown state.
Recommended Action Check the line card redundancy configuration and try to remedy by CLI if it is not correct. Check the configuration by entering the show redundancy linecard all and show redundancy linecard group all commands. If the redundancy configuration cannot be corrected, then copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard history, show version, and show running-config commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-SYNC_FAILURE_ISSU_NOT_OK : Could not send checkpoint message during [chars] sync because issu infrastructure deemed ISSU state is incorrect.
Explanation The ISSU infrastructure deemed the ISSU state of line card redundancy's ISSU client peer is incorrect.
Recommended Action If this message occurs once ISSU client negotiation is complete, and the system is up and running, reset the standby RP. If it occurs during system bringup, nothing needs to be done. The HA infrastructure should recover without intervention.
Error Message%LCRED-3-UNMAPPED_IFINDEX : NULL/Invalid [chars] ifindex [hex] downloaded for interface group number [int].
Explanation The interface identifier specified for a member or virtual interface of a redundant interface group does not correspond to a known interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard all, show redundancy linecard group all, and show redundancy linecard history commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-UPDATENOTSENT : The update message was not sent to the linecard(s)
Explanation An attempt was made to deliver an update to the LCRED database down to the line card(s), but the update could not be delivered. The LCRED database on the RP could be out of synchronization with that of the line card(s).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard all, show redundancy linecard group all, and show redundancy linecard history commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-3-VIFTWICE : LC : Request to add a second virtual interface to group [int].
Explanation An attempt was made to add a virtual interface to a redundant interface group that already has a configured virtual interface.
Recommended Action If this error was in response to a user command, then check the command and try again if it appears correct. If the error seems to be from some undefined action, then copy the message exactly as it appears on the console or in the system log. Enter the show redundancy linecard group all and show redundancy linecard history commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. LDP Messages
Recommended Action The following are Label Distribution Protocol messages.
Error Message%LCRED-3-VIF_HWIDB_CREATE_FAIL : Virtual hwidb creation failed from physical i/f ([chars]): [chars].
Explanation Creation of virtual hwidb has failed with the specified error.
Recommended Action Without the virtual hwidb (VIF), the interface will not be protected. Try the CLI that caused this error again. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show version, show running-config, show processes memory, show redundancy linecard all, show redundancy linecard group all, and show redundancy linecard history commands to gather data that might help identify the nature of the message. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LCRED-4-PARTIAL_CONFIG_LOSS : Partial redundancy config loss while configuring redundant interface ([dec]/[dec])
Explanation During system reload, could not get hwidb for the secondary interface, so the secondary redundancy configuration will be lost. The primary interface will be active if it was parsed correctly.
Recommended Action Verify that primary interface is configured. Reconfigure the secondary interface for redundancy.
Error Message%LC_10G-3-ACCESS_FAIL : [chars] Access Fail
Explanation A read or write operation to the LRC scratch pad register has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-AFOVR_ERR : Autofailover Error[chars]
Explanation The optical switch has encountered an error during an autofailover operation.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
LC_10G Messages
Error Message%LC_10G-3-AFOVR_EVNT : Autofailover event occured [chars]
Explanation An autofailover event has occurred.
Recommended Action No action is required.
Error Message%LC_10G-3-CDL_HEC_ERR_THR : CDL HEC Errors threshold [chars]
Explanation The threshold of allowable CDL HEC errors has been exceeded.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-CRC_ERR_THR : CRC Errors threshold [chars]
Explanation The threshold of allowable CRC errors has been exceeded.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-ETH_DCC_LPBK_FAIL : EthernetDcc loopback Fail
Explanation A loopback operation through the Ethernet backplane has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-IDPROM_ACCESS_FAIL : Idprom Access Fail
Explanation The ID of the PROM could not be read or checked.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-INTERNAL_CRITICAL : [chars]
Explanation A critical error condition has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-INTERNAL_ERROR : [chars]
Explanation An error condition has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-INT_LPBK_FAIL : Internal Card loopback Fail
Explanation An loopback attempt that was internal to the card has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-LASER_AUTO_SHUTDOWN : Auto Laser Shutdown [chars]
Explanation The laser has been automatically shut down.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-LASER_BIAS_ALARM : Optic Laser Bias Alarm [chars]
Explanation An error involving laser bias has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-LASER_TEMP_ALARM : Optic Laser Temperature Alarm [chars]
Explanation An error involving the temperature of the optics laser has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-LASER_TX_FAULT : Optic Laser Transmit Fault [chars]
Explanation An error involving optics laser transmission has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-LOSS_OF_LOCK : Transceiver Loss of Lock [chars]
Explanation The transceiver has lost the lock onto the incoming signal.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-LOSS_OF_SYNC : Transceiver Loss of Sync [chars]
Explanation The transceiver has lost its frame synchronization.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-LPBK_THRU_PSC_FAIL : loopback through PSC Fail
Explanation A internal card loopback attempt through the PSC has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-MIB_AFOVR_ERR_ALM : Optical Switch Error[chars] [chars] [chars]
Explanation An optical switch error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-MIB_AFOVR_EVNT_ALM : AutoFailover Event [chars] [chars] [chars]
Explanation An autofailover event has occurred.
Recommended Action No action is required.
Error Message%LC_10G-3-MIB_AUTO_LASER_SHUTDOWN : Auto Laser Shutdown [chars] [chars] [chars]
Explanation The laser has been shut down.
Recommended Action No action is required.
Error Message%LC_10G-3-MIB_LASER_BIAS_ALM : Laser Bias Alarm [chars] [chars] [chars]
Explanation An error involving trunk laser bias has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-MIB_LASER_TEMP_ALM : Laser Temperature Alarm [chars] [chars] [chars]
Explanation An error involving the temperature of the trunk laser has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-MIB_LASER_TX_FLT_ALM : Laser Transmit Fault [chars] [chars] [chars]
Explanation An error involving trunk laser transmission has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-MIB_LOSS_OF_LOCK_ALM : Loss of Lock [chars] [chars] [chars]
Explanation A loss-of-lock event has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-MIB_LOSS_OF_SYNC_ALM : Loss of Sync [chars] [chars] [chars]
Explanation A loss-of-synchronization event has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_10G-3-SYML_ERR_THR : Symbol Errors threshold [chars]
Explanation The threshold of allowable symbol errors has been exceeded.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
LC_2P5G Messages
The following are Hamptons 2.6G trunk card-related messages.
Error Message%LC_2P5G-2-INTERNAL_CRITICAL : [chars]
Explanation An internal critical error condition has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-ACCESS_FAIL : Access Fail [chars]
Explanation A read or write operation to the LRC scratch pad register has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-AFOVR_ERR : Autofailover Error [chars]
Explanation The optical switch failed to perform an autofailover operation.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-CDL_HEC_ERR_THR : CDL HEC Errors threshold [chars]
Explanation The threshold of allowable CDL HEC errors has been exceeded.
Recommended Action Ensure that the cables connected to the Rx transceiver are plugged in and are not bent or twisted. Check the physical nature of the cables to ensure that they are in good condition. Check the physical state (the transmit laser power level) and the configuration of the remote end that is connected to the port associated with this message. If this message persists, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-CRC_ERR_THR : CRC Errors threshold [chars]
Explanation The threshold of allowable CRC errors has been exceeded.
Recommended Action Ensure that the cables connected to the Rx transceiver are plugged in and are not bent or twisted. Check the physical nature of the cables to ensure that they are in good condition. Check the physical state (the transmit laser power level) and the configuration of the remote end that is connected to the port associated with this message. If this message persists, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-ETH_DCC_LPBK_FAIL : EthernetDcc loopback Fail [chars]
Explanation A loopback operation through the Ethernet backplane has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-IDPROM_ACCESS_FAIL : Idprom Access Fail [chars]
Explanation The ID of the PROM could not be read or checked.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-INTERNAL_ERROR : [chars]
Explanation An internal error condition has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-INT_LPBK_FAIL : Internal Card loopback Fail [chars]
Explanation A loopback operation that was internal to the card has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-LASER_DEGRADATION_ALARM : Optic Laser Degradation Alarm [chars]
Explanation The transmission power of the optics laser module is degrading.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-LASER_NO_LIGHT_ALARM : Optic Laser Loss of Light Alarm [chars]
Explanation The optics laser has experienced a loss of light.
Recommended Action Ensure that the cables connected to the Rx transceiver are plugged in and are not bent or twisted. Check the physical nature of the cables to ensure that they are in good condition. Check the physical state (the transmit laser power level) and the configuration of the remote end that is connected to the port associated with this message. If this message persists, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-LASER_TX_FAULT : Optic Laser Transmit Fault [chars]
Explanation An optics laser transmission fault has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-LASER_WAVE_LN_DEV_ALARM : Optic Laser Wavelength Deviation Alarm [chars]
Explanation The wavelength of the optics laser module has deviated.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-LOSS_OF_LOCK : Transceiver Loss of Lock [chars]
Explanation The receiver has lost the lock on the incoming signal.
Recommended Action Ensure that the cables connected to the Rx transceiver are plugged in and are not bent or twisted. Check the physical nature of the cables to ensure that they are in good condition. Check the physical state (the transmit laser power level) and the configuration of the remote end that is connected to the port associated with this message. If this message persists, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-LOSS_OF_SYNC : Transceiver Loss of Sync [chars]
Explanation The decoder has lost its frame synchronization.
Recommended Action Ensure that the cables connected to the Rx transceiver are plugged in and are not bent or twisted. Check the physical nature of the cables to ensure that they are in good condition. Check the physical state (the transmit laser power level) and the configuration of the remote end that is connected to the port associated with this message. If this message persists, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-LPBK_THRU_PSC_FAIL : loopback through PSC Fail [chars]
Explanation An internal card loopback operation through the PSC has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-MIB_AFOVR_ERR_ALM : Optical Switch Error[chars] [chars] [chars]
Explanation An autofailover operation for the optical switch has failed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-MIB_CVRD_ERR_THR : CVRD Error Threshold Exceeded [chars] [chars] [chars]
Explanation The threshold of allowable symbol errors has been exceeded.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-MIB_LASER_DEG_ALM : Laser Degradation Alarm [chars] [chars] [chars]
Explanation The transmission power of the optics laser module is degrading.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-MIB_LASER_TX_FLT_ALM : Laser Transmit Fault [chars] [chars] [chars]
Explanation An optics laser transmission fault has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-MIB_LASER_WV_DEV_ALM : Laser Wavelength Deviation Alarm [chars] [chars] [chars]
Explanation The wavelength of the optics laser module has deviated.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-MIB_LOSS_OF_LOCK_ALM : Loss of Lock [chars] [chars] [chars]
Explanation The receiver has lost its lock on the incoming signal.
Recommended Action Ensure that the cables connected to the Rx transceiver are plugged in and are not bent or twisted. Check the physical nature of the cables to ensure that they are in good condition. Check the physical state (the transmit laser power level) and the configuration of the remote end that is connected to the port associated with this message. If this message persists, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-MIB_LOSS_OF_SYNC_ALM : Loss of Sync [chars] [chars] [chars]
Explanation The decoder has lost its frame synchronization.
Recommended Action Ensure that the cables connected to the Rx transceiver are plugged in and are not bent or twisted. Check the physical nature of the cables to ensure that they are in good condition. Check the physical state (the transmit laser power level) and the configuration of the remote end that is connected to the port associated with this message. If this message persists, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LC_2P5G-3-MIB_NO_LIGHT_ALM : Laser Loss of Light Alarm [chars] [chars] [chars]
Explanation An error involving a loss of light for the optics laser has occurred.
Recommended Action Ensure that the cables connected to the Rx transceiver are plugged in and are not bent or twisted. Check the physical nature of the cables to ensure that they are in good condition. Check the physical state (the transmit laser power level) and the configuration of the remote end that is connected to the port associated with this message. If this message persists, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error MessageExplanation Symbol errors crossed threshold limit.
Recommended Action Check that the cables are connected to the Rx transciever and are unbent and untwisted. Check the condition of the cables. Check the physical state (transmit laser power level) and configuration of remote end connected to the port associated. If this message recurs, 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. LCINFO Messages
Recommended Action The following are line card crash information messages.
Error Message%LC_2P5G-3-SYML_ERR_THR : Symbol Errors threshold [chars]
Explanation The threshold of allowable symbol errors has been exceeded.
Recommended Action Ensure that the cables connected to the Rx transceiver are plugged in and are not bent or twisted. Check the physical nature of the cables to ensure that they are in good condition. Check the physical state (the transmit laser power level) and the configuration of the remote end that is connected to the port associated with this message. If this message persists, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. LCFE Messages
Recommended Action The following are Fast Ethernet line card driver messages.
Error Message%LC_2P5G-5-AFOVR_EVNT : Autofailover event occured [chars]
Explanation An autofailover event has occurred.
Recommended Action No action is required.
Error Message%LC_2P5G-5-LASER_AUTO_SHUTDOWN : Auto Laser Shutdown [chars]
Explanation The laser has been automatically shut down.
Recommended Action No action is required.
Error Message%LC_2P5G-5-MIB_AFOVR_EVNT_ALM : AutoFailover Event [chars] [chars] [chars]
Explanation An autofailover event has occurred.
Recommended Action No action is required.
Error Message%LC_2P5G-5-MIB_AUTO_LASER_SHUTDOWN : Auto Laser Shutdown [chars] [chars] [chars]
Explanation The laser has been automatically shut down.
Recommended Action No action is required.
LDP Messages
The following are Label Distribution Protocol (LDP) messages.
Error Message%LDP-3-AUTOCFG : Interface [chars] is in an unexpected autoconfig state [hex], [chars] request.
Explanation An interface is in an unexpected LDP auto config state. This could impact the LDP session running on this interface.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LDP-3-ISSU_XFORM : ISSU [chars] transformation failed for msg type ([dec])[chars].
Explanation LDP could not upgrade/downgrade a checkpointing message.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LDP-3-ISYNC : [chars]
Explanation An unexpected error happened in LDP-IGP Synchronization operation.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LDP-3-ISYNC_CHKPT : [chars]: : [chars] request failed ([chars])
Explanation An unexpected condition happened while (un)checkpointing an igp-sync-record.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LDP-3-MALFORMED_MSG : peer [chars]; format error for msg type [hex]
Explanation A malformed LDP message has been received from an LDP peer.
Recommended Action This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message recurs, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LDP-3-RECONNECT : [chars]
Explanation An error occurred while parsing the incoming LDP Initialization message. The FT Reconnect Timer value received was greater than the locally-configured Forwarding State Holding Timer value.
Recommended Action Reconfigure the Forwarding State Holding Timer value. LFD Messages
Recommended Action The following are Label Forwarding Database (LFD) messages.
Error Message%LDP-3-UNKNOWN_MPLS_APP : [chars] [chars] message from [chars]; [chars];
Explanation An LDP message with an unknown label type or address family has been received from a peer. The message has been dropped.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. LFD Messages
Recommended Action The following are MFI Label Switching Database (LFD) messages.
Error Message%LDP-4-ADV : Label advertisement mode (DU/DoD) mismatch with peer [chars], resolved to [chars].
Explanation A disagreement about the label distribution mode to be used with an LDP peer has been resolved according to the LDP protocol specification. For LCATM links, when there is a disagreement, the protocol specification requires that the session use Downstream on Demand mode. For frame-based links, when there is disagreement, the protocol requires that the session use Downstream Unsolicited mode.
Recommended Action This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message occurs repeatedly, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LDP-4-PTCL : peer [chars], [chars]
Explanation A violation of the LDP protocol by an LDP peer has been detected.
Recommended Action This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message recurs, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LDP-5-CLEAR_CHKPT : Clear LDP bindings checkpoint state ([chars]) by [chars]
Explanation The checkpoint state for one or more LDP bindings has been reset.
Recommended Action No action is required.
Error Message%LDP-5-CLEAR_NBRS : Clear LDP neighbors ([chars]) by [chars]
Explanation One or more LDP neighbor sessions has been reset.
Recommended Action No action is required.
Error Message%LDP-5-GR : [chars]
Explanation An LDP notice was generated for a graceful restart event.
Recommended Action No action is required.
Error Message%LDP-5-NBRCHG : [chars] Neighbor [chars] is [chars]
Explanation An LDP neighbor has either come up or gone down. The message describes the change for it.
Recommended Action This informational message normally appears as routers and LDP neighbors go up or down. However, unexpected neighbor loss might indicate high error rates or high packet loss in the network and should be investigated.
Error Message%LDP-5-PWDCFG : Password configuration changed for [chars]
Explanation An informational LDP notice was generated to report password configuration change for a neighbor.
Recommended Action No action is required.
Error Message%LDP-5-PWDRO : Password rolled over for [chars]
Explanation An informational LDP notice was generated to report lossless password change for a neighbor.
Recommended Action No action is required.
Error Message%LDP-5-SP : [chars]
Explanation An informational LDP notice was generated for a Session Protection event.
Recommended Action No action is required. LFD Messages
Recommended Action The following are Label Forwarding Database messages.
Error Message%LES_FDDI-2-ILLEGAL : msgtxt_fddi_illegal
Explanation This error message is displayed when the router does not have enough I/O memory to support a FDDI interface. The FDDI interface requires at least 4MB of I/O memory.
Recommended Action Install the required amount of I/O memory. For maximum performance, Cisco reccommends installing 8Mb of I/O memory for a single FDDI NIM, and 16MB of I/O memory if 2 FDDI NIMs are installed. With 4MB of I/O memory the system will create 256 FDDI buffers for a one FDDI interface or 384 buffers for two FDDI interfaces. With 8MB of I/O memory the system will create 512 FDDI buffers for either one or two FDDI interfaces. With 16MB of I/O memory the system will create 512 FDDI buffers for a one FDDI interface or 1024 buffers for two FDDI interfaces.
LEX Messages
Error Message%LEX-3-NOTSENT : Serial line down, %s : %s not sent
Explanation The serial line went down, and the specified command was not sent to the LAN Extender.
Recommended Action Determine why the serial line went down. For example, was the cable was pulled, or the LAN Extender powered off? The command will automatically be re-sent once the serial interface is operational.
Error Message%LEX-3-RCMDNAK : %s : %s could not be processed by LAN Extender
Explanation The LAN Extender could not process the command from the host router. Possible causes are: The LAN Extender ran out of memory. The message from the host router is malformed. A request to write flash occurred while the LAN Extender was busy writing flash for a previous request. The size of a file to be downloaded is greater than the amount of flash memory available.
Recommended Action If the command was copy tftp lex unit-number or copy flash lex unit-number, make sure that the correct file, that is, a FLEX image file, is specified. Only a single copy request can be handled at one time. If the problem was caused by a temporary out-of-memory condition on the LAN Extender, re-enter the command.
Error Message%LEX-3-RCMDREJ : %s : %s could not be processed by LAN Extender
Explanation The LAN Extender did not recognize the code for the specified remote command. This might occur if the user is running old LAN Extender software with newer host router software that has support for new LEX remote commands.
Recommended Action Update the LAN Extender software.
Error Message%LEX-3-TIMEOUT : Retry count exceeded for %s : %s
Explanation The host router re-sent the given message as many times as specified in the lex retry-count command configuration variable, without receiving an acknowledgment from the LAN Extender. At this point, the host router gives up trying to send this particular remote command message.
Recommended Action Use the LEDs on the LAN Extender to determine if it is operational. Confirm that the lex timeout configuration command is set appropriately for the speed of the link.
LFD Messages
Error Message%LFD-2-AVL : [chars] [hex]
Explanation An error involving an AVL tree operation has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-2-FPIHANDLER3 : [chars] [hex] [hex] [hex]
Explanation An error has been detected in the FPI handler.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-2-WAVL : FPI type:[chars] [chars] [hex]
Explanation A wavelength tree operation error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. LINK Messages
Recommended Action The following are data link messages.
Error Message%LFD-3-BADEXEC : Unexpected Code Execution: [chars] [dec]
Explanation An error involving unexpected execution of code has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-BADFRRTYPE : illegal frr type: [dec]
Explanation An error involving an FRR request type has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-BADLABELADD : Cannot add label - [chars].
Explanation Unable to create label due to reason given.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-BADSHORTLABELADD : Cannot add short label: path_idx [dec], moi_type [dec]
Explanation Unable to create MFI feature space in FIB entry, so unable to store short path extension information there.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-BROKERINITFAIL : Failed to initialise lte RP broker facility
Explanation An internal software error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-CHUNKMGR : chunk mgr: [chars] [hex]
Explanation An error involving the chunk manager has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-CHUNKMGRALLOC : failed chunk alloc: [chars]
Explanation An error involving chunk allocation has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-CHUNKMGRDEALLOC : failed chunk dealloc: [chars]
Explanation An error involving the freeing of a chunk has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-EVTLOGBADSOURCE : Illegal log event source: [dec]
Explanation An illegal event in the log buffer has been detected.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-FPIHANDLER : [chars] [hex] [hex]
Explanation An error has been detected in the FPI handler.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-FPITYPEWRONG : Require fpi type [chars], get fpi type [chars]
Explanation An error involving unmatched FPI types has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-INTFDB : intf db: [chars] [hex]
Explanation An interface DB error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-INTFDB2 : intf db: [chars] [hex] [hex]
Explanation An interface DB error has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-INVINSTALLER : Wrong installer [dec] for [chars] [dec]/[dec] update (was [dec])
Explanation Label was previously installed by different installer.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-INVIPLABELTYPE : Wrong label type %d for IP Label %d, table %d prefix %s, vrf %s
Explanation Label type is invalid for the indicated label table entry
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, gather the output of show version and show running-config andcontact your Cisco technical support representative.
Error Message%LFD-3-INVLABELTYPE : Wrong label type %d for non-ip LTE %d/%d
Explanation Label type invalid for non-ip label table entry
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-INVRWID : Wrong rwid %d for non-ip LTE %d/%d
Explanation Rewrite ID invalid for non-ip label table entry
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-INVXDRLEN : Length [int] for [chars] field in LTE msg for [chars]
Explanation An error occured when encoding the MPLS label information for the FEC in question. This could result in linecards having stale labels for this FEC.
Recommended Action Refer to the Bug Navigator at www.cisco.com to see if this condition has been previously reported and resolved in a later release. If not, copy the message exactly as it appears on the console or in the system log. Enter the show version, show running-config and show mpls forwarding-table commands to gather information that might help identify the natur of the error. 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-LCXDRCLIENT : LTE distribution client: %s
Explanation An internal software error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-LTABLEMEM : Cannot allocate new mpls table [dec] of size [dec] needed for entry [dec]
Explanation Insufficient contiguous memory was available for the MPLS forwarding table.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%LFD-3-NONIPINFO : Non-ip info: %s
Explanation An internal software error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-NOOCE : Attempt to get labels from OCE failed - [chars].
Explanation Calling function has provided insufficient information to get labels.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-NORESOURCE : [chars] [dec]
Explanation A resource failure has occurred.
Recommended Action If this message recurs, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-NULLADJACENCY : NULL Adjacency
Explanation An adjacency with a null value has been encountered.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-NULLFIBIDB : NULL FIB IDB: [chars] [dec]
Explanation A FIB IDB with a null value has been encountered.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-ORPHANIPLTE : Found an IP LTE with no [chars] - label [dec]/[dec].
Explanation Every IP LTE must have an associated fib entry.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-ORPHANNONIPLTE : Found a non-owned non-IP LTE of ptype [dec] - label [dec]/[dec].
Explanation Every non-IP LTE must be owned.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-3-REWMGR : Rewrite Manager: [chars] [hex]
Explanation An error involving the rewrite manager has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-REWMGR2 : [chars] [hex] [hex]
Explanation A rewrite lookup attempt has failed becuase of an inconsistency in the FPI.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-SM : [chars] [dec]
Explanation An error involving the state machine has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-SMBADEVENT : Unexpected event [chars] for state [chars]
Explanation The LFD received an event that was unexpected for its state. The state of the LFD, and the unexpected event, are specified in the message text.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-UPDATEHANDLER2 : [chars] [hex] [hex]
Explanation An error involving the update handler has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-UPDATEHANDLER3 : [chars] [hex] [hex] [hex]
Explanation An error involving the update handler has occurred.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-UPDATEHANDLERFPI : No handler installed: fpi=[dec] handler type=[chars]
Explanation No handler has been installed.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-3-XDRBADMAGIC : xdr message for %s spilled out of allocated static storage
Explanation An internal software error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-4-NOFIBIDB : [chars] - ifnum [dec]
Explanation The FIB IDB is missing on the line card.
Recommended Action If this message recurs, 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LFD-4-OWNCHANGED : Owner changed for [chars] [dec]/[dec] from [dec] to [dec]
Explanation Label was previously installed by different installer.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-4-RESOURCE : [chars]
Explanation MPLS is not supported by the platform.
Recommended Action No action is required.
Error Message%LFD-4-UNSUPPORTED : MPLS not supported by platform for this slot
Explanation MPLS is either not needed or not handled by the platform for this card.
Recommended Action No action is required.
Error Message%LFD-4-UNSUPPORTEDRW : Unexpected rewrites seen where MPLS is not supported by platform for this slot
Explanation MPLS is either not needed or not handled by the platform for this card and should not handle rewrites.
Recommended Action No action is required.
Error Message%LFD-5-FRRISSULOG : FRR is not ISSU compatible, notified by %s
Explanation ISSU negotation results for FRR not compatible
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LFD-6-RESOURCE : %s
Explanation MPLS software is disabled on LC
Recommended Action No action is required.
Error Message%LI-4-DEDICATED_MODE : Slot [dec] can not switch to LI dedicated mode because ther are SPAs in it.
Explanation A SIP-400 can be configured as LI dedicated service card. But it can only switch to dedicated mode if all SPAs in it are un-plugged. Otherwise it will stay in non-dedicated mode.
Recommended Action Un-plug all the SPAs in the SIP-400. It will automatically switch to LI dedicated mode.
LIBT2F Messages
Error Message%LIBT2F-2-NEW_CONTEXT : A new text2fax context could not be created
Explanation An internal error occurred in the initialization of thetext2fax engine. The fax transmission will be aborted.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIBT2F-3-ENGINE_FAILED : The text2fax engine failed
Explanation This occcurred most likely due to a memory limitation orillegal data being passed into the text2fax engine. The faxtransmission will be aborted
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIBT2F-3-GETBUFFER_FAILED : Cannot allocate a packetfrom shared memory
Explanation The system is running low on packet memory. The fax cannot besent correctly.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIBT2F-3-NULL_BUFFER : A text buffer is NULL
Explanation An internal error occurred in the text buffer processing. Thefax tranmission be aborted.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIBTIFF-3-BAD_DIALPEER : Invalid dial peer tag %d
Explanation Invalid mmoip dial peer tag
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIBTIFF-3-ENGINE_FAILED : The tiff engine failed
Explanation This occcurred most likely due to a memory limitation orillegal data being passed into the tiff engine. The fax transmission will be aborted
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIBTIFF-3-GETBUFFER_FAILED : Cannot allocate a packetfrom shared memory
Explanation The system is running low on packet memory. Thefax cannot be sent correctly
Error Message%LIBTIFF-3-INVALID_BUFFER : A tiff buffer is invalid
Explanation An internal error occurred in the tiff bufferprocessing. The fax tranmission will be aborted.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIBTIFF-3-NEW_CONTEXT : A new tiff context could not be created
Explanation An internal error occurred in the initialization of thetiff engine. The fax transmission will be aborted.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIBTIFF-3-NULL_BUFFER : A tiff buffer is NULL
Explanation An internal error occurred in the tiff bufferprocessing. The fax tranmission will be aborted.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIBTIFF-4-COPY_QUALITY : Bad copy quality on tty%d
Explanation Noisy phone lines or a bad modem caused this error
Recommended Action If the error recurs, 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
LICENSE Messages
Error Message%LICENSE-1-ENFORCEMENT : Feature %s %s running without a License. UDI=%s
Explanation Your system is running a feature that is licensed. Running a feature without a license will create support and legal issues.
Recommended Action Please buy and install the license for the feature immediately. If you are seeing this message afterinstallation, contact TAC with show license file and show license detail output
Error Message%LICENSE-1-REQUEST_FAILED : License request for feature %s %s failed. UDI=%s
Explanation Your system is trying to run a feature without a license.
Recommended Action Please buy and install the license for the feature immediately
Error Message%LICENSE-2-EXPIRED : License for feature %s %s has expired %s. UDI=%s
Explanation License for the feature specified has expired
Recommended Action If this message recurs, customer should buy the license from Cisco since feature will not run
Error Message%LICENSE-2-IPC_INIT : License IPC subsystem could not be initialized: %s
Explanation License IPC subsystem could not be initialized. The reason for failureis displayed after :
Recommended Action If this error message recurs, please copy the message and and contact the customer service, See whether the system resourcesare available
Error Message%LICENSE-2-LIC_STORAGE : %s
Explanation The IOS licensing subsystem does not have a primary storage
Recommended Action If this error message recurs, please copy the message and and contact the customer service.
Error Message%LICENSE-2-LIC_STORAGE_CORRUPT : %s UDI=%s
Explanation The IOS licensing subsystem detected corrupted storage
Recommended Action If this error message occurs, please reinstall all the licenses.If you do not have the licenses, please contact Cisco with the correctUDI to get all the licenses issued for this particular device.
Error Message%LICENSE-2-NO_MEM : No memory available for %s
Explanation The IOS licensing subsystem could not obtain the memory it needed.
Recommended Action If this error message recurs, attempt to reduce memory usage by reducing the number of router features, or interfaces, enabled. Alternatively, add more memory. To display total memory usage for a router enter show memory summary at the privileged command line prompt. To display buffer usage enter show buffers at the prompt.
Error Message%LICENSE-2-UNRECOVERABLE : The IOS license storage on this device was not recovered. UDI=%s
Explanation The IOS license storage on this device was not recovered
Recommended Action If this error message occurs, please reinstall all the licenses.
Error Message%LICENSE-2-VLS_ERROR : '%s' failed with an error - rc = %d - '%s'
Explanation The IOS licensing subsystem encountered an error with the VLS api
Recommended Action If this error message recurs, please copy the message and and contact the customer service.
Error Message%LICENSE-3-IMPLICIT_LIC : %s
Explanation The IOS licensing subsystem encountered an error while initializing/handling the implicit licenses
Recommended Action If this error message recurs, please copy the message and and contact the customer service.
Error Message%LICENSE-3-IPC_PORT : License %s IPC port %s failed: %s
Explanation License IPC port could not be created. The reason for failureis displayed after :
Recommended Action If this error message recurs, please copy the message and and contact the customer service, See whether the system resourcesare available.
Error Message%LICENSE-3-LIC_PROCESS_CREATION_FAILED : %s
Explanation The IOS licensing subsystem was unable to create a process
Recommended Action If this error message recurs, please copy the message and and contact the customer service, See whether the system resourcesare available.
Error Message%LICENSE-3-SLAVE_REGISTER : License Slave device registration failed : %s
Explanation License Slave registration failed. The reason for failureis displayed after :
Recommended Action If this error message recurs, please copy the message and and contact the customer service, See whether the system resourcesare available.
Error Message%LICENSE-4-EXPIRING : License for feature %s %s will expire in %s. UDI=%s
Explanation License for the feature specified will expire in the specified time.
Recommended Action If this message recurs, customer should buy license for the feature from Cisco since feature will not run after license expiry.
Error Message%LICENSE-4-INSTALL_EXPIRED : Expired license is loaded for feature: %s %s. UDI=%s; StoreIndex=%s
Explanation An expired license is loaded or installed in the system
Recommended Action If you are seeing this message,please buy and install a license for this featureif you plan to use the feature. %LICENSE-4-LIC_AGENT_OFF : License Agent is turned off. UDI=%s
Explanation The License Agent on this device is not running
Recommended Action Please check the device configuration if you need to enable it.
Error Message%LICENSE-4-PRECEDENCE : Setting precedence for feature %s failed with error : %d
Explanation Setting precedence for a grace period license failed. This will causecustomer to use wrong license for the same feature
Recommended Action If this error message recurs, please copy the message and and contact the customer service.
Error Message%LICENSE-6-ANNOTATED : License for feature %s %s has been annotated. UDI=%s; StoreIndex=%s; Comment=%s
Explanation Feature was annotated on this device
Recommended Action none.
Error Message%LICENSE-6-COUNT : Feature %s %s license count changed from %d to %d.
Explanation The feature's maximum licensable count has changed
Recommended Action This is just an informational message todenote count change for particular feature.
Error Message%LICENSE-6-EULA_ACCEPTED : EULA for feature %s %s has been accepted. UDI=%s; StoreIndex=%s
Explanation End User License Agreement was accepted on this device
Recommended Action none.
Error Message%LICENSE-6-INSTALL : Feature %s %s was installed in this device. UDI=%s; StoreIndex=%s
Explanation Feature was installed on this device
Recommended Action none %LICENSE-6-RECOVERED : The IOS license storage on this device was recovered. UDI=%s
Explanation The IOS license storage on this device was recovered
Recommended Action none
Error Message%LICENSE-6-REMOVE : Feature %s %s was removed from this device. UDI=%s; StoreIndex=%s
Explanation Feature was removed from this device
Recommended Action none.
Error Message%LICENSE-6-REVOKED : License for feature %s %s has been revoked. UDI=%s; StoreIndex=%s
Explanation A license is revoked from the system
Recommended Action This is just an informational message to log a message when a license has been revoked.
Error Message%LICENSE-6-VIOLATION : Feature %s %s count violation - count = %d, usage count = %d.
Explanation The feature's count is less than the current usage count
Recommended Action This is just an informational message todenote count change for particular. feature.
LIC_AGENT Messages
Error Message%LIC_AGENT-3-MEMORY : %s
Explanation License Agent subsystem has experienced a problem gettting the required memory to complete this operation.
Recommended Action Check system memory for other memory allocation errors and contact Technical support for problem resolution. In the absence of IOS errors upgrading the memory in the network device may be required.
Error Message%LIC_AGENT-3-UNKNOWN_EVENT : event %d, %s
Explanation License Agent tried to execute an unknown event.
Recommended Action Contact technical support for problem resolution.
Error Message%LIIN-3-SET_ACCESS_FAIL : Installing LIIN interface access control failed
Explanation This error happens when IOS failed to set the access control function for the LIIN, possibly due to IOSd out of memory orcorruption. In this case, LIIN interface setup will not proceed, will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIIN-3-SET_TABLEID_FAIL : Installing %s LIIN interface tableid failed
Explanation This error happens when IOS failed to set tableid into linux kernel, possibly due to either IOSd or kernel out of memory or corruption. In this case, LIIN interface will not have VRF installed for the associated address family. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIIN-3-VRFADD_FAIL : Problem creating vrf
Explanation The LIIN config process failed to allocate a mandatory iVRF. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIIN-3-VRFMODIFY_FAIL : Problem adding LIIN interface to vrf table
Explanation The LIIN config process failed to assign the LIIN interface to its mandatory iVRF. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIIN-3-SET_ACCESS_FAIL : Installing LIIN interface access control failed
Explanation This error happens when IOS failed to set the access control function for the LIIN, possibly due to IOSd out of memory orcorruption. In this case, LIIN interface setup will not proceed, will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIIN-3-SET_TABLEID_FAIL : Installing [chars] LIIN interface tableid failed
Explanation This error happens when IOS failed to set tableid into linux kernel, possibly due to either IOSd or kernel out of memory or corruption. In this case, LIIN interface will not have VRF installed for the associated address family. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIIN-3-VRFADD_FAIL : Problem creating vrf
Explanation The LIIN config process failed to allocate a mandatory iVRF. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LIIN-3-VRFMODIFY_FAIL : Problem adding LIIN interface to vrf table
Explanation The LIIN configuration process failed to assign the LIIN interface to its mandatory iVRF. The LIIN interface will not operate properly and cannot be recovered. Persistent access features and interactive commands will not work.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LSMPI-4-INJECT_FEATURE_ESCAPE : Egress [chars] packet delivered via legacy inject path
Explanation A packet with a CPP supported L3 encapsulation (such as IP) was produced by IOS but delivered to CPP via the L2/legacy inject path instead of the proper L3 inject path. For this packet, outbound features will not be applied and packet accounting will likely be incorrect.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_BADSTATUS : NRP slot %d subslot %d invalid Mailbox status area contents or unreachable.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_CONFIG : NRP slot [dec] subslot [dec] invalid Mailbox config area contents or unreachable.
Explanation The mailbox configuration area contents are invalid or missing.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_CRASHING : NRP slot %d subslot %d crashing.
Error Message%LINECARD-3-NRP_CRASHREBOOT : NRP slot %d subslot %d crashed and rebooted.
Explanation
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_NONOP : NRP slot [dec] subslot [dec] non-operational.
Explanation An NRP slot on the line card has failed.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINECARD-3-NRP_SECONDARYDEAD : NRP slot %d subslot %d reports EHSA secondary down.
Error Message%LINECARD-3-NRP_SECONDARYUP : NRP slot %d subslot %d reports EHSA secondary up.
Error Message%LINECARD-3-NRP_SECONDARY_TO_PRIMARY : NRP slot %d subslot %d EHSA secondary to primary cutover.
Error Message%LINEPROTO-5-UPDOWN : Line protocol on Interface %s, changed state to %s
Explanation The data link level line protocol changed state.
Recommended Action No action is required.
LINK Messages
Error Message%LINK-0-REENTER : Fatal reentrancy, level=%d, intfc=%s
Explanation An internal software error occurred. The system code tried to access a critical data structure which was already in use.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-2-BADVCALL : Interface %s, undefined entry point
Explanation An internal software error occurred. The high-level system code tried to use an unimplemented entry point with the virtual interface descriptor block (IDB) driver.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-2-INTVULN : In critical region with interrupt level=%d, intfc=%s
Explanation An internal software error occurred. The high-level system code tried to call this routine with interrupts enabled.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-2-LINEST : No linestate vector for %s
Explanation An internal software inconsistency occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-2-NOSOURCE : Source idb not set
Explanation An internal software error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LINK-3-BADENCAP : Interface %s, Bad encapsulation code (%d)
Explanation The lower level software was unable to write a MAC header for a datagram. A probable cause is configuration error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-3-BADMACREG : Interface %s, non-existent MACADDR registry for link %d
Explanation An attempt to map a network level address to a MAC level address failed.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-3-BOGUSENCAP : msgtxt_badencap
Explanation A serial interface has been configured with an unknown encapsulation.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-3-COMPREG : Interface %s, non-existent (de)compression registry. Packet dropped
Explanation A software or hardware error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-3-EMPTYPAK : Interface %s, empty packet dequeued; linktype %d, queue %d.
Explanation This message indicates an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-3-FCS_ERROR : [chars] [chars] [chars] [chars]
Explanation The FCS error rate has exceeded the configured threshold.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LINK-3-IDBLISCRE : Unable to create %s interface list
Explanation This message indicates an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-3-IDBLISINS : Not able to insert interface %s into %s list
Explanation This message indicates an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-3-LINK_FAULT : [chars] [chars] [chars] [chars]
Explanation The link state for the port is inactive (down).
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%LINK-3-TOOSMALL : Interface %s, Output runt packet of %d bytes
Explanation An output packet was detected that was smaller than the minimum allowable datagram size. An error in another driver or an error in the system software probably triggered this error message.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-3-UPDOWN : Interface %s, changed state to %s
Explanation The interface hardware went either up or down.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface.
Error Message%LINK-4-BADQID : Interface %s, bad output queue ID specified (%d). Packet dropped
Explanation This message indicates an internal software error.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-4-BRIDGECONFLICT : Interface %s, encapsulated BPDU recvd from %e
Explanation An FCIT running in nonencapsulating transparent mode detected an FDDI bridge running in encapsulation mode on the same fiber. This is an unstable situation and should be corrected. The incoming interface is displayed, along with the FDDI MAC address in standard form.
Recommended Action Upgrade the errant interface to full transparent mode. Copy the error message exactly as it appears, and report it to your Cisco technical support representative.
Error Message%LINK-4-FDDISTAT : Interface %s, FDDI state %s detected
Explanation There was a state change on the FDDI ring.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-4-NOMAC : A random default MAC address of %e has been chosen. Ensure that this address is unique, or specify MAC addresses for commands (such as 'novell routing') that allow the use of this address as a default.
Explanation An addressing inconsistency occurred.
Recommended Action Make sure that this address is unique, or specify MAC addresses for commands such as novell routing that allow the use of this address as a default.
Error Message%LINK-4-NOSSB : SSB deleted with timer running
Explanation An internal software error has occurred. The problem has been corrected, and router operation has not been impaired.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. LOGIN Messages
Recommended Action The following are login messages.
Error Message%LINK-4-TOOBIG : Interface %s, Output packet size of %d bytes too big
Explanation An internal software error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-5-BOOTP : %s address %i, resolved by %i
Explanation An interface's IP address was successfully learned dynamically through BootP. The first address is the learned IP address. The second IP address is the IP address of the BootP server that provided the information.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-5-CHANGED : Interface %s, changed state to %s
Explanation The interface hardware changed state.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-5-LOOPSTATUS : Interface %s, %s
Explanation The interface entered or exited loopback.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-5-RARP : %s address %i, resolved by %i
Explanation The Reverse Address Resolution Protocol (RARP) resolved an IP address.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-5-REMLOOP : Interface %s, remote loop %s %s
Explanation The interface entered or exited a remote loopback.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. %LINK-5-SLARP : %s address %i, resolved by %i
Explanation The Serial Line Address Resolution Protocol (SLARP) resolved an IP address.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-5-SLARP : [chars] address [IP_address], resolved by [IP_address]
Explanation The SLARP has resolved an IP address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LINK-6-BERTMSGS : [chars]
Explanation BERT related information messages.
Recommended Action 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. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LINK-6-BERTSTATUS : Interface %s, %s
Explanation BERT is completed for this interface.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LLC-2-UNEXPECT : LLC2 : %s UNEXPECTED EVENT
Explanation An internal software error was found. A software component is trying to use LLC2 structures that do not exist.
Recommended Action Record the configuration and any information that would be useful in recreating the error and call your technical support representative.
Error Message%LLDP-4-LLDP_NEW_ENTRY : Neighbor record not committed - malloc failure
Explanation LLDP entry creation failed.
Recommended Action Run memory diagnostics. LNM Messages
Recommended Action The following are the link noise monitor messages.
Error Message%LLIST-3-OFFLIST : %s from 0x%x, 0x%x not on list
Explanation An internal inconsistency was detected when an attempt was made to remove an item from a list not on the list.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%LLIST-3-ONLIST : %s to 0x%x, 0x%x on list
Explanation An internal inconsistency was detected when an attempt was made to add an item to a list already on the list.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%LNE_INFO-6-BGP_MSG : %s
Error Message%LNE_INFO-6-EIGRP_MSG : %s
Error Message%LNE_INFO-6-IGRP_MSG : %s
Error Message%LNE_INFO-6-ISIS_MSG : %s
Error Message%LNE_INFO-6-OSPF_MSG : %s
Error Message%LNE_INFO-6-RIP_MSG : %s
LNM Messages
Error Message%LNM-2-REMEXCEED : Interface [chars], noise exceeded above removal threshold
Explanation Noise on the link has exceeded above the threshold value configured for link removal
Recommended Action This link requires administrative attention.
Error Message%LNM-2-REMEXCEEDLASTLINK : Interface [chars], Last link in bundle, noise exceeded above removalthreshold
Explanation Noise on the link has exceeded above the threshold value configured for link removal. However, this link is the last link in the multilink bundle and it is not removed from the service.
Recommended Action This link requires administrative attention.
Error Message%LNM-2-REMFAILED : Interface [chars], failed to remove link from bundle
Explanation Noise on the link has exceeded above the threshold value configured for link removal. However, this link is not removed from the MLP bundle
Recommended Action No Action is required.
Error Message%LNM-2-REMIMPROVE : Interface [chars], noise improved below removal threshold
Explanation Noise on the link has improved and is below the threshold value configured for link removal.
Recommended Action No Action is required.
Error Message%LNM-2-REMOVE : Interface [chars] removed from bundle. Noise exceeded above remove threshold
Explanation Noise on the link has crossed the threshold value configured for link removal.This link is taken out of the MLP bundle. This is critical status for the link. This link is under monitoring state and will be added to the bundle again when the noise level is below the configured value.
Recommended Action This link requires administrative attention.
Error Message%LNM-2-RESTORE : Interface [chars] restored to bundle. Noise improved below removal threshold
Explanation Noise on the link has improved below the threshold value configured for link removal. This link is restored back to MLP bundle.
Recommended Action No action is required.
Error Message%LNM-2-RESTOREFAILED : Interface [chars], failed to restore link to the bundle
Explanation Noise on the link has improved and is below the threshold value configured for link removal. However, the link restore back to the MLP bundle failed
Recommended Action No Action is required. LRE_CPE Messages
Recommended Action The following are LRE CPE initialization messages.
Error Message%LNM-3-GENEVENT : [chars]
Explanation An Error has occured in the link noise monitoring.
Recommended Action Copy the error message exactly as it appears and report it to your technical support representative.
Error Message%LNM-3-LNM_NULLPTR : Controller [chars], driver_data not initialized
Explanation Noise monitoring not properly set up for this controller.
Recommended Action 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LNM-3-MAJWARNEXCEED : Interface [chars], noise exceeded above major warning threshold
Explanation Noise on the link has exceeded above the threshold value configured for major warning level.
Recommended Action This link requires administrative attention.
Error Message%LNM-3-MAJWARNIMPROVE : Interface [chars], noise improved below major warning threshold
Explanation Noise on the link has improved and is below the threshold value configured for major warning level.
Recommended Action No Action is required.
Error Message%LNM-3-MINWARNEXCEED : Interface [chars], noise exceeded above minor warning threshold
Explanation Noise on the link has exceeded above the threshold value configured for minor warning level.
Recommended Action This link requires administrative attention.
Error Message%LNM-3-MINWARNIMPROVE : Interface [chars], noise improved below minor warning threshold
Explanation Noise on the link has improved and is below the threshold value configured for minor warning level.
Recommended Action No Action is required.
Error Message%LNM-4-WARNEXCEED : Controller [chars], noise exceeded LCV warning threshold [dec] / PCV threshold [dec], duration [dec]
Explanation Noise level on the E1/T1 link has exceeded the warning threshold.
Recommended Action Link quality has degraded. Contact T1/E1 link service provider.
Error Message%LNM-4-WARNIMPROVE : Controller [chars], noise improved below LCV threshold [dec] / PCV threshold [dec], duration [dec]
Explanation Noise level on the E1/T1 link has improved below the warning threshold.
Recommended Action Link noise level has improved. LOGIN Messages
Recommended Action The following are Login authentication messages.
Error Message%LNM-5-DISABLED : Interface [chars], noise monitoring disabled for [chars]
Explanation Link Noise Monitoring has been disabledon the specified T1/E1 interface.
Recommended Action This is an information message tonotify that Link Noise Monitoring has been disabled on the T1/E1 link.No user action is required.
Error Message%LNM-5-ENABLED : Interface [chars], noise monitoring enabled for [chars]
Explanation Link Noise Monitoring has been enabledon the specified T1/E1 interface.
Recommended Action This is an information message tonotify that Link Noise Monitoring has been enabled on the T1/E1 link.No user action is required.
Error Message%LNMC-3-BADCLSI : %s primitive not valid for lnm %s %s
Explanation A LAN network manager system error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSICNF : %s Invalid confirm %s %s
Explanation A LAN network manager system error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIDATALEN : %s Bad data len = %d %s
Explanation A LAN network manager system error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIHDRLEN : %s Bad header len = 0x%x %s
Explanation A LAN network manager system error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIIDTYPE : %s Invalid ID type = 0x%x %s
Explanation A LAN network manager system error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information._ERR %LNMC-3-BADCLSIIND : %s Invalid indication %s, %s
Explanation A LAN network manager system error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIIND : [chars] Invalid indication [chars], [chars]
Explanation A LAN network manager system error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIPRIMTYPE : %s Invalid primitive type = 0x%x %s
Explanation A LAN network manager system error occurred.
Recommended Action 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/cisco/web/support/index.html. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%LNMC-3-BADCLSIRET : %s Invalid ret code (0x%x) %s, %s
Explanation A LAN network manager system error occurred.
Recommended Action