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
Explanation A single-bit correctable error was detected on a read from DRAM. The show ddr command can be used to dump Single-bit errors logged thus far.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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%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.
MLS_RATE Messages
The follwing are the MLS_RATE messages.
Error Message%MLS_RATE-4-ENABLING_FIB_GLEAN_RECEIVE : [chars] will be subject to the output ACLs of the input VLAN
Explanation When the FIB glean or FIB receive rate limiters are enabled, adjacency redirect is used. The router performs an egress lookup on the incoming interface and the result is applied on the incoming packets.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.MLSCEF Messages
The following are Multilayer Switching Cisco Express Forwarding messages.
Error Message%MLSCEF-2-EXCESSIVE_FIB_CORR_SSRAM_ERRORS : Too many fib correctable ecc error interrupts.
Explanation Number of correctable error interrupts exceeded threshold of 1000 correctable EC.
Recommended Action Collect the outputs of the show mls cef hardware, show mls cef log and show ver commands. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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%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.
Error Message%MLSCEF-2-FIB_TCAM_WRITE_INCONSISTENCY : FIB TCAM Mismatch for [chars]: Index: [dec]
Expected: Entry: [hex]-[hex]-[hex]
Hardware: Entry: [hex]-[hex]-[hex]
Explanation Possible problem in writing to the specified FIB TCAM entry. The specific entry could be bad.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Collect the outputs of the show mls cef hardware, show mls cef log and show ver commands. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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%MLSCEF-2-HARDWARE_LIMIT_REACHED : The number of CEF entries have far exceeded the supported hardware FIB capacity. Freezing the hardware FIB or reloading the system.
Explanation The number of route entries that are installed has far exceeded the supported hardware FIB capacity. No more free index available for CEF entry. Freezing hardware FIB if mls cef error action freeze is present in the configuration, otherwise reloading the system.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.MPLSIFMIB Messages
The following are the MPLSIFMIB messages.
Error Message%MPLSIFMIB-3-GENERAL : [chars]
Explanation A memory corruption of MPLS layer subblock may have occurred. The cause is unknown.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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_ADJ_SB Messages
The following are MPLS Adjacency Sublock messages.
Error Message%MPLS_ADJ_SB-4-NO_BACKUP_INTF : [chars] - ifnum [dec]
Explanation Backup interface cannot be programmed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.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-PATH_LABEL_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-PATH_LABEL_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-PATH_LABEL_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-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_RATE Messages
The following are MPLS Rate messages.
Error Message%MLS_RATE-4-OVERWRITING_PORTSEC_DEFAULT : Port security rate limiter was set to non-default value.
Explanation Overwriting the default port security rate 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.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-3-MFIERROR : [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.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. If you still require assistance, open a case with the Technical Assistance Center via the 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-XMITFAIL : [chars], message seq no [dec], current seq no [dec]
Explanation MPLS VPN Label Manager failed to deliver a 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.MPLS_VPN_ISSU Messages
The following are MPLS VPN ISSU client messages.
Error Message%MPLS_VPN_ISSU-3-CF_ERR : [chars] [hex]
Explanation MPLS VPN ISSU client 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%MPLS_VPN_ISSU-3-GENERR : [chars]
Explanation MPLS VPN ISSU client 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_ISSU-3-ISSU_RC_ERR : [chars] [chars]
Explanation MPLS VPN ISSU client ISSU infra 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.MPLSOMGRE_SHIM Messages
The following are the MPLSOMGRE_SHIM messages.
Error Message%MPLSOMGRE_SHIM-3-NOMEM : Memory Allocation Failure - [chars] : [chars]([hex])
Explanation The memory required to service one or more Network Processors could not be allocated.
Recommended Action This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via
the configuration. Try to reload the Cisco IOS software image on the affected card or platform. If the error persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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.MPLSMFISTATIC Messages
The following are MPLS MFI static application messages.
Error Message%MPLSMFISTATIC-3-CHUNKMGR : [chars] [hex]
Explanation MPLS MFI Static Application chunk manager error has occurred.
Recommended Action Problem might be due to a low memory condition on the device. Check system memory and minimum memory requirements for this release and configuration, and add memory if required. If memory appears to be sufficient and problem persists, 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 process memory, show version and show running-config commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLSMFISTATIC-3-FCALLFAILED : [chars]
Explanation MPLS MFI Static Application function call return 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 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%MPLSMFISTATIC-3-INVALIDPRAMS : [chars] [dec]
Explanation Unexpected MPLS MFI Static Application parameter 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 process memory, show version and show running-config commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MPLSMFISTATIC-3-WRONGCODEPATH : [chars]
Explanation Unexpected MPLS MFI Static Application code path 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 process memory, show version and show running-config commands to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.MRIB PROXY Messages
The following are Multicast Routing Information Base Proxy messages.
Error Message y%MRIB_PROXY-2-MRIB_LC_CONNECT_FAIL : The linecard could not connect to the RP proxy: [chars]
Explanation The line card failed to make a connection to the MRIB proxy on the RP. The MFIB will not be started on this 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%MRIB_PROXY-2-MRIB_RP_INIT_FAIL : The RP proxy process failed to initialize: [chars]
Explanation The MRIB RP proxy failed to initialized correctly. This will prevent the MFIB from starting on line cards.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.MR_MGR Messages
The following are MR Manager messages.
Error Message%MR_MGR-6-CONFIG_CHANGE_NOT_ALLOWED : [chars]
Explanation Following protocol combinations are allowed for co-existence PVST & CFM GVRP & CFM GVRP & PVST. This error message is given if user tries combinations other than supported ones.
Recommended Action Limit co-existence to supported combinations.
MROUTE Messages
The following are Multicast Route messages.
Error Message%MROUTE-3-IGMP_NOT_FOUND : IGMP group [IP_address] to delete from interface [chars] not found in VRF [chars]
Explanation The group to be deleted from the interface could not be found in the IGMP cache for the VRF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MROUTE-3-IGMP_TWHEEL_INIT_ERR : Error trying to initialize the IGMP timer wheel
Explanation An error occured intializing a timer twheel
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MROUTE-3-NO_PIM_NBR : There is no PIM neighbor on this IDB: [chars]
Explanation Probably PIM is not configured correctly on this interface or on interfaces of the nexthop routers.
Recommended Action Check PIM configurations on local and neighbor routers. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MROUTE-3-RECUR_ROUTE_DEPTH_ERR : Recursive route lookup has reached its max depth for: [IP_address]
Explanation Recursive route lookup has a pre-defined depth limit and it has been reached.
Recommended Action If possible, reduce rounds of next hop lookup needed for the network address in question. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MROUTE-4-REGISTER_SOURCE_CONFIG : Removing pim register source configuration for [chars] from vrf [chars]
Explanation The register source interface was deleted, had its IP address removed, or its vrf forwarding changed.
Recommended Action No action required, just check 'ip pim register-source' configuration.
Error Message%MROUTE-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 enter the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required.
Error Message%MROUTE-6-UNSUPPORTED_SAP_FORMAT : Received unsupported format SAP message from ([IP_address])
Explanation Received compressed payload SAP 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.MSB Messages
The following are MSB messages.
Error Message%MSB-5-MSB_NTP : Could not update clock on Multi-Service module [dec], rc is [dec]
Explanation Either the line card or the Cisco IOS software encountered some problems while sending a clock update from IOS to the line card.
Recommended Action In this message recurs, reset the Multi-Service module. If resetting the module does not solve the problem, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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%MSB-5-MSB_SCP : Multi-Service module SCP communication failed for module [dec], subopcode is [dec]
Explanation Either the line card or the Cisco IOS software encountered some problems while communicating through SCP channels.
Recommended Action If this message recurs, reset the Multi-Service module. If resetting the module does not solve the problem, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.MSC100_SPA_CC Messages
The following are Cisco 7304 SPA carrier card messages.
Error Message%MSC100_SPA_CC-0-FPGA_BAY_ERROR_EXCEED_LIMIT : [chars] detected [chars] exceed limit ([dec]) (hardware-status = [hex])
Explanation Critical FPGA error was detected on the spa or carrier card for the specified subslot. The spa in this subslot has been disabled since the error was deemed critical.
Recommended Action Try to reactivate the card by entering the hw-module subslot <slot-number/subslot-number> start command. If this message recurs, enter the show diag <slot-number > command to gather data that might help identify the nature of the message. If you cannot determine the nature of the message from the error message text or from the show diag <slot-number> command output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MSC100_SPA_CC-0-FPGA_ERROR : [chars] Slot [dec]: Hardware error detected [[chars]]
Explanation Critical FPGA error was detected on the carrier card. The carrier card is deactivated and then an automatic recovery is initiated. If a similar error occurs more than five times within an hour, the carrier card is deactivated.
Recommended Action If the line card is no longer automatically reactivating, copy the message exactly as it appears on the console or in the system log. Enter the show diag <slot-number> command to gather data that might help identify the nature of the message. If you cannot determine the nature of the message from the error message text or from the show diag <lot-number> command output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MSC100_SPA_CC-0-FPGA_ERROR_EXCEED_LIMIT : [chars] Slot [dec] detected [chars] exceed limit ([dec]) (hardware-status = [hex])
Explanation Critical FPGA error was detected on the carrier card. The carrier card is deactivated and then an automatic recovery is initiated. If similar error occurs more than five times within an hour, the carrier card is deactivated.
Recommended Action If the line card is no longer automatically reactivating, copy the message exactly as it appears on the console or in the system log. Enter the show diag <slot-number> command to gather data that might help identify the nature of the message. If you cannot determine the nature of the message from the error message text or from the show diag <slot-number> command output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MSC100_SPA_CC-0-MISSING_RP_FPGA_SUPPORT : The 7304-MSC-100 in slot [int] has been deactivated because the RP FPGA requires an upgrade.
Explanation The MSC-100 SPA carrier card in the specified slot requires a particular version of the RP FPGA. The MSC-100 will be deactivated until this FPGA incompatibility is addressed.
Recommended Action Enter the upgrade fpga all command to upgrade the RP FPGA. After upgrading the RP FPGA, reactivate the MSC-100 by removing and reinserting the MSC-100.
MTRIE Messages
The following are Mtrie messages.
Error Message%MTRIE-4-MTRIECORRUPTLEAF : [IP_address]/[dec] - [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MTRIE-4-MTRIELEAFOPFAIL : [IP_address]/[dec] - [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MTRIE-4-PLACEALLOC : Failed to allocate place holder
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.MUESLIX Messages
The following are Mx serial application-specific integrated circuit (ASIC) messages.
Error Message%MUESLIX-3-ERROR : [chars]
Explanation General error information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.MV64 Messages
The following are MAC controller messages.
Error Message%MV64-3-BAD_GBIC_EEPROM : [chars] - GBIC contains a bad EEPROM
Explanation Interface contains a GBIC with a bad EEPROM. This causes the link to be down.
Recommended Action Ensure the GBIC type is compatible with the interface. Verify that the GBIC was obtained from Cisco or a supported vendor.
Error Message%MV64-1-BAD_IDB : Invalid Interface Descriptor Block
Explanation The driver tried to fetch the interface's IDB and failed.
Recommended Action Software bug - open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-1-BAD_MEDIA : Unknown media-type in subblock
Explanation The media-type specified in the driver subblock is invalid.
Recommended Action Software bug - open a case with Development Engineering.Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-1-BAD_PARTICLE : Problem getting particle size
Explanation The driver was unable to get the particle size for this interface.
Recommended Action Software bug - open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-1-BAD_PLUGIN : Plugin function table incomplete or missing
Explanation The driver could not access the PA's specific function table.
Recommended Action Software bug - open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-1-BAD_POOL : Could not init buffer pools
Explanation The driver failed to get a pool of buffers from IOS.
Recommended Action Software bug - open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-1-BAD_SB_NOMEM : [chars] - Cannot create IDB subblock due to insufficient memory
Explanation There was insufficent system memory to create the subblock.
Recommended Action The router requires more main memory. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-1-BAD_STRUCT : Could not initialize structure
Explanation The driver failed to initialize a structure.
Recommended Action Software bug - open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-1-BAD_SUBBLOCK : [chars] - Could not install or use IDB subblock
Explanation An internal IOS error prevented the IDB subblock from being installed or used.
Recommended Action Software bug - open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-3-ERRINT : [chars], error interrupt, mac_status = [hex]
Explanation The MAC controller has signalled an error condition.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-1-IDBTYPE_UNK : Unknown IDBTYPE while starting driver
Explanation The IDBTYPE in the interface's instance structure is undefined for this driver.
Recommended Action Software bug - open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log.Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-1-INITFAIL_NOMEM : [chars], initialization failed, no buffer memory
Explanation The Ethernet port initialization failed due to insufficient memory.
Recommended Action The router requires more packet memory - consider upgrade.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%MV64-1-MODE_INVALID : Unknown or invalid chip mode (MII/TBI)
Explanation The driver subblock contains an invalid or undefined chip operating mode (MII or TBI mode).
Recommended Action Software bug - open a case with Development Engineering. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-2-NOISL : Interface [chars] does not support ISL
Explanation ISL is not supported on the specified interface's hardware.
Recommended Action No action is required.
Error Message%MV64-1-RESET : MAC Still in Reset
Explanation An attempt was made to access the MAC while it was in reset.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MV64-3-TOOBIG : [chars], packet too big ([dec]), from [enet]
Explanation The interface detects a packet larger than what is defined by MTU.
Recommended Action Check the other station's MTU settingNo action is required.
Error Message%MV64-3-UNKNOWN_GBIC : [chars] - Unknown GBIC type
Explanation Interface contains a GBIC of unknown type. This causes the link to be down.
Recommended Action Ensure the GBIC type is compatible with the interface. Verify that the GBIC was obtained from Cisco or a supported vendor
MWAM Messages
The following are Multiprocessor WAN Application Module (MWAM) messages.
Error Message%MWAM-0-ADDRESS_TRAP : Address trap: [dec] occurred on physical address: [hex] at EPC: [hex], ERR_EPC: [hex]
Explanation A previously defined address trap 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%MWAM-0-CORRECTABLE_ECC_ERR : A correctable ECC error has occurred, A_BUS_L2_ERRORS: [hex], A_BUS_MEMIO_ERRORS: [hex], A_SCD_BUS_ERR_STATUS: [hex]
Explanation A correctable ECC error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MWAM-0-MISDIRECTED_INTERRUPT : A misdirected interrupt occurred with int_mask: [hex]
Explanation A misdirected interrupt 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%MWAM-0-UNCORRECTABLE_ECC_ERR : An uncorrectable ECC error has occurred, A_BUS_L2_ERRORS: [hex], A_BUS_MEMIO_ERRORS: [hex], A_SCD_BUS_ERR_STATUS: [hex]
Explanation An uncorrectable ECC error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.MWAM_FILESYSTEM Messages
The following are Multiprocces WAN Application Module (MWAM) crash information and bootflash file system messages.
Error Message%MWAM_FILESYSTEM-6-BOOTFLASH_BUSY : Cannot access bootflash, filesystem is busy
Explanation The MWAM bootflash does not support reading and writing at the same time. The message means that bootflash is being accessed by some other operation, like copy, dir, format or squeeze.
Recommended Action Try the bootflash operation again after other operations have completed.
Error Message%MWAM_FILESYSTEM-3-FC_CANNOT_FORMAT : Insufficient memory to format bootflash file system.
Explanation The router does not have enough working storage available in heap memory to format a file system for crashinfo data. The router will function normally without a bootflash file system, however, the router cannot save information for problem analysis if it crashes.
Recommended Action Try to format the file system again at a later time or shortly after a re-boot.
Error Message%MWAM_FILESYSTEM-3-FC_DIR_IS_FULL : Cannot add [chars] to file system, directory is full.
Explanation The file system directory holds a limited number of entries, and an attempt was made to add a new file when the directory was already full. This can happen even when the file system still contains free space.
Recommended Action Delete an existing file or FORMAT the file system.
Error Message%MWAM_FILESYSTEM-3-FC_FLASH_WRITE_ERROR : Cannot write to bootflash file system: [chars].
Explanation The router cannot write to the bootflash.
Recommended Action If the problem occurred while executing a CLI command, try the command again. 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%MWAM_FILESYSTEM-3-FC_INVALID_DIR_REQ : Cannot read or write complete [chars] file system.
Explanation A CLI command attempted to copy or overwrite the full file system.
Recommended Action Copy from or to an individual file.
MWAM_FLASH Messages
The following are Multiprocessor WAN Application Module (MWAM) flash memory messages.
Error Message%MWAM_FLASH-3-ERR : [chars]
Explanation An error occured while programming/erasing the BootFlash
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MWAM_FLASH-3-FLASH_LOCKED_BY_OTHER_CPU : [chars]
Explanation The other CPU within this complex is programming the shared flash, flash programming must complete before proceeding with reload.
Recommended Action Wait for the other CPU to complete its flash programming operation, then re-enter the CLI command.
Error Message%MWAM_FLASH-3-OTHER_CPU_RELOAD : [chars]
Explanation The other CPU within this complex is reloading, flash programming operation cannot proceed.
Recommended Action Wait for the system to complete the reload operation.
MWAM_FUR Messages
The following are Multiprocessor WAN Application Module FUR messages.
Error Message%MWAM_FUR-3-ERR : [chars]
Explanation An error occurred while upgrading or invalidating the Field-Upgradable ROMMON.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MWAM_FUR-1-INFO : [chars]
Explanation Information about the Field-Upgradable ROMMON.
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.MWAM_NVRAM Messages
The following are Multiplexor WAN Application Module NVRAM messages.
Error Message%MWAM_NVRAM-3-ERR : [chars]
Explanation An error occurred while saving or erasing the configuration from flash.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%MWAM_NVRAM-5-INFO : [chars]
Explanation Information showing the state of the NVRAM configuration inthe BootFlash.
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%MWAM_NVRAM-5-KRUSTY_NVRAM_NOT_FOUND : [chars]
Explanation Information stating there is no NVRAM pointer.
Recommended Action This indicates either NVRAM has not initialised properly, or it is corrupted. Copy the message exactly as it appears on the console or in the system log.Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.MWAM_VRTC Messages
The following are Multiprocessor WAN Application Module VTRC messages.
Error Message%MWAM_VRTC-3-INVALID_DATE : Trying to set an invalid date ([dec]/[dec]/[dec]) in the system
Explanation A message containing an invalid date (for e.g. 30 Feb or 31 Nov) is received by the MWAM 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%MWAM_VRTC-5-INVALID_TIME : Trying to set invalid time
summer_time_start[[dec]], set time[[dec]], summertime offset[[dec]]Explanation A message containing time which violates the summertime rules, is received by the MWAM module.
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.NATMIB_HELPER Messages
The following are NAT MIB helper messages.
Error Message%NATMIB_HELPER-3-NOCREAT : NATMIB Helper Process not created - NAT MIB will not work properly
Explanation Attempt to start NATMIB Helper Process failed when the NATMIB subsystem was initialized.
Recommended Action The NATMIB Helper process was not created, possibly due to lack of memory. If you want to use the NATMIB, reconfigure the system so that less memory is used by other features, or add more memory to the system. Reload the system after reconfiguring.
NETWORK_PORT_SATELLITE Messages
The following are network port satellite messages.
Error Message%NETWORK_PORT_SATELLITE-3-PHY_LOCKUP : Repeated phy lockup seen on [chars]. Interface will be shut down.
Explanation Phy lockup was detected too many times in a row. Interface is shutdown to avoid continuous link flapping.
Recommended Action To re-enable interface enter the shutdown command followed by a no shutdown command in interface configuration mode.
NETWORK_RF_API Messages
The following are network redundancy feature API messages.
Error Message%NETWORK_RF_API-3-FAILSENDMSGTOACTIVE : Failed to send [chars] message to active for [chars], [chars]
Explanation The specified synchronization message, which is an internal IPC message, could not be sent to the active unit in the specified run-time module. The failure most likely occurred because of a software error. Additional details on the nature of the message are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%NETWORK_RF_API-6-IDB_TRANSITIONS_PENDING : Switchover terminated with [dec] transitions pending after there was no transition activity for [dec] seconds
Explanation The system terminated the switchover idb transitioning phase with a number of idb transitions still pending because no switchover related IDB transitions were logged during the specified time interval. Some connected routes might experience a temporary loss of traffic.
Recommended Action No action is required.
Error Message%NETWORK_RF_API-3-ISSU_MSG_MTU_INVALID : The ISSU message MTU is invalid: [chars]
Explanation A message buffer size that is used for state synchronization was found to be invalid. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the nature of the message are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%NETWORK_RF_API-3-ISSU_MSG_TYPE_INCOMPAT : The active and standby ISSU message types are incompatible
Explanation A message that is used for state synchronization is deemed to be incompatible. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%NETWORK_RF_API-3-ISSU_REG_SES_INFO : Failed to register ISSU session information: [chars]
Explanation The system failed to register the ISSU session information required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the nature of the message are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%NETWORK_RF_API-3-ISSU_START_NEGO_SES : Failed to start ISSU session: [chars]
Explanation The system failed to start the ISSU negotiation session required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the nature of the message are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%NETWORK_RF_API-3-ISSU_TRANSFORM_FAIL : The ISSU message [chars] transformation failed: [chars]
Explanation A message that is used for state synchronization could not be transformed correctly. An internal data structure for a message could not be retrieved. The failure most likely occurred because of a software error. Additional details on the nature of the message are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%NETWORK_RF_API-3-ISSU_UNREG_SES_INFO : Failed to register ISSU session information: [chars]
Explanation The system failed to unregister the ISSU session information required to complete version exchange between the active and standby units. The failure most likely occurred because of a software error. Additional details on the nature of the message are specified in the message text on the console or in the system log. The system state between the active and standby units might not be properly synchronized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.NP Messages
The following are Network Processor messages.
Error Message%NP-2-BADREAD : Read failed for [chars] on NP [dec].
Explanation There was a read error on the file during the microcode image load.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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%NP-2-HDRCORRUPT : Microcode header has been corrupted, expected [hex], got [hex].
Explanation Network Processor microcode appears to be corrupted. This could be due to an already corrupted image or, less likely, a software 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.Error Message%NP-2-INVALID : Corrupted microcode retrieved from the image bundle for NP [dec].
Explanation The retrieved microcode appears to be corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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%NP-2-NONEXIST : Could not open or file does not exist [chars] for NP [dec].
Explanation There is a possibility that the Network Processor microcode may not be bundled into the image correctly or a software error occurred that prevented locating the microcode.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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%NP-2-RESTARTED : NP [dec] restarted.
Explanation Network Processor has been restarted, either manually or via a microcode reload, or as a result of an exception.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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%NP-5-RESTARTEDALL : All NPs have been restarted.
Explanation All Network Processors have been restarted, either manually or via a microcode reload, or as a result of an exception.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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%NP-2-WRONGHARD : The microcode type does not match, expected [hex], got [hex].
Explanation There is a possibility the images has been corrupted or, less likely, an incorrect microcode set is bundled into the image.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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%NP-2-WRONGMAGIC : Microcode section contains inalid magic for NP [dec].
Explanation Network Processor microcode appears to mismatch the ucode hdr type. This could be due to an already corrupted image or a read error on the file during the downloading on the NP.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.NP_CLIENT Messages
The following are Network Processor Client messages.
Error Message%NP_CLIENT-3-UNEXPECTED : NP Client Unexpected - [chars]: [chars] [chars] [dec] [dec]
Explanation NP Client unexpected error condition.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech show log command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.NP_CRASHINFO Messages
The following are Network Processor Crashinfo messages.
Error Message%NP_CRASHINFO-2-OPEN_FAILED : Could not open crashinfo file [[chars]]
Explanation The file for writing crashinfo could not be opened. This is usually caused by the file system 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.Error Message%NP_CRASHINFO-2-WRITE_FAILED : Could not write crashinfo file [[chars]]
Explanation Could not write crashinfo to the file. This is usuallycaused by the file system 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.Error Message%NP_CRASHINFO-2-WRITING : Writing crashinfo file [[chars]]
Explanation NP detected a watchdog timeout. The crashinfo is collectedfrom problematic NP and stored in the location.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.NP_DEV Messages
The following are Network Processor Device messages.
Error Message%NP_DEV-3-ECC_DOUBLE : Double-bit ECC error detected on NP [dec], Mem [dec], SubMem [hex],SingleErr [dec], DoubleErr [dec] Count [dec] Total [dec]
Explanation Double-bit ECC error detected for a Network Processor device component.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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. If the problem persists, hardware may need to be replaced.Error Message%NP_DEV-6-ECC_SINGLE : Recovered from a single-bit ECC error detected on NP [dec], Mem [dec], SubMem [hex],SingleErr [dec], DoubleErr [dec] Count [dec] Total [dec]
Explanation Recovered from a single-bit ECC error detected for a Network Processor device component.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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. If the problem persists, hardware may need to be replaced.Error Message%NP_DEV-3-ERRINTR : Error caused by: [chars] on NP [dec]
Explanation Error in Network Processor device operation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%NP_DEV-5-INTRTHR : Interrupt: cause [dec] for NP([int]) throttled
Explanation Too many interrupts are being generated from Network Processor device
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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%NP_DEV-2-INVREGINTR : Illegal Write on NP RMA Register: [hex], Data: [hex]
Explanation This is an illegal Write to an NP RMA Register. This is to debug NP Parity Error issue. Examine traceback and forward it to development team.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.Message%NP_DEV-3-PERR : Non-recoverable Parity error detected on NP [dec], cause [dec] count [int] uqParityMask [hex], uqSRAMLine [hex], bRecov [dec], bRewr [dec] Total [dec]
Explanation A non-recoverable parity error detected for a Network Processor device component.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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. If the problem persists, hardware may need to be replaced.Message%NP_DEV-6-PERR_RECOVERED : Recovered from a Parity error on NP [dec], cause [dec], count [int] uqParityMask [hex], uqSRAMLine [hex], bRecov [dec], bRewr [dec] Total [dec]
Explanation Recovered from a Parity error detected for a Network Processor device component.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance 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.If the problem persists, hardware may need to be replaced.NSE100 Messages
The following are NSE100 messages.
Error Message%NSE100-5-AUTONEG_ENABLE : Auto negotiation is enabled for interface GigabitEthernet[dec]/[dec] due to [chars]
Explanation The auto-negotiation feature has been enabled for the Gigabit Ethernet interface in the slot and port specified in the message text. The reason why the feature was enabled is specified in the message text. The auto-negotiation feature is required for the interface to work properly.
Recommended Action No action is required.
Error Message%NSE100-3-IOBUSTIMEOUT : IO access to the address [hex] timed out (Target: [chars])
Explanation The System Controller flagged an I/O access timeout. It indicates either a transient or fatal system component issue or an underlying software initialization issue. The source of the problem can be determined more accurately by decoding the address being accessed. If the I/O address is a valid one in the system memory map and if the system has been up and operational for a while, the problem is probably hardware related. If this problem is seen repeatedly, the corresponding component might need to be replaced.
Recommended Action If the mesage is seen repeatedly, collect the following information:
Description of the user activity just before the occurrence of this incident, prevailing system operational conditions like traffic pattern, amount of traffic, system neighbors, etc.,
System console messages and the output of the following commands, show running-config, show c7300 pxf accounting, show c7300 pxf interfaces all, show diag and show c7300.
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%NSE100-3-PAK_LENGTH : Packet Length mismatch detected: datagramsize=[dec], particle data sum=[dec] input i/f=[chars], output i/f=[chars]
pak=[hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][ hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][ hex][hex][hex][hex][hex][hex][hex][hex][hex]Explanation A packet length inconsistency has been detected when transmitting a a packet from the RP to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%NSE100-3-PINNACLE_PORT : [chars] - [chars]
Explanation This error appears as a result of the failure in one of the the initialization tasks of the GE ports presenton the NSE100. This is mostly due either to a software problem or a transient condition before the GE port comes up successfully.
Recommended Action If the GE ports either stay down or fail to forward the traffic, due to the above problem, entering the Shut and No Shut interface configuration commands on the affected GE ports restores the forwarding. If the mesage is seen repeatedly, collect following information:
Description of the user activity just before the occurrence of this incident, prevailing system operational conditions like traffic pattern, amount of traffic, system neighbors etc.
System console messages and the output of the following commands: show version, show running-config, show controller gigabitEthernet , show interface gigabitEthernet , show pxf accounting and show c7300.
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%NSE100-3-UNEXPECTED_TIMEREVENT : The NSE-100 GE port driver couldn't determine the port associated with the expired internal managed timer.The expired managed timer is pointing to [chars]
Explanation The expired managed timer returned a null context.This condition indicates a software failure in the management of the managed timer.
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%NSE100-3-VA_ERROR : Vanallen ASIC detected an error condition: [chars]
Explanation The Vanallen ASIC detected an error condition. This message either indicates a hardware error or an error in the 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.NTP Messages
The following are Network Time Protocol messages.
Error Message%NTP-6-PEERREACH : Peer [IP_address] is reachable
Explanation The NTP peer is reachable.
Recommended Action No action is required.
Error Message%NTP-5-PEERSYNC : NTP synced to peer [IP_address]
Explanation NTP has synchronized the local clock to a new peer.
Recommended Action No action is required.
Error Message%NTP-4-PEERUNREACH : Peer [IP_address] is unreachable
Explanation The NTP peer is unreachable.
Recommended Action Check network connection to the peer and if NTP is running on the peer.
Error Message%NTP-6-RESTART : NTP process starts
Explanation NTP process has just started or re-started.
Recommended Action No action is required.
Error Message%NTP-6-STOP : NTP process stops
Explanation NTP is disabled.
Recommended Action Check if NTP is disabled by administrator purposely.
Error Message%NTP-4-UNSYNC : NTP sync is lost
Explanation NTP synchronization to its peer is lost.
Recommended Action Check network connection to the peer, if NTP is running on the peer, if the peer itself is synchronized to a stable time source, and if NTP packets from the peer have passed validity tests specified in the RFC1305 etc.
OC12SRP Messages
Error Message%OC12SRP-1-BLKCMD : Schooner System IPC failure for OC12SRP card
Explanation c10k_card_send_blocking_cmd 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%OC12SRP-3-INTERNAL : OC12 SRP internal error, [chars] [dec] [dec]
Explanation Internal OC12 SRP 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%OC12SRP-3-INTERNALCMD : OC12 SRP LC command internal error, [chars] [dec] [dec]
Explanation Internal OC12 SRP LC command 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%OC12SRP-3-INTERNALEVT : OC12 SRP LC Event internal error, [chars] [dec] [dec]
Explanation Internal OC12 SRP LC event 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%OC12SRP-3-MIBINITFAIL : OC12 SRP MIB initialization failed, [chars] [dec]
Explanation MIB initialization for OC12SRP 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%OC12SRP-4-MSGVERSION : Incompatible message version with slot [dec]
Explanation There is incompatibility between the the message version being sent by the line card and the message version used by the PRE. This type of incompatibility could happen if the PRE and OC12 SRP card card are using different IOS versions due to an PRE oir event
Recommended Action A microcode reload will solve the problem.
Error Message%OC12SRP-1-UNKEVT : Schooner subsystem unknown event:([dec])
Explanation Schooner System received unknown event 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.OCE Messages
The following are OCE infrastructure messages.
Error Message%OCE-3-MISSING_HANDLER_FOR_SW_OBJ : Missing handler for '[chars]' function
Explanation An internal API request has been ignored because it was unexpected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OCE-3-MISSING_HANDLER_FOR_SW_OBJ_TYPE : Missing handler for '[chars]' function for type [chars]
Explanation An internal API request has been ignored because it was unexpected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OCE-3-OCE_CHANGED_BY_APPLY_FUNCTION : Target OCE[hex_addr] changed to[hex_addr] by apply function[hex_addr]
Explanation An unexpected internal API request has been received. It has been ignored.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OCE-3-OCEDEPDUMP : [chars]
Explanation An error condition triggered display of oce dependents.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OCE-3-OCE_FWD_STATE_HANDLE : Limit of oce forward state handle allocation reached; maximum allowable number is [int]
Explanation Did not store the re-inject forwarding state handle, as the maximum number of handles are already in use.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OCE-3-OCE_FWD_STATE_HANDLE_INIT : Failed to initialize a stack of reusable forward state handles; at element [int], initial stack size is [int] elements
Explanation Could not allocate enough forwarding state handles for initial handle re-use.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OCE-3-QUEUE_UNLOCK : Failed to [chars] unlock[chars] for [chars] oce [hex]
Explanation Failed to enqueue a unlock for an oce, this might lead to a memory leak.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OCE-3-UNEXPECTED_DISP_TYPE : Unexpected disposition type is encounted; expecting disposition types are [chars], found [chars]
Explanation An internal disposition counter measure request has been ignored because it was unexpected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OCE-3-UNEXPECTED_SW_OBJ_TYPE : SW_OBJ handle/type mismatch; expecting oce type [chars], found [dec]
Explanation An internal API request has been ignored because it was unexpected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OCE-3-UNINITIALIZED_VECTOR : Improperly initialized [chars] vector in [chars] OCE bundle [hex], packet dropped
Explanation An OCE bundle vector was improperly initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.ODM Messages
The following are order dependent merge messages.
Error Message%ODM-3-PEER_INCOMPATIBLE : Online Diags Peer Version is different
Explanation Version of the peer Online Diagnostics Manager is different.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%ODM-3-SC_TEST_FAIL : Slot [dec], Subcard [dec],[chars] [chars] Failed
Explanation Online diagnostic test failed for the subcard.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.OIR Messages
The following are online insertion and removal (OIR) messages.
Error Message%OIR-3-HARD_RESET : Module [dec] is being hard reset as a part of switchover error recovery
Explanation The module specified in error message is being hard reset as a recovery for failure to respond to switchover message.
Recommended Action No action is required.
Error Message%OIR-5-ISSU_RESET : Module [dec] is being [chars]-reset during ISSU
Explanation The module specified in error message is being hard/soft resetas part of a planned ISSU upgrade.
Recommended Action No action is required.
Error Message%OIR-3-PSM_SUBCARDDETECT : Slot [dec] [chars] [dec]: subcard [dec] inserted
Explanation A PSM subcard has been detected in the specified slot.
Recommended Action This is an informational message only. No action is required.
Error Message%OIR-3-PSM_SUBCARDREMOVE : Slot [dec] [chars] [dec]: subcard [dec] removed
Explanation A PSM subcard has been removed from the specified slot.
Recommended Action This is an informational message only. No action is required.
Error Message%OIR-6-PWRFAILURE : Module [dec] is being disabled due to power convertor failure [hex]
Explanation The DC-DC power convertor failed on this module, need to replace hardware.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OIR-3-SOFT_RESET : Module [dec] is being soft reset as a part of switchover error recovery
Explanation The module specified in error message is being soft reset as a part of swichover error recovery.
Recommended Action No action is required.
OLM Messages
The following are Optical Link Management and Link Management Protocol messages.
Error Message%OLM-3-LMPSDMISMATCH : Service Discovery: Attribute [chars] incompatible with neighbor [chars]
Explanation Specified service attribute does not match with neighbor. The neighbor and/or the local node might not be properly configured.
Recommended Action Enter the show mpls uni lmp neighbor command on the local and the neighbor node (where applicable) to determine the service attributes. Modify the configuration, where feasible, to ensure that the attributes match.
Error Message%OLM-3-LMPSDPORTFAILED : Service Discovery: Attributes for port [chars] incompatible with nbr [chars]
Explanation Port-level service attribute does not match with those of the neighbor. The neighbor and/or the local node might not be properly configured.
Recommended Action Enter the show mpls uni lmp neighbor command on the local and the neighbor node (where applicable) to determine the service attributes. Modify the configuration, where feasible, to ensure that the port-level service attributes match.
ONS15530 Messages
The following are Cisco ONS 15530 trunk card messages.
Error Message%ONS15530-3-CHASSIS : Unknown chassis model.
Explanation Data stored in midplane is bad or incomplete.
Recommended Action Contact technical support to update your system.
Error Message%ONS15530-4-COOKIE : Corrupt or missing MAC address cookie using random base [enet]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%ONS15530-1-DISCOVER_ENET : Failed to init Ethernet device [dec]
Explanation The software could not initialize.
Recommended Action Power down the system, 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. 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%ONS15530-3-IONOT0 : IO card discover in non-zero slot [dec]/[dec]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%ONS15530-3-IPCOPENFAILED : Couldn't open IPC portfor port id [hex] slot [int]/[int]: [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%ONS15530-4-MACBLKSIZE : Unknown MAC address block size.
Explanation Data stored in midplane is bad or incomplete.
Recommended Action Contact technical support to update your system.
Error Message%ONS15530-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%ONS15530-3-NOMEM : OUT of Memory: [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%ONS15530-2-NOMEMORY : No memory available for [chars]
Explanation An attempt to allocate memory has failed.
Recommended Action Perform the following actions to attempt to remedy the problem:
-Add memory.
-Disable some features.
-Apply filtering to decrease the size of system data structures (the routing table, for example).
-Reduce other system activities to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.Error Message%ONS15530-3-NOPORTINFO : Port info invalid for port [dec] slot [int]/[int]: [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%ONS15530-3-NOPORTINFO_ID : Port info invalid for port id [hex] slot [int]/[int]: [chars]
Explanation Unavailable.
Recommended Action Unavailable.
OPTICAL_MONITOR Messages
The following are optical monitoring messages.
Error Message%OPTICAL_MONITOR-4-FAILED : [chars] [chars]
Explanation Monitoring cannot be turned on for the specified rate with current hardware version.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.OSM_MULTILINK Messages
The following are Optical Services Module (OSM) distributed multilink messages.
Error Message%OSM_MULTILINK-4-MLPLINK_NULL : Unexpected mlp link missing in [chars]
Explanation A software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.OSPF Messages
The following are the Open Shortest Path First messages.
Error Message%OSPF-5-ADJCHG: Process %d, Nbr %i on %s from %s to %s, %s
Explanation An OSPF neighbor has changed state. The message describes the change and the reason for it. This message appears only if the log-adjacency-changes command is configured for the OSPF process.
Recommended Action No action is required.
Error Message%OSPF-4-AREA_ALLOC_FAIL: Can not allocate memory for area structure
Explanation An internal error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-6-AREACHG: %i%m changed from area %s to area %s
Explanation An OSPF configuration change has caused a network range to change areas.
Recommended Action No action is required.
Error Message%OSPF-4-ASBR_WITHOUT_VALID_AREA: Router is currently an ASBR while having only one area which is a stub area
Explanation An ASBR must be attached to an area that can carry AS External or NSSA LSAs.
Recommended Action Make the area to which the router is attached an NSSA or regular area.
Error Message%OSPF-6-BAD_LSA_COUNT: OSPF-%d Area %s: LSA ID %i, Type %d, Adv-rtr %i, LSA counter %s
Explanation An internal error has been self-corrected. This operation does not affect the operation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support ospf commands and your pertinent troubleshooting logs.
Error Message%OSPF-6-BADCHKSUM: Checksum Failure in database in area %s Link State Id %i Old Checksum %#x New Checksum %#x
Explanation OSPF has detected a checksum error in the database due to memory corruption.
Recommended Action Restart the OSPF process.
Error Message%OSPF-4-BADLENGTH: Invalid length %d in OSPF packet type %d from %i (ID %i), %s
Explanation The system received an OSPF packet with a length field of less than the normal header size or inconsistent with the size of the IP packet in which it arrived. This indicates an error in the sender of the packet.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-4-BADLSAMASK: Bad LSA mask: Type %d, LSID %i Mask %i from %i NOTE: This route will not be installed in the routing table.
Explanation The router received an LSA with an invalid LSA mask. The cause is probably wrong configuration from the LSA originator.
Recommended Action Find the originating router of the LSA that has the bad mask. Correct any misconfiguration of this LSA's network. For further debugging, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%OSPF-4-BADLSATYPE: Invalid lsa: %s Type %d, Length %d, LSID %i from %i, %i, %s
Explanation The router received an LSA with invalid data. The LSA contains an invalid LSA type, wrong checksum, or wrong length. The cause is either memory corruption or unexpected behavior on a router.
Recommended Action From a neighboring address, locate the problem router. Perform the following steps:
1.
Collect a running configuration of the router by entering the show running-config command.
2.
3.
4.
5.
6.
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OSPF-3-CFG_NBR_ALLOC_FAILED: Could not allocate or find neighbor %i
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OSPF-3-CFG_NBR_FAILED: Neighbor %i not configured
Explanation The configured neighbor options are not valid.
Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
Error Message%OSPF-4-CFG_NBR_INVAL_NBMA_OPT: Can not use configured neighbor: cost and database-filter options are allowed only for a point-to-multipoint network
Explanation The configured neighbor was found on an NBMA network, and either the cost or the database-filter option was configured. These options are allowed only on point-to-multipoint type networks.
Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
Error Message%OSPF-4-CFG_NBR_INVAL_NET_TYPE: Can not use configured neighbor: neighbor command is allowed only on NBMA and point-to-multipoint networks
Explanation The configured neighbor was found on a network for which the network type was neither NBMA nor point-to-multipoint.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%OSPF-4-CFG_NBR_INVAL_P2MP_OPT: Can not use configured neighbor: poll and priority options are allowed only for a NBMA network
Explanation The configured neighbor was found on a point-to-multipoint network and either the poll or priority option was configured. These options are allowed only on NBMA type networks.
Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
Error Message%OSPF-4-CFG_NBR_P2MP_NEEDS_COST: Can not use configured neighbor: cost or database-filter option is required for point-to-multipoint broadcast network
Explanation The configured neighbor was found on a point-to-multipoint broadcast network. Either the cost or the database-filter option must be configured.
Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
Error Message%OSPF-4-CONFLICTING_LSAID: Process %d area %s: LSA origination prevented by LSA with same LSID but a different mask Existing Type %d LSA: LSID %i%m New Destination: %i%m
Explanation An LSA origination was prevented by a conflict with an existing LSA with the same LSID but a different mask. The algorithm in RFC 2328, Appendix E is used to resolve conflicts when multiple LSAs with the same prefix and different masks are advertised. When using this algorithm is used and host routes are advertised, situations can occur where conflict resolution is impossible and either the host route or the conflicting prefix is not advertised.
Recommended Action Locate the prefix that is not advertised and the conflicting prefix using the show ip route and show ip ospf database commands.Decide which route or prefix is more important to advertise and take steps to prevent advertising the conflicting route or prefix. If you cannot determine the nature of the error from the collected information, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%OSPF-3-DBEXIST: area %s lsid %i mask %i type %d
Explanation OSPF is trying to add an existing LSA to the database.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-4-DUP_RTRID_AREA: Detected router with duplicate router ID %i in area %s
Explanation OSPF has detected a router in the area that has the same router ID as this routing process. Duplicate router IDs may result in network instability, causing some destinations to be unreachable.
Recommended Action The OSPF router ID should be unique. Make sure all routers in the area have a unique router ID.
Error Message%OSPF-4-DUP_RTRID_NBR: OSPF detected duplicate router-id %i from %i on interface %s
Explanation OSPF has received a hello packet from a neighbor that has the same router ID as this routing process. A full adjacency cannot be established.
Recommended Action The OSPF router ID should be unique. Change the router ID of the neighbor.
Error Message%OSPF-4-ERRRCV: Received invalid packet: %s from %i, %s
Explanation An invalid OSPF packet was received. Details are included in the error message. The cause might be a misconfigured OSPF or an internal error in the sender.
Recommended Action Check the OSPF configuration of the receiver and the sender for inconsistency.
Error Message%OSPF-4-FLOOD_WAR: Process %d %s LSA ID %i type-%d adv-rtr %i in area %s
Explanation Router is extensively reoriginating or flushing the LSA reported by this error message.
Recommended Action If this router is flushing the network LSA, the router has received a network LSA whose LSA ID conflicts with the IP address of one of the router's interfaces, and so the router flushed the LSA out of the network. For OSPF to function correctly, the IP addresses of transit networks must be unique. The conflicting routers are the router reporting this error message and the router with the OSPF router ID reported as adv-rtr in this message. If this router is reoriginating an LSA, it is probable that some other router is flushing this LSA out of the network. Find that router and resolve the conflict. Conflict for type-2 LSA may be due to duplicate LSA ID; for type-5 LSA it may be duplicate router IDs on the routers reporting this error message and on the routers connected to the other area. In an unstable network, this message may also warn of extensive reorigination of LSA for some other reason. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-3-FORW_RT_NO_LSA: OSPF LSID %i adv %i type %d gateway %i metric %d forwarding addr route %i/%i type %d has no corresponding LSA.
Explanation OSPF found an inconsistency between its database and the IP routing table.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-3-INT_ATTACHED_MULTI_AREAS: Interface %s is attached to more than one area
Explanation The interface is on the interface list for an area other than the one to which the interface links.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-3-INT_INIT_FAILED: Init failed for interface %s, %s.
Explanation The interface initialization failed. Possible reasons:
1) The area to which the interface is being attached is being deleted.
2) It was not possible to create the link scope database.
3) It was not possible to create a neighbor datablock for the local router.Recommended Action Remove the configuration command that covers the interface and then try it again. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%OSPF-3-INTERNALERR: Internal error: %s
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%OSPF-4-INV_LSA_BLD_FLG: Invalid build flag %x for LSA %i, type %d
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-4-INVALID_METRIC: OSPF-%d Area %s: Router %i originating invalid type %d LSA, ID %i, Metric %d on Link ID %i Link Type %d
Explanation The router indicated in this message has originated an LSA with an invalid metric. If this is an router LSA and the link metric is zero, routing loops and traffic loss could occur in the network.
Recommended Action Configure a valid metric for a given LSA type and link type on the router originating reported LSA.
Error Message%OSPF-4-LOW_NET_METRIC: Network %i metric %d goes down. In range of summary %i %i with metric %d
Explanation A software or hardware error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-6-LRIB_WRONG_REFCNT: OSPF-%d Invalid reference count for %i/%d
Explanation A negative database reference count has been encountered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support and show tech-support ospf commands and your pertinent troubleshooting logs.
Error Message%OSPF-3-LSA_LEN: Area %s router-LSA of length %d bytes plus update overhead %d bytes is too large to flood.
Explanation The router tried to build a router-LSA that is larger than the huge system buffer size or the OSPF protocol-imposed maximum.
Recommended Action If the reported total length (LSA size plus overhead) is larger than the huge system buffer size but less than 65535 bytes (the OSPF protocol-imposed maximum), you may increase the huge system buffer size. If the reported total length is greater than 65535, you must decrease the number of OSPF interfaces in the reported area.
Error Message%OSPF-6-MODECHG: Base topology enabled on interface %s attached to MTR compatible mode area %s
Explanation The base topology is being enabled.
Recommended Action No action is required.
Error Message%OSPF-4-NO_IPADDRESS_ON_INT: No IP address for interface %s
Explanation The user has configured OSPF to run on an interface which is unnumbered (for example: it does not have an IP address), but OSPF is not configured point-to-point on the interface.
Recommended Action Either change the interface type or provide the interface an IP address.
Error Message%OSPF-4-NO_OUTPUTQ: Packet not written to the output queue
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-3-NO_SNMP_IFINDEX: Interface %s does not have an SNMP MIB ifIndex and has been disabled
Explanation The OSPF process has been configured to use the SNMP MIB ifIndex value for the interface IDs. However, the ifIndex is not set on this interface, so the interface can not be enabled.
Recommended Action Unconfigure interface-id snmp-if-index for this OSPF process.
Error Message%OSPFv3-3-NO_SNMP_IFINDEX: Interface %s does not have an SNMP MIB ifIndex and has been disabled
Explanation The OSPF process has been configured to use the SNMP MIB ifIndex value for the interface IDs. However, the ifIndex is not set on this interface, so the interface cannot be enabled.
Recommended Action Unconfigure interface-id snmp-if-index for this OSPF process.
Error Message%OSPF-3-NOBACKBONE: Flagged as being an ABR without a backbone area
Explanation The router was flagged as an Area Border Router (ABR) without a backbone area in the router.
Recommended Action Restart the OSPF process.
Error Message%OSPF-3-NOCONNDB: No database entry for connected address %i
Explanation While calculating OSPF routes, the router could not find the LSA that represents the connected route in the router.
Recommended Action To clear the IP routes in the routing table, use the clear ip route command.
Error Message%OSPF-3-NOLSA: Failed to find this routers LSA in %s
Explanation The router is not able to find its own router LSA.
Recommended Action This will self-correct. However, if this message recurs, restart the OSPF process.
Error Message%OSPF-4-NONEIGHBOR: Received %s from unknown neighbor %i
Explanation An OSPF hello, database description, or database request packet was received, but the router could not identify the sender.
Recommended Action This situation should correct itself. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%OSPF-4-NORTRID: OSPF process %d failed to allocate unique router-id and cannot start
Explanation OSPF failed while attempting to allocate a unique router ID from the IP addresses of its interfaces.
Recommended Action Ensure that at least one interface is up and has a valid IP address. If there are multiple OSPF processes running on the router, each requires a unique router ID. Configure a unique router ID manually, using the router-id command or configure an interface in the same VRF table, using the ip vrf forwarding command to which the OSPF process belongs. Configure on that interface an IP address that is not used as a router ID by any other OSPF process.
Error Message%OSPF-3-NOSELF: if %s if_state %d
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-6-NOSRCPDB: ex_route_callback(): Can't find the src protocol to redistribute net %i%m
Explanation OSPF attempted to redistribute a route but could not find a valid source protocol.
Recommended Action No action is required.
Error Message%OSPF-4-NOTREDIST5: db_free: external LSA %i%m
Explanation An internal software error has resulted in the deletion of a self-originated type-5 LSA from the local database without its first being flushed from the other routers in the OSPF routing domain. This may result in a temporary increase in memory usage in the other routers.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-4-NSSA_NO_FA: OSPF process %u lacks forwarding address for type 7 LSA %i in NSSA %s - P-bit cleared
Explanation Due to the unavailability of a viable forwarding address in the NSSA area, the P-bit has been cleared and the NSSA translator does not translate the type 7 LSA to the type 5 LSA.
Recommended Action Configure at least one interface in the NSSA with an advertised IP address. A loopback is preferable so that advertisement will not be dependent on the underlying layer 2 state.
Error Message%OSPF-4-NULL_LINKAGE: Doubly linked list linkage is NULL
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-4-NULL_PREV_LINKAGE: Doubly linked list prev linkage is NULL %x
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-4-OSPF_MAX_LSA: Maximum number of non self-generated LSA has been exceeded %s - %d LSAs
Explanation Maximum number of non self-generated LSA has been exceeded.
Recommended Action Determine if a router in the network is generating a large number of LSAs as a result of a misconfiguration.
Error Message%OSPF-4-OSPF_MAX_LSA_THR: Threshold for maximum number of non self-generated LSA has been reached %s - %d LSAs
Explanation Threshold for maximum number of non self-generated LSAs has been reached.
Recommended Action Determine if a router in the network is generating a large number of LSAs as a result of a misconfiguration.
Error Message%OSPF-6-PROC_REM_FROM_INT: OSPF process %d removed from interface %s
Explanation The OSPF process was removed from the interface due to IP VRF removal.
Recommended Action No action is required.
Error Message%OSPF-3-RECONF_VL: OSPF process %d is changing router-id. Reconfigure virtual link neighbors with our new router-id
Explanation The OSPF process is being reset, and it will select a new router ID. This will bring down all the virtual links. To make them work again, the virtual link configuration must be changed on all virtual link neighbors.
Recommended Action Change the virtual link configuration on all the virtual link neighbors to reflect the new router ID.
Error Message%OSPF-4-RTRID_IN_USE: Router-ID %i is in use by ospf process %d
Explanation An attempt was made to assign a Router ID which is in use by another process.
Recommended Action Configure another Router ID for one of the processes.
Error Message%OSPF-3-UNKNOWNSTATE: Reached unknown state in neighbor state machine
Explanation An internal software error in this router has resulted in an invalid neighbor state during database exchange.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-4-UNREC_TIMER: Unrecognized timer %d in OSPF %s
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-6-UNREC_VIRT_INT_TYPE: Unrecognized virtual interface %s. Treat it as loopback stub route
Explanation The virtual interface type was not recognized by OSPF, so it will be treated as a loopback interface stub route.
Recommended Action No action is required.
Error Message%OSPF-4-VIRTUAL_IN_NON_BACKBONE: Virtual link information found in non-backbone area: %s
Explanation An internal software error has caused this router to generate a router LSA that has a virtual link in a non-backbone area.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPF-6-ZERO_BANDWIDTH: interface %s has zero bandwidth
Explanation The interface has reported its bandwidth as zero.
Recommended Action No action is required.
OSPFv3 Messages
The following are Open Shortest Path First version 3 messages.
Error Message%OSPFv3-5-ADJCHG: Process %d, Nbr %i on %s from %s to %s, %s
Explanation An OSPF neighbor has changed state. The message describes the change and the reason for it. This message appears only if the log-adjacency-changes command is configured for the OSPF process.
Recommended Action No action is required.
Error Message%OSPFv3-4-AREA_MISMATCH : Received packet with incorrect area from[ipv6_addr], [chars], area [IP_address], packet area [IP_address]
Explanation An OSPF packet was received with an area ID in its header that does not match the area of this interface.
Recommended Action Check the OSPF configuration of the receiver and the sender for inconsistency.
Error Message%OSPFv3-4-ASBR_WITHOUT_VALID_AREA: Router is currently an ASBR while having only one area which is a stub area
Explanation An ASBR must be attached to an area that can carry AS External or NSSA LSAs.
Recommended Action Make the area to which the router is attached an NSSA or regular area.
Error Message%OSPFv3-6-BADCHKSUM: Checksum Failure in database in area %s Link State Id %i Old Checksum %#x New Checksum %#x
Explanation OSPF has detected a checksum error in the database due to memory corruption.
Recommended Action Restart the OSPF process.
Error Message%OSPFv3-4-BADLENGTH: Invalid length %d in OSPF packet type %d from %P (ID %i), %s
Explanation The system received an OSPF packet with a length field of less than normal header size or inconsistent with the size of the IP packet in which it arrived. This indicates an error in the sender of the packet.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message %OSPFv3-4-BADLSATYPE: Invalid lsa: %s: Type 0x%x, Length 0x%x, LSID %u from %i,%P, %sExplanation The router received an LSA with invalid data. LSA contains invalid LSA type, wrong checksum or wrong length. The cause is either memory corruption or unexpected behavior on a router.
Recommended Action From a neighboring address, locate the problem router. Perform the following steps:
1.
2.
3.
4.
5.
6.
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%OSPFv3-3-CFG_NBR_ALLOC_FAILED: Could not allocate or find the neighbor
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%OSPFv3-4-CFG_NBR_INVAL_NBMA_OPT: Can not use configured neighbor: cost and database-filter options are allowed only for a point-to-multipoint network
Explanation The configured neighbor was found on an NBMA network and either the cost or database-filter option was configured. These options are only allowed on point-to-multipoint type networks.
Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
Error Message%OSPFv3-4-CFG_NBR_INVAL_NET_TYPE: Can not use configured neighbor: neighbor command is allowed only on NBMA and point-to-multipoint networks
Explanation The configured neighbor was found on a network for which the network type was neither NBMA or point-to-multipoint.
Recommended Action No action is required.
Error Message%OSPFv3-4-CFG_NBR_NOT_NBMA_NET: Neighbor command allowed only on NBMA networks
Explanation The neighbor command is allowed only on NBMA networks.
Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
Error Message%OSPFv3-4-CFG_NBR_INVAL_P2MP_OPT: Can not use configured neighbor: poll and priority options are allowed only for a NBMA network
Explanation The configured neighbor was found on a point-to-multipoint network and either the poll or priority option was configured. These options are allowed only on NBMA type networks.
Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
Error Message%OSPFv3-4-CFG_NBR_P2MP_NEEDS_COST: Can not use configured neighbor: cost or database-filter option is required for point-to-multipoint broadcast network
Explanation The configured neighbor was found on a point-to-multipoint broadcast network. Either the cost or database-filter option must be configured.
Recommended Action Check the configuration options for the neighbor command and correct the options or the network type for the neighbor's interface.
Error Message%OSPFv3-4-DB_NOT_FOUND: Can't find LSA database type %x, area %x , interface %x
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPFv3-4-DBD_ALLOC_FAIL: Could not allocate DBD packet
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%OSPFv3-3-DBEXIST: DB already exist : area %s lsid %i adv %i type 0x%x
Explanation OSPF is unable to locate the LSA. This condition could lead to a memory leak.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPFv3-4-DUP_RTRID_AREA: Detected router with duplicate router ID %i in area %s
Explanation OSPF has received a hello packet from a neighbor that has the same router ID as this routing process. A full adjacency cannot be established.
Recommended Action The OSPF router ID should be unique. Change the neighbor's router ID.
Error Message%OSPFv3-4-DUP_RTRID_NBR: OSPF detected duplicate router-id %i from %P on interface %s
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPFv3-4-ERRRCV: Received invalid packet: %s from %P, %s
Explanation An invalid OSPF packet was received. Details are included in the error message. The cause might be a misconfigured OSPF or an internal error in the sender.
Recommended Action Check the OSPF configuration of the receiver and the sender and resolve any inconsistency.
Error Message%OSPFv3-3-INIT_IDB: OSPF is enabled on %s during idb initialization
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPFv3-3-INT_ATTACHED_MULTI_AREAS: Interface %s is attached to more than one area
Explanation The interface is on the interface list for an area other than the one to which the interface links.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPFv3-3-INT_INIT_FAILED: Init failed for interface %s, %s.
Explanation The interface initialization failed. Possible reasons:
1) The area to which the interface is being attached is being deleted.
2) It was not possible to create the link scope database.
3) It was not possible to create a neighbor datablock for the local router.Recommended Action Remove the configuration command that covers the interface and then try it again. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPFv3-3-INTERNALERR: Internal error: %s
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%OSPFv3-4-INV_LSA_BLD_FLG: Invalid build flag %x for LSA %i, type 0x%x
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPFv3-4-INVALID_METRIC: OSPFv3-%d Area %s: Router %i originating invalid type 0x%x LSA, ID %u, Metric %d on Link ID %d Link Type %d
Explanation The router indicated in this message has originated an LSA with an invalid metric. If this is an router LSA and the link metric is zero, routing loops and traffic loss could occur in the network.
Recommended Action Configure a valid metric for given LSA type and link type on the router that originated the reported LSA.
Error Message%OSPFv3-4-NO_GLOBAL_ADDR: Could not select a global IPv6 address. Virtual links require at least one global IPv6 address.
Explanation A virtual link was configured. For the virtual link to function, a global IPv6 address must be available. However, no global IPv6 address could be found on the router.
Recommended Action Configure a global IPv6 address on an interface on this router.
Error Message%OSPFv3-4-NO_OUTPUTQ: Packet not written to the output queue
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPFv3-3-NO_SNMP_IFINDEX: Interface %s does not have an SNMP MIB ifIndex and has been disabled
Explanation The OSPF process has been configured to use the SNMP MIB ifIndex value for the interface IDs. However, the ifIndex is not set on this interface, so the interface cannot be enabled.
Recommended Action Unconfigure interface-id snmp-if-index for this OSPF process.
Error Message%OSPFv3-3-NOBACKBONE: Flagged as being an ABR without a backbone area
Explanation The router was flagged as an Area Border Router (ABR) without backbone area in the router.
Recommended Action Restart the OSPF process.
Error Message%OSPFv3-4-NONEIGHBOR: Received %s from unknown neighbor %i
Explanation An OSPF hello, database description, or database request packet was received, but the router could not identify the sender.
Recommended Action This situation should correct itself. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%OSPFv3-4-NORTRID: OSPFv3 process %d could not pick a router-id, please configure manually
Explanation OSPFv3 failed while attempting to allocate a router ID from the IP address of one of its interfaces.
Recommended Action Make sure that there is at least one interface that is up and has a valid IP address. If there are multiple OSPF processes running on the router, each requires a unique router ID. You must have enough active interfaces so that each of them can obtain a router ID.
Error Message%OSPFv3-3-NOSELF: if %s if_state %d
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPFv3-4-NULL_LINKAGE: Doubly linked list linkage is NULL
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPFv3-4-NULL_PREV_LINKAGE: Doubly linked list prev linkage is NULL %x
Explanation An internal error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%OSPFv3-3-RDB_NO_LSA: lsid %i adv %i type 0x%x gateway %i metric %d network %i mask %i protocol %#x attr %#x net-metric %d
Explanation OSPF has found an inconsistency between its database and the IP routing table.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at