-
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
System Messages
This section lists messages alphabetically by facility and mnemonic.
AAA Messages
The following are authentication, authorization, and accounting messages.
Error Message%AAA-3-ACCT_IOMEM_LOW : AAA ACCT process suspended : low I/O memory
Explanation An AAA accounting process has been suspended because of insufficient I/O memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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%AAA-3-AUTH_LOW_IOMEM : AAA process is suspended due to low I/O memory
Explanation An AAA process has been suspended from processing incoming requests because of insufficient I/O memory.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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%AAA-6-ACCTSESSIDWRAP : Accounting-Session-ID [dec] exceeded max value allowed
Explanation The value in the accounting session ID exceeds the maximum allowed value.
Recommended Action This is an informational message only. No action is required.
Error Message%AAA-3-BADMETHODERROR : Cannot process [chars] method [chars]
Explanation A method list function has encountered a method type that is unknown or that cannot be handled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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%AAA-3-BADSERVERTYPEERROR : Cannot process [chars] server type [chars]
Explanation A method list function encountered a server type that was unknown, or could not be handled. This may be due to a server misconfiguration.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.
Error Message%AAA-3-NULLVRF : Null vrf entry
Explanation A VRF entry with a null value was found while the AAA VRF attributes were being compared.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AAA-5-USER_LOCKED : User [chars] locked out on authentication failure
Explanation The user was locked out because the number of authentication failures exceeded the configured threshold.
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. 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 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 gathered information.
Error Message%AAA-5-USER_RESET : User [chars] failed attempts reset by [chars]
Explanation The number of failed user authentication attempts has been reset to zero.
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. 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%AAA-5-USER_UNLOCKED : User [chars] unlocked by [chars]
Explanation The user has been unlocked by the system administrator. The user is enabled to log in to the system.
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 at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. 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.
AAAA Messages
The following are TACACS+ authentication, authorization, and accounting security messages.
Error Message%AAAA-3-ACCTATTR : last accounting attribute:
Explanation The data buffer overflowed while building the accounting packet. The accounting attribute that was being written to the buffer when the buffer overflow occurred, was logged.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the Output Interpreter and other 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. Collect the logs by using the debug aaa api, debug aaa attr, and debug aaa accounting commands.
Error Message%AAAA-3-ACCTDUMP : dump of accounting data:
Explanation The data buffer overflowed while building the accounting packet. The accounting attribute that was being written to the buffer when the buffer overflow occurred, was logged.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the Output Interpreter and other 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. Collect the logs by using the debug aaa api, debug aaa attr, and debug aaa accounting commands.
Error Message%AAAA-3-BADAUTHENSTR : Bad authentication data: [chars]
Explanation The data buffer overflowed while building the authentication packet when the total length of the attributes exceeded the buffer 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 Output Interpreter and other 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. Collect the logs by using the debug aaa api, debug aaa attr, and debug aaa accounting commands.
Error Message%AAAA-3-BADMETHNAME : Bad [chars] method-list name "[chars]" rejected
Explanation A method-list name should not be the same as a method name. Please choose a different name for the method list.
Recommended Action Pick a different method-list name, that is not also a method-name.
Error Message%AAAA-4-BADSGTYPE : Server-group [chars] is not of type [chars].
Explanation The specified server group name does not match the specified type.
Recommended Action Verify that the group exists and that it is of the same type.
Error Message%AAAA-4-SERVNOGRP : Warning: Server [IP_address]:[dec],[dec] is not part of server group [chars].
Explanation The specified server does not belong to the specified server group.
Recommended Action Check that the specified server belongs to the server group.
AAL5 Messages
The following are ATM Adaptation Layer 5 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.
AESOP_AIM Messages
The following are service engine AIM messages.
Error Message%AESOP_AIM-1-INITFAIL : AIM slot [dec]: PCI device [dec] initialization failed
Explanation The service engine AIM has failed to initialize.
Recommended Action Power off the system, reseat the interface card, and reboot the system. 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.
AHDLC_TRINIAN
The following are PPP in HDLC-like framing device driver messages.
Error Message%AHDLC_TRINIAN-3-BADCHANNEL : chid [dec]
Explanation The AHDLC driver has detected that the channel number is greater than what is supported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AHDLC_TRINIAN-3-BADDEV : packet received for unknown device
Explanation The channel encapsulation 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%AHDLC_TRINIAN-3-BADDEVCH : packet received for unknown device channel [dec]
Explanation The channel encapsulation 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%AHDLC_TRINIAN-3-BADHW : Bad Hardware
Explanation The AHDLC hardware did not initialize.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AHDLC_TRINIAN-1-DISCOVER : Found [dec] interfaces on bay [dec], shutting down bay
Explanation The number of interfaces found was not the number that was expected. This condition possibly indicates a hardware failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AHDLC_TRINIAN-3-DOWNLOAD : download fail at [hex], expect=[hex], readback=[hex]
Explanation A software or hardware error has occurred. The AHDLC driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-NOCH : packet received for unknown resource manager channel [dec]
Explanation The channel encapsulation 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%AHDLC_TRINIAN-3-NOMEMORY : No Memory for channel allocation
Explanation The AHDLC driver could not allocate memory for the channel.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AHDLC_TRINIAN-3-NOTAHDLC : Device reported [hex]
Explanation The AHDLC hardware has failed. A non-AHDLC device pointed at the software for the AHDLC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AHDLC_TRINIAN-3-NOTAHDLCHW : Bad HWIDB returned.
Explanation The AHDLC driver detected that the CDMA software invoked the AHDLC driver with an incorrect engine ID.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AHDLC_TRINIAN-3-PAKOVERFLOW : packet buffer, pak=[hex], size=[dec]
Explanation A software or hardware error has occurred. The AHDLC driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-3-PAKTOOBIG : packet buffer, pak=[hex], size=[dec]
Explanation A software or hardware error has occurred. The AHDLC driver received a packet from an application that was larger than the expected 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.
Error Message%AHDLC_TRINIAN-3-SEQERR : rsc_mgr_chid [dec], receive=[dec], expect=[dec]
Explanation A software or hardware error has occurred. The AHDLC driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%AHDLC_TRINIAN-6-SHUTDOWN : [chars] shutting down
Explanation The specified AHDLC driver is shutting down. The driver may have been physically removed.
Recommended Action No action is required.
Error Message%AHDLC_TRINIAN-3-TXOVERRUN : dev [dec] chid [dec], particle_count=[dec]
Explanation The AHDLC driver detected that the outstanding Tx buffer has exceeded its maximum allowance.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AHDLC_TRINIAN-3-TXQFULL : pak=[hex], particle_count=[dec], wp=[dec], rp=[dec]
Explanation A software or hardware error has occurred. The AHDLC driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
ALARM Messages
The following are Telco chassis alarm-related messages.
Error Message%ALARM-3-CLEAR : [chars] [chars] [chars] [chars] [chars]
Explanation An alarm has been cleared.
Recommended Action No action is required.
Error Message%ALARM-3-NOCLASS : Unknown Alarm Severity Class
Explanation The alarm status tables contain an alarm entry with an unknown alarm severity class.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%ALARM-3-NOMEM : OUT of Memory: [chars]
Explanation A memory allocation failure has occurred.
Recommended Action Reboot the system. 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 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.
Error Message%ALARM-3-NOMESSAGES : No alarm messages left
Explanation No more alarm messages are available in the message cache.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%ALARM-3-NORESOURCES : Failed to [chars] [chars] alarms for [chars].
Explanation System resources were insufficient to process the alarm request.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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%ALARM-3-NOSOURCE : Attempt to set alarm status for undefined source
Explanation The alarm subsystem has no record of this alarm source. The source either has not been registered or has been deleted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%ALARM-3-NOTYPE : Attempt to change alarm status for undefined type
Explanation The alarm subsystem has no record of this type of alarm. The type either has not been registered or has been deleted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%ALARM-3-TOOMANYSOURCES : Max number of alarm sources exceeded
Explanation Too many alarm sources have been added by the system.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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.
AMDP2_FE Messages
The following are AMDP2 Ethernet and Fast Ethernet messages.
Error Message%AMDP2_FE-4-BABBLE : AMDP2/FE [chars], Babble error
Explanation The transmitter has been on the channel longer than the time it took to transmit the largest frame.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-5-COLL : AMDP2/FE [chars], Excessive collisions, TDR=[dec], TRC=[dec].
Explanation Ethernet or Fast Ethernet is detecting multiple collisions. This situation may occur under heavy loads.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-5-CONFIGNOT : The Internal Ethernet Interface is not configurable
Explanation The internal Ethernet interface is for system use only and is not configurable.
Recommended Action No action is required.
Error Message%AMDP2_FE-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay
Explanation The software could not identify the interface card.
Recommended Action Power down, reseat the interface card, and reboot the system. If the 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%AMDP2_FE-1-INITFAIL : AMDP2/FE [chars], Init failed, CSR[dec]=[hex]
Explanation The software failed to initialize or restart an Ethernet or Fast Ethernet interface.
Recommended Action Clear the interface. If the 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%AMDP2_FE-5-LATECOLL : AMDP2/FE [chars], Late collision
Explanation Late collisions occurred on the Ethernet or Fast Ethernet interface.
Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. If the interface is regular Ethernet, the system should recover. No action is required.
Error Message%AMDP2_FE-5-LOSTCARR : AMDP2/FE [chars], Lost carrier. Transceiver problem?
Explanation The cable or transceiver is not connected.
Recommended Action Connect the cable or transceiver.
Error Message%AMDP2_FE-1-MEMERR : AMDP2/FE [chars], Memory error, CSR[dec]=[hex]
Explanation The interface could not access system resources for a long period of time. This condition may occur under very heavy loads.
Recommended Action The system should recover. No action is required. If the 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%AMDP2_FE-2-NOISL : Interface [chars] does not support ISL
Explanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the configuration of the interface.
Error Message%AMDP2_FE-1-NOMII : AMDFE [chars],MII Interface transceiver not connected
Explanation The MII transceiver was disconnected while the MII port was selected.
Recommended Action Connect the transceiver and enter the shutdown and no shutdown commands in global configuration mode for the interface.
Error Message%AMDP2_FE-3-NOTAMDP2 : Device reported [hex]
Explanation The software could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot the system. If the 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%AMDP2_FE-3-OVERFLO : AMDP2/FE [chars], Receive overflow
Explanation While receiving a frame, the local buffer of the controller chip transmitted insufficient data because data could not be transferred to DRAM quickly enough to keep pace with its input rate. Normally, such a condition is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-3-OWNERR : AMDP2/FE [chars], Buffer ownership error, pak=[hex]
Explanation The software has detected an error in descriptor ownership.
Recommended Action Try a later version of Cisco IOS software. If the 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%AMDP2_FE-3-SPURIDON : AMDP2/FE [chars], Spurious IDON interrupt, CSR[dec]=[hex]
Explanation An illegal condition indicating an "initialization done" event has occurred.
Recommended Action Clear the interface. If the 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%AMDP2_FE-4-SPURIOUS : AMDP2/FE [chars], Spurious interrupt error
Explanation An illegal condition was encountered during system initialization.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-5-SUBIF : Subinterfaces are not supported on FastEthernet
Explanation There is no subinterface support for Fast Ethernet-configured interfaces.
Recommended Action Do not configure subinterfaces on Fast Ethernet-configured interfaces.
Error Message%AMDP2_FE-3-UNDERFLO : AMDP2/FE [chars], Transmit underflow
Explanation While a frame was being transmitted, the local buffer of the controller chip local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a condition is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
AP Messages
The following are authentication proxy (AP) messages.
Error Message%AP-4-AUTH_PROXY_NOMEM : Sufficient memory was not available to [chars]
Explanation Insufficient memory was available to perform the specified operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%AP-6-POSTURE_DOWNLOAD_ACL : Send AAA request to download ([chars]) named access control list
Explanation The router has sent a request to AAA to retrieve the contents of the specified downloadable access control list.
Recommended Action This is an informational message only. No action is required.
Error Message%AP-4-POSTURE_EXCEED_MAX_INIT : Exceeded maximum limit ([dec]) on entires in authentication proxy posture cache in initializing state
Explanation The number of entries in the authentication proxy posture cache that are in the initializing state has exceeded the maximum limit. This condition might indicate a denial-of-service attack.
Recommended Action If a denial-of-service attack is suspected, determine the source of the entries and block the source of the entries. One method of blocking the entries is using an access control list.
Error Message%AP-6-POSTURE_POLICY : [chars] [chars] ([chars]) policy for host ([IP_address])
Explanation The specified policy has been enforced or removed for the specified host. The policy could be either an access control list or a URL to which any intercepted HTTP traffic would be redirected.
Recommended Action This is an informational message only. No action is required.
Error Message%AP-6-POSTURE_START_VALIDATION : IP=[IP_address]| Interface=[chars]
Explanation The router has created an entry for the host in authentication proxy posture cache and has initiated the posture validation process.
Recommended Action This is an informational message only. No action is required.
Error Message%AP-6-POSTURE_STATE_CHANGE : IP=[IP_address]| STATE=[chars]
Explanation A change of posture validation state has occurred for the specified host in the authentication proxy posture validation cache.
Recommended Action This is an informational message only. No action is required.
APPFW Messages
The following are Application Firewall for HTTP subsystem messages.
Error Message%APPFW-3-HTTP_APPFW_CONF_ERROR : Application Firewall configuration error -- [chars]
Explanation An error has occurred during Application Firewall configuration.
Recommended Action There might be a potential security problem. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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.
Error Message%APPFW-4-HTTP_CONT_LENGTH : content-length
Explanation An HTTP message has been detected that violates the content-length Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_CONT_TYPE_MATCH : Sig:[dec] Content type not found - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the content-type-verification Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_CONT_TYPE_SIZE : Sig:[dec] Content size [int] out of range - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the content-type-verification Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_CONT_TYPE_VERIFY : Sig:[dec] Content type does not match the specified type - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the content-type-verification Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_DEOBFUSCATE : Sig:[dec] Deobfuscation signature detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the deobfuscate Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_MATCH_REQ_RESP : Sig:[dec] Content type: [chars] does not match the Accept-Type from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the content-type-verification Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_MAX_HDR_LEN : Sig:[dec] HTTP Header length exceeded. Received [int] byte of header - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the max-hdr-len Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-3-HTTP_MAX_REQ_EXCEED : Maximum of [dec] unanswered HTTP requests exceeded from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the transfer encoding Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_MAX_URI_LEN : Sig:[dec] HTTP URI length exceeded. Received [int] byte of URL - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the max-uri-len Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_PORT_MISUSE_IM : Sig:[dec] HTTP Instant Messenger detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the port misuse Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_PORT_MISUSE_P2P : Sig:[dec] HTTP Peer-to-Peer detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the port misuse Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_PORT_MISUSE_TUNNEL : Sig:[dec] HTTP Tunnel detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the port misuse Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_REQ_METHOD_EXT : Sig:[dec] HTTP Extension method illegal - [chars] '[chars]' from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the request-method Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_REQ_METHOD_RFC : Sig:[dec] HTTP RFC method illegal - [chars] '[chars]' from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the request-method Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-6-HTTP_SESSION_AUDIT_TRAIL : HTTP session initiator [IP_address]:[dec] sends [dec] bytes - responder [IP_address]:[dec] sends [dec] bytes
Explanation An HTTP message has been detected that violates the transfer encoding Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_STRICT_PROTOCOL : Sig:[dec] HTTP protocol violation detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the strict-http Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
Error Message%APPFW-4-HTTP_TRANSFER_ENCODE : Sig:[dec] HTTP Transfer encoding violation detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation An HTTP message has been detected that violates the transfer encoding Application Firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.
APS Messages
The following are APS messages.
Error Message%APS-5-CMDFAIL : Controller [chars], execution of '[chars]' command failed.
Explanation The APS switch command that was entered by the user has been rejected.
Recommended Action Review the controller information and, if required, reenter the command.
Error Message%APS-5-STATUS : Controller [chars], fiber port [dec] is [chars].
Explanation The specified port has changed its state to either functional or nonfunctional.
Recommended Action No action is required.
Error Message%APS-5-SWITCH : Controller [chars], fiber port [dec] is now active port.
Explanation The specified port has become the active fiber port and has started to transmit traffic.
Recommended Action No action is required.
ARCHIVE_CONFIG Messages
The following are archive configuration-related messages.
Error Message%ARCHIVE_CONFIG-4-ARCHIVE_DELETE_FAILED : Delete of a previously saved archive of the router configuration could not be completed.
Explanation The router could not delete a previously written file. The file that was being deleted contains an archive of the router configuration. This condition might occur if the file was deleted manually.
Recommended Action No action is required.
Error Message%ARCHIVE_CONFIG-4-ARCHIVE_SKIPPED : Archive of router configuration was skipped due to a previous initiation.
Explanation An attempt was made to create two or more archives simultaneously. Only one archive can be created at a time. This condition might occur if two users attempted to create an archive simultaneously.
Recommended Action Retry the archive creation later, after the previous archive has been written.
ARCHIVE_DIFF Messages
The following are Archive Diff and Rollback-related messages.
Error Message%ARCHIVE_DIFF-3-DIFF_CMD_INIT_FAILED : Failed to register the special case [chars] command:"[chars]" during initialization. Config Diff and Rollback cannot be used as a result of this error.
Explanation An internal software error occurred during initialization of the Archive Diff program. As a result of this error, checking configuration differences (Config Diff) and Rollback operations cannot be performed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%ARCHIVE_DIFF-3-DIFF_INIT_FAILED : Could not initialize the Config Diff and Rollback subsystem
Explanation An internal software error occurred during initialization of the Archive Diff program. As a result of this error, checking configuration differences (Config Diff) and Rollback operations cannot be performed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.
AS5400 Messages
The following are Cisco AS5400 platform messages.
Error Message%AS5400-3-HW_ERROR : NULL
Explanation A DFC hardware error has been detected. The Cisco IOS software will power down this DFC and clean up the associated data structures.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AS5400-1-NVRAM : [chars]
Explanation An error has occurred during NVRAM functions.
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. 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 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 gathered information.
Error Message%AS5400-1-NVRAM_INT_LEVEL : [chars] [dec]
Explanation Performing NVRAM erase/write functions with a non-zero interrupt level.
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. 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 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 gathered information.
Error Message%AS5400-3-RTC_TIMEOUT : [chars] to onboard Real Time Clock timed out
Explanation A timeout occurred while reading or writing to the onboard Real Time Clock through the SMBUS.
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. 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 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 gathered information.
Error Message%AS5400-1-UNINSTALLED_MASKED_INT : Uninstalled or masked interrupt: interrupt status [hex] mask [hex] vector [hex]
Explanation The system detected an uninstalled or masked interrupt.
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. 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 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 gathered information.
Error Message%AS5400-1-UNKNOWN_ISR : Unknown ISR: interrupt mask [hex]
Explanation An Interrupt Service Routine has never been installed for the interrupt mask.
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 at https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. 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.
ATM Messages
The following are Asynchronous Transfer Mode messages.
Error Message%ATM-6-PVC_STATE_CHANGE : ATM([chars]): PVC(VCD=[dec], VPI=[dec], VCI=[dec]) state changed to [chars].
Explanation The ATM PVC status has changed.
Recommended Action No action is required.
Error Message%ATM-4-STUCK_VCD : clearing stuck VCD [dec] from map on [chars]
Explanation An SVC map entry has a VCD attached to it. This VCD is stuck and has been previously cleared in the driver.
Recommended Action The stuck VCD condition was detected and has been cleared. No action is required.
ATM_AIM Messages
The following are ATM advanced module messages.
Error Message%ATM_AIM-5-ACTIVE_LINK_DOWN : Interface [chars] of IMA Group [chars] is now inactive.
Explanation The specified link in the specified IMA group has become inactive.
Recommended Action No action is required.
Error Message%ATM_AIM-5-ACTIVE_LINK_UP : Interface [chars] of IMA Group [chars] is now active.
Explanation The specified link in the specified IMA group has become active.
Recommended Action No action is required.
ATMLC Messages
The following are Cisco 7300 ATM line card software messages.
Error Message%ATMLC-4-ALARM : Interface ATM[dec]/[dec], received SONET/SDH alarm: [chars]
Explanation The ATM framer interface has received a SONET or SDH alarm. The message text provides more information on the specific nature of the message.
Recommended Action Perform one or more following actions, depending on when and how the error was received:
–
SONET or SDH alarms may occur while a line card is initializing and negotiating its clock synchronization with the peer. In this situation, the alarms will be cleared, this message is informational only, and no action is required.
–
–
–
–
Error Message%ATMLC-6-CLOCKING : Interface ATM[dec]/[dec], changed clock source to [chars]
Explanation The clock source of the ATM interface has changed to either the line clock or the internal clock, as indicated in the message. If the ATM interface has been configured for line clocking and receives SONET or SDH alarms including loss of signal, loss of frame, and line alarm indication alarms, the interface will first change to the internal clock before changing back to the line clock when the alarms are cleared. If the ATM interface is configured for internal clocking, the SONET or SDH alarms will not cause any clocking change. This message shows the run-time clock source changes on an ATM interface; the show controller atm command always shows the user-configured clock source.
Recommended Action No action is required.
Error Message%ATMLC-3-HWFAIL : The ATM line card in slot [dec] encountered a hardware failure: [chars]
Explanation The ATM line card has encountered a hardware failure and should be deactivated. The problem can be any one of the following:
–
–
–
–
–
–
The message indicates a hardware failure. The line card may have been deactivated by the system.
Recommended Action Perform an OIR operation on the line card to confirm that the problem persists. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Enter the show c7300, show diag slot-number commands, with slot-number being the slot number of the affected card, and the show c7300 errorlog slot, show interface atm, and show controller atm commands 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%ATMLC-1-INITFAIL : The ATM line card in slot [dec] failed to initialize (cause [chars])
Explanation The ATM line card has failed its initialization. The reason for the failure is indicated in the message text. The problems can be one of the following:
–
–
–
–
–
Recommended Action Perform one or more of the following actions:
–
–
–
–
ATMPA Messages
The following are ATM port adapter messages.
Error Message%ATMPA-3-BADTXBFD : [chars]: bad tx buffer descriptor on vcd [dec] size [dec] bfd_index [dec]
Explanation The PA host driver has detected an invalid Tx buffer descriptor.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%ATMPA-3-BADTXPACKET : [chars]: bad tx packet on vcd [dec] size [dec]
Explanation The PA host driver detected a bad Tx host buffer that had a size of 0.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the debug atm events command and gather the output from the 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, show tech-support and debug atm events commands and your pertinent troubleshooting logs.
Error Message%ATMPA-0-BATMANERROR : misc_cntl_reg [hex]. Resetting the OC12 PA...
Explanation The ASIC that interfaces the SAR engines to the VIP4 packet-switching and routing processor has encountered an error that has caused it to fail. As its main function, this ASIC supports the SARs by implementing the cell and packet buffering scheme that is expected on the Port 1 interface, and by managing the commands and indications sequences on the Port 2 interface.
Recommended Action The OC-12 will reboot itself; no action is required. If necessary, clear the interfaces by entering the clear interface command.
Error Message%ATMPA-3-FWCKSUM : [chars] SAR firmware checksum error (expected [hex], obtained [hex])
Explanation CM622 ATM SAR firmware checksum errors have occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the debug atm events command and gather the data from the 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, show tech-support and debug atm events commands and your pertinent troubleshooting logs.
Error Message%ATMPA-3-INITERROR : In file [chars] - line [dec]
Explanation The CM622 process agent could not be created. This process is a temporary process that is used to download firmware.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the debug atm events command and gather the output from the 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, show tech-support and debug atm events commands and your pertinent troubleshooting logs.
Error Message%ATMPA-3-NOTCM622 : Slot [dec] device is not a valid PCI device vendor ID used onOC-12 PA (ID [hex])
Explanation The driver found a device type other than what it expected in the specified PCI slot.
Recommended Action Power down the system, reseat the interface card, and reboot the system. 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%ATMPA-3-NOVPSPACE : [chars] Runs out of VP space for vpi [dec]
Explanation A driver for the VP control block could not be obtained from an unused queue or a queue that is already in use. A new VP or VC could not be created.
Recommended Action Enter the atm vc-per-vp command in interface configuration mode to increase the number of VPs that are configurable on the PA-A3-OC12.
Error Message%ATMPA-4-RXSARIND : RX SAR cmd [chars] error: [chars] (indication=[hex] [hex] [hex])
Explanation Errors involving ATM driver RX SAR indication have occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the debug atm events command and gather the data from the 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, show tech-support and debug atm events commands and your pertinent troubleshooting logs.
Error Message%ATMPA-3-SAROP : [chars] SAR doing [chars] error: [chars]
Explanation An error involving an ATM driver SAR operation has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the debug atm events command and gather the data from the 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, show tech-support and debug atm events commands and your pertinent troubleshooting logs.
Error Message%ATMPA-3-SETUPVCFAILURE : [chars]: Platform Setup_vc failed for [dec]/[dec], vcd [dec]
Explanation A VC could not be set up for the RSP platform.
Recommended Action Enter the debug atm error command on the platform console to attempt to identify the nature of the problem.
Error Message%ATMPA-3-SETUPVPFAILURE : [chars]: Platform Setup_vp failed for vpi [dec]
Explanation A VP could not be set up for the RSP platform.
Recommended Action Enter the debug atm error command on the platform console to attempt to identify the nature of the problem.
Error Message%ATMPA-3-TNLNOTEMPTY : [chars] Have to close all VCs beforemodifying the VP tunnel [dec]
Explanation The VP tunnel has open VCs that are associated with it.
Recommended Action Remove all the VCs that are associated with the VP tunnel before modifying the VP.
Error Message%ATMPA-3-TXACKERROR : [chars] tx cmd ack error ([hex]), vcd [dec].
Explanation An error occurred while a Tx acknowledgment was being processed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the debug atm events command and gather the data from the 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, show tech-support and debug atm events commands and your pertinent troubleshooting logs.
Error Message%ATMPA-3-TXCMDFAIL : TX CMD [dec] failed for vcd [dec].
Explanation A failure occurred while a command for the Batman ASIC SAR was being processed, or an acknowledgment could not be performed for a command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the debug atm events command and gather the data from the 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, show tech-support and debug atm events commands and your pertinent troubleshooting logs.
AUDIT Messages
The following are Audit feature messages.
Error Message%AUDIT-5-AUDIT_DISABLED : Auditing disabled
Explanation The audit function has been disabled on the router.
Recommended Action Verify that the audit function was disabled by someone who is authorized to do so. No other action is required.
Error Message%AUDIT-5-AUDIT_ENABLED : Auditing enabled
Explanation The auditing function has been enabled on the router.
Recommended Action If the changes are valid, audit logs can be verified. No other action is required.
Error Message%AUDIT-3-FILE_RESIZE_ERR : Cannot resize Audit file.
Explanation A file system error occurred while the audit file was being resized.
Recommended Action Check the disk file systems on the router.
Error Message%AUDIT-5-FILE_ROLLOVER : Audit File Roll-over: [dec]
Explanation The audit circular file has rolled over.
Recommended Action Increase the file size of the audit file.
Error Message%AUDIT-1-FILESYSTEM : Hash: %s User: %s
Explanation The Flash memory or disk file systems on the router have been changed.
Recommended Action Verify that the change is valid. No other action is required.
Error Message%AUDIT-5-FILESYSTEM : Filesystem changed. Hash: [chars]
Explanation The Flash memory or disk file systems on the router have been changed.
Recommended Action Verify that the change is valid. No other action is required.
Error Message%AUDIT-3-FILE_WRITE_ERR : Cannot write to Audit file.
Explanation A file system error occurred while the system was writing to the audit file.
Recommended Action Check the disk file systems on the router.
Error Message%AUDIT-1-HARDWARE_CONFIG : Hardware changed. Hash: [chars]
Explanation The hardware on the router has been changed.
Recommended Action Verify that the change is valid. No other action is required.
Error Message%AUDIT-5-HARDWARE_CONFIG : Hardware changed. Hash: [chars]
Explanation The hardware on the router has been changed.
Recommended Action Verify that the change is valid. No other action is required.
Error Message%AUDIT-3-NOFILE : Cannot create Audit file.
Explanation A file system error occurred while the audit file was being created.
Recommended Action Check the disk file systems on the router. No other action is required.
Error Message%AUDIT-3-NOPROC : Cannot create Audit process.
Explanation Insufficient internal resources are available to create the audit process.
Recommended Action Check the available memory on the router.
Error Message%AUDIT-1-RUN_CONFIG : Hash: %s User: %s
Explanation The running configuration on the router has changed.
Recommended Action Verify that the change in configuration is valid. No other action is required.
Error Message%AUDIT-5-RUN_CONFIG : Running Configuration changed. Hash: [chars]
Explanation The running configuration on the router has changed.
Recommended Action Verify that the change in configuration is valid. No other action is required.
Error Message%AUDIT-1-RUN_VERSION : Hash: %s User: %s
Explanation The version of Cisco IOS software running on the router has changed.
Recommended Action Verify that the change in version is valid. No other action is required.
Error Message%AUDIT-5-RUN_VERSION : Running Version changed. Hash: [chars]
Explanation The version of Cisco IOS software running on the router has changed.
Recommended Action Verify that the change in version is valid. No other action is required.
Error Message%AUDIT-1-STARTUP_CONFIG : Hash: %s User: %s
Explanation The startup configuration on the router has changed.
Recommended Action Verify that the change in startup configuration is valid. No other action is required.
Error Message%AUDIT-5-STARTUP_CONFIG : Startup Configuration changed. Hash: [chars]
Explanation The startup configuration on the router has changed.
Recommended Action Verify that the change in startup configuration is valid. No other action is required.
AUTOSEC Messages
The following are AutoSecure messages.
Error Message%AUTOSEC-3-APPLY_ROLLBACK : Applying AutoSecure Rollback to revert to Pre-Autosecure-Running-Config
Explanation The configuration of the AutoSecure session could not be applied to the running configuration. The system has reverted back to the running configuration that preceded AutoSecure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AUTOSEC-1-MODIFIED : AutoSecure configuration has been Modified on this device
Explanation Security configuration has been modified on this device.
Recommended Action This is a notification message only. To apply the modified AutoSecure configuration to the running configuration, restart the AutoSecure feature.
AUTOSTATE Messages
The following are messages for the Autostate feature.
Error Message%AUTOSTATE-6-BRING_UP : Taking interface [chars] out of Autostate mode
Explanation The specified interface is no longer in Autostate mode.
Recommended Action No action is required.
Error Message%AUTOSTATE-3-NO_BOOL : Autostate subsystem: Unable to create watched boolean\n
Explanation The software could not create a watched Boolean operator.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AUTOSTATE-3-NO_QUEUE : Autostate subsystem: Unable to create watched queue\n
Explanation The software could not create a watched queue.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%AUTOSTATE-6-SHUT_DOWN : Putting interface [chars] into Autostate mode
Explanation The specified interface has been placed in Autostate mode.
Recommended Action No action is required.
BAMBAM Messages
The following are one-port Fast Ethernet with coprocessor assist module messages.
Error Message%BAMBAM-3-INSERT_ERROR : 1 FE/Co-Processor error in slot [dec] because [chars].
Explanation A one-port Fast Ethernet coprocessor was inserted into the system before the system was fully initialized. Some Fast Ethernet coprocessors may not become active, and as a result the RPM may reboot or be marked as failed on the PXM.
Recommended Action Do not install more adapters until the system has been fully initialized.
Error Message%BAMBAM-3-MULTDEV : Cannot support more then [dec] 1 FE/Co-Processors
Explanation Too many one-port Fast Ethernet coprocessors were discovered in the system. The one-port Fast Ethernet coprocessor software supports only a single one-port Fast Ethernet coprocessor. All other one-port Fast Ethernet coprocessors that have been installed will be ignored.
Recommended Action Do not install more than the supported number of adapters in the system.
BAT Messages
The following are power supply (BAT) messages.
Error Message%BAT-3-BAT_LOW : Battery voltage is Low
Explanation The system has detected a battery that has a low-voltage condition. This condition was most likely caused by either a battery that is not maintaining its voltage consistently or a loose or broken connection from the AC voltage power supply to the battery backup unit.
Recommended Action Replace the battery or connect the AC voltage power supply to the battery backup unit.
Error Message%BAT-3-BAT_OK : Battery voltage is now normal.
Explanation The system previously detected a low-battery condition that has been corrected and cleared. This condition was most likely caused by either a battery that is not maintaining its voltage or a loose or broken connection to the battery backup unit.
Recommended Action No action is required.
Error Message%BAT-3-DCOUTPUTVOLTFAIL : System detected Power System DC FAIL condition.
Explanation The power system has experienced a DC failure. One of the DC outputs has failed on the power supply.
Recommended Action Identify the DC output that has failed. Most likely, the power supply will require replacement.
Error Message%BAT-3-DCOUTPUTVOLTOK : Power System DC condition is now normal
Explanation The power system DC condition is now normal. Ensure that the AC circuit in your building is operational, verify that the power cord is plugged both into the wall and the power supply, and ensure that the AC power switch on the power supply is set to "On".
Recommended Action This is an informational message only. No action is required.
Error Message%BAT-3-ERROR : Wrong value for battery state
Explanation The system has detected an invalid value for the state of the battery.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%BAT-1-INITSYS : [chars]
Explanation The system failed to create an environmental monitor process. The most likely cause of this condition is a lack of system memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%BAT-3-INPUTVOLTFAIL : System detected Power System AC FAIL condition.
Explanation The power system has experienced an AC failure. One of the AC inputs has failed on the power supply.
Recommended Action Ensure that the AC circuit in your building is operational, verify that the power cord is plugged both into the wall and the power supply, and ensure that the AC power switch on the power supply is set to "On".
Error Message%BAT-3-INPUTVOLTOK : Power System AC condition is now normal
Explanation The power system AC has recovered from a previous failure and is now operational.
Recommended Action This is an informational message only. No action is required.
Error Message%BAT-3-OVERTEMP : System detected Power System THERMAL FAIL condition.
Explanation The power system has experienced an over-temperature condition. This condition was most likely caused by a high ambient temperature in the area in which the router is located.
Recommended Action Ensure that the room temperature is not too high and that air flow to the router is not blocked. If this condition persists, the power supply might be shut down. For further 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%BAT-3-OVERTEMP_OK : System temperature is now normal.
Explanation The system is now operating at a normal temperature. The system previously detected a too-high temperature condition that has now cleared. This condition was most likely caused by a high ambient temperature in the area in which the router is located.
Recommended Action No action is required.
BCM Messages
The following are BCM controller messages.
Error Message%BCM-4-COR_ECC_HIGH : High correctable ECC error rate detected\nL2 cache data errors = [dec]\nL2 cache tag errors = [dec]\nMemory data errors = [dec]\n
Explanation A high rate of soft-parity errors in system memory has been detected. Normal system operation may be affected.
Recommended Action If there is a regular or sustained occurrence of this message, reseat the memory or replace the memory with memory that is known to be operational.
Error Message%BCM-4-ECC_L2CACHE : Corrected ECC from L2 cache
Explanation A soft-parity error from the Layer 2 cache has been detected and corrected. Normal system operation should continue.
Recommended Action If this message appears regularly or for a sustained period of time, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%BCM-4-ECC_MEMORY : Corrected ECC from memory
Explanation A soft-parity error from the memory has been detected and corrected. Normal system operation should continue.
Recommended Action If this message appears regularly or for a sustained period of time, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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.
BCM_GEWAN Messages
The following are Messages related to the Cisco 3800 system controller.
Error Message%BCM_GEWAN-1-GT_MCSC_FAIL : GT96124 : MCSC/MCDMA Initialization failed
Explanation MCSC/MCDMA initialization failed. The chip will not support 128 channels of E1T1.
Recommended Action Reboot the router and see if this message recurs. If it does, contact TAC to RMA the router.
Error Message%BCM_GEWAN-1-GT_MCSC_FAIL : GT96124 : MCSC/MCDMA Initialization failed
Explanation The MCSC or MCDMA could not be initialized. The chip will not support 128 channels of E1T1.
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%BCM_GEWAN-1-GT_PCI_FAIL : GT 96124 PCI Initialization Failed.
Explanation The PCI serial controller for WAN interfaces that is installed on the router motherboard could not be 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%BCM_GEWAN-1-GT_REV_FAIL : GT96124 : Incorrect revision of the chip.Expected [hex] Obtained [hex]
Explanation This revision of the chip does not support 128 channels of E1T1.
Recommended Action Reboot the router and see if this message recurs. If it does, contact TAC to RMA the router
Error Message%BCM_GEWAN-1-GT_REV_FAIL : GT96124 : Incorrect revision of the chip.Expected [hex] Obtained [hex]
Explanation The revision of the chip does not support 128 channels of E1T1.
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%BCM_GEWAN-3-GT_VEND_FAIL : GT 96124: Vendor id - expected [hex] obtained [hex]
Explanation The component has an incorrect revision number, or an incorrect component has been installed.
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%BCM_GEWAN-3-SNMP_REG_FAIL : [chars] SNMP high capacity counter register failed
Explanation The SNMP high counter component could not be registered.
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%BCM_GEWAN-1-VWIC_HW_FAIL : GT96k Motherboard WAN Hardware initialization failed
Explanation The timer library for the GT95K motherboard could not be 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%BCM_GEWAN-3-VWIC_INIT_FAIL : GT96k Motherboard WAN card initialization failed
Explanation One or more of the WAN cards that are installed on the motherboard could not be 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.
BERT Messages
The following are bit error rate tester (BERT) messages.
Error Message%BERT-3-BERT_ALREADY_TEST : A BERT is already running
Explanation A BERT is already in progress on this interface. Another BERT operation cannot be run until either this test is completed or this BERT operation is stopped.
Recommended Action Either wait for the ongoing BERT test to complete or stop the ongoing test by entering the bert abort command and retry the testing operation. No action is required.
Error Message%BERT-3-BERT_BAD_INTERFACE : Interface [dec] is down, BERT cannot be executed on this interface
Explanation The BERT process cannot be started on an interface that either is inactive (down) or has been shut down by the administrator.
Recommended Action Attempt to initialize the interface by entering the no shutdown command on the interface. If this message recurs, or you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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%BERT-6-BERT_FINISH_TIMESLOTS : Finished Generation of Data for timeslots [dec] to [dec] on interface [dec] using profile [dec]
Explanation A BERT with the specified profile has generated data for the time slot range on the controller as specified.
Recommended Action No action is required.
Error Message%BERT-3-BERT_INVPROFILE : The Profile [dec] is not Valid
Explanation A BERT was requested that used an invalid profile number.
Recommended Action Ensure that the BERT number is valid and has been configured, and reenter the BERT number. If a BERT profile has not yet been created, enter the bert profile command in global configuration mode to create a BERT profile.
Error Message%BERT-3-BERT_INVPROFILE_CHANGE : Profile [dec], currently under test, cannot modify
Explanation An attempt was made to modify a profile that is being used by a BERT that is currently running.
Recommended Action Wait until the BERT test has completed to modify the profile, or terminate the BERT operations by entering the bert abort command.
Error Message%BERT-3-BERT_NO_CONT : Controller [dec] does not exist
Explanation The controller specified by the command does not exist.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-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%BERT-6-BERT_RESULTS : [chars]
Explanation This message provides the results of the bert controller command.
Recommended Action No action is required.
Error Message%BERT-6-BERT_START : Starting BERT on Interface [dec] with Profile [chars]
Explanation A BERT operation is starting on the specified interface.
Recommended Action No action is required.
Error Message%BERT-6-BERT_TIMESLOTS : No Results will be generated for this Test
Explanation A BERT was done on individual time slots in the controller. No results were generated for the specified time slots.
Recommended Action No action is required.
BGP Messages
The following are Border Gateway Protocol messages.
Error Message%BGP-3-ADDPATH : Number of paths per prefix exceeded allowed maximum of [dec]
Explanation The number of paths per prefix has exceeded the maximum that is allowed. The maximum number of prefixes is specified in the message text. This condition indicates that BGP is receiving the same prefix from too many neighbors.
Recommended Action Attempt to restrict the number of neighbors that are sending the same prefix. You can restrict the number of neighbors advertising the same prefix by having robust inbound filters.
Error Message%BGP-4-AFIMPORT : [chars] prefixes imported to [chars] vrf reached the limit [dec]
Explanation The number of prefixes imported from other address-family to a VRF has reached its configured limit.
Recommended Action Check the number of imported prefixes from the address-family and verify if the limit should be increased. Check to see if the route map has been correctly associated and imported with the IP VRF.
Error Message%BGP-4-ATTRNULL : A NULL attribute has been assigned to a path
Explanation The path should have been assigned a valid attribute but was incorrectly assigned a value of NULL.
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. 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 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 gathered information.
Error Message%BGP-6-BIGCHUNK : Big chunk pool request ([dec]) for [chars]. Replenishing with malloc
Explanation A request for a large chunk pool has occurred. If the size of the static chunk pools is not adequate to service the request, the request is serviced with a memory allocation (malloc).
Recommended Action This is an informational message only. If this message is a cause for concern, enter the chunk and bgp summary commands, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://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%BGP-5-DAMPENING_DECAY_TIME : Decay time from maximum penalty to suppress penalty is [dec] secs. Maximum penalty: [dec], suppress penalty: [dec]
Explanation The configured dampening parameters may not be feasible. The time interval between the maximum penalty and the suppress penalty may be short.
Recommended Action If you think the decay time from the maximum penalty to the suppress penalty is too short, increase the half-life time or the maximum penalty values.
Error Message%BGP-5-DAMPENING_HIGH_MAX_PENALTY : Maximum penalty ([dec]) is more than allowed maximum ([dec]). Dampening is OFF
Explanation The configured dampening parameters may not be feasible. The maximum penalty time as specified in the error message is less than the maximum allowed penalty time. Dampening will be turned off.
Recommended Action Depending on the value of the maximum penalty, adjust the maximum suppress time. Because the maximum penalty is more than the allowed maximum, reduce the maximum suppress time. The maximum penalty should be greater than the suppress penalty, but less than the maximum allowable penalty.
Error Message%BGP-5-DAMPENING_LOW_MAX_PENALTY : Maximum penalty ([dec]) is less than suppress penalty ([dec]), Dampening is OFF
Explanation The configured dampening parameters may not be feasible. The maximum penalty time as specified in the error message is less than the configured suppress penalty time. Dampening will be turned off.
Recommended Action Depending on the value of the maximum penalty, adjust the maximum suppress time. Because the maximum penalty is less than the suppress penalty, increase the maximum suppress time. The maximum penalty should be greater than the suppress penalty, but less than maximum allowable penalty.
Error Message%BGP-4-INCORRECT_TTL : Discarded message with TTL [dec] from [chars]
Explanation A BGP message was received that contained a TTL value that is not within the acceptable configuration parameters.
Recommended Action If you consider the message to be valid, modify the TTL security configuration to an appropriate value. Otherwise, this message could be coming from a spurious source. If you determine that this message is coming from a spurious source, locate and block the source of the messages.
Error Message%BGP-3-INSUFCHUNKS : Insufficient chunk pools for [chars], requested size [dec]
Explanation The size of the static chunk pools is not correct. This condition is caused by an internal software problem.
Recommended Action Enter the chunk and bgp summary commands to collect information regarding chunks and BGP summary.
Error Message%BGP-4-MAX_EXTCOMM_EXCEED : Exceeded limit of [dec] extended communities per advertised prefix
Explanation An attempt was made to advertise a prefix with an extended community attribute that contains more extended communities than the allowed limit.
Recommended Action Reduce the configured number of Route Targets or other extended communities that will be added to prefix advertisements so that the limit is not exceeded.
Error Message%BGP-4-NBRTRACK : Route Tracking failed on memory. Neighbor tracking for route-fall-over will stop
Explanation The route tracking system has failed to allocate memory. Neighbor route fall-over will stop tracking neighbor routes.
Recommended Action The route tracking system failed to allocate memory. Neighbor route fall-over will stop tracking neighbor routes so that it can give away some memory. If you think that the system is stable then reconfigure neighbor route fall-over. If you get this message, neighbor route-fallover has been deconfigured.
Error Message%BGP-4-NORTRID : BGP could not pick a router-id. Please configure manually.
Explanation A BGP router ID has not been manually configured and BGP is unable to allocate a router ID from the IPv4 address of one of its interfaces.
Recommended Action Make sure that there is at least one interface that is up and has a valid IPv4 address, or configure the router ID manually.
Error Message%BGP-3-ORF_PFXLIST : Received misformatted prefixlist ORF from [chars]
Explanation The received prefix list ORF is formatted incorrectly.
Recommended Action Check the prefix list ORF implementation on the neighboring router.
BSTUN Messages
The following are block serial tunneling (BSTUN) messages.
Error Message%BSTUN-4-RECONFAPIPROUT : Duplicate APIP route found - \n nailing the duplicate and reconfiguring
Explanation The system has detected a duplicate set of connection parameters for this command. The system has unconfigured the command and created a new set of connection parameters.
Recommended Action No action is required.