Table Of Contents
NETWORK_PORT_SATELLITE Messages
MEM_ECC Messages
The following are ECC controller messages.
Error Message%MEM_ECC-3-BADADDR_MBE : Invalid MBE dram address: [hex] latched by ECC Ctrl
Explanation The address that was found by the ECC control register while an MBE was being detected is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%MEM_ECC-3-BADADDR_MBE_RMW : Invalid MBE dram address: [hex] latched by ECC Ctrl
during a RMW cycleExplanation The address that was found by the ECC control register while an MBE was being detected during a read, modify or write cycle is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%MEM_ECC-3-BADADDR_SBE : Invalid SBE dram address: [hex] latched by ECC Ctrl
Explanation The address that was found by the ECC control register while an SBE was being detected is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%MEM_ECC-3-BADADDR_SBE_RMW : Invalid SBE dram address: [hex] latched by ECC Ctrl
during a RMW cycleExplanation The address that was found by the ECC control register while an SBE was being detected during a read, modify or write cycle is not a valid DRAM address. This condition probably indicates a malfunctioning ECC control register that requires replacement.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%MEM_ECC-2-MALLOC : Attempt to malloc [dec] bytes for the ECC error log failed.
ECC errors will only be reported and not recorded.Explanation Memory could not be allocated for the ECC error log.
Recommended Action If the ystem has only 32 MB of memory, a memory upgrade is recommended. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%MEM_ECC-2-MBE : Multiple bit error detected at [hex]
Explanation A multi-bit uncorrectable error was detected on a CPU read from DRAM.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MEM_ECC-2-MBE_RMW : Multiple bit error detected
at [hex] on a read-modify-write cycleExplanation A multi-bit uncorrectable error was detected during a read-modify- write cycle on a CPU read from DRAM for a non 8-byte access.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MEM_ECC-2-PARITY : Parity error on CPU write to address: [hex]
Explanation Bad parity on data was detected by the ECC Ctrl during a CPU write operation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MEM_ECC-2-PARITY_INFO : Parity error was detected on the
following byte(s) of a double word: [chars] [chars] [chars]Explanation Indicates which bytes of a 64-bit word had bad parity that caused the ECC Ctrl to generated an interrupt.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MEM_ECC-3-SBE : Single bit error detected and corrected at [hex]
Explanation A single-bit correctable error was detected on a read from DRAM.
Recommended Action Enter the show ecc command to display the single-bit errors that have been logged. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MEM_ECC-3-SBE_HARD : Single bit *hard* error detected at [hex]
Explanation A single-bit error that could not be corrected (a "hard" error) was detected during a CPU read from DRAM.
Recommended Action Enter the show memory ecc command to display the single-bit errors that have been logged and display the hard error address locations. Monitor the system by periodically entering the show memory ecc command and replace the DRAM if too many errors are encountered.
Error Message%MEM_ECC-3-SBE_LIMIT : Single bit error detected and corrected
at [hex]Explanation A single-bit correctable error was detected on a CPU read from DRAM.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MEM_ECC-3-SBE_RMW : Single bit error detected and corrected at
[hex] on a read-modify-write cycleExplanation A single-bit correctable error was detected during a read-modify-write cycle on a CPU read from DRAM for a non-eight-byte access.
Recommended Action Enter the show ecc command to display the single-bit errors that have been logged. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%MEM_ECC-3-SBE_RMW_HARD : Single bit *hard* error detected at
[hex] on a read-modify-write cycleExplanation A single-bit uncorrectable hard error was detected during a read-modify-write cycle on a CPU read from DRAM for a non-eight-byte access.
Recommended Action Monitor the system by periodically entering the show memory ecc command and replace the DRAM if too many errors are encountered. Enter the show ecc command to display the single-bit errors that have been logged. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%MEM_ECC-3-SBE_RMW_LIMIT : Single bit error detected and corrected at [hex] on a read-modify-write cycle
Explanation A single-bit correctable error was detected on during a read-modify- write cycle on a CPU read from DRAM for a non-eight-byte access.
Recommended Action Enter the show ecc command to display the single-bit errors that have been logged. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%MEM_ECC-3-SYNDROME_MBE : 8-bit Syndrome for the detected Multi-bit error: [hex]
Explanation A multi-bit error has been detected for the eight-bit syndrome. This value does not indicate the exact positions of the bits in error, but can be used to approximate their positions.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%MEM_ECC-3-SYNDROME_SBE : 8-bit Syndrome for the detected Single-bit error: [hex]
Explanation A single-bit error has been detected for the eight-bit syndrome. This value does not indicate the exact positions of the bits in error, but can be used to approximate their positions.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%MEM_ECC-3-SYNDROME_SBE_LIMIT : 8-bit Syndrome for the detected Single-bit error: [hex]
Explanation A single-bit error has been detected for the eight-bit syndrome. This value does not indicate the exact positions of the bits in error, but can be used to approximate their positions.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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.METOPT Messages
The following are Cisco Optical Networking Systems (ONS) 15540 Extended Services Platform (ESP) messages.
Error Message%METOPT-6-DI_ASSERTED : CDL Defect Indication: [chars] Asserted on interface [chars]
Explanation Some CDL defect indication bits have been asserted on this interface.
Recommended Action Recommended Action Closely monitor the CDL defect indication status.
Error Message%METOPT-6-DI_CLEARED : CDL Defect Indication: [chars] cleared on interface [chars]
Explanation The CDL defect indication status has been changed.
Recommended Action No action is required.
Error Message%METOPT-2-NOPAKBUFFER : No packet buffer available for [chars] interface to send this packet to higher layer
Explanation An attempt to allocate a packet buffer has failed.
Recommended Action Perform one or more of the following actions to remedy the problem:
-Reload the system.
-If a redundant CPU system is present in the system, perform a CPU switchover.METOPT_DRV Messages
The following are Cisco Optical Networking Systems (ONS) 15540 Extended Services Platform (ESP) driver messages.
Error Message%METOPT_DRV-3-REPROGRAM_ERROR : [chars]
Explanation The Metro Optical Reprogram driver encountered an error. The message contains information useful to help identify the nature of the problem.
Recommended Action Retry the reprogram of the card. If the reprogram fails again, remove the card and reinsert it. If the card does not come up, save the console log. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. 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.MFI Messages
The following are MFI MPLS Forwarding Infrastructure messages.
Error Message%MFI-3-BADREADUPDATESIZE : Read update reply message from RP has bad size: [dec]
Explanation read update message does not match the read message parse result.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MFI-3-CLIENT_INTF : [chars]: [hex] [hex]
Explanation Client Interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MFI-3-EVTLOGCAPTURE : Event Logger Capture Error [dec] [dec]
Explanation Failure during Event Logger capture.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MFI-3-EVTLOGCLIENT : Invalid client [dec]
Explanation Invalid client accessed the Event Logger.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MFI-3-EVTLOGCONTROL : [chars]: [dec]
Explanation General Event Logger Controller 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%MFI-3-EVTLOGREGISTER : Event Logger Registration Error [dec] [dec] [dec]
Explanation Failure during Event Logger client registration.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MFI-3-LCPULSE : LC pulse failed: [chars] [dec]
Explanation LC pulse request 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%MFI-3-MFICOMM : [chars]
Explanation An error involving the communications module 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%MFI-3-MFICOMM2 : [chars]: [hex] [hex]
Explanation An error involving the communications module 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%MFI-3-MFICOMM3 : [chars]: [hex] [hex] [hex]
Explanation An error involving the communications module 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%MFI-4-MFICOMM4 : [chars]: [hex] [hex]
Explanation MFI General Communication Module.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MFI-3-MPLS_MTU_SET : [chars] [dec] [chars] [chars] [chars] [dec][chars]
Explanation Most drivers will be able to support baby giants and will gracefully drop packets that are too large. Certain drivers will have packet forwarding problems including data corruption.
Recommended Action Increase the interface mtu on all routers connected to this interface to the needed mtu size by entering the mtu bytes command.
Error Message%MFI-3-NOCLIENTREQ : [chars] [chars]: [dec] [dec] [dec]
Explanation Client reply could not find an outstanding request.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MFI-3-PNDMSGMGR : [chars] [chars] [dec] [dec] [dec]
Explanation Only one outstanding request is allowed from same 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.Error Message%MFI-3-REDISTMGR : Redistribution Manager: [chars] [hex]
Explanation Redistribution 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%MFI-3-REDISTMGR2 : Redistribution Manager: [chars] [hex] [hex]
Explanation Redistribution 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%MFI-4-REDISTMGR3 : Redistribution Manager: [chars] [hex]
Explanation Redistribution 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%MFI-3-REPLYMSGSIZE : Reply message is too large: [chars]: [dec]
Explanation A read update message won't fit into the xdr 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.MFIB Messages
The following are Multicast Forwarding Information Base messages.
Error Message%MFIB-3-NO_SBCTRLFUNC : A[chars] function is required for the MFIB sub-block, but none was provided
Explanation MFIB could not distribute interface information toa linecard due to an internal 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.MFIB_STATS Messages
The following are MFIB statistics messages.
Error Message%MFIB_STATS-2-MFIB_STATS_HW_CAPABILITY : Attempt to modify MFIB [chars] HW stats capability ignored
Explanation The MFIB ignored an illegal change in the HW stats capability mask. Collection of HW statistics and liveness information might be disabled as a result.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.MFR_HAL Messages
The following are messages that appear when configuring MLPPP on Crackerjack.
Error Message%MFR_HAL-4-MODE_CHANGE_TO_HW : Multilink interface [chars] Changed to hardware mode
Explanation MLPPP operation on this interface will now happen on the PA hardware.
Recommended Action No action is required.
Error Message%MFR_HAL-4-MODE_CHANGE_TO_SW : Multilink interface [chars] Changed to software mode
Explanation The configuration on the interface to operate in hardware is unsupported. MLPPP operation on this interface will now happen in the IOS.
Recommended Action Verify and correct your Multilink configuration for this interface if this needs to operate in the hardware mode.
MLP_HAL Messages
The following are messages that appear when configuring MLPPP on Crackerjack.
Error Message%MLP_HAL-4-MODE_CHANGE_TO_HW : Multilink interface [chars] Changed to hardware mode
Explanation MLPPP operation on this interface will now happen on the PA hardware.
Recommended Action No action is required.
Error Message%MLP_HAL-4-MODE_CHANGE_TO_SW : Multilink interface [chars] Changed to software mode
Explanation The configuration on the interface to operate in hardware is unsupported. MLPPP operation on this interface will now happen in the IOS.
Recommended Action Verify and correct your Multilink configuration for this interface if this needs to operate in the hardware mode.
Error Message%MLP_HAL-3-NULL_DATA_STRUCTURE : Data structure [chars] found Null
Explanation Data structure was found NULL.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MLP_HAL-4-QOVERFLOW : Multilink interface [chars] Delayed event handling queue overflow
Explanation QUEUE for handling the configuration over flowed.
Recommended Action Try reconfiguring the failed configuration.
MLSCEF Messages
The following are Multilayer Switching Cisco Express Forwarding messages.
Error Message%MLSCEF-2-EXCESSIVE_FIB_SSRAM_ERRORS : Too many fib uncorrectable ecc error interrupts.
Explanation Number of uncorrectable error interrupts exceeded threshold, bringing down 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%MLSCEF-4-FIB_EXCEPTION : FIB TCAM exception for IPv4 unicast. Packets through some routes will be software switched.
Use "mls cef maximum-routes" to modify the FIB TCAM partition.Explanation Either the number of route entries that are installed has exceeded the hardware capacity, or the protocol that generated an exception condition does not have enough route entries reserved. As a result of this condition, some prefixes will be software switched.
Recommended Action Enter the mls cef maximum-routes <protocol> command, with 'protocol' being the MLS CEF protocol used, to increase the maximum number of the routes for the protocol.
Error Message%MLSCEF-4-FIB_EXCEPTION_THRESHOLD : Hardware CEF entry usage is at 95% capacity for [chars] protocol.
Explanation The number of route entries that are installed is about to reach the hardware FIB capacity, or the maximum routes limit set for the specified protocol. If the limit is reached, some prefixes will be software switched.
Recommended Action Enter the mls cef maximum-routes <protocol> global configuration command to increase the maximum number of routes for the protocol. Refer to the configuration manuals for the differing capacity limitations of XL vs non-XL systems, as well as for impacts to other protocols when changing maximum-routes of one protocol. Enter show mls cef summary to see the current usage summary.
MPLS_IPRM Messages
The following are MPLS IP rewrite manager (IPRM) messages.
Error Message%MPLS_IPRM-3-DB : [chars]
Explanation There is an inconsistency in the information required to request labels from or to process labels received from an IP label distribution module.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_IPRM-3-DB_PATH : [chars]
Explanation There is an inconsistency in the information about a prefix path required to request labels from or to process labels received from an IP label distribution module.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_IPRM-3-DB_PNDG_DISC : [chars]
Explanation There is an inconsistency in the information about a temporarily deferred action required to populate MPLS forwarding data structures for a prefix.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_IPRM-3-DB_TABLE : [chars]
Explanation There is an inconsistency in the information about a (vrf) tableid required to request labels from or to process labels received from an IP label distribution module.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_IPRM-3-DB_TRANS : [chars]
Explanation There is an inconsistency in the information about an ongoing transaction required to populate MPLS forwarding data structures for a prefix.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_IPRM-3-INTERNAL : [chars]
Explanation An operation that is required for proper operation of the IP rewrite manager has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%MPLS_IPRM-3-REWRITE_DEL : [chars]
Explanation An attempt to delete MPLS forwarding information for the specified prefix has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_IPRM-3-REWRITE_GET : [chars]
Explanation An attempt to access MPLS forwarding information for the specified prefix has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_IPRM-3-REWRITE_UPD : [chars]
Explanation An attempt to update MPLS forwarding information for the specified prefix has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_IPRM-3-WALK : [chars]
Explanation A request by an IP label distribution module (e.g., LDP, BGP) to walk a CEF table cannot be handled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.MPLS_PACKET Messages
The following are MPLS packet messages.
Error Message%MPLS_PACKET-3-FWDDISABLE : MPLS [chars] forwarding path disabled
Explanation MPLS forwarding plane disabled.
Recommended Action This is an informational message only. No action is required.
Error Message%MPLS_PACKET-3-FWDREENABLE : MPLS [chars] forwarding path reenabled
Explanation MPLS forwarding plane re-enabled.
Recommended Action This is an informational message only. No action is required.
Error Message%MPLS_PACKET-4-NOLFDSB : MPLS packet received on non MPLS enabled interface [chars] L3 type [hex] label {[dec] [dec] [dec] [dec]}
Explanation MPLS packets received on an interface are being dropped as the interface is not setup to handle MPLS. This message might be seen when an mpls application is disabled on a interface and should go away when the upstream neighbor has reprogrammed its cef/mpls entries.
Recommended Action If an MPLS application has just be disabled and traffic is flowing, then the message is expected and should be ignored. If the message recurs in steady state, you should monitor the network for attacks and report the occurrence to Cisco.
MPLS_TE Messages
The following are Label Switch Path (LSP) tunnel messages.
Error Message%MPLS_TE-2-ADJ_WALK_ERR : [chars]
Explanation Error during bundle adjacency walk.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_TE-2-BUNDLE_INSERT : [chars][chars]
Explanation Request for inserting a traffic engineering tunnel bundle 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%MPLS_TE-3-LSDERROR : [chars]: [chars] [chars]
Explanation A traffic engineering request to the label switching database encountered an unexpected 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. 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%MPLS_TE-4-LSPREJECT : LSP [chars] rejected: matching passive TE tunnel [chars]
Explanation An RSVP Path message for an LSP for a tunnel was rejected with a PathErr message, due to the absence of a properly configured MPLS passive tunnel interface which is administratively up.
Recommended Action Create and/or properly configure an MPLS passive tunnel interface which will match the rejected LSP, and ensure that it is administratively up, or modify the tunnel interface configuration at the head end of the tunnel.
Error Message%MPLS_TE_PCALC-2-INVLD_RTR_FRAGMENT : Router id ([IP_address]) received from [chars] in fragment [int], previously received in fragment [int]
Explanation Received Router ID in multiple fragments.
Recommended Action Locate the problem router and copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_TE-2-UNSUPPORTED_LINK_TYPE : [chars]
Explanation Unsupported link 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.MPLS_TE_AUTOMESH Messages
The following are MPLS TE Automesh messages.
Error Message%MPLS_TE_AUTOMESH-5-AUTOTEMPLATE_HWIDB_DELETE : Failed to delete hwidb for Auto-Template [dec] index [dec]
Explanation Deletion of Auto-Template interface 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.MPLS_TE_LM Messages
The following are MPLS TE Link Management messages.
Error Message%MPLS_TE_LM-3-LSP_BAD_ENCODING_TYPE : LSP [chars] requesting Encoding Type [[chars]] that is unsupported on interface [chars].
Explanation The indicated TE LSP, routed on the indicated interface, requested an Encoding Type that is unsupported on the interface. The requested value appears in the Generalized Label Request.
Recommended Action Verify that the head end originating the TE LSP has a Generalized Label Request that is specifying an Encoding Type acceptable to the interface in question. If not, alter the head end configuration to request an LSP with an appropriate value, or cause the LSP to be routed on a different interface. 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%MPLS_TE_LM-3-LSP_BAD_ENCODING_TYPE_REQUESTED : [chars]: LSP requests encoding type unsupported or invalid
Explanation The indicated TE LSP, routed on the indicated interface, requested a Switching Type that is unsupported on the interface. The requested value appears in the Generalized Label Request.
Recommended Action Verify that the head end originating the TE LSP has a Generalized Label Request that is specifying a Switching Type acceptable to the interface in question. If not, alter the head end configuration to request an LSP with an appropriate value, or cause the LSP to be routed on a different interface. 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%MPLS_TE_LM-3-LSP_BAD_GPID : LSP [chars] requesting G-PID [[chars]] that is unsupported on interface [chars][chars].
Explanation The indicated TE LSP, routed on the indicated interface, requested a (Generalized) Payload Identifier unsupported on the interface. The requested value appears in the Label Request/Generalized Label Request.
Recommended Action Verify that the head end originating the TE LSP has a Label Request that is specifying a PID acceptable to the interface in question. If not, one possibility is to alter the head end configuration to request an LSP with an appropriate value. Alternatively, if this error is generated at the penultimate hop of an LSP where the endpoint is advertising an implicit-null label (penultimate hop popping is in use), alter the endpoint to advertise an explicit-null label. 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. Provide the output of show tech-support and a topology diagram showing the hops in the LSP, marking each hop with the vendor/software, and identify which hop is the IOS device issuing the error message.Error Message: [chars]: LSP requests G-PID unsupported or invalid
Explanation The indicated TE LSP requested a GPID that is unsupported on the interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_TE_LM-3-LSP_BAD_SWITCHING_TYPE : LSP [chars] requesting Switching Type [[chars]] that is unsupported on interface [chars].
Explanation The indicated TE LSP, routed on the indicated interface, requested a Switching Type that is unsupported on the interface. The requested value appears in the Generalized Label Request.
Recommended Action Verify that the head end originating the TE LSP has a Generalized Label Request that is specifying a Switching Type acceptable to the interface in question. If not, alter the head end configuration to request an LSP with an appropriate value, or cause the LSP to be routed on a different interface. 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. Pprovide the output of show tech-support and a topology diagram showing the hops in the LSP, marking each hop with the vendor/software, and identify which hop is the IOS device issuing the error message.Error Message: [chars]: LSP requests switching type [[chars]] unsupported on link [[chars]]
Explanation The indicated TE LSP, routed on the indicated interface, requested a Switching Type that is unsupported on the link.
Recommended Action copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.MPLS_VPN_HA Messages
The following are MPLS VPN HA checkpoint label bindings messages.
Error Message%MPLS_VPN_HA-3-CF_GEN_ERROR : [chars]
Explanation MPLS VPN HA client CF related 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%MPLS_VPN_HA-3-CLIENTREG : [chars]
Explanation MPLS VPN HA failed to register to CF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_VPN_HA-3-DBOPERATION : [chars] RD [chars], [IP_address]/[dec], label [dec]
Explanation MPLS VPN HA Checkpoint database 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%MPLS_VPN_HA-7-LABELFREE : [chars] [dec]
Explanation MPLS VPN Label Manager failed to free label.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLS_VPN_HA-7-MALLOCFAIL : [chars]
Explanation MPLS VPN HA failed to allocate 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%MPLS_VPN_HA-3-SIZEMISMATCH : Label table size ([dec]) mismatch, get label tableid failed.
Explanation MPLS VPN HA Label Table size mismatch.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl</