Table Of Contents
LC Messages
The following are line card messages.
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. 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_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-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-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.
LC_10G Messages
The following are 10G trunk card messages.
Error Message%LC_10G-3-ACCESS_FAIL : [chars] Access Fail
Explanation Read/Write to LRC scratch pad register 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. 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_10G-3-AFOVR_ERR : Autofailover Error [chars]
Explanation Optical switch failed to auto failover.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_10G-3-AFOVR_EVNT : Autofailover event occured [chars]
Explanation Autofailover occured.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_10G-3-CDL_HEC_ERR_THR : CDL HEC Errors threshold [chars]
Explanation CDL HEC Errors crossed threshold limit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_10G-3-CRC_ERR_THR : CRC Errors threshold [chars]
Explanation CRC Errors crossed threshold limit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_10G-3-ETH_DCC_LPBK_FAIL : EthernetDcc loopback Fail
Explanation Loopback through Ethernet backplane 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. 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_10G-3-IDPROM_ACCESS_FAIL : Idprom Access Fail
Explanation Reading and checking of Idprom 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. 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_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. 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_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. 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_10G-3-INT_LPBK_FAIL : Internal Card loopback Fail
Explanation Loopback internal to the card 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. 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_10G-3-LASER_AUTO_SHUTDOWN : Auto Laser Shutdown [chars]
Explanation Auto Laser Shutdown.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_10G-3-LASER_BIAS_ALARM : Optic Laser Bias Alarm [chars]
Explanation Optics Laser Bias 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. 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_10G-3-LASER_TEMP_ALARM : Optic Laser Temperature Alarm [chars]
Explanation Optics Laser Temp 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. 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_10G-3-LASER_TX_FAULT : Optic Laser Transmit Fault [chars]
Explanation Optics Laser Tx Fault.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_10G-3-LOSS_OF_LOCK : Transceiver Loss of Lock [chars]
Explanation Receiver has lost the lock on 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. 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_10G-3-LOSS_OF_SYNC : Transceiver Loss of Sync [chars]
Explanation Decoder has lost the 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. 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_10G-3-LPBK_THRU_PSC_FAIL : loopback through PSC Fail
Explanation Internal card loopback through PSC 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. 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_10G-3-MIB_AFOVR_ERR_ALM : Optical Switch Error [chars] [chars] [chars]
Explanation Optical Switch 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. 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_10G-3-MIB_AFOVR_EVNT_ALM : AutoFailover Event [chars] [chars] [chars]
Explanation AutoFailover Event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_10G-3-MIB_AUTO_LASER_SHUTDOWN : Auto Laser Shutdown [chars] [chars] [chars]
Explanation Automatic Laser Shutdown 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. 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_10G-3-MIB_LASER_BIAS_ALM : Laser Bias Alarm [chars] [chars] [chars]
Explanation Trunk Laser Bias 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. 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_10G-3-MIB_LASER_TEMP_ALM : Laser Temperature Alarm [chars] [chars] [chars]
Explanation Trunk Laser Temperature 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. 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_10G-3-MIB_LASER_TX_FLT_ALM : Laser Transmit Fault [chars] [chars] [chars]
Explanation Trunk Laser Transmit Fault.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_10G-3-MIB_LOSS_OF_LOCK_ALM : Loss of Lock [chars] [chars] [chars]
Explanation Loss of Lock.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_10G-3-MIB_LOSS_OF_SYNC_ALM : Loss of Sync [chars] [chars] [chars]
Explanation Loss of 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. 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_10G-3-SYML_ERR_THR : Symbol Errors threshold [chars]
Explanation Symbol Errors crossed threshold limit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.LC_2P5G Messages
The following are 2.6G trunk card messages.
Error Message%LC_2P5G-3-ACCESS_FAIL : Access Fail [chars]
Explanation Read/Write to LRC scratch pad register 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. 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_2P5G-3-AFOVR_ERR : Autofailover Error [chars]
Explanation Optical switch failed to auto failover.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_2P5G-5-AFOVR_EVNT : Autofailover event occured [chars]
Explanation An auto failover event occured.
Recommended Action No action is required.
Error Message%LC_2P5G-3-CDL_HEC_ERR_THR : CDL HEC Errors threshold [chars]
Explanation CDL HEC Errors crossed threshold limit.
Recommended Action Check that the cables connected to the Rx transciever are plugged in and 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.Error Message%LC_2P5G-3-CRC_ERR_THR : CRC Errors threshold [chars]
Explanation CRC Errors crossed threshold limit.
Recommended Action Check that the cables connected to the Rx transciever are plugged in and unbent and untwisted. Check the condition of the cablesn. 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.Error Message%LC_2P5G-3-ETH_DCC_LPBK_FAIL : EthernetDcc loopback Fail [chars]
Explanation Loopback through Ethernet backplane 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. 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_2P5G-3-IDPROM_ACCESS_FAIL : Idprom Access Fail [chars]
Explanation Reading and checking of Idprom 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. 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_2P5G-2-INTERNAL_CRITICAL : [chars]
Explanation An Internal critical 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%LC_2P5G-3-INTERNAL_ERROR : [chars]
Explanation An Internal 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%LC_2P5G-3-INT_LPBK_FAIL : Internal Card loopback Fail [chars]
Explanation Loopback internal to the card 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. 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_2P5G-5-LASER_AUTO_SHUTDOWN : Auto Laser Shutdown [chars]
Explanation Automatic laser shutdown event occurred.
Recommended Action No action is required.
Error Message%LC_2P5G-3-LASER_DEGRADATION_ALARM : Optic Laser Degradation Alarm [chars]
Explanation Optics laser module's transmit power 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. 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_2P5G-3-LASER_NO_LIGHT_ALARM : Optic Laser Loss of Light Alarm [chars]
Explanation Optics laser loss of light alarm.
Recommended Action Check the cables connected to the Rx transciever to be plugged in and unbent/untwisted. Check the physical nature of the cables to be in good condition. Check the physical state (transmit laser power level) and configuration of remote end connected to the port associated. If the 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. lso 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_2P5G-3-LASER_TX_FAULT : Optic Laser Transmit Fault [chars]
Explanation Optics laser transmit fault.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_2P5G-3-LASER_WAVE_LN_DEV_ALARM : Optic Laser Wavelength Deviation Alarm [chars]
Explanation Optics laser module's wavelength 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. 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_2P5G-3-LOSS_OF_LOCK : Transceiver Loss of Lock [chars]
Explanation Receiver has lost the lock on the incoming signal.
Recommended Action Check the cables connected to the Rx transciever to be plugged in and unbent/untwisted. Check the physical nature of the cables to be in good condition. Check the physical state (transmit laser power level) and configuration of remote end connected to the port associated. If the 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%LC_2P5G-3-LOSS_OF_SYNC : Transceiver Loss of Sync [chars]
Explanation Decoder has lost the frame synchronization.
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.Error Message%LC_2P5G-3-LPBK_THRU_PSC_FAIL : loopback through PSC Fail [chars]
Explanation Internal card loopback through PSC 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. 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_2P5G-3-MIB_AFOVR_ERR_ALM : Optical Switch Error [chars] [chars] [chars]
Explanation Optical switch failed to auto failover.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_2P5G-5-MIB_AFOVR_EVNT_ALM : AutoFailover Event [chars] [chars] [chars]
Explanation An auto failover event occurred.
Recommended Action No action is required.
Error Message%LC_2P5G-5-MIB_AUTO_LASER_SHUTDOWN : Auto Laser Shutdown [chars] [chars] [chars]
Explanation Automatic laser shutdown event occurred.
Recommended Action No action is required.
Error Message%LC_2P5G-3-MIB_CVRD_ERR_THR : CVRD Error Threshold Exceeded [chars] [chars] [chars]
Explanation 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.Error Message%LC_2P5G-3-MIB_LASER_DEG_ALM : Laser Degradation Alarm [chars] [chars] [chars]
Explanation Optics laser module's transmit power 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. 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_2P5G-3-MIB_LASER_TX_FLT_ALM : Laser Transmit Fault [chars] [chars] [chars]
Explanation Optics laser transmit fault.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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_2P5G-3-MIB_LASER_WV_DEV_ALM : Laser Wavelength Deviation Alarm [chars] [chars] [chars]
Explanation Optics laser module's wave length 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. 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_2P5G-3-MIB_LOSS_OF_LOCK_ALM : Loss of Lock [chars] [chars] [chars]
Explanation Receiver has lost the lock on the incoming signal.
Recommended Action Check the cables connected to the Rx transciever to be plugged in and unbent/untwisted. Check the physical nature of the cables to be in good condition. Check the physical state (transmit laser power level) and configuration of remote end connected to the port associated. If themessage 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%LC_2P5G-3-MIB_LOSS_OF_SYNC_ALM : Loss of Sync [chars] [chars] [chars]
Explanation Decoder has lost the frame synchronization.
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.Error Message%LC_2P5G-3-MIB_NO_LIGHT_ALM : Laser Loss of Light Alarm [chars] [chars] [chars]
Explanation Optics laser loss of light alarm.
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.Error Message %LC_2P5G-3-SYML_ERR_THR: Symbol Errors threshold [chars]
Explanation 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
The following are line card crash information 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-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-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%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-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
The following are internet router line card logger messages.
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
The following are Cisco Optical Networking Systems (ONS) 15540 Extended Services Platform (ESP) messages.
Error Message%LCMDC-3-FPGA_ACCESS_FAIL : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation Submit An alarm - Prints out descriptive 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%LCMDC-6-TX_ALARM_SOAK : [chars]
Explanation Submit An alarm - Prints out descriptive 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.LDP Messages
The following are Label Distribution Protocol (LDP) 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 (DoD) mode; for frame-based links when there is disagreement, the protocol requires that the session use Downstream Unsolicited (DU) 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 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%LDP-5-CLEAR_CHKPT : Clear LDP bindings checkpoint state ([chars]) by [chars]
Explanation Checkpoint state for one or more LDP bindings has been reset.
Recommended Action No action is required.
Error Message%LDP-5-GR : [chars]
Explanation An informational LDP notice was generated for a Graceful Restart event.
Recommended Action No action is required.
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-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
The following are Label Forwarding Database messages.
Error Message%LFD-2-AVL : [chars] [hex]
Explanation AVL tree operation 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. 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-BADEXEC : Unexpected Code Execution: [chars] [dec]
Explanation Unexpected Code Execution.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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-BADFRRTYPE : illegal frr type: [dec]
Explanation FRR request type 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. 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-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-CHUNKMGR : chunk mgr: [chars] [hex]
Explanation Chunk manager 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. 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-CHUNKMGRALLOC : failed chunk alloc: [chars]
Explanation Chunk alloc() 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. 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-CHUNKMGRDEALLOC : failed chunk dealloc: [chars]
Explanation Chunk free() 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. 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-EVTLOGBADSOURCE : Illegal log event source: [dec]
Explanation Illegal event found in log 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. 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-FPIHANDLER : LFD SSS Handler: [chars]
Explanation Error in 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. 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-2-FPIHANDLER3 : [chars] [hex] [hex] [hex]
Explanation FPI Handler 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. 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-FPITYPEWRONG : Require fpi type [chars], get fpi type [chars]
Explanation Unmatched FPI 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. 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-INTFDB : intf db: [chars] [hex]
Explanation Interface db 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. 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-INTFDB2 : intf db: [chars] [hex] [hex]
Explanation Interface db 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. 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-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-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-LTABLEMEM : Cannot allocate new mpls table [dec] of size [dec] needed for entry [dec]
Explanation There is not enough contiguous memory 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-4-NOFIBIDB : [chars] - ifnum [dec]
Explanation Fibidb missing on linecard.
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. 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 Resource Failure: [chars] [dec].
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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-NULLADJACENCY : NULL Adjacency
Explanation NULL adjacency 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. 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-NULLFIBIDB : NULL FIB IDB: [chars] [dec]
Explanation NULL FIB IDB 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. 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-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-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-3-REWMGR : Rewrite Manager: [chars] [hex]
Explanation Rewrite Manager 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. 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-REWMGR2 : [chars] [hex] [hex]
Explanation Rewrite lookup failed due to FPI inconsisency.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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-SM : [chars] [dec]
Explanation State Machine error: [chars] [dec].
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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-SMBADEVENT : Unexpected event [chars] for state [chars]
Explanation The LFD received an unexpected event 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. 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-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-3-UPDATEHANDLER2 : [chars] [hex] [hex]
Explanation Error in update 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. 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-UPDATEHANDLER3 : [chars] [hex] [hex] [hex]
Explanation Error in update 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. 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-UPDATEHANDLERFPI : No handler installed: fpi=[dec] handler type=[chars]
Explanation No handler 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. 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.LI Messages
The following are Cisco C7600 Lawful Intercept messages.
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.
LINK Messages
The following are data link messages.
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-3-FCS_ERROR : [chars] [chars] [chars] [chars]
Explanation The FCS Error rate exceeds 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. 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 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. 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.LLDP Messages
The following are Link Layer Discovery Protocol messages.
Error Message%LLDP-4-LLDP_NEW_ENTRY : Neighbor record not committed - malloc failure
Explanation LLDP entry creation failed.
Recommended Action Run memory diagnostics.
LRE_CPE Messages
The following are LRE CPE initialization messages.
Error Message%LRE_CPE-3-INVALIDMODE : CPE on interface [chars] is in invalid mode [chars].
Explanation The CPE is in an inconsistent mode; for example, the model number might imply a MAC mode while the CPE is in a PHY mode.
Recommended Action Use the command show controllers lre cpe mfg to verify that the CPE Model Number string is correct. Use the command hw-module slot <slot> lre upgrade remote to ensure that the CPE has the latest supported firmware. If the CPE's Model Number and firmware are correct, enter the interface configuration command shutdown followed by the no shutdown command to force the switch to re-read CPE information. 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%LRE_CPE-3-INVALIDPATCH : CPE on interface [chars] has invalid LRE firmware.
Explanation The LRE firmware header does not have a valid signature, or the header information on the specified firmware is inconsistent with the contents of the firmware.
Recommended Action Upgrade the firmware on the CPE to the latest supported one by entering the command hw-module slot <slot> upgrade lre remote.
Error Message%LRE_CPE-3-INVALIDPHY : CPE on interface [chars] has an unsupported Ethernet PHY.
Explanation The Ethernet PHY device on the CPE attached to the interface specified in the message is not supported. This error occurs when the switch cannot recognize the PHY identifier of the PHY device(s) on the CPE. The reason could be one of the following:
The IOS version running on the switch is not compatible with this CPE,
the CPE is not a Cisco-supported one or,
the switch did not correctly read the PHY identifier from the CPE.Recommended Action Verify that the CPE is a Cisco-supported one. Enter the command show controllers lre cpe mfg to verify that the CPE Model Number string is correctly set. If the IOS version and CPE model number look correct, enter the interface configuration command shutdown followed by the command no shutdown to force the switch to read the PHY identifer again. As a last resort, power cycle the CPE. 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%LRE_CPE-3-NOVERCKSUM : Could not fetch CPE firmware version and checksum on interface [chars].
Explanation The system could not obtain the CPE firmware version and checksum. If the CPE has the latest firmware, and the CPE Model Number is correct, the most likely cause for this error is that the LRE link between the switch and the CPE is of poor quality.
Recommended Action Enter the command show controllers lre cpe mfg to verify that the CPE Model Number string is correctly set for this CPE. Enter the command hw-module slot <slot> lre upgrade remote to ensure that the CPE has the latest firmware. Enter the interface configuration command shutdown followed by no shutdown to force the switch to re-fetch the CPE firmware version and checksum. As a last resort, power cycle the CPE. 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%LRE_CPE-5-SSNCHANGED : CPE unit on interface [chars] changed.
Explanation The CPE system serial number changed. This condition usually means that the CPE unit on this interface was replaced.
Recommended Action No action is required.
Error Message%LRE_CPE-3-UNKNOWNMODEL : CPE has unrecognizable model number [chars] on interface [chars]
Explanation The model number string in the CPE does not match a known CPE model number.
Recommended Action Enter the show controllers lre cpe mfg command to examine the Model Number of the CPE. Verify that the Model Number is a Cisco-supported one. Enter the interface configuration command shutdown followed by no shutdown to force the switch to re-read the CPE Model Number. 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%LRE_CPE-3-WRONGAPPVER : CPE on interface [chars] reported unsupported version of application firmware [chars].
Minimum application firmware version needed [chars]Explanation Each CPE requires a currently-supported application firmware version for it to function correctly. This CPE has a application firmware version that predates the earliest supported version.
Recommended Action Application firmware is not currently used on the CPE. This message is for future use.
Error Message%LRE_CPE-3-WRONGBOOTVER : CPE on interface [chars] reported unsupported version of bootloader firmware [chars].Minimum bootloader firmware version needed [chars]
Explanation Each CPE requires a currently-supported bootloader firmware version for it to function correctly. This CPE has a bootloader firmware version that predates the earliest supported version.
Recommended Action Upgrade the bootloader firmware on the CPE to a recent version that supports the current requirements by enteringg the command hw-module slot <slot> lre upgrade remote. If the CPE firmware upgrade does not solve the problem, force the switch to re-read the bootloader firmware version by entering the interface configuration command shutdown followed by the command no shutdown. As a last resort power cycle the CPE. 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%LRE_CPE-3-WRONGPATCH :
CPE on interface [chars] has wrong patch version [hex].
Patch version [hex] or higher is needed for this CPE.Explanation Each CPE requires a currently-supported patch version for it to function. This CPE has a patch version that predates the earliest supported version.This condition might occur because the switch was upgraded with the latest Cisco IOS Software image, but the CPE firmware has not been upgraded.
Recommended Action Upgrade the patch on the CPE to the latest supported version by entering the command hw-module slot <slot> upgrade lre remote.
LRE_LINK Messages
The following are LRE link for the Catalyst 2950 LRE switches messages.
Error Message%LRE_LINK-4-HEALTH_MON : Interface [chars], had crossed certain monitored thresholds
Explanation The link status monitor for the interface specified in the messages has detected conditions that have crossed the configured thresholds.
Recommended Action Enter the show controllers lre link monitor command to obtain more information on this error. If the change in operating conditions was unexpected, confirm the configuration settings for the interface.
Error Message%LRE_LINK-3-PROFILE_FAILURE : Interface [chars], profile [chars] failure
Explanation The interface specified in the message did not achieve link with attached profile.
Recommended Action If the link failure was unexpected, confirm the profile settings for the interface.
Error Message%LRE_LINK-3-UPDOWN : Interface [chars], changed state to [chars]
Explanation The interface hardware either has become active (came up) or has become inactive (gone down).
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface.
LRE_LOG Messages
The following are LRE log messages.
Error Message%LRE_LOG-7-LRE_LOGGING : LRE Log:Interface [chars]: State: [chars], Event: [chars], Data: [chars].
Explanation The system has changed its state. The message text provides more information on the nature of the change.
Recommended Action This is an informational message only. No action is required.
LRE_UPGRADE Messages
The following are LRE upgrade for the Catalyst 2950 LRE switches messages.
Error Message%LRE_UPGRADE-4-INIT_RESOURCE : [chars]
Explanation The LRE Upgrade module cannot locate a required resource.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LRE_UPGRADE-3-INIT_SYSTEM : Upgrade module failed to initialize
Explanation The LRE Upgrade module failed to initialize.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LRE_UPGRADE-3-LOCAL_FAILURE : Upgrade of local controller [chars] failed
Explanation LRE upgrade is unable to download firmware to a local 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. 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%LRE_UPGRADE-2-LOCAL_LOAD_FAILURE : The system failed to load the firmware for local PHY controller:[dec]
Explanation An internal system error has occurred while loading the firmware for a local PHY controller.
Recommended Action Power cycle the switch. 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%LRE_UPGRADE-4-TERMINATE : Upgrade on [chars] terminated
Explanation The CPE was disconnected or changed in the middle of an upgrade.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.LSD Messages
The following are MFI label switching database messages.
Error Message%LSD-3-APPMGR : [chars] [hex]
Explanation An error involving the application 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. 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%LSD-2-APP_NOTSUPP : [chars] interface does not support app [chars]
Explanation The specified interface does not support the specified application.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD-2-AVL : [chars] [hex]
Explanation AVL tree operation 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. 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%LSD-4-BADAPI : [chars] from [chars]
Explanation LSD recieved message with invalid parameters.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD-3-BADEXEC : Unexpected Code Execution: [chars] [dec]
Explanation Unexpected code execution, as specified.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD-3-CHUNKMGR : chunk mgr: [chars] [hex]
Explanation Chunk manager 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. 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%LSD-3-CLIENT_CONN : [chars]
Explanation Client connection 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. 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%LSD-3-CLIENT_CONN2 : [chars] [hex] [hex]
Explanation Client connection 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. 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%LSD-3-EVTLOGBADSOURCE : Illegal log event source: [dec]
Explanation Illegal event found in log 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. 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%LSD-2-FPIHANDLER : [chars] [hex]
Explanation FPI Handler 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. 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%LSD-3-INTF_DB : [chars]
Explanation interface db 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. 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%LSD-3-INTF_DB2 : [chars] [hex] [hex]
Explanation interface db 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. 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%LSD-2-INVALID_VAR : [chars]
Explanation Function received invalid parameters.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD-2-INVALID_VAR2 : [chars] [hex] [hex]
Explanation Function received invalid parameters.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD-3-LABEL : [chars][dec]
Explanation Label operation 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. 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%LSD-3-LABEL2 : [chars] [hex] [hex]
Explanation Label 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. 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%LSD-4-LABELFREETO : requested free timeout ([int] ms) by [chars] limited to: [int] ms
Explanation MPLS application label free timeout exceeded maximum allowed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD-4-LABEL_RESOURCE : label range [dec]-[dec] exhausted
Explanation MPLS application is trying to allocate more labels than configuration will allow.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD-3-MULTISERVICEREQ : Multiple outstanding service requests: [dec] [dec]
Explanation Server request attempted with one already outstanding.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD-2-RESOURCE : [chars]
Explanation System resource error occured.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%LSD-3-REWMGR : Rewrite Manager: [chars] [hex]
Explanation Rewrite Manager 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. 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%LSD-3-REWMGR2 : [chars] [hex] [hex]
Explanation Rewrite lookup failed due to FPI inconsisency.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD-2-TESTAPP2 : Test app error: [chars]: [hex] [hex]
Explanation Test application 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. 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%LSD-3-UPDATELISTMGR2 : [chars] [dec] [dec]
Explanation General 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. 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%LSD-3-UPDATELISTMGREXEC : Illegal exec: [chars] [hex]
Explanation Illegal code execution.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.LSD_CLIENT Messages
The following are MFI label switching database messages.
Error Message%LSD_CLIENT-3-CLIENTAPI : Client API error: [chars] [dec]
Explanation Unexpected Client API error.
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 and show running-config commands to gather information 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%LSD_CLIENT-3-INVALID_VAR : [chars]
Explanation Function received invalid parameters.
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 and show running-config commands to gather information 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%LSD_CLIENT-2-MSGHANDLERERR : Client=[dec] Msg type=[dec] Error=[chars]
Explanation LSD Client API message handler error encountered.
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 and show running-config commands to gather information 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%LSD_CLIENT-3-PCHUNK2 : [chars]: [chars] [hex] [hex]
Explanation Parameterized Chunk Manager error occurred.
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 and show running-config and show process commands to gather information 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%LSD_CLIENT-3-UTIL2 : [chars]: [hex] [hex]
Explanation MFI Utilities error occurred.
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 and show running-config commands to gather information 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%LSD_CLIENT-2-XDREXEC : [chars] [dec]
Explanation Illegal code execution in XDR path.
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 and show running-config commands to gather information 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%LSD_CLIENT-2-XDREXEC2 : [chars] [hex] [hex]
Explanation Illegal code execution in XDR path.
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 and show running-config commands to gather information 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.LSD_HA Messages
The following are LSD HA messages.
Error Message%LSD_HA-2-CF : [chars][dec]
Explanation CF related 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. 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%LSD_HA-3-GENERAL : [chars]
Explanation Function received invalid parameters.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD_HA-3-INVALID_VAR : [chars]
Explanation Function received invalid parameters.
Recommended Action CCopy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD_HA-3-LABEL_RANGE_DB : [chars]
Explanation Error happened in label range db.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%LSD_HA-2-RESOURCE : [chars]
Explanation System resource error occured.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%LSD_HA-2-RF : [chars][dec]
Explanation RF related 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. 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%LSD_HA-3-UNSENT_MSG_DB : [chars]
Explanation Error happened in unsent msg db.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.LSPV Messages
The following are MPLS Label-Switched Path Verification messages.
Error Message%LSPV-3-COMM_UNKNOWN_RC : Unexpected oce return code
Explanation Comm module - unexpected oce return code 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. 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.MACSEC Messages
The following are EVC MAC address security violation report messages.
Error Message%MACSEC-4-VIOLATION_RESTR_BD_LIMIT : Attempt to learn [enet] on [chars] caused configured bridge-domain limit ([int]) to be exceeded.
Explanation The bridge-domain specified in the system message is not allowed to learn addresses beyond the limit specified in the system message. A service instance belonging to this bridge-domain received a frame with unknown source MAC address, and if this address is learned it would cause the bridge-domain limit to be exceeded. The address has not been learned.
Recommended Action If the MAC address has to be permitted to be learned, either increase the MAC Security limit configured on the bridge-domain, or clear the MAC address table for the affected bridge-domain to give this address a chance to be learned. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it.
Error Message%MACSEC-4-VIOLATION_RESTR_INST_DENIED : Attempt to learn denied address [enet] on [chars].
Explanation The ethernet service instance specified in the system message has been configured for restrict-mode MAC Security, and has been configured to deny the MAC address specified in the system message. A frame was received from this denied MAC address. The address has not been learned.
Recommended Action If the MAC address has to be permitted to be learned, remove the address from the list of denied addresses on the service instance. Otherwise, this is a genuine violation and no action is needed on the device; instead, locate the cause for the violation and remove it.
Error Message%MACSEC-4-VIOLATION_RESTR_INST_LIMIT : Attempt to learn [enet] on [chars] caused configured service instance limit ([int]) to be exceeded.
Explanation The ethernet service instance specified in the system message has been configured for restrict-mode MAC Security, and is not allowed to learn addresses beyond the limit specified in the system message. This service instance received a frame with unknown source MAC address, and if this address is learned it would cause the limit to be exceeded. The address has not been learned.
Recommended Action If the MAC address has to be permitted to be learned, either increase the MAC Security limit configured on the service instance, or clear the MAC address table for the affected bridge-domain to give this address a chance to be learned. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it.
Error Message%MACSEC-3-VIOLATION_RESTR_RELEARN : Attempt to move [enet] from [[chars]] to [[chars]]
Explanation The MAC address specified in the system message is currently learned on the first ethernet service instance specified in the system message. An ethernet frame with the same MAC address has now been encountered on the second ethernet service instance. This is a violation of MAC Security policy.
Recommended Action If the MAC address has to be permitted to be re-learned on the second service instance, remove the address from the list of addresses permitted on the first service instance (if applicable), and clear the address from the MAC Address Table. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it.
Error Message%MACSEC-4-VIOLATION_RESTR_SYS_CFG_LIMIT : Attempt to learn [enet] on [chars] caused system limit ([int]) to be exceeded.
Explanation It is not allowed to learn addresses beyond the system limit that allowsnumber of permitted + sticky addresses to be configured in the system. A service instance received a frame with unknown source MAC address, and if this address is learned it would cause the system limit to be exceeded. The address has not been learned.
Recommended Action If the MAC address has to be permitted, remove some of permitted or sticky addresses from configuration for the affected service instance to give this address a chance to be learned. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it.
Error Message%MACSEC-4-VIOLATION_RESTR_SYS_LIMIT : Attempt to learn [enet] on [chars] caused system limit ([int]) to be exceeded.
Explanation It is not allowed to learn addresses beyond the system limit. A service instance received a frame with unknown source MAC address, and if this address is learned it would cause the system limit to be exceeded. The address has not been learned.
Recommended Action If the MAC address has to be permitted to be learned, clear the MAC address table for the affected service instance orbridge-domain to give this address a chance to be learned. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it.
Error Message%MACSEC-3-VIOLATION_SHUT_INST_DENIED : Attempt to learn denied address [enet] on [chars]. Service instance will be shutdown.
Explanation The ethernet service instance specified in the system message has been configured for shutdown-mode MAC Security, and has been configured to deny the MAC address specified in the system message. A frame was received from this denied MAC address. The address has not been learned, and additionally the service instance has been shutdown.
Recommended Action If the MAC address has to be permitted to be learned, remove the address from the list of denied addresses on the service instance. Otherwise, this is a genuine violation and no action is needed on the device; instead, locate the cause for the violation and remove it. Once the violation cause has been identified and resolved, re-enable the service instance.
Error Message%MACSEC-3-VIOLATION_SHUT_INST_LIMIT : Attempt to learn [enet] on [chars] caused configured service instance limit ([int]) to be exceeded. Service instance will be shutdown.
Explanation The ethernet service instance specified in the system message has been configured for shutdown-mode MAC Security, and is not allowed to learn addresses beyond the limit specified in the system message. This service instance received a frame with unknown source MAC address, and if this address is learned it would cause the limit to be exceeded. The address has not been learned, and additionally the service instance has been shutdown.
Recommended Action If the MAC address has to be permitted to be learned, either increase the MAC Security limit configured on the service instance, or clear the MAC address table for the affected bridge-domain to give this address a chance to be learned. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it. Once the violation cause has been identified and resolved, re-enable the service instance.
Error Message%MACSEC-3-VIOLATION_SHUT_RELEARN : Attempt to move [enet] from [[chars]] to [[chars]], shutting down the latter
Explanation The MAC address specified in the system message is currently learned on the first ethernet service instance specified in the system message. An ethernet frame with the same MAC address has now been encountered on the second ethernet service instance. This is a violation of MAC Security policy, and as a result the second service instance will be shut down.
Recommended Action If the MAC address has to be permitted to be re-learned on the second service instance, remove the address from the list of addresses permitted on the first service instance (if applicable), and clear the address from the MAC Address Table. If this is a genuine violation, no action is needed on the device; instead, locate the cause for the violation and remove it. Once the violation cause has been identified and resolved, re-enable the service instance.
MCAST Messages
The following are Layer 2 multicast messages.
Error Message%MCAST-3-GROUP_IP_INVALID : MCAST: Invalid group_ip in SSO sync msg for LTL type=[dec], index [hex]
Explanation System 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. 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.MCAST_RP Messages
The following are Cat6000 Multicast messages.
Error Message%MCAST_RP-4-MPLS_PIM_RATE_LIMIT : [chars] when [chars] will reprogram hardware setting for PIM. Please reapply PIM rate-limiter.
Explanation Router Guard or PIM Snooping features require the Catalyst 6500 hardware to be programmed in a manner different from MPLS. Hence these two features are incompatible with MPLS. When either Router Guard or PIM snooping is enabled while MPLS is ON, PIM rate-limiter will not work properly. To fix this issue unconfigure and reconfigure the rate-limiter back using show mls rate-limit multicast ipv4 pim command. The same solution applies to the situation when both Router Guard and PIM snooping are disabled and MPLS is being turned ON.
Recommended Action Unconfigure and reconfigure back PIM rate-limiter by entering the show mls rate-limit multicast ipv4 pim command.
Error Message%MCAST_RP-4-MPLS_PIM_SNOOPING : The MPLS and PIM Snooping features do not work together. Please disable either one.
Explanation The PIM Snooping feature requires the Catalyst 6500 hardware to be programmed in such a way that PIM register messages with MPLS tags might be lost.
Recommended Action Unconfigure either MPLS or PIM Snooping.
MCE Messages
The following are MCE TAM subsystem messages.
Error Message%MCE-3-GTM : [chars]
Explanation MCE GTM interaction 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. 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%MCE-5-TCAM_CARVE : [chars]: [dec]
Explanation MCE TCAM Carve 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. 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%MCE-5-TCAM_DRV : [chars]
Explanation MCE TCAM driver 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. 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%MCE-3-TCAM_FULL_MERGE : [chars]
Explanation MCE TCAM Full 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. 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%MCE-3-TCAM_FULL_NOMERGE : [chars]. Try 'hw-mod tcam compile'
Explanation MCE TCAM Full 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. 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%MCE-3-V6_ACL : [chars]
Explanation MCE IPv6 ACL TCAM 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. 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.MCE_HQF_NP_CLIENT Messages
The following are MCE HQF NP Client messages.
Error Message%MCE_HQF_NP_CLIENT-3-ALLEXISTS : NP Client Previously Defined Software Element - [chars]: [chars] [chars]
Explanation The NP Client has detected a previously defined software element.
Recommended Action Try to reload the IOS image on the affected card or platform. 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%MCE_HQF_NP_CLIENT-2-FATAL : NP Client [chars] : [chars] ([dec], [dec])
Explanation NP Client software detected a critical programming error.
Recommended Action 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%MCE_HQF_NP_CLIENT-3-HQF_NP_CLIENT_GENERAL : [chars] error detected: [chars] [hex] [hex]
Explanation A software programming error for the HQF NP Client was detected.
Recommended Action This software programming error is not considered fatal to the operation of the TT NPs. 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%MCE_HQF_NP_CLIENT-3-INITFAIL : NP Client Initialization Failed - [chars]: [chars] [chars]
Explanation NP Client could not initialize memory needed to service one or more Network Processors.
Recommended Action This error might indicate that an incompatibility exists between the NP firmware and the associate IOS image. Try to reload the IOS image on the affected card or platform. 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%MCE_HQF_NP_CLIENT-3-MAXEXCEED : NP Client Max Services Exceeded - [chars]: [chars] [chars]
Explanation The maximum number NP Client services have been exceeded.
Recommended Action Change the configuration to reduce the number of services configured. 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%MCE_HQF_NP_CLIENT-3-METADATA : [chars] failed: [chars] [[chars]] [chars]
Explanation Processing of the Metadata for the specified Network Processor failed. The specified Network Processor will fail to operate.
Recommended Action Try to reload the Network Processor microcode. 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%MCE_HQF_NP_CLIENT-3-NOMEM : Memory Allocation Failure - [chars]: [chars] [chars]
Explanation NP Client could not allocate required memory needed to service one or more Network Processors.
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, 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%MCE_HQF_NP_CLIENT-3-NOTFOUND : NP Client Software Element Not Found - [chars]: [chars] [chars]
Explanation The NP Client could not locate a required software element.
Recommended Action Try to reload the IOS image on the affected card or platform. 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%MCE_HQF_NP_CLIENT-3-NOTSUP : NP Client Feature Not Supported - [chars]: [chars] [chars]
Explanation The NP Client does not support the specified feature.
Recommended Action Verify that the correct IOS image is loaded on the affected card or platform for the configured features. 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%MCE_HQF_NP_CLIENT-3-NPUNKNOWN : NP Client Unsupported NP - [chars]: [chars] [chars]
Explanation NP Client detected an unsupported NP.
Recommended Action Verify that the correct IOS image is loaded on the affected card or platform for the configured features. 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.MCE_HT Messages
The following are HyperTransport data plane driver messages.
Error Message%MCE_HT-3-HTDPERR : CPU [dec] HTDP error [chars]: [chars]
Explanation The Cobalt3 HTDP generated an 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. 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%MCE_HT-1-INITFAIL_NOBUF : [chars], buffer replacement failed, no buffers available
Explanation The HyperTransport data plane driver could not secure replacement buffers packet reception.
Recommended Action The router either requires more packet memory - consider upgrade. Or some software module is holding onto the receive buffers and not releasing them back to the driver. 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%MCE_HT-3-NOTCOB3 : Device ID seen as [hex], expected [hex]. Bus number [hex] device number [hex].
Explanation The software could not recognize the data plane chip.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MCE_HT-1-RESFAIL : [chars]
Explanation The HyperTransport data plane driver failed to get resources to attach its data structures to the global table. System is running low on 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. 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%MCE_HT-3-TOOBIG : attempt to send giant packet on [chars] ([dec] bytes from offset [dec], max allowed [dec])
Explanation A process inside the router is attempting to send an oversized 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. 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.MCT1E1 Messages
The following are CT1/CE1 shared port adapter messages.
Error Message%MCT1E1-3-AUTODNR : [chars] failed for slot [dec] bay [dec] err [dec]
Explanation AUTODNR/USNDNR process has failed.The SPA and LC are out of sync.This conditionindicates a 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 that you have gathered.Error Message%MCT1E1-3-BERT_OPERATION_ERR : [chars]: BERT operation error on interface [chars] - [chars].
Explanation The SPA reported failure during BERT operation. The current BERT operation will be terminated, but the affected interface might not be operational, if that is the case, enter the shutdown and then no shutdown to let the interface try to recover from this failure.
Recommended Action If manual shutdown and then no shutdown of the interface does not restore the operation, then SPA will need to be reloaded to recover from this failure state.
Error Message%MCT1E1-3-BERT_STOP_ERR : [chars]: Failed to stop BERT operation on interface [chars] - [chars].
Explanation The SPA failed to stop the BERT operation on the indicated interface. The interface might not be functional after this event, if that is the case, enter the shutdownand and no shutdown commands to let the interface try o recover from this failure.
Recommended Action If manual shutdown and then no shutdown of the interface does not restore the operation, then SPA will need to be reloaded to recover from this failure state.
Error Message%MCT1E1-2-EV_DROP : [chars], cmd: [dec], arg0: [dec], arg1: [dec] arg2: [dec] arg3: [dec] reason [chars]
Explanation The SPA driver dropped an event notification command. Counters or line protocols for one or more interfaces or controllers might be incorrect.
Recommended Action Restart any interfaces or controllers that are down. 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%MCT1E1-3-FPGA_CNTR_ERR : [chars]: [dec] [chars] error(s) encountered.
Explanation The SPA driver detected an FPGA error condition on the SPA card. Interface packet error counter corruption might result.
Recommended Action The SPA driver has encountered a parity error on the SPA card. The SPA should continue to function normally. If the error condition recurs, reset the SPA by doing a physical OIR. 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 logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%MCT1E1-3-LOOPBACK_CFG_ERR : [chars]: Loop [chars] configuration error on controller [chars] - [chars][chars].
Explanation The SPA reported failure during setting of loop up/down operation. The current loopback will be terminated, but the affected controller might not be operational, if that is the case, enter the shutdown and no shutdown commands to let the controller try to recover from this failure.
Recommended Action If manual shutdown and then no shutdown of the controller does not restore the operation, then SPA will need to be reloaded to recover from this failure state.
Error Message%MCT1E1-3-TIMEOUT :
[chars]: [chars] failed: [dec], state: [dec], ml_id: [dec] progress: [dec]Explanation Linkrec is stuck at non ready. This condition indicates a 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 that you have gathered.MCU Messages
The following are MCU Port Adapter messages.
Error Message%MCU-1-CONFIGNOTETHER : Cannot configure any of the IPC ethernet interfaces
Explanation The IPC Ethernet interfaces cannot be configured.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MCU-1-DISCOVER : Cannot initialize bay [dec], shutting down bay
Explanation Most likely a system fault .
Recommended Action Reload the router.
Error Message%MCU-3-EREVENT : slot ([dec]):([chars])
Explanation A general failure occured for the printed slot as defined by the failure string.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MCU-3-GENERAL : [chars]
Explanation A general failure occured for the MCU driver as as defined by the failure string.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MCU-6-HWREV : Slot [dec]: HW revision is [dec]
Explanation Hardware revision message.
Recommended Action No action is required.
Error Message%MCU-3-LOWCPU : MCU port adapter in Slot [dec] requires CPU card type NPE400 or higher
Explanation MCU cards are only supported on NPE400 cards and higher.
Recommended Action Upgrade CPU card to NPE400 or higher.
Error Message%MCU-6-OLDHWREV : Slot [dec]: HW revision is below 1.8 - board should be upgraded
Error Message%MCU-5-RESET : MCU port adapter in slot [dec] was reset
Explanation MCU Port adapter was reset.
Recommended Action No action is required.
MCUCLC Messages
The following are MCU CLC Cisco IOS messages.
Error Message%MCUCLC-3-EREVENT : [chars]
Explanation A general failure occured as defined by the failure string.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MCUCLC-3-NOTMCU : PCI device ID seen as [hex], expected [hex]
Explanation The software could not recognize the Sibyte chips.
Recommended Action Power down, reseat the interface card, and reboot. 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%MCUCLC-3-PCIANALYZE : PCI device ([dec]) initialization failed
Explanation PCI device initialization failed.
Recommended Action Most likely a system fault. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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 Faulty cable line cardError Message%MCUCLC-6-PCIENBDISAB : NPE PCI data interface [[dec]]: [chars]
Explanation The NPE PCI data interface has been enabled/disabled.
Recommended Action No action is required.
Error Message%MCUCLC-3-UNKEVENT : [chars]: [dec]
Explanation An unknown event was received by the IOS 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. 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.MCUFSM Messages
The following are MCU Port Adapter FSM messages.
Error Message%MCUFSM-3-BADSLOT : Invalid slot [dec] in function [chars]
Explanation Invalid slot number provided as argument to function.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MCUFSM-1-CARD_LOADING : Card in slot ([dec]) booting: [chars], size [dec] bytes, version [hex], checksum [hex]
Explanation Alert the user that the MCU card in the specified slot is being 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. 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%MCUFSM-3-ENQFAIL : Enqueue of message failed slot ([dec]), major event ([dec])
Explanation Enqueue of a OIR message to an event queue 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. 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%MCUFSM-3-FSMEXECUTE : slot [dec]: fsm execution failed ([dec])
Explanation Failure in the execution of the MCU OIR finite state machine.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MCUFSM-3-GENERAL : [chars]
Explanation A general failure occured in the operation of the state machine as defined by the failure string.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MCUFSM-3-LOADEXIST : slot [dec]: previous download process
Explanation A previous download process exists. A new download cannot start until the previous process terminates. The download retry that has not completed was killed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MCUFSM-3-OPENERR : slot [dec]: failed to open file [chars]
Explanation Microcode download file open operation 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. 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%MCUFSM-3-UNKNOWN : card type is unknown for slot ([dec]) in [chars]
Explanation Enqueue failed to a major event queue.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.MCX Messages
The following are voice port adapter messages.
Error Message%MCX-3-FREEDMFATAL : Bay [dec]: freedm reset, command-status register [hex]
Explanation CHOPIN experienced fatal freedm related 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 information that you have gathered.MDS Messages
The following are multicast distributed switching messages.
Error Message%MDS-2-LC_INVALID_HWIDB_INDEX : Invalid if_index for HWIDB [chars]
Explanation Invalid if_index for HWIDB.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MDS-2-LC_INVALID_HWIDBQ_SIZE : Invalid Q count value
Explanation Invalid Q count value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MDS-2-LC_INVALID_INPUT_IF_INDEX : Invalid input if_index ([hex]) for HWIDB [chars]
Explanation The input hardware IDB interface index 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. 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%MDS-2-LC_INVALID_INPUT_IFNUM : Invalid input if_num ([hex]) for SWIDB [chars]
Explanation The input software IDB interface number 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. 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%MDS-2-LC_INVALID_SWIDB_IFNUM : Invalid if_num for SWIDB [chars]
Explanation Invalid if_num for SWIDB.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MDS-2-LC_INVALID_SWIDBQ_SIZE : Invalid Q count value
Explanation Invalid Q count value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MDS-2-LC_SWIDB_UPDATE_NULL_MVRF : LC received swidb update for if_number [hex] ([chars]) tableid [hex].mvrf pointer for this tableid is NULL.
Explanation The line card received a software IDB update from the Route Processor specifying a multicast VRF table ID for which no multicast VRF exists in the line 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. 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%MDS-4-ROUTELIMIT_ATTEMPT : Attempt to exceed multicast route-limit of [dec]
Explanation The number of multicast routes equals the configured maximum allowed. New routes cannot be added unless the configuration is changed.
Recommended Action If multicast traffic is of any priority among the traffic carried by this router, then use the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required.
MDT Messages
The following are PIM MDT messages.
Error Message%MDT-4-UPDATED_RD_CONFLICT : MDT entry [chars]:([IP_address],[IP_address]) received an update for RD [chars]
Explanation The previously existing entry should have been withdrawn by BGP before sending this conflicting update.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.MDX Messages
The following are MDX messages.
Error Message%MDX-1-DAEMSGSNDFAILED : FAILED to send IPC message of TYPE [chars] to slot [dec] on the DAE, FAIL REASON = [chars]
Explanation IPC failed to send the message across after retries.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%MDX-1-DAENODPENTRY : MDX framework could not find an entry for the DP with dp_id = [dec] on slot = [dec], on DAE
Explanation IPC messages that were sent to the line card have been lost because the line card buffers were being reassigned. As a result of this condition, the MDX DP failed to register. This condition has no effect on system operation.
Recommended Action Disable the SNMP query of the MIBs depending on the value of dp_id as follows: If the dp_id is 1, disable the CISCO-ENHANCED-MEMPOOL-MIB SNMP query. If the dp_id is 2, disable the CISCO-PROCESS-MIB SNMP query. If the dp_id is 3, disable the CISCO-OPTICAL-MONITORING-MIB SNMP query. If the dp_id is 4, disable the CISCO-FABRIC-C12K-MIB SNMP query. You can replace the SNMP query with command line input to obtain the same results. Enter one or more of the following commands to obtain the required information: show processes memory, show processes cpu, show controller optics, show controller fia, show controller xbar, or show controller sca.
Error Message%MDX-1-DAEPORTCREATEFAIL : Could not create IPC port for MDX framework on DAE, FAIL REASON = [chars]
Explanation The IPC port for MDX framework on the DAE (Data Aggregator End) failed because of the reason specified in the message text. This condition has no effect on system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs.
Recommended Action Enter one or more of the following commands to obtain the required information: show processes memory, show processes cpu, show controller optics, show controller fia, show controller xbar, or show controller sca.
Error Message%MDX-1-DAEPORTOPENFAIL : UNABLE to open port to primary RP FAIL REASON = [chars]
Explanation The MDX DAE (Data Aggregator End) IPC port could not be opened, even after three retry attempts. This condition has no effect on system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs.
Recommended Action Enter one or more of the following commands to obtain the required information: show processes memory, show processes cpu, show controller optics, show controller fia, show controller xbar, or show controller sca.
Error Message%MDX-1-DAEPORTOPENFAILRETRY : UNABLE to open port to primary RP try number = [dec],
FAIL REASON = [chars], Will retry againExplanation Opening of MDX DAE IPC port failed, will retry a maximum of three times.
Recommended Action No action is required.
Error Message%MDX-1-DPENTRYEXISTS : An entry already exists for the DP with dp_id [dec] on the DPE, could not create a new entry
Explanation The DP entry that is attempting to be added already exists on the DPE. The new entry could not be created.
Recommended Action No action is required.
Error Message%MDX-1-DPEPORTOPENFAIL : UNABLE to open port to MDX framework on slot = [dec] from DAE, FAIL REASON = [chars]
Explanation The MDX DPE (Data Provider End) IPC port could not be opened because of the reason specified in the message text.
Recommended Action This condition has no effect on system operation. No action is required.
Error Message%MDX-1-DPREGFAILED : DP Registration with MDX framework failed on DPE
Explanation The DP could not be registered with the MDX framework on the DPE (Data Provider End. This condition has no effect on system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs.
Recommended Action Enter one or more of the following commands to obtain the required information: show processes memory, show processes cpu, show controller optics, show controller fia, show controller xbar, or show controller sca.
Error Message%MDX-1-IPCMSGSNDFAILED : FAILED to send IPC message of TYPE [chars] to DAE, FAIL REASON = [chars]
Explanation The MDX component could not send the IPC message because of the reason specified in the message text.
Recommended Action This condition has no effect on system operation. No action is required.
Error Message%MDX-1-IPCMSGUNAVAIL : Request for IPC buffer failed for size = [int]
Explanation An IPC buffer request returned NULL. The IPC has run out of buffer space.
Recommended Action Increase the IPC cache by entering the ipc cache <size> command.
Error Message%MDX-1-MSG : [chars]
Explanation An internal error regarding the MDX facility 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. lso 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%MDX-1-NODPENTRY : MDX framework could not find an entry for the DP with dp_id = [dec]
Explanation The entry for the DP does not exist in the MDX framework. A possible reason for this error is that the DP has not registered with the framework. This condition has no effect on system operation, except that the MDX framework will not be able to obtain the requested data from the MIBs.
Recommended Action Enter one or more of the following commands to obtain the required information: show processes memory, show processes cpu, show controller optics, show controller fia, show controller xbar, or show controller sca.
Error Message%MDX-1-NOMGDTIMERCNTXT : The expired timer does not have a timer context
Explanation MDX framework found a managed timer that does not have a context.
Recommended Action This condition has no effect on system operation. No action is required.
Error Message%MDX-1-PORTCREATEFAIL : Could not create IPC port for MDX Framework, FAIL REASON = [chars]
Explanation An IPC port could not be opened for the MDX framework even after three retry attempts.
Recommended Action This condition has no effect on system operation. No action is required.
Error Message%MDX-1-PORTCREATEFAILRETRY : Could not create IPC port for MDX framework try number = [dec], FAIL REASON = [chars], Will retry again
Explanation IPC Port creation failed. The system will retry a maximum of three times.
Recommended Action No action is required.
Error Message%MDX-1-PORTREGFAIL : Could not Register IPC port for MDX framework FAIL REASON = [chars]
Explanation The IPC Port could not be registered with the IPC master, even after three retry attempts.
Recommended Action This condition has no effect on system operation. No action is required.
Error Message%MDX-1-PORTREGFAILRETRY : Could not Register IPC port for MDX framework try number = [dec], on slot = [dec], FAIL REASON = [chars], Will retry again
Explanation IPC Port registration with IPC master failed. The system will retry a maximum of three times.
Recommended Action No action is required.
Error Message%MDX-1-SIZEMISMATCH : Recieved an IPC message with inconsistent size compared to the MDX TU in its data region
Explanation The size of the IPC message that was received by the MDX framework is not consistent when it is compared to the MDX TU.
Recommended Action This condition has no effect on system operation. No action is required.
Error Message%MDX-1-UNKNOWNMSGTYPE : The rcvd msg-type is not supported, msg-type [chars]
Explanation The msg-type that was received is not supported by the MDX framework.
Recommended Action This condition has no effect on system operation. No action is required.