AAA through ADJ
AAA
| %AAA-3-BADMETHOD : Cannot process [chars] method [int] | |
|---|---|
| Explanation | A method list function encountered a method list that was unknown, or could not be handled. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-BADMETHODERROR : Cannot process [chars] method [chars] | |
|---|---|
| Explanation | A method list function encountered a method type that was unknown, or could not be handled. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %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 | Research the cause of the misconfiguration and attempt to correct it, otherwise take the following action. LOG_STD_ACTION |
| %AAA-2-FORKFAIL : Cannot fork process [chars] | |
|---|---|
| Explanation | Attempted to fork a process and failed. The reason could be either hardware or software. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-2-AAAMULTILINKERROR : [chars]([hex]): Acct db for Id [hex] absent | |
|---|---|
| Explanation | AAA internal error |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-SORTFAIL : [chars] :Peruser Could not sort the [chars] attributes | |
|---|---|
| Explanation | Sorting of the attributes received from AAA server failed. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-INVALIDATTRLIST : aaa attribute list CLI is not valid when configuring in sub-mode. | |
|---|---|
| Explanation | An internal error has occurred |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-ISDNINTF : [chars] [chars]: Can not apply configuration to ISDN channel: [chars] | |
|---|---|
| Explanation | Configuration can not be applied to individual ISDN channels. |
| Recommended Action | You need virtual-profiles and virtual-access interfaces to apply configuration to ISDN. Refer to the section on Configuring virtual profile by AAA Configuration in the Cisco IOS Dial Technologies Configuration Guide. |
| %AAA-3-AUTHORMLISTUNDEF : Authorization method list '[chars]' is not defined. Please define it. | |
|---|---|
| Explanation | A given method list was listed in a command without defining it first. The method list should be defined before use. |
| Recommended Action | Define the method list before using it. |
| %AAA-3-PARSEERR : Error([dec]) parser is unable to parse [chars] per-user command | |
|---|---|
| Explanation | All attempts to parse this per_user unconfigure command failed. The unconfigure command is called when an error occurs while configuring per-user commands, to revert back. The unconfiguration may fail due to parser or AAA error. |
| Recommended Action | The given unconfigure command was not executed. Switch on the debug peruser command and repeat the steps that caused the error. If you get the error, Report it to your technical support representative. |
| %AAA-6-ACCTSESSIDWRAP : Accounting-Session-ID [dec] exceeded max value allowed | |
|---|---|
| Explanation | Accounting-Session-ID value exceeded max value allowed. Now it is wrapping. |
| Recommended Action | This is informational only, not an error. |
| %AAA-3-PASSWDRESTRICTERR : AAA password restriction failed.- [chars] | |
|---|---|
| Explanation | The password/secret/key entered is not meeting the password restrictions configured |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-BADCURSOR : invalid cursor index [dec] max [dec] service [chars] protocol [chars] | |
|---|---|
| Explanation | A 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-MLIST_TOO_MANY_METHODS : method list '[chars]' | |
|---|---|
| Explanation | This is an internal software error. An AAA client attempted to add too many methods to a method list. |
| Recommended Action | This is an internal software error. Check bug tool-kit on Cisco web-site for the issue. If you didn't find one, Collect the error message and report it to your technical support representative. |
| %AAA-3-SG_INTERNAL_ERROR : server group '[chars]': [chars] | |
|---|---|
| Explanation | This is an internal software error in the AAA server group subsystem. |
| Recommended Action | This is an internal software error. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, collect all the information and error message, report it to your technical support representative. |
| %AAA-3-SG_DEADTIME_FORKFAIL : Failed to fork process for [chars]. | |
|---|---|
| Explanation | Quite likely, we ran out of memory. Other explanations are possible. |
| Recommended Action | If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, collect all the information and error message and report it to your technical support representative. |
| %AAA-3-SG_TESTPROC_FORKFAIL : Failed to fork process for [chars]. | |
|---|---|
| Explanation | Quite likely, we ran out of memory. Other explanations are possible. |
| Recommended Action | If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, Collect all the information and error message and report it to your technical support representative. |
| %AAA-3-MLIST_INTERNAL_ERROR : method list '[chars]': [chars] | |
|---|---|
| Explanation | This is an internal software error. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-SERVER_INTERNAL_ERROR : Server '[chars]': [chars] | |
|---|---|
| Explanation | This is an internal software error in the AAA server group subsystem. |
| Recommended Action | This is an internal software error. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, Collect all the information and error message and report it to your technical support representative. |
| %AAA-3-ATTRFORMATERR : Attribute with unknown format [dec] | |
|---|---|
| Explanation | An attribute was found with an invalid format. |
| Recommended Action | Attribute with unknown format in definition. Enable AAA debug and try to replicate the steps to get the message. If the meassage appears again, Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, Collect all the information and error message and report it to your technical support representative. |
| %AAA-3-NULLCURSOR : Null cursor | |
|---|---|
| Explanation | A 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-NOTABLE : AAA ID [int] | |
|---|---|
| Explanation | Resource failure. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-BADLIST : invalid list AAA ID [int] | |
|---|---|
| Explanation | A 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-6-BADHDL : invalid hdl AAA ID [int], hdl [hex], [chars] | |
|---|---|
| Explanation | A 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-IPILLEGALMSG : Invalid use of ip_pid([int]) | |
|---|---|
| Explanation | This error means a process sent an illegal message. |
| Recommended Action | If this message recurs. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, Collect all the information and error message and report it to your technical support representative. |
| %AAA-3-INVALIDPARM : invalid parameter was used when accessing AAA function | |
|---|---|
| Explanation | A AAA client tried to use a AAA function with an invalid parameter. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-BADMAGIC : Data structure failed magic number sanity check | |
|---|---|
| Explanation | A corrupted data structure has been found which was stored internally. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-BUFFER_OVERFLOW : Radius I/O buffer has overflowed | |
|---|---|
| Explanation | An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer. |
| Recommended Action | This is an internal software error. Check bug toolkit on Cisco website for the issue. If you didn't find one, Enter Show tech-support command, Collect all the information and error message and report it to your technical support representative. |
| %AAA-3-DROPACCTFAIL : Accounting record dropped, send to server failed: [chars] | |
|---|---|
| Explanation | An attempt to send an accounting record to a server failed. This happens when device exhaust all its retries and retransmission. The cause for this be the servers may not be operational or the NAS is not configured properly. |
| Recommended Action | Check the server , whether they are operational or not. Next check whether the device is configured properly. Refer to the server configuration section of the cisco IOS documentation. Finally, check that the NAS can communicate with the server. If the problem persist, Enter show running- config command, contact your cisco technical support representative and provide all the information gathered to the representative. |
| %AAA-3-AUTH_LOW_IOMEM : RADIUS process is unable to handle the requests due to insufficient I/O memory | |
|---|---|
| Explanation | RADIUS process unable to handle request due to insufficient IO memory. Hence returning failure. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-ACCT_LOW_PROC_MEM_TRASH : AAA unable to handle accounting requests due to insufficient processor memory and could be trashing the queued accounting records | |
|---|---|
| Explanation | Dropping the accounting request as there is no enough processor memory. Hence all queued accounting requests shall be trashed |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-ACCT_LOW_IO_MEM_TRASH : AAA unable to handle accounting requests due to insufficient I/O memory and could be trashing the queued accounting records | |
|---|---|
| Explanation | Dropping the accounting request as there is no enough I/O memory. Hence all queued accounting requests shall be trashed |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-ACCT_UNKNOWN_REASON_TRASH : AAA unable to handle accounting requests, reason unknown and could be trashing the queued accounting records | |
|---|---|
| Explanation | Dropping the accounting request, reason unknown. Hence all queued accounting requests shall be trashed |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-ACCT_LOW_MEM_UID_FAIL : AAA unable to create UID for incoming calls due to insufficient processor memory | |
|---|---|
| Explanation | Stop creating the AAA UID, due to LOW processor memory |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-LOW_MEM : [chars] process is unable to handle the incoming packet due to low memory | |
|---|---|
| Explanation | Please check the processor memory or IO memory. Most likely one is them has less available memory or worst case, both may have insufficient memory. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-ACCT_IOMEM_LOW : AAA ACCT process suspended : low I/O memory | |
|---|---|
| Explanation | AAA ACCT process has been suspended due to insufficient IO memory. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-5-USER_LOCKED : User [chars] locked out on authentication failure | |
|---|---|
| Explanation | User locked out since 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-5-LOCAL_USER_BLOCKED : User [chars] blocked for login till [chars] | |
|---|---|
| Explanation | User blocked since the number of authentication failures in the watch time exceeded the configured threshold. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-5-USER_UNLOCKED : User [chars] unlocked by [chars] | |
|---|---|
| Explanation | User unlocked by the system administrator. User is enabled to login to the system. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-5-USER_RESET : User [chars] failed attempts reset by [chars] | |
|---|---|
| Explanation | User's number of failed authentication attempts so far has been reset to zero |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-NULLVRF : Null vrf entry | |
|---|---|
| Explanation | A NULL VRF entry found while comparing the AAA VRF attributes. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-6-INVALIDROUTE : Syntax error in route statement: [chars] | |
|---|---|
| Explanation | Currently downloading route contains syntax error. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-HA_INIT_FAILURE : High availability initialization failure: [chars] | |
|---|---|
| Explanation | The AAA subsystem was unable to perform necessary high-availability related initialization. In the event of switchover to a standby device, sessions depending on high availability capabilities in the AAA subsystem will be forced to renegotiate. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-3-HA_INTERNAL_ERROR : High availability internal error for unique id [hex]: [chars] | |
|---|---|
| Explanation | The AAA subsystem was suffered an internal error. In the event of switchover to a standby device, sessions depending on high availability capabilities in the AAA subsystem may be forced to renegotiate. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-6-USER_BLOCKED : Enable view requires to be authenticated by non-none methods, Please use the appropriate method with the login authentication | |
|---|---|
| Explanation | None method authentication is not allowed in CLI |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAA-6-USER_FAIL_VIEW_AAA : User [chars] failed to enter view '[chars]'. | |
|---|---|
| Explanation | You have provided wrong User ID or Password for the requested view |
| Recommended Action | This message is for information only. No action is required. |
| %AAA-6-SKIP_MOH_ATTRIBUTE : Warning: Hardware idb is NULL. No Modem. MoH attribute can not be applied and it is Skipped for authorization. | |
|---|---|
| Explanation | To handle Modem-on-Hold attribute, we need connectivity with modems supporting V.92 modem standards. If there is no modem, there wouldn't be any tty, without which we cannot use MOH attributes. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
AAAA
| %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. In all cases, this indicates an internal software error, and that accounting information for a particular user session has been lost. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %AAAA-3-ACCTDUMP : dump of accounting data: | |
|---|---|
| Explanation | The data buffer overflowed while building the accounting packet as the total length of the attributes exceed the buffer size. Last 128 bytes of buffer data is dumped. |
| Recommended Action | LOG_STD_ACTIONCollect the logs with these debugs by using commands #debug aaa api,#debug aaa attr,#debug aaa accounting |
| %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 while the buffer overflow occured was logged. |
| Recommended Action | LOG_STD_ACTIONCollect the logs with these debugs by using commands #debug aaa api,#debug aaa attr,#debug aaa accounting |
| %AAAA-3-BADAUTHENSTR : Bad authentication data: [chars] | |
|---|---|
| Explanation | The data buffer overflowed while building the authentication packet as the total length of the attributes exceeded the buffer size. |
| Recommended Action | LOG_STD_ACTIONCollect the logs with these debugs by using the commands #debug aaa api,#debug aaa attr,#debug aaa authentication |
| %AAAA-3-NULUSR : accounting for null user | |
|---|---|
| Explanation | This message indicates an internal software error. 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 most likely reason for this error is 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, and report it to your technical support representative. |
| %AAAA-3-NULPORT : Could not establish port information | |
|---|---|
| Explanation | This message indicates an internal software error. AAA could not determine a valid port string based on the information provided to it via a client. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %AAAA-3-RELOGIN : sanity check in re-login [chars] to [chars] | |
|---|---|
| Explanation | A software or hardware error occurred. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %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 failed. |
| Recommended Action | Check that the server (TACACS+ or RADIUS) is operational. Next, check the NAS is configured properly. Finally, check that the NAS can communicate with the server |
| %AAAA-3-DROPACCTLOWMEM : Accounting record dropped due to low memory: [chars]-[chars] [chars] [chars] | |
|---|---|
| Explanation | An accounting record dropped due to low memory. |
| Recommended Action | Disable periodic accounting if it is on. Try to reduce the load on the router. |
| %AAAA-3-DROPACCTFULLQ : Accounting record dropped due to a full aaa accounting queue: [chars]-[chars] [chars] [chars] | |
|---|---|
| Explanation | An accounting record was dropped because there are too many accounting packets enqueued. |
| Recommended Action | Disable periodic accounting if it is on. The accounting queue may have grown to be large, which is usually due to a non-responsive AAA server. Use 'show radius statistics' or 'show tacacs' to see if the number of timeouts is increasing or if the response delay is unusually high. |
| %AAAA-3-DROPACCTQUEUEEXCEEDED : accounting record dropped, output record queue full: [chars]-[chars] [chars] [chars] | |
|---|---|
| Explanation | An accounting record was dropped. The record could not be enqueued because the number of records in the output queue has exceeded the system limit. |
| Recommended Action | Disable periodic accounting if it is on. [no] aaa accounting update newinfo periodic <interval> |
| %AAAA-3-MKTIMERFAIL : Failed to create periodic accounting timer for user [chars]. This user may not generate periodic accounting records. | |
|---|---|
| Explanation | Failed to malloc a timer struct for periodic accounting. |
| Recommended Action | Free up some memory and have user re-authenticate. |
| %AAAA-3-MKTIMERINVALID : Invalid request to create periodic accounting timer for user [chars]. Timer already exists. | |
|---|---|
| Explanation | Invalid client usuage of timer struct for periodic accounting. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %AAAA-3-PERIODICFORKFAIL : Failed to start periodic accounting process. Periodic accounting records may not be sent. | |
|---|---|
| Explanation | Failed to create the periodic accounting process. |
| Recommended Action | Free up some memory. |
| %AAAA-3-ACCTFORKFAIL : Failed to start accounting process. Accounting records may not be sent. | |
|---|---|
| Explanation | Failed to create the accounting process. |
| Recommended Action | Free up some memory. |
| %AAAA-3-AAAFORKFAIL : Failed to start AAA process. AAA requests may not be processed. | |
|---|---|
| Explanation | Failed to create the AAA process. |
| Recommended Action | Free up some memory. |
| %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. Please choose a different name for the method list. |
| Recommended Action | Pick a different method-list name, that is not also a method-name. |
| %AAAA-3-ILLEGALNAME : Illegal [chars] [chars] name [chars] rejected | |
|---|---|
| Explanation | A method-list name should not be the same as a method name. Please choose a different name for the method list. |
| Recommended Action | Pick a different method-list name, that is not also a method-name. |
| %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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-4-UNSUPWAITSTART : %% AAA: Unsupported option wait-start mapped to start-stop. | |
|---|---|
| Explanation | wait-start accounting is not supported. It is being mapped to start-stop |
| Recommended Action | wait-start accounting is not supported. It is being mapped to start-stop |
| %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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-BADARG : %% AAA: bad argument (%0#4x) | |
|---|---|
| Explanation | We tried to NVGEN a non-existent AAA command. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-BADSTATE : %% AAA: Bad state for [chars] list name ([dec]) | |
|---|---|
| Explanation | A AAA method list is neither default nor named. This is bad. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %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 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) . If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case) , or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-TIMERNOPER : AAA/ACCT/TIMER: No periodic update but timer set. | |
|---|---|
| Explanation | We are trying to free a timer, but the update method is not PERIODIC, and so no timer should exist. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-PERNOTIMER : AAA/ACCT/TIMER: Periodic update but no timer. | |
|---|---|
| Explanation | We are trying 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-OVERWRITE : Overwrote internal buffer space [chars] | |
|---|---|
| Explanation | An internal software error. |
| Recommended Action | Report to tac@cisco.com. |
| %AAAA-3-DLRFORKFAIL : Failed to fork process for [chars]. | |
|---|---|
| Explanation | Quite likely, we ran out of memory. Other explanations are possible. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-STRCREATE : str_create overwrote its internal buffer. | |
|---|---|
| Explanation | An internal buffer, used to assemble a string, was exceeded, thus possibly corrupting other memory. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-6-ACCTSTART : [chars] | |
|---|---|
| Explanation | A AAA accounting start message. |
| Recommended Action | This information is for information only. |
| %AAAA-6-ACCTSTOP : [chars] | |
|---|---|
| Explanation | A AAA accounting stop message. |
| Recommended Action | This information is for information only. |
| %AAAA-6-ACCTWATCH : [chars] | |
|---|---|
| Explanation | A AAA accounting watchdog/update message. |
| Recommended Action | This information is for information only. |
| %AAAA-6-ACCTLOCAL : Username: [chars] Privilege level: [dec] Command: [chars] | |
|---|---|
| Explanation | AAA local accounting log message |
| Recommended Action | This information is to store buffered logs locally and send to SYSLOG server |
| %AAAA-3-SUBTYPE : Bad Subtype [dec] for [chars] ([dec]) | |
|---|---|
| Explanation | An internal software error. |
| Recommended Action | Report to tac@cisco.com. |
| %AAAA-3-NOLIST : [chars]: no method list-name. | |
|---|---|
| Explanation | An internal software error. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-INVSTATE : [chars] AUTHOR/[chars]: Internal state is invalid: astruct 0x[int]struct [hex] | |
|---|---|
| Explanation | One of the two mentioned data-structures is not set, but is needed here. This is an internal software error. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-LISTCREATE : The list [dec] for [chars] is NULL. This should never be. | |
|---|---|
| Explanation | One of the method-lists, created at startup, wasn't created. This may cause a reload |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-NOSERV : No name for servergroup in method [chars] | |
|---|---|
| Explanation | An internal error has occurred |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %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 defining it first. Server-groups should be defined before use. |
| Recommended Action | Define the server-group before using it. |
| %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 doesn't support the configured aaa action. |
| Recommended Action | Use a tacacs+ server-group. |
| %AAAA-4-SERVNORADIUS : The server-group [chars] is not a radius server group. Please define [chars] as a radius server group. | |
|---|---|
| Explanation | The protocol used by the server-group doesn't support the configured aaa action. |
| Recommended Action | Use a radius server-group. |
| %AAAA-4-DNISGPUNDEF : Warning: DNIS group [chars] is not defined. | |
|---|---|
| Explanation | The DNIS group was used without defining it first. It should be defined before use. |
| Recommended Action | Define the DNIS group before using it. |
| %AAAA-3-NOREG : [chars] method [dec] has no registry! | |
|---|---|
| Explanation | An internal error has occurred |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-BADREG : Illegal registry call. | |
|---|---|
| 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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-NOSG : No server-group passed through parser. | |
|---|---|
| Explanation | An internal error has occurred |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-6-SERVERMSG : [chars] [chars]: [chars] | |
|---|---|
| Explanation | This message was passed to the NAS from the AAA server |
| Recommended Action | No action need be taken, but the message may contain usefull information regarding some event on the server |
| %AAAA-6-ADMINMSG : [chars] [chars]: [chars] | |
|---|---|
| Explanation | This administrative message was passed to the NAS from the AAA server |
| Recommended Action | No action need be taken, but the message may contain usefull information regarding some event on the server |
| %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 | Please pick a different server-group name. |
| %AAAA-4-NOSERVER : Warning: Server [chars] is not defined. | |
|---|---|
| Explanation | The given server is not on the master-list, and should be defined, or unexpected things might happen. |
| Recommended Action | Please define the server on the appropriate master-list as soon as possible. |
| %AAAA-4-BADSGNAME : Bad server-group name [chars] (type [chars]). | |
|---|---|
| Explanation | The given server-group name either doesn't exist or the given type does not match the defined server-group. |
| Recommended Action | Verify that the group exists and has the same type. |
| %AAAA-4-BADSGTYPE : Server-group [chars] is not of type [chars]. | |
|---|---|
| Explanation | The given server-group name does not match the specified type |
| Recommended Action | Verify that the group exists and has the same type. |
| %AAAA-4-SERVNOGRP : Warning: Server [IP_address]:[dec],[dec] is not part of server group [chars]. | |
|---|---|
| Explanation | The server does not belong to the specified server group |
| Recommended Action | Please check that the specified server belongs to the server group |
| %AAAA-3-NOADMINPROC : [chars] | |
|---|---|
| Explanation | Administrative process has been enabled but somehow could not run |
| Recommended Action | |
| %AAAA-3-INTERNAL_ERROR : [chars] | |
|---|---|
| Explanation | This is an internal software error. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-3-SGDUPFREE : Duplicate free of server group [hex] | |
|---|---|
| Explanation | This is an internal software error. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-4-NOCACHEPROC : The aaa cache process is not created. Please configure aaa cache profile first | |
|---|---|
| Explanation | Cache was listed in a method-list without defining it first. Cache profile should be defined before use. |
| Recommended Action | Define the cache profile before using it. |
| %AAAA-3-INVALIDATTRLIST : aaa attribute list CLI is not valid when configuring in sub-mode. | |
|---|---|
| Explanation | An internal error has occurred |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AAAA-4-CLI_DEPRECATED : [chars] | |
|---|---|
| Explanation | CLI deprecated. New CLI to be used |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
AC
| %AC-3-AC_WS_REGISTER : L2VPN WS registration failed for [chars] | |
|---|---|
| Explanation | An error was encountered when attempting to register the specified Attachment Circuit type with the Layer 2 Virtual Private Network Wire Service facility. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AC-3-AC_SANITY : [chars] | |
|---|---|
| Explanation | A unexpected sanity check failed during Attachment Circuit processing. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AC-3-L2SS_NULL_CONTEXT : Encountered a NULL context in [chars] | |
|---|---|
| Explanation | Encountered a NULL context in L2SS Manager. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AC-3-L2SS_WRONG_KEYS : Wrong set of keys in [chars] message | |
|---|---|
| Explanation | SIP sends a wrong set of keys to L2SS Manager. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AC-3-L2SS_UNEXPECTED : Received unexpected [chars] message | |
|---|---|
| Explanation | L2SS received unexpected message. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AC-3-L2SS_BAD_HANDLE : Corrupted L2SS handle [[hex]]. | |
|---|---|
| Explanation | An internal L2SS Manager occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AC-3-ACMGR_XDM_CREATE : Failed to create XDM - rc [int] | |
|---|---|
| Explanation | Attachment Circuit Manager was unable to create a Dispatch Manager instance for event handling. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AC-3-ACMGR_INVALID_MSG : Received [chars] | |
|---|---|
| Explanation | Attachment Circuit Manager receives invalid message. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AC-3-ACMGR_MISSED_CIRCUIT : Circuit info missing in [chars] message. | |
|---|---|
| Explanation | AC Manager received message with missing circuit info |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %AC-3-ACMGR_INVALID_HDL : Received invalid [chars] handle | |
|---|---|
| Explanation | Attachment Circuit Manager receives invalid handle. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
ACCESS_IE
| %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. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
ACCESS_SESSION
| %ACCESS_SESSION-3-TRACE_INIT_FAIL : Initialization failed with code: [dec] | |
|---|---|
| Explanation | Failed to initialize access-session trace. |
| Recommended Action | No action is required. |
| %ACCESS_SESSION-3-TRACE_REG_FAIL : Component [chars] registration failed. Error code: [dec] | |
|---|---|
| Explanation | Component failed to register with access-session trace |
| Recommended Action | No action is required. |
ACCESS_SESSION_TRACE
| %ACCESS_SESSION_TRACE-3-TRACE_INIT_FAIL : | |
|---|---|
| Explanation | Failed to initialize access-session trace. |
| Recommended Action | Review smd logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. |
| %ACCESS_SESSION_TRACE-3-TRACE_REG_FAIL : | |
|---|---|
| Explanation | Component failed to register with access-session trace |
| Recommended Action | Review smd logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. |
ACE
| %ACE-3-INITFAIL : [chars]: initialization failed ([chars]) | |
|---|---|
| Explanation | ACE initialization sequence failed. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-3-TRANSERR : [chars]: [chars] trans [hex]; opcode [hex]; param [hex]; error [hex]; retry cnt [dec] | |
|---|---|
| Explanation | An error occured in the indicated control transaction. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-6-SWITCHOVER : VPN-SM switchover: [dec]/[dec] has been [chars] [dec]/[dec] | |
|---|---|
| Explanation | A blade to blade switcover has occurred. System performance is not affected. |
| Recommended Action | System performance is not affected. No customer action is necessary. |
| %ACE-3-TRANSERR_RL : [chars]: [chars] trans [hex]; opcode [hex]; param [hex]; error [hex]; retry cnt [dec] | |
|---|---|
| Explanation | An error occured in the indicated control transaction. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-3-TRANSTO : [chars]: [chars] trans [hex]; opcode [hex]; param [hex]; too many retries | |
|---|---|
| Explanation | An error occured in the indicated control transaction. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-3-TRANSNAK : [chars]: [chars] NAK trans [hex]; opcode [hex]; param [hex] | |
|---|---|
| Explanation | An negative acknowledge occured in the indicated control transaction. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-3-NOMORETID : [chars]: out of [chars] transactions | |
|---|---|
| Explanation | Transaction pool for the indicated transaction type was exhausted. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-3-INVTID : [chars]: [chars] of invalid [chars] trans id [dec] | |
|---|---|
| Explanation | An invalid transaction ID of for the indicated transaction type was encountered |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-3-HAPITRUNC : [chars]: Received truncated HAPI message (tlen=[dec], actual=[dec]) | |
|---|---|
| Explanation | The received ACE control packet was smaller than the size field indicated |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-6-UNEXP_OUTBOUND_IPSEC : [chars]: received unexpected IPsec packet: src IP: [IP_address]; dst IP: [IP_address]; firsthop/lasthop = [chars]/[chars] (count=[dec]) | |
|---|---|
| Explanation | An IPsec packet was unexpectedly forwarded to the RP |
| Recommended Action | If this message was seen in the context of the router booting, enabling the hardware crypto accelerator, or with an invalid peer IP address then this message is normal and can be safely ignored. Otherwise, please copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-6-UNEXP_INBOUND_IPSEC : [chars]: received unexpected IPsec packet: src IP: [IP_address]; dst IP: [IP_address]; (count=[dec]) | |
|---|---|
| Explanation | An IPsec packet was unexpectedly forwarded to the RP |
| Recommended Action | If this message was seen in the context of the router booting, enabling the hardware crypto accelerator, then this message is normal and can be safely ignored. Otherwise, please copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-3-CRASHDUMPSTART : [chars]: crashdump retrieval initiated to file [chars] | |
|---|---|
| Explanation | The ACE crashed and was rebooted. Upon reboot, a crashdump file was detected and uploaded to the sup-bootflash filesystem. |
| Recommended Action | Report the crash and transfer the crashdump file to your technical support representative. |
| %ACE-6-CRASHDUMPEND : [chars]: crashdump retrieval complete | |
|---|---|
| Explanation | The ACE crashed and was rebooted. Upon reboot, a crashdump file was detected and uploaded to the sup-bootflash filesystem. |
| Recommended Action | Report the crash and transfer the crashdump file to your technical support representative. |
| %ACE-3-CRASHDUMPERR : [chars]: crashdump retrieval error: [chars] [chars] | |
|---|---|
| Explanation | An error occurred during crashdump file retrieval from ACE. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-6-BOOTMSGINFO : [chars]: boot info: [chars] | |
|---|---|
| Explanation | The ACE completed booting, but with a non-zero informational status code. This does not indicate an error and ACE will run normally. |
| Recommended Action | No action is necessary. |
| %ACE-3-BOOTMSGERR : [chars]: boot error: [chars] | |
|---|---|
| Explanation | The ACE completed booting, but with an error status code. ACE will not operate and it will not register with the crypto subsystem. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-3-OUTOFRES : Too many [chars] in the system. Cannot allocate a new one | |
|---|---|
| Explanation | All VPN-accelerator resources of a particular are in used and thus this allocation request fails. |
| Recommended Action | Remove the cryptomap set from the interface. Reduce the number of that resource in the system. For ACL, reduce the number of ACL permit ACE in the system. For cryptomap, reduce the number of cryptomaps in the system. For SPD and SPD map, reduce the number of interface with cryptomap set attached. |
| %ACE-2-INTTABOPERR : Internal [chars] table error: [chars] | |
|---|---|
| Explanation | Internal table operation fails. This means the state of the module is mostly like inconsistent. |
| Recommended Action | Contact your technical support representative |
| %ACE-2-CRYPTOENGERR : Crypto engine error: [chars] ([dec]) | |
|---|---|
| Explanation | A crypto engine operation did not complete. This error condition can indicate that the crypto engine cannot bind or unbind an interface to a crypto engine. It can also indicate that the crypto engine cannot query an interface ID. |
| Recommended Action | Remove the cryptomap set from the interface by issuing no crypto map command. Then reattach the cryptomap set to the interface using crypto map command. Although removing and reattaching the crypto map might fix the cryptographic engine operation failure, report the failure to your technical support representative along with the sequence of commands that lead to the failure. |
| %ACE-6-INFO : [chars]: [chars] | |
|---|---|
| Explanation | This is informational message from ACE |
| Recommended Action | This is informational message from ACE. This occurs in normal operation. |
| %ACE-3-OUTOFID_RL : Too many [chars] IDs in the system. Cannot allocate a new one | |
|---|---|
| Explanation | All the IDs of the specified type are in use |
| Recommended Action | Reduce the traffic load, number of IPSec tunnels and/or frequency of re-key. If this message was seen under light loading conditions, then copy the error message exactly as it appears, and report it to your technical support representative. |
| %ACE-3-NOENGINESLOT : Interface [chars] has no crypto engine slot | |
|---|---|
| Explanation | An IKE SA was requested for a given interface, but no crypto engine slot was assigned to that interface |
| Recommended Action | Configure the interface in question with the `crypto engine [sub]slot' command |
| %ACE-3-CEAL_REGISTRATION : ACE [chars] failed to register. | |
|---|---|
| Explanation | The ACE failed to register with CEAL |
| Recommended Action | Reset the hw module |
| %ACE-4-BV_IDMGR_DESTROY : ACE failed to destroy [chars] ID manager. Leaking memory. | |
|---|---|
| Explanation | The ACE failed to destroy memory space for ID management. |
| Recommended Action | Copy the error message exactly as it appears, and report it to your technical support representative. |
ACL
| %ACL-3-UNEXPECTED_STATE : type [dec], int [chars] [chars]put, w0: [hex], w1: [hex] | |
|---|---|
| Explanation | An error has occurred in the setup of ACL hardware. |
| Recommended Action | LOG_STD_ACTION |
| %ACL-3-UNEXPECTED_PKT_TYPE : type [dec], int [dec] [chars]put | |
|---|---|
| Explanation | ACL logging has encountered unexpected pkt type. |
| Recommended Action | LOG_STD_ACTION |
ACL_ERRMSG
| %ACL_ERRMSG-4-UNLOADED : [chars] [chars] [chars] ACL on interface [chars] could not be programmed in hardware and traffic will be dropped. | |
|---|---|
| Explanation | The configuration is too large dropped will be dropped on this interface. |
| Recommended Action | Allocate more space to the relevant section of the TCAM and reboot, or else use a simpler configuration. If possible, use the same ACLs on multiple interfaces. |
| %ACL_ERRMSG-4-HASH_FULL : [chars] [chars] [chars] ACL on cell [chars] could not be programmed in hardware, SGACL table is full. | |
|---|---|
| Explanation | The configuration is too large. |
| Recommended Action | You have exceeded the system limit of SGACL cells, use a simpler configuration which uses less SGACL cells. |
| %ACL_ERRMSG-4-HASH_ERROR : [chars] [chars] [chars] ACL on cell [chars] could not be found. | |
|---|---|
| Explanation | The configuration is unknown. |
| Recommended Action | There is no SGACL Cell with this configuration found. |
| %ACL_ERRMSG-4-PROGRAM_FAILED : [chars] [chars] [chars] ACL on [chars] programming failed in hardware. | |
|---|---|
| Explanation | The configuration is too large. |
| Recommended Action | You have exceeded the system limit of entries, use a simpler configuration which uses less entries. |
| %ACL_ERRMSG-6-RELOADED : [chars] [chars] [chars] ACL on interface [chars] has now been loaded into the hardware. | |
|---|---|
| Explanation | The configuration that previously was unable to fit into the hardware will now fit and has been programmed for this interface. |
| Recommended Action | No action required, informational only. |
| %ACL_ERRMSG-6-REMOVED : The [chars] [chars] [chars] ACL configuration that was previously unloaded has been removed from interface [chars]. | |
|---|---|
| Explanation | The configuration that was previously unloaded, because of lack of space, has been removed. |
| Recommended Action | No action required, informational only. |
| %ACL_ERRMSG-3-ERROR : [chars] [chars] [chars] ACL [chars] configuration could not be applied on [chars]. | |
|---|---|
| Explanation | The given ACL configuration could not be applied to hardware. |
| Recommended Action | Find out more about the error by using the show platform software trace messages fed command. |
| %ACL_ERRMSG-3-CHANGE_ERROR : [chars] [chars] [chars] ACL [chars] change configuration could not be updated on all installed interfaces. | |
|---|---|
| Explanation | The given ACL change configuration could not be applied to all installed policies in hardware. |
| Recommended Action | Find out more about the error by using the show platform software trace messages fed command. |
| %ACL_ERRMSG-6-PACL_INFO : Logging is not supported for PACL. | |
|---|---|
| Explanation | The ACL logging is not supported on port interface. |
| Recommended Action | No action is needed. |
| %ACL_ERRMSG-6-GACL_INFO : Logging is not supported for GACL. | |
|---|---|
| Explanation | The ACL logging is not supported for client/group ACL. |
| Recommended Action | No action is needed. |
| %ACL_ERRMSG-3-SGACL_ERROR : SGACL configuration could not be changed on [chars]. | |
|---|---|
| Explanation | An error occurred during SGACL configuration change, all SGACLs have been removed from cell. |
| Recommended Action | User needs to manually remove the cell configuration and attempt to re-apply when resources have been freed. |
ADJ
| %ADJ-3-BADMACALIGN : adjacency mac string end [hex] not [chars] aligned | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-BADMAGIC : adjacency [chars] is followed by bad magic | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ALLOCATEONDOWN : Allocating adj when adj subsystem down | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ALLOCATEFAIL : Failed to allocate an adjacency | |
|---|---|
| Explanation | An internal software error occurred. This is probably because not enough memory was available. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-BOARDENCAP : Generation of encapsulation string for [chars] failed | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ILLEGALARGS : Illegal arguments - [chars] | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-STATETRANSITION : Unexpected state transition from [chars] to [chars] | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-NOFIBIDB : CEF Interface not found - [chars] | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-LCXDRCLIENT : Adjacency distribution client: [chars] | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-RPXDRCLIENT : Adjacency distribution client: [chars] | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-BROKERINITFAIL : Failed to initialise adjacency RP broker facility | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-SBINITFAIL : Failed to initialise adjacency subblock facility | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ILINITFAIL : Failed to initialise adjacency interest list facility | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-BUNDLES : Adj bundles: [chars] | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ILALLOCATEFAIL : Failed to allocate an adjacency interest list subblock | |
|---|---|
| Explanation | An internal software error occurred. This is probably because not enough memory was available. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ILDEALLOCATEFAIL : Failed to deallocate an adjacency interest list subblock | |
|---|---|
| Explanation | An internal software error occurred. This is probably because not enough memory was available. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-DBGFILTERALLOCATEFAIL : Failed to allocate an adjacency debug filter block | |
|---|---|
| Explanation | An internal software error occurred. This is probably because not enough memory was available. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ADJMGRALLOCATEFAIL : Failed to allocate an adjacency summary event block | |
|---|---|
| Explanation | An internal software error occurred. This is probably because not enough memory was available. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ADJGENALLOCATEFAIL : Failed to allocate memory [chars] | |
|---|---|
| Explanation | An internal software error occurred. This is probably because not enough memory was available. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ADJGENDEALLOCATEFAIL : Failed to deallocate memory [chars] | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ADJMGRREFRESHFAIL : Failed to dispatch a refresh adjacency summary event | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ADJMGRDISPATCHFAIL : Failed to enqueue an adjacency summary event block | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-5-PARENT : Midchain parent maintenance for [chars] - [chars] | |
|---|---|
| Explanation | A midchain adjacency failed to stack onto output chain because a loop was detected. Traffic through the adjacency will be dropped until the adj is restacked. This condition is typically transient and is rectified by the control plane driving stacking. E.g. if an ip tunnel destination resolves through the tunnel transiently this message would appear. The situation would be rectified either by learning the tunnel destination through an interface other than the tunnel itself or by bringing the tunnel down. Monitor 'show adjacency internal' to determine if the problem has been resolved. |
| Recommended Action | No action is required. |
| %ADJ-3-ADJSTACK2 : Adj stack2 error [chars]: [chars] | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-5-ADJISSUINCOMPATIBLE : All or part of adjacency message for [chars] not sent to incompatible CEF instance for [chars] | |
|---|---|
| Explanation | The adjacency is not distributed in whole to the remote CEF instance. This may impact traffic forwarding on remote CEF instance |
| Recommended Action | No action is required. |
| %ADJ-3-BADADDRTYPE : Using an unsupported address type [dec] when trying to add/delete/modify/find an adjacency | |
|---|---|
| Explanation | An internal software error occurred. An attempt to reference an adjacency with an unsupported address type has been made. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-BADADDRLEN : Zero address length detected distributing adj [chars] | |
|---|---|
| Explanation | An internal software error occurred. An attempt to reference an adjacency with an unsupported address type has been made. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-BADLINKTYPE : Using an unsupported linktype [chars] when trying to add/delete/modify/find an adjacency | |
|---|---|
| Explanation | An internal software error occurred. An attempt to reference an adjacency with an unsupported address type has been made. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-BADMACALIGN2 : Adjacency mac string for [chars] not byte aligned, offset [hex], length [hex] | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-MACOVERFLOW : Adjacency mac address for [chars] overflowed by [dec] bytes | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-5-RESOLVE_REQ_FAIL : Adj resolve request failed for [chars] on [chars] | |
|---|---|
| Explanation | The source (e.g. ARP or ND) could not resolve the address. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-MACSTRING_PD_ERROR : Platform request for header type [chars] from adjacency [chars] [chars][chars] | |
|---|---|
| Explanation | An internal software error occurred. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ISSU_REG : ISSU client [chars] ([dec]), entity [dec], failed ISSU registration: [chars] | |
|---|---|
| Explanation | ISSU negotiation failed for this XDR client. |
| Recommended Action | This error indicates a coding problem. It is an error that will occur every time this image is run, and requires a code change to fix it. |
| %ADJ-3-CONNID_POOL_EXHAUSTED : Pool of connection ids is fully utilized. It may not be possible to encode new sets of extended keys. | |
|---|---|
| Explanation | Either there are too many unique sets of extended keys in the system, or ids have been leaking. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-CONNID_INVALID_KEY : Unexpected connection-id parameter: Expecting [chars] when encoding [chars] | |
|---|---|
| Explanation | An application has provided an invalid key for computing a connection-id. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-CONNID_TREE_OP_FAIL : Tree [chars] failed for [chars] for id [int] (connid [int]) | |
|---|---|
| Explanation | A tree operation failed for the connection-id manager. An inability to correctly construct a tree will have negative consequences for the system. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-CONNID_INVALID : Connection id [int] not recognized ([chars]) | |
|---|---|
| Explanation | A supplied connection id did not exist in the managed id database. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-CONNID_INCOMPATIBLE_ID : Connection id [int] could not be transformed: [chars] | |
|---|---|
| Explanation | A connection id could not be transformed from a lower revision. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-CONNID_TREE_MISMATCH : Supplied connid [int] and extended keys ([chars]) do not match database: [int] ([chars]) | |
|---|---|
| Explanation | An adjacency has a connection id and extended keys mapping that doesn't match what's in the managed connection id database. This will likely result in a rejected adjacency update or sync. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-ADJ_XKEYS : Adj extended keys error [chars]: [chars] | |
|---|---|
| Explanation | An initialization error occurred for extended keys. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
| %ADJ-3-XKEYS_XDR_LEN : Expected [int] bytes of extended adjacency keys: decoded [int] bytes | |
|---|---|
| Explanation | The XDR message was incorrectly formatted and may contain bad xkey data. |
| Recommended Action | Copy the error message exactly as it appears on the console or in the system log. Perform a search of the Bug Toolkit (https://bst.cloudapps.cisco.com/bugsearch/). If you still require assistance, open a case with the Technical Assistance Center via the Internet (https://mycase.cloudapps.cisco.com/case), or contact your Cisco technical support representative and provide the representative with the gathered information. |
Feedback