-
Cisco IOS Release 12.0S System Message Guide
-
System Messages Overview
-
AAAA through AUDIT messages
-
AUTORP through C10KSDCC messages
-
C10K_TOASTER through CBUS messages
-
CE3 through CPUIF messages
-
CRYPTO through ECC messages
-
EDGE through EE192 messages
-
EELC through ENV_MON messages
-
ESMP through FM messages
-
FR through GLCSPA messages
-
GRP through GRPSPA messages
-
GRP_CHOCX through GT96K_FE messages
-
HA through I82543 messages
-
ICC through IPV6FIB messages
-
IP_VRF through LC_CHOCX messages
-
LCCOREDUMP through LCINFO messages
-
LCLOG through MBUSFLASH messages
-
MCC192 through MPLS_TE_LM messages
-
MPLS_TE_PCALC through PM3386 messages
-
PM622 through PRP2 messages
-
PS through RSP messages
-
RSVP through SW_MGR messages
-
SYS through TCAM_MGR messages
-
TCATM through XCPA messages
-
Glossary of Acronyms
-
Table Of Contents
PS Messages
The following are Power Supply messages.
Error Message%PS-3-MULTFAIL T There is more than one failure with the Power System
Explanation The power system experienced multiple failures. This is a critical condition.
Recommended Action There are multiple failures on the power supply. Read the LEDs on the front of the power supply to determine which failures have occurred.
PSA Messages
The following are PSA messages.
Error Message%PSA-3-L2FWD : [chars]
Explanation L2FWD specific error messages.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.
PSAACL Messages
The following are PSA ACL messages.
Error Message%PSAACL-3-ATM8XOC3 : [chars]
Explanation An internal error involving the 128 iACL has occurred on the 8XOC3 ATM.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PSAACL-3-CBV : [chars] [dec]
Explanation An out of bounds request to set and clear a CBV entry has been received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PSAACL-3-COUNTNUMACLERR : Count_num_acl_lines_for_lincard has had an unexpected error [chars].
Explanation An error has occurred while the system was performing an ACL line count.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. tative, and provide the representative with the information you have gathered.
Error Message%PSAACL-3-DISABLE : Disabling PSA ACLs with active ACLs configured - packets for input ACLs on this card or output ACLs on any other card will not have the ACLs applied on this card.
Explanation PSA ACLs were applying ACLs, and the no access-list hardware psa command was entered. If the card was processing input ACLs, the input ACLs are no longer applied. If the card was processing output ACLs, the output ACLs are no longer applied.
Recommended Action Reenable the PSA ACL by issuing the access-list hardware psa command.
Error Message%PSAACL-3-INCORRECTUCODE : We do not have the correct ACL Ucode loaded here. [chars].
Explanation The incorrect PSA ACL microcode has been loaded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PSAACL-3-INNOTSUPPORTED : Input PSA ACLs are not supported on this card - packets will not be filtered for interface [chars].
Explanation Input PSA ACLs are required to implement ACL on the interface, or packets will not be filtered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PSAACL-0-INVALID : 448 PSA ACLs and MPLS VPN are not supported on this card -- ACL is removed from this card.
Explanation An invalid configuration has been detected.
Recommended Action Perform one of the following actions:
•
Remove the MPLS VPN and rebind the ACL to the interface so that ACL will work.
•
Error Message%PSAACL-3-NOACLUCODE : We do not have any ACL Ucode loaded here. There should be. [chars].
Explanation PSA ACL microcode has not been loaded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PSAACL-3-NOTCONFIG : PSA ACLs are not configured - packets will not be filtered for interface [chars].
Explanation PSA ACLs are required to implement ACL on the interface, or packets will not be filtered.
Recommended Action Configure ACLs using the access-list hardware psa command.
Error Message%PSAACL-3-NOTSUPPORTED : PSA ACLs are not supported on this card - packets will not be filtered for interface [chars].
Explanation The card does not support PSA ACLs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PSAACL-3-NOUCODELOADING : There has not been any selection to load a psa-acl ucode bundle [chars].
Explanation PSA ACL microcode has not been selected to load.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%PSAACL-3-OUTNOTSUPPORTED : Output PSA ACLs are not supported on this card - packets will not be filtered for interface [chars].
Explanation Output PSA ACLs are required to implement ACL on the interface, or packets will not be filtered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PSAACL-3-RANGEFULL : PSA ACL Range array overflow, max size [dec] current [dec].
Explanation This is an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PSAACL-3-REQUESTUCODE : request_acl_ucode_dnld - No ucode bundle selected. [chars].
Explanation PSA ACL microcode has not been requested.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%PSAACL-3-SUBINT : ACLs on sub-interfaces ([chars]) are not supported for this line card
Explanation This is an unsupported feature. ACLs on subinterfaces are ignored.
Recommended Action ACLs must be configured on primary interfaces.
Error Message%PSAACL-3-TAZ : [chars]
Explanation An internal error of 128 iACL on Taz 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%PSAACL-0-UNSUPPORTED : 448 PSA ACLs and MPLS VPN are not supported on this card -- MPLS VPN is removed.
Explanation An invalid configuration has been detected.
Recommended Action Perform one of the following actions:
•
•
PSABYPASS Messages
The following are PSA bypass messages.
Error Message%PSABYPASS-4-ATM8XOC3 : [chars] [dec] [chars] [dec]
Explanation On 8XOC3 ATM Version B cards, each channel is associated with two ports. Enabling a PSA bypass configuration on one port also enables the PSA configuration to be applied to the other port. Similarly, disabling a PSA bypass configuration on one port also disables the PSA configuration on the other port.
Recommended Action This is an informational message only. No action is required.
Error Message%PSABYPASS-4-TAZ : [chars] [dec] [chars] [dec]
Explanation This is a message regarding TAZ-B cards. Each channel is associated with two ports, so enabling PSA bypass on one port also enables PSA bypass on the other port. Similarly, disabling PSA bypass on a port is allowed when PSA bypass is also disabled on the other port.
Recommended Action No action is required.
PXF_DMA Messages
The following are PXF DMA subsystem messages.
Error Message%PXF_DMA-3-FBB_LINE_CARD : [chars]
Explanation A PXF DMA fast back-to-back 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 The 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 The 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 P%PXF_DMA-2-TBB_SYNC_FAILED : TBB sync of the RP failed. No traffic is being sent to the RP!
Explanation The synchronization of the TBB with the RP 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 synchronization of the TBB with the RP 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.
QM Messages
The following are Quality of Service (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 because of TCAM resource contention. The configured ACLs are too large to all fit in the hardware TCAM.
Recommended Action 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 because of aggregate policer resource contention. There are too many configured aggregate policers to fit in the hardware aggregate RAM.
Recommended Action Share the same aggregate policer(s) across multiple classes 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 commands are specified as policy actions for the same class, the police command is ignored as long as the aggregate has been defined by using the mls qos aggregate command.
Recommended Action Do not specify both police and police aggregate commands in the same class.
Error Message%QM-2-BAD_MESSAGE : Error in internal messaging - bad result [dec]
Explanation A software error may have affected the programming of ACLs into the TCAM.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%QM-2-BAD_TLV : Error in internal messaging - bad tlv [dec]
Explanation A software error may have affected the programming of ACLs into the TCAM.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%QM-3-BUFFER_LOOP : Detected looped buffer qelem: [int] queue: [hex]
Explanation The TBM sanity process detected a buffer that is looping. The card datapath will be reset to correct the problem.
Recommended Action The router will self recover from this condition by running error recovery. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs
Error Message%QM-4-BUFFER_SANITY : [chars] : [chars] [dec] [chars] [dec] [chars] [dec]
Explanation The buffer queues are corrupted. Further details on the nature of the error are specified in the text of the message. The system has recovered from this condition.
Recommended Action No action is required.
Error Message%QM-2-DSCP_NE : Different aggregate and microflow DSCP in class [chars][policy [chars]]
Explanation Conform actions in the 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 the police or police flow commands to make both actions the same or remove one of the two commands.
Error Message%QM-3-ERROR : [chars] [chars]:[dec]
Explanation This message provides information about a software error and may take many forms.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%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 the transition includes features that cannot be applied to the interface after the transition. Since a service policy is applied automatically, 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 only includes applicable features.
Error Message%QM-2-LABEL_FAILURE : Exceed the maximum number of QM labels.
Interface [chars] traffic will not comply with rate limiting or
MQC in [chars] direction(s)Explanation The TCAM label usage has reached to the maximum in hardware TCAM. Rate limiting or MQC will not be applied on traffic for this interface due to a TCAM label resource contention.
Recommended Action Try to remove the rate limiting or MQC configuration from the interfaces to free up resources.
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 because of a microflow policer resource contention.
Recommended Action There are too many configured microflow policers to fit in the hardware Threshold RAM. Specify the same microflow policing parameters (rate and burst) across multiple classes or interfaces to reduce the policer resource contention.
Error Message%QM-2-NO_AGGREG_PLC : Hardware aggregate policer resources exceeded
Explanation The hardware does not 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 policers.
Error 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 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 the default per-interface policers.
Error Message%QM-2-NO_FLOW_PLC : Hardware microflow policer resources exceeded
Explanation The hardware does not have the capacity to handle microflow policers required by the policy map.
Recommended Action Adjust the microflow policing rate or burst parameters so that the total number of different rate/burst combinations in the device is reduced.
Error Message%QM-3-PARITY : [chars] Address [hex] Data [hex]
Explanation A hardware error has been detected by the queue manager. The device will be reset. If the problem persists, the card will be reset automatically.
Recommended Action If this message 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%QM-4-RESET : The linecard will be reset due to the QM is stuck for an extended period
Explanation The QM is stuck for an extended period. The line card will be reset.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%QM-2-SEQUENCE : Error in internal messaging - lost message (i/f [chars], dir [chars], type [dec])
Explanation A software error may have affected the programming of ACLs into the TCAM.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%QM-4-STUCK : Port [dec] Queue mask [hex]
Explanation All of the queues for a port have become stuck. This error message is only a warning that the situation has occurred.
Recommended Action The system will recover from this error.
Error Message%QM-4-SW_SWITCH : Interface [chars] routed traffic will be software switched in [chars] direction(s)
Explanation A TCAM resource contention prevents the QoS feature from being applied in the TCAM for this interface. The traffic on this interface will be sent to the software so that the QoS can be applied. The configured ACLs are too large to all fit in the hardware TCAM.
Recommended Action Try to reduce the number of QoS rules on the interfaces to reduce TCAM resource contention.
Error Message%QM-2-TCAM_BAD_LOU : Bad TCAM LOU operation in ACL
Explanation A software error caused programming ACLs into the TCAM to fail.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%QM-4-TCAM_CAPMAP : Interface [chars] hardware TCAM LOU usage capability exceeded
Explanation The hardware TCAM does not have the capacity to handle the number of logical operations used with the configured ACLs on this specific interface. The hardware TCAM can handle only up to nine logical operations per interface and up to 64 logical operations in total.
Recommended Action Reduce the use of logical operations in the ACLs.
Error Message%QM-4-TCAM_ENTRY : Hardware TCAM entry capacity exceeded
Explanation The hardware TCAM does not have the capacity to handle all the configured ACLs. The configured ACLs are too large to all fit in the hardware TCAM.
Recommended Action 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 caused programming ACLs into the TCAM to fail.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%QM-4-TCAM_LABEL : Hardware TCAM label capacity exceeded
Explanation The hardware TCAM does not have the capacity to handle the number of interfaces configured with ACLs. The hardware TCAM can handle only 500 interfaces configured with ACLs.
Recommended Action Remove ACLs from some of the interfaces.
Error Message%QM-4-TCAM_LOU : Hardware TCAM LOU capacity exceeded
Explanation The hardware TCAM does not have the capacity to handle the number of logical operations used with the configured ACLs. The hardware TCAM can handle only up to 9 logical operations per interface and up to 64 logical operations in total.
Recommended Action Reduce the use of logical operations in the ACLs.
Error Message%QM-2-TCAM_MEMORY : LC TCAM memory low intf:[chars] [chars]
Explanation Inadequate memory caused programming ACLs into the TCAM to fail.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.ge text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%QM-4-VLOU_EXCEEDED : Exceeds the maximum logical operation, [chars] traffic of interface [chars] will be forwared by software
Explanation The hardware TCAM can process a maximum of 64 logical operations. To prevent the possibility that the hardware TCAM does not have the capacity to process the number of logical operations used with the configured rate-limit rule based on the ACLs, the software has bridged the traffic to the CPU.
Recommended Action If possible, put the entries using a TCP flag before the other entries in the ACL, or accept having the traffic forwarded to the CPU.
Error Message%QM-3-VLOU_EXCEEDED_MQC : Policy-map [chars] on interface [chars] exceeds maximum logical operations. ACL [chars] will not be matched
Explanation The hardware TCAM can process a maximum of 64 logical operations. The hardware TCAM does not have the capacity to handle the number of logical operations used with the configured policy-map rule-based ACLs. The indicated match statement will not be processed and will be ignored.
Recommended Action If possible, put the entries using the TCP flags before the others in the match ACL.
Error Message%QM-4-WREDCONF : WARNING: [chars] WRED's configuration exceeds the linecard's physical buffer memory!
Explanation WRED is misconfigured.
Recommended Action Reconfigure WRED.
QOS Messages
The following are Quality of Service (QoS) messages.
Error Message%QOS-3-CFGERR : interface [chars]: configuration failed\n
Explanation Enough memory is not available to configure the feature. It is not possible to configure issued commands (features) unless required memory is released by some other means.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%QOS-3-HQFPOOLERR : interface [chars]: failed to allocate hqf particle\n
Explanation The HQF particle pool is empty. It cannot process a router-generated packet.
Recommended Action Enter the show buffer and show policy interface commands. Copy the resulting messages exactly as they appear on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the information you have gathered. Attach the information to your case in nonzipped, plain-text (.txt) format.
Error Message%QOS-4-INVALIDBW : interface [chars]: Not enough bandwidth to configure service-policy
Explanation The interface bandwidth specified is less than the total bandwidth that is required for the QoS policy on this interface.
Recommended Action Reconfigure the service policy for the new issued bandwidth on the interface or increase the issued interface bandwidth to the required value.
Error Message%QOS-3-MAIN_SUB_POLICY : FR fragmentation is not supported with interface or sub-interface based policies
Explanation On Cisco 7500 series routers, Frame Relay fragmentation is not supported when service policies are configured on the interface or subinterfaces.
Recommended Action Remove the service policy configuration under the interface or subinterfaces and reissue either the class command from Frame Relay DLCI interface configuration mode or the frame-relay fragment command from map-class configuration mode.
RADIUS Messages
The following are RADIUS messages.
Error Message%RADIUS-3-SECRETDEFINEFAILED : Key definition ignored.
Explanation The user is attempting to store either a corrupted shared secret, or memory allocation failed during secret definition. Any existing shared secret will be preserved.
Recommended Action Configure a proper secret.
RED Messages
The following are redundancy-related messages.
Error Message%RED-3-CHKPTADDCLIENT : Check Point Client [dec] Add Failed - [dec]
Explanation The check point message client 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-CHKPTALLOC : Check Point Message Allocation Failed - [dec]
Explanation Check point 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 check point 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 size of a check point Message 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 A check point message has been sent, but the delivery was unsuccessful.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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 check point message failed to 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 The decode data descriptor 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 The Encode data descriptor 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 RP has sent change by way of 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 Client 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 usually defined at the top of the configuration. Until the redundancy mode is read, or the end of the configuration is encountered, the system will not allow the peer RSC to continue booting. Therefore, if the system has to wait until the end of the configuration to discover that the default redundancy mode should be used, system booting times will be 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 plug-in that describes the capabilities of the redundancy mode specified in the error message could not be registered with the redundancy mode client. The specified redundancy mode may 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.
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 of what was attempted and what went wrong are displayed in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%REDUNDANCY-3-FSM : [chars]
Explanation A redundancy Finite State Machine error has occurred. The details of what was attempted and what went wrong are displayed in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%REDUNDANCY-3-GENERAL : [chars]
Explanation A redundancy error has occurred. The details of what was attempted and what went wrong are displayed in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%REDUNDANCY-3-IPC : [chars] [chars]
Explanation An Interprocess Communication error has occurred. The details of what was attempted and what went wrong are displayed in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%REDUNDANCY-3-MEMORY_DIFF : WARNING, nonsymetrical configuration:
Active has [dec]K Standby has [dec]K\nExplanation The redundant RPs have different memory configurations. The configuration is allowed but discouraged.
Recommended Action No action is required.
Error Message%REDUNDANCY-3-PEER_MONITOR : [chars]
Explanation A redundancy peer monitor error has occurred. The details of what was attempted and what went wrong are displayed in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the information you have gathered.
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 message displayed on the console or in the system log should provide additional details on the reason for the switchover.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Copy 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 of what was attempted and what went wrong are displayed in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%REDUNDANCY-3-STANDBY_LOST : Standby processor fault ([chars])
Explanation The standby processor is no longer available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%REDUNDANCY-3-SWITCHOVER : RP switchover ([chars])
Explanation An RP redundancy switchover has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Copy the system configuration along with any other relevant information. Contact your Cisco technical support representative and provide the representative with the information you have gathered.
REGISTRY Messages
The following are registry messages.
Error Message%REGISTRY-3-STUB_CHK_OVERWRITE : Attempt made to overwrite a set stub function in [chars].
Explanation A single function can be set as a callback function for when a stub with a check registry is invoked. This message indicates that an attempt to set a new callback has failed, because a callback function has already been set.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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 messages.
Error Message%RIM-6-CHANGETORED : Changed to Redundant configuration: Active slot: [dec]/[dec]
Explanation The system has changed to a redundant configuration.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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-CUTOVERINT1 : cutover int on nil card [dec] [dec]
Explanation An internal Redundant Interface Manager 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%RIM-3-CUTOVERINT2 : Received disabled LC management interrupt [hex]
Explanation An internal Redundant Interface Manager 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.