-
Cisco IOS Release 12.0S System Message Guide
-
System Messages Overview
-
AAAA through AUDIT messages
-
AUTORP through C10KSDCC messages
-
C10K_TOASTER through CBUS messages
-
CE3 through CPUIF messages
-
CRYPTO through ECC messages
-
EDGE through EE192 messages
-
EELC through ENV_MON messages
-
ESMP through FM messages
-
FR through GLCSPA messages
-
GRP through GRPSPA messages
-
GRP_CHOCX through GT96K_FE messages
-
HA through I82543 messages
-
ICC through IPV6FIB messages
-
IP_VRF through LC_CHOCX messages
-
LCCOREDUMP through LCINFO messages
-
LCLOG through MBUSFLASH messages
-
MCC192 through MPLS_TE_LM messages
-
MPLS_TE_PCALC through PM3386 messages
-
PM622 through PRP2 messages
-
PS through RSP messages
-
RSVP through SW_MGR messages
-
SYS through TCAM_MGR messages
-
TCATM through XCPA messages
-
Glossary of Acronyms
-
Table Of Contents
MPLS_TE_PCALC Messages
The following are MPLS TE path calculation facility messages.
Error Message%MPLS_TE_PCALC-2-DUP_IP_ADDRESS : [chars] [IP_address] [chars]
Explanation Two nodes have the same stable IP address.
Recommended Action Find the system that has the duplicate IP address and configure a different IP address for that system.
Error Message%MPLS_TE_PCALC-2-DUP_RRR_ID : [chars] [IP_address] [chars]
Explanation Two nodes have the same stable router ID.
Recommended Action Find the system that has the duplicate router ID and configure a different router ID for that system.
Error Message%MPLS_TE_PCALC-3-INIT : pcalc_system_id_size == 0
Explanation An internal inconsistency was detected when an attempt was made to initialize the MPLS TE path calculation system id before the system ID size is known.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
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 A router ID has been received in multiple fragments.
Recommended Action Locate the problem router. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. tative, and provide the representative with the information you have gathered.
Error Message%MPLS_TE_PCALC-2-INVLD_RTR_ID : Invalid router id ([IP_address]) received from [chars] in fragment [int]
Explanation An invalid router LSA has been received. The LSA should not contain a Router ID of zero. The cause of this problem may be a misconfiguration, memory corruption, or unexpected behavior on a router.
Recommended Action Locate the problem router and check the configuration. To determine what is causing this problem, contact your Cisco technical support representative for assistance.
Error Message%MPLS_TE_PCALC-3-LSA : [chars] [chars]
Explanation An internal inconsistency was detected when an attempt was made to establish a handle-received LSA for the MPLS TE topology 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MPLS_TE_PCALC-2-MEM : [chars] [dec]
Explanation A failure at an attempt to allocate memory was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MPLS_TE_PCALC-3-PATH : [chars]
Explanation An internal inconsistency was detected when an attempt was made to establish an MPLS TE tunnel using the MPLS TE path calculation subsystem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
MRIB Messages
The following are Multicast Routing Information Base (MRIB) messages.
Error Message%MRIB-4-DEBUGERR : Debugging error: [chars] in [chars] line [dec] ([chars])
Explanation An error related to the debugging subsystem 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB-4-FILTRVIOLERR : Filter violation error: conn [dec] ([chars]:[chars]) in [chars]
Explanation A client tried to modify a route attribute that it does not own.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB-3-GENCOMMERR : Communication error: [chars] [chars] in [chars]
Explanation An IPC 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB-3-GENINITFAIL : Initialization failed: [chars] [chars]
Explanation An unrecoverable error occurred during system initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB-4-INCORRECTPARS : Illegal parameter in function call ([chars]) in [chars]
Explanation An externally accessible function was called with illegal parameters. The parameters have been changed to an acceptable 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB-3-INTERNALERR : Internal error: [chars] in [chars] line [dec] ([chars])
Explanation An internal software error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB-2-NOMEMORY : No memory for [chars] in [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MRIB-4-NOMEMORYW : No memory for [chars] in [chars]. Handling: [chars]
Explanation The requested operation could not be accomplished because of a low memory condition. The problem has been processed locally.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MRIB-3-REDUCEDFUNCT : Initialization of "[chars]" functionality failed
Explanation The initialization of a function has failed. This component might continue to operate without the specified functionality.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
MRIB_API Messages
The following are Multicast Routing Information Base (MRIB) client API messages.
Error Message%MRIB_API-3-ASYNC_ERR : Asynchronous error: [chars]
Explanation An asynchronous error occurred in the MRIB API.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_API-7-ASYNC_WAR : Warning: [chars]
Explanation A recoverable error condition occurred in the MRIB API.
Recommended Action No action is required.
Error Message%MRIB_API-3-CORRPT : Corrupted update: [chars]
Explanation A corrupted update was received from the MRIB by the MRIB API.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_API-3-REG_FAIL : Server unexpected error: [chars]
Explanation An internal error occurred in a registry call from the MRIB API.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
MRIB_PROXY Messages
The following are Multicast Routing Information Base (MRIB) proxy messages.
Error Message%MRIB_PROXY-2-MRIB_LC_FAILED_GET_IPC : LC failed allocating IPC buffer which may lead to data loss or inconsistent MFIB states, slot = [dec]
Explanation The line card has failed to allocate an interprocessor communication buffer.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MRIB_PROXY-2-MRIB_LC_FAILED_IDB_MAP : LC failed in mapping interface number [dec]
Explanation The line card failed to map an interface from the global representation to a local representation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_PROXY-2-MRIB_LC_FAILED_IPC_ACK : RP failed in getting Ack for IPC message of type = [dec], status = [dec], error = [chars]
Explanation The Route Processor failed to obtain IPC acknowledgment.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_PROXY-2-MRIB_LC_FAILED_IPC_OPEN : LC in slot [dec] failed to open IPC port to RP, error = [chars]
Explanation The line card failed to open an IPC port toward the Route Processor.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_PROXY-2-MRIB_LC_FAILED_SEND_LC_READY : LC in slot [dec] failed to send LC ready to RP, error = [chars]
Explanation The line card failed to send a Ready message to the Route Processor.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_PROXY-2-MRIB_LC_READY_NOIPC : LC failed allocating IPC buffer to send LC ready, slot = [dec]
Explanation The line card has failed to allocate an interprocessor communication buffer in order to send the Ready message.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MRIB_PROXY-2-MRIB_RP_FAILED_GET_IPC : RP failed allocating IPC buffer which may lead to data loss or inconsistent MFIB states
Explanation The Route Processor failed to allocate an interprocessor communication buffer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_PROXY-2-MRIB_RP_FAILED_IDB_MAP : RP failed in mapping interface
Explanation The Route Processor failed to map an interface from the global representation to the local representation, or from the local representation to the global representation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_PROXY-2-MRIB_RP_FAILED_IPC_ACK : LC failed in getting Ack for IPC message of type = [dec], status = [dec], error = [chars]
Explanation The line card has failed to obtain an IPC acknowledgment.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_PROXY-2-MRIB_RP_FAILED_IPC_CREATE : RP failed in creating IPC port, error = [chars]
Explanation The Route Processor failed to create an MFIB IPC port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_PROXY-2-MRIB_RP_FAILED_LC_DIST_MODE_INIT_PROC : RP failed in creating distribute mode init process for a linecard, slot = [dec]
Explanation The Route Processor failed to create a distributed mode initialization process for a 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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_PROXY-2-MRIB_RP_FAILED_LC_PORT_INFO : RP failed in creating linecard port info for distributed mode, slot = [dec]
Explanation The Route Processor failed to create line card port information for distributed mode 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_PROXY-2-MRIB_RP_FAILED_LC_PORT_OPEN : RP failed in opening linecard port info for distributed mode, slot = [dec]
Explanation The Route Processor failed to obtain line card port information for distributed mode 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MRIB_PROXY-2-MRIB_RP_FAILED_RPC_REPLY : RP failed in sending [chars] reply to a linecard in slot = [dec], IPC error = [chars]. This is normal after linecard removal or reset. At other times, data loss or mroute state inconsistency may result.
Explanation The Route Processor failed to send a remote procedure call reply to a line card. This condition is normal after a line card has been removed or reset. At other times, data loss or multicast route state inconsistency may result.
Recommended Action If a line card has been removed or reset, no action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
MROUTE Messages
The following are multicast route messages.
Error Message%MROUTE-6-LARGE_TWHEEL_DELAY : Exceeded maximum delay ([dec] ms) requested: [dec]
Explanation Because of the way the timer wheel works, there is a maximum delay defined. If a function is scheduled with a higher delay, it will be scheduled using the maximum delay possible minus a small delay offset. A timer with large delay was requested.
Recommended Action Check if a large IGMP query interval is set. Some timers may refresh periodically to allow for the large delay. No action is required.
Error Message%MROUTE-3-MIDB_QUEUE_ERR : Interface [chars] not in ([IP_address], [IP_address])
Explanation An error in maintaining the multicast route table has occurred. The MIDB has the highest expiration timer but was not in the MDB->MIDB.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. tative, and provide the representative with the information you have gathered.
Error Message%MROUTE-3-ROUTECOUNT_ERR : Running multicast route count [int]
Explanation An error in maintaining the multicast route count has occurred. The running count of multicast routes is different from that in the multicast routing table.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MROUTE-3-ROUTECOUNT_ZERO : Multicast route count reached zero
Explanation An error in maintaining the multicast route count has occurred; the running count of multicast routes has reached zero when it should be nonzero.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MROUTE-4-ROUTELIMIT : [int] routes exceeded multicast route-limit of [dec] - VRF [chars]
Explanation The number of multicast routes exceeds the configured maximum number. 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, enter the ip multicast route-limit command to increase the number of multicast routes. Otherwise, no action is required.
Error Message%MROUTE-4-ROUTELIMITWARNING : multicast route-limit warning (curr [int] threshold [int]) - VRF [chars]
Explanation The number of multicast routes has reached the configured percentage of the multicast route limit.
Recommended Action Consider increasing the multicast route limit.
Error Message%MROUTE-4-RPF_LOOKUP_LOOP : RPF route lookup loop for [IP_address], route [IP_address]/[dec]
Explanation A possible routing loop is caused because the Route Processor is forwarding routes to different tables.
Recommended Action Verify that the routing tables used for RPF are configured properly.
Error Message%MROUTE-3-TWHEEL_DELAY_ERR : Exceeded maximum delay ([dec] ms) requested: [dec]
Explanation An error in maintaining the timer wheel has occurred. If you try to schedule a function with a delay higher than the defined maximum delay, it will be scheduled using the maximum delay possible.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. tative, and provide the representative with the information you have gathered.
Error Message%MROUTE-3-TWHEEL_ERR : Timer wheel internal error
Explanation A timer wheel 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. tative, and provide the representative with the information you have gathered.
Error Message%MROUTE-3-TWHEEL_INT_ERR : Timer wheel error at interrupt level [dec]
Explanation An internal error involving timer wheel maintenance 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MROUTE-3-TWHEEL_SLOT_ERR : Timer wheel event:[hex] slot:[dec] func:[hex] unequal to exec slot: [dec]
Explanation A timer wheel event contains an inconsistent slot number.
Recommended Action Enter the clear ip mroute * command. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%MROUTE-3-TWHEEL_INSERT_ERR : An error occured after inserting or executing a timer wheel event
Explanation An error occurred after inserting or executing a timer wheel event. An error in maintaining the timer wheel 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. tative, and provide the representative with the information you have gathered.
Error Message%MROUTE-3-WAVLINIT : Could not initialize WAVL tree for ([IP_address],[IP_address])
Explanation An error in initializing the multicast routing occurred. Because you cannot search for MIDBs when the WAVL tree cannot be initialized, there is no reason to keep the MDB.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. tative, and provide the representative with the information you have gathered.
MSDP Messages
The following are multicast source discovery protocol (MSDP) messages.
Error Message%MSDP-5-PEER_IS_SELF : Peering with self ([IP_address])
Explanation MSDP is attempting a peering operation with itself.
Recommended Action Check the address of the MSDP peer.
Error Message%MSDP-5-PEER_UPDOWN : Session to peer [IP_address] going [chars]
Explanation The session to the specified peer has reached a specific state. Going up means that the session to the specified peer has reached the Established state. Going down means that the session to the specified peer has reached the Inactive state.
Recommended Action This message is informational. No action is required.
Error Message%MSDP-4-PKT_TOO_BIG : Message size violation on [int]-byte packet from [IP_address], discarded
Explanation A message larger than the maximum MSDP message size was received.
Recommended Action Verify that the MSDP message size is set correctly. If this problem persists, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative, and provide the representative with the information you have gathered.
Error Message%MSDP-4-SA_LIMIT : SA from peer [IP_address], RP [IP_address] for ([IP_address], [IP_address]) exceeded sa-limit of [dec]
Explanation The number of MSDP SAs exceeds the configured maximum number. SA cache entries cannot be added unless the configuration is changed.
Recommended Action If MSDP SAs come from legitimate sources or RPs, use the ip msdp sa-limit command to increase the number of SA entries allowed from the subject peer; otherwise no action is required.
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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
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. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
MUESLIX Messages
The following are Mx serial application-specific integrated circuit (ASIC) messages.
Error Message%MUESLIX-3-DISCOVER : Mx serial (bay [dec]): Interface found: [dec]
Explanation The system could not recognize all the Mueslix devices that are present on the system.
Recommended Action Try to reseat the PA properly in the system slots. If this error message recurs, verify for a hardware failure including the 7200 chassis in the case of the Cisco 7200, or the VIP in case of RSP and the PA, as this error will come only if there is a failure in hardware.
Error Message%MUESLIX-1-DWNLDFL : Mx serial (bay [dec]): PA down load failed
Explanation The Mx serial hardware has failed. It could not download its operational microcode.
Recommended Action Try to reseat the PA properly in the system slots. If this error message recurs, verify for a hardware failure including the 7200 chassis in the case of the Cisco 7200, or the VIP in case of RSP and the PA, as this error will come only if there is a failure in hardware.
Error Message%MUESLIX-1-FAILURE_CAUSE : [chars]: [chars][chars]: [hex], [hex]
Explanation A STOPFAIL/STARTFAIL problem has occurred.
Recommended Action Copy the information from the port adaptor to show what error caused the STOPFAIL/STARTFAIL problem. Enter the debug serial mueslix debug command. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show log commands command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show log command output, contact your Cisco technical support representative and provide the representative with the information you have gathered. After that you can disable the debug serial mueslix command.
Error Message%MUESLIX-1-HALT : Mx serial: [chars] TPU halted: cause [hex] status [hex] shadow [hex]
Explanation The Mx serial firmware is not in synchronization with the driver.
Recommended Action This condition will clear by itself. Enter the debug serial mueslix debug command. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show log commands command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show log command output, contact your Cisco technical support representative and provide the representative with the information you have gathered. After that you can disable the debug serial mueslix command.
Error Message%MUESLIX-1-INITFAIL : Mx serial (bay [dec]), Init Failed at [chars]
Explanation The Mx serial port adaptor failed to complete its hardware initialization.
Recommended Action Try to reseat the PA properly in the system slots. If this error message recurs, verify for a hardware failure including the 7200 chassis in the case of the Cisco 7200, or the VIP in case of RSP and the PA, as this error will come only if there is a failure in hardware.
Error Message%MUESLIX-3-NOTMUESLIX : Mx serial (bay [dec]): Device reported [hex]
Explanation The system hardware has failed. A non-Mx serial device pointed at the Mx serial software.
Recommended Action Check the system configuration for the failure in the bay number that is reported in the error message. If it is not a Mx-based PA, contact the appropriate component to which that PA belongs. If it is a Mx-based PA, try to reseat the PA once again. If this error message recurs, issue the show tech-support and show log commands command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show log command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%MUESLIX-3-OWNERR : [dec] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The Mx serial driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Enter the debug serial mueslix debug command. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show log commands command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show log command output, contact your Cisco technical support representative and provide the representative with the information you have gathered. After that you can disable the debug serial mueslix command.
Error Message%MUESLIX-1-STARTFAIL : Mx serial, [chars] Start Failed at [chars]
Explanation A software or hardware error has occurred. The Mx microcode is not responding to the enable command used to restart the serial interface.
Recommended Action Enter the debug serial mueslix debug command. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show log commands command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show log command output, contact your Cisco technical support representative and provide the representative with the information you have gathered. After that you can disable the debug serial mueslix command.
Error Message%MUESLIX-1-STOPFAIL : Mx serial, [chars] Stop Failed at [chars]
Explanation A software or hardware error has occurred. The Mx microcode is not responding to the disable command used to stop the serial port.
Recommended Action Enter the debug serial mueslix debug command. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show log commands command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show log command output, contact your Cisco technical support representative and provide the representative with the information you have gathered. After that you can disable the debug serial mueslix command.
NBAR Messages
The following are NBAR messages.
Error Message%NBAR-2-NOMEMORY : No memory available for [chars]
Explanation An attempt to allocate memory for the specified device or task has failed.
Recommended Action Reduce system activities to ease memory demands. Try disabling some features or apply filtering to decrease the sizes of the system data structures, such as the routing table. If conditions warrant, upgrade to a larger memory configuration.
Error Message%NBAR-2-NOSTATEMEM : Memory for maintaining state used up
Explanation NBAR uses memory to maintain state information about stateful flows. There is a maximum limit on how much memory NBAR can use for this purpose and this limit has been reached.
Recommended Action Increase memory on the platform.
Error Message%NBAR-2-RMINVALIDCONFIG : NBAR resource manager : too many buckets ([dec])
Explanation NBAR was configured so that the internal data structures that are needed to maintain stateful protocol information were too large.
Recommended Action Configure the router using the ip nbar resources command to specify a smaller maximum idle time.
Error Message%NBAR-2-RMNORESOURCE : NBAR resources exhausted
Explanation To save stateful information on protocols, NBAR must use dynamic resources. These resources have been exhausted.
Recommended Action Configure the router using the ip nbar resources command to allocate a larger initial pool of resources. The default number of initial resources is 10,000. Also try configuring a shorter maximum idle time.
OOBP Messages
The following are out-of-band port (OOBP) messages.
Error Message%OOBP-4-ASYNC_NO_RSP : Warning -- reset async oobp no response
Explanation The asynchronous driver does not respond to the async reset command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. tative, and provide the representative with the information you have gathered.
Error Message%OOBP-4-OOBP_CANT_BE_USED : Warning -- oobp can't be used
Explanation The asynchronous driver cannot send out the OOBP message because no resource is indicated.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. tative, and provide the representative with the information you have gathered.
Error Message%OOBP-4-TIMEOUT_AT_WRONG_STATE : Warning -- OOBP driver timeout at wrong state
Explanation The OOBP response timed out at the wrong OOBP state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. tative, and provide the representative with the information you have gathered.
OSPF Messages
The following are Open Shortest Path First (OSPF) messages.
Error Message%OSPF-6-AREACHG : [IP_address][IP_netmask] changed from area [chars] to area [chars]
Explanation A change in the OSPF configuration has caused a network range to change areas.
Recommended Action No action is required.
Error Message%OSPF-6-BADCHKSUM : Checksum Failure in database in area [chars]
Link State Id [IP_address] Old Checksum [hex] New Checksum [hex]Explanation OSPF has detected a checksum error in the database because of memory corruption.
Recommended Action Restart the OSPF process.
Error Message%OSPF-4-BADLENGTH : Invalid length [dec] in OSPF packet type [dec] from [IP_address] (ID [IP_address]), [chars]
Explanation The system received an OSPF packet with a length field that is smaller than the normal header size, or inconsistent with the size of the IP packet in which it arrived. This event 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case 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 [dec], LSID [IP_address] Mask [IP_address] from [IP_address] \nNOTE: This route will not be installed in the routing table.
Explanation The router has received an LSA with an invalid LSA mask. The cause is most likely due to an incorrect configuration from the LSA originator.
Recommended Action Find the originating router of this LSA with an invalid mask, and correct any misconfiguration of the network for this LSA. For further debugging assistance, contact your Cisco technical support representative.
Error Message%OSPF-3-DUP_RTRID : OSPF detected duplicate router-id [IP_address] from [IP_address] on interface [chars]
Explanation OSPF 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 must be unique. Change the router ID for the neighbor.
Error Message%OSPF-3-INVALID_ENCR_PASSWORD : Invalid encrypted password [chars].
Explanation The user-specified encrypted password is invalid. If the specified encrypted password is invalid, an error message will be printed during system configuration.
Recommended Action Either specify a clear text password and enter the service password-encryption command for encryption, or ensure that the specified encrypted password is valid.
Error Message%OSPF-4-NORTRID : OSPF process [dec] cannot pick a router-id.
Please configure manually or bring up an interface with an ip address.Explanation OSPF failed while a router ID was being allocated from the IP address of one of its interfaces.
Recommended Action Ensure that there is at least one interface is operational (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 operational (up) interfaces so that each of them can obtain a router ID.
Error Message%OSPF-4-OSPF_MAX_LSA : Maximum number of non self-generated LSA has been exceeded "[chars]" - [dec] LSAs
Explanation The maximum number of non-self-generated LSAs has been exceeded.
Recommended Action Check to see if a router in the network is generating a large number of LSAs because of a misconfiguration.
Error Message%OSPF-4-OSPF_MAX_LSA_THR : Threshold for maximum number of non self-generated LSA has been reached "[chars]" - [dec] LSAs
Explanation The threshold for the maximum number of non-self-generated LSAs has been reached.
Recommended Action Check to see if a router in the network is generating large number of LSAs as a result of a misconfiguration.
Error Message%OSPF-3-RECONF_VL : OSPF process [dec] is changing router-id. Reconfigure virtual link neighbors with our new router-id
Explanation The OSPF process is being reset, and a new router ID will be selected. This reset process will take down all virtual links. To activate the links again, virtual link configuration requires to be changed on all virtual link neighbors.
Recommended Action Change the virtual link configuration on all virtual link neighbors to reflect the newly assigned new router ID.
Error Message%OSPF-4-WRONG_DEFAULT : Found generating default LSA with non-zero mask
LSA type : [dec] Mask : [IP_address] metric : [int] area : [chars]Explanation The router tried to generate a default LSA with the wrong mask and possibly the wrong metric because of an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
OSPFv3 Messages
The following are Open Shortest Path First (OSPF) messages.
Error Message%OSPFv3-5-ADJCHG : Process [dec], Nbr [IP_address] on [chars] from [chars] to [chars], [chars]
Explanation An OSPF neighbor has changed state. The error 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-6-AREACHG : [IP_address][IP_netmask] changed from area [chars] to area [chars]
Explanation An OSPF configuration change has caused a network range to change areas.
Recommended Action No action is required.
Error Message%OSPFv3-6-BADCHKSUM : Checksum Failure in database in area [chars]
Link State Id [IP_address] Old Checksum [hex] New Checksum [hex]\nExplanation OSPF has detected a checksum error in the database due to a memory corruption.
Recommended Action Restart the OSPF process.
Error Message%OSPFv3-4-BADLENGTH : Invalid length [dec] in OSPF packet fromUnrecognized format ` %P' (ID [IP_address]), [chars]
Explanation The system received an OSPF packet with a length field of less than a normal header size or a size that is inconsistent with the size of the IP packet in which it arrived. This condition 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. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case 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: [chars]: Type [hex], LSID [int] from [IP_address],Unrecognized format ` %P', [chars]
Explanation The router received an invalid LSA. The cause is either memory corruption or unexpected behavior on a router.