-
12.3 T System Message Guide
-
System Message Overview
-
AAA through BSTUN messages
-
C10K through CALL_CONTROL messages
-
CALLRECORD through CPOS messages
-
CRYPTO through DMA messages
-
DNET through ENVM messages
-
ENVMON through FDM_HA messages
-
FECPM through GT96K_TDM messages
-
GTP through HEALTH_MONITOR messages
-
HHM through IPSECV6 messages
-
IPV6 through MICA messages
-
MIPC through NP_VPD messages
-
NRP through PIF messages
-
PIM through PVDM2 messages
-
PXF through RPM_BULK messages
-
RPM_CONN_MGMT through SEC_LOGIN messages
-
SENSOR through SWITCH_IF messages
-
SWITCHOVER through Y88E8K messages
-
Glossary of Acronyms
-
Table Of Contents
PXF Messages
The following are Parallel eXpress Forwarding (PXF) messages.
Error Message%PXF-2-RESTARTEDALL : All PXFs have been restarted.
Explanation All PXF coprocessors have been restarted, either manually via a microcode reload or as a result of an exception.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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.
PXF_DMA Messages
The following are Parallel eXpress Forwarding (PXF) DMA subsystem messages.
Error Message%PXF_DMA-3-FBB_LINE_CARD : [chars]
Explanation A PXF DMA FBB line card 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%PXF_DMA-3-FTBB_ERROR : FTBB is set to disable for slot [int]/[int]!
Explanation FTBB has been disabled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PXF_DMA-3-IRONBUS_NOTRUNNING : Data path to slot [int]/[int] failed to synchronize ([chars])
Explanation A PXF DMA data path could not be initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_DMA-2-TBB_SYNC_FAILED : TBB sync of the RP failed. No traffic is being sent to the RP!
Explanation The TBB synchronization of the Route Processor has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_DMA-2-TBB_SYNC_LC_FAILED : TBB sync of the line card failed (slot [int]/[int]). No traffic is being through the line card. Need to reset the line card.
Explanation The TBB synchronization of the Route Processor has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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.
PXF_FIB Messages
The following are Parallel eXpress Forwarding (PXF) FIB select-specific messages.
Error Message%PXF_FIB-3-WS_FIB_EVENT : [chars]
Explanation This message provides information on generic PXF CEF errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.
PXF_FLOW Messages
The following are Parallel eXpress Forwarding (PXF) NetFlow-related messages.
Error Message%PXF_FLOW-4-AGG_SCHEME : Agg scheme from PXF IPC msg may be corrupted:
scheme expected: [dec] scheme in ipc msg: [dec]Explanation The expected results of the aggregation scheme output are different from the actual value of the aggregation scheme field that was returned in the IPC records.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PXF_FLOW-4-INVLDAGG : Invalid agg scheme.
Explanation The aggregation scheme is out of range or has not yet been configured.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_FLOW-4-INVLDEXP : Invalid export version [dec] (control [hex])
Explanation The export version field of the PXF record might have become corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%PXF_FLOW-4-NPKT_NULL : The number of packets in received flow record is zero
and reset to 1.Explanation The received record has become corrupted. The value is set to a nonzero value to avoid an exception in flow statistics code.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PXF_FLOW-4-NULL_PKTS : The number of packets/bytes is zero.
Explanation The number of packets or the number of bytes is zero in the export record. This condition indicates that the record has become corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%PXF_FLOW-4-PREFIX_UNSUPPORTED : Prefix aggregation is not supported on PXF.
Explanation The prefix aggregation scheme is currently not supported on PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_FLOW-4-SRING_INDX_BAD : Show ring index ([dec]) is out of range.
Explanation The size of the ring index is out of the configured range. The value should be between 0 and the maximum value of the flow ring size.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.
PXF_GRE Messages
The following are Parallel eXpress Forwarding (PXF) GRE tunnel-related messages.
Error Message%PXF_GRE-4-INVLDCFG_SEQUENCE : PXF will enable the [chars] config after access-lists are configured.
Explanation The configuration will have no effect in the PXF packet classification while access lists are being configured. The requested configuration operation will take effect in PXF as soon as the first access list has been configured.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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.
PXF_NAT Messages
The following are Parallel eXpress Forwarding (PXF) Network Address Translation (NAT)-related messages.
Error Message%PXF_NAT-3-MAIN_TABLES_ALLOC_ERR : PXF NAT: insufficient memory for main tables
Explanation There is not enough memory to add the PXF NAT tables. PXF-switched traffic that requires Network Address Translation will fail.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PXF_NAT-3-PXF_MEM_ERR_CLR_NAT_STATS : PXF MEM ERROR when clearing NAT statistics entry in PXF (Addr=[hex])
Explanation An error occurred while the system was writing to PXF memory. NAT statistics could not be properly cleared in PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_NAT-3-PXF_MEM_ERR_IN_NATABILITY : PXF MEM ERROR when setting interface as 'ip nat inside' in PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to the PXF memory. The interface could not be set to the "ip nat inside" configuration in PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_NAT-3-PXF_MEM_ERR_NAT_ACTIVE_FLAG : PXF MEM ERROR when downloading NAT active flag to PXF (Addr=[hex])
Explanation An error occurred while the system was writing to PXF memory. The "NAT active" flag could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_NAT-3-PXF_MEM_ERR_NAT_ENTRY : PXF MEM ERROR when downloading NAT entry to PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. A NAT entry could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_NAT-3-PXF_MEM_ERR_NAT_HASH : PXF MEM ERROR when downloading NAT hash entry to PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. A NAT hash entry could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_NAT-3-PXF_MEM_ERR_NAT_OUTCOME : PXF MEM ERROR when downloading NAT ACL entry to PXF (Addr=[hex])
Explanation An error occurred while the system was writing to PXF memory. A NAT ACL entry could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_NAT-3-PXF_MEM_ERR_NAT_STATS : PXF MEM ERROR when reading NAT statistics entry from PXF (Addr=[hex])
Explanation An error occurred while the system was reading from the PXF memory. A NAT statistics entry could not be properly read from PXF, and a value of zero has been applied.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PXF_NAT-3-PXF_MEM_ERR_NAT_TIMEOUT : PXF MEM ERROR when downloading NAT timeout value to PXF (Addr=[hex])
Explanation An error occurred while the system was writing to PXF memory. A NAT timeout value could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_NAT-3-PXF_MEM_ERR_NAT_TIMER : PXF MEM ERROR when downloading NAT timer entry to PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. A NAT timer entry could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_NAT-3-ST_FIB_ALLOC_ERR : PXF NAT: insufficient memory for static translation, addresses: [IP_address]/[IP_address] => [IP_address]/[IP_address]
Explanation Insufficient memory is available to allocate a PXF NAT static entry. PXF-switched traffic for this entry will fail.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.
PXF_QOS Messages
The following are Parallel eXpress Forwarding (PXF) Quality of Service (QoS)-related messages.
Error Message%PXF_QOS-3-LINK_BANDWIDTH : VTMS will not work correctly. Use hierarchical policy-map for this interface.
Explanation This interface does not have a configured link bandwidth. A link bandwidth is required for VTMS to operate correctly.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PXF_QOS-3-PXF_MEM_ERR_ATTACH_POLICY : PXF MEM ERROR when attaching service policy in PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. A service policy map could not be properly attached to an interface in PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_QOS-3-PXF_MEM_ERR_CBWFQ_DETACH : PXF MEM ERROR when detaching CBWFQ from an interface in PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. CBWFQ could not be properly detached from an interface in PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_QOS-3-PXF_MEM_ERR_CBWFQ_PARAM : PXF MEM ERROR when downloading CBWFQ parameters to PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. CBWFQ parameters could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_QOS-3-PXF_MEM_ERR_CBWFQ_SETUP : PXF MEM ERROR when setting CBWFQ up in an interface in PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. CBWFQ could not be properly set up for an interface in PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_QOS-3-PXF_MEM_ERR_CLASS_ENTRY : PXF MEM ERROR when downloading QoS classificaton entry to PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. A QoS classification entry could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_QOS-3-PXF_MEM_ERR_CLR_WRED_CNT : PXF MEM ERROR when clearing a WRED counter in PXF (Addr=[hex])
Explanation An error occurred while the system was writing to PXF memory. A PXF WRED counter could not be properly cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PXF_QOS-3-PXF_MEM_ERR_DETACH_POLICY : PXF MEM ERROR when detaching service policy in PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. A service policy map could not be properly detached from an interface in PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_QOS-3-PXF_MEM_ERR_POL_PARAM : PXF MEM ERROR when downloading policing parameters to PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. Policing parameters could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_QOS-3-PXF_MEM_ERR_PRI_PARAM : PXF MEM ERROR when downloading priority parameters to PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. Parameters for the priority command parameters could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_QOS-3-PXF_MEM_ERR_SET_PARAM : PXF MEM ERROR when downloading marking parameters to PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. Parameters for the set command parameters could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_QOS-3-PXF_MEM_ERR_WRED_CNT : PXF MEM ERROR when reading a WRED counter from PXF (Addr=[hex])
Explanation An error occurred while the system was reading from PXF memory. A PXF WRED counter could not be properly read, and a value of 0 has been applied.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PXF_QOS-3-PXF_MEM_ERR_WRED_PARAM : PXF MEM ERROR when downloading WRED parameters to PXF (Addr=[hex])
Explanation An error occurred while the system was reading from or writing to PXF memory. WRED parameters could not be properly downloaded to PXF.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%PXF_QOS-3-TOO_MANY_POSSIBLE_OUTCOMES : Too many possible turbo acl outcomes: [dec] (max policies: [dec]).
Explanation This message provides information involving the QoS PXF classification engine based on Turbo ACL. Insufficient system memory is available to hold all possible outcomes of the Turbo ACL compilation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PXF_QOS-3-TOO_MANY_POSSIBLE_OUTCOMES_FOR_POLICIES : Too many possible turbo acl outcomes ([dec]) for current number ofconfigured policy-maps ([dec]).
Explanation This message provides information involving the QoS PXF classification engine based on Turbo ACL. Because of the current number of policy maps, there is not enough memory to hold all possible outcomes of the Turbo ACL compilation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PXF_QOS-3-TOO_MANY_POSSIBLE_POLICIES_FOR_OUTCOMES : Too many configured policy-maps ([dec]) for current number ofTurboACL classification outcomes ([dec]).
Explanation This message provides information involving the QoS PXF classification engine based on Turbo ACL. Because of the current number of possible outcomes of the Turbo ACL compilation, there is not enough memory to hold new policy maps.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PXF_QOS-3-UNKNOWN_QOS_ACTION : Unknown QoS action type: [hex].
Explanation A QoS feature that is unrecognized by PXF has been configured using Modular QoS CLI. The feature will work, but excessive punting of packets may occur if the feature is on an output interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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.
PXF_VRFS Messages
The following are Parallel eXpress Forwarding (PXF) Parallel eXpress Forwarding (PXF) VRF selection-specific messages.
Error Message%PXF_VRFS-3-WS_VRFS_EVENT : [chars]
Explanation This message provides information on generic PXF VRFS errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.
QM Messages
The following are QoS manager messages.
Error Message%QM-2-ACL_FAILURE : Interface [chars] traffic will not comply with ACLs in [chars] direction(s)
Explanation ACLs will not be applied to traffic for this interface due to TCAM resource contention.
Recommended Action The configured ACLs are too large to all fit in the hardware TCAM. Try to share the same ACLs across multiple interfaces to reduce TCAM resource contention.
Error Message%QM-2-AGGREG_FAILURE : Interface [chars] aggregate QoS will not comply with policymap in [chars] direction(s)
Explanation QoS will not be applied to traffic for this interface due to aggregate policer resource contention.
Recommended Action There are too many configured aggregate policers to fit in the hardware Aggregate RAM. Try to share the same aggregate policer(s) across multiple classes and/or interfaces to reduce policer resource contention. Use named QoS aggregates as a mechanism for sharing policers.
Error Message%QM-4-AGGREG_PLC_IGNORED : 'police' command ignored in presence of 'police aggregate [chars]'
Explanation If both 'police' and 'police aggregate' are specified as policy actions for the same class, 'police' is ignored as long as aggregate has been defined via 'mls qos aggregate'.
Recommended Action Do not specify both 'police' and 'police aggregate' in the same class.
Error Message%QM-2-BAD_MESSAGE : Error in internal messaging - bad result [dec]
Explanation A software error may have affected programming ACLs into the TCAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%QM-2-BAD_TLV : Error in internal messaging - bad tlv [dec]
Explanation A Software error may have affected programming ACLs into the TCAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%QM-2-DSCP_NE : Different aggregate and microflow DSCP in class [chars][policy [chars]]
Explanation Conform actions in 'police' and 'police flow' commands must be the same for the same class in a service-policy applied to MLS interfaces.
Recommended Action Change the conform-action in 'police' or 'police flow' command to make both actions the same, or remove one of two commands.
Error Message%QM-3-ERROR : [chars] [chars]:[dec]
Explanation This message can take many forms. It provides information about a software error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QM-3-ERROR_STAT : [chars] stat:[dec] in [chars]:[dec]
Explanation This message can take many forms. It provides information about a software error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%QM-4-IDB_MODE_CHANGE_SERV_POLICY : Interface [chars] service-policy is not preserved on transition to/from switchport
Explanation The service-policy applied to the interface before transition includes features that cannot be applied to the interface after the transition. Since a service-policy is applied atomically, none of the features in its policy-map are applied after the transition.
Recommended Action After the transition, install a different service-policy on the interface, which includes only applicable features.
Error Message%QM-2-MICROFLOW_FAILURE : Interface [chars] microflow QoS will not comply with policymap in [chars] direction(s)
Explanation QoS will not be applied to traffic for this interface due to microflow policer resource contention.
Recommended Action There are too many configured microflow policers to fit in the hardware Threshold RAM. Try to specify the same microlow policing parameters (rate+burst) across multiple classes/interfaces to reduce the policer resource contention.
Error Message%QM-2-NO_AGGREG_PLC : Hardware aggregate policer resources exceeded
Explanation The hardware doesn't have the capacity to handle the aggregate policers required by the configuration.
Recommended Action Reduce the total number of aggregate policers required by all service-policies
installed in the device. For example, use shared aggregate policers, as defined by the mls qos aggregate-policer command, instead of the default per-interface policersError Message%QM-2-NO_AGGREG_PLC_IF : Out of hardware aggregate policers (policy [chars], class [chars], interface [chars]
Explanation The hardware does not have the capacity to handle the aggregate policers required by the service-policy class for the indicated interface.
Recommended Action Reduce the total number of aggregate policers required by all service-policies
installed in the device. For example, use shared aggregate policers, as defined by the mls qos aggregate-policer command, instead of default per-interface policersError Message%QM-2-NO_FLOW_PLC : Hardware microflow policer resources exceeded
Explanation The hardware doesn't have the capacity to handle the microflow policers required by the policy-map.
Recommended Action Adjust microflow policing rate or burst parameters so that the total number of different rate/burst combinations in the device is reduced.
Error Message%QM-2-SEQUENCE : Error in internal messaging - lost message (i/f [chars], dir [chars], type [dec])
Explanation A software error may have affected programming ACLs into the TCAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%QM-2-TCAM_BAD_LOU : Bad TCAM LOU operation in ACL
Explanation A software error has caused failure in programming ACLs into the TCAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%QM-4-TCAM_CAPMAP : Interface [chars] hardware TCAM LOU usage capability exceeded
Explanation The hardware TCAM doesn't have the capacity to handle the number of logical operations used with the configured ACLs on this specific interface.
Recommended Action The hardware TCAM can handle only 9 logical operations per interface and up to 64 logical operations in total. Reduce the use of logical operations in the ACLs.
Error Message%QM-4-TCAM_ENTRY : Hardware TCAM entry capacity exceeded
Explanation The hardware TCAM doesn't have the capacity to handle all of the configured ACLs.
Recommended Action The configured ACLs are too large to all fit in the hardware TCAM. Try to share the same ACLs across multiple interfaces to reduce TCAM resource contention.
Error Message%QM-2-TCAM_ERROR : TCAM programming error [dec]
Explanation A software error has caused a failure in programming ACLs into the TCAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%QM-4-TCAM_LABEL : Hardware TCAM label capacity exceeded
Explanation The hardware TCAM doesn't have the capacity to handle the number of interfaces that are configured with ACLs.
Recommended Action The hardware TCAM can handle only 500 interfaces configured with ACLs. Deconfigure ACLs from some of the interfaces.
Error Message%QM-4-TCAM_LOU : Hardware TCAM LOU capacity exceeded
Explanation The hardware TCAM doesn't have the capacity to handle the number of logical operations used with the configured ACLs.
Recommended Action The hardware TCAM can handle only 9 logical operations per interface and up to 64 logical operations in total. Reduce the use of logical operations in the ACLs.
Error Message%QM-2-TCAM_MEMORY : NMP processor memory low
Explanation Inadequate memory caused failure in programming ACLs into the TCAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
RADIUS Messages
The following are RADIUS messages.
Error Message%RADIUS-3-CANNOT_OPEN_SOCKET : Cannot open UDP socket for service [chars]
Explanation The router is unable to open a socket for UDP communications by the indicated service
Recommended Action Check your configuration to make sure that no other services are using the same port.
Error Message%RADIUS-4-NOPUBLICSERV : Warning: No servers werefound in the public server list.
Explanation The specified server is not on the global public servers list. This condition indicates an internal consistency error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%RADIUS-3-UNKNOWNAPI : Unknown API type [dec]
Explanation RADIUS code has been invoked using an unknown API type. This condition is the result of a problem in the RADIUS subsystem.
Recommended Action Collect the traceback information. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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.
RADSRV Messages
The following are embedded RADIUS server messages.
Error Message%RADSRV-4-BLOCKED : Client [chars] blocked due to repeated failed authentications
Explanation A user has failed authentication for the maximum configured number of times. The account has been disabled. The account will be unblocked either when the configured amount of time elapses or when it is manually unblocked by user-entered CLI. If this condition continues to occur, it may be an indication of a break-in attempt.
Recommended Action If the cause of the condition is not known, monitor the system for any other indications of a break-in attempt.
Error Message%RADSRV-4-NAS_KEYMIS : NAS shared key mismatch with [IP_address]
Explanation A request was received from a network authenticator, and the message signature indicates that the shared key text does not match.
Recommended Action Correct the server entry for the NAS to obtain the correct key.
Error Message%RADSRV-4-NAS_UNKNOWN : Unknown authenticator: [IP_address]
Explanation A request was received for a network authenticator whose IP address was not in the server database.
Recommended Action Add the IP address and a shared secret password into the local RADIUS server database.
RE Messages
The following are RE subsystem messages.
Error Message%RE-4-COMPILE_FAILED : Compile failed on pattern number [dec] - states [dec] - [chars]
Explanation Memory cannot be allocated for the specified RE subsystem.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
RECONCILIATION_HA Messages
The following are reconciliation high availability messages.
Error Message%RECONCILIATION_HA-3-NO_RECON_PROCESS : Failed to create a Reconciliation process
Explanation An error occured during the creation of the reconciliation process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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.
RED Messages
The following are redundancy-related messages.
Error Message%RED-3-CHKPTADDCLIENT : Check Point Client [dec] Add Failed - [dec]
Explanation A checkpoint client message could not be added.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%RED-3-CHKPTALLOC : Check Point Message Allocation Failed - [dec]
Explanation Checkpoint buffer allocation has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RED-3-CHKPTINVALIDDATA : Check Point Client has invalid data
Explanation A checkpoint message contains invalid 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. 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%RED-3-CHKPTMSGSIZE : Check Point Message Size is Zero!
Explanation The checkpoint message size is zero.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%RED-3-CHKPTSENDFAIL : Check Point Message Send - Unsuccessful delivery
Explanation An error involving checkpoint message sending occurred. The message could not be delivered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%RED-3-CHKPTSENDMSG : Check Point Message Send Failed - [dec]
Explanation A checkpoint message could not be sent.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%RED-3-DATADECODE : Decode Data Descriptor for data type Failed
Explanation An attempt to decode the data descriptor has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RED-3-DATAENCODE : Encode Data Descriptor for data type [chars] Failed
Explanation An attempt to encode the data descriptor has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RED-5-REDCHANGE : EHSA Register changed Prev - [int]h, Current - [int]h
Explanation A peer Route Processor has sent a change via the EHSA register.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.
RED_MODE Messages
The following are high availability redundancy mode messages.
Error Message%RED_MODE-4-NO_MODE_IN_CLI : Redundancy mode not defined in configuration. Please add to configuration
Explanation The redundancy mode is not defined in the configuration. The redundancy mode is usually defined at the top of the configuration. Until the redundancy mode is read, or the end of the configuration is encountered, the system does not allow the peer RSC to continue to boot. If the system waits until the end of the configuration and then discovers that the default redundancy mode should be used, then system booting times are extended by the time taken for the RSC to read its configuration.
Recommended Action Explicitly write the configuration to NVRAM so that the redundancy mode is discovered at an early stage.
Error Message%RED_MODE-3-NO_REGISTER : Could not register plugin for redundancy mode [chars]
Explanation At system initialization, the plugin that describes the capabilities of the specified redundancy mode could not be registered with the redundancy mode client. This redundancy mode might not be available as an option from the parser.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.
RED_REMOTE Messages
The following are redundancy-remote messages.
Error Message%RED_REMOTE-3-BAD_REMOTE_IPC_PORT : Unable to open remote IPC port [chars], received error '[chars]'.
Explanation The system failed to open the specified remote IPC port for inter-RP communications. Communications with the remote RP cannot operate for this particular feature until the port can be created.
Recommended Action Ensure that the peer RSC is up and running. Ensure that the RSC itself is operational.
Error Message%RED_REMOTE-3-IPC_MSG_ERROR : IPC messsage received by port [chars] with error '[chars]'.
Explanation An IPC message received by the message handler for the specified port was in error. Communications with the remote RP cannot operate properly for this particular feature until the message handler has received successful IPC messages.
Recommended Action Ensure that the peer RSC is up and running. Ensure that the RSC itself is operational.
Error Message%RED_REMOTE-3-IPC_PORT_CREATE_ERROR : Named IPC port [chars] could not be created, received error '[chars]'.
Explanation The system failed to create the specified IPC port for use in inter-RP communications. Communications with the remote RP cannot operate for this particular feature until the port can be opened.
Recommended Action Ensure that the peer RSC is up and running. Ensure that the RSC itself is operational.
Error Message%RED_REMOTE-3-IPC_PORT_REG_ERROR : Named IPC port [chars] could not be registered after delay, received error '[chars]'.
Explanation The system has failed to register the specified IPC port for inter-RP communications. Communications with the remote RP cannot operate for this particular feature until the port can
be registered.Recommended Action Ensure that the peer RSC is up and running. Ensure that the RSC itself is operational.
REDUNDANCY Messages
The following are redundancy related messages.
Error Message%REDUNDANCY-3-CONFIG_SYNC : [chars]
Explanation A redundancy configuration synchronization error has occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy down the system's configuration along with any other relevant information. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%REDUNDANCY-3-FSM : [chars]
Explanation A redundancy FSM error has occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy down the system's configuration along with any other relevant information. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%REDUNDANCY-3-GENERAL : [chars]
Explanation A redundancy error has occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy down the system's configuration along with any other relevant information. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%REDUNDANCY-3-IPC : [chars] [chars]
Explanation An IPC error has occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy down the system's configuration along with any other relevant information. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%REDUNDANCY-4-PEER_DID_NOT_RESPOND : Resetting peer [chars] because it did not respond to verification of HA role.
Explanation The platform uses the HA hardware lines to perform HA role negotiation during system boot. Whichever controller card becomes the standby verifies this role via the MBus with the active card. If the active card does not respond, it is considered to be hung and is reset, or is running an old version of software.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%REDUNDANCY-3-PEER_MONITOR : [chars]
Explanation A redundancy peer monitor error has occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy down the system's configuration along with any other relevant information. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%REDUNDANCY-5-PEER_MONITOR_EVENT : [chars] ([chars][chars]([dec]))\n
Explanation A redundancy peer monitor event has occurred and has been reported. The report should help determine the reason for the switchover.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Copy down the system configuration along with any other relevant information. Research and attempt to resolve the 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%REDUNDANCY-3-REDUNDANCY_ALARMS : [chars]
Explanation A redundancy alarm assertions error has occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy down the system's configuration along with any other relevant information. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%REDUNDANCY-4-RELOADING_STANDBY : Reloading the Standby [chars]
Explanation The active unit has sent a reload IPC request to the standby unit. If the reload request is not successful, the standby peer is power-cycled.
Recommended Action Copy down the system's configuration along with any other relevant information. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%REDUNDANCY-6-STANDBY_HAS_RELOADED : The Standby [chars] has reloaded; reason: [chars]
Explanation The standby peer has reloaded to correct a configuration mismatch between the active and the standby units. The standby unit detects that the configuration for a line card is missing. This condition usually occurs when the standby unit is reloaded before the new card is inserted.
Recommended Action No action is required.
Error Message%REDUNDANCY-3-STANDBY_LOST : Standby processor fault ([chars])
Explanation The standby processor is no longer available.
Recommended Action Copy down the system's configuration along with any other relevant information. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%REDUNDANCY-3-SWITCHOVER : RP switchover ([chars])
Explanation A redundancy switchover has occurred.
Recommended Action Copy down the system's configuration along with any other relevant information. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%REDUNDANCY-6-SWITCHOVERTIME : Time taken to switchover = [dec] milliseconds
Explanation This message indicates the length of time that the standby peer needed to become active after the failure of the active unit.
Recommended Action No action is required.
RESOURCE_MGR Messages
The following are Resource Manager messages.
Error Message%RESOURCE_MGR-6-NOTIFY : [chars] to [chars], level: [chars], direction: [chars], type: [chars], limit: [int], usage: [int]
Explanation A notification has been sent out by the Resource Owner because of a threshold violation. Details are in the message
Recommended Action This is an informational message only. This message appears because a threshold has been violated. Enter a show running-config command and look for the configuration under the mode 'resource manager' check the thresholds that have been set. This is just a notification that the threshold has been violated; nothing to stop the resource exhaustion is being done here.
RF Messages
The following are Redundancy facility messages.
Error Message%RF-3-CAPENTRY_REG : RF Cap Entry ([dec]) for Entity ([dec]) Registration failed
Explanation An attempt to register an ISSU capabilities entry for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries 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%RF-3-CAPGROUP_REG : RF Cap Group ([dec]) for Entity ([dec]) Registration failed
Explanation An attempt to register an ISSU capabilities group for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability groups 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%RF-3-CAP_REG : RF cap reg failed: reason [dec]
Explanation An attempt to register an ISSU capability for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability 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%RF-3-CAPTYPE_REG : RF Cap Type for Entity ([dec]) Registration failed
Explanation An attempt to register an ISSU capabilities type for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability types 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%RF-3-CLIENT_REG : RF Client ([dec]) Registration failed
Explanation An attempt to register an ISSU client for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu clients 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%RF-3-ENTITY_REG : RF Entity ([dec]) Registration failed
Explanation An attempt to register an ISSU entity for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu entities 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%RF-3-MSGGROUP_REG : RF Msg Group ([dec]) for Entity ([dec]) Registration failed
Explanation An attempt to register an ISSU message group for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message groups 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%RF-3-MSG_REG : RF msg reg failed: reason [dec]
Explanation An attempt to register an ISSU message for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message 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%RF-3-MSGTYPE_REG : RF Msg Type for Entity ([dec]) Registration failed
Explanation An attempt to register an ISSU message type for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu message types 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%RF-3-SES_REG : RF session reg failed: reason [dec]
Explanation An attempt to register an ISSU session for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions 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%RF-3-SESSION_REG : RF session for Entity ([dec]) Registration failed
Explanation An attempt to register an ISSU session for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions 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%RF-3-SESSION_UNREG : RF session ([dec]) Un-Registration failed
Explanation An attempt to deregister an ISSU session for the redundancy facility has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu sessions 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.
RF_INTERDEV Messages
The following are Redundancy facility (RF) interdevice messages.
Error Message%RF_INTERDEV-4-INTERDEVINI : Cannot create timer process!
Explanation The delay timer process could not be created while the RF driver was being initialized.
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. 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%RF_INTERDEV-4-PREEMPT_ERR : % RF interdev will not work with HSRP preemption enabled
Explanation The redundancy facility interdevice code detected an error while HSRP was being configured.
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. 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%RF_INTERDEV-4-RELOAD : % RF induced self-reload
Explanation The redundancy facility interdevice code is reloading this device because of a forced switchover or an error involving the dual active.
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. 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%RF_INTERDEV-4-UNEXPECTED : Unexpected error: [chars]
Explanation An unexpected error occurred while a redundancy facility interdevice operation was being performed.
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. 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.
RIM Messages
The following are Redundant Interface Manager (RIM) messages.
Error Message%RIM-6-CHANGETORED : Changed to Redundant configuration: Active slot: [dec]/[dec]
Explanation The configuration has been changed to a redundant configuration.
Recommended Action No action is required.
Error Message%RIM-3-CUTOVERINT1 : cutover int on nil card [dec] [dec]
Explanation An internal error involving the redundant interface manager has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RIM-3-CUTOVERINT2 : Received disabled LC management interrupt [hex]
Explanation An internal error involving the redundant interface manager has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RIM-3-GETRPSPAIR : active in illegal state [dec] [dec] [hex] [hex]
Explanation An internal error involving the redundant interface manager has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RIM-3-IDB2RPS : idb2rps failed [dec] [dec] [hex]
Explanation An internal error involving the redundant interface manager has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RIM-3-INTERNALRIM : RIM internal error, [chars] [dec] [dec]
Explanation An internal error involving the redundant interface manager has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RIM-3-PLUGIN2RCS : plugin2rcs failed [dec] [hex]
Explanation An internal error involving the redundant interface manager has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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.
RITE Messages
The following are IP traffic export messages.
Error Message%RITE-5-ACTIVATE : Activated IP traffic export on interface [chars]
Explanation IP traffic export has been enabled on the interface specified in the error message.
Recommended Action No action is required.
Error Message%RITE-5-DEACTIVATE : Deactivated IP traffic export on interface [chars]
Explanation IP traffic export has been disabled on the specified interface.
Recommended Action No action is required.
Error Message%RITE-5-MODIFIED : Changed IP traffic export outbound interface from [chars] to [chars]
Explanation The outbound interface for IP traffic exporting has been changed.
Recommended Action No action is required.
ROUTEMAP Messages
The following are route map messages.
Error Message%ROUTEMAP-4-BADTRACKOBJECTTYPE : can't track this type of object
Explanation Route maps only support "STATE" type track objects. This object is not a "STATE" object.
Recommended Action Reconfigure the track object to make it a "STATE" object.
RPC Messages
The following are Remote Procedure Call messages.
Error Message%RPC-2-APPNOTREG : Remote application '[chars]' not registered
Explanation The remote application has not registered itself with the RPC subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%RPC-4-BADID : Application ID [dec] is invalid
Explanation The application ID used by the RPC subsystem is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%RPC-4-DUPREG : Application '[chars]' is already registered
Explanation The application has already registered itself with the RPC subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%RPC-2-FAILED : Failed to send RPC request [chars]
Explanation A communication error has occurred during an RPC request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%RPC-2-NOMEM : No memory available for [chars]
Explanation The RPC subsystem could not obtain the memory it needed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%RPC-2-NOSUCH : The referenced RPC application ([dec]) does not exist
Explanation A message was received for a non-existent RPC application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%RPC-2-NOTREADY : The referenced RPC application ([dec],[chars]) is not ready
Explanation A message was received for an RPC application that is not ready.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%RPC-4-TOOMANY : Too many RPC applications, '[chars]' not registered
Explanation There are too many applications registered with the RPC subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
RPM Messages
The following are Route Processor Module (RPM) messages.
Error Message%RPM-4-CDINFOSNDFAIL : Sending [chars] info to pxm failed.
Explanation The card information could not be successfully sent to PXM.
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. 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%RPM-4-LVCRECOVER : vcd [int] holds [int] buffers.
Explanation The LVC of the MPLS subinterface is stuck. The system will recover by itself because automatic SAR recovery and automatic LVC recovery features are enabled.
Recommended Action Check to see that the system recovers automatically and that traffic is flowing in both directions through the LVC corresponding to the VCD. Otherwise, clear the Switch1 interface by entering CLI and check to see if the LVC recovers. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%RPM-3-LVCSTUCK : LVC (vcd = [int]) stuck with [int] buffers held.
Explanation The LVC of the MPLS subinterface has become stuck. This condition can affect the outgoing traffic through this LVC.
Recommended Action Enable the automatic SAR recovery and automatic LVC recovery features to recover automatically from the LVC stuck condition. Otherwise, clear the Switch1 interface by entering CLI to manually recover the LVC.
Error Message%RPM-3-MPLSPTR : Error setting MPLS pointers for the interface [chars].
Explanation The congestion pointers for the interface could not be set because two MPLS interfaces have already been configured.
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. 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%RPM-5-SUBIFNOSHUT : Sub-interface Switch1.[dec], changed state to up.
Explanation The switch subinterface has been activated by the CLI that was entered by the user.
Recommended Action No action is required.
Error Message%RPM-5-SUBIFSHUT : Sub-interface Switch1.[dec], changed state to administratively down.
Explanation The switch subinterface has been deactivated by the CLI that was entered by the user.
Recommended Action No action is required.
Error Message%RPM-6-SWIFCLR : Clear interface done on interface Switch1
Explanation A clear interface command has been successfully processed for the Switch1 interface.
Recommended Action No action is required.
RPM_BKCD Messages
The following are RPM Back card messages.
Error Message%RPM_BKCD-3-PXM_UPDATE : Back card line update to PXM failed/timedout: [chars] Error : [dec]
Explanation The back card line update to the PXM has failed or timed out.
Recommended Action Check for any error message in the PXM logs. Also verify whether the dspcd command shows the correct information for this front 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. 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 that 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.
RPM_BULK Messages
The following are RPM-specific bulk file messages.
Error Message%RPM_BULK-3-ADDERR : Cannot add file [chars]. File Index [hex] Error [dec]
Explanation The bulk file entry could not be added to the MIB table.
Recommended Action Check if this error is caused by an invalid value or an incorrect row status that is being used to set the object. 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.
Error Message%RPM_BULK-3-ADDOBJECTERR : Cannot add object. File [hex]. Object [dec]. Error [dec]
Explanation The bulk file object entry could not be added to the MIB table.
Recommended Action Check if this error is caused by an invalid value or an incorrect row status that is being used to set the object. 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.
Error Message%RPM_BULK-3-CREATEABORT : File Index [hex] error state [hex]
Explanation The bulk file could not be created. The error detail is defined in the MIB variable "cbfStatusFileState" in the CISCO-BULK-FILE-MIB.my MIB. If the file state returned by the MIB object "cbfStatusFileState" is between 4 and 9, inclusive, an 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%RPM_BULK-5-CREATEDONE : [chars]. File Index [hex]
Explanation The bulk file transfer has completed.
Recommended Action No action is required.
Error Message%RPM_BULK-5-CREATESTARTED : File Index [hex]
Explanation The bulk file has opened, and the file transfer has started.
Recommended Action No action is required.
Error Message%RPM_BULK-3-DEFSETERR : Cannot set Bulk File definitions. Error [dec]
Explanation An error has occurred while bulk file definitions were being set.
Recommended Action Check to see if this error is due to an invalid value was used to set the object. 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.
Error Message%RPM_BULK-5-GENINFO : [chars]
Explanation This message provides general information regarding the bulk file.
Recommended Action No action is required.
Error Message%RPM_BULK-5-GOACTV : Received GO ACTIVE.
Explanation The RPM bulk process has received a "GO ACTIVE" event.
Recommended Action No action is required.
Error Message%RPM_BULK-5-GOREADY : Process initialization is done. Wait for Events.
Explanation The RPM bulk process is ready to process events.
Recommended Action No action is required.
Error Message%RPM_BULK-5-GOSTBY : Received GO STANDBY
Explanation The RPM bulk process has received a "GO STANDBY" event.
Recommended Action No action is required.
Error Message%RPM_BULK-5-INIT : Initialize process
Explanation The RPM bulk process has entered its initialization phase.
Recommended Action No action is required.
Error Message%RPM_BULK-3-PARTCNFERR : Cannot set partial config. File [hex], Object [hex], size [hex], Error [dec]
Explanation An error has occurred while the partial configuration was being set for the bulk file.
Explanation Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%RPM_BULK-5-POPULATED : Configurations are populated in MIB tables.
Explanation RPM bulk file configurations have been initialized.
Recommended Action No action is required.
Error Message%RPM_BULK-3-STATSETERR : Cannot set Bulk File stats objects. Error [dec]
Explanation An error occurred while bulk file status objects were being set.
Explanation Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%RPM_BULK-3-TRAPBAD : Bad file index. File Index [hex] state [hex] reason [hex]
Explanation The bulk file trap could not be sent because of an invalid file index.
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. 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%RPM_BULK-3-TRAPERR : Cannot generate trap. File Index [hex] state [hex] reason [hex] error [hex]
Explanation The bulk file could not be sent out because of the reason specified in the message text.
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. 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.