-
Cisco IOS Release 12.4 System Messages, Volume 1 of 2
-
System Messages Overview
-
AAA through ASPP
-
AT through BGP
-
BIT through C6KPWR
-
C6MSFC through CHOPIN_MAINBOARD_ASYNC_PQII
-
CI through COT
-
CPAD through DBUS
-
DCV through DSCREDCLK
-
DSI through ENT
-
ENV_MON through FR_FRAG
-
FR_LMI through GSR_ENV
-
GSRIPC through IF
-
IFINDEX through ISA
-
ISDN through LCCOREDUMP
-
LCINFO through MBRI
-
Volume 1 Glossary
-
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-2-AAAMULTILINKERROR : [chars]([hex]): Acct db for Id [hex] absent
Explanation An AAA internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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-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-ATTRFORMATERR : Attribute with unknown format [dec]
Explanation An attribute was found with an invalid or unknown format.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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-3-AUTHORMLISTUNDEF : Authorization method list '[chars]' is not defined. Please define it.
Explanation The method list specified in the error message has not yet been defined but has been used in a command.
Recommended Action Define the method list before using it in a command.
Error Message%AAA-3-BADCURSOR : invalid cursor index [dec] max [dec] service [chars] protocol [chars]
Explanation An AAA client has provided an invalid attribute cursor to AAA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-BADHDL : invalid hdl AAA ID [int], hdl [hex], [chars]
Explanation An AAA client has provided an invalid attribute list handle to AAA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-BADLIST : invalid list AAA ID [int]
Explanation An AAA client has provided an invalid attribute list to AAA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-BADMETHOD : Cannot process [chars] method [int]
Explanation A method list function has encountered a method list that was unknown or that could not be processed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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-BADPROTOCOL : Unknown protocol [int]
Explanation The AAA subsystem has encountered an unknown protocol type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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-BADSERVICE : Unknown service [int]
Explanation The AAA subsystem has encountered an unknown service type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-BUFFER_OVERFLOW : Radius I/O buffer has overflowed
Explanation An unusually large number of RADIUS attributes has caused AAA to overflow the RADIUS I/O buffer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-2-FORKFAIL : Cannot fork process [chars]
Explanation An attempt to fork a process has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-IPILLEGALMSG : Invalid use of ip_pid([int])
Explanation A process has sent an illegal message to IP to which IP has not subscribed.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-ISDNINTF : [chars] [chars]: Can not apply configuration to ISDN channel:
"[chars]"Explanation Virtual profiles and virtual access interfaces are required to apply configuration to ISDN. Configuration can not be applied to individual ISDN channels.
Recommended Action Refer to the section on "Configuring virtual profiles by AAA Configuration" in the Cisco IOS Dial Technologies Configuration Guide.
Error Message%AAA-3-MLIST_INTERNAL_ERROR : method list '[chars]': [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-MLIST_TOO_MANY_METHODS : method list '[chars]'
Explanation An internal software error has occurred. An AAA client attempted to add too many methods to a method list.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-NOTABLE : AAA ID [int]
Explanation A resource failure involving AAA has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-NULLCURSOR : Null cursor
Explanation An AAA client has provided a nonexistent attribute cursor to AAA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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-3-PARSEERR : parser is unable to parse [chars] per-user unconfigure command
Explanation All attempts to parse the specified per-user unconfigure command have failed. The specified unconfigure command was not unconfigured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-PARSEERR : Error([dec]) parser is unable to parse [chars] per-user command
Explanation All attempts to parse the specified per-user unconfigure command have failed. The specified unconfigure command was not unconfigured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-SERVER_INTERNAL_ERROR : Server '[IP_address]': [chars]
Explanation An internal software error has occurred in the AAA server group subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-SG_DEADTIME_FORKFAIL : Failed to fork process for [chars].
Explanation An internal software error has occurred. The most likely cause for this condition is system memory exhaustion.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-SG_INTERNAL_ERROR : server group '[chars]': [chars]
Explanation An internal software error has occurred in the AAA server group subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAA-3-SORTFAIL : [chars] :Peruser Could not sort the [chars] attributes
Explanation The attributes received from the AAA server could not be sorted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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.
AAA_CACHE Messages
The following are AAA cache-related messages.
Error Message%AAA_CACHE-3-NULL_TREE_PERIODIC_PROC : Cache Tree pointer is of null value
Explanation The cache tree pointer has a null value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
AAAA Messages
The following are TACACS+ authentication, authorization, and accounting (AAA) security accounting messages.
Error Message%AAAA-3-AAAFORKFAIL : Failed to start AAA process. AAA requests may not be processed.
Explanation The AAA process could not be created.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
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-ACCTFORKFAIL : Failed to start accounting process. Accounting records may not be sent.
Explanation The accounting process could not be created.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%AAAA-6-ACCTSTART : [chars]
Explanation This message is an AAA accounting start message.
Recommended Action No action is required.
Error Message%AAAA-6-ACCTSTOP : [chars]
Explanation This message is an AAA accounting stop message.
Recommended Action No action is required.
Error Message%AAAA-6-ACCTWATCH : [chars]
Explanation This message is an AAA accounting watchdog/update message.
Recommended Action No action is required.
Error Message%AAAA-6-ADMINMSG : [chars] [chars]: [chars]
Explanation This administrative message was passed to the NAS from the AAA server.
Recommended Action No action is required, but the message may contain useful information regarding an event on the server.
Error Message%AAAA-3-BADARG : % AAA: bad argument ([hex])
Explanation NVGEN was attempted on a nonexistent AAA command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-BADAUTHENSTR : Bad authentication data: [chars]
Explanation During AAA authentication operations, the internal database of authentication information for a user was found to be corrupt, and that information used for authenticating a particular user has been lost. This indicates an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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-BADCOMM : Trying config command but should not be.
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-BADLIST : % AAA: bad [chars] list [chars]
Explanation One of the AAA methods does not seem to have a list associated with it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-4-BADMETHNAME : Bad [chars] method-list name "[chars]" (this is only a warning)
Explanation A method list name should not be the same as a method name.
Recommended Action Choose a different method list name that is not also a method name.
Error Message%AAAA-3-BADREG : Illegal registry call.
Explanation An internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-4-BADSGNAME : Bad server-group name [chars] (type [chars]).
Explanation Either the given server-group name does not exist or the given type does not match the defined server group.
Recommended Action Verify that the group exists and that the type is accurate.
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-3-BADSTATE : \n% AAA: Bad state for [chars] list name ([dec])
Explanation An AAA method list is neither named nor supplied by default.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-BADSTR : Bad accounting data: [chars]
Explanation During AAA accounting operations, the internal database of accounting information for a user was found to be corrupt. An internal software error has occurred, and the accounting information for this user session has been lost.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-DLRFORKFAIL : Failed to fork process for [chars].
Explanation A possible memory loss has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-4-DNISGPUNDEF : Warning: DNIS group [chars] is not defined.
Explanation The DNIS group was used without being defined.
Recommended Action Define the DNIS group before using it.
Error Message%AAAA-3-DROPACCTFULLQ : Accounting record dropped due to a full aaa accounting queue: [chars]-[chars] [chars] [chars]
Explanation An accounting record has been dropped because too many accounting packets were enqueued.
Recommended Action If periodic accounting is on, disable it. The accounting queue might have grown too large. This condition is usually due to a nonresponsive AAA server. Enter the show radius statistics or show tacacs command to see if the number of timeouts is increasing or the response delay is unusually high.
Error Message%AAAA-3-DROPACCTLOWMEM : Accounting record dropped due to low memory: [chars]-[chars] [chars] [chars]
Explanation An accounting record has been dropped because of low memory.
Recommended Action If periodic accounting is on, disable it. Attempt to reduce the load on the router.
Error Message%AAAA-3-DROPACCTSNDFAIL : Accounting record dropped, send to server failed: [chars]-[chars] [chars] [chars]
Explanation An attempt to send an accounting record to a server has failed.
Recommended Action Check that the server (TACACS+ or RADIUS) is operational, and then ensure that the NAS is configured properly. Finally, check that the NAS can communicate with the server.
Error Message%AAAA-3-ILLEGALNAME : Illegal [chars] [chars] name "[chars]" rejected
Explanation A method list name should not be the same as a method name.
Recommended Action Choose a different method list name that is not also a method name.
Error Message%AAAA-3-ILLSGNAME : Illegal server-group name [chars] (type [chars]).
Explanation The given server-group name is a name that could conflict with internally chosen lists.
Recommended Action Choose a different server-group name.
Error Message%AAAA-3-INTERNAL_ERROR : [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-INVALIDLIST : % AAA: invalid [chars] list [dec].
Explanation One of the AAA methods lists has inconsistent settings.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-INVSTATE : [chars] AUTHOR/[chars]: Internal state is invalid: astruct [hex] ustruct [hex]
Explanation One of the two mentioned data structures is not set but is needed. An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-LISTCREATE : The list [dec] for [chars] is NULL. This should never be.
Explanation One of the method lists to be created at startup was not created. This may cause a reload.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-MKTIMERFAIL : Failed to create periodic accounting timer for user [chars]. This user may not generate periodic accounting records.
Explanation The system failed to allocate memory for a periodic accounting timer.
Recommended Action Free up some memory and have the user reauthenticate.
Error Message%AAAA-3-MKTIMERINVALID : Invalid request to create periodic accounting timer for user [chars]. Timer already exists.
Explanation The request to create a periodic accounting timer was invalid because the timer already existed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-NOADMINPROC : [chars]
Explanation An administrative process has been enabled but could not run.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-NOFREELISTS : % AAA: No free [chars] lists for "[chars]"
Explanation You have reached the maximum number of possible authentication lists for this method.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-NOLIST : [chars]: no method list-name.
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-NOREG : [chars] method [dec] has no registry!
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-NOSERV : No name for servergroup in method [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-NOSG : No server-group passed through parser.
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-4-NOSERVER : Warning: Server [IP_address] is not defined.
Explanation The specified server is not on the master list and should be defined, or unexpected results may occur.
Recommended Action Define the server on the appropriate master list as soon as possible.
Error Message%AAAA-3-NULPORT : Could not establish port information
Explanation An internal software error has occurred. AAA could not determine a valid port string based on the client-provided information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-NULUSR : accounting for null user
Explanation An internal software error has occurred. During shutdown of a line or interface, the system tried to send accounting information via AAA, but could not find the user to which the accounting information belonged. The error was probably caused by the system trying to do accounting twice for the same event. This error message can occur without any loss of accounting information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-OVERWRITE : Overwrote internal buffer space [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-PERIODICFORKFAIL : Failed to start periodic accounting process. Periodic accounting records may not be sent.
Explanation An attempt to create the periodic accounting process has failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%AAAA-3-PERNOTIMER : AAA/ACCT/TIMER: Periodic update but no timer.
Explanation An attempt was made to free a timer, and the method is PERIODIC, but no timer seems to exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-RELOGIN : sanity check in re-login [chars] to [chars]
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-6-SERVERMSG : [chars] [chars]: [chars]
Explanation This error message was passed to the NAS from the AAA server.
Recommended Action No action is required, but the message may contain useful information regarding an event on the server.
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.
Error Message%AAAA-4-SERVNOTACPLUS : The server-group "[chars]" is not a tacacs+ server group. Please define "[chars]" as a tacacs+ server group.
Explanation The protocol used by the server group does not support the configured AAA action.
Recommended Action Use a server group that has been configured as a TACACS+ server group.
Error Message%AAAA-4-SERVUNDEF : The server-group "[chars]" is not defined. Please define it.
Explanation A given server group was listed in a method list without first being defined.
Recommended Action Define the server group before using it.
Error Message%AAAA-3-SGDUPFREE : Duplicate free of server group [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-STRCREATE : str_create overwrote its internal buffer.
Explanation An internal buffer used to assemble a string was exceeded, possibly corrupting other memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-SUBTYPE : Bad Subtype [dec] for "[chars]" ([dec])
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-3-TIMERNOPER : AAA/ACCT/TIMER: No periodic update but timer set.
Explanation An attempt to free a timer was unsuccessful. The update method was not PERIODIC, and therefore no timer will exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AAAA-4-UNSUPWAITSTART : % AAA: Unsupported option wait-start mapped to start-stop.
Explanation The "wait-start" form of accounting is not supported and will be mapped to "start-stop".
Recommended Action No action is required.
AC Messages
The following are Attachment Circuit messages.
Error Message%AC-3-ACMGR_INVALID_HDL : Received invalid [chars] handle
Explanation The Attachment Circuit manager has received an invalid handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AC-3-ACMGR_INVALID_MSG : Received [chars]
Explanation The Attachment Circuit manager has received an invalid message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AC-3-ACMGR_MISSED_CIRCUIT : Circuit info missing in [chars] message.
Explanation The Attachment Circuit manager has received a message from which circuit information is missing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AC-3-AC_PROVISION : [chars]
Explanation An error was encountered during Attachment Circuit provisioning or unprovisioning.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AC-3-AC_SUBBLOCK : [chars]
Explanation An error was encountered during the creation or removal of an Attachment Circuit subblock.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AC-3-AC_VECTOR : [chars]
Explanation During Attachment Circuit configuration, an error was encountered that caused problems in the setting or restoration of the interface vectors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AC-3-L2SS_BAD_HANDLE : Corrupted L2SS handle [[hex]].
Explanation An internal Layer 2 Service Switch manager error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AC-3-L2SS_NULL_CONTEXT : Encountered a NULL context in [chars]
Explanation The system has encountered a null context in the Layer 2 Service Switch manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AC-3-L2SS_UNEXPECTED : Received unexpected [chars] message
Explanation The Layer 2 Service Switch manager has received an unexpected message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AC-3-L2SS_WRONG_KEYS : Wrong set of keys in [chars] message
Explanation SIP has sent an invalid set of keys to the Layer 2 Service Switch manager.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
ACCESS_IE Messages
The following are Access information element (IE) messages.
Error Message%ACCESS_IE-3-INVALID_HANDLE : Caller passed in invalid handle - traceback to follow.
Explanation An invalid handle was encountered in the Access IE library.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
ACLMERGE Messages
The following are access control list (ACL) merge messages.
Error Message%ACLMERGE-3-CUDDERROR : A CUDD Library error was detected in [chars]
Explanation An error was detected by the CUDD library, and the ACL merge has failed. The failed ACL merge may cause more traffic to be switched by the software, resulting in lower performance for the interface on which the ACL merge had failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information, along with the ACL configuration of this device.
Error Message%ACLMERGE-3-CUDDWARN : A CUDD Library warning message for interest in this event in [chars]
Explanation A CUDD library warning message for the specified event has been received.
Recommended Action This is a debug message only. No action is required.
ADAPTER Messages
The following are Channel Interface Processor (CIP) messages for the adapter task.
Error Message%ADAPTER-6-BADREQUEST : Bad request code [dec] generated on port [dec]
Explanation A request was sent to the function that handles general requests for the specified port. The request code was not in a range recognized by that function.
Recommended Action The CIP has recovered by ignoring the request. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-BADSTATE : Bad state: port [dec], request code [dec], state [dec], flags [hex]
Explanation The specified port was in an invalid state while it was attempting to process the specified general request.
Recommended Action The CIP recovered by forcing the port into a valid state. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-DIAGBEGIN : [chars] diagnostic starting
Explanation The user has used the test cbus command to request a particular adapter diagnostic to be run. This message informs the user that the diagnostic routine has started.
Recommended Action Wait for the next message.
Error Message%ADAPTER-0-DIAGDATA : Module Call: [hex][hex] Error ID: [hex][hex]
Explanation A diagnostic routine has detected a failure in the ECA hardware. The indicated codes are used to locate the specific component that failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-DIAGDATA2 : Module Call: [hex][hex] Error ID: [hex][hex]
Explanation A diagnostic routine has detected a failure in the ECA hardware. The indicated codes are used to locate the specific component that failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-0-DIAGFAIL : Port [dec] failed the [chars] diagnostic
Explanation A diagnostic routine has failed. The specified port will not be used.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-DIAGFAIL2 : [chars] diagnostic failed
Explanation A diagnostic requested by the test cbus command has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-DIAGGOOD2 : [chars] diagnostic ran successfully
Explanation A diagnostic requested by the test cbus command has completed successfully.
Recommended Action No action is required.
Error Message%ADAPTER-6-DIAGRANGE : Diagnostic number ([dec]) out of range 0-[dec]
Explanation The diagnostic number requested by the test cbus command is invalid.
Recommended Action Reenter the command with a valid diagnostic number.
Error Message%ADAPTER-6-DIAGSTOP : Interface must be shutdown to run diagnostic
Explanation The test cbus command was used to run a diagnostic on an active interface. The interface must be shut down before the diagnostic is run.
Recommended Action Use the shutdown command to stop the interface and then reissue the diagnostic request.
Error Message%ADAPTER-0-DIAGTERM : Port [dec]: The [chars] diagnostic failed to terminate
Explanation A diagnostic routine did not end when expected. The specified port will not be used.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-DIAGTERM2 : [chars] diagnostic failed to terminate
Explanation A diagnostic requested by the test cbus command did not end when expected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-0-LOADFAIL : Port [dec] microcode load failed.
Explanation Each adapter has an onboard microprocessor. This message indicates that the operation to load the code for that microprocessor has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-LOGDATA : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation An error has occurred in the adapter. The information displayed will help software developers determine the nature of the error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-LOGOUT : Port [dec] logout data. Adapter microcode [hex]
Explanation This message indicates the start of the logout data. Logout data occurs whenever a problem is detected on the port adapter or, with an ECA, on the fiber.
Recommended Action If this message is being continually generated on a new installation, it may indicate that the fiber is not connected properly. Verify that the connector is firmly seated. If a loose fiber was not the cause of these messages, report this message to your Cisco technical support representative.
Error Message%ADAPTER-6-LOGSAME : [hex] to [hex] same as above
Explanation This message is used when logout information is displayed to avoid printing duplicate data.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-NO_CHAN_EV_BUF : No channel event buffer: Daughter board [dec]
Explanation Channel link incident events are being dropped by the channel adapter because of an overflow of incidents.
Recommended Action Use SNMP to poll the CIP for the current LIR counts.
Error Message%ADAPTER-6-NO_CHAN_EV_POOL : Could not allocate channel event pool
Explanation There is insufficient memory on the channel adapter to allocate buffers used for generating channel adapter events. Unless the memory is increased, no channel link incident events (SNMP traps) will be generated.
Recommended Action Add more memory to the channel adapter.
Error Message%ADAPTER-6-SCAN : Port [dec] scan data. Adapter microcode [hex]
Explanation This message precedes the "SCANDATA" error message for the adapter in the specified port. This scan is usually produced as a result of a hardware error.
Recommended Action Report the entire error message, including the "SCANDATA" error message that follows it, to your Cisco technical support representative.
Error Message%ADAPTER-6-SCANDATA : [hex] [hex] [hex] [hex] [hex]
Explanation The data in this message is related to the hardware failure of an adapter.
Recommended Action Report the entire error message, including the preceding "SCAN" error message, to your Cisco technical support representative.
Error Message%ADAPTER-0-START_FAIL : Diagnostics failed for port [dec], start request ignored.
Explanation Prior to receipt by the adapter of a start command from the Route Processor, a set of diagnostics is run. If one of them fails, then the adapter will not be started when the start command is issued.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADAPTER-6-WRAP : Wrap plug detected in port [dec]. Wrap loop started.
Explanation A wrap plug is installed in the specified port. Wrap diagnostics will run until the wrap plug is removed, if this is the only adapter, or until both adapters have wrap plugs installed.
Recommended Action Remove the wrap plug and connect the interface to a channel.
Error Message%ADAPTER-6-WRAPSTOP1 : Wrap plug removed from port [dec]. Wrap loop ended.
Explanation The wrap plug has been removed, causing the wrap diagnostics to end.
Recommended Action No action is required.
Error Message%ADAPTER-6-WRAPSTOP2 : Port [dec] active. Port [dec] wrap loop ended.
Explanation The wrap diagnostics have ended because the other adapter is active.
Recommended Action Remove the wrap plug and connect the interface to a channel if you wish to use this adapter. Otherwise, no action is required.
ADJ Messages
The following are adjacency subsystem messages.
Error Message%ADJ-3-ADJDELMSG : Invalid delete message length [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADJ-3-ADJFIBIDB : Adjacency update with invalid fibidb([dec])
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADJ-3-NULLFIBHWIDB : Add [chars] with null cef hwidb([chars])
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ADJ-3-NULLFIBIDB : Add [chars] with null cef idb
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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.
AICMGMT Messages
The following are Alarm Interface Controller management messages.
Error Message%AICMGMT-1-AIC_ALERT : AIC Slot [int]: [chars]
Explanation The Alarm Interface Controller network module in the specified slot has forwarded this error message to the Cisco IOS software. This error is localized to the Alarm Interface Controller network module and does not involve the Cisco IOS software.
Recommended Action Consult the documentation for the Alarm Interface Controller network module for information about the described condition.
Error Message%AICMGMT-2-AIC_CRITICAL : AIC Slot [int]: [chars]
Explanation The Alarm Interface Controller network module in the specified slot has forwarded this error message to the Cisco IOS software. This error is localized to the Alarm Interface Controller network module and does not involve the Cisco IOS software.
Recommended Action Consult the documentation for the Alarm Interface Controller network module for information about the described condition.
Error Message%AICMGMT-3-AIC_ERR : AIC Slot [int]: [chars]
Explanation The Alarm Interface Controller network module in the specified slot has forwarded this error message to the Cisco IOS software. This error is localized to the Alarm Interface Controller network module and does not involve the Cisco IOS software.
Recommended Action Consult the documentation for the Alarm Interface Controller network module for information about the described condition.
Error Message%AICMGMT-4-AIC_UNEXPVER : AIC Slot [int]: management message version mismatch - [hex] [hex] [hex] [hex]\n
Explanation The Cisco IOS software image and the firmware version of the Alarm Interface Controller network module may be incompatible. The four bytes that are specified in the error string represent the version of the current Alarm Interface Controller network module firmware. To see the expected version for the Alarm Interface Controller network module firmware (specified when the current Cisco IOS image was produced), enter the show alarm-interface slot# command.
Recommended Action To correct the mismatched versions, replace the installed version of the Cisco IOS software image or the version of the firmware of the Alarm Interface Controller network module, or replace both versions. The Cisco documentation for release notes and field notices will provide information on the versions that are compatible. This message is only a warning. It does not imply that errors will occur if the system continues to run with the mismatched versions. If you decide to contact a Cisco technical support representative for assistance, first enter the show alarm-interface slot# command for the slot that was specified in the error message. Report the gathered information, along with the version of Cisco IOS software used, to your Cisco technical support representative.
Error Message%AICMGMT-4-AIC_WARNING : AIC Slot [int]: [chars]
Explanation The Alarm Interface Controller network module in the specified slot has forwarded this error message to the Cisco IOS software. This error is localized to the Alarm Interface Controller network module and does not involve the Cisco IOS software.
Recommended Action Consult the documentation for the Alarm Interface Controller network module for information about the described condition.
AIM Messages
The following are advanced interface module (AIM) messages.
Error Message%AIM-2-AIMSUPP : AIM type [dec] is not supported by this platform.
Explanation The AIM that is installed is not supported by this platform.
Recommended Action Power off the router and replace the AIM card.
Error Message%AIM-2-AIMUNSUPP : AIM type [hex] is not supported by this platform.
Explanation The AIM that is installed is not supported by this platform.
Recommended Action Power off and replace the AIM card.
AIP Messages
The following are ATM Interface Processor (AIP) messages.
Error Message%AIP-3-AIPFAILSETUPVC : [chars] Failed to setup vc [dec] (Cause: [chars])
Explanation The AIP driver has failed to set up a VC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%AIP-3-AIPFAILSETUPVCAVG : Interface [chars], Failed to setup vc [dec] (Cause: [chars]) Expected range [[dec] .. [dec]]Kbps for AIP Average Rate Metering. Average Rate=Peak Rate= [dec] Kbps turns Average Rate Metering OFF
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
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-1-CRITICAL_ALARM : CRITICAL alarm condition detected
Explanation A critical alarm event that needs immediate attention has occurred. The system will shut down within two minutes.
Recommended Action Check the source of the critical alarm to take any corresponding action. Do not power on unless the situation is corrected. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALARM-2-MAJOR_ALARM : Major alarm condition detected
Explanation A major alarm event that affects system service has occurred.
Recommended Action Check the source of the major alarm in order to take corresponding actions. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALARM-3-MINOR_ALARM : Minor alarm condition detected
Explanation A minor alarm event that does not affect system service has occurred.
Recommended Action Check the source of the minor alarm to avoid a worsening of the situation. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 alarm type either has not been registered or it 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.
ALC Messages
The following are ATM line card messages.
Error Message%ALC-3-CMDERR : ([dec]/[dec]) Interface ([chars]): [chars] IPC command fails (cause: [hex])
Explanation The ATM RP driver has experienced an IPC command error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-3-EVENT : ([dec]/[dec]) Interface ([chars]): unknown IPC event ([int]) from linecard
Explanation The ATM RP driver has received a unknown event from the line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-4-HIRATE : ([dec]/[dec]) Interface ([chars]): SAR limits VBR VC PCR to [dec] kbps, opening UBR VC instead
Explanation The SAR sublayer limits VBR VC PCR to one-half of the link bandwidth.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-3-INIT : ATM driver ([int]/[int]) initialization [chars].
Explanation The ATM RP driver has experienced a software initialization error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-4-NULLCEFIDB : ([dec]/[dec]) Interface ([chars])
Explanation CEF IDB is missing from this interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-4-UNSUP : ([dec]/[dec]) Interface ([chars]): unsupported feature: [chars]
Explanation This feature is not supported by Internet router ATM RP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-3-VCADJ : ([dec]/[dec]) Per-VC adjacency error: VC:[int] [chars]
Explanation The ATM RP driver has experienced a per-VC adjacency software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALC-3-VCENCTYPE : ([dec]/[dec]) VC:[int] unknown VC encapsulation type ([int])
Explanation The ATM RP driver has experienced an unknown VC encapsulation software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
ALIGN Messages
The ALIGN facility controls a feature in RISC-processor-based Cisco products that identifies software in need of memory use optimization. The following are memory optimization in RISC processor messages.
Error Message%ALIGN-3-CORRECT : Alignment correction made at [hex] [chars]ing [hex]
Explanation An alignment error has been detected and corrected. Alignment errors are due to misaligned reads and writes caused by a software failure. Correcting alignment errors consumes processor resources and may result in a performance penalty. If there are recurring alignment errors, CPU utilization may be seriously affected.
Recommended Action To take advantage of recent fixes, upgrade your system to the latest Cisco IOS software release in your release train. If this message recurs, enter the show log, show alignment and show tech-support commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALIGN-1-FATAL : [chars]
Explanation An alignment error has occurred. Alignment errors are caused by misaligned reads and writes. For example, a two-byte read of a memory address that is not a multiple of two bytes is an alignment error. Alignment errors are caused by internal software failures. The system will be reloaded, often with a bus error.
Recommended Action This message is caused by a software failure. To take advantage of recent fixes, upgrade your system to the latest Cisco IOS software release in your release train. If this message recurs, copy the error message text exactly as it appears on the console or in the system log, enter the show log, show alignment and show tech-support commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALIGN-3-FULL : Alignment log is full - no new entries will be recorded
Explanation The router identified more software components in need of memory optimization than it can record.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALIGN-3-READEXCEPTION : Warning : read accees failed at [chars], still continuing
Explanation In ls1010, read access failures prevent the router from reloading. The failures can be caused by either a bad register value in release 3.3 of the ASP or a problem in the hardware.
Recommended Action If the ASP version is 3.3 or later, contact your Cisco technical support representative.
Error Message%ALIGN-3-READEXCEPTION : Warning : read access failed at [chars], still continuing \n
Explanation A read access failure has occurred. For LightStream 1010 ATM switches, a read access failure does not cause the switch to reload. This condition can be caused either by a bad register value in the ATM switch processor, if the ATM switch processor is version 3.3 or earlier, or by a hardware problem.
Recommended Action If the ASP version is 3.3 or earlier, no action is required. The switch will ignore the error and continue. If the ASP version is later than version 3.3, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALIGN-3-SPURIOUS : Spurious memory access made at [hex] reading [hex]
Explanation A spurious access occurs when a process attempts to read from the lowest region of memory. This portion of memory is reserved and should never be accessed. An attempted read operation to this region of memory is usually caused by the return of a nonexisting value to a function in the software.
Recommended Action The system has detected the illegal access and was able to correct it without a system failure. This condition indicates a software failure. To take advantage of recent fixes, upgrade your system to the latest Cisco IOS software release in your release train. If this message recurs, enter the show log, show alignment and show tech-support commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALIGN-3-TRACE : -Traceback= [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation This tracing message provides information about a previous ALIGN error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALIGN-3-TRACEX : [chars]
Explanation This tracing message provides information about a memory optimization error that involves the RISC processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
ALPS Messages
The following are Airline Protocol Support (ALPS) messages.
Error Message%ALPS-3-ALPSFAIL : ALPS: Assertion failed: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ALPS-5-ASCU_DISABLED_ASCU_STUCK : ASCU [hex] on interface [chars] has been disabled since 4 consecutive messages were received from same SID.
Explanation An ALPS ASCU has been automatically disabled.
Recommended Action No action is required.
Error Message%ALPS-5-ASCU_DOWN : ASCU [hex] on interface [chars] is down.
Explanation An ALPS ASCU has transitioned from up to down.
Recommended Action No action is required.
Error Message%ALPS-3-ASCU_FSM_ERR : ASCU [hex] on interface [chars] has an internal FSM error.
Explanation An internal software error has occurred.
Recommended Action Turn debug flags on, capture traces, and contact Cisco technical support.
Error Message%ALPS-3-ASCU_IF_STUCK : Polling for ASCU [hex] on interface [chars] is stalled.
Explanation The polling mechanism for an ALPS interface has become stuck.
Recommended Action No action is required.
Error Message%ALPS-5-ASCU_UP : ASCU [hex] on interface [chars] is up.
Explanation An ALPS ASCU has transitioned from down to up.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_ASCU_REJECT : Circuit [chars] received a Circuit Open Confirm with a list of rejected ascus
Explanation An ALPS circuit sent a "circuit open request" message and received a "circuit open confirm" message with a list of rejected ASCUs.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_BUSY_END : Circuit [chars] has exited a congested state.
Explanation An ALPS circuit is no longer experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_BUSY_START : Circuit [chars] has entered a congested state.
Explanation An ALPS circuit is experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-5-CIRCUIT_CLOSED : Circuit [chars] changed state to closed, rsn = [chars].
Explanation An ALPS circuit has transitioned from open to closed.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_CKT_DISABLED : Threshold exceeded for circuit disabled drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by a disabled circuit exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_INVALID_ASCU : Threshold exceeded for invalid ASCU drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by an invalid ASCU identifier exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_LIFETIME_EXPIRED : Threshold exceeded for lifetime timer expiration drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by a lifetime timer expiration exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_QUEUE_OVERFLOW : Threshold exceeded for queue overflow drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by queue overflow exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-CIRCUIT_DROPS_VC_RESET : Threshold exceeded for X.25 VC Reset drops for circuit [chars]
Explanation The number of ALPS circuit drops caused by an X.25 VC reset exceeds the ALPS circuit threshold value.
Recommended Action No action is required.
Error Message%ALPS-5-CIRCUIT_OPEN : Circuit [chars] changed state to open.
Explanation An ALPS circuit has transitioned from closed to open.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_OPEN_FAILED : Circuit [chars] received a Circuit Open Failed message, rsn = [chars].
Explanation An ALPS circuit sent a "circuit open request" message and received a "circuit open failed" message as a reply.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_UPDATE_FAILED : Circuit [chars] received a Circuit Open Failed message, rsn = [chars].
Explanation An ALPS circuit sent a "circuit update" message and received a "circuit open failed" message as a reply.
Recommended Action No action is required.
Error Message%ALPS-6-CIRCUIT_X25_VC_STUCK : Host unresponsive on X.25 VC for circuit [chars]
Explanation The X.25 or EMTOX host is not advancing the transmit window for extended periods of time. This delay may indicate a temporary problem with the host application. An X.25 reset is sent to reset the transmit and receive windows to allow communication to proceed.
Recommended Action No action is required.
Error Message%ALPS-6-PEER_BUSY_END : Peer ([IP_address], [chars]) has exited a congested state.
Explanation An ALPS peer connection is no longer experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-6-PEER_BUSY_START : Peer ([IP_address], [chars]) has entered a congested state.
Explanation An ALPS peer connection is experiencing congestion.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_CLOSED : Peer ([IP_address], [chars]) changed state to closed.
Explanation An ALPS peer connection is now closed.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_CLOSED_DYNAMIC_INACTIVITY : Peer ([IP_address], [chars]) closed due to inactivity.
Explanation An ALPS peer connection is now closed because of inactivity.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_CONN_ID_CHANGE : Peer ([IP_address], [chars]) ID modified to ([IP_address], [chars]).
Explanation An ALPS peer connection identifier has changed.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_MAX_SIZE_EXCEEDED : Threshold exceeded for maximum size exceeded drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops caused by surpassing maximum size exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_PEER_UNREACHABLE : Threshold exceeded for peer unreachable peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops caused by a peer unreachable condition exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_QUEUE_OVERFLOW : Threshold exceeded for TCP Queue overflow peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops caused by a queue overflow exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-7-PEER_DROPS_VERSION_MISMATCH : Threshold exceeded for version mismatch peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops caused by a version mismatch exceeds the ALPS peer threshold value.
Recommended Action No action is required.
Error Message%ALPS-5-PEER_OPEN : Peer ([IP_address], [chars]) changed state to open.
Explanation An ALPS peer connection is now open.
Recommended Action No action is required.
Error Message%ALPS-6-PEER_OPEN_FAIL : Peer ([IP_address], [chars]) open failed, rsn = [chars]
Explanation An attempt to open an ALPS peer connection has failed.
Recommended Action No action is required.
AMD79C971_FE Messages
The following are AMD 79C971 Fast Ethernet device driver messages.
Error Message%AMD79C971_FE-5-FAILED_SUSPEND : Failed to suspend the amd79c971 chip
Explanation An attempt to suspend the AMD Am79C971 chip has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
AMDP2_FE Messages
The following are AMD 79C970A Ethernet and Fast Ethernet messages.
Error Message%AMDP2_FE-4-BABBLE : [chars], transmit problem, CSR0=[hex]
Explanation The transmitter has been on the channel longer than the time it has taken to transmit the largest frame. This message also indicates that 1519 or more bytes are transmitted.
Recommended Action The system should recover. No action is required.
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-3-BIC_FE_RESET : Reseting [chars]
Explanation The BIC FE interface is being reset.
Recommended Action No action is required.
Error Message%AMDP2_FE-5-COLL : [chars], Excessive collisions, TDR=[dec], TRC=[dec].
Explanation Ethernet or Fast Ethernet is seeing multiple collisions. This problem may occur under heavy loads. The system should recover.
Recommended Action 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-5-EXCESSCOLL : [chars] TDR=[dec], TRC=[dec]
Explanation Ethernet or Fast Ethernet is seeing multiple collisions. This condition may occur under heavy loads. If an interface fails to allocate a slot in which it can transmit its frame without another collision for 16 times, it will not retry the operation. The frame is not transmitted and is marked as an excessive collision.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-6-EXCESSCOLL : [chars] TDR=[dec], TRC=[dec]
Explanation Ethernet or Fast Ethernet is seeing multiple collisions. This condition may occur under heavy loads. If an interface fails to allocate a slot in which it can transmit its frame without another collision for 16 times, it will not retry the operation. The frame is not transmitted and is marked as an excessive collision.
Recommended Action The system should recover. No action is required.
Error Message%AMDP2_FE-1-INITFAIL : [chars], Init failed, CSR[dec]=[hex]
Explanation The software has failed to initialize or restart an Ethernet or Fast Ethernet interface.
Recommended Action Clear the interface. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 : [chars], transmit error
Explanation Late collisions have occurred on the Ethernet or Fast Ethernet interface. When a collision is detected by a station after it has sent the 512th bit of its frame, it is counted as a late collision.
Recommended Action If the interface is a Fast Ethernet interface, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required.
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 : [chars], lost carrier. cable/transceiver problem?
Explanation The cable or transceiver is not connected.
Recommended Action Connect the cable or transceiver.
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 : [chars], Memory error, CSR[dec]=[hex]
Explanation The interface could not access system resources for a long time. This condition may occur under very heavy loads.
Recommended Action The system should recover. No action is required.
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-MISS : [chars], [chars] receive problem, CSR0=[hex]
Explanation The interface lost an incoming receive frame because a receive descriptor was not available.
Recommended Action The system should recover. No action is required.
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 : [chars] MII 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 for the interface in the configuration menu.
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 : Slot [dec] device ID seen as [hex], expected [hex]
Explanation The software could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot the system. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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-1-NOTSUPPORTED : 2FE PA not supported on NPE100, shutting down bay
Explanation A 2FE PA is not supported on a Cisco 7200 series router with NPE100.
Recommended Action Upgrade to NPE150 or higher.
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 : [chars], packet buffer, pak=[hex]
Explanation The software has detected an error in descriptor ownership.
Recommended Action Upgrade to a more recent version of the software. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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 : [chars], Spurious chip interrupt, CSR[dec]=[hex]
Explanation An illegal condition has occurred, indicating that initialization has been done.
Recommended Action Clear the interface. If the message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AMDP2_FE-3-SPURIDON : AMDP2/FE [chars], Spurious IDON interrupt, CSR[dec]=[hex]
Explanation An illegal condition has occurred, indicating that initialization has been done.
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 : [chars], Spurious interrupt error, CSR0=[hex]
Explanation An illegal condition was encountered during initialization. The system should recover.
Recommended Action No action is required.
Error Message%AMDP2_FE-4-SPURIOUS : AMDP2/FE [chars], Spurious interrupt error
Explanation An illegal condition was encountered during system initialization. The system should recover.
Recommended Action 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-TOOMANYPART : Bad packet with [dec] particles, pak=[hex]
Explanation The software has detected an invalid packet.
Recommended Action Try a more recent version of the software. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AMDP2_FE-3-UNDERFLO : [chars], transmit error
Explanation While transmitting a frame, the local buffer of the controller chip received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system. The system should recover.
Recommended Action No action is required.
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. The system should recover.
Recommended Action No action is required.
AP Messages
The following are authentication proxy (AP) messages.
Error Message%AP-6-AUTH_PROXY_AUDIT_START : initiator ([IP_address]) start
Explanation This message documents the transaction log of AP network activities. The message is issued at the start of each AP cache, recording the source addresses.
Recommended Action This message is for informational purposes only and can be used to collect the basic accounting data for the proxied caches.
Error Message%AP-6-AUTH_PROXY_AUDIT_STOP : initiator ([IP_address]) send [int] packets [int] bytes; duration time [chars]
Explanation This message documents the transaction log of AP network activities. The message is issued at the stop of each AP cache, recording the source addresses, the number of bytes transmitted by the client, and the cache duration time.
Recommended Action This message is for informational purposes only and can be used to collect the basic accounting data for the proxied caches.
Error Message%AP-1-AUTH_PROXY_DDOS_ATTACK : Distributed DOS attack
Explanation The authentication proxy router is possibly undergoing a distributed DOS attack. It has received more than 512 HTTP connections containing no data.
Recommended Action If a DDOS attack is suspected, disallow the source from accessing the router.
Error Message%AP-1-AUTH_PROXY_DOS_ATTACK : Possible DOS attack from source IP-address [IP_address]
Explanation A host is continuously opening HTTP connections through the authentication proxy router without sending any data. This condition indicates a DOS attack. This message can also be caused when a user is connecting to an HTTP server via a Telnet-like program to port 80.
Recommended Action If a DOS attack is suspected, disallow the source of the HTTP connections from accessing the router.
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-1-AUTH_PROXY_RETRIES_EXCEEDED : IP-address [IP_address] has exceeded the maximum retry limit
Explanation A host has exceeded the maximum allowed limit for login attempts. The host may be infected by a virus that is continuously sending HTTP requests. This condition indicates a potential DOS attack, but it can also occur when a user is making legitimate attempts to log in.
Recommended Action If a DOS attack is suspected, disallow the source of the login attempts from accessing the router.
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 automatic protection switching 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.
ARAP Messages
The following are AppleTalk Remote Access Protocol (ARAP) messages.
Error Message%ARAP-3-0 : TTY [dec]: arap callback aborted
Explanation ARAP callback has ended because the system received an unexpected message during the MNP4 link setup.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ARAP-6-ADDRFREE : TTY [dec]: ARAP ended for user [chars]; address [atalk_net]; [dec] seconds connected
Explanation This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged out.
Recommended Action No action is required.
Error Message%ARAP-6-ADDRUSED : TTY [dec]: ARAP started for user [chars]; address [dec].[dec]
Explanation This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged in.
Recommended Action No action is required.
Error Message%ARAP-3-BADCONFIG : TTY [dec]: unhandled configuration command
Explanation A configuration command was not recognized.
Recommended Action Check the configuration file on the server for any invalid configuration commands.
Error Message%ARAP-6-BADEXIT : TTY [dec]: exited user [chars]: [chars]
Explanation A user was disconnected from ARA protocol unexpectedly. The disconnection may be caused by dropped modems, server error, client problems, or other difficulties.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Error Message%ARAP-3-BADPAK : TTY [dec]: Bad packet type in arap_send_msg
Explanation Internal data structures are corrupted.
Recommended Action Check for abnormally high CPU usage.
Error Message%ARAP-4-CONFAILED : TTY [dec]: ARAP connection failed: [chars]
Explanation The ARA protocol client was denied access, probably because of a configuration problem on the server. The error message should indicate the problem. This message does not indicate access denials caused by the use of bad passwords.
Recommended Action Investigate the problem reported in the error message.
Error Message%ARAP-0-DEFAULT : TTY [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-5-INITCONFUSED : TTY [dec]: ARAP unexpected initialization packet [chars]
Explanation The startup negotiation between a client and the ARA protocol server fell out of order. If this message is received sporadically, it indicates line noise.
Recommended Action If this message recurs, reinstall the ARA client software.
Error Message%ARAP-6-LRPHASERROR : TTY [dec]: Received LT in CONNECTION PHASE
Explanation The router received an invalid packet during the ARA protocol connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Error Message%ARAP-6-MAXRESENDS : TTY [dec]
Explanation The router resent MNP4 packets the maximum number of times without receiving an acknowledgment.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Error Message%ARAP-6-MNP4RCVDISC : TTY [dec]: MNP4 input disconnect
Explanation The router has received a disconnect request from the remote Macintosh client.
Recommended Action No action is required.
Error Message%ARAP-6-MNP4T401 : TTY [dec]: T401 [dec] baud rate [dec]
Explanation The router has received a MNP4 connection request. The MNP4 acknowledgment timer value is also indicated.
Recommended Action No action is required.
Error Message%ARAP-4-NOEXTTACACS : TTY [dec]: arap TACACS is configured but extended TACACS is not.
Explanation TACACS authentication has failed because extended TACACS is not configured.
Recommended Action Configure extended TACACS.
Error Message%ARAP-2-NOLOG : TTY [dec]: Could not malloc log
Explanation Sufficient memory is not available for internal MNP4 logging.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-0-NOTNULLRESEND : TTY [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-0-NULLRESEND : TTY [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ARAP-5-PAKINVALID : TTY [dec]: ARAP invalid packet received
Explanation A corrupted packet has reached the ARA protocol code.
Recommended Action Check for excessive CPU usage or excessive line noise.
Error Message%ARAP-6-RCVGIANT : TTY [dec]: Rcv giant. dropping frame
Explanation The router has received an oversized MNP4 frame.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Error Message%ARAP-6-RCVNOPAK : TTY [dec]: Receive getbuffer failure. dropping frame
Explanation No buffer exists for an incoming packet.
Recommended Action Examine buffer usage statistics. Possibly more memory is required.
Error Message%ARAP-3-REMOTEERROR : TTY [dec]: arap input error
Explanation ARAP connection was terminated without a known cause.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ARAP-6-RESENDSLOW : TTY [dec]
Explanation The router repeated resending of MNP4 packets because the Macintosh client failed to acknowledge previously resent packets.
Recommended Action If this error message persists for several ARAP connections, report it to your Cisco technical support representative.
Error Message%ARAP-3-TIMEOUT : TTY [dec]: arap expected message timeout
Explanation The software timed out during the MNP4 link setup.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ARAP-6-TIMERERROR : TTY [dec]: MNP4 timeout error
Explanation The router is dropping the connection after doing the maximum number of resends.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
Error Message%ARAP-0-VSERROR : TTY [dec]: VS queued error
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ARAP-0-WAITBADMSG : TTY [dec]: arg msg bad [hex]
Explanation The router received an invalid packet during the ARAP MNP4 connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.
Error Message%ARAP-6-XTICKLE : TTY [dec]: exited user [chars]: Other side stopped answering ARAP tickles (mnp4 pak resent [dec] mnp4 pak sent [dec] last [dec] now [dec])
Explanation The router disconnected as the remote Macintosh client stopped sending ARAP tickle or data packets.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.
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-1-DFC_ERR : DFC [dec]: Detected PCI [chars] Error, CSR=[hex]
Explanation A PCI error that was caused by a hardware failure has been detected on the DFC. The Cisco IOS software will power down this DFC and clean up the associated system data structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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-1-OLD_FIRMWARE : [chars]
Explanation The specified component should have the latest hardware revision. If this hardware revision is not the latest, it must to be updated to the version specified in this message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, 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_DFC_INT : Unknown DFC interrupt: DFC slot no [dec], interrupt [dec]
Explanation An unknown DFC interrupt has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AS5400-1-UNKNOWN_INT : Unknown interrupt: interrupt [dec]
Explanation The system has detected an unknown interruption.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, 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.
AS5400_ENVM Messages
The following are Cisco AS5400 environmental monitor messages.
Error Message%AS5400_ENVM-1-CAN_NOT_POWER_ON_DFC : Can't power on DFC on slot [dec] for unknown reason.
Explanation An attempt to power on a DFC has failed.
Recommended Action Check the power plug to the DFC on the slot. If the DFC still fails to power on, unplug the DFC and run diagnostics on it.
Error Message%AS5400_ENVM-1-DFC_BUSYOUT : All DFCs are busy out due to board over temperature.
Explanation The system has become overheated. The DFCs have busied out so that they can cool and avoid being damaged.
Recommended Action Check the air conditioning in the area in which the Cisco AS5400 router is kept. Enter the show environment command to display temperature data. Compare the data with the temperature meter to verify the recovery. If the system fails, contact your Cisco technical support representative to replace the temperature sensor.
Error Message%AS5400_ENVM-1-DFC_POWER_DOWN : A DFC is powered down due to board over-temperature. Slot: [dec], Type: [chars]
Explanation The system has become overheated. A DFC has powered down to lower the temperature.
Recommended Action Check the air conditioning in the area in which the Cisco AS5400 router is kept. Enter the show environment command to display temperature data. Compare the data with the temperature meter to verify the recovery. If the system fails, contact your Cisco technical support representative to replace the temperature sensor.
Error Message%AS5400_ENVM-1-DFC_POWER_ON : A DFC is powered on due to board temperature cooling down. Slot: [dec], Type: [chars]
Explanation The temperature in the system has cooled. A DFC has powered on, and the system returns to normal functionality.
Recommended Action Enter the show environment command to display temperature data. Compare the data with the temperature meter to verify the recovery.
Error Message%AS5400_ENVM-1-DFC_UNBUSYOUT : All DFCs are unbusy out due to board temperature cooling down.
Explanation The system had become overheated and has now cooled. All DFCs return to normal functionality.
Recommended Action Enter the show environment command to display the temperature data. Compare the data with the temperature meter to verify the recovery.
Error Message%AS5400_ENVM-3-DISABLE_ENVM : AS5400 Environmental Monitor is disabled.
Explanation The Cisco AS5400 environmental monitor has been disabled. In certain situations, a configuration command can disable the Cisco AS5400 environmental monitor when necessary.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%AS5400_ENVM-1-DROP_FAN_MONITOR : Environmental Monitor of Fans is dropped.
Explanation The environmental monitoring of the fans has been dropped. This condition can occur if a temperature sensor at the inlet or outlet fails to work.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Also provide the system configuration information along with any other relevant information.
Error Message%AS5400_ENVM-1-DROP_TEMP_MONITOR : Environmental Monitor of Temperature is dropped.
Explanation Environmental temperature monitoring has been dropped. This condition can occur if all temperature sensors fail to work.
Recommended Action Copy the error message exactly as it appears, contact your Cisco technical support representative, and provide the representative with the gathered information. Also provide the system configuration information along with any other relevant information.
Error Message%AS5400_ENVM-3-ENABLE_ENVM : AS5400 Environmental Monitor is enabled.
Explanation The Cisco AS5400 environmental monitor has been enabled. In certain situations, a configuration command can enable Cisco AS5400 environmental monitor after it was disabled.
Recommended Action No action is required.
Error Message%AS5400_ENVM-3-FAN_FAIL : [chars] fail to work.
Explanation Some cooling fans have failed to work. This error was detected by the temperature delta between the inlet and outlet. A large delta indicates a fan failure.
Recommended Action Replace the fan as soon as possible. If this is not done, the system may shut itself down or fail to operate properly.
Error Message%AS5400_ENVM-3-FAN_OK : [chars] recovered to work.
Explanation Some cooling fans have recovered after a failure. This situation is detected by the temperature delta between the inlet and outlet. A small delta indicates a fan recovery.
Recommended Action Verify that the fan is working properly by checking all four fans. Enter the show environment command to display temperature delta data and verify the recovery.
Error Message%AS5400_ENVM-1-OIR_POWER_DOWN : Environmental monitor is trying to power down a DFC by simulating OIR removal. Slot: [dec], Type: [chars]
Explanation The system has become overheated. A DFC has powered down to lower the temperature. The environmental monitor uses OIR to power down the DFC.
Recommended Action Ensure that the room temperature is not too high and that air flow to the card is not blocked. Check the air conditioning surrounding the Cisco AS5400 router.
Error Message%AS5400_ENVM-1-OIR_POWER_ON : Environmental monitor is trying to power on a DFC by simulating OIR insertion. Slot: [dec], Type: [chars]
Explanation The temperature has cooled down inside the chassis after overheating. When the board temperature cools, a DFC is powered on and resumes functionality. The environmental monitor uses OIR to power on the DFC.
Recommended Action No action is required.
Error Message%AS5400_ENVM-1-OK_FAN_MONITOR : Environmental Monitor of Fans is recovered.
Explanation Environmental monitoring of the fans has recovered. This condition can occur if the temperature sensors at either the inlet or outlet recover. A console message is sent out, and the alarm is disabled. The fan state is set to normal.
Recommended Action Enter the show environment command to display temperature data. Compare the data with the temperature meter to verify the recovery.
Error Message%AS5400_ENVM-1-OK_TEMP_MONITOR : Environmental Monitor of Temperature is recovered.
Explanation Environmental monitor of temperature has recovered. This condition can occur if a temperature sensor has recovered to work.
Recommended Action No action is required.
Error Message%AS5400_ENVM-1-TEMP_SENSOR_FAIL : Temperature sensor #[dec] fails to work.
Explanation The health of each temperature sensor is monitored. There are three situations in which a sensor fails to operate normally: a sensor generates extraordinary data, such as higher than 200 degrees Celsius; a temperature change exceeds the maximum temperature in one minute, such as 25 degrees Celsius; or a temperature differential between sensors in the same box is greater than the limit, such as 25 degrees Celsius. When the failure of a temperature sensor is detected, ENVMON will set the temperature state of that sensor as disabled and send out console message. The temperature data from that sensor is ignored.
Recommended Action Enter the show environment command to display temperature data. Compare the data with the temperature meter. If the sensor fails, contact your Cisco technical support representative to replace the temperature sensor.
Error Message%AS5400_ENVM-1-TEMP_SENSOR_OK : Temperature sensor #[dec] recovers to work.
Explanation The health of each temperature sensor is monitored. There are three situations in which a sensor fails to operate normally: a sensor generates extraordinary data, such as higher than 200 degrees Celsius; a temperature change exceeds the maximum temperature in one minute, such as 25 degrees Celsius; or a temperature differential between sensors in the same box is greater than the limit, such as 25 degrees Celsius. Once the recovery of a temperature sensor is detected, ENVMON will set the state of that sensor as normal and send out console message. The temperature data from that sensor is read again.
Recommended Action Enter the show environment command to display temperature data and compare with the temperature meter to verify the recovery.
Error Message%AS5400_ENVM-1-TEMP_STATE : System detected that temperature is in [chars] condition.
Explanation The environmental monitor has detected a temperature change that is either a failure or a recovery.
Recommended Action Ensure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Check air conditioning and the surroundings of the Cisco AS5400 router. Contact your Cisco technical support representative for assistance if necessary.
ASPP Messages
The following are Asynchronous Security Protocol messages.
Error Message%ASPP-3-NOTTY : [chars]: Unable to set Rx/Tx tty async service hooks.
Explanation This message occurs only when ASP is configured. The serial interface using ASP is configured incorrectly or does not support asynchronous mode.
Recommended Action Verify that the correct hardware interface type is being used.