Table Of Contents
NETWORK_CLOCK_SYNCHRONIZATION Messages
HWIF_QOS Messages
The following are Port QOS messages.
Error Message%HWIF_QOS-6-EOM_FORCE_TRUSTED : EoMPLS on [chars] caused install of 'trust cos' state
Explanation If EoMPLS is configured on the interface or any of its subinterfaces, the 'no trust' state is auto-replaced by 'trust cos'.
Recommended Action Remove all EoMPLS configuration from the interface to restore 'no trust'.
Error Message%HWIF_QOS-6-EOM_RESTORE_UNTRUSTED : The 'no trust' state is restored on EoMPLS removal from [chars]
Explanation If EoMPLS is de-configured on the interface and all its subinterfaces, the configured 'no trust' state is restored.
Recommended Action No action is required.
Error Message%HWIF_QOS-6-EOM_TRUST_NOT_INSTALLED : 'no trust' command is not installed on [chars] in presence of EoMPLS
Explanation If EoMPLS is configured on the interface or any of its subinterfaces, the 'no trust' command is not installed.
Recommended Action Remove all EoMPLS configuration from the interface.
HW_PARSING_ENGINE Messages
Error Message%HW_PARSING_ENGINE-3-DROP_FIFO_OVERFLOW : Parsing Engine Drop Fifo Overflow
Explanation This message indicates that the DFC WAN Line Card parsing engine has detected that the Drop FIFO queue has exceeded the maximum limit. New updates will be discarded. The parsing engine continues to process data from the interfaces if possible.
Recommended Action If traffic has resumed, no action is required. 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%HW_PARSING_ENGINE-3-INTERRUPT_ERROR : [chars]
Explanation This message indicates that the DFC WAN Line Card parsing engine has detected the specified interrupt event. The message text on the console or in the system log provides more information on this error. The parsing engine continues to process data from the interfaces if possible.
Recommended Action If traffic has resumed, no action is required. 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%HW_PARSING_ENGINE-3-MASTER_ABORT : Parsing Engine CPU Master Abort Error
Explanation This message indicates that the DFC WAN Line Card parsing engine has detected a CPU Master Abort Interrupt. A read to a write-only register or a write to a read-only register could cause this interrupt. The parsing engine continues to process data from the interfaces if possible.
Recommended Action If traffic has resumed, no action is required. 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%HW_PARSING_ENGINE-3-PARITY_ERROR : Parsing Engine CPU Parity Error
Explanation This message indicates that the DFC WAN Line Card parsing engine has detected a CPU parity. Suspect hardware fault on second occurrence only. Otherwise, the Parsing Engine continues to process data from the interface if possible.
Recommended Action If traffic has resumed, no action is required. 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%HW_PARSING_ENGINE-3-RP_INT_WATCHDOG_TIMEOUT : Parsing Engine RP Interface Watchdog Timeout
Explanation This message indicates that the DFC WAN Line Card parsing engine has detected an RP interface Watchdog Timeout. The RP Interface process has not relinquished the processor for the watchdog timeout period. The parsing engine continues to process data from the interfaces if possible.
Recommended Action If traffic has resumed, no action is required. 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.ID82545 Messages
The following are Intel 82545 E/FE/GE Controller messages.
Error Message%I82545-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.
IDBINDEX_SYNC Messages
The following are Interface Desriptor Block (IDB) index synchronization messages.
Error Message%IDBINDEX_SYNC-3-IDBINDEX_ENTRY_DEL : Cannot delete entry from interface index table: "[chars]", [dec]
Explanation An interface index table entry is not deleted from the interface index table due to an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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 the show running-config, show logging, show monitor event-trace ifnum merged all, show ifnum list, show ifnum statistics, show cef idb and show cef interface commands. Also provide the sequence of commands that was used to reproduce the error.Error Message%IDBINDEX_SYNC-3-IDBINDEX_ENTRY_SET : Cannot set entry to interface index table: "[chars]", [dec]
Explanation An interface index table entry is not set to the interface index table due to an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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 the show running-config, show logging, show monitor event-trace ifnum merged all, show ifnum list, show ifnum statistics, show cef idb and show cef interface commands. Also provide the sequence of commands that was used to reproduce the error.Error Message%IDBINDEX_SYNC-3-INIT_ERR : [chars]
Explanation The interface index synchronization ISSU client has an initialization 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. Provide the output of the show running-config, show logging, show monitor event-trace ifnum merged all, show ifnum list, show ifnum statistics, show cef idb and show cef interface commands. Also provide the sequence of commands that was used to reproduce the error.Error Message%IDBINDEX_SYNC-3-IPC_ERR : [chars]: [chars].
Explanation The interface index synchronization IPC session has an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the output of the show running-config, show logging, show monitor event-trace ifnum merged all, show ifnum list, show ifnum statistics, show cef idb and show cef interface commands. Also provide the sequence of commands that was used to reproduce the error.Error Message%IDBINDEX_SYNC-3-ISSU_ERR : [chars][chars], rc=[dec]
Explanation The interface index synchronization ISSU client has an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the output of the show running-config, show logging, show monitor event-trace ifnum merged all, show ifnum list, show ifnum statistics, show cef idb and show cef interface commands. Also provide the sequence of commands that was used to reproduce the error.Error Message%IDBINDEX_SYNC-3-RF_ERR : [chars] [dec].
Explanation The interface index synchronization RF client has 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. Provide the output of the show running-config, show logging, show monitor event-trace ifnum merged all, show ifnum list, show ifnum statistics, show cef idb and show cef interface commands. Also provide the sequence of commands that was used to reproduce the error.IDBMAN Messages
The following are IDB Manager (IDBMAN) messages.
Error Message%IDBMAN-4-CONFIG_WRITE_FAIL : FFailed to generate confgiruation for interface [chars]
Explanation Failed to generate configuration for the specified interface because of a problem with the file system. If this happens, the active and standby supervisor will have configuration mismatch. The standby supervisor is reloaded to recover from the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.IDMGR Messages
The following are ID Manager messages.
Error Message%IDMNGR-7-ALLOCFAIL : Error: Failed to allocate memory for [chars]
Explanation Internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IDMNGR-3-CORECTXALLOC : Error: Unable to handle request [hex]
Explanation Unable to handle a client 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%IDMNGR-3-INVALIDEVENT : Error: Invalid process event received [dec]
Explanation Internal process 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%IDMGR-3-INVALID_ID : bad id in [chars] (id: [hex])
Explanation An ID Manager 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IDMNGR-3-INVALIDREQUEST : Error: Invalid request type received [dec]
Explanation Unable to handle a client 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%IDMNGR-3-NOPROCESS : Error: NO idmgr process
Explanation Internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IDMNGR-3-PROCNAME : Error: Unable to get idmgr process name for request [hex]
Explanation Unable to handle a client request or event .
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. . Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IDMGR-3-ID_MANAGER_INTERNAL_ERROR : [chars]
Explanation Internal error occured with ID Manager.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.IEDGE Messages
The following are Intelligent Services Gateway (ISG) messages.
Error Message%IEDGE-4-PBHK_DEPLETED_INDICES : No more portbundles can be allocated
Explanation The source interfaces configured for the Portbundle Hostkey feature are not sufficient and the number of portbundles available are all in use.
Recommended Action Check the configuration on the ISG. Add more source interfaces in the configuration.
Error Message%IEDGE-4-TC_UNDEFINED_ACL : Traffic class ACL [chars] is not defined, creating permit all ACL
Recommended Action The ACL specified for classification of traffic is not configured on the ISG. Creating a permit all ACL. ACL should be configured on the ISG.
Recommended Action Configure the ACL on the ISG.
IF Messages
The following are interface messages.
Error Message%IEDGE-4-TC_UNDEFINED_ACL : Traffic class ACL [chars] is not defined, creating permit all ACL
Explanation The ACL specified for classification of traffic is not configured on the ISG. Creating a permit all ACL. ACL should be configured on the ISG.
Recommended Action Configure the ACL on the ISG.
IF Messages
The following are interface messages.
Error Message%IF-3-BADLOCK : Invalid lock use for [chars]: [chars][chars]
Explanation Application layer code attempted to access an unlocked interface.
Recommended Action LOG_STD_ACTION.
IFMGR Messages
The following are interface manager messages.
Error Message%IFMGR-3-IFINDEX_PERSIST_ENTRY_CORRUPT : [chars] seems to be corrupted. Trying to read [dec] size
Explanation The ifIndex-table seems to be corrupted.
Recommended Action Delete the ifindex-table.
Error Message%IFMGR-3-IFTDB : IF manager interface table database [chars] failure- [dec]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%IFMGR-3-INVALID_PERSISTENT_DATA : Invalid persistent data
Explanation Trying to write invalid persistent data.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IFMGR-3-NOTYPEVECTOR : Interface manager failed to allocate IF type vector. size [dec]
Explanation The interface type vector was not able to be allocated with the number of elements required--initially or resize.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IFMGR-3-VECTOREXD : IF manager attempted to use interface [dec] outside vector range.
Explanation This message indicates that an interface with too large of an ifIndex value was attempted to be added to the IF-MGR DB.
Recommended Action Additional IF-MGR warning and/or error messages should accompany indication of this error. These additional messages should provide more details on the affected interface.
Error Message%IFMGR-3-VECTORPOSUSED : IF manager attempted to add interface [dec] which was already added.
Explanation This message comes from the IF-MGR DB when it is trying to add an ifIndex value for this interface which already exists in the ifIndex DB.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.INBAND Messages
The following are INBAND messages.
Error Message%INBAND-3-INVALID_SEND : Invalid send operation (packet on [chars])
Explanation Internal error caused illegal call to device driver. Normal operation continues.
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%INBAND-3-NO_BUFFER_POOLS : Initialization of private buffer pools failed
Explanation Private buffer pools not created for naboo ibc.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%INBAND-3-TOOBIG : An attempt made to send giant packet on [chars] ([dec] bytes from [hex], max allowed [dec])
Explanation An attempt was made to send an oversized packet.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.INTR_MGR Messages
The following are Interrupt Manager messages.
Error Message%INTR_MGR-3-BURST : [chars] [chars] [[dec]]
Explanation A burst of hardware interrupts of the type indicated has occurred.
Recommended Action The message text on the console or in the system log provides more information on the specific nature of the message. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%INTR_MGR-3-INTR : [chars] [chars]
Explanation The specified interrupt event has been detected.
Recommended Action The message text on the console or in the system log provides more information on the specific nature of the message. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%INTR_MGR-3-MAXBURST : [chars] [chars] [[dec]]
Explanation The specified hardware interrupt has exceeded the maximum allowed number of bursts.
Recommended Action The message text on the console or in the system log provides more information on the specific nature of the message. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.IP Messages
The following are Internet Protocol messages.
Error Message%IP-3-IPTOPOID : Topology ID [hex] is invalid, can't get the base topology ID.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IP-3-MAXIRDP : Attempt to send IRDP to proxies exceeding configurable limit: [dec], interface: [chars], secondary = [dec], proxy = [dec]
Explanation The sum of configured secondary addresses and configured proxy addresses exceeds the number of total addresses that the IRDP can support in its implementation.
Recommended Action Reduce the number of either the secondary IP addresses or proxy addresses configured for the interface.
Error Message%IP-3-NONALIAS : non-alias address [IP_address] in table [chars] found in IP alias list
Explanation The IP alias list holds IP aliases only but non-alias entries are found.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.IPAD Messages
The following are IPAD messages.
Error Message%IPAD-3-BLOCKEMPTY : Block does not exist.
Explanation Try to access a block that does not exist.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPAD-3-CTXTMASKTYPE : Search context mask type or sub type not recognized: [dec], [dec]. Search
context last found IP address [IP_address], search context target IP address [IP_address].Explanation An internal IPAD error occurred. Search context mask type not defined.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPAD-3-LISTTYPE : Double-linked list (DLL) type not recognized: [dec].
Explanation An internal IPAD error occurred. DLL type not defined.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPAD-3-MEMORY : Can not allocate memory for a block in IPAD: [chars]
Explanation The operation might have failed due to lack of memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPAD-3-TRIM : Access on level [dec], to the left of index [dec].
Explanation IPAD is not trimmed properly.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.IPC Messages
The following are Inter-Process Communication messages.
Error Message%IPC-2-INITFAILED : [chars]
Explanation IPC Resource Management Initialization failed.
Recommended Action This is a critical failure for IPC functionality. Copy the message exactly as it appears on the console or in the system log. Enter the sh version 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.Error Message%IPC-6-MAXRPCTIMEOUT : Maximum RPC timeout value [dec] seconds set for port [hex]
Explanation The maximum RPC timeout for an IPC message exceeds the maximum expected value of 10 minutes.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%IPC-4-MSGMAXTIMEOUT : Invalid maximum timeout value [dec] seconds; Period - [dec]; Retries - [dec]
Explanation The maximum message timeout for an IPC message exceeds 2 minutes.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show version command to gather data that might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%IPC-2-NODISPATCH : Message for [hex].[hex] has no receive queue or dispatch routine
Explanation The IPC user failed to provide any means of handling the received message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show ipc ports 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.Error Message%IPC-5-NULLDELFUNC : Invalid registration
Explanation An IPC application has attempted to register NULL function in the IPC initialization list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc 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.Error Message%IPC-5-OUTPUT_FAIL : Num [dec] Func=[hex] Seat: ID=[hex] [chars] Sent [dec] Heard [dec]
Explanation The IPC module has failed in transmitting an IPC message to the indicated seat with the last specified sequence number sent and last sequence number acknowledged.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc 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.Error Message%IPC-6-STATEFUL : [chars]
Explanation A Stateful IPC Event occurred.
Recommended Action No action is required.
Error Message%IPC-5-WATERMARK : [dec] messages pending in [chars] for the port [chars]([hex].[hex]) from source seat [hex]
Explanation Several IPC messages are pending to be processed. If the number increases, it might result in the IPC header cache or buffers being exhausted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc 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.IPCGRP Messages
The following are RP Interprocess Communication messages.
Error Message%IPCGRP-6-BARENBDISAB : Barium interface [chars] Primary [chars]
Explanation The Barium interface has been enabled or disabled.
Recommended Action No action is required.
Error Message%IPCGRP-6-LCREBOOT : LC Reset due to "[chars]".
Explanation The LC has been reset.
Recommended Action No action is required.
IPCOIR Messages
The following are IPC Online Insertion and Removal (OIR) messages.
Error Message%IPCOIR-3-CARD_WRONGTYPE : Mismatched card type ([chars]) in slot [dec]/[dec]. Expected type [chars]. Use 'no card [dec]/[dec]' command to override preprovisioning and update card type.
Explanation The line card inserted does not match the currently provisioned card type.
Recommended Action Replace the wrong card type with the currently provisioned card type, or enter "no card" to allow a new card type to be discovered.
Error Message%IPCOIR-3-CARD_WRONGTYPE_HH : Mismatched card type ([chars]) in slot [dec]/[dec]. Expected half-height card. Use 'no card [dec]/[dec]' command to override preprovisioning and update card type.
Explanation The line card inserted does not match the currently provisioned card type.
Recommended Action Replace the wrong card type with the currently provisioned card type, or enter "no card" to allow a new card type to be discovered.
Error Message%IPCOIR-3-IVFS_BROKEN : IVFS image file [chars] corrupted.
Explanation The indicated IVFS image file is corrupted.
Recommended Action Reinstall the file and/or ensure the filename is provisioned correctly.
Error Message%IPCOIR-5-IVFS_FILE_LOADING : Extracting [chars] from [chars].
Explanation The image for the indicated line card type has been located.
Recommended Action Normal operation, wait a moment for it to complete.
Error Message%IPCOIR-3-IVFS_MISSING : IVFS image file [chars] not found.
Explanation The indicated IVFS image file was not found.
Recommended Action Ensure the IVFS contains this line card image filename.
Error Message%IPCOIR-3-JACKETSLOTCONFLICT : card [chars] in slot [[dec]/[dec]] Jacket card slot conflict shutting down card if present
Explanation The Jacket card cannot be plugged into an even slot.
Recommended Action Insert Jacket card into an odd slot .
IP_DEVICE_TRACKING Messages
The following are Switch IP Host Tracking messages.
Error Message%IP_DEVICE_TRACKING-4-TABLE_LOCK_FAILED : Table already locked by process-id [dec]([chars])
Explanation The IP device tracking table could not be updated due to a lock held by another process.
Recommended Action No action is required.
Error Message%IP_DEVICE_TRACKING_HA-4-ENTRY_OUT_OF_SYNC : Host mac-address [enet] ip-address [IP_address] interface [chars]
Explanation An inconsistency has been detected in the IP device tracking table for this host between active and standby.
Recommended Action No action is required.
IPFAST Messages
The following are IP Fast Switching messages.
Error Message%IPFAST-2-FASTPORTCREATEERR : Attempt to create [chars] failed after [dec] retries (last error:[chars])
Explanation The line card attempted to create a port to the Route processor but has failed after a few retries. This might result in CEF getting disabled in 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%IPFAST-4-FASTPORTCREATEWARN : Attempt to create [chars] failed. Will be retried [dec] times (last error:[chars])
Explanation The line card is attempting to create a port to the Route processor but has failed. This could be a transient behavior; retries will be attempted.
Recommended Action The router should be able to recover from this situation. If CEF gets disabled for this line card, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPFAST-2-FASTPORTOPEN : Requested to open [chars], id [int] when already open. Attempting to re-open.
Explanation The line card is attempting to open a port to the Route processor when one is already open. This could be transient behavior but might result in multiple ports opened for the same purpose.
Recommended Action The router should be able to recover from this situation. If CEF problems develop for this line card, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPFAST-2-FASTPORTOPENERR : Attempt to open [chars] failed after [dec] retries (last error:[chars])
Explanation The line card attempted to open a port to the Route processor but has failed after a few retries. This might result in CEF getting disabled in 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%IPFAST-4-FASTPORTOPENWARN : Attempt to open [chars] failed. Will be retried [dec] times (last error:[chars])
Explanation The line card is attempting to open a port to the Route processor but has failed. This could be a transient behavior ; retries will be attempted.
Recommended Action The router should be able to recover from this situation. If CEF gets disabled for this line card, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPFAST-2-FASTPORTREGISTERERR : Attempt to register [chars] failed after [dec] retries (last error:[chars])
Explanation The line card attempted to register a port to the Route processor but has failed after a few retries. This might result in CEF getting disabled in 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%IPFAST-4-FASTPORTREGISTERWARN : Attempt to register [chars] failed. Will be retried [dec] times (last error:[chars])
Explanation The line card is attempting to register a port to the Route processor but has failed. This could be a transient behavior; retries will be attempted.
Recommended Action The router should be able to recover from this situation. If CEF gets disabled for this line card, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPFAST-2-MSGDROP : IPC queue limit is reached and message is dropped. queue limit = [dec] cumulative drops = [dec]
Explanation IPC raw queue limit for IP fast path is reached.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPFAST-5-SUCCEEDOPENIPCPORT : Attempt to open the IPC ports succeeded. [chars]
Explanation Ipfast succeeded in an attempt to open the ipc port to communicate to the LC/RRP/SP.
Recommended Action No action is required.
IPMCAST_RPF Messages
The following are Multicast RPF messages.
Error Message%IPMCAST_RPF-4-FOREIGN_VRF : RPF for [IP_address] (VRF [chars]) resolves in a foreign VRF ([chars])
Explanation RPF resolves in a foreign VRF without specifing any encapsulation or non-IP transport, multicast cannot handle this, thus a tree will not be built. This could be a temporary condition, but if the error persists, check your routing configuration.
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%IPMCAST_RPF-3-INTERNAL_ERROR : An internal error has occured while obtaining RPF information ([chars])
Explanation RPF handling Internal error.
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%IPMCAST_RPF-3-RIB_REGISTER_FAIL : Failed to register with RIB, multicast RPF lookups will notfunction
Explanation Multicast could not register with RIB to obtain RPF information later. This will cause a severe problem when there is multicast traffic flow, since it will not be possible to obtain RPF 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.Error Message%IPMCAST_RPF-4-RIB_UNREGISTER_FAIL : Multicast failed to unregister with RIB
Explanation Multicast could not unregister with RIB when multicast is disabled. There will not be any existing traffic flow since multicast is already disabled. However, if enabled again, and if a problem is seen with multicast traffic flow, it should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPMCAST_RPF-4-RPF_LOOKUP_LOOP : RPF route lookup loop for [IP_address]
Explanation A routing loop occurred during the recursive resolution of an RPF address.
Recommended Action Check routing tables used for RPF.
Error Message%IPMCAST_RPF-4-RTMGR_TOPO_ERR : Unexpted error accessing topology specific information
Explanation An internal error has occured while accessing topology specific information. The RPF informationmight not be obtained as a result, thus resulting in problems with multicast flows.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%IPMCAST_RPF-3-START_FAIL : Error trying to start RPF watch for prefix [IP_address] ([chars]), RPF information will not be obtained
Explanation Internal error has occured while trying to obtain RPF information for a prefix. Subsequent changes in RPF information for the prefix will also not be obtained as a result. This will impact the multicast traffic flow for this prefix.
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%IPMCAST_RPF-3-STOP_FAIL : Error trying to stop RPF watch for a prefix
Explanation Internal error has occured while trying to stop obtaining RPF change information.
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.IPRT Messages
The following are Internet Protocol Routing messages.
Error Message%IPRT-3-RIB_LOOP R Resolution loop formed by routes in RIB
Explanation RIB route producers have installed routes in the RIB that form a loop during resolution.
Recommended Action Resolve the RIB route loop:
1) Determine which routes are involved in the loop be entering the show ip route loops command.
2) Correct the protoco