AAA through COMPILED_ACL

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. 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-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.


%ACE-6-SWITCHOVER : VPN-SPA 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-6-UNEXP_INBOUND_IPSEC : [chars]: received unexpected IPsec packet: src IP: [chars]; dst IP: [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, 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-OUTOFID_RL : Too may [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.


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-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.


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.


AGGMGR through APM

AGGMGR

%AGGMGR-0-NO_SPACE : No space left for creator [chars] to add data item to agg list (items [dec] max [dec] remaining [dec])
Explanation An attempt was made to add an item to an aggregation list that had just been successfully created but for some reason the add failed. This situation should never occur. If it does occur, then it is the result of a program error which would be found during development and considered an internal error. There is no work around.
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.


ALARM

%ALARM-3-NOMEM : OUT of Memory: [chars]
Explanation
Recommended Action


%ALARM-3-CLEAR : [chars] [chars] [chars] [chars] [chars]
Explanation
Recommended Action


%ALARM-6-ENTITY_INFO : [chars] [chars] [chars] [chars] [chars]
Explanation Entity alarm assertion or deassertion information.
Recommended Action No action is required.


ALG_COM

%ALG_COM-3-ALG_COND_DEBUG_REG_FAILED : [chars]
Explanation
Recommended Action


%ALG_COM-3-CHUNK_CREATE_FAIL : [chars]
Explanation A request to create a chunk failed
Recommended Action LOG_STD_ACTION


%ALG_COM-3-CHUNK_EXTEND_FAIL : [chars]
Explanation A request to create a chunk failed
Recommended Action LOG_STD_ACTION


%ALG_COM-3-IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION


%ALG_COM-3-ALG_REGISTER_FAILED : [dec]
Explanation ALG registration failed.
Recommended Action LOG_STD_ACTION


ALG_PROXY

%ALG_PROXY-3-PROXY_MEM_REQ_FAILED : ALG IPC subtype: [dec]
Explanation Requesting more memory failed.
Recommended Action LOG_STD_ACTION


%ALG_PROXY-3-PROXY_MEM_EXTEND_FAILED : ALG IPC subtype: [dec]
Explanation Extending memory failed.
Recommended Action LOG_STD_ACTION


%ALG_PROXY-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Invalid IPC message length.
Recommended Action LOG_STD_ACTION


%ALG_PROXY-4-PROXY_IPC_INVALID_MSG : [dec]
Explanation Invalid IPC message subtype.
Recommended Action LOG_STD_ACTION


%ALG_PROXY-3-PROXY_IPC_FAIL : rc= [dec], MSGDEF_LIMIT_MEDIUM
Explanation The ALG proxy has experienced a failure when trying to send an IPC
Recommended Action LOG_STD_ACTION


ALIGN

%ALIGN-3-CORRECT : Alignment correction made at [hex] [chars]ing [hex]
Explanation A software component within the router needs memory optimization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ALIGN-3-FULL : Alignment log is full - no new entries will be recorded
Explanation The router identified more software components in need of memory optimization than it can record.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ALIGN-3-SPURIOUS : Spurious memory access made at [hex] reading [hex]
Explanation An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show alignment command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show alignment output, call your Cisco technical support representative and provide the representative with the gathered information.


%ALIGN-3-TRACE : -Traceback= [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation A trace that shows where the previous ALIGN error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ALIGN-3-TRACEX : [chars]
Explanation A trace that shows where the previous ALIGN error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ALIGN-3-READEXCEPTION : Warning : read accees failed at [chars], still continuing
Explanation In ls1010 read access failures do not make the box reload. They can be caused by either a bad register value in the asp ver 3.3 or earlier or a real problem in the hardware
Recommended Action If the ASP version is 3.3 or more, report it to your technical support representative.


%ALIGN-3-CORRECT : Alignment correction made at [chars] [chars]ing [hex]
Explanation A software component within the router needs memory optimization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ALIGN-3-CORRECT_SO : Alignment correction made at [chars] [chars]ing [chars]
Explanation A software component within the router needs memory optimization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ALIGN-3-SPURIOUS : Spurious memory access made at [chars] reading [hex]
Explanation An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show alignment command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show alignment output, call your Cisco technical support representative and provide the representative with the gathered information.


%ALIGN-3-SPURIOUS_SO : Spurious memory access made at [chars] reading [chars]
Explanation An attempted but illegal access to a low memory address within a software component in the router has been temporarily blocked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show alignment command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show alignment output, call your Cisco technical support representative and provide the representative with the gathered information.


%ALIGN-3-TRACE : -Traceback= [chars]
Explanation A trace that shows where the previous ALIGN error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%ALIGN-3-TRACE_SO : -Traceback= [chars]
Explanation A trace that shows where the previous ALIGN error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


ALPS

%ALPS-3-ALPSFAIL : ALPS: Assertion failed: [chars]
Explanation An internal software error has occurred.
Recommended Action LOG_STD_ACTION


%ALPS-5-PEER_CONN_ID_CHANGE : Peer ([IP_address], [chars]) ID modified to ([IP_address], [chars]).
Explanation An ALPS peer connection identifier has changed.
Recommended Action LOG_STD_NO_ACTION


%ALPS-5-PEER_OPEN : Peer ([IP_address], [chars]) changed state to open.
Explanation An ALPS peer connection is now open.
Recommended Action LOG_STD_NO_ACTION


%ALPS-5-PEER_CLOSED : Peer ([IP_address], [chars]) changed state to closed.
Explanation An ALPS peer connection is now closed.
Recommended Action LOG_STD_NO_ACTION


%ALPS-5-PEER_CLOSED_DYNAMIC_INACTIVITY : Peer ([IP_address], [chars]) closed due to inactivity.
Explanation An ALPS peer connection is now closed due to inactivity.
Recommended Action LOG_STD_NO_ACTION


%ALPS-6-PEER_OPEN_FAIL : Peer ([IP_address], [chars]) open failed, rsn = [chars]
Explanation An ALPS peer connection attempted to open, but failed to open.
Recommended Action LOG_STD_NO_ACTION


%ALPS-6-PEER_BUSY_START : Peer ([IP_address], [chars]) has entered a congested state.
Explanation An ALPS peer connection is experiencing congestion.
Recommended Action LOG_STD_NO_ACTION


%ALPS-6-PEER_BUSY_END : Peer ([IP_address], [chars]) has exited a congested state.
Explanation An ALPS peer connection is no longer experiencing congestion.
Recommended Action LOG_STD_NO_ACTION


%ALPS-7-PEER_DROPS_MAX_SIZE_EXCEEDED : Threshold exceeded for maximum size exceeded drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops due to maximum size exceeded exceeds the ALPS peer threshold value.
Recommended Action LOG_STD_NO_ACTION


%ALPS-7-PEER_DROPS_VERSION_MISMATCH : Threshold exceeded for version mismatch peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops due to version mismatch exceeds the ALPS peer threshold value.
Recommended Action LOG_STD_NO_ACTION


%ALPS-7-PEER_DROPS_QUEUE_OVERFLOW : Threshold exceeded for TCP Queue overflow peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops due to queue overflow exceeds the ALPS peer threshold value.
Recommended Action LOG_STD_NO_ACTION


%ALPS-7-PEER_DROPS_PEER_UNREACHABLE : Threshold exceeded for peer unreachable peer drops for peer ([IP_address], [chars]).
Explanation The number of ALPS peer drops due to a peer unreachable condition exceeds the ALPS peer threshold value.
Recommended Action LOG_STD_NO_ACTION


%ALPS-5-CIRCUIT_OPEN : Circuit [chars] changed state to open.
Explanation An ALPS circuit has transitioned from closed to open.
Recommended Action LOG_STD_NO_ACTION


%ALPS-5-CIRCUIT_CLOSED : Circuit [chars] changed state to closed, rsn = [chars].
Explanation An ALPS circuit has tranistioned from open to closed
Recommended Action LOG_STD_NO_ACTION


%ALPS-6-CIRCUIT_OPEN_FAILED : Circuit [chars] received a Circuit Open Failed message, rsn = [chars].
Explanation An ALPS circuit sent a Circuit Open Request message and received a Circuit Open Failed message as a reply.
Recommended Action LOG_STD_NO_ACTION


%ALPS-6-CIRCUIT_ASCU_REJECT : Circuit [chars] received a Circuit Open Confirm with a list of rejected ascus
Explanation An ALPS circuit sent a Circuit Open Request message and received a Circuit Open Confirm with a list of rejected ascus.
Recommended Action LOG_STD_NO_ACTION


%ALPS-6-CIRCUIT_UPDATE_FAILED : Circuit [chars] received a Circuit Open Failed message, rsn = [chars].
Explanation An ALPS circuit sent a Circuit Update message and received a Circuit Open Failed message as a reply.
Recommended Action LOG_STD_NO_ACTION


%ALPS-6-CIRCUIT_BUSY_START : Circuit [chars] has entered a congested state.
Explanation An ALPS circuit is experiencing congestion.
Recommended Action LOG_STD_NO_ACTION


%ALPS-7-CIRCUIT_BUSY_END : Circuit [chars] has exited a congested state.
Explanation An ALPS circuit is no longer experiencing congestion.
Recommended Action LOG_STD_NO_ACTION


%ALPS-7-CIRCUIT_DROPS_QUEUE_OVERFLOW : Threshold exceeded for queue overflow drops for circuit [chars]
Explanation The number of ALPS circuit drops due to queue overflow exceeds the ALPS circuit threshold value.
Recommended Action LOG_STD_NO_ACTION


%ALPS-7-CIRCUIT_DROPS_CKT_DISABLED : Threshold exceeded for circuit disabled drops for circuit [chars]
Explanation The number of ALPS circuit drops due to circuit disabled exceeds the ALPS circuit threshold value.
Recommended Action LOG_STD_NO_ACTION


%ALPS-7-CIRCUIT_DROPS_LIFETIME_EXPIRED : Threshold exceeded for lifetime timer expiration drops for circuit [chars]
Explanation The number of ALPS circuit drops due to lifetime timer expiration exceeds the ALPS circuit threshold value.
Recommended Action LOG_STD_NO_ACTION


%ALPS-7-CIRCUIT_DROPS_INVALID_ASCU : Threshold exceeded for invalid ASCU drops for circuit [chars]
Explanation The number of ALPS circuit drops due to invalid ASCU identifier exceeds the ALPS circuit threshold value.
Recommended Action LOG_STD_NO_ACTION


%ALPS-7-CIRCUIT_DROPS_VC_RESET : Threshold exceeded for X.25 VC Reset drops for circuit [chars]
Explanation The number of ALPS circuit drops due to X.25 VC Reset exceeds the ALPS circuit threshold value.
Recommended Action LOG_STD_NO_ACTION


%ALPS-6-CIRCUIT_X25_VC_STUCK : Host unresponsive on X.25 VC for circuit [chars]
Explanation The X.25 or EMTOX host is not advancing the transmit window for extended periods of time. This may be indicative of a temporary problem with the host application. An X.25 Reset is sent to reset the transmit and receive windows to allow communication to proceed.
Recommended Action None


%ALPS-5-ASCU_UP : ASCU [hex] on interface [chars] is up.
Explanation An ALPS ASCU has transitioned from down to up.
Recommended Action LOG_STD_NO_ACTION


%ALPS-5-ASCU_DOWN : ASCU [hex] on interface [chars] is down.
Explanation An ALPS ASCU has transitioned from up to down.
Recommended Action LOG_STD_NO_ACTION


%ALPS-3-ASCU_FSM_ERR : ASCU [hex] on interface [chars] has an internal FSM error.
Explanation Internal error.
Recommended Action Turn debug flags on, capture traces & contact Cisco technical support


%ALPS-3-ASCU_IF_STUCK : Polling for ASCU [hex] on interface [chars] is stalled.
Explanation The polling mechanism for an ALPS interface has become stuck.
Recommended Action LOG_STD_NO_ACTION


%ALPS-5-ASCU_DISABLED_ASCU_STUCK : ASCU [hex] on interface [chars] has been disabled since 4 consecutive messages were received from same SID.
Explanation An ALPS ASCU has been automatically disabled.
Recommended Action LOG_STD_NO_ACTION


AMT

%AMT-2-GATEWAY_INIT : Error initializing AMT Gateway
Explanation Insufficient memory is available to initialize Gateway
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%AMT-2-RELAY_INIT : Error initializing AMT Relay
Explanation Insufficient memory is available to initialize Relay
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%AMT-2-MSGTYPE_ERR : [chars] AMT message with invalid type [dec]
Explanation AMT type is not 1-7
Recommended Action No action is required.


%AMT-2-PROCESS_ERR : Error initializing AMT process
Explanation Can't start the AMT process
Recommended Action No action is required.


%AMT-2-ADD_GATEWAY : Error adding new Gateway
Explanation Can't get memory for a new Gateway %s, port %d
Recommended Action No action is required.


%AMT-2-RPT_WAVLINIT : Error initializing IGMP Unsolicited Report handler
Explanation Insufficient memory is available to initialize the IGMP Unsolicited Report handler.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


AN

%AN-4-DEVICE_NOT_IN_WHITELIST : Device with UDI ([chars]) connected to Proxy (Addr [chars]) on interface [chars] is not in whitelist and will not be allowed by autonomic registrar in its domain [chars]
Explanation The autonomic network registration authority will not allow this device to join as it is not in whitelist
Recommended Action No action is required.


%AN-4-DEVICE_ALREADY_REGISTERED_BY_ANR : Device with UDI ([chars]) connected to Proxy (Addr [chars]) on interface [chars] is already registered by autonomic registrar in its domain [chars] with a different public key
Explanation The autonomic network registration authority will not allow this device to join as it already registered with a different public key
Recommended Action No action is required.


%AN-6-DEVICE_ALLOWED_BY_ANR : Device with udi [chars] is allowed by autonomic registrar in its Domain ID [chars] with addr [chars] and Device ID [chars]
Explanation The autonomic network registration authority has authorised this device to enter its network
Recommended Action No action is required.


%AN-6-DEVICE_ENROLLED : Device with UDI ([chars]) connected to Proxy (Addr [chars]) on the interface [chars] is allowed by Autonomic registrar (Addr [chars]) in its domain [chars] and has been assigned IP Addr ([chars]) and Device ID ([chars])
Explanation The autonomic network registration authority has enrolled this device
Recommended Action No action is required.


%AN-5-DEVICE_BOOTSTRAPPED_BY_ANR : Device with UDI ([chars]) and (Addr [chars]) has been boot strapped by autonomic registrar, in autonomic domain [chars]
Explanation The autonomic network registration authority has bootstrapped this device
Recommended Action No action is required.


%AN-5-ANR_UP : A New Autonomic Registrar has been configured in domain ([chars]) and it has been assigned IP Addr ([chars]) and Device ID as ([chars])
Explanation The autonomic network registration authority has been confgiured and is locally up
Recommended Action No action is required.


%AN-5-ANR_DOWN : Disabled autonomic registrar with Addr ([chars])
Explanation The autonomic network registration authority functionality is disabled
Recommended Action No action is required.


%AN-4-MASA_AUTH_FAIL : Device with udi [chars] is not authorized by MASA
Explanation The MASA - manufacturer authorised signing authority has not authorised this device in its network
Recommended Action No action is required.


%AN-4-MASA_AUDIT_LOG_FAIL : Device with udi [chars] is not in the audit log of MASA
Explanation The manufacturer authorised signing authority audit log doesnt contain this device in its database
Recommended Action No action is required.


%AN-6-MASA_NOT_CONFIG : Autonomic registrar with udi [chars] has no reachability to MASA -not configured, Cant verify device udi [chars]
Explanation The manufacturer authorised signing authority has not been configured, cannot do the verification of device
Recommended Action No action is required.


%AN-6-ANR_WHITELIST_CONFIG : Autonomic registrar with (Addr [chars]) Domain id [chars] has whitelist- will allow only these devices in autonomic network
Explanation The autonomic registeration authority has been configured with white list and will allow only these devices to enter its network
Recommended Action No action is required.


%AN-6-ANR_WHITELIST_NOT_CONFIG : Autonomic registrar with (Addr [chars]) has no whitelist- will allow all devices
Explanation The autonomic registeration authority has not been configured with white list and will allow all devices to enter its network
Recommended Action No action is required.


%AN-3-ANR_WHITELIST_FILE_ERROR : Autonomic Registrar with (Addr [chars]) encountered error in reading from whitelist file [chars]
Explanation The autonomic registeration authority encountered file error when reading from whitelist file, check the file name and its contents
Recommended Action No action is required.


%AN-3-IDP_INTENT_FILE_ERROR : Device (Addr [chars]) encountered error ([chars]) when reading from intent file
Explanation The Intent Distribution Protocol Module, encountered file error when reading from intent file, check the file name and its contents
Recommended Action No action is required.


%AN-5-IDP_INTENT_VER_UPDATED : Device (Addr [chars]) updated to a new Intent version [dec]
Explanation The device received a new intent file by Intent Distribution Protocol
Recommended Action No action is required.


%AN-5-IDP_INTENT_VER_OLD_DISCARD : Device (Addr [chars]) discarded the older intent version [dec]
Explanation The device received an old intent file by Intent Distribution Protocol and is discarding it
Recommended Action No action is required.


%AN-5-SERVICE_LEARNT : Device with (Addr [chars]) learnt Autonomic service with Service Type ([dec]) Service IP Addr ([chars])
Explanation The device received a new autonomic service by Service Discovery Protocol
Recommended Action No action is required.


%AN-6-UDI_AVAILABLE : UDI - [chars]
Explanation Unique device identification number is available on the device
Recommended Action No action is required.


%AN-6-AN_ABORTED_BY_CONSOLE_INPUT : Autonomic disabled due to User intervention on console. configure 'autonomic' to enable it.
Explanation User entered into configuration mode So AN is disabled, An process is stopped
Recommended Action No action is required.


%AN-6-AN_ABORTED_BY_NO_AUTONOMIC : Autonomic disabled due to 'no autonomic' command.
Explanation 'No autonomic' command is entered So AN is disabled, An process is stopped
Recommended Action No action is required.


%AN-6-AN_ABORTED_BY_MANUAL_CONFIG_DETECTED : Autonomic disabled due to detection of new configuration.
Explanation Some other process configures something. So AN is disabled, An process is stopped
Recommended Action No action is required.


%AN-6-CONFIG_SAVE : Issuing 'write memory' to save config
Explanation Saving configurations to startup-config by AN process
Recommended Action No action is required.


%AN-6-SUDI_AVAILABLE : secure UDI - [chars]
Explanation Secure unique device identification number is available on the device
Recommended Action No action is required.


%AN-5-NBR_IN_DOMAIN : Neighbor with (Addr [chars]) connected via interface [chars] to device (Addr [chars]) is brought inside my domain [chars]
Explanation The device has been admitted into the autonomic domain
Recommended Action No action is required.


%AN-5-NBR_OUT_DOMAIN : Neighbor with (Addr [chars]) connected via interface [chars] to device (Addr [chars]) is now outside the autonomic domain
Explanation The device is removed from the autonomic domain ,it can happen if the domain certificate is NULL or if the domain certificate is invalid
Recommended Action No action is required.


%AN-5-NBR_ADDED : Device with UDI ([chars]) is added as a Neighbor to Device with (Addr [chars]) on the interface [chars]
Explanation A hello message is received and the device is added in the neighbor table
Recommended Action No action is required.


%AN-5-NBR_LOST : Device with ACP (Addr [chars]) lost connectivity to its Neighbor (Addr [chars]) on interface [chars]
Explanation Lost connectivity to the neighboring device & it is no longer part of autonomic domain
Recommended Action No action is required.


%AN-6-NBR_DOMAIN_CERT_VALID : Domain certificate of Neighbor with (Addr [chars]) connected on interface [chars] is valid
Explanation The domain certificate of the neighbor device is validated successfully
Recommended Action No action is required.


%AN-3-NBR_DOMAIN_CERT_INVALID : Domain certificate of Neighbor with (Addr [chars]) connected on interface [chars] is invalid
Explanation The domain certificate of the neighbor device is invalid
Recommended Action No action is required.


%AN-3-NBR_DOMAIN_CERT_REVOKED : Domain certificate of Neighbor with (Addr [chars]) connected on interface [chars] is revoked
Explanation The domain certificate of the neighbor device has been revoked
Recommended Action No action is required.


%AN-3-NBR_DOMAIN_CERT_EXPIRED : Domain certificate of Neighbor with (Addr [chars]) connected on interface [chars] has expired
Explanation The domain certificate of the neighbor device has expired
Recommended Action No action is required.


%AN-6-MY_DOMAIN_CERT_RENEWED : Domain certificate of device (Addr [chars]) has been renewed
Explanation The domain certificate of this device is renewed
Recommended Action No action is required.


%AN-6-MY_DOMAIN_CERT_EXPIRED : Domain certificate of this device (Addr [chars]) has expired
Explanation The domain certificate of this device has expired
Recommended Action No action is required.


%AN-3-DOMAIN_KEY_GEN_FAIL : The bootstrapping device with key label ([chars]) failed to generate key pair for enrollment at Autonomic registrar
Explanation The key pair generation failed at the device for triggering BS request message to Autonomic registrar. Can be due to failure in RSA key pair generation in the crypto library
Recommended Action No action is required.


%AN-4-ANR_SIGN_VERIFY_FAIL : Device UDI ([chars]) signature verification of Autonomic registrar by new device has failed due to error ([chars])
Explanation The new device joining the network verified the signature of autonomic registrar as a part of mutual authentication and the verification failed
Recommended Action No action is required.


%AN-4-MASA_AUTH_TOKEN_PARSE_ERROR : Error while parsing authentication token from MASA server for device udi-[chars]
Explanation Encountered error while parsing the authentication token response string from MASA server
Recommended Action No action is required.


%AN-3-TLV_PARSE_ALIGN_ERROR : TLV parsed Len [dec], Next TLV could be misaligned
Explanation Parsed TLV message is not a multiple of 4 and the next TLV message can be misaligned
Recommended Action No action is required.


%AN-3-TLV_PARSE_LEN_INCORRECT : TLV parsed len [dec] > original message length [dec]
Explanation Parsed TLV message length is greater than original message length
Recommended Action No action is required.


%AN-3-MSG_INVALID_HEADER : Invalid message header type [dec] received
Explanation The message packet header got corrupted and invalid header received
Recommended Action No action is required.


%AN-6-ACP_ROUTING_GLOBAL_ENABLED : Enabled global OSPFv3 pid [dec],rid [IP_address],area [dec]
Explanation OSPF routing has been enabled globally
Recommended Action No action is required.


%AN-6-ACP_ROUTING_INTERFACE_ENABLED : OSPF routing enabled on interface: [chars], (pid [dec],rid [IP_address], area [dec])
Explanation OSPF routing has been enabled on all physical interface
Recommended Action No action is required.


%AN-6-ACP_ROUTING_GLOBAL_DISABLE : Removed OSPFv3 routing globally, pid [dec]
Explanation OSPF routing has been disabled globally
Recommended Action No action is required.


%AN-6-ACP_VRF_GLOBAL_CREATE_SUCCESS : Device UDI ([chars]) Autonomic VRF created globally vrf name [chars], vrf id [dec]
Explanation Autonomic network VRF has been created globally
Recommended Action No action is required.


%AN-3-ACP_VRF_GLOBAL_CREATE_FAIL : Device UDI ([chars]) failed to create Autonomic VRF globally, vrf name [chars], vrf id [dec]
Explanation Autonomic network VRF has not been created globally
Recommended Action No action is required.


%AN-6-ACP_VRF_GLOBAL_REMOVE : Device UDI ([chars]) Autonomic VRF removed globally vrf name [chars], vrf id [dec]
Explanation Autonomic network VRF has been removed globally
Recommended Action No action is required.


%AN-6-ACP_VRF_INTERFACE_CREATE_SUCCESS : Device UDI ([chars]) Autonomic VRF created successfully on interface [chars], vrf name [chars], vrf id [dec]
Explanation Autonomic network VRF has been created on the interface
Recommended Action No action is required.


%AN-3-ACP_VRF_INTERFACE_CREATE_FAIL : Device UDI ([chars]) failed to create Autonomic VRF on interface [chars], vrf name [chars], vrf id [dec]
Explanation Autonomic network VRF has not been created on the interface
Recommended Action No action is required.


%AN-6-ACP_CHANNEL_TO_NBR_CREATED : Established ACP [chars] from Device (Addr [chars]) to Neighbor (Addr [chars]) connected on interface [chars]
Explanation Autonomic Network Control plane Channel has been created to the neighbor
Recommended Action No action is required.


%AN-3-ACP_CHANNEL_TO_NBR_FAILED : Failed to create ACP [chars] from Device (Addr [chars]) to Neighbor (Addr [chars]) connected on interface [chars]
Explanation Autonomic Network Control Plane Channel has not been created to the neighbor
Recommended Action No action is required.


%AN-6-ACP_CHANNEL_TO_NBR_REMOVED : Removed ACP [chars] from Device (Addr [chars]) to Neighbor (Addr [chars]) connected on interface [chars]
Explanation Autonomic Network Control Plane Channel to neighbor is removed
Recommended Action No action is required.


%AN-6-ACP_IPSEC_TO_NBR_CREATED : Established IPSEC on ACP from Device (Addr [chars]) to Neighbor (Addr [chars]) connected on interface [chars]
Explanation Autonomic Network Control plane - IPSEC tunnel established to neighbor
Recommended Action No action is required.


%AN-3-ACP_IPSEC_TO_NBR_FAILED : Failed to create IPSEC on ACP from device (Addr [chars]) to Neighbor (Addr [chars]) on interface [chars]
Explanation Autonomic Network Control plane - Failed to create IPSEC tunnel to neighbor
Recommended Action No action is required.


%AN-6-ACP_IPSEC_TO_NBR_REMOVED : Removed IPSEC on ACP from Device (Addr [chars]) to Neighbor (Addr [chars]) connected on interface [chars]
Explanation Autonomic Network Control plane - IPSEC tunnel to neighbor is removed
Recommended Action No action is required.


%AN-6-ACP_DIKE_TO_NBR_CREATED : Established DIKE on ACP [chars] from Device (Addr [chars]) to Neighbor (Addr [chars]) connected on interface [chars]
Explanation Autonomic Network Control plane - DIKE tunnel established to neighbor
Recommended Action No action is required.


%AN-3-ACP_DIKE_TO_NBR_FAILED : Failed to create DIKE on ACP [chars] from Device (Addr [chars]) to Neighbor (Addr [chars]) connected on interface [chars]
Explanation Autonomic Network Control plane - Failed to create DIKE tunnel to neighbor
Recommended Action No action is required.


%AN-6-ACP_DIKE_TO_NBR_REMOVED : Removed DIKE on ACP [chars] from Device (Addr [chars]) to Neighbor (Addr [chars]) connected on interface [chars]
Explanation Autonomic Network Control plane - DIKE tunnel to neighbor is removed
Recommended Action No action is required.


%AN-6-CONFIG_DOWNLOAD_SUCCESS : Config download at the Device (Addr [chars]) is Successful
Explanation Download of the config file to the Running config is Successful
Recommended Action No action is required.


%AN-6-CONFIG_DOWNLOAD_FAILED : Config download on the Device (Addr [chars]) has FAILED
Explanation Failed to download the config file to the Running config
Recommended Action No action is required.


%AN-6-CONFIG_DOWNLOAD_STARTED : Config download started on the Device (Addr [chars])
Explanation Config download is triggerred
Recommended Action No action is required.


%AN-5-CD_STATE_CHANGED : [chars] Channel ([dec]) [chars] - Our Intf ([chars]), Nbr UDI ([chars]), Nbr Intf ([chars])
Explanation CD L2 or Reuse Channel Created/Removed/Expired
Recommended Action No action is required.


ANALOG_SM

%ANALOG_SM-6-STAGGER_RINGING : INFO only: REN resources have been exhausted. Unable to ring FXS voice port on slot [dec]. Stagger ringing algorithm has been triggered to compensate.
Explanation Too many FXS voice ports are being rung at the same time on this module. Stagger ringing is triggered to prevent overload the HW module
Recommended Action Make sure ren configuration of all analog FXS voice ports on this module is correctly configured and matching up the actually required REN LOG_STD_RECUR_ACTION


APM

%APM-3-INIT : [chars]
Explanation Easy Perf Mon Initialization 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.


%APM-3-LIST : [chars] [chars]
Explanation List operation 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.


%APM-3-MEM : Memory [chars] failed - [chars]
Explanation Memory operation 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.


APPFW through ATA

APPFW

%APPFW-4-HTTP_STRICT_PROTOCOL : Sig:[dec] HTTP protocol violation detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the strict-http application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_CONT_LENGTH : content-length
Explanation The HTTP message has been detected to violate the content-length application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_CONT_TYPE_VERIFY : Sig:[dec] Content type does not match the specified type - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the content-type-verification application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_MATCH_REQ_RESP : Sig:[dec] Content type: [chars] does not match the Accept-Type from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the content-type-verification application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_CONT_TYPE_MATCH : Sig:[dec] Content type not found - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the content-type-verification application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_CONT_TYPE_SIZE : Sig:[dec] Content size [int] out of range - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the content-type-verification application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_MAX_HDR_LEN : Sig:[dec] HTTP Header length exceeded. Received [int] byte of header - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the max-hdr-len application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_MAX_URI_LEN : Sig:[dec] HTTP URI length exceeded. Received [int] byte of URL - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the max-uri-len application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_REQ_METHOD_RFC : Sig:[dec] HTTP RFC method illegal - [chars] '[chars]' from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the request-method application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_REQ_METHOD_EXT : Sig:[dec] HTTP Extension method illegal - [chars] '[chars]' from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the request-method application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_PORT_MISUSE_IM : Sig:[dec] HTTP Instant Messenger detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the port misuse application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_PORT_MISUSE_P2P : Sig:[dec] HTTP Peer-to-Peer detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the port misuse application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_PORT_MISUSE_TUNNEL : Sig:[dec] HTTP Tunnel detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the port misuse application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_TRANSFER_ENCODE : Sig:[dec] HTTP Transfer encoding violation detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the transfer encoding application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-4-HTTP_DEOBFUSCATE : Sig:[dec] Deobfuscation signature detected - [chars] [chars] from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the deobfuscate application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-3-HTTP_MAX_REQ_EXCEED : Maximum of [dec] unanswered HTTP requests exceeded from [IP_address]:[dec] to [IP_address]:[dec]
Explanation The HTTP message has been detected to violate the transfer encoding application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-6-HTTP_SESSION_AUDIT_TRAIL : HTTP session initiator [IP_address]:[dec] sends [dec] bytes - responder [IP_address]:[dec] sends [dec] bytes
Explanation The HTTP message has been detected to violate the transfer encoding application firewall inspection rule.
Recommended Action This message is for informational purposed only, but may indicate a security problem.


%APPFW-3-HTTP_APPFW_CONF_ERROR : Application Firewall configuration error -- [chars]
Explanation An error has occurred during Application Firewall configuration.
Recommended Action This message indicates an error during firewall configuration and may be a potential security problem.


%APPFW-6-IM_YAHOO_SESSION : im-yahoo [chars] service session initiator [IP_address]:[dec] [chars] [dec] bytes [chars] responder [IP_address]:[dec]
Explanation The YMSGR well known service message has been detected.
Recommended Action This message is for informational purposed only.


%APPFW-6-IM_YAHOO_P2P_CHAT : im-yahoo text-chat service session: [IP_address]:[dec] establishing a direct chat with [dec].[dec].[dec].[dec]
Explanation A specific service yyyy has been detected to establish a direct connection with another peer in a Yahoo! Instant Messenger application and the application firewall inspection policy has been configured to send an alarm for this event. Typical services are ñ text-chat, voice-chat, file-transfer etc.
Recommended Action This message is for informational purposed only.


%APPFW-6-IM_AOL_SESSION : im-aol [chars] service session initiator [IP_address]:[dec] [chars] [dec] bytes [chars] responder [IP_address]:[dec]
Explanation The AIM well known service message has been detected.
Recommended Action This message is for informational purposed only.


%APPFW-6-IM_MSN_SESSION : im-msn [chars] service session initiator [IP_address]:[dec] [chars] [dec] bytes [chars] responder [IP_address]:[dec]
Explanation The MSNMSGR well known service message has been detected.
Recommended Action This message is for informational purposed only.


%APPFW-6-IM_YAHOO_CLIENT_VERSION : im-yahoo [IP_address]:[dec] attempting to establish connection with yahoo server [IP_address]:[dec] using an unsupported version of the client
Explanation The YAHOO client version is not supported
Recommended Action This message is for informational purposed only.


%APPFW-6-IM_MSN_CLIENT_VERSION : im-msn [IP_address]:[dec] attempting to establish connection with msn server [IP_address]:[dec] using an unsupported version of the client
Explanation The MSN client version is not supported
Recommended Action This message is for informational purposed only.


%APPFW-6-IM_AOL_CLIENT_VERSION : im-aol [IP_address]:[dec] attempting to establish connection with aol server [IP_address]:[dec] using an unsupported version of the client
Explanation The AOL client version is not supported
Recommended Action This message is for informational purposed only.


APPNAV_CLIENT

%APPNAV_CLIENT-3-CFT_INIT_FAILED : AppNav failed initialize flow table - [int].
Explanation Flow table is a critical component of AppNav. The failure is likely due to lack of memory (DRAM) on the ESP. The previous configuration needs to be removed and re-applied.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


APPNAV_CONTROLLER

%APPNAV_CONTROLLER-4-SC_SN_UNREACHABLE : APPNAV-CONTROLLER: Alarm #29007, Severity: Major
Explanation Service context has entered Operational state and there is at least one configured node that is not part of the SN view.
Recommended Action Check status of configured SNs.


%APPNAV_CONTROLLER-5-SC_MIXED_FARM : APPNAV-CONTROLLER: Alarm #29003, Severity: Minor
Explanation When an appnav controller detects upon that there are other appnav-controllers/SNs in the cluster with different ICIMP/DMP minor version number.
Recommended Action Check versions of SNs in network.


%APPNAV_CONTROLLER-4-SNG_UNAVAILABLE : APPNAV-CONTROLLER: Alarm #30001, Severity: Major
Explanation No SN in appnav node group is available for optimization.
Recommended Action Check status of configured nodes.


%APPNAV_CONTROLLER-4-SNG_AO_UNAVAILABLE : APPNAV-CONTROLLER: Alarm #30000, Severity: Major
Explanation No node in service node group is available for optimization and traffic is getting optimized by a secondary SNG.
Recommended Action Check status of configured SNs.


%APPNAV_CONTROLLER-5-SC_CONVERGENCE_FAILED : APPNAV-CONTROLLER: Alarm #29001, Severity: Critical
Explanation CMM is not coming out of convergence state
Recommended Action Check connectivity between SN's and AC's


%APPNAV_CONTROLLER-5-SC_DEGRADED_CLUSTER : APPNAV-CONTROLLER: Alarm #29002, Severity: Critical
Explanation Mismatch of stable AC views between AC's
Recommended Action Check connectivity between AC's


%APPNAV_CONTROLLER-4-SC_SC_UNREACHABLE : APPNAV-CONTROLLER: Alarm #29006, Severity: Major
Explanation Connectivity with AC's under ACG is lost
Recommended Action Make sure AC's configured under ACG are up and reachable


%APPNAV_CONTROLLER-4-SC_SN_EXCLUDED : APPNAV-CONTROLLER: Alarm #29008, Severity: Major
Explanation Stable SN views across AC's are different. Those SN's that are not reachable by other AC's are exlcuded
Recommended Action Make sure excluded SN's are reachable from all AC's


%APPNAV_CONTROLLER-4-ACG_IP_CHANGED : APPNAV-CONTROLLER: Alarm #10000, Severity: Major Appnav controller group IP address changed! All relevant service contexts will be disabled
Explanation Appnav controller group IP address changed! All relevant service contexts will be disabled
Recommended Action Change AppNav Controller's IP


%APPNAV_CONTROLLER-6-CM_REGISTER_SUCCESS : AppNav registered with Central Manager successfully
Explanation Received a registration success message from the Central Manager
Recommended Action None. All is well


%APPNAV_CONTROLLER-3-CM_REGISTER_FAILED : AppNav registration with Central Manager failed for the following reason: [chars]
Explanation Received a registration failure message from the AppNav Central Manager. AppNav has not registered with the Central Manager
Recommended Action Issue the debug waas management errors command, and the debug waas management events , Contact your Cisco technical support representative , and provide the representative with the gathered information.


%APPNAV_CONTROLLER-4-SERVICE_CTX_DISABLE : SERVICE-CONTROLLER: Alarm 10001, Severity: Major Disabling service context [chars]
Explanation Disabling service context
Recommended Action


ARAP

%ARAP-5-PAKINVALID : TTY [dec]: ARAP invalid packet received
Explanation A corrupted packet reached the ARA protocol code.
Recommended Action Check for excessive CPU usage or excessive line noise.


%ARAP-6-ADDRUSED : TTY [dec]: ARAP started for user [chars]; address [dec].[dec]
Explanation This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged in.
Recommended Action No action is required.


%ARAP-6-ADDRFREE : TTY [dec]: ARAP ended for user [chars]; address %A; [dec] seconds connected
Explanation This message appears only when ARA protocol logging is configured. The message notes that an ARA protocol user has logged out.
Recommended Action No action is required.


%ARAP-5-INITCONFUSED : TTY [dec]: ARAP unexpected initialization packet [chars]
Explanation The startup negotiation between a client and the ARA protocol server fell out of order. If this message is received sporadically, it indicates line noise.
Recommended Action If this message recurs, reinstall the ARA client software.


%ARAP-4-CONFAILED : TTY [dec]: ARAP connection failed: [chars]
Explanation The ARA protocol client was denied access, probably due to a configuration problem on the server. The error message should indicate the problem. This message does not indicate access denials due to bad passwords.
Recommended Action Investigate the problem reported in the error message.


%ARAP-3-BADCONFIG : TTY [dec]: unhandled configuration command
Explanation A configuration command was not recognized.
Recommended Action Check the configuration file on the server for any invalid configuration commands.


%ARAP-3-BADPAK : TTY [dec]: Bad packet type in arap_send_msg
Explanation Internal data structures are corrupted.
Recommended Action Check for abnormally high CPU usage.


%ARAP-6-BADEXIT : TTY [dec]: exited user [chars]: [chars]
Explanation A user was disconnected from ARA protocol at an unexpected time. The disconnection may be due to modems dropping, server error, client problems, or any number of other difficulties.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.


%ARAP-6-XTICKLE : TTY [dec]: exited user [chars]: Other side stopped answering ARAP tickles (mnp4 pak resent [dec] mnp4 pak sent [dec] last [dec] now [dec])
Explanation The router disconnected as the remote Macintosh client stopped sending ARAP tickle or data packets.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.


%ARAP-6-MAXRESENDS : TTY [dec]
Explanation The router resent MNP4 packets maximum number of times without receiving an acknowledgement.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.


%ARAP-0-NULLRESEND : TTY [dec]
Explanation An internal software error occured.
Recommended Action Report this error to you technical support representative.


%ARAP-0-NOTNULLRESEND : TTY [dec]
Explanation An internal software error occured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ARAP-6-LRPHASERROR : TTY [dec]: Received LT in CONNECTION PHASE
Explanation The router received an invalid packet during ARA connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.


%ARAP-6-RCVNOPAK : TTY [dec]: Receive getbuffer failure. dropping frame
Explanation No buffer exists for an incoming packet.
Recommended Action Examine buffer usage statistics. Possibly more memory is required.


%ARAP-6-RCVGIANT : TTY [dec]: Rcv giant. dropping frame
Explanation The router received an oversized MNP4 frame.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.


%ARAP-0-DEFAULT : TTY [dec]
Explanation An internal software error occured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ARAP-0-WAITBADMSG : TTY [dec]: arg msg bad [hex]
Explanation The router received an invalid packet during ARAP MNP4 connection setup phase.
Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.


%ARAP-0-VSERROR : TTY [dec]: VS queued error
Explanation An internal software error occured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ARAP-6-MNP4T401 : TTY [dec]: T401 [dec] baud rate [dec]
Explanation This message indicates that the router received MNP4 connection request. MNP4 acknowledgement timer value is also indicated.
Recommended Action No action is required.


%ARAP-6-RESENDSLOW : TTY [dec]
Explanation The router repeated resending of MNP4 packets as the Macintosh client failed to acknowledge previously resent packets.
Recommended Action If this error message persists for several ARAP connections report it to your technical support representative.


%ARAP-2-NOLOG : TTY [dec]: Could not malloc log
Explanation Memory not available for internal MNP4 logging.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ARAP-6-MNP4RCVDISC : TTY [dec]: MNP4 input disconnect
Explanation This indicates that the router received disconnect request from the remote Macintosh client.
Recommended Action No action is required.


%ARAP-3-REMOTEERROR : TTY [dec]: arap input error
Explanation ARAP connection was terminated without a known cause.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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.


%ARAP-6-TIMERERROR : TTY [dec]: MNP4 timeout error
Explanation The router is dropping the connection after doing maximum resends.
Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.


%ARAP-4-NOEXTTACACS : TTY [dec]: arap TACACS is configured but extended TACACS is not.
Explanation Terminal Access Controller Access Control System (TACACS) authentication failed because extended TACACS is not configured.
Recommended Action Configure extended TACACS.


%ARAP-3-ABORTED : TTY [dec]: arap callback aborted
Explanation An unexpected message was received during the Microcom Networking Protocol version 4 (MNP4) link setup.
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.


%ARAP-3-TIMEOUT : TTY [dec]: arap expected message timeout
Explanation The software timed out during the MNP4 link setup.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. 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.


ARCHIVE_CONFIG

%ARCHIVE_CONFIG-4-ARCHIVE_SKIPPED : Archive of router configuration was skipped due to a previous initiation.
Explanation Only one archive can be created at a time. Two or more simultaneous archives in progress is not allowed. This could occur for example if two users attempt to create an archive simultaneouly.
Recommended Action Retry the archive creation later, when the previous archive has finished being written.


%ARCHIVE_CONFIG-4-ARCHIVE_DELETE_FAILED : Delete of a previously saved archive of the router configuration could not be completed.
Explanation The router could not delete a file that was previously written. The file that was being deleted file contains an archive of the router configuration. This could occur for example if the file was manually deleted.
Recommended Action None


%ARCHIVE_CONFIG-6-ARCHIVE_CREATE_FAILED_STANDBY : Could not create an archive of the router configuration on the standby RP.
Explanation The router could not create an archive file on the standby RP. The file that was being created contains an archive of the router configuration. This could occur for example if the active RP cannot communicate with the standby RP.
Recommended Action None


%ARCHIVE_CONFIG-6-ARCHIVE_DELETE_FAILED_STANDBY : Delete of a previously saved archive of the router configuration could not be completed on the standby RP.
Explanation The router could not delete a file that was previously written on the standby RP. The file that was being deleted file contains an archive of the router configuration. This could occur for example if the file was manually deleted. Alternatively, the file could not be deleted when the active RP cannot communicate with the standby RP.
Recommended Action None


ARCHIVE_ISSU

%ARCHIVE_ISSU-2-INIT : Archive ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The Archive ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.
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.


%ARCHIVE_ISSU-3-TRANSFORM_FAIL : Archive ISSU client [chars] transform failed for 'Message Type [dec]'. Error: [dec] ([chars])
Explanation The Archive ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the Archive state between the active device and the standby device is not identical.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated version <session_id>)


%ARCHIVE_ISSU-3-MSG_NOT_OK : Archive ISSU client 'Message Type [dec]' is not compatible
Explanation The Archive ISSU client received an incompatible message from the peer device. The message cannot be processed.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>)


%ARCHIVE_ISSU-3-MSG_SIZE : Archive ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The Archive ISSU client failed to calculate the MTU for the specified message. The Archive ISSU client is not able to send the message to the standby device.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>)


%ARCHIVE_ISSU-3-INVALID_SESSION : Archive ISSU client does not have a valid registered session.
Explanation The Archive ISSU client does not have a valid registered session.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>)


%ARCHIVE_ISSU-2-SESSION_REGISTRY : Archive ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The Archive ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>)


%ARCHIVE_ISSU-3-SESSION_UNREGISTRY : Archive ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The Archive ISSU client failed to unregister session information.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>)


%ARCHIVE_ISSU-2-SESSION_NEGO_FAIL_START : Failed to start Archive ISSU session negotiation. Error: [dec] ([chars])
Explanation The Archive ISSU client failed to start session negotition. If a problem occurs with the ISSU session start, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id>)


%ARCHIVE_ISSU-2-SEND_NEGO_FAILED : Archive ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The Archive ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)


%ARCHIVE_ISSU-2-GET_BUFFER : Archive ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The Archive ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)


ARP

%ARP-4-ENTRYTHRESHOLD : Cannot insert more than [int] dynamic ARP entries on [chars]
Explanation This message indicates that the number of dynamically learned ARP entries, complete or incomplete, has exceeded a preconfigured limit, indicating a possible misconfiguration or DOS attack.
Recommended Action First, inspect the ARP entries on the affected interface. If they are valid entries, either increase the configured ARP entry limit or reconfigure the network to reduce ARP peers. If they are invalid entries, there is a possible DOS attack on the system.


%ARP-4-TRAPENTRY : [int] dynamic ARP entries on [chars] installed in the ARP table
Explanation This message indicates that the number of dynamically learned ARP entries, complete or incomplete, has exceeded a preconfigured threshold, indicating a possible misconfiguration or DOS attack.
Recommended Action First, inspect the ARP entries on the affected interface. If they are valid entries, either increase the configured log threshold or reconfigure the network to reduce ARP peers. If they are invalid entries, there is a possible DOS attack on the system.


%ARP-4-ARPLEARNTHRES : Learned ARP entries have reached to threshold level [int]
Explanation This message indicates that the number of learned ARP entries, which are not configured, has reached a preconfigured threshold, indicating a possible misconfiguration or DOS attack.
Recommended Action First, inspect the ARP entries on the interface.reconfigure the network to reduce ARP peers.


%ARP-4-ARPLEARNCROSS : [int] Learned ARP entries are installed in the ARP table and reached the max limit
Explanation This message indicates that the number of dynamically learned ARP entries has reached a preconfigured max. limit in ARP Table.
Recommended Action First, inspect the ARP entries on the interface. If they are valid entries, either increase the configured max limit or reconfigure the network to reduce ARP peers.


%ARP-6-ARPLEARNRESUME : Resuming Learn ARP entries to install in ARP table.
Explanation This message indicates that the number of dynamically learned ARP entries is in range of permit threshold value.System is allowing new Learned ARP entries to install in ARP table.
Recommended Action No action is required.


%ARP-3-STCKYARPOVR : Attempt to overwrite Sticky ARP entry: [IP_address], hw: [enet] by hw: [enet]
Explanation Multiple stations configured with same IP in Private VLAN. Possible case of IP address stealing.
Recommended Action Change the IP address of one of the two systems.


%ARP-3-TABLEERR : Internal software error during ARP table operation for ARP entry
Explanation An internal software error has occurred during an ARP table operation.
Recommended Action If this message recurs, 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.


%ARP-4-ARPADJ : Received CEF Adjacency updation request on different interfaces: [IP_address] on [chars]
Explanation A request to update CEF adjacency came on two different interfaces.
Recommended Action If this message recurs, 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.


%ARP-3-ARPINIT : Internal software error during ARP subsystem initialization
Explanation An internal software error has occurred during ARP subsystem initialization.
Recommended Action If this message recurs, 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.


%ARP-3-ARPHAMSGFMT : Malformed ARP HA checkpointing message (size = [int], entry count = [int])
Explanation A malformed ARP HA checkpointing message has been received.
Recommended Action If this message recurs, 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.


%ARP-4-NULL_SRC_MAC : NULL MAC address from [IP_address] on [chars]
Explanation Application or peer tried to insert entry with NULL SRC MAC
Recommended Action If this message recurs, call your technical support representative for assistance.


%ARP-3-ARPINT : ARP table accessed at interrupt level [dec]
Explanation ARP table is accessed at interrupt level which is forbidden.
Recommended Action If this message recurs, 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.


%ARP-3-ARPINVALIDEENTRY : ARP system internal error. Returns NULL arp entry on node [IPV6 address]
Explanation An internal software error has occurred in ARP subsystem, an NULL arp entry is got.
Recommended Action If this message recurs, 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.


ASPP

%ASPP-3-NOTTY : [chars]: Unable to set Rx/Tx tty async service hooks.
Explanation This message occurs only when ASP is configured. It indicates the serial interface using ASP is configured incorrectly or does not support asynchronous mode.
Recommended Action Verify the correct hardware interface type is being used.


AT

%AT-3-NOTRUNNING : AppleTalk not running
Explanation You tried to show or change the AppleTalk configuration when AppleTalk routing was not turned on.
Recommended Action Issue the appletalk routing command before issuing any other AppleTalk configuration or display command.


%AT-5-ADDRINUSE : [chars]: AppleTalk node warning; address %A already in use
Explanation The initial hint address was in use. A search will be made for a valid address.
Recommended Action No action is required.


%AT-5-ADDRINVALID : [chars]: AppleTalk node warning; address %A is invalid
Explanation The hint address specified for the interface was not valid for the current configuration.
Recommended Action The hint address is ignored and a random valid hint address is automatically computed. LOG_STD_NO_ACTION


%AT-3-DISCOFF : [chars]: AppleTalk node warning; discovery mode disabled
Explanation A hardware or 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.


%AT-3-NOADDRSAVAIL : [chars]: AppleTalk node down; no addresses available
Explanation No free node could be found on the interface.
Recommended Action If your AppleTalk network has less than 250 nodes, issue the debug appletalk errors command and then call your technical support representative. If your AppleTalk network has more than 250 nodes, split it into smaller networks by creating new segments and moving some nodes into the new segments.


%AT-3-NOSRCADDR : [chars]: AppleTalk packet error; no source address available
Explanation The router could not generate an AppleTalk packet because no valid AppleTalk source address was available to identify this router in the packet.
Recommended Action Configure an interface to have an address or cable range. Use the show appletalk command to verify that the interface is operational.


%AT-6-ADDRUSED : [chars]: AppleTalk node up; using address %A
Explanation No hint address or a bad hint address was specified. This message indicates which AppleTalk address will be used for the interface.
Recommended Action No action is required.


%AT-4-NETINVALID : [chars]: AppleTalk node down; conflicts with active internet
Explanation The configuration specified for the interface conflicts with the active AppleTalk internetwork. For example, a cable range might be configured that overlaps an existing route but does not match the entry exactly.
Recommended Action Use the appletalk cable-range command to reconfigure the interface so that there are no conflicts with the existing AppleTalk rnetwork, or take any other actions necessary to resolve the conflict. AppleTalk will periodically attempt to restart the interface.


%AT-3-NETDISAGREES : [chars]: AppleTalk interface disabled; network incompatible with %#a
Explanation The interface was disabled because the configured AppleTalk address or cable range for the interface conflicts with that of another router on the attached network.
Recommended Action Reconfigure the affected routers so that there are no conflicting addresses or cable ranges on the attached network.


%AT-3-DEFZONEERR : [chars]: AppleTalk interface warning; default zone differs from %#a
Explanation During the verification startup process, there was a disagreement between the default zone (the first zone defined after the appletalk cable-range command) and the router that confirmed the configuration. When an AppleTalk end node is first connected to a network, it joins the default zone until it is overridden.
Recommended Action Use the appletalk zone command to correct the configuration so that all routers are advertising the same default zone. Note that several router implementations are known to mismanage the default zone.


%AT-3-ZONEDISAGREES : [chars]: AppleTalk interface disabled; zone list incompatible with %#a
Explanation The zone list of the configured interface is inconsistent with the zone list of other routers.
Recommended Action Reconfigure the zone list on the router so that it does not conflict with that the zoen lists on other routers.


%AT-6-CONFIGOK : [chars]: AppleTalk interface enabled; verified by %#a
Explanation The AppleTalk configuration was verified by consulting the indicated router.
Recommended Action No action is required.


%AT-6-ONLYROUTER : [chars]: AppleTalk interface enabled; no neighbors found
Explanation No other AppleTalk routers were found on the network attached to the interface.
Recommended Action No action is required.


%AT-3-MCMISMATCH : [chars]: AppleTalk interface warning; zone multicast [enet] differs from our multicast [enet]
Explanation A computed multicast address disagrees with that provided by another AppleTalk router. The other AppleTalk router might be misconfigured or faulty.
Recommended Action Correct the problem at the other router.


%AT-5-INTDOWN : [chars]: AppleTalk node down; line protocol down
Explanation An AppleTalk hardware interface was disabled because of a bad serial line, a configuration command, or a bad interface.
Recommended Action If the interface was not intentionally disabled, this message indicates a hardware problem. In this case, repair or replace the applicable hardware.


%AT-5-INTRESTART : [chars]: AppleTalk interface restarting; protocol restarted
Explanation The hardware interface was reset because of a configuration change. After the reset, AppleTalk automatically reinitialized the interface.
Recommended Action No action is required.


%AT-6-INTUP : [chars]: AppleTalk interface restarting; line protocol came up
Explanation An AppleTalk interface that was previously shut down was restarted.
Recommended Action No action is required.


%AT-6-BADROUTE : Route to %#A has gone bad
Explanation The system did not detect a route within the required timeout period. Therefore, the route is marked as bad. A network might have become unreachable for some reason, perhaps because of a broken connection. This message does not necessarily indicate an error condition.
Recommended Action No action is required.


%AT-5-PATHCHANGE : Route to %#A is now using path of type [chars] on [chars] via %#a
Explanation The path to a network changed because either the old path went down or the new path was better.
Recommended Action No action is required.


%AT-5-RTMPSTATE : [chars]: RTMP path to %#A via %#a now in [chars] state (metric [dec], [dec] hops)
Explanation The state of a path changed.
Recommended Action No action is required.


%AT-6-PATHNOTIFY : [chars]: AppleTalk [chars] path to %#A down; reported bad by %#a
Explanation A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.
Recommended Action No action is required.


%AT-6-PATHADD : [chars]: AppleTalk [chars] path to network %#A added; via %#a (metric [dec])
Explanation A new AppleTalk path has been learned. The message indicates the source of the path, its distance in hops, its metric, and the type of path.
Recommended Action No action is required.


%AT-6-PATHDEL : [chars]: AppleTalk [chars] path to %#A via %#a has been deleted
Explanation A path on the AppleTalk network aged out.
Recommended Action No action is required.


%AT-6-ROUTEOK : [chars]: AppleTalk network up; %#A via %#a ([dec] hop [chars])
Explanation A routing update was received for a previously suspect route.
Recommended Action No action is required.


%AT-6-ROUTENOTIFY : [chars]: AppleTalk network down; %#A reported bad by %#a
Explanation A router went down somewhere on the AppleTalk network. The indicated peer notified this router of the change.
Recommended Action No action is required.


%AT-6-ROUTEDOWN : [chars]: AppleTalk network down; interface to %#A disabled
Explanation A connected route is being advertised as down (also known as notify neighbor) because the configured interface is no longer operational.
Recommended Action No action is required.


%AT-6-NEWROUTE : [chars]: AppleTalk network added; %#A via %#a ([dec] hop [chars])
Explanation A new AppleTalk route was learned. The message indicates the source of the route and its distance in hops.
Recommended Action No action is required.


%AT-6-DELROUTE : AppleTalk network deleted; %#A removed from routing table
Explanation A route on the AppleTalk network aged out.
Recommended Action No action is required.


%AT-6-NEWZONE : AppleTalk zone added; zone %*s defined
Explanation A new AppleTalk zone was created.
Recommended Action No action is required.


%AT-6-ZONEGC : AppleTalk zone deleted; zone [chars] released
Explanation The router removed an unused zone from the zone table.
Recommended Action No action is required.


%AT-6-NODEWRONG : [chars]: AppleTalk node %a misconfigured; reply has been broadcast
Explanation An AppleTalk node sent a GetNet Info request to this router specifying an invalid network number for the source of the GetNet Info request. This situation occurs when an AppleTalk end node is moved to another network and is therefore misconfigured for the current network.
Recommended Action No action is required.


%AT-7-BUGREPORT : AppleTalk bug: [chars]
Explanation The software detected an unexpected condition. The router takes corrective action and continues.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.


%AT-2-ASSERTFAILED : AppleTalk assertion failed: [chars]
Explanation The software detected an inconsistency. Although this error is serious, the router attempts to continue. AppleTalk processing might be impaired.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.


%AT-7-DEBUGMSG : AppleTalk debug: [chars]
Explanation This message is generated by a debug command and provides additional information about an AppleTalk condition.
Recommended Action Copy the message exactly as it appears, note any AppleTalk problems you experience, and call your technical support representative.


%AT-5-COMPATERR1 : [chars]: AppleTalk internet compatibility mode required by %#a
Explanation A neighboring router supports only extended AppleTalk networks with a cable range of 1 and with one assigned zone, for example, 25-25.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.


%AT-5-COMPATERR2 : AppleTalk neighbor incompatibility; %#A has multiple zones
Explanation Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route with multiple zone names defined. This condition can cause node inconsistencies on your AppleTalk network.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.


%AT-5-COMPATERR3 : AppleTalk neighbor incompatibility; %#A has wide cable range
Explanation Although this router has neighbors that require your internetwork to observe compatibility rules, AppleTalk has learned of a route that has a cable range greater than 1. This condition can cause node inconsistencies on your AppleTalk network.
Recommended Action Upgrade the routers that support only the original AppleTalk specification. In the meantime, observe the compatibility rules for AppleTalk Phase 1 and Phase 2 routers.


%AT-5-FDDICOMPAT : AppleTalk FDDI neighbor %#a using obsolete FDDI addressing
Explanation Another AppleTalk router on the FDDI ring is running a release of the router software earlier than 9.0(2). Routers running these early software releases use an encapsulation for AppleTalk on FDDI rings that is not compatible with the Apple FDDITalk implementation.
Recommended Action Upgrade the routers running the software releases that use the pre-FDDITalk encapsulation for AppleTalk on FDDI rings.


%AT-5-LOSTNEIGHBOR : [chars]: AppleTalk neighbor down; lost contact with %#a
Explanation A peer router is unreachable.
Recommended Action No action is required.


%AT-6-NEWNEIGHBOR : [chars]: AppleTalk neighbor added; %#a is operational
Explanation The router discovered a new AppleTalk router on the network.
Recommended Action No action is required.


%AT-6-NEIGHBORUP : [chars]: AppleTalk neighbor up; %#a has restarted
Explanation A neighboring router to which this router previously lost connectivity reappeared on the network.
Recommended Action No action is required.


%AT-5-BADNEIGHBOR : [chars]: AppleTalk neighbor ignored; %#a is misconfigured
Explanation A neighboring router's AppleTalk configuration does not agree with this router's AppleTalk configuration. This condition can result from a mismatch between the neighbor's network range and this router's network range.
Recommended Action Modify either this router's or the neighboring router's configuration so that the network ranges agree.


%AT-6-ACQUIREMODE : [chars]: AppleTalk interface initializing; acquiring [chars]
Explanation The interface is determining the correct configuration. This message is displayed when discovery mode is enabled and no other router is detected.
Recommended Action No action is required.


%AT-6-ZONEPROXY : AppleTalk proxy defined; zone [chars] using network %#A
Explanation This message reports the zone name and network number that are being advertised to support the appletalk nbp-proxy command.
Recommended Action When proxy service is initiated, this message is generated each time the appletalk nbp-proxy command is issued. LOG_STD_NO_ACTION


%AT-6-NOPROXY : AppleTalk proxy deleted; zone [chars] freed network %#A
Explanation A previously configured Name Binding Protocol (NBP) proxy was deleted. The router can no longer convert NBP requests to a format understood by routers that support only the original AppleTalk specification.
Recommended Action No action is required.


%AT-5-NOTSUPPORTED : [chars]: AppleTalk node down; line protocol not supported
Explanation An encapsulation method on the specified interface does not support AppleTalk.
Recommended Action No action is required.


%AT-5-DUPADDR : [chars]: AppleTalk interface restarting; node address taken by [enet]
Explanation Another AppleTalk node on a common network interface claimed the same AppleTalk address that this router was using. This error indicates a serious, unexpected problem. If it recurs, a physical network problem in which the nodes cannot communicate with each other might exist.
Recommended Action The interface on this router restarts AppleTalk processing on the common network interface to resolve the address conflict. LOG_STD_NO_ACTION


%AT-5-INTCLEARED : [chars]: AppleTalk interface restarting; interface cleared
Explanation A clear interface command was issued on an interface that is currently routing AppleTalk.
Recommended Action No action is required.


%AT-5-OLDMCI : [chars]: AppleTalk route cache disabled; firmware is obsolete
Explanation The firmware on the MCI controller card does not support AppleTalk fast switching.
Recommended Action No corrective action is required. Normal AppleTalk operation continues, but the fast switching cache is disabled for the interface associated with the MCI card. If this message is unexpected, verify that the MCI firmware for the interface specified in the error message is at level 1.7 or higher.


%AT-3-IFCONFLICT : [chars]: AppleTalk interface disabled; conflicts with interface [chars]
Explanation An attempt was made to configure an interface to have the same or a conflicting AppleTalk address or cable range as another interface on the same router.
Recommended Action Verify that you are not specifying an AppleTalk address or cable range used previously on this router, and reconfigure the interface.


%AT-3-SUBROUTINE_ERROR : AppleTalk error: [chars]
Explanation An internal error occurred. Specifically, a programming assertion in the AppleTalk networking code was violated.
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.


%AT-6-MACIPUP : [chars]: MacIP server operational, [IP_address]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is fully initialized and is ready to accept client requests. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.


%AT-6-MACIPDOWN : [chars]: MacIP server shutting down, [IP_address]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server is no longer operational for any reason. MacIP servers shut down in response to MacIP configuration changes or errors, or a change in the condition or configuration of an AppleTalk or IP interface for which the MacIP server is providing service. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.


%AT-4-MACIPBADCONF : [chars]: MacIP inoperable configuration, [IP_address]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server cannot begin or recover operations because of an invalid IP address configuration. This condition only occurs when the configured MacIP server's IP address is not valid on the same cable of any operable IP interface. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command. When this error occurs, the MacIP configuration is considered invalid and is deleted.
Recommended Action No action is required.


%AT-4-MACIPNOCABLE : [chars]: MacIP inoperable IP interface, [IP_address]
Explanation If the appletalk event-logging command is configured, this message appears on the console when a MacIP server can no longer operate due to a change in the condition of the IP interface it serves. This condition can occur if IP routing is shut down on the interface, or the IP address of the interface is changed so that the MacIP server's IP address is no longer valid on the same cable. The AppleTalk zone served by the MacIP server replaces the zone specified in the appletalk zone command. The IP address configured on the MacIP server replaces the IP address configured by the ip address command.
Recommended Action No action is required.


%AT-5-NOSUCHROUTE : No such route [dec]
Explanation You specified a nonexistent route in a show appletalk route or clear appletalk route command.
Recommended Action Specify a valid route, that is, one that appears in the output of the show appletalk route command.


%AT-3-NOSUCHNBR : No such neighbor, %#a
Explanation You specified a nonexistent neighbor address in a show appletalk neighbor or clear appletalk neighbor.
Recommended Action Specify a valid neighbor address, that is, one that appears in the output of the show appletalk neighbor command.


%AT-6-NBRDELETED : Neighbor entry for %#a deleted
Explanation The clear appletalk neighbor command displays this command when it completes successfully.
Recommended Action No action is required.


%AT-6-REGPENDING : NBP registration of [chars] at [[chars]] pending
Explanation A name registration call is being performed.
Recommended Action No action is required.


%AT-1-NOMEM : Could not allocate memory for [chars] at line [dec] in [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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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.


%AT-3-NOBESTPATH : Could not compute best path for network %#A
Explanation A path to the specified network could not be found.
Recommended Action Use the show appletalk route command to verify that a path to the specified network exists. If it does, copy the error message exactly as it appears, and report it along with the output of the show appletalk route command to your technical support representative.


%AT-3-NOROUTE : No route to destination %a
Explanation The router could not deliver a packet to a destination because it did not know where to send it.
Recommended Action Use the show appletalk route command to verify that a path to the destination exists. If it does, copy the error message exactly as it appears, and report it with the output of the show appletalk route command to your technical support representative.


%AT-3-CANTDEL : Cannot delete [chars] route [dec] by clearing; remove it by reconfiguring
Explanation You attempted to remove a route from the routing table by issuing the clear appletalk route command. The command failed because the route was on a directly connected interface, that is, it was created when you configured the router.
Recommended Action Remove the route by reconfiguring the directly connected interface with which it is associated.


%AT-3-INVNBPCMD : Invalid NBPtest command [chars]
Explanation An unrecognized command was specified in the Name Binding Protocol (NBP) test facility.
Recommended Action Enter a valid command.


%AT-3-OUTOFSYNC : [chars]: AURP connection out of sync...terminating
Explanation AURP detected packets that were out of sequence. This might be caused by a lost connection.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%AT-4-PATHREJECTED : AURP path %#A rejected; conflict detected
Explanation The router detected a conflicting cable range. A router is configured with a cable range that overlaps with an existing range but does not match the entry exactly.
Recommended Action Use the show appletalk command to identify the overlapped cable range, and then reconfigure the misconfigured router.


%AT-3-DOMOVERFLOW : Remap range overflow for [chars] domain [dec]
Explanation The remap range overflowed. If a network (range) cannot fit inside the remapping range, the network or cable range being advertised by a neighboring router is not accepted. When an overflow occurs, all interfaces in the domain are disabled.
Recommended Action Use the appletalk domain remap-range command to increase the remapping range. Then restart the interfaces.


%AT-3-DOMLOOP : Loop detected on domain [dec] [[chars]]
Explanation The domain router detected a routing loop. Routing loops are not allowed. The domain router runs a background loop detection process. The domain router starts this process when it receives a new zone list from a domain that is identical to the list in the main routing table and whose network range length matches that in this list. The loop detection process sends several AppleTalk NBP loopback packets. When one of these packets is received on an interface that does not belong to the original domain, the domain router first shuts off all the domains involved in the loop, and then shuts off all the interfaces in these domains. The loop detection does not catch all types of loops. It is your responsibility to make sure that no loop exists.
Recommended Action Disable the cause of the routing loop. Then use the clear appletalk command to restart the interfaces involved.


%AT-3-NOVIRTUAL : [chars]: client tried to connect, but no virtual network is declared
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%AT-3-NOSOCKET : [chars]: client tried to open socket, but failed
Explanation open socket failed;Possible out of memory situation
Recommended Action


ATA

%ATA-6-ATA_STATUS_TIMEOUT : Timeout occurred while querying the status of ATA device. Status returned :[hex], event: [dec]
Explanation A timeout occurred while querying the status of ATA device.
Recommended Action Replace the new ATA device and retry the operation. If the problem persists, (1) Run 'show tech' command. (2) Enable file system operation logs using the following commands: (a) 'debug ifs file' (b) 'debug ifs fs' (c) 'debug ifs verbose' (3) Contact the TAC or engineering team with the output of the commands.


%ATA-3-ATA_STATUS_ERROR : Error occurred while querying the status of ATA device. Return: [dec], stat_reg: [hex]
Explanation An error occurred while querying the status of ATA device. Device not responding
Recommended Action Replace the new ATA device and retry the operation. If the problem persists, (1) Run 'show tech' command. (2) Enable file system operation logs using the following commands: (a) 'debug ifs file' (b) 'debug ifs fs' (c) 'debug ifs verbose' (3) Contact the TAC or engineering team with the output of the commands.


ATMSIG through BCRDU

ATMSIG

%ATMSIG-3-FAILASSERT : Assertion failed: [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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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.


%ATMSIG-3-NOSVC : no SVC, [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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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.


%ATMSIG-3-NOCALLREF : Cannot find a Callref value to allocate: [chars]
Explanation This indicates an internal software error, probably including memory exhaustion.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-ATMSIG_SVC_INSERT_FAILED : ATMSIG([chars] [dec],[dec] - %04d/%02d) SVC wavl ins failed:svc [hex]
Explanation A software error occurred during creation of an SVC. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-ATMSIG_SVC_DELETE_FAILED : ATMSIG([chars] [dec],[dec] - %04d/%02d) SVC wavl del failed:svc [hex]
Explanation A software error occurred during closure of an SVC. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-ATMSIG_PRTY_INSERT_FAILED : ATMSIG([chars] [dec],[dec] - %04d/%02d) avl prty ins failed:svc [hex] party [hex]
Explanation A software error occurred during addition of a party to a point-to-multipoint call. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-ATMSIG_PRTY_DELETE_FAILED : ATMSIG([chars] [dec],[dec] - %04d/%02d) avl prty del failed:svc [hex] party [hex]
Explanation A software error occurred during removal of a party from a point-to-multipoint call. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-ATMSIG_CUG_INSERT_FAILED : ATMSIG([chars])
Explanation A software error occurred during addition of a member to a closed user group. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-ATMSIG_CUG_DELETE_FAILED : ATMSIG([chars])
Explanation A software error occurred during removal of a member from a closed user group. Other error messages appearing immediately prior to this one may be related.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-FAILHALFLEGREM : halfLeg removal failed, [chars]
Explanation An internal software error occurred. This message should only be displayed when verbose debugging is enabled for an SVC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-FAILXCONN : Xconnect failed, [chars]
Explanation An internal software error occurred during installation of an SVC cross-connect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-INVPNNIMSG : Invalid msg from routing/pnni : [chars]
Explanation This message indicates an error in the PNNI routing subsystem. It could be caused by an internal software error or by bad control information received from peer equipment. The message will contain additional information that can help locate the cause. Any message with 'NULL' probably indicates a problem with this system, others probably point at the peer equipment.
Recommended Action Check this system and the peer equipment for any obvious errors. LOG_STD_RECUR_ACTION


%ATMSIG-4-CONFIG_ERROR : Configuration Error: [chars] [chars]
Explanation This message indicates a configuration error in the ATM Signaling subsystem. The message will display more specific information about the problem location.
Recommended Action Change the configuration to correct the error.


%ATMSIG-3-FAIL1STHALFLEG : 1st halfLeg failed, [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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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.


%ATMSIG-3-FAIL2NDHALFLEG : 2nd halfLeg failed, [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. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit (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.


%ATMSIG-3-ENQFAIL : process_enqueue failed, [chars]
Explanation An internal software error occurred while handling a user request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-DBINITFAIL : Signalling control block initialization failure, [chars]
Explanation An internal software or resource error occurred
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-ATMSIG_LISTEN_FAILED_DUP : Duplicate LISTEN by [chars] for existing NSAP [chars] owned by [chars]
Explanation An application attempted to either LISTEN on an NSAP owned by another application or to LISTEN for the same NSAP twice
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSIG-3-PNNI_TRACE_INTERNAL : [chars]
Explanation An internal software error or unexpected condition occured during PNNI (Connection/Path) Trace related processing
Recommended Action LOG_STD_SH_CMD_ACTION(show atm pnni trace information) Also gather information about where/how trace was initiated, and for what type of VC.


ATMSPA

%ATMSPA-3-FATAL_ERROR : occurred on [chars]. Resetting SPA
Explanation The SPA has been reset due to a critical error in one of its devices. The error could either be a single occurrence of an event or multiple occurrences within a period of time. The message text on the console or in the system log provides more information on the specific nature of the error.
Recommended Action If the SPA is reset more than once, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).


%ATMSPA-4-SETUPVC : Interface [chars], VC ([dec]) setup failed, reason = [dec]
Explanation A command to setup a VC has failed on RP.
Recommended Action The SPA ATM driver has detected a problem creating the internal OAM VC. Reload the indicated SPA card to reconfigure the internal OAM VC. If the error messages persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).


%ATMSPA-4-TEARDOWNVC : Interface [chars], VC ([dec]) teardown failed, reason = [dec]
Explanation A command to remove a VC config has failed on RP.
Recommended Action The SPA ATM driver has detected a problem tearing down the internal OAM VC. Reload the indicated SPA card to do a clean tear down of the internal OAM VC. If the error messages persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).


%ATMSPA-3-SW_ERROR : [chars] Error [hex] [chars]
Explanation The specified software error has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSPA-3-HW_ERROR : [chars] Error [hex] [chars]
Explanation The specified hardware error has been detected.
Recommended Action The message text on the console or in the system log provides more information on the specific nature of the error. LOG_STD_SH_TECH_ACTION


%ATMSPA-3-KEEPALIVE_FAILURE : occurred on [chars]. Resetting SPA
Explanation One of the devices of the SPA failed to respond to keepalives due to which SPA has been reset. The message text on the console or in the system log provides more information on which device failed to respond.
Recommended Action If the SPA is reset more than once, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at BUG_TOOLKIT If you still require assistance, open a case with the Technical Assistance Center via the Internet at TAC_CASE_OPEN or contact your Cisco technical support representative. Be sure to provide the information you have gathered and <cmdBold>show tech-support<nocmdBold> to your support representative, or attach it to your case


%ATMSPA-3-DATA_ERROR : [chars] Error [hex] [chars]
Explanation A datapath protocol violation or sequence error has been detected.
Recommended Action The message text on the console or in the system log provides more information on the specific nature of the error. LOG_STD_SH_TECH_ACTION


%ATMSPA-3-GEN_ERROR : [chars] Error [hex] [chars]
Explanation The specified error has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%ATMSPA-2-INITFAIL : [chars] - Init Failed return code: [int]
Explanation The SPA failed to complete hardware initialization. One of the devices in the SPA failed to initialize successfully. Information about the failed device is specified in the message text on the console or in the system log.
Recommended Action Please power down and reseat the indicated SPA card. If the condition persists, copy the error message exactly as it appears. Next research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case or contact your Cisco technical support representative. Be sure to provide the the information you have gathered and a 'show tech-support' to your support representative, or attach it to your case in non-zipped, plain text format (.txt).


%ATMSPA-4-VCSETUP : [chars]: VC setup command received on the LC for an existing VC (VCD [dec])
Explanation A command to set up a VC has been received for a VC that has already been set up. The VC has already been configured by a previous setup VC command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the LC for the previous setup command.
Recommended Action No action is required.


%ATMSPA-4-VCTEARDOWN : [chars]: VC tear down command received on the LC for a non-existing VC (VCD [dec])
Explanation The VC does not exist on the LC. Most likely, it has been torn down by a previous teardown command from RP. A duplicate teardown command may indicate that the RP did not receive a response from the LC for the previous teardown command.
Recommended Action No action is required.


%ATMSPA-4-VPSETUP : [chars]: VP setup command received on the LC for an existing VP (VPI [dec])
Explanation A command to set up a VP has been received for a VP that has already been set up. The VP has already been configured by a previous setup VP command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the LC for the previous setup command.
Recommended Action No action is required.


%ATMSPA-4-VPTEARDOWN : [chars]: VP tear down command received on the LC for a non-existing VP (VPI [dec])
Explanation The VP does not exist on the LC. Most likely, it has been torn down by a previous teardown command from RP. A duplicate teardown command may indicate that the RP did not receive a response from the LC for the previous teardown command.
Recommended Action No action is required.


%ATMSPA-3-VCQ_ERROR : [chars]: VC queue configuration failed due to un-initialized queue table (global identifier [dec])
Explanation Software configuration of a VC queue failed due to un-initialized queue table.
Recommended Action Attempt to perform a soft OIR operation by entering the command that is described in the shared port adapter software configuration guide. If the condition persists, copy the error message exactly as it appears, and report it to your technical support representative. Also supply a 'show tech-support' at that time.


%ATMSPA-3-QOS_ALLOC_FAILED : [chars] [chars] [chars]: [dec]
Explanation Traffic shaping parameters could not be configured because the number of unique shaping parameters that are configured on the PVCs or PVPs in this specified ATM SPA is over the maximum limit. The maximum number of unique shaping parameters that can be configured on the PVCs or PVPs is 4096.
Recommended Action Ensure that the total number of unique shaping parameters that are configured on both PVCs and PVPs does not exceed the maximum limit of 4096.


%ATMSPA-3-FPD_VER_DEPENDENCY_NOTE : Cannot perform the requested FPD update operation because [chars] in subslot [int]/[int] has incompatible HW version [int].[int] with FPD image version [dec].[dec] for FPD ID [dec]. Only image version greater than [int].[int] can be used in the update operation of [chars] with HW version greater than [int].[int].
Explanation The version of the FPD image from the FPD image bundle or package is not compatible with the HW version of the target card
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.


%ATMSPA-3-ATM_SPA_AUTOVC_FAIL : [chars]: atm autovc discovery configuration failed, reason: [chars]
Explanation A command to configure the atm autovc discovery on an atm interface has 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.


ATMSSCOP

%ATMSSCOP-4-UNMATCHUNIVERSION : ([chars]): [chars]. Please verify peer UNI version
Explanation The ATM peer equipment appears to be running an old version of ATM UNI. Communication with it is not possible.
Recommended Action The ATM peer equipment may need attention. Please verify its UNI version is at least 3.1, and upgrade if necessary.


%ATMSSCOP-3-SSCOPERR : INIT SSCOP -Intf : [chars], Event : [chars], State : [chars].
Explanation A software error occurred in the ATM SSCOP subsystem.
Recommended Action LOG_STD_SH_CMD_ACTION


%ATMSSCOP-5-SSCOPINIT : - Intf : [chars], Event : [chars], State : [chars].
Explanation This message indicates a routine step of the ATM SSCOP initialization sequence.
Recommended Action LOG_STD_NO_ACTION


ATTN

%ATTN-2-MBOX_REG_FAIL : return code [dec]
Explanation Registration of handler function for mailbox event failed mailbox event failed.
Recommended Action LOG_STD_ACTION


%ATTN-2-PROXY_INIT_FAIL_IPC_REG : return code [dec]
Explanation Initialization of attention proxy failed due to error registering IPC handler function.
Recommended Action LOG_STD_ACTION


%ATTN-3-PROXY_UNHANDLED_MSG : subtype [dec]
Explanation Attention proxy received a message with an unknown subtype.
Recommended Action LOG_STD_ACTION


%ATTN-3-PROXY_IPC_ALLOC_FAILED : [chars]
Explanation Allocation of an IPC packet buffer by the attention proxy failed.
Recommended Action LOG_STD_ACTION


%ATTN-3-PROXY_IPC_SEND_FAILED : [chars]
Explanation Transmission of an IPC message by the attention proxy failed.
Recommended Action LOG_STD_ACTION


%ATTN-3-SYNC_TIMEOUT : msecs since last timeout [int], missing packets [dec]
Explanation Attention sync command timed out.
Recommended Action LOG_STD_ACTION


AUTHMGR

%AUTHMGR-5-START : Starting '[chars]' for client ([enet]) on Interface [chars] AuditSessionID [chars]
Explanation Starting an authentication method
Recommended Action No action is required.


%AUTHMGR-5-SUCCESS : Authorization succeeded for client ([enet]) on Interface [chars] AuditSessionID [chars]
Explanation Authorization was successful.
Recommended Action No action is required.


%AUTHMGR-5-FAIL : Authorization failed or unapplied for client ([enet]) on Interface [chars] AuditSessionID [chars]
Explanation Authorization was unsuccessful.
Recommended Action No action is required.


%AUTHMGR-5-VLANASSIGN : VLAN [dec] assigned to Interface [chars] AuditSessionID [chars]
Explanation VLAN assignment
Recommended Action No action is required.


%AUTHMGR-5-SECURITY_VIOLATION : Security violation on the interface [chars], new MAC address ([enet]) is seen. AuditSessionID [chars]
Explanation A host on the specified interface is attempting to gain access into the network or is trying to authenticate in a host mode that does not support the number of hosts attached. This is treated as a security violation and the port has been error-disabled.
Recommended Action Ensure that the port is configured to support the number of hosts attached. Enter the shutdown command followed by no shutdown command to restart the port.


%AUTHMGR-7-FAILOVER : Failing over from '[chars]' for client ([chars]) on Interface [chars] AuditSessionID [chars]
Explanation Failing over from the current authentication method
Recommended Action No action is required.


%AUTHMGR-7-STOPPING : Stopping '[chars]' for client [enet] on Interface [chars] AuditSessionID [chars]
Explanation Stopping the current authentication method
Recommended Action No action is required.


%AUTHMGR-7-NOMOREMETHODS : Exhausted all authentication methods for client ([chars]) on Interface [chars] AuditSessionID [chars]
Explanation All available authentication methods have been tried
Recommended Action No action is required.


%AUTHMGR-5-MACMOVE : MAC address ([enet]) moved from Interface [chars] to Interface [chars] AuditSessionID [chars]
Explanation Client has moved to a new interface without logging off on the previous one.
Recommended Action No action is required.


%AUTHMGR-5-MACREPLACE : MAC address ([enet]) on Interface [chars] is replaced by MAC ([enet]) AuditSessionID [chars]
Explanation A new client has triggered a violation causing an existing client to be replaced
Recommended Action No action is required.


%AUTHMGR-4-UNAUTH_MOVE : [chars] MAC address ([enet]) from [chars] to [chars]
Explanation Move while not authenticated on old IDB
Recommended Action No action is required.


%AUTHMGR-4-ILLEGAL_TRACE_REQ : Component ID [dec] not registered.
Explanation Attempt to log a message with unregistered ID.
Recommended Action No action is required.


%AUTHMGR-0-CONFIG_CORRUPT : Checksummed interface configuration corruption detected.
Explanation Interface configuration field was modified unexpectedly.
Recommended Action No action is required.


AUTOSEC

%AUTOSEC-3-CONFSAVE_FAIL : Applying AutoSecure config to running-conf failed with error [dec]
Explanation Configuration of the AutoSecure session could not be applied to the running configuration
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.


%AUTOSEC-5-ENABLED : AutoSecure is configured on the device
Explanation Security configuration of the device is done using AutoSecure.
Recommended Action Notification message only. No action required.


AUTO_FPD

%AUTO_FPD-5-FRU_HWPRG_UPG_START : [chars] in slot [chars] are upgrading, \ please don't reload or power-cycle this card.
Explanation The hw-programmable firmware is upgrading
Recommended Action No action is required. This is informational message


%AUTO_FPD-5-FRU_HWPRG_UPG_SUCCESS : [chars] in slot [chars] are successfully programmed.
Explanation The hw-programmable was upgraded succesfully
Recommended Action No action is required. This is informational message


%AUTO_FPD-3-FRU_HWPRG_UPG_FAILED : [chars] in slot [chars] failed to program. error: [chars]
Explanation The hw-programmable was upgraded failed
Recommended Action Retry upgrade


%AUTO_FPD-3-FRU_HWPRG_UPG_ERR : Error reason:[chars]
Explanation Some error occurred during auto upgrade
Recommended Action Retry upgrade


AUTO_UPGRADE

%AUTO_UPGRADE-5-AUTO_ADVISE_SW_CONV : [chars] [dec] running bundled software has been added to the stack that is running installed software.\The 'install autoupgrade' command can be used to convert [chars] [dec] to the installed running mode by \installing its running software.
Explanation No explanation required.
Recommended Action No specific action required.


%AUTO_UPGRADE-5-AUTO_ADVISE_SW_BUNDLED : switch [dec] running installed software has been added to the stack.\Switch [dec] must be running bundled software in order to join the stack.
Explanation No explanation required.
Recommended Action Boot the member with compatible software.


%AUTO_UPGRADE-3-AUTO_ADVISE_SW_COM_BUNDLED : Switch [dec] running incompatible bundled software has been added to the stack. \Switch [dec] must be running compatible bundled software in order to join the stack.
Explanation No explanation required.
Recommended Action Boot the member with compatible software.


%AUTO_UPGRADE-3-AUTO_UPGRADE_MODE_UNKNOWN : Switch [dec] has been added to the stack. Failed to initiate auto upgrade \for switch [dec] because switch [dec] is not running installed or bundled software
Explanation No explanation required.
Recommended Action Boot the member with compatible software.


%AUTO_UPGRADE-3-AUTO_ADVISE_SW_MODE_UNKNOWN : Switch [dec] has been added to the stack. Failed to initiate auto advise \for switch [dec] because switch [dec] is not running installed or bundled software
Explanation No explanation required.
Recommended Action Boot the member with compatible software.


%AUTO_UPGRADE-3-AUTO_UPGRADE_INTERNAL_ERROR : Local chassis/RP number did not publish yet
Explanation Somehow the chassis/FRU number is missing.
Recommended Action Try to do it again.


%AUTO_UPGRADE-3-AUTO_UPGRADE_NOT_SUPPORTED : The system is not running installed software. Auto upgrade for [chars] [dec] cannot be initiated
Explanation A system with incompatible software has been detected in the stack. The auto upgrade functionality cannot be \initiated because the stack/HA system is not running installed software. The user must manually upgrade the incompatible switch/FRU.
Recommended Action Perform the one shot cli to convert system is install mode. Boot the system from the boot directory (bootflash/harddisk) using 'boot bootflash:packages.conf'


%AUTO_UPGRADE-5-AUTO_UPGRADE_CONV : Converting [chars] [dec] to installed mode by installing its running software.
Explanation This needs to be converted as part of the auto upgrade.
Recommended Action No action is required.


%AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_DISK : [chars] [dec] doesn't have enough free disk space to perform auto upgrade. A minimum of [dec] KB of free disk space is required \Initiating the auto-delete of the old images on joining member/FRU. (Default is oldest image in configuration mode)
Explanation There might be older files because of which there is not enough memory.
Recommended Action Clean up disk space in the remote switch.


%AUTO_UPGRADE-3-SMU_UPGRADE_FAILED_DISK : Switch [dec] doesn't have enough free disk space to sync SMU. A minimum of [dec] KB of free disk space is required. Auto upgrade will pass with out syncing SMUs on this switch
Explanation There might be older files because of which there is not enough memory.
Recommended Action Clean up disk space in the remote switch.


%AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_MEM : [chars] [dec] doesn't have enough free memory to perform auto upgrade. A minimum of [dec] KB of free memory is required
Explanation There might be older files because of which there is not enough memory.
Recommended Action Clean up disk space in the remote switch.


%AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_EXPAND : Failed to install the running software on switch [dec]
Explanation TODO: add an explanation.
Recommended Action No action required.


%AUTO_UPGRADE-3-SMU_SYNC_FAILED : SMU upgrade failed on switch [dec]. Auto upgrade of image will pass with out syncing SMUs on this switch. SMUs will be synced at boot time of the switch [dec]
Explanation SMU sync failed because of some reason.
Recommended Action No action required, SMU sync will be tried in next reload.


%AUTO_UPGRADE-5-SMU_RB_SYNC_FAILED : SMU rollback sync failed on [chars]. Rollback operations may be affeced
Explanation SMU rollback sync failed on some reason. Most probable causes are SMUs are not present on the media or the media is full.
Recommended Action Bring back the SMUs deleted and check whether there is enough space in remote member/SMUs


%AUTO_UPGRADE-3-AUTO_UPGRADE_ROMMON_NOT_UPDATED : Unable to confirm boot config on [chars] [dec], assuming it is set as [chars].
Explanation TODO: add an explanation.
Recommended Action NO action is required.


%AUTO_UPGRADE-5-AUTO_UPGRADE_RELOAD : Reloading [chars] [dec] to complete the auto upgrade.
Explanation Part of autoupgrade
Recommended Action Just wait until the reload completes.


%AUTO_UPGRADE-5-AUTO_UPGRADE_START_CHECK : Auto upgrade start checking for incompatible switches.
Explanation Part of autoupgrade
Recommended Action NO action is required.


%AUTO_UPGRADE-5-AUTO_ADVISE_SW_SEARCH : Searching stack for software to upgrade [chars] [dec].
Explanation Just an init message.
Recommended Action No action is required.


%AUTO_UPGRADE-5-AUTO_UPGRADE_SEARCH : Searching stack for software to upgrade [chars] [dec].
Explanation Just an init message.
Recommended Action No action is required.


%AUTO_UPGRADE-5-AUTO_ADVISE_SW_FOUND : Found donor switch [dec] to auto upgrade switch [dec].
Explanation Just an init message.
Recommended Action No action is required.


%AUTO_UPGRADE-5-AUTO_UPGRADE_FOUND : Found donor [chars] [dec] to auto upgrade [chars] [dec].
Explanation Just an init message.
Recommended Action No action is required.


%AUTO_UPGRADE-5-AUTO_ADVISE_SW_START : Upgrading [chars] [dec] with software from [chars] [dec].
Explanation Just an init message.
Recommended Action No action is required.


%AUTO_UPGRADE-5-AUTO_UPGRADE_START : Upgrading [chars] [dec] with software from [chars] [dec].
Explanation Just an init message.
Recommended Action No action is required.


%AUTO_UPGRADE-5-AUTO_ADVISE_SW_INITIATED : Auto advise initiated for [chars] [dec].
Explanation A system with incompatible software has been detected in the stack. The stack will now determine whether or not \software is available to be copied to the incompatible system, and if so, advise the user how to copy it. \Otherwise, the system will merely let the user know that the software on the stack needs to be updated.
Recommended Action No action is required.


%AUTO_UPGRADE-5-AUTO_UPGRADE_INITIATED : Auto upgrade initiated for [chars] [dec].
Explanation A system with incompatible software has been detected in the stack. The stack will first attempt to download \software from a previously-configured location, and install it to make the system compatible. If this is not successful, the stack will then determine whether \running software on another stack member is available to be copied to the incompatible system, and \whether or not it is appropriate to copy the software automatically
Recommended Action No action is required.


%AUTO_UPGRADE-3-AUTO_UPGRADE_PLATMISMATCH : No software was found to upgrade [chars] [dec]
Explanation Happens because of incompatible switches. For example, ngwc and non-ngwc ones are incompatible
Recommended Action Plugin compatible switches for autoupgrade to run.


%AUTO_UPGRADE-3-AUTO_CONF_EXEC : Auto upgrade is enabled by config. Please disable auto upgrade configuration to execute auto upgrade manually using exec CLI.
Explanation TODO: add an explanation.
Recommended Action TODO: add an action


%AUTO_UPGRADE-5-AUTO_ADVISE_SW_MSG : [chars] [dec] with incompatible software has been added to the system/stack. \all system/stack members were scanned and it has been determined that the\ 'install autoupgrade' command can be used to install compatible software on [chars] [dec].
Explanation TODO: add an explanation.
Recommended Action TODO: add an action


%AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_COPY : Failed to copy upgrade packages from [chars] [dec] to [chars] [dec].
Explanation TODO: add an explanation.
Recommended Action TODO: add an action


%AUTO_UPGRADE-5-AUTO_UPGRADE_RELOAD_INSTALLED : Reloading [chars] [dec] to boot in installed mode.
Explanation TODO: add an explanation.
Recommended Action TODO: add an action


%AUTO_UPGRADE-5-AUTO_UPGRADE_INSTALLED : Finished installing the running software on [chars] [dec].
Explanation TODO: add an explanation.
Recommended Action TODO: add an action


%AUTO_UPGRADE-5-AUTO_UPGRADE_FINISH : Finished installing software on [chars] [dec].
Explanation TODO: add an explanation.
Recommended Action TODO: add an action


%AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_PLATFORM : Failed to determine platform hardware type of [chars] [dec]
Explanation Somehow the platform type could not determined.
Recommended Action Add an action


%AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_STATE : A previous provisioning action is pending reboot. Please reboot the [chars] [dec].
Explanation The user has run an operation that requires a reboot to take action.
Recommended Action Reload the switch


%AUTO_UPGRADE-3-AUTO_ADVISE_SW_FAILED_PLATFORM : Failed to determine platform hardware type of switch [dec]
Explanation Somehow the platform type could not determined.
Recommended Action Add an action


%AUTO_UPGRADE-3-AUTO_UPGRADE_NOTHING_TO_UPGRADE : No incompatible standby/member is found, nothing to auto-upgrade.
Explanation Exec autoupgrade scenario when there is no incompatible member in stack.
Recommended Action No action is required from the user


%AUTO_UPGRADE-3-AUTO_UPGRADE_NOTHING_TO_CLEAN : Couldn't find enough old install images on incompatible standby/member for deletion.\ Please manually free up [dec] MB space on incompatible standby/member and try again using 'install autoupgrade'.
Explanation If there is no old images are found on joining standby/member's boot directory
Recommended Action User will have to manually delete old files using IOS delete command


AUTO_UPGRADE_MODULAR

%AUTO_UPGRADE_MODULAR-5-SMU_AUTO_UPGRADE_INITIATING : Initiating SMU autoupgrade for [chars] [dec]
Explanation No explanation required.
Recommended Action Boot the member with same software.


%AUTO_UPGRADE_MODULAR-5-AUTO_ADVISE_SW_MISSMATCH : Active and standby are running differnt versions, SMUs will not be synced.
Explanation No explanation required.
Recommended Action Boot the member with same software.


%AUTO_UPGRADE_MODULAR-5-AUTO_NOTICE_STBY_RELOAD : Installing SMUs on standby. Standby will reload
Explanation No explanation required.
Recommended Action No action required.


%AUTO_UPGRADE_MODULAR-5-AUTO_NOTICE_RUN_MISSMATCH_STBY_RELOAD : Missmatch between running version of SMUs. Trying to recover. Standby will reload
Explanation There is a missmatch on the running version. This will happen when the standby reloads after activate/deactivate and before commit. The machine will try to correct it. One reload is required for correcting the chanages.
Recommended Action No action required.


%AUTO_UPGRADE_MODULAR-3-AUTO_NOTICE_RUN_CORRECTION_FAILED : Failed to correct the SMU mismatch between the running version on active and standby. Pls abort the smu installation using 'install abort'
Explanation The system tried to recover from the missmatch, but failed. Engineer intervention is required
Recommended Action Get the 'show install log' and the btrace logs from active and standby


%AUTO_UPGRADE_MODULAR-3-AUTO_ERR_SMU_SYNC_FAILED : Failed to sync SMUs to standby. Make sure that SMU files are present on active and there is space enough to copy SMUs on standby.
Explanation SMU sync failed. Most probable cause are the smu files may have been removed from the active switch using IOS/linux commands. Another reason is there is no space enough to copy the files to the standby
Recommended Action If the files are removed from the active bring it back to same location. Make sure there is enough space to copy the files on the standby


BCRDU

%BCRDU-3-PATCH_ACTIVATE_FAIL_MESSAGE : Failed to activate patch. The patch name is [chars] and the reason is: [chars]
Explanation During system reload, all committed patches will be automatically activated.For some reason, a patch activation fails.
Recommended Action Check [bcrdu] ERR entries in the log files for message reporting problems.


BFD_HA through BRI

BFD_HA

%BFD_HA-2-RESOURCE : [chars]
Explanation System resource error occured
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.


%BFD_HA-2-CF : [chars][dec]
Explanation CF related 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.


%BFD_HA-2-ET : [chars][dec]
Explanation Enhanced-timer 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.


BFD_ISSU

%BFD_ISSU-2-INIT : BFD ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation The BFD ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.
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.


%BFD_ISSU-3-TRANSFORM_FAIL : bfd ISSU client [chars] transform failed for message [dec]'. Error: [dec] ([chars])
Explanation The BFD ISSU client could not transform the specified message type. If the transmit transformation failed, the checkpoint message was not sent to the standby device. If the receive transformation failed, the checkpoint message was not applied on the standby device. In both cases, the BFD state between the active device and the standby device is not identical.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated version <session_id>)


%BFD_ISSU-2-GET_BUFFER : BFD ISSU client failed to get buffer for message. Error: [dec] ([chars])
Explanation The BFD ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)


%BFD_ISSU-2-SEND_NEGO_FAILED : BFD ISSU client failed to send negotiation message. Error: [dec] ([chars])
Explanation The BFD ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show logging and show checkpoint client)


%BFD_ISSU-2-SESSION_NEGO : BFD ISSU client encountered unexpected client nego_done. Error: [dec] ([chars])
Explanation An ISSU-compliant client transitions through a series of internal states. The BFD ISSU client encountered a 'client negotiation done' state that was unexpected. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>)


%BFD_ISSU-2-SESSION_REGISTRY : BFD ISSU client failed to register session information. Error: [dec] ([chars])
Explanation The BFD ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>)


%BFD_ISSU-3-SESSION_UNREGISTRY : BFD ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The BFD ISSU client failed to unregister session information.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu session <client_id> and show issu negotiated capability <session_id>)


%BFD_ISSU-3-MSG_SIZE : BFD ISSU client failed to get the MTU for Message Type [dec]. Error: [dec] ([chars])
Explanation The BFD ISSU client failed to calculate the MTU for the specified message. The BFD ISSU client is not able to send the message to the standby device.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu message group <client_id> and show issu session <client_id> and show issu negotiated version <session_id>)


%BFD_ISSU-3-INVALID_SESSION : BFD ISSU client does not have a valid registered session.
Explanation The BFD ISSU client does not have a valid registered session.
Recommended Action LOG_STD_SH_CMD_ACTION( show issu capability entries <client_id> and show issu session <client_id> and show issu negotiated capability <session_id>)


BFD_OFFLOAD

%BFD_OFFLOAD-3-INIT_FAILED : Initialization of the BFD Offload feature in QFP failed
Explanation Initialization of the BFD Offload feature in the QFP failed. This indicates a software 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.


%BFD_OFFLOAD-3-ALLOC_FAILED : Allocation of [chars] memory failed for BFD Offload feature in QFP
Explanation Allocation of memory by the QFP BFD Offload feature microcode failed. The name of the memory chunk is specified in the message. This indicates a software 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.


%BFD_OFFLOAD-3-PKT_REPLICA_INIT_FAILED : Failed to register with generic packet replication for BFD Offload feature in QFP
Explanation BFD Offload initialization of packet replication registration 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.


%BFD_OFFLOAD-3-HA_INVALID_STATE : state [dec], MSGDEF_LIMIT_MEDIUM
Explanation An invalid HA state was received from the HA infrastructure.
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.


%BFD_OFFLOAD-3-HA_BULK_SYNC_FAIL : rg [dec], MSGDEF_LIMIT_MEDIUM
Explanation There was a failure such that BFD Offload domain bulk sync did not occur
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.


BFD_PROXY

%BFD_PROXY-3-BFD_MEM_REQ_FAILED : BFD IPC subtype: [dec]
Explanation Requesting more memory 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.


%BFD_PROXY-3-BFD_MEM_EXTEND_FAILED : BFD IPC subtype: [dec]
Explanation Extending memory 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.


%BFD_PROXY-4-PROXY_INVALID_MSG_LEN : QFP BFD Proxy IPC invalid length, [dec]:[dec] len [dec] flags [hex] source [dec]
Explanation Cisco internal software error. QFP BFD Proxy received invalid IPC message length from control plane. This message will be ignored.
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.


%BFD_PROXY-4-PROXY_INVALID_MSG : QFP BFD Proxy received invalid message type [dec]
Explanation Cisco internal software error. QFP BFD Proxy received an invalid message from control plane. This message will be ignored.
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.


%BFD_PROXY-2-PROXY_IPC_INIT_FAILED : QFP BFD Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP BFD Proxy initialization detected that the IPC interface initialization failed. QFP BFD proxy will not be functional while this condition exists.
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.


%BFD_PROXY-3-PROXY_BAD_MSG : QFP BFD Proxy received bad length message type [dec]
Explanation Cisco internal software error. QFP BFD Proxy received a corrupted message from control plane. This message will be ignored.
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.


%BFD_PROXY-3-PROXY_IPC_ALLOC_FAILED : QFP BFD Proxy [chars] message lost due to message buffer allocation failure.
Explanation Cisco internal software error. QFP BFD Proxy message processing detected a message buffer allocation failure. The message is lost as the result of this condition.
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.


%BFD_PROXY-3-PROXY_IPC_SEND_FAILED : QFP BFD Proxy [chars] message lost due to message sent failure (result: [dec]).
Explanation Cisco internal software error. QFP BFD Proxy message processing detected a message sent failure. The message is lost as the result of this condition.
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.


BINOS_LOGIN

%BINOS_LOGIN-3-AUTHERR : The authentication process failed, [chars]
Explanation This error occurs when there is an error in the system that prevents the user from being successfully authenticated
Recommended Action No action is required.


%BINOS_LOGIN-3-PWNOENT : No entry for user [chars] in passwd file
Explanation The username/password authenticated correctly, but the user's environment could not be established because the user's environment data is missing.
Recommended Action No action is required.


%BINOS_LOGIN-3-PAMERR : PAM error [chars] encountered.
Explanation The system encountered a PAM error.
Recommended Action No action is required.


%BINOS_LOGIN-6-PAMAUTHDENY : User was not authenticated
Explanation User was not authenticated
Recommended Action No action is required.


%BINOS_LOGIN-6-PAMMAXTRIES : Maximum number of retries exceeded.
Explanation The user tried and failed too many times to login.
Recommended Action No action is required.


%BINOS_LOGIN-3-NOTROOT : login attempted to run without proper credentials.
Explanation login can not be run without proper credentials.
Recommended Action No action is required.


%BINOS_LOGIN-3-NOTTY : login attempted but stdin is not a tty
Explanation login can not be run without stdin set to tty
Recommended Action No action is required.


BIPC

%BIPC-3-BIPC_PERFORMANCE : buffer size request [int] failed
Explanation An internal buffer allocation has failed.
Recommended Action No action is required. If the problem persists, or router performance is noticeably degraded, contact Cisco technical support. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


BIPCMGR

%BIPCMGR-3-INVALID_TDL_ERROR_ON_MARSHAL : TDL epoch error on marshal [dec] unexpected: [chars]
Explanation The bipc manager has attempt to marshal a message to be sent. The tdl library has generated an error on marshal that is unexpected. The message was not sent.
Recommended Action This is unexpected. Report this to Cisco TAC


BOOST_PERFORMANCE

%BOOST_PERFORMANCE-2-CONFIG_REMOVED : Boost capability removed. Throughput will be defaulted on next reload. Reason: [chars]
Explanation Device no longer support boost throughput level
Recommended Action


BOOT

%BOOT-0-DRV_INITFAIL : [chars] driver failed to initialize properly
Explanation A kernel driver that is critical to the functioning of the system failed to initialialize properly.
Recommended Action Note the time of the error message and check the kernel error logs for additional information on the problem. If you are unable to resolve this problem, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.


%BOOT-0-DRV_LOADFAIL : Failed to load driver [chars] ( [chars] )
Explanation A kernel driver that was critical to the functioning of the system failed to load.
Recommended Action Note the time of the error message and check the kernel error logs for additional information on the problem. If you are unable to resolve this problem, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.


%BOOT-6-DRV_LOAD : Loaded driver [chars]
Explanation A kernel driver that was critical to the functioning of the system was successfully loaded.
Recommended Action No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only.


%BOOT-3-APP_STARTFAIL : Failed to launch process [chars]
Explanation A process that does not affect the forwarding of network traffic failed to start.
Recommended Action If the failed process is not something that needs to be corrected, do not address this message. If the failed process needs to be addressed, install new software and reload the router.


%BOOT-0-APP_STARTFAILCRIT : Failed to launch a critical process [chars]
Explanation A process important to the chassis has failed.
Recommended Action Note the time of the message and investigate the error message logs to learn more about the problem. If the problem persists or cannot be resolved, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.


%BOOT-6-APP_START : The process [chars] has started
Explanation The process has successful launched and begun executing.
Recommended Action No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only.


%BOOT-3-DUAL_BOOT_MEMORY : Dual IOS boot indicated in ROMMON ([chars]), unavailable on [chars] RP
Explanation Running two IOS instances on the same RP is unavailable on route-processors with insufficient memory
Recommended Action Unset the specified ROMMON variable or increase the memory on the route-processor.


%BOOT-3-PARTIAL_CORE_CLEANUP_FAILURE : Partial core clean up failed for [chars]: [chars]
Explanation During RP boot, a failure occurred cleaning up incomplete core files.
Recommended Action Please check the router file systems.


%BOOT-6-PARTIAL_CORE_REMOVED : Removed incomplete core file: [chars]
Explanation On boot of the RP, an incomplete core file was found and removed. Incomplete core files can happen for a variety or reasons, including the coincident failure of the active RP while a core file is being generated.
Recommended Action No action required. This is not an error, it is an indication that the system is cleaning up a previous error.


%BOOT-3-EXT_ISSU_CHK_FAILED : Detected booting up of standby RP with image beyond the ISSU domain of active RP by the [chars] process. The standby RP is forced to reset.
Explanation If standby RP is booted up with an image which is beyond the ISSU software domain of the active RP's image, the functionality of active RP may be unpredictable. Hence the standbby is being reset.
Recommended Action Remove the standby RP FRU from the chassis or boot it up with an image whose version is compatible with current running active RP.


%BOOT-3-FLASH_READ_FAIL : failed to get [chars] from flash
Explanation Property not populated.
Recommended Action No user action is necessary. This is informative message.


%BOOT-3-BOOTTIME_INCOMPATIBLE_SW_DETECTED : Incompatible software detected. Details: [chars]
Explanation Incompatible software is detected on target fru/chassis.
Recommended Action Upgrade manually or check auto-upgrade configuration.


%BOOT-3-BOOTTIME_MISMATCH_RESTRICTED_STACK_SETUP_DETECTED : Mismatch detected. Details: [chars]
Explanation Incompatible stacked setup detected on target fru/chassis.
Recommended Action Switch with mismatch require to be reloaded


%BOOT-5-BOOTTIME_SMU_MISMATCH_DETECTED : SMU mismatch from active detected. SMUs will be copied and switch [chars] will be reloaded
Explanation SMU mismatch found on newly joined switch.
Recommended Action Switch with mismatch will be reloaded


%BOOT-5-BOOTTIME_SMU_RUN_MISMATCH_DETECTED : Running SMU mismatch from active dectected. System will try to correct it, switch [chars] will be reloaded
Explanation Running version of SMU mismatch found on newly joined switch.
Recommended Action Stack will try to correct itself.


%BOOT-3-BOOTTIME_SMU_SYNC_FAILED : Failed to copy the SMUs to switch [chars]. Reload cancelled and switch will be declared incompatible
Explanation SMU sync failed on newly joined switch.
Recommended Action Switch with mismatch will be declared incompatible. Check the space on the remote switch. Check whether the file is present on active.


%BOOT-5-BOOTTIME_RB_SYNC_FAILED : Failed to sync the SMUs to switch [chars]. Install rollback operation may get affected.
Explanation Rollback point sync failed on newly joined switch.
Recommended Action Switch will not have the rollback points. Check the space on the remote switch.


%BOOT-3-BOOTTIME_SMU_RUN_CORRECTION_FAILED : Failed to correct the SMU mismatch between the running version on active and [chars]. Pls abort the smu installation using 'install abort'
Explanation The system tried to recover from the missmatch, but failed. Engineer intervention is required
Recommended Action Get the 'show install log' and the btrace logs from active and standby


%BOOT-3-BOOTTIME_SMU_MISSING_DETECTED : SMU file [chars] missing and system impact will be unknown
Explanation SMU file not found during bootup.
Recommended Action System will be running without the fix from the SMU


%BOOT-5-BOOTTIME_SMU_TEMP_ACTIVE_DETECTED : SMU file [chars] active temporary... SMU commit is pending
Explanation SMU file is active temporary and 'install commit' needs to be run to make it permanent. Else reload without commit will deactive this SMU.
Recommended Action Execute 'install commit' before reload to make activate permanent.


%BOOT-5-BOOTTIME_SMU_TEMP_DEACTIVE_DETECTED : SMU file [chars] deactive temporary... SMU commit is pending
Explanation SMU file is deactive temporary and 'install commit' needs to be run to make it permanent. Else reload without commit will active this SMU again.
Recommended Action Execute 'install commit' before reload to make deactivate permanent.


%BOOT-0-BOOT_COMPLETE_FAIL : Critical boot tasks failed: [chars]
Explanation The system has encountered a critical failure preventing successful boot.
Recommended Action Note the time of the error message and system logs for additional information on the problem. If you are unable to resolve this problem, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.


%BOOT-3-SYSD_STARTFAIL : Failed to launch boot task [chars] ( [chars] )
Explanation A boot task failed to start.
Recommended Action If the failed boot task is not something that needs to be corrected, do not address this message. If the failed boot task needs to be addressed, install new software and reload the router.


BRI

%BRI-1-NOMEMORY : msgtxt_nomemory
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%BRI-1-INITFAIL : msgtxt_initfail
Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.


%BRI-4-NOSWITCH : msgtxt_initfail
Explanation ISDN leased line requires an ISDN switch type configure.
Recommended Action Choose and configure a BRI switch type; if unsure, choose any switch.


%BRI-4-OVERSIZE_D_MTU : Failed to set MTU of [dec] on [chars]. Can't support MTU over [dec].
Explanation User config IP MTU size not supported by BRI hardware.
Recommended Action Reconfigure IP MTU base on the suggested range.


%BRI-4-OVERSIZE_B1_MTU : Failed to set MTU of [dec] on [chars]. Can't support MTU over [dec].
Explanation User config IP MTU size not supported by BRI hardware.
Recommended Action Reconfigure IP MTU base on the suggested range.


%BRI-4-OVERSIZE_B2_MTU : Failed to set MTU of [dec] on [chars]. Can't support MTU over [dec].
Explanation User config IP MTU size not supported by BRI hardware.
Recommended Action Reconfigure IP MTU base on the suggested range.


BSC through CALL_CONTROL

BSC

%BSC-3-BADPEERTYPE : Peer [chars] is incorrect type
Explanation This message occurs only when BSC local-ack is configured. It indicates the serial interfaces that are using the BSTUN tunnel are configured incorrectly, that is, both have been configured as a secondary.
Recommended Action Reconfigure the serial interfaces correctly to be a primary and secondary pair.


%BSC-2-NOMEM : No buffers available on interface [chars].
Explanation This message indicates that memory in the router was exhausted.
Recommended Action Perform diagnostics on the router to locate the subsystem or interface responsible for consuming memory. The only method that will clear this situation is to reload the router.


%BSC-3-BADLINESTATE : Line state Tx when receiving [chars] on line [chars]
Explanation An unexpected receive occurred during a transmission.
Recommended Action Verify that the line has been consistently defined in regards to the carrier. If a message report was sent, hard-on stop and start the bisynchronous interface in question.


BSHELL

%BSHELL-6-BSHELL_UPGRADE_DETECTED : [[chars]] New software detected. Bshell instance restarting.
Explanation The diagnostic shell detected a new installation of diagnostic shell software. The diagnostic shell instance exits and restarts with the new software version.
Recommended Action This is an informational message only. No action is required.


%BSHELL-6-SMAN_CONNECTION_LOST : [[chars]] Shell Manager connection lost
Explanation The diagnostic shell was disconnected from the Shell Manager and the Shell Manager process is no longer available. This type of error is experienced if a software upgrade is in progress.
Recommended Action This is an informational message only. No action is required. Once the Shell Manager process has restarted, the diagnostic shell will reconnect.


%BSHELL-6-SMAN_CONNECTION_FAILED : [[chars]] Shell Manager connect failed: [chars]
Explanation The diagnostic shell is unable to connect to the Shell Manager, possibly because the Shell Manager process is no longer available. This type of error is experienced if a software upgrade is in progress.
Recommended Action No action is required. Once the Shell Manager process has restarted, the diagnostic shell will reconnect.


%BSHELL-6-SESSION_STARTED : [[chars]] bshell session started for user '[chars]'
Explanation A user has started a diagnostic shell session.
Recommended Action This is an informational message only. No action is required.


%BSHELL-6-SESSION_ENDED : [[chars]] bshell session ended for user '[chars]'
Explanation A user has exited a diagnostic shell session.
Recommended Action This is an informational message only. No action is required.


%BSHELL-3-EXEC_PREPARE_FAIL : [[chars]] Command execution prepare failed
Explanation The diagnostic shell was unable to prepare the requested interactive command for execution. The command failed.
Recommended Action Check the diagnostic shell trace file for more information on the underlying failure.


%BSHELL-3-EXEC_FAIL : [[chars]] Command execution failed
Explanation The diagnostic shell was unable to execute the requested interactive command.
Recommended Action Check the diagnostic shell trace file for more information on the underlying failure.


%BSHELL-3-EXEC_DIRECTIVE_FAIL : [[chars]] Command directive execution failed: [chars]
Explanation The diagnostic shell was unable to execute the requested directive.
Recommended Action Check the diagnostic shell trace file for more information on the underlying failure.


%BSHELL-3-TERMINAL_OPERATION_FAIL : [[chars]] Terminal [chars] [chars] failed: [chars]
Explanation The diagnostic shell was unable to get or set terminal properties. An attempt to change or act on terminal properties failed.
Recommended Action Restart the diagnostic shell and reattempt the failed operation


%BSHELL-3-GET_HOSTNAME_FAIL : [[chars]] Get hostname failed: [chars]
Explanation The diagnostic shell was unable to read the hostname from the kernel.
Recommended Action No action is required. The diagnostic shell periodically checks for hostname changes to set the user prompt.


%BSHELL-3-SEND_MESSAGE_FAILED : [[chars]] Send message [chars] failed: [chars]
Explanation The diagnostic shell was unable to send a message to the Shell Manager.
Recommended Action Retry the operation or start a new diagnostic shell session.


%BSHELL-3-RECEIVE_MESSAGE_FAILED : [[chars]] Receive message [chars] failed: [chars]
Explanation The diagnostic shell was unable to receive a message from the Shell Manager
Recommended Action Retry the operation or start a new diagnostic shell session.


BSMRP

%BSMRP-0-CHASFS_LOCATION_TRANSLATE : Failed to translate a location to a chasfs object name because [chars]
Explanation The backplane switch manager failed to translate a location to a chasfs object name.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-CHASFS_OBJECT_CREATE : Failed to create chassis filesystem object [chars] because [chars]
Explanation The hardware failed to create a chassis filesystem object.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-CHASFS_PROPERTY_CREATE : Failed to create chassis filesystem object [chars] property [chars] because [chars]
Explanation A chassis filesystem property was not properly created.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-CHASFS_PROPERTY_GET : Failed to read chassis filesystem object [chars] property [chars] because [chars]
Explanation A chassis filesystem property was not properly read by the system.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-CHASFS_PROPERTY_SET : Failed to write chassis filesystem object [chars] property [chars] because [chars]
Explanation A chassis filesystem property failed to write.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-RESOLVE_FRU : Failed to determine [chars] card because [chars]
Explanation The router failed to determine a FRU state.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-EVENT_LIBRARY : An event facility initialization or maintenance function failed because [chars]
Explanation An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-PEER_TABLE : A peer table initialization or maintenance function failed because [chars]
Explanation A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-3-PEER_INVALID : A peer table entry has invalid state.
Explanation A peer table entry has an invalid state. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-UIPEER_CREATE : Failed to create user interface peer.
Explanation The system failed to create a user interface peer.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-SLOTS_INITIALIZATION : Failed to initialize chassis slot information because [chars]
Explanation The system failed to initialize the chassis slot information.
Recommended Action Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-SIGNAL_INITIALIZATION : Failed to initialize signals because [chars]
Explanation The system failed to initialize signals.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-SERVICES_INITIALIZATION : Failed to initialize general application services because [chars]
Explanation The system failed to initialize application services.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-MESSAGE_REGISTER : Failed to register with active RP because [chars]
Explanation The active RP failed to register.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-MESSAGE_RESPONSE : An invalid message response was received because [chars]
Explanation An invalid message response was received. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-CHASSIS_TYPE : The chassis type [chars] is invalid.
Explanation The chassis type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-PLATFORM_FAMILY_TYPE : The platform family type [chars] is invalid.
Explanation The platform family type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-CHASSIS_STATUS : Failed to get chassis hardware status because [chars]
Explanation The system failed to get the chassis hardware status.
Recommended Action Note the time of the error message and examine the logs for CPLD driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-3-CHASFS_OBJECT_DESTROY : Failed to destroy chassis filesystem object [chars] because [chars]
Explanation A chassis filesystem object that should have been destroyed was not destroyed.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-3-CHASFS_PROPERTY_DESTROY : Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars]
Explanation A chassis filesystem property that should have been destroyed was not destroyed.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-CHASFS_OBJECT_WATCH : Failed to watch chassis filesystem object [chars] because [chars]
Explanation A chassis filesystem object was not watched because of the reason stated in the error message.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-CHASFS_OBJECT_NOT_PRESENT : Expected chassis filesystem object [chars] not present.
Explanation A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-CHASFS_PROPERTY_NOT_PRESENT : Expected chassis filesystem object [chars] property [chars] not present.
Explanation A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-INVALID_ARGUMENT : A system function was given an invalid argument.
Explanation A system function was given an invalid argument. This is due to a software defect.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-SLOT_INVALID : A card absolute slot number cannot be determined for this chassis type
Explanation An absolute slot number is invalid. This could be due to a software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-IPC_INITIALIZATION : IPC initialization failed because [chars]
Explanation IPC initialization failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-IPC_CONNECT_MASTER : IPC connection to the active RP failed because [chars]
Explanation IPC connection to the active RP failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-IPC_CONNECTION_INVALID : An IPC connection has invalid state.
Explanation An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-MQIPC_INITIALIZATION : MQIPC initialization failed because [chars]
Explanation MQIPC initialization failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-MQIPC_ADVANCE : Failed to advance MQIPC queue because [chars]
Explanation The MQIPC initialization failed.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-0-MESSAGE_RELAY : Failed to relay a message because [chars]
Explanation Failed to relay a message. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%BSMRP-3-BSM_SERVICE_SETUP : Failed to setup the backplane switch manager (bsm) service
Explanation Backplane Switch Manager failed to set itself up as a proxy to the backplane switch.
Recommended Action Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


BSO_SAR_VRF

%BSO_SAR_VRF-3-API_FAILED : NULL
Explanation A call to the API of another component has indicated an 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.


BSTUN

%BSTUN-4-DUPROUTE : Cannot define duplicate route on thesame group
Explanation This route command is defined on another interface belonging to thesame group. Cannot define duplicate route on the same group
Recommended Action Consider defining a new group and moving this interface onto thatgroup


%BSTUN-4-PEERSTATE : Peer [chars], wrong state [dec] ([dec])
Explanation An internal software error occurred.
Recommended Action If this message recurs, 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.


%BSTUN-3-BADMAGIC : [chars]: wrong magic, mine [hex], theirs [hex] ([dec])
Explanation An internal software error occurred.
Recommended Action If this message recurs, 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.


%BSTUN-3-BADMAGICTCP : [chars]: peer [chars], wrong magic, mine [hex], theirs [hex]
Explanation An internal software error occurred.
Recommended Action If this message recurs, 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.


%BSTUN-3-BADLENOP : [chars]: bad len or unknown op, op [dec], len [dec]
Explanation An internal software error occurred.
Recommended Action If this message recurs, 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.


%BSTUN-6-TCPPEERSHUT : [chars] [chars], [IP_address]([dec])
Explanation This route closed a BSTUN connection with a remote peer.
Recommended Action Examine this router to see why it closed this connection with this peer. This can be caused by normal events, such as reconfiguration.


%BSTUN-3-CONNILLSTATE : CONN: Peer [chars], illegal state [dec]
Explanation An internal software error occurred.
Recommended Action If this message recurs, 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.


%BSTUN-3-BADCONN : CONN: bad connection ([dec]), peer: [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, 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.


%BSTUN-6-ERR : [chars]: [chars]: [chars], op [hex], len [dec]
Explanation An internal software error occurred.
Recommended Action If this message recurs, 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.


%BSTUN-3-SENDPUNT : [chars]: sent [chars] to [chars]
Explanation An internal software error occurred.
Recommended Action If this message recurs, 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.


%BSTUN-4-SENDPUNTTCP : [chars]: sent [chars] to ([[int]])[IP_address]
Explanation An internal software error occurred.
Recommended Action If this message recurs, 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.


%BSTUN-6-OPENING : CONN: opening peer [chars], [dec]
Explanation A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.
Recommended Action No action is required.


%BSTUN-6-CONNOPENFAIL : CONN: peer [chars] open failed, [chars] [[int]]
Explanation An attempt to connect to a remote TCP BSTUN peer failed.
Recommended Action Verify that the remote peer is accessible from this router, that it is running software capable of supporting BSTUN, and that it is configured correctly.


%BSTUN-3-BADPASSIVEOPEN : passive open from [IP_address]([dec]) -> [dec] failed
Explanation An internal software error occurred.
Recommended Action If this message recurs, 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.


%BSTUN-6-PASSIVEOPEN : passive open [IP_address]([dec]) -> [dec]
Explanation A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.
Recommended Action No action is required.


%BSTUN-6-TCPFINI : peer [chars] closed [previous state [chars]]
Explanation A remote peer closed a BSTUN connection with this router.
Recommended Action Examine the other router to see why it closed this connection with this peer. This can be caused by normal events, such as reconfiguration.


%BSTUN-6-PEERSHUTDOWN : shutting down peer [chars] on [chars]
Explanation A connection to a remote peer is being shut down. This is typically the result of user intervention in BSTUN reconfiguration or disabling. This is good, expected behavior.
Recommended Action No action is required.


%BSTUN-6-OPENED : [chars]: peer [chars] opened, [previous state [chars]]
Explanation A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.
Recommended Action No action is required.


%BSTUN-6-RECONNECT : PHDR: reconnect from peer [chars]
Explanation A remote peer reestablished a connection to this router.
Recommended Action No action is required.


%BSTUN-2-NOBUF : Interface [chars], no buffer available to [chars]
Explanation A memory shortage existed at the time that the configuration command was issued. This condition is rare and, under normal conditions, temporary.
Recommended Action Reconfigure the BSTUN group. If memory shortages persist, call your technical support representative for assistance.


%BSTUN-3-NOGRPDEF : No bstun group defined on interface [chars]
Explanation An action was taken that requires the previous definition of a BSTUN group number.
Recommended Action Make sure encapsulation bstun and the bstun group have been defined for the interface.


%BSTUN-3-UNKPROTOEV : Unknown protocol event [dec] on interface [chars]
Explanation An event passed to the BSTUN layer for processing could not be decoded.
Recommended Action Perform a hard restart on the indicated interface.


%BSTUN-6-PROCEXIT : Process terminating. Due to signal [dec]. Subcode [dec]. Address [hex].
Explanation The BSTUN background process is terminating.
Recommended Action If this message appears while you are unconfiguring BSTUN, no action is required. Otherwise, record all the displayed values and any other BSTUN error messages, and contact your technical support representative.


%BSTUN-3-NOPEER : No peer configured to route frame with destination address [chars] (bstun group [dec])
Explanation A BSTUN route has not been configured for the frame with a destination address.
Recommended Action If this message appears while you are debugging bstun, it indicates that no specific bstun route has been configured for the frames being received with the device address listed in the packet debug trace. You may choose to configure a bstun route, or ignore this message.


%BSTUN-3-IFNOTSETUP : Could not setup interface for protocol [chars]
Explanation BSTUN was unable to start the interface for handling the specified protocol traffic.
Recommended Action If this message appears while you are configuring BSTUN, check for other system errors, such as no available memory in the router, or the interface shutting down. If no obvious problem can be detected, record all the displayed values and any other BSTUN error messages, and contact your technical support representative.


BUFCAP

%BUFCAP-6-CAPPOINT_EXISTS : [chars]
Explanation EEM Policy provisioning by Auto-deploy is successful.
Recommended Action No action is required.


%BUFCAP-6-ENABLE : Capture Point [chars] enabled.
Explanation Specified capture point has been enabled.
Recommended Action No action is required.


%BUFCAP-6-DISABLE : Capture Point [chars] disabled.
Explanation Specified capture point has been disabled.
Recommended Action No action is required.


%BUFCAP-6-DISABLE_ASYNC : Capture Point [chars] disabled. Reason : [chars]
Explanation Specified capture point has been disabled due to asynchronous event.
Recommended Action No action is required.


%BUFCAP-6-CREATE : Capture Point [chars] created.
Explanation Specified capture point has been created.
Recommended Action No action is required.


%BUFCAP-6-DELETE : Capture Point [chars] deleted.
Explanation Specified capture point has been deleted.
Recommended Action No action is required.


%BUFCAP-6-CAPPOINT_EXISTS : Capture Point [chars] already exists.
Explanation A Capture point by the specified name already exists.
Recommended Action No action is required.


%BUFCAP-5-TIME_EXCEEDED : Capture Point [chars] disabled. The associated capture buffer's ([chars]) configured duration ( [dec] sec(s) ) exceeded.
Explanation The duration of the capture exceeds the maximum configured duration associated with the capture buffer. The associated capture point will be disabled.
Recommended Action No action is required.


%BUFCAP-5-ELEM_TRIMMED : Element trimmed as there was not enough space in capture buffer [chars]. Original Size: [dec]; Copied Size: [dec].
Explanation The linear buffer does not have enough space left. Hence the packet was trimmed. This is the final element in the buffer.
Recommended Action No action is required.


%BUFCAP-5-BUFFER_FULL : Linear Buffer associated with capture buffer [chars] is full.
Explanation The linear buffer is full. Further capture would be halted.
Recommended Action No action is required.


%BUFCAP-5-MAX_ELEMS : Capture point [chars] disabled. The number of elements in associated capture buffer's ([chars]) has reached the maximum configured value ([dec] elements).
Explanation The buffer contains the maximum configured number of packets. The associated capture point will be disabled.
Recommended Action No action is required.


%BUFCAP-3-NO_MEM : Not enough memory available for Buffer Capture Infrastructure
Explanation The buffer capture infrastructure could not get the memory it requested.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%BUFCAP-3-INVALID_CAPPOINT : Invalid capture point.
Explanation Some operation was attempted on a invalid capture point.
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.


%BUFCAP-3-ACTIVE_CAPPOINT : Invalid operation was attempted on an active capture point [chars].
Explanation Invalid operation was attempted on an active capture point.
Recommended Action Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, copy the error message exactly as it appears on the console or in the system log, enter the show monitor capture point all and show tech commands and contact your Cisco technical support representative, providing the representative with the gathered information.


%BUFCAP-3-INVALID_PARAM : Invalid parameters
Explanation Invalid parameters were passed in to a buffer capture infrastructure function.
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.


%BUFCAP-3-EXPORT_BUFFER : Error exporting buffer [chars] to location [chars]
Explanation The Buffer Capture Infrastructure is not able to export the buffer to the specified location
Recommended Action Please check if a valid destination was specified. Or if a file by the same name already exists, rename the dump file or remove the existing file from the destination location. If those actions do not resolve the problem, LOG_STD_ACTION


%BUFCAP-6-RATE_LIMIT : [dec] packets from capture point [chars] dropped due to rate limiting.
Explanation Rate limiting has been enabled and the number of packets exceed the allowed configured value.
Recommended Action


%BUFCAP-6-TOO_BIG : The packet to be dumped is bigger than the buffer size of capture buffer [chars]. Packet of size [dec] dropped.
Explanation The packet is bigger than the configured/default buffer size.
Recommended Action Change the parameters of the capture buffer. You can try to increase the size of the buffer or limit the number of bytes copied.


%BUFCAP-3-NOSUCHCAPTURE : Error finding capture point.
Explanation No such capture point exists
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.


CALLPROG

%CALLPROG-3-API_INIT : api front init failed for [chars]
Explanation Failed to init Call Progress Notification support structures for APIs.
Recommended Action System running low on available memory.


%CALLPROG-3-API_USE : no free front-end q elt's; dropping api call info (func=[dec])
Explanation Failed to get free element from front end queue.
Recommended Action Platform requires additional free elements to properly function. Stop using Call Progress Notification applications. Call TAC to report the problem


CALLTREAT

%CALLTREAT-3-HIGH_CPU_ONE_MIN_LOAD : System experiencing high cpu utilization over one minute interval. Processing for callID([dec]) is rejected.
Explanation Based on the average CPU utilization over a 60 second interval, the system does not have enough CPU resources available to accept a new call. The specified call was rejected.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Enter the show proc cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the five-second CPU utilization on the gateway exceeds 98%.


%CALLTREAT-3-HIGH_CPU_5SEC_LOAD : System experiencing high cpu utilization. Processing for callID([dec]) is rejected.
Explanation System does not have enough CPU resources available to accept a new call. The specified call was rejected.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Enter the show proc cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the five-second CPU utilization on the gateway exceeds 89%. The default value can be overridden by enabling call treatment and entering the call threshold global cpu-5sec command.


%CALLTREAT-3-HIGH_CPU_AVERAGE_LOAD : System experiencing high average cpu utilization. Processing for callID([dec]) is rejected.
Explanation Based on the average CPU utilization over a 60-second interval or an interval configured through the call threshold poll-interval command, the system does not have enough CPU resources available to accept a new call. The specified call was rejected.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Check to see if the current call setup rate is supported on this gateway. Enter the show proc cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the five-second CPU utilization on the gateway exceeds 98%. The default value can be overridden by enabling call treatment and entering the call threshold global cpu-avg command.


%CALLTREAT-3-HIGH_IOMEM_USAGE : System running low on I/O memory. Processing for callID([dec]) is rejected.
Explanation The system does not have enough free I/O memory to accept a new call. The specified call was rejected.
Recommended Action Ensure that the gateway has the recommended amount of I/O memory for this Cisco IOS feature set and version. Enter the show mem and show proc mem commands to see which processes are consuming the most memory. Check to see if the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. The high and low thresholds for I/O memory utilization can be configured by enabling call treatment and entering the call threshold global io-mem command.


%CALLTREAT-3-HIGH_PROCMEM_USAGE : System running low on processor memory. Processing for callID([dec]) is rejected.
Explanation The system does not have enough free processor memory to accept a new call. The specified call was rejected.
Recommended Action Ensure that the gateway has the recommended amount of processor memory for this Cisco IOS feature set and version. Enter the show mem and show proc mem commands to see which processes are consuming the most memory. Check to see if the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. The high and low thresholds for processor memory utilization can be configured by enabling call treatment and entering the call threshold global proc-mem command.


%CALLTREAT-3-HIGH_TOTAL_CALLS : High call volume. Processing for callID([dec]) is rejected.
Explanation The system is experiencing a high call volume. There are not enough resources to accept a new call. The specified call was rejected.
Recommended Action Disable call threshold, modify the call threshold global high and low values, or investigate the cause of the high resource utilization. The high and low thresholds for total number of calls can be configured by enabling call treatment and entering the call threshold global proc-mem command.


%CALLTREAT-3-HIGH_MEMORY_USAGE : System running low on memory. Processing for callID([dec]) is rejected.
Explanation The system does not have enough free memory to accept a new call. The specified call was rejected.
Recommended Action Ensure that the gateway has the recommended amount of memory for this Cisco IOS feature set and version. Enter the show mem and show proc mem commands to see which processes are consuming the most memory. Check to see if the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. By default, the system will reject calls if there is less than 2% free processor memory on the gateway. This value can be overridden by enabling call treatment and entering the call threshold global total-mem command.


CALLTREAT_NOSIGNAL

%CALLTREAT_NOSIGNAL-3-HIGH_CPU_ONE_MIN_LOAD : System experiencing high cpu utilization over one minute interval.
Explanation Based on the average CPU utilization over a 60 second interval, the system does not have enough CPU resources available.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Enter the show proc cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject resource allocation if the five-second CPU utilization on the gateway exceeds 98%.


%CALLTREAT_NOSIGNAL-3-HIGH_CPU_5SEC_LOAD : System experiencing high cpu utilization.
Explanation System does not have enough CPU resources available to allocate a new resource.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Enter the show proc cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the five-second CPU utilization on the gateway exceeds 89%. The default value can be overridden by enabling call treatment and entering the call threshold global cpu-5sec command.


%CALLTREAT_NOSIGNAL-3-HIGH_CPU_AVERAGE_LOAD : System experiencing high average cpu utilization.
Explanation Based on the average CPU utilization over a 60-second interval or an interval configured through the call threshold poll-interval command, the system does not have enough CPU resources available to accept a new call.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Check to see if the current call setup rate is supported on this gateway. Enter the show proc cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the five-second CPU utilization on the gateway exceeds 98%. The default value can be overridden by enabling call treatment and entering the call threshold global cpu-avg command.


%CALLTREAT_NOSIGNAL-3-HIGH_IOMEM_USAGE : System running low on I/O memory.
Explanation The system does not have enough free I/O memory.
Recommended Action Ensure that the gateway has the recommended amount of I/O memory for this Cisco IOS feature set and version. Enter the show mem and show proc mem commands to see which processes are consuming the most memory. Check to see if the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. The high and low thresholds for I/O memory utilization can be configured by enabling call treatment and entering the call threshold global io-mem command.


%CALLTREAT_NOSIGNAL-3-HIGH_PROCMEM_USAGE : System running low on processor memory.
Explanation The system does not have enough free processor memory.
Recommended Action Ensure that the gateway has the recommended amount of processor memory for this Cisco IOS feature set and version. Enter the show mem and show proc mem commands to see which processes are consuming the most memory. Check to see if the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. The high and low thresholds for processor memory utilization can be configured by enabling call treatment and entering the call threshold global proc-mem command.


%CALLTREAT_NOSIGNAL-3-HIGH_TOTAL_CALLS : High call volume.
Explanation The system is experiencing a high call volume.
Recommended Action Disable call threshold, modify the call threshold global high and low values, or investigate the cause of the high resource utilization. The high and low thresholds for total number of calls can be configured by enabling call treatment and entering the call threshold global proc-mem command.


%CALLTREAT_NOSIGNAL-3-HIGH_MEMORY_USAGE : System running low on memory.
Explanation The system does not have enough free memory to allocated new resource.
Recommended Action Ensure that the gateway has the recommended amount of memory for this Cisco IOS feature set and version. Enter the show mem and show proc mem commands to see which processes are consuming the most memory. Check to see if the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. By default, the system will reject calls if there is less than 2% free processor memory on the gateway. This value can be overridden by enabling call treatment and entering the call threshold global total-mem command.


CALL_CONTROL

%CALL_CONTROL-6-MAX_CONNECTIONS : Maximum number of connections reached for dial-peer [dec]
Explanation The dial-peer in question has reached its maximum connections configurations. No more calls will be taken on this dial-peer.
Recommended Action No action is required, however, to increase the number of connections allowed to this dial peer see 'maximum connections' configuration under the dial-peer configuration mode.


%CALL_CONTROL-6-APP_NOT_FOUND : Application [chars] in dial-peer [dec] not found. Handing callid [dec] to the alternate app [chars].
Explanation The inbound dial-peer points to an unavailable application. The call is being handed to the alternate application or is rejected.
Recommended Action Reconfigure the dial-peer to have a valid application name or verify the application is accesible at its location.


%CALL_CONTROL-6-APP_NOT_EXIST : The requested application does not exist any more. The event for the callid [dec] is being discarded.
Explanation The event points to a session application which does not exist any more. The event is being discarded.
Recommended Action No action is required for the users


%CALL_CONTROL-6-NUMBERING_TYPE_NO_MATCH : The called number numbering type did not match The event for the callid [dec] is being discarded.
Explanation The event points to a session application which does not exist any more. The event is being discarded.
Recommended Action No action is required for the users


%CALL_CONTROL-3-NORAWMSG : no free raw msg structure available from [chars] for signaling message
Explanation There were no rawmsg structures remaining in the system pools to alert the router of a voice or signaling event.
Recommended Action Check that the voice port for which the event was reported is still operational. If not, clear the voice port.


%CALL_CONTROL-3-CCAPI_DB_ERR : ccapi database error
Explanation Internal CCAPI conference or call record database error. This message represents an internal software fault and may manifest itself as dropped or hung calls.
Recommended Action Contact your technical support representative, include the full text of the error message.


%CALL_CONTROL-6-CALL_LOOP : The incoming call has a global identifier already present in the list of currently handled calls. It is being refused.
Explanation The incoming call has a global identifier already present in the list of currently handled calls. It means that the voice gateway has detected a loop in the call route.
Recommended Action Please check your configuration.


%CALL_CONTROL-6-UNKNOWN_EXT_AGENT_RESET_ATTEMPT : Request to reset an uknown external agent (ID [dec]) attempted. Attempt ignored.
Explanation A request to reset an external agent (eg H323 Gatekeeper or MGCP CA etc) was attempted but IOS doesn't know how to process the request. This is not usually a problem for the router. It does however mean that the external agent for whom the reset was intended never got 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.


%CALL_CONTROL-3-INVALID_PARAMETER : An invalid parameter is passed to the function
Explanation This is due to coding error.
Recommended Action No action is required for the users


%CALL_CONTROL-3-STAT_MEMORY_CORRUPTED : Memory corruption detected in memory=[hex] allocated for RTCP statistic
Explanation This is due to coding error
Recommended Action No action is required for the users


CAPWAP_REASS_PROXY through CD_SW_SSL_SHIM

CAPWAP_REASS_PROXY

%CAPWAP_REASS_PROXY-3-PROXY_IPC_MEM_INIT_FAILED :
Explanation Initialization of Capwap Reassembly memory pool 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.


%CAPWAP_REASS_PROXY-3-PROXY_IPC_MEM_EXTEND_FAILED :
Explanation Increasing of Capwap Reassembly memory pool 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.


%CAPWAP_REASS_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization 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.


%CAPWAP_REASS_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Received an invalid IPC messages subtype.
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.


CASA

%CASA-3-BADVER : Incoming packet is CASA v[dec], this router is v[dec]
Explanation A packet was received for the wrong version of CASA
Recommended Action Verify that all CASA devices are running the same version of the protocol


%CASA-2-NOMEM : Out of memory: [chars]
Explanation CASA failed to allocate memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%CASA-4-BADMSG : Message parsing error: [chars]
Explanation Failed to parse an incoming packet
Recommended Action If this message is occurring repeatedly, enable 'debug ip casa error'and record the output, call your Cisco technical support representative,and provide the gathered information.


%CASA-4-SECURITY_FAIL : [chars] security information in CASA packet.
Explanation Security check failed.
Recommended Action Make sure all CASA systems are configured with the same password.


%CASA-4-UNEXPECTED : Unexpected error: [chars]
Explanation An unexpected error occurred while performing CASA operation
Recommended Action If this message recurs, 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.


%CASA-4-WARNING : Unexpected condition: [chars]
Explanation An unexpected condition was detected while performing CASA operation
Recommended Action If this message recurs, 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.


%CASA-4-PORTCHANGE : Wildcard overlap: [chars]
Explanation A CASA wildcard, received on one port, has been overwritten by a service manager sending to another port. This message may appear once if you are migrating your service to a new forwarding-agent port,if it recurs, it could indicate a configuration problem.
Recommended Action If this message recurs, 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.


CBAC_C3PL

%CBAC_C3PL-4-OBJ_CREATE : Firewall [chars] object [chars] creation failed in the data plane, error [dec]
Explanation The notification of the creation of a firewall object e.g. a parameter map, has failed to update the data plane and as such the application of the parameters contained within the object will not be applied to the data plane. It is also possible that the common classification may fail to locate and bind to the object rendering the configuration incomplete in terms of application.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show memory command to gather data that may help identify the nature of the error. Also 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.


%CBAC_C3PL-4-OBJ_DELETE : Firewall [chars] object [chars] deletion failed in the data plane, error [dec]
Explanation The notification of the deletion of a firewall object e.g. a parameter map, has failed to update the data plane and as such the application of the parameters contained within the object may continue to be applied to the data plane.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show memory command to gather data that may help identify the nature of the error. Also 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.


%CBAC_C3PL-4-OBJ_MODIFY : Firewall [chars] object [chars] modification failed in the data plane, error [dec]
Explanation The notification of the modification of a firewall object e.g. a parameter map, has failed to update the data plane and as such the application of the parameters contained within the object will not be applied to the data plane.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show memory command to gather data that may help identify the nature of the error. Also 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.


%CBAC_C3PL-3-INIT : Firewall data plane updates are disabled
Explanation The firewall notification of objects to the data plane has failed to startup and as such data plane updates are disabled.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show registry brief command to gather data that may help identify the nature of the error. Also 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.


CBUS

%CBUS-4-RSETFAIL : Interface [chars] failed to reset properly in [chars], code [hex]
Explanation An interface reset command failed. This may be a software or hardware problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-OUTHUNG : [chars]: tx%c output hung (%-04x - [chars]), [chars]
Explanation A transmission attempt on an interface failed. The interface might not be attached to a cable or there might be a software problem.
Recommended Action Check that the interfaces are all connected to the proper cables. If that is not the problem, call your technical support representative.


%CBUS-4-NOCOOKIE : [chars]-[dec] controller missing configuration data - disabled
Explanation The controller type was derived from a hardware probe. The controller number indicates the ciscoBus relative slot number. This is a hardware error
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-TESTFAIL : Unit [dec], failed [chars] test - interface disabled
Explanation A hardware component failed an internal diagnostic test.
Recommended Action Check switch settings on the interface cards. Check for proper unit numbers. Reset the cards. Replace the malfunctioning device.


%CBUS-3-DAUGHTER : Unit [dec], daughter controller [dec] failed [chars] test - interface disabled
Explanation A hardware component failed an internal diagnostic test. Test output and descriptions of ranges follow: Unit [dec] (ranges 0-14): Indicates the Multibus jumper setting for the ciscoBus controller, or in the Cisco 7000, a slot number. daughter controller [dec] (ranges 0-3): Indicates the ciscoBus relative slot number (0 to 3, or in the Cisco 7000, 0 to 4) of the daughter card that failed the test. failed [chars] test ([chars]= memd read, memd write):If the failed test was memd read, the processor was able to write to shared ciscoBus buffer memory from the ciscoBus registers, but was unable to read back that memory through special commands to the daughter card. If the failed test was memd write, writes to the memory device through the daughter card were not verified successfully with reads through the ciscoBus controller. The daughter card under test responds successfully to some commands (otherwise the software would have received a DAUGHTER_NO_RSP message), but its memory device tests failed. The daughter card must be able to write to some memory device addresses; otherwise, it cannot respond to any commands.
Recommended Action First check that the daughter controller card is properly seated in its Multibus and ciscoBus connectors. Next, swap daughter cards and check whether the error follows the daughter card or the slot. If the message recurs, call your technical support representative for assistance.


%CBUS-3-DAUGHTER_NO_RSP : Unit [dec], daughter [dec], not responding ([hex]) - disabled
Explanation A hardware component failed an internal diagnostic test. Test output and descriptions of ranges are as follows: Unit [dec] (ranges 0-14): Indicates the Multibus jumper setting for the ciscoBus controller. daughter controller [dec] (ranges 0-3): Indicates the ciscoBus relative slot number (0 to 3, or in the Cisco 7000, 0 to 4) of the daughter card that failed the test. The daughter card hardware was recognized across the cBus backplane, but the daughter card did not respond to the first command issued to it. This condition is a result of one of the following: the daughter card did not reset, or the microcode on the card is in a hung state, or the card cannot fully communicate across the ciscoBus backplane (cannot read or write shared MEMD or does not get the MALU_ATTENTION signal across the ciscoBus).
Recommended Action First, make sure that the daughter card is properly seated in its Multibus and ciscoBus connectors. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information


%CBUS-3-CORRUPT : Controller [dec], wrote 0x%-04x, read 0x%-04x, loc 0x%-04x - dci_memtest()
Explanation A hardware component failed an internal diagnostic test.
Recommended Action Replace the malfunctioning device.


%CBUS-3-TXALLOC : Error (%-04x) tx_allocate - cbus_init()
Explanation A hardware device did not respond appropriately to a request.
Recommended Action Make sure the device is functioning and is configured correctly.


%CBUS-3-BUFFER : Controller [dec], Error (%-04x), Buffersize = [dec], Bufferpool = [dec], number [dec]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-INITERR : Interface [dec], Error (%-04x), idb [hex] [dec] [chars] - cbus_init()
Explanation The switch processor or ciscoBus controller signaled an error while processing a packet or selecting an interface. This indicates a software problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-INTR : Interface [dec], idb [hex] [dec] [chars] - cbus_interrupt()
Explanation The switch processor or ciscoBus controller returned a nonsensical value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CBUSBCE : Failed to select a BCE, response [hex] - cbus_bce_update_ifa()
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CBUSBCEPERM : Failed to select a BCE, response [hex] - cbus_bce_permissions_update()
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-FDDIRSET : Interface [chars], Error (%-04x) [chars] - fddi_reset()
Explanation A hardware device did not respond appropriately to a request.
Recommended Action Make sure the device is functioning and is configured correctly.


%CBUS-3-FDDIRSETU : Unit [dec], Error (%-04x) [chars] - fddi_reset()
Explanation A hardware device did not respond appropriately to a request.
Recommended Action Make sure the device is functioning and is configured correctly.


%CBUS-5-FDDICMD : '[chars]' is not supported on [chars]
Explanation This command is not supported on this FDDI interface.
Recommended Action No action is required.


%CBUS-3-HSSIRSET : Interface [chars], Error (%-04x) [chars] - hssi_reset()
Explanation A command to reset an HSSI interface was issued by the RSP, but the interface did not respond to the command within the expected time delay. The delay is given for the processor to return the buffers that it has allocated and to perform any necessary cleanup. This condition may be caused by a large number of buffers that have been allocated by the interface due to either heavy traffic or a hardware problem with the interface.
Recommended Action Verify that the card is properly seated. If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.


%CBUS-3-SRPRSET : Interface [chars], Error (%-04x) [chars] - srp_reset()
Explanation A command to reset an SRP interface was issued by the RSP, but the interface did not respond to the command within the expected time delay. The delay is given for the processor to return the buffers that it has allocated and to perform any necessary cleanup. This condition may be caused by a large number of buffers that have been allocated by the interface due to either heavy traffic or a hardware problem with the interface.
Recommended Action Verify that the card is properly seated. If this error recurs, then issue the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.


%CBUS-3-CTRRAMTEST : Interface [chars], RAM Addressing Test Failed - [chars]
Explanation The Token Ring interface failed its memory diagnostic tests.
Recommended Action Issue a clear interface command. LOG_STD_RECUR_ACTION


%CBUS-3-CTRINIT : Interface [chars], CTR Initialization Failed - [chars]
Explanation The Token Ring interface failed one of its internal self-tests.
Recommended Action Issue a clear interface command. LOG_STD_RECUR_ACTION


%CBUS-3-CTRCMDFAILED : Interface [chars], CTR Command [chars] Failed, [chars] (%#04x)
Explanation A command sent from the system to the Token Ring interface failed to complete successfully.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CTRCMDFAILED2 : Interface [chars], CTR Command [chars] Failed, Code %#04x
Explanation A command sent from the system to the Token Ring interface failed to complete successfully.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CTRRSET : Interface [chars] failed to initialize
Explanation The Token Ring interface failed to insert into the Token Ring. The interface is placed into reset state and will not automatically try to re-insert itself.
Recommended Action Issue a clear interface command. LOG_STD_RECUR_ACTION


%CBUS-3-CTRACHECK : Interface [chars], Adapter Check Error ([hex] [hex] [hex] [hex])
Explanation The Token Ring monitor firmware detected a fatal error on the interface card.
Recommended Action Issue a clear interface command. LOG_STD_RECUR_ACTION


%CBUS-3-CTRUCHECK : Interface [chars], Microcode Check Error
Explanation The Token Ring interface microcode detected an unrecoverable error.
Recommended Action Issue a clear interface command. LOG_STD_RECUR_ACTION


%CBUS-3-CTRBADLOVE1 : Interface [chars], SRB_COMPLETE lovenote received with unknown command ([hex])
Explanation The system received a message from the Token Ring interface but does not recognize the message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CTRBADLOVE1_DUMP : Dump of MEMB follows-SRB_ADDR: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation The system is printing codes related to a previous lovenote error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-4-CTRBADLOVE2 : Interface [chars], Unexpected SRB_COMPLETE lovenote, command=[hex], result=[hex]
Explanation The system received an unsolicited message from the Token Ring interface. The system ignored the message and continued normal processing.
Recommended Action If this message recurs, 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.


%CBUS-3-RESETNXI : Reset of removed interface [hex] ([chars])
Explanation An interface reset was attempted on an interface that was removed from the router. This message appears if you use the shutdown command to bring down a removed interface.
Recommended Action No action is required.


%CBUS-3-FSIPRSET : Interface [chars], Error (%-04x) [chars] - fsip_reset()
Explanation A Fast Serial Interface Processor (FSIP) did not respond to a reset request from the Route Processor.
Recommended Action Check FSIP electrical connections, cable, and ciscoBus connections. An FSIP microcode reload will be required. If the check of electrical connections reveals no problems and the message recurs, call your technical support representative for assistance.


%CBUS-3-SERRSET : Interface [chars], Error (%-04x) [chars] - serial_reset()
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CATMRSET : Interface [chars], Error (%-04x) [chars] - aip_reset()
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CATMRSETU : Unit [dec], Error (%-04x) [chars] - cbus_atm_reset()
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CATMCFG : Interface [chars], Cannot config interface, CBus ATM MEM [hex], status [dec]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CBUS-3-AIPINVPLIM : Interface [chars], Invalid PLIM detected. Interface downed
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CATMREJCMD : [chars] [chars] command failed (error code [hex])
Explanation The cBus ATM microcode rejected a command sent by the Route Processor (RP). The error code is the status value returned by the command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-BADVC : [chars] [dec]/[dec] got bad VC packet [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation An interface received a packet with bad VC encapsulation. This indicates either a software or hardware problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-POLLFAIL : Interface [chars] failed to respond, debug info follows
Explanation A Token Ring interface card failed to respond to periodic polling. This can indicate a software or hardware problem. See CBUS-3-POLLFAILDAT for the syntax of this message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-POLLFAILDAT : Int [dec]: [hex] [hex] [hex] [hex] [hex] [hex]
Explanation This is the debugging information for the CBUS-3-POLLFAIL error.
Recommended Action This is a debug message only. No action is required.


%CBUS-3-FCICMDFAIL0 : Controller [dec], cmd ([dec]) failed (0x%-04x) count ([dec])
Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.


%CBUS-3-FCICMDFAIL1 : Controller [dec], cmd ([dec] 0x%-08x) failed (0x%-04x) count ([dec])
Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.


%CBUS-3-CTRLRCMDFAIL0 : Controller [dec], cmd ([dec]) failed (0x%-04x) count ([dec])
Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.


%CBUS-3-CTRLRCMDFAIL1 : Controller [dec], cmd ([dec] 0x%-08x) failed (0x%-04x) count ([dec])
Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.


%CBUS-3-CCBCMDFAIL0 : Controller [dec], cmd ([dec]) failed (0x%-04x)
Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.


%CBUS-3-CCBCMDFAIL1 : Controller [dec], cmd ([dec] 0x%-08x) failed (0x%-04x)
Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.


%CBUS-3-CCBCMDFAIL3 : Controller [dec], cmd ([dec] 0x%-04x, 0x%-04x, 0x%-04x) failed (0x%-04x)
Explanation A command sent from the system to an interface processor failed to complete successfully.
Recommended Action The system recovered by generating an error code to the requester.


%CBUS-3-UNKENC : Interface [chars], unknown encaps type [hex]
Explanation A packet was received from the CIP with an unknown encapsulation type. The packet will be dropped.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CT3STAT : Out of buffers--losing status information for CT3 on VIP card
Explanation A status information message from the VIP was received. A memory buffer is required to process the status information message, but the memory allocation routine due to insufficient system buffer memory. Therefore, the status information message was not processed. This condition may be caused either by a heavy memory utilization at the time of the memory buffer request or by insufficient memory in the system.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If this message recurs or appears regularly, contact your Cisco technical representative to upgrade the memory of the system.


%CBUS-3-HALSTAT : Out of buffers--losing status information for ChSTM-1 on VIP card
Explanation An internal software resource has been exhausted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-POTSTAT : Out of buffers--losing status information for POTENT on VIP card
Explanation An internal software resource has been exhausted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CT3DSX3ERR : ([chars])Illegal dsx3 value - unit is [dec]
Explanation
Recommended Action


%CBUS-3-CE3DSX3ERR : ([chars])Illegal E3 value - unit is [dec]
Explanation A status information message was received from the CT3 VIP, but during message processing it was detected that an element in the data structure corresponding to the status information message has not been set. This condition may be caused by either an element that has not been passed by the VIP or a corruption in the status message.
Recommended Action If this error recurs, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.


%CBUS-3-HALSDHERR : ([chars])Illegal sdh value - unit is [dec]
Explanation Internal data structure is corrupted, which causes the love letter to drop.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-5-CBADVCSETUP : Interface [chars], setup vc failed with vci exceeding (vc-per-vp - 3) on the last vpi.
Explanation The TI1570 chip reserves 3 RX DMA channels for OAM cells. As a result, the last 3 VCIs of the last VPI block cannot be used for regular traffic.
Recommended Action Avoid try different vci/vpi combinations.


%CBUS-3-CFGCMDDROPPED : Config queue is full, command was dropped, slot [dec]
Explanation Sending a config command was retried. The receiving queues were still full after retries therefore the command was dropped.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CBUS-3-ADDRFILTR : Interface [chars], address filter [chars] command failed, code %#04x
Explanation The specified address filter command sent to the specified interface failed with the displayed error code.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CBUS-3-BADRXEOFVEC : [chars] ustatus: [chars] ([hex]), [hex] [hex] [hex] [hex]
Explanation Debugging information when an IP panics.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CBUS-3-BADTXSTATE : [chars] ustatus: [chars] ([hex]), [hex] [hex] [hex] [hex]
Explanation Debugging information when an IP panics.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CBUS-3-BADTXEOFVEC : [chars] ustatus: [chars] ([hex]), [hex] [hex] [hex] [hex]
Explanation Debugging information when an IP panics.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CBUS-3-TXSTARTPENDACTIVE : [chars] ustatus: [chars] ([hex]), [hex] [hex] [hex] [hex]
Explanation Debugging information when an IP panics.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CBUS-3-UNKNOWN : [chars] ustatus: [chars] ([hex]), [hex] [hex] [hex] [hex]
Explanation Debugging information when an IP panics.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CBUS-3-CMDTIMEOUT : Cmd timed out, CCB [hex], slot [dec], cmd code [dec]
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CMDDROPPED : Cmd dropped, CCB [hex], slot [dec], cmd code [dec]
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CCBSEMINFO : CCB semaphore acquired traceback:[chars] CCB semaphore released traceback:[chars]
Explanation More information on the CCB semaphore. The tracebacks indicate the program counters and stack that point to the code that was the last to acquire this semaphore and the last to release this semaphore respectively
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CCBPTIMEOUT : CCB handover timed out, CCB [hex], slot [dec]
Explanation A hardware or software error occurred.
Recommended Action Please gather the logs and tracebacks and contact the TAC


%CBUS-3-PORTTYPE : Unexpected interface type for [chars][int], port [int], type [int]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-CMD : Cmd failed: [chars], response %#04x, [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.


%CBUS-3-MODULE : Missing [chars] for [chars]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-NOBUF : Buffer allocation failure: [chars]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-5-INPUTERR : Interface [chars] excessive input error rate
Explanation Interface disabled because too many input errors occurred.
Recommended Action Inspect condition of attached network hardware


%CBUS-4-FIXBADTXVC : Detected and fixed bad tx vc encap on [chars], bad vc [dec], fixed vc [dec]
Explanation A transmit packet on a channelized serial interface does not have the vc number encapsulation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-TXVCENCAPFAIL : Detected bad tx vc encap on [chars], vc [dec]. Board encap failed [hex], [hex], [hex]
Explanation Board encap failed on a transmit packet on a channelized serial interface which does not have the vc number encapsulation
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-SELECTBADVC : Select invalid vc number [dec].
Explanation An invalid channel number is selected
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CBUS-3-SENDIPCMDFAIL : Send Ip Cmd Failed. Command dropped after [dec] retries, CCB [hex], slot [dec], cmd code [dec]
Explanation Sending an ip command was retried. The receiving queues were still full after retries therefore the command was dropped.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%CBUS-5-SENDIPCMDRECOV : Send Ip Cmd Succeeded after [dec] retries, CCB [hex], slot [dec], cmd code [dec]
Explanation Sending an ip command was retried due to receiving queues being full. But after some retries, command was send successfuly.
Recommended Action No action is required.


CCE_PI_PD

%CCE_PI_PD-4-TARGET_CLASS_GROUP_DB : Failed to [chars] id [hex] [chars] database
Explanation An operation to manipulate the record of the target class groups supplied via the PI/PD API has failed to perform the required action on a target class group successfully. This may imply that the resultant notification via the API was deferred or dropped.
Recommended Action LOG_STD_SH_CMD_ACTION(show cce cpdp bindings target <id>)


%CCE_PI_PD-6-TARGET_BINDINGS_DB : [chars] [chars] [chars] target class group [hex] contains feature bindings
Explanation The target class group is reporting the presence of feature bindings upon its removal. This is informational.
Recommended Action LOG_STD_SH_CMD_ACTION(show cce cpdp bindings target <id>)


%CCE_PI_PD-4-CLASS_GROUP_DB : Failed to [chars] id [hex] [chars] database
Explanation An operation to manipulate the record of the class groups and classes supplied via the PI/PD API has failed to perform the required action on a class group successfully. This may imply that the resultant notification via the API was deferred or dropped.
Recommended Action LOG_STD_SH_CMD_ACTION(show cce cpdp associations class-group <id>)


%CCE_PI_PD-4-CLASS_DB : Failed to [chars] class group id [hex] class id [hex] [chars] database
Explanation An operation to manipulate the record of the class groups and classes supplied via the PI/PD API has failed to perform the required action on a class successfully. This may imply that the resultant notification via the API was deferred or dropped.
Recommended Action LOG_STD_SH_CMD_ACTION(show cce cpdp associations class group <id>)


%CCE_PI_PD-4-CLASS_CLASS_GROUP_DB : Failed to [chars] class group id [hex] class id [hex] class group [hex] [chars] database
Explanation An operation to manipulate the record of the class groups and classes supplied via the PI/PD API has failed to perform the required action on a class group attached to a class successfully. This may imply that the resultant notification via the API was deferred or dropped.
Recommended Action LOG_STD_SH_CMD_ACTION(show cce cpdp associations class-group <id>)


%CCE_PI_PD-4-FEATURE_BIND_DB : Failed to [chars] target id [hex] class group [hex] class id [hex] feature [chars] binding [chars] database
Explanation An operation to manipulate the record of the binding of a action within a policy map class to a particular target supplied via the PI/PD API has failed to perform the required action successfully. This may imply that the resultant notification via the API was deferred or dropped.
Recommended Action LOG_STD_SH_CMD_ACTION(show cce cpdp bindings target <id>)


%CCE_PI_PD-3-FILTER_LIST : Failed to create class [chars] id [hex] filter list
Explanation An operation to create the filter list for a particular class has failed due to a resource issue. This may imply that the resultant notification via the API was deferred or dropped.
Recommended Action LOG_STD_SH_CMD_ACTION(show class-map [type <class type>] <name>)


%CCE_PI_PD-6-CLASS_GROUP_CLASSES_DB : Class group [hex] contains classes
Explanation The class group is reporting the presence of classes upon its removal. This is informational.
Recommended Action LOG_STD_SH_CMD_ACTION(show cce cpdp associations class-group <id>)


%CCE_PI_PD-6-CLASS_CLASSES_DB : Class group [hex] class [hex] ([chars]) contains a class group
Explanation The class is reporting the presence of a class group upon its removal. This is informational.
Recommended Action LOG_STD_SH_CMD_ACTION(show cce cpdp associations class-group <id>)


%CCE_PI_PD-3-CLASS_NAME : Map name [chars] id [hex] unable to [chars] string ([hex])
Explanation During the addition or removal of a class or a class group its name which corresponds to a class or policy map was either not found within the database of strings or it was unable to add the name to the database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show cce cpdp associations command to gather data that may help identify the nature of the error. Also 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.


%CCE_PI_PD-6-CLASS_FILTER : Class [chars], id [hex], type [chars], filter list is unbalanced
Explanation During the addition of a class, an internal error was encountered during the construction of the match terms comprising that class.
Recommended Action LOG_STD_SH_CMD_ACTION(show class-map [type <type>] <name>)


CCH323

%CCH323-3-CANNOT_ALLOCATE_GW : [chars]: cannot allocate gateway structure
Explanation Allocation of the CCH323 gateway instance failed. This is possibly due to the fact that system memory pool is exhausted.
Recommended Action This can be a catastrophic error


%CCH323-3-CANNOT_CREATE_CCB : [chars]: cannot create the H.323 ccb Tree
Explanation Creation of the H.323 CCB Tree failed. This is possibly due to the fact that system memory pool is exhausted.
Recommended Action This can be a catastrophic error


%CCH323-3-CANNOT_ALLOCATE_CCB : [chars]: cannot allocate call control block
Explanation Allocation of the CCH323 call control block failed. This is possibly due to the fact that system memory pool is exhausted.
Recommended Action This can be a catastrophic error


%CCH323-3-CANNOT_ALLOCATE_CALL_INFO : [chars]: cannot allocate call info data structure
Explanation Allocation of the CCH323 call info structure failed. This is possibly due to the fact that system memory pool is exhausted.
Recommended Action This call will be terminated due to lack of resource


%CCH323-3-CANNOT_INSERT_CCB : [chars]: cannot insert control block [hex] to tree
Explanation Insertion of this CCH323 call control block to the RBTree failed. This can be related to a corrupted RBTree
Recommended Action This can be a catastrophic error


%CCH323-3-CANNOT_FIND_CCB : [chars]: cannot find CCH323 call control block based on callID [dec]
Explanation Cannot find a CCH323 call control block based on the specified callID
Recommended Action No action is required. This is an indication that some events happen out of sequence


%CCH323-3-CCAPI_DISCONNECT_ERROR : [chars]: cc_api_call_disconnected returns [dec]
Explanation An error is returned when CCH323 attempts to call cc_api_call_disconnected
Recommended Action None


%CCH323-3-CCAPI_CONNECT_ERROR : [chars]: cc_api_call_disconnected returns [dec]
Explanation An error is returned when CCH323 attempts to call cc_api_call_connected
Recommended Action None


%CCH323-3-CANNOT_CREATE_CRVHASH_TBL : [chars]: cannot create the H.323 crv hash table
Explanation Creation of the H.323 CRV Hash Table failed. This is possibly due to the fact that system memory pool is exhausted.
Recommended Action This can be a catastrophic error


%CCH323-3-BAD_IP_ADDRESS : [chars]: illegal destination [chars]
Explanation The IP address passed from CCAPI in the call setup request is invalid
Recommended Action Check the dial-peer configuration for the dial-peer that matches the called party number. Make sure that the session target field contains valid IP address. or DNS name


%CCH323-3-CALL_SETUP_FAILED : [chars]: call setup failed
Explanation The call setup request failed
Recommended Action Verify that the remote destination identified by the IP address is reachable


%CCH323-3-OSS_INIT_FAILED : [chars]: OSS init failure: errno = [dec]
Explanation OSS ASN1 initialization failed
Recommended Action This can be catastrophic


%CCH323-3-H225_SM_INIT_FAILED : [chars]: H.225.0 State Machine integrity check failed for state [chars]
Explanation H.225 State Machine integrity check failed
Recommended Action This can be catastrophic


%CCH323-3-H225_LIBRARY_INIT_FAILED : [chars]: H.225.0 library initialization failed
Explanation H.225.0 library initialization failed
Recommended Action This can be catastrophic


%CCH323-3-CCH323_UNKNOWN_EVENT : unknown event [hex]
Explanation Unknown CCH323 Event
Recommended Action No action is required


%CCH323-3-CCH323_RSCMON_SETUP_FAILURE : [chars][dec]
Explanation A failure was encountered in setting up the monitoring of H323 resources.
Recommended Action Try power cycling the system. LOG_STD_RECUR_ACTION


%CCH323-3-STRCALLHISFAIL : cch323_store_call_history: [chars]
Explanation Insert an active H323 call record into call history list failed
Recommended Action No action is required


%CCH323-2-GTWY_UNREGSTR : Gateway [chars] unregistered from Gatekeeper [chars]
Explanation Gateway unregistered from the Gatekeeper
Recommended Action Verify whether this is user intended or otherwise report this to the technical support representative.


%CCH323-2-GTKP_UNREGSTR : Gatekeeper [chars] requested unregister from Gateway [chars]
Explanation Gatekeeper requested unregister from Gateway
Recommended Action Verify whether this is user intended or otherwise report this to the technical support representative.


%CCH323-6-REGSTR : Gateway [chars] registered with Gatekeeper [chars]
Explanation Gateway registered with the Gatekeeper
Recommended Action no action is required


%CCH323-2-GTWY_REGSTR_FAILED : Gateway [chars] failed to register with Gatekeeper [chars] even after [dec] retries
Explanation Gateway failed to register with Gatekeeper
Recommended Action Report this immediately to the technical support representative.


%CCH323-2-GTWY_REGSTR_FAILED_ALT_GK : Gateway [chars] failed attempt to register with Alternate Gatekeeper [chars]
Explanation Gateway failed attempt to register with Alternate Gatekeeper
Recommended Action Report this immediately to the technical support representative.


%CCH323-2-E164_LENGTH_IS_NOT_SUPPORTED : [chars]: E164 address length [dec] is not supported
Explanation Received E164 address with the length that is not supported.
Recommended Action Report this immediately to the technical support representative.


%CCH323-3-CCH323_MALLOC_FAILED : [chars]: cannot allocate message buffer
Explanation Allocation of the CCH323 message buffer failed. This is possibly due to the fact that system memory pool is exhausted.
Recommended Action This can be a catastrophic error


%CCH323-3-INTERNAL_EVENT_QUEUE_INIT_FAILED : [chars]: Internal event queue initialization failed
Explanation Errors are found during initialization of internal event qeuue machanisa
Recommended Action This can be a catastrophic error


%CCH323-3-POSSIBLE_INTERNAL_EVENT_LOOP : [chars]: Exceeding limit on servicing internal event for the same call
Explanation The maximum limit on servicing internal event queue has exceeded the limit. The condition may be caused by internal loops on sending events between state machines.
Recommended Action This can be a severe error


%CCH323-3-MAXIMUM_INTERNAL_EVENT_BUFFERS_EXCEED : [chars]: Exceeding limit on allocating internal event buffers
Explanation The limit for allocating internal event buffers has been exceeded. The condition may be caused by internal loops on sending events between state machines.
Recommended Action This can be a severe error


%CCH323-3-CCH323_H225_SEND_EVENT_FAILED : [chars]: create send internal event [chars] to H.225 state machine failed
Explanation create and send event to H.225 state machine failed. This is possibly due to the missing call control block or not enough memory for event buffers
Recommended Action This can be a catastrophic error


%CCH323-3-CCH323_H245_SEND_EVENT_FAILED : [chars]: create and send event [chars] to H.245 state machine failed
Explanation create and send event to H.245 state machine failed. This is possibly due to the missing call control block or not enough memory for event buffers
Recommended Action This can be a catastrophic error


%CCH323-3-CCH323_RAS_SEND_EVENT_FAILED : [chars]: create and send event [chars] to RAS state machine failed
Explanation create and send event to RAS state machine failed. This is possibly due to the missing call control block or not enough memory for event buffers
Recommended Action This can be a catastrophic error


%CCH323-6-LONG_DUR_CALL_DETECTED : Long Duration Call is detected [chars]
Explanation The call is active for configured duration of long call
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.


%CCH323-6-CALL_PRESERVED : [chars]: H.323 call preserved due to socket closure or error, Call Id = [int], fd = [dec]
Explanation An H.225.0 or H.245 socket was closed due to a TCP FIN received from the remote endpoint or a socket error. Calls using these sockets for which call preservation was configured will be preserved. This is not an error, but call preservation can occasionally cause hung calls.
Recommended Action Use show h323 calls preserved command to get a list of all active preserved calls. Long duration preserved calls can then be cleared using clear call voice command.


CCK_QAT

%CCK_QAT-3-INIT_FAIL : [chars]: initialization failed ([chars])
Explanation CCK QAT initialization sequence failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


CD_FFP_IPSEC_PROXY

%CD_FFP_IPSEC_PROXY-2-FFP_INIT_FAILED : FFP Crypto device Proxy Agent initialization failure (result: [dec]).
Explanation Cisco internal software error. FFP Crypto device Procy Agent initialization detected critical failure. FFP Crypto device software library will not be functional while this condition exists.
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.


%CD_FFP_IPSEC_PROXY-2-FFP_PROXY_INIT_FAILED : FFP Crypto device Procy Agent Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. FFP Crypto device Procy Agent Proxy initialization detected that the IPC interface initialization failed. FFP Crypto device Procy Agent proxy will not be functional while this conidtion exists.
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.


%CD_FFP_IPSEC_PROXY-3-FFP_PROXY_IPSEC_SA_CRT_FAILED : FFP Crypto device Procy Agent Proxy IPSec SA create failure (result: [dec]).
Explanation Cisco internal software error. FFP Crypto device Procy Agent Proxy message processing detected IPSec SA create failure. The request is rejected as the result of this condition.
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.


%CD_FFP_IPSEC_PROXY-3-ESG_IPSEC_KAT_TEST_FAILED : Cryptographic Known-Answer Test failure (result: [chars])
Explanation Cisco internal software error. Cryptographic Known-Answer Tests. Error due to one of the Cryptographic Power-on Self-tests (Known-Answer Tests) not returning the expected value.
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.


CD_SW_IPSEC_SHIM

%CD_SW_IPSEC_SHIM-2-SHIM_INIT_FAILED : QFP Crypto device software library initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP Crypto device software library initialization detected critical failure. QFP Crypto device software library will not be functional while this condition exists.
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.


%CD_SW_IPSEC_SHIM-2-SHIM_PROXY_INIT_FAILED : QFP Crypto device software library Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP Crypto device software library Proxy initialization detected that the IPC interface initialization failed. QFP Crypto device software library proxy will not be functional while this conidtion exists.
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.


%CD_SW_IPSEC_SHIM-3-SHIM_PROXY_IPSEC_SA_CRT_FAILED : QFP Crypto device software library Proxy IPSec SA create failure (result: [dec]).
Explanation Cisco internal software error. QFP Crypto device software library Proxy message processing detected IPSec SA create failure. The request is rejected as the result of this condition.
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.


%CD_SW_IPSEC_SHIM-2-KAT_TEST_FAILED : QFP Crypto device software library kat test failure (result: [dec]).
Explanation Cisco internal software error. QFP Crypto device software library detected critical failure. QFP Crypto device software library will not be functional while this condition exists.
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.


CD_SW_SSL_SHIM

%CD_SW_SSL_SHIM-2-SHIM_INIT_FAILED : QFP Crypto device software library initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP Crypto device software library initialization detected critical failure. QFP Crypto device software library will not be functional while this condition exists.
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.


%CD_SW_SSL_SHIM-2-SHIM_PROXY_INIT_FAILED : QFP Crypto device software library Proxy IPC interface initialization failure (result: [dec]).
Explanation Cisco internal software error. QFP Crypto device software library Proxy initialization detected that the IPC interface initialization failed. QFP Crypto device software library proxy will not be functional while this conidtion exists.
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.


%CD_SW_SSL_SHIM-3-SHIM_PROXY_SSL_CTX_ALLOC_FAILED : QFP Crypto device software library Proxy IPSec CTX create failure (result: [dec]).
Explanation Cisco internal software error. QFP Crypto device software library Proxy message processing detected IPSec CTX create failure. The request is rejected as the result of this condition.
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.


CEF_PROXY through CHAT

CEF_PROXY

%CEF_PROXY-3-PROXY_IPC_ADJ_ID_HASH_FAILED :
Explanation Getting Hash Address failed.
Recommended Action LOG_STD_ACTION


%CEF_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]
Explanation IPC handler initialization failed.
Recommended Action LOG_STD_ACTION


%CEF_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]
Explanation Received an invalid IPC messages subtype.
Recommended Action LOG_STD_ACTION


%CEF_PROXY-3-PROXY_IPC_OCE_CHAIN_PTR_FAILED : [hex]
Explanation Null OCE Chain pointer.
Recommended Action LOG_STD_ACTION


%CEF_PROXY-3-PROXY_IPC_PACKET_ALLOCATION_FAILED : [hex]
Explanation Failed to allocate packet buffer for IPC
Recommended Action LOG_STD_ACTION


%CEF_PROXY-3-PROXY_IPC_PACKET_SEND_FAILED : [hex]
Explanation Failed to send IPC packet.
Recommended Action LOG_STD_ACTION


%CEF_PROXY-3-PROXY_IPC_ADJ_IDX_FAILED : [hex]
Explanation Failed to get adjacency index from IPC packet.
Recommended Action LOG_STD_ACTION


CELLWAN

%CELLWAN-2-NO_PROCESS : Could not start process [chars]
Explanation Could not start one of the processes.
Recommended Action Add more memory.


%CELLWAN-2-SEND_TIMEOUT : [chars] not responding
Explanation The cellular modem is not responding.
Recommended Action If the problem persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-HEART_BEAT_TIMEOUT : No heart beat signal from [chars]
Explanation The cellular modem is not responding.
Recommended Action If the problem persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-MODEM_TOO_HOT : [chars] modem will be [chars]
Explanation Modem radio temperature has reached critical point. The call will be disconnected and the modem could be shutdown.
Recommended Action Check if the router fans are working properly.


%CELLWAN-2-MODEM_NOT_ACTIVATED : [chars] modem has not been activated
Explanation The cellular modem has not been activated by the cellular provider.
Recommended Action Please check the user documentation on how to activate the modem. The cellular modem needs to be activated before it can be used on a cellular network.


%CELLWAN-2-MODEM_RADIO : [chars] Modem radio has been turned [chars]
Explanation Modem radio has been turned on/off.
Recommended Action No action if the message appears during bootup. Otherwise please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x radio command and <CmdBold>show tech-support)


%CELLWAN-2-MODEM_UP : Modem in slot [dec]/[dec] is now UP
Explanation The cellular modem is now UP.
Recommended Action No action if the message appears during bootup. Otherwise please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-MODEM_DOWN : Modem in slot [dec]/[dec] is DOWN
Explanation The cellular modem is not operational.
Recommended Action This is expected during modem firmware upgrade and modem activation. If the problem happens during other times, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-5-FIRMWARE_SWITCH : Firmware switchover initiated for modem in slot [dec]/[dec]
Explanation Firmware switchover caused by user request.
Recommended Action No action is required.


%CELLWAN-5-MODEM_BOOT_READY : Modem in slot [dec]/[dec] is in Boot Ready Mode.. Please perform FW upgrade
Explanation The cellular modem is not operational.
Recommended Action This is expected during modem firmware upgrade and modem activation. If the problem happens during other times, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-UNSUPPORTED_CELLULAR_NIM : Unsupported Cellular NIM inserted in slot [int]/[int]
Explanation This NIM is not supported for the current software release
Recommended Action Please contact TAC for supported software release for this NIM


%CELLWAN-2-DYING_GASP_NOT_SUPPORTED : Dying Gasp Feature is not supported in Cellular slot [int]/[int]
Explanation This NIM is not supporting Dying Gasp Feature.
Recommended Action Please contact TAC for Dying Gasp Feature Supported NIM


%CELLWAN-2-MODEM_INIT_TIMEOUT : Cellular modem initialization timeout for [chars]
Explanation Modem failed to initialize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CELLWAN-2-MICRO_DNLD_START_FAIL : Modem returned following error to Download Start Request:[chars]
Explanation Modem Firmware Download Start Request Failed. It generally means that firmware binary file is wrong.
Recommended Action Please make sure that the firmware binary file is correct. If unsure about validity of the file, please provide the following: LOG_STD_SH_CMD_ACTION(show flash:<noCmdBold> command and <CmdBold>show controller cellular x/x/x all)


%CELLWAN-2-MICRO_FW_DNLD_FAIL : Modem returned following error to Download Request:[chars]
Explanation Modem Firmware Download Continue Request Failed. It generally means that firmware binary file is corrupt.
Recommended Action Please make sure that the firmware binary file is correct. If unsure about validity of the file, please provide the following: LOG_STD_SH_CMD_ACTION(show flash:<noCmdBold> command and <CmdBold>show controller cellular x/x/x all)


%CELLWAN-2-MICRO_DNLD_END_FAIL : Modem returned following error to Download End Request:[chars]
Explanation Modem Firmware Download End Request Failed
Recommended Action Please make sure that the firmware binary file is correct. If unsure about validity of the file, please provide the following: LOG_STD_SH_CMD_ACTION(show flash:<noCmdBold> command and <CmdBold>show controller cellular x/x/x all)


%CELLWAN-2-MICRO_FLASH_PRGM_FAIL : Modem returned following error to Flash Program Request:[chars]
Explanation Modem failed to launch the new firmware.
Recommended Action Please make sure that the firmware binary file is correct. If unsure about validity of the file, please provide the following: LOG_STD_SH_CMD_ACTION(show flash:<noCmdBold> command and <CmdBold>show controller cellular x/x/x all)


%CELLWAN-2-SIM_FAILURE : [[chars]]: SIM read failed [chars]
Explanation If the SIM is not present, insert SIM in the SIM socket. If error still persists, SIM needs to be replaced.
Recommended Action Insert SIM if SIM is absent in the NIM. If error still persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-SIM_LOCKED : [[chars]]: SIM is locked [chars]
Explanation SIM is locked and no data call can be made till it is unlocked.
Recommended Action Contact service provider on how to unlock the SIM. If error still persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-SIM_REJECTED : [[chars]]: SIM rejected by the network [chars]
Explanation The SIM is not valid to be used in the network. A new valid SIM needs to be inserted in the SIM socket.
Recommended Action Insert valid SIM in the NIM SIM socket. If error still persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-SIM_CHV1_BLOCKED : [[chars]]: SIM is blocked. PUK is required to unblock the SIM [chars]
Explanation SIM is blocked and no data call can be made until it is unblocked using PUK.
Recommended Action Contact service provider to get PUK to unblock the SIM. Please execute 'cellular <unit> gsm sim unblock <puk> <new-pin>' for unblocking SIM and to set new PIN. If error still persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-SIM_MEP_LOCKED : [[chars]]: Invalid SIM or device locked to carrier [chars]
Explanation Invalid SIM or device locked to carrier
Recommended Action Insert valid SIM or contact service provider. If error still persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-SIM_CHV1_CONFIG_REMOVED : [[chars]]: CHV1 verfication failed [chars] : Incorrect PIN configured. Erased the CHV1 code from router runnning configuration to avoid SIM blocking during modem reset/powercycle. !!!WARNING: If the incorrect PIN is saved in router start-up configuration, please remove it manually to avoid SIM blocking during router reload
Explanation SIM CHV1 verfication failed. Incorrect PIN configured.
Recommended Action Please remove incorrect PIN if saved in startup configuration or configure correct PIN. If error still persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-SIM_SECURITY_SHUTDOWN : [[chars]]: CHV1 PIN is configured while SIM is unlocked [chars]. Shutting down all PDP interfaces
Explanation CHV1 is configured while SIM is unlocked The SIM is not valid to be used in the network. A new valid locked SIM needs to be inserted in the SIM socket.
Recommended Action Insert valid SIM in the NIM SIM socket or remove CHV1 configuration. If error still persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-SIM_NOT_READY : [chars] Modem is not ready. SIM status may be not current.
Explanation SIM access cannot be granted or may return an error when : (1) The modem is not up or during a reset. (2) The SIM has gone bad.
Recommended Action (1) Wait till MODEM UP message is seen from the console before accessing SIM. (2) Replacing with a working SIM. LOG_STD_SH_CMD_ACTION(show cellular x/x/x security<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-SIM_NOT_PRESENT : [[chars]]: SIM is not present in Slot [dec]
Explanation SIM has not been detected in the NIM SIM socket
Recommended Action Insert a valid sim in the NIM SIM socket.


%CELLWAN-6-SIM_PRESENT : [[chars]]: SIM is present in Slot [dec]
Explanation SIM has been detected in the SIM socket
Recommended Action No action


%CELLWAN-6-SIM_INSERTED : [[chars]]: SIM in slot [dec] has been inserted
Explanation SIM is inserted to the slot.
Recommended Action No action


%CELLWAN-6-SIM_REMOVED : [[chars]]: WARNING: SIM in slot [dec] has been removed
Explanation SIM is removed from the slot.
Recommended Action No action


%CELLWAN-2-SIM_SWITCH_FAILURE : [[chars]]: Failed to switch to SIM slot [dec] !!
Explanation Failed to switch to the requested NIM SIM slot
Recommended Action Examine SIM in the indicated slot


%CELLWAN-5-SIM_DETECT_START : [[chars]]: SIM presence detection starts !!
Explanation SIM presence detection has started
Recommended Action No action is required.


%CELLWAN-5-SIM_DETECT_COMPLETE : [[chars]]: SIM presence detection has completed !!
Explanation SIM presence detection has completed
Recommended Action No action is required.


%CELLWAN-5-SIM_ACTIVATION : [[chars]]: SIM slot [dec] is being activated !!
Explanation The request to activate the indicated SIM slot has been sent to the modem
Recommended Action No action is required.


%CELLWAN-5-SIM_ACTIVE : [[chars]]: SIM slot [dec] is Active !!
Explanation The indicated SIM slot is active.
Recommended Action No action is required.


%CELLWAN-5-SIM_ACTIVATION_TIMEOUT : [[chars]]: SIM slot [dec] activation request timeout !!
Explanation Timeout on the request sent to the modem to activate the indicated SIM slot
Recommended Action No action is required.


%CELLWAN-5-SIM_ACQUISITION_TIMEOUT : [[chars]]: SIM slot [dec] Acquisition Timer timeout !!
Explanation Timeout on the SIM slot acquisition timer, initiate sim switching request to the alter SIM slot
Recommended Action No action is required.


%CELLWAN-5-SIM_FAILOVER_TIMEOUT : [[chars]]: SIM slot [dec] Failover Timer timeout !!
Explanation Timeout on the SIM slot failover timer, initiate sim switching request to the alter SIM slot
Recommended Action No action is required.


%CELLWAN-2-INTERFACE_GOING_DOWN : [chars] is being shutdown temporarily due to authentication failure for [dec] secs.
Explanation The interface is being shutdown because the call could not be connected due to PPP authentication failures. The interface will be brought up after the specified time. This is to prevent frequent calls being attempted if authentication problems are not fixed.
Recommended Action Activate the modem again by following the steps in the user docs. If the problem persists contact the wireless service provider. LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-OMA_DM_NI_ALERT : [[chars]]: OMA DM NI Alert is received for [chars] Please execute 'cellular <unit> cdma activate oma-dm ni-alert [allow | deny]'
Explanation OMA DM Network-Initiated alert is received by modem
Recommended Action Please execute 'cellular <unit> cdma activate oma-dm ni-alert [allow | deny]'. It is recommended to allow the session so as to update device configuration or PRL that is being pushed by carrier. The session can be allowed when data call is disconnected. NI session will disconnect active call and service will be interrupted until the session is completed. Please use 'show cellular <unit> oma-dm ni-alert' to view the pending NI alert. Otherwise, deny the session if update is not required. For any support, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-OMA_DM_NO_OP : [[chars]]: OMA DM [chars] could not be completed. Please try again later. If the problem persists, you may need to contact Customer Service.
Explanation OMA DM session state is received by modem
Recommended Action Activate the modem again by following the steps in the user docs. If the problem persists contact the wireless service provider. LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-OMA_DM_ERROR : [[chars]]: OMA DM [chars] Failed - Error:[hex]([chars])
Explanation OMA DM session state is received by modem
Recommended Action Activate the modem again by following the steps in the user docs. If the problem persists contact the wireless service provider. LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-OMA_DM_HFA_PENDING : [[chars]]: OMA DM [chars], waiting for retry in [int] seconds
Explanation OMA DM session state is received by modem
Recommended Action Activate the modem again by following the steps in the user docs. If the problem persists contact the wireless service provider. LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-OMA_DM_ACTIVE : [[chars]]: OMA DM [chars] session is active
Explanation OMA DM session state is received by modem
Recommended Action Activate the modem again by following the steps in the user docs. If the problem persists contact the wireless service provider. LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-OMA_DM_SUCCESS : [[chars]]: OMA DM [chars] completed successfully
Explanation OMA DM session state is received by modem
Recommended Action Activate the modem again by following the steps in the user docs. If the problem persists contact the wireless service provider. LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-OMA_DM_NO_PRL : [[chars]]: OMA DM - No PRL update available
Explanation OMA DM session state is received by modem
Recommended Action Activate the modem again by following the steps in the user docs. If the problem persists contact the wireless service provider. LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-POWER_SAVE_MODE : [[chars]]: is in Power save mode. Command ignored.
Explanation radio is currently OFF on this NIM
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.


%CELLWAN-5-SMS_SERVICE_AVAILABLE : [chars] SMS service is now available.
Explanation You can send and receive text messages on this cellular interface
Recommended Action No action is required.


%CELLWAN-5-SMS_SERVICE_UNAVAILABLE : [chars] SMS service is now unavailable.
Explanation You can not send and receive text messages on this cellular interface
Recommended Action No action is required.


%CELLWAN-5-INCOMING_SMS : [chars] has just received new incoming SMS.
Explanation New incoming text messages arrived at cellular interface
Recommended Action Please do 'cellular <unit> gsm|cdma sms view' to read SMS


%CELLWAN-5-OUTGOING_SMS_SENT : [chars] has just sent an outgoing SMS successfully.
Explanation Outgoing text message was sent successfully from cellular interface
Recommended Action No action is required.


%CELLWAN-4-OUTGOING_SMS_ERROR : [chars] failed to send an outgoing SMS.
Explanation Outgoing text message failed to send from cellular interface
Recommended Action Please do 'show cellular <unit> sms' to see error code


%CELLWAN-4-OUTGOING_SMS_SERV_UNAVAIL : [chars] can't send an SMS because SMS service is not available.
Explanation Text message service is not available on specified cellular interface
Recommended Action Check modem is powered up, radio is not in power saving mode, and SIM is inserted


%CELLWAN-2-SMS_ARCH_PATH_UNCONFIGURED : [chars] failed to archive SMS because 'gsm|cdma|lte sms archive path' under cellular controller is not configured.
Explanation 'gsm|cdma|lte sms archive path' under cellular controller must be configured first before background incoming text message archive can function properly
Recommended Action Configure 'gsm|cdma|lte sms archive path' under cellular controller


%CELLWAN-5-SMS_INBOX_ARCH_DONE : [chars] has just archived all incoming SMS to FTP server successfully.
Explanation Incoming text messages were archived to FTP server successfully from cellular interface
Recommended Action No action is required.


%CELLWAN-2-SMS_INBOX_ARCH_OPEN_ERROR : [chars] failed to open [chars] to archive incoming SMS.
Explanation Incoming text messages archive to FTP server failed because the FTP URL configured with 'gsm|cdma|lte sms archive path' under cellular controller can not be opened
Recommended Action Please check that the FTP server configured under cellular controller is reachable, and that the directory exists


%CELLWAN-2-SMS_INBOX_ARCH_WRITE_ERROR : [chars] failed to write [chars] to archive incoming SMS.
Explanation Incoming text messages archive to FTP server failed because of write error to the FTP URL configured with 'gsm|cdma|lte sms archive path' under cellular controller
Recommended Action Please check that the FTP server configured under cellular controller with 'gsm|cdma|lte sms archive path' is reachable, and has enough storage space


%CELLWAN-5-SMS_INBOX_MSG_ARCH_DONE : [chars] has just archived an incoming SMS to FTP server successfully.
Explanation An incoming text message was archived to FTP server successfully from cellular interface
Recommended Action No action is required.


%CELLWAN-5-SMS_OUTBOX_ARCH_DONE : [chars] has just archived an outgoing SMS to FTP server successfully.
Explanation An outgoing text message was archived to FTP server successfully from cellular interface
Recommended Action No action is required.


%CELLWAN-2-SMS_OUTBOX_ARCH_OPEN_ERROR : [chars] failed to open [chars] to archive an outgoing SMS.
Explanation Outgoing text message archive to FTP server failed because the FTP URL configured with 'gsm|cdma|lte sms archive path' under cellular controller can not be opened
Recommended Action Please check that the FTP server configured under cellular controller is reachable, and that the directory exists


%CELLWAN-2-SMS_OUTBOX_ARCH_WRITE_ERROR : [chars] failed to write [chars] to archive an outgoing SMS.
Explanation Outgoing text message archive to FTP server failed because of write error to the FTP URL configured with 'gsm|cdma|lte sms archive path' under cellular controller
Recommended Action Please check that the FTP server configured under cellular controller with 'gsm|cdma|lte sms archive path' is reachable, and has enough storage space


%CELLWAN-4-CELLULAR_FW_UNSUPPORTED : [chars]: Unsupported or older modem firmware [chars] detected, please upgrade modem to supported firmware of at least [chars]
Explanation The current firmware on specified cellular interface is not supported. Any actions and errors that occur will not be supported until the fw is upgraded to at least the version requested
Recommended Action Please upgrade to the latest FW from online using 'microcode reload'


%CELLWAN-2-DMLOG_FILTER_FILE_OPEN_ERROR : [chars] failed to open [chars] to read DM log filter.
Explanation Failed to open filter file from the location configured with 'gsm|cdma|lte modem dm-log filter' under cellular controller
Recommended Action Please check that the path configured under cellular controller is reachable


%CELLWAN-2-DMLOG_OUTPUT_FILE_OPEN_ERROR : [chars] failed to open [chars] to archive DM log files.
Explanation Saving DM packets to file system failed. Output file URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller can not be opened
Recommended Action Please check that the path configured under cellular controller is reachable


%CELLWAN-2-DMLOG_OUTPUT_WRITE_ERROR : [chars] failed to write [chars] DM packets to configured file system
Explanation Saving DM packets to file system failed because of write error to the URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller
Recommended Action Please check that the URL configured under cellular controller with 'gsm|cdma|lte modem dm-log output path' is reachable, and has enough storage space


%CELLWAN-2-DMLOG_OUTPUT_SPACE_FULL : [chars] DM log file storage is full!
Explanation Saving DM packets to file system failed because there is no more space left on the URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller
Recommended Action Please delete existing log files from the specified URL 'gsm|cdma|lte modem dm-log output path' or upload them to the server then re-enable logging.


%CELLWAN-5-DMLOG_AUTOSTOP_TRIGGER : [chars]: DM logging will be stopped in [dec] [chars], autostop trigger event [chars] set
Explanation DM log autostop trigger event configured, DM logging will be stopped after the timer expiry
Recommended Action No action is required.


%CELLWAN-5-DMLOG_AUTOSTOP_TIMER_EXPIRY : [chars]: DM logging stopped
Explanation DM logging is stopped due to autostop trigger timer expiry
Recommended Action No action is required.


%CELLWAN-5-DMLOG_AUTOSTOP_TIMER_CANCEL : [chars]: DM logging autostop timer canceled
Explanation DM logging autostop timer is canceled
Recommended Action No action is required.


%CELLWAN-5-DMLOG_DISABLE_OIR : [chars]: OIR Detected. DM logging stopped
Explanation DM logging is stopped due to OIR
Recommended Action No action is required.


%CELLWAN-5-DMLOG_DISPLAY_OUTPUT_PATH_EXTERN : DM log output path = bootflash:/core/modules
Explanation DM log output path set to bootflash:/core/modules
Recommended Action


%CELLWAN-5-DMLOG_DISPLAY_OUTPUT_PATH_INTEGRATED : DM log output path = bootflash:
Explanation DM log output path set to bootflash:/
Recommended Action


%CELLWAN-2-SVBLOG_OUTPUT_FILE_OPEN_ERROR : [chars] failed to open [chars] to archive SVB log files.
Explanation Saving SVB packets to file system failed. Output file URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller can not be opened
Recommended Action Please check that the path configured under cellular controller is reachable


%CELLWAN-2-SVBLOG_OUTPUT_WRITE_ERROR : [chars] failed to write [chars] SVB packets to configured file system
Explanation Saving SVB packets to file system failed because of write error to the URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller
Recommended Action Please check that the URL configured under cellular controller with 'gsm|cdma|lte modem dm-log output path' is reachable, and has enough storage space


%CELLWAN-2-SVBLOG_OUTPUT_SPACE_FULL : [chars] SVB log file storage is full!
Explanation Saving SVB packets to file system failed because there is no more space left on the URL configured with 'gsm|cdma|lte modem dm-log output path' under cellular controller
Recommended Action Please delete existing log files from the specified URL 'gsm|cdma|lte modem dm-log output path' or upload them to the server then re-enable logging.


%CELLWAN-5-SVBLOG_AUTOSTOP_TRIGGER : [chars]: SVB logging will be stopped in [dec] minutes, autostop trigger event [chars] set
Explanation SVB log autostop trigger event configured, SVB logging will be stopped after the timer expiry
Recommended Action No action is required.


%CELLWAN-5-SVBLOG_AUTOSTOP_TIMER_EXPIRY : [chars]: SVB logging stopped
Explanation SVB logging is stopped due to autostop trigger timer expiry
Recommended Action No action is required.


%CELLWAN-5-SVBLOG_AUTOSTOP_TIMER_CANCEL : [chars]: SVB logging autostop timer canceled
Explanation SVB logging autostop timer is canceled
Recommended Action No action is required.


%CELLWAN-2-WCDMA_ALL_BAND_UNDEFINED : [[chars]]: wcdma-all band not supported
Explanation wcdma-all band is not supported by modem or not defined
Recommended Action Please contact TAC support LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-CALL_SETUP_FAIL : [chars] data call setup failed due to [chars].
Explanation Data call setup failed because the IP address configured under cellular interface does not match the IP address assigned by the network
Recommended Action Please check the IP address configuration under cellular interface


%CELLWAN-2-MDM_LINK_FAILURE : [chars] direct IP synchronization process fails after [dec] attempts
Explanation Direct IP synchronization fails to come up after maximum number of attempts.
Recommended Action Contact customer service if the problem persists.


%CELLWAN-3-GPS_FAIL_START_TRACK : [[chars]] GPS failed to start tracking - [chars] [[hex]], please try again
Explanation Modem failed to enable GPS mode due to error indicated. Fix that error and try again.
Recommended Action Fix error indicated and try enabling GPS again.


%CELLWAN-3-GPS_FAIL_END_SESSION : [[chars]] GPS failed to end location fix session - [chars] [[hex]], please try again
Explanation Modem failed to disable GPS mode due to error indicated. Fix that error and try again.
Recommended Action Fix error indicated and try disabling GPS again.


%CELLWAN-2-GSM_PROFILE_UNDEFINED : [[chars]]: Default profile [dec][chars] does not exist. Please execute 'cellular <unit> gsm profile create <profile #>' to create the profile.
Explanation Default profile is undefined. the profile does not exist because it is not defined or is deleted.
Recommended Action Create the profile by cellular exec cli. If error still persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-3-GSM_PROFILE_CREATION_FAILURE : [[chars]] GSM profile creation fails - [chars] [[hex]], please try again
Explanation Modem failed to create the GSM profile due to error indicated. Fix that error and try again.
Recommended Action Fix error indicated and try creating GSM profile again.


%CELLWAN-2-MODEM_TIMEOUT : Modem in [chars] not responding
Explanation The cellular modem is not responding.
Recommended Action If the problem persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-4-CELLULAR_MODEM_SKU_MISMATCH : [chars]: Mismatch detected between installed modem [chars][SKU ID [chars]] on SKU type [chars]. Expected modem for this SKU is [chars][SKU ID [chars]]
Explanation Incorrect modem type has been installed on this SKU. Any actions and issues caused by it will not be supported
Recommended Action Please contact the cisco customer service to replace the card


%CELLWAN-1-POOL_INIT_FAIL : cellular pool init failed for subslot [dec]/[dec] pool name [chars]
Explanation The NIM cellular pool init failed for this module.
Recommended Action If the problem persists, please provide the following: LOG_STD_SH_CMD_ACTION(show cellular x/x/x all<noCmdBold> command and <CmdBold>show tech-support)


%CELLWAN-2-QOS_ENABLED : QoS Feature in [chars] is now activated
Explanation QoS Feature is now enabled and activated in the modem.
Recommended Action QoS Feature is now enabled and activated in the modem.


%CELLWAN-2-QOS_NW_STATUS : Network status for QoS feature is [chars] in [chars].
Explanation Network status for QoS feature is either enabled or disabled by the carrier.
Recommended Action check with carrier if you expect QoS feature but it is disabled


%CELLWAN-2-QOS_PRI_EVENT_STATUS : QoS Event Status = [dec] for default bearer in [chars] in [chars].
Explanation QoS Event Status for default bearer for the cellular interface.
Recommended Action check with carrier to see if the default bearer config is changed


%CELLWAN-2-BEARER_UP : Instance id=[dec], [chars] bearer (bearer_id=[int]) QCI=[dec] in [chars] is now UP
Explanation default/dedicated bearer has been added.
Recommended Action Check the TFT rules of the dedicated bearer by doing show cellular and configure the host QOS configuration to match the TFT rules


%CELLWAN-2-BEARER_DOWN : Instance id=[dec], [chars] bearer (bearer_id=[int]) QCI=[int] in [chars] is now down.
Explanation default/dedicated bearer has been deleted.
Recommended Action Host QOS configuration may need to be modified to match the modem configuration


%CELLWAN-2-BEARER_DELETED : [chars] bearer (bearer_id=[int]) in [chars] is now deleted.
Explanation default/dedicated bearer has been deleted.
Recommended Action Host QOS configuration may need to be deleted to match the modem configuration


%CELLWAN-2-BEARER_SUSPENDED : Instance id=[dec], [chars] bearer (bearer_id=[int]) QCI=[dec] in [chars] is now suspended.
Explanation default/dedicated bearer has been suspended.
Recommended Action Host QOS configuration may need to be suspended to match the modem configuration


%CELLWAN-2-BEARER_MODIFIED : Instance id=[dec], [chars] bearer (bearer_id=[int]) QCI=[dec] configuration in [chars] is modified
Explanation default/dedicated bearer configuration has been modified.
Recommended Action Check the TFT rules of the dedicated bearer by doing show cellular and configure the host QOS configuration to match the TFT rules


%CELLWAN-2-BEARER_CONGESTION_ON : Instance id=[dec], [chars] bearer (bearer_id=[int]) QCI=[int] in [chars] is congested
Explanation Traffic congestion present in the dedicated bearer. If it does not clear, make sure the host QOS configuration matches the dedicated bearer configuration
Recommended Action Check the MBR of the dedicated bearer by doing show cellular and configure the host QOS configuration to match MBR of the dedicated bearer.


%CELLWAN-2-BEARER_CONGESTION_OFF : Instance id=[dec], [chars] bearer (bearer_id=[int]) QCI=[int] in [chars] is NOT congested now
Explanation Traffic congestion has cleared in the dedicated bearer
Recommended Action No action is needed


%CELLWAN-2-DEDICATED_BEARER_STATUS_UNKNOWN : Instance id=[dec], [chars] bearer (bearer_id=[int]) QCI=[int] configuration in [chars] is unknown=[dec]
Explanation Dedicated bearer configuration status is unknown.
Recommended Action Check the TFT rules of the dedicated bearer by doing show cellular and report the TFT rules to the carrier.


%CELLWAN-4-MANUAL_PLMN_SELECTION_FAILED : Manual/Force PLMN Selection Failed. [chars]
Explanation Manual/Force PLMN Selection Failed
Recommended Action Please use Different PLMN or check number of MNC Bits in PLMN Selection


%CELLWAN-4-DG_SMS_CONFIG_FAILED : Dying Gasp SMS Configuration Failed. [chars]
Explanation Dying Gasp SMS Configuration Failed.
Recommended Action Please try Dying Gasp SMS Configuration later


%CELLWAN-4-DG_DETACH_CONFIG_FAILED : Dying Gasp Detach Configuration Failed. [chars]
Explanation Dying Gasp Detach Configuration Failed.
Recommended Action Please try Dying Gasp Detach Configuration later


%CELLWAN-4-MODEM_RESTART_IND : [chars] Modem restart [chars]
Explanation Modem Restart Indication
Recommended Action No action is needed


%CELLWAN-4-MODEM_COMM_FAIL : Communication between Modem and IOS failed: [chars]
Explanation Communication between Modem and IOS Failed
Recommended Action Modem Reset will recover


%CELLWAN-6-CELLULAR_BACKOFF_START : [chars]: Cellular back-off has started on PDN [dec]
Explanation Back off has started because of certain error codes from network side
Recommended Action


%CELLWAN-6-CELLULAR_BACKOFF_STOP : [chars]: Cellular back-off has stopped on PDN [dec]
Explanation Back off has stopped
Recommended Action


%CELLWAN-6-CELLULAR_NETWORK_ATTACH_FAILURE : [chars]: Cellualr network attachment failure. Reject Cause [dec], [chars].
Explanation Network attachment failure
Recommended Action Check 3GPP Table 10.5.95/3GPP TS 24.008 for information


%CELLWAN-2-LINK_RECOVERY : [chars]: Cellular Modem has been power cycled : [chars]
Explanation Link Recovery Process has detected an inconsistent state of the modem
Recommended Action


%CELLWAN-2-DYING_GASP_POWER_FAILURE : Dying Gasp SMS will not be sent out by Modem in slot [dec]/[dec] due to standby power failure. Please contact TAC.
Explanation Modem doesn't have enough power to send Dying Gasp SMS
Recommended Action Please contact TAC


%CELLWAN-2-DYING_GASP_POWER_SUCCESS : Modem in slot [dec]/[dec] has sufficient power to send Dying Gasp SMS
Explanation Modem has sufficient power to send Dying Gasp SMS
Recommended Action No action is needed


%CELLWAN-2-CRASHDUMP_SUCCESS : [chars]:Crashdump successfully logged in /bootflash/
Explanation Cellular Modem Crashdump files successfully logged to local flash.
Recommended Action


%CELLWAN-6-FOTA_DNLD_STARTED : [[chars]]: Firmware download started in cellular slot [dec]/[dec]
Explanation FOTA Cellular modem firmware download started.
Recommended Action


%CELLWAN-6-FOTA_DNLD_COMPLETE : [[chars]]: Firmware has been downloaded for modem in cellular slot [dec]/[dec]
Explanation FOTA Cellular modem firmware download started.
Recommended Action


%CELLWAN-6-FOTA_UPGRADE_STARTED : [[chars]]: Firmware upgrade started in cellular slot [dec]/[dec]. Modem will reset and come up with new firmware.
Explanation FOTA Cellular modem firmware upgraded started.
Recommended Action


%CELLWAN-6-FOTA_UPGRADE_SUCESS : [[chars]]: Firmware upgrade successful in cellular slot [dec]/[dec]
Explanation FOTA Cellular modem firmware upgraded successfully.
Recommended Action


%CELLWAN-6-FOTA_UPGRADE_TIMEOUT : [[chars]]: Firmware upgrade timed out in cellular slot [dec]/[dec]
Explanation FOTA Cellular modem firmware upgrade timed out.
Recommended Action


CEM

%CEM-1-ISSU_NOMEMORY : msgtxt_nomemory
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.


%CEM-3-ISSU_SENDFAILED : CEM ISSU: send message failed, rc = [dec]
Explanation The sending of a message has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CEM-4-ISSU_INCOMPATIBLE : cem-issu-compat: returned FALSE
Explanation The compatibility checking has failed
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


%CEM-4-ISSU_XFORM : [chars]: failed, rc=[chars]
Explanation The transform has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. Also 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.


CEMA

%CEMA-3-SPA_CMD_FAIL : [chars]: Command [chars]([dec]) failed ([chars] partial command dump [hex] [hex] [hex] [hex]
Explanation A failure occurred when sending a command to the SPA indicated in the error message.
Recommended Action SPA_CEMA_FAIL_ACTION


%CEMA-3-CEMA_ADD_FAIL : [chars]: CEMA SB addition failed for interface [chars]
Explanation A failure occurred when adding cema_sb to the interface shown in the error message.
Recommended Action SPA_CEMA_FAIL_ACTION


%CEMA-3-CLEAR_CONNECTION_STATS_FAIL : [chars]: clear connection stats failed ([chars])
Explanation A failure occurred when sending a clear connection stats command.
Recommended Action CEMA_CMD_FAIL_ACTION


%CEMA-3-CONNECTION_DELETE_FAIL : [chars]: connection delete failed ([chars])
Explanation A failure occurred when sending a connection delete command.
Recommended Action CEMA_CMD_FAIL_ACTION


%CEMA-3-ATM_VP_CONFIG_FAIL : [chars]: connection configuration failed for VP [int] ([chars])
Explanation A failure occurred when sending a VP configuration command.
Recommended Action CEMA_CMD_FAIL_ACTION


%CEMA-3-ATM_VC_CONFIG_FAIL : [chars]: connection configuration failed for VC [int]/[int] ([chars])
Explanation A failure occurred when sending a VC configuration command.
Recommended Action CEMA_CMD_FAIL_ACTION


%CEMA-3-CLEAR_INTERFACE_STATS_FAIL : [chars]: clear interface stats failed ([chars])
Explanation A failure occurred when sending a clear interface stats command.
Recommended Action CEMA_CMD_FAIL_ACTION


%CEMA-3-INTERFACE_DELETE_FAIL : [chars]: interface delete failed ([chars])
Explanation A failure occurred when sending an interface delete command.
Recommended Action CEMA_CMD_FAIL_ACTION


%CEMA-3-INTERFACE_CONFIG_FAIL : [chars]: interface configuration failed ([chars])
Explanation A failure occurred when sending an interface delete command.
Recommended Action CEMA_CMD_FAIL_ACTION


%CEMA-3-CARD_TYPE_CONFIG_FAIL : [chars]: card type configuration failed ([chars])
Explanation A failure occurred when sending a card type configuration command.
Recommended Action CEMA_CMD_FAIL_ACTION


CENT

%CENT-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper CENT software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%CENT-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper CENT software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%CENT-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the CENT feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the CENT feature will not function. LOG_STD_ACTION


CFC_LISP

%CFC_LISP-3-ALLOCATEFAIL : Failed to allocate memory for [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.


%CFC_LISP-3-SB_OPERATION_FAILED : Failed to [chars] subblock on [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.


%CFC_LISP-3-LOCAL_EID : Failed to [chars] local EID prefix [chars]/[int]
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.


%CFC_LISP-3-REMOTE_EID : Failed to [chars] remote EID prefix [chars]/[int][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.


%CFC_LISP-3-REMOTE_EID_PREFIX : Failed to [chars] remote EID prefix [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.


%CFC_LISP-3-NO_ADJ : Failed to find adjacency for [chars] [chars] [chars] [int]
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.


%CFC_LISP-3-NO_FIBIDB : Failed to find fibidb for [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.


%CFC_LISP-3-NO_SB : Failed to find subblock for [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.


%CFC_LISP-3-NO_TABLE : Failed to find table for [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.


%CFC_LISP-3-BG_PROCESS : Background process failed 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.


%CFC_LISP-3-SBINIT : Error initializing [chars] subblock data structure. [chars]
Explanation Initialization of the specified subblock data structure could not be accomplished.
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.


%CFC_LISP-3-TABLE_STATE : Error setting state for table [chars] to top-id [int], iid [int], role [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.


%CFC_LISP-3-TABLE_BIND : Error setting [chars] table [chars] for top-id [int], iid [int], [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.


%CFC_LISP-3-TREE_OP_FAIL : Tree [chars] failed for [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.


%CFC_LISP-3-VIF : Unable to [chars] virtual interface [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.


%CFC_LISP-3-ADJ_SEQ : Adjacency [chars] is still complete after interface shutdown
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.


%CFC_LISP-3-NO_VIF : Unable to find [chars]virtual interface [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.


%CFC_LISP-3-UNABLE_TO_IDENTIFY_TABLE : Unable to identify table for packet from [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.


%CFC_LISP-3-INVALID_INPUT : Invalid input [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.


%CFC_LISP-3-RLOC_VRF_IN_USE : RLOC vrfid [int] already in use by user [chars] top-id [int], cannot assign to top-id [int]
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.


%CFC_LISP-3-UNEXPECTED_PKT : [chars]: [hex]
Explanation A packet with an unexpected protocol was given to the LISP datapath.
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.


%CFC_LISP-3-UNKNOWN_PAYLOAD : Dropping LISP encapsulated packet, unknown payload [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.


%CFC_LISP-5-IGNOREICMPMTU : Ignoring received ICMP Type 3 Code 4, [chars]->[chars] next hop mtu [int], due to pmtu min or max setting
Explanation An ICMP Type 3 Code 4 (fragmentation needed and DF set) packet has been received. This packet has specified a Next-Hop MTU that is smaller or greater than the current minimum or maximum path MTU discovery mtu value. The ICMP packet has been ignored and the MTU has not been changed.
Recommended Action If you want the ICMP packet to be accepted and used, use the ip lisp pmtu min NUMBER max NUMBER command to decrease the minimum MTU allowed and/or increase the maximum MTU that is allowed.


%CFC_LISP-5-IGNOREICMPV6MTU : Ignoring received ICMPv6 Type 2, [chars]->[chars] next hop mtu [int], due to pmtu min or max setting
Explanation An ICMPv6 Type 2 (Packet Too Big) packet has been received. This packet has specified a Next-Hop MTU that is smaller or greater than the current minimum or maximum path MTU discovery mtu value. The ICMP packet has been ignored and the MTU has not been changed.
Recommended Action If you want the ICMP packet to be accepted and used, use the ipv6 lisp pmtu min NUMBER max NUMBER command to decrease the minimum MTU allowed and/or increase the maximum MTU that is allowed.


%CFC_LISP-3-IPL_SRC : Failed to [chars] IPL source [chars] [chars]/[int][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.


%CFC_LISP-3-PUSH_CNTR : Failed to [chars] push counter for [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.


%CFC_LISP-3-ELIG_OCE : Failed to [chars] LISP eligibility oce [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.


%CFC_LISP-3-DECAP_OCE : Failed to [chars] LISP decapsulation OCE: [chars][chars]
Explanation An operation dealing with a LISP decapsulation OCE encountered an error. The error message will indicate which operation failed, and the address-family context.
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.


%CFC_LISP-3-SIGNAL_OCE : Failed to [chars] LISP signal OCE [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.


%CFC_LISP-3-TIMESTAMP_CTRL_PKT : Failed to timestamp LISP control packet
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.


%CFC_LISP-3-FREE_WITH_DEPS : Request to remove dependency sb on [chars] with dependents
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.


%CFC_LISP-3-DEP_ELEM : Request to [chars] dependency [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.


%CFC_LISP-3-ADJ : Request to [chars] adjacency [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.


%CFC_LISP-5-ADJ_STACK : Stacking adjacency [chars] [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.


%CFC_LISP-3-XDR_REG_ERR : Failed to register XDR client [chars] ([int]), error [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.


%CFC_LISP-3-XDR_LEN_ERR : Failed to [chars] XDR message [chars] len [int] > max [int]
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.


%CFC_LISP-3-ISSU_REG_ERR : Failed to register [chars] for ISSU client [chars] ([int]) entity [int], error [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.


%CFC_LISP-3-ISSU_NEGO_ERR : Failed to negotiate [chars] for XDR client [chars], error [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.


%CFC_LISP-3-ISSU_XFORM_ERR : Failed to ISSU transform XDR message [chars], error [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.


%CFC_LISP-3-UNKN_INSTANCE : Unknown instance, unable to find/create virtual interface
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.


%CFC_LISP-3-WALK_DEP : Walking dependents [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.


%CFC_LISP-3-TERM_ADJ : Terminal 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.


%CFC_LISP-5-BELOW_MIN_MTU : Cannot set [chars] MTU for RLOC [chars] to [int], [chars] MTU for [chars] [chars] is [int], below minimum MTU [int]+[int] required for LISP encap
Explanation Unable to set the EID payload MTU for a remote RLOC below the minimal MTU, this will cause the encapsulated packet to be bigger than the MTU of the path to the remote RLOC, and may cause packet loss.
Recommended Action Increase the MTU of the path to the remote RLOC


%CFC_LISP-3-DEPRECATED_API : Use of a deprecated API [chars][chars]
Explanation
Recommended Action Increase the MTU of the path to the remote RLOC


%CFC_LISP-3-UNEXPECTED_PATH : Unexpected path type [chars]/[int]
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.


%CFC_LISP-3-NO_PATH : Failed to resolve path type for [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.


%CFC_LISP-3-SRC_RLOC_IDX : [chars] source RLOC index database[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.


%CFC_LISP-3-GSMR : Failed to [chars] generalised SMR attribute for [chars]/[int]
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.


%CFC_LISP-3-DYN_EID_IP_ADDR_CONFLICT : Ignore dynamic EID detection due to IP Address conflict [chars]:[chars] on [chars]
Explanation A dynamic EID Host attempted to register with an IP address conflicting with the XTR gateway. Refer to error message log for more details.
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.


CFT

%CFT-3-IPC_OPEN_REPLY : IPC Open Reply failed, request [int]
Explanation For a request from upper CFT software stack layers it was not possible to open the reply buffer. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%CFT-3-IPC_NORES : No space for the IPC reply, size [int]
Explanation For a request from upper CFT software stack layers it was not possible to allocate space for a reply for the specified size. The consequence of this could be a stuck monitor that cannot be established etc. In rare cases this could also affect other operations such as feature activation.
Recommended Action This is normally a software issue. LOG_STD_RECUR_ACTION


%CFT-2-IPC_INIT : IPC message handler registration failure, rc [int]
Explanation Registering an IPC message handler for the CFT feature failed. This will cause the feature to not function.
Recommended Action This is normally a software issue. The consequences are that the CFT feature will not function. LOG_STD_ACTION


CFT_API

%CFT_API-3-CFT_ERRMSG_NO_MEMORY : [chars] [chars] [dec]
Explanation The system was unable to supply the requested memory for flow processing to continue.
Recommended Action Check the available memory on your system. Possible solutions include: disable some features; reduce other system activities to ease memory demands; upgrade to a larger memory configuration. LOG_STD_SH_TECH_ACTION


%CFT_API-3-CFT_ERRMSG_MAX_MEMORY : [chars] [chars] [dec]
Explanation The maximum number of concurrent flows allowed has been exceeded. Some flows might not received the provisioned level of service.
Recommended Action This is the platform limit. Either lower the network load on this device or upgrade to a higher capacity platform. LOG_STD_SH_TECH_ACTION


%CFT_API-4-CFT_ERRMSG_CLIENT_PRE_CREATE_PREVENTED : [chars] [chars] [dec]
Explanation Flow creation was prevented by a flow table client. This may be due to an explicit policy that is enabled.
Recommended Action Check your policies to ensure this what you intend. LOG_STD_SH_TECH_ACTION


%CFT_API-4-CFT_ERRMSG_FLOW_CREATION_PREVENTED : [chars] [chars] [dec]
Explanation Flow creation was denied by a the system. A possible denial of service attack may have been detected.
Recommended Action Modify your denial of service policy if this is in error. LOG_STD_SH_TECH_ACTION


%CFT_API-5-CFT_ERRMSG_UNSUPPORTED_L3_PROTOCOL : [chars] [chars] [dec]
Explanation An unsupported layer 3 protocol was identified.
Recommended Action Flow based inspection does not support this protocol at this time. LOG_STD_SH_TECH_ACTION


%CFT_API-5-CFT_ERRMSG_NON_FIRST_IP_FRAGMENT : [chars] [chars] [dec]
Explanation The flow table was unable to process a TCP fragmented packet. Service for these packets may be unavailable.
Recommended Action Enable the virtual fragment reassembly (VFR) functionality. If fragmentation is excessive, try to identify the source in your network topology that is causing packet fragmentation. LOG_STD_SH_TECH_ACTION


%CFT_API-7-CFT_ERRMSG_CLIENT_API : [chars] [chars] [dec]
Explanation A CFT client may have a incorrectly accessed an API.
Recommended Action This is an internal software error. Please report it to your technical support representative. LOG_STD_SH_TECH_ACTION


%CFT_API-3-CFT_ERRMSG_UNKNOWN : [chars] [chars] [dec]
Explanation The error message type does not match the possible enumerated definitions.
Recommended Action This is an internal software error. Please report it to your technical support representative. LOG_STD_SH_TECH_ACTION


CHASFS

%CHASFS-3-NOCHASFSDIR : The directory [chars] does not exist.
Explanation No explanation.
Recommended Action No action is required.


%CHASFS-3-NOINOTIFY : The inotify device could not be opened. Error [dec].
Explanation This error occurs when there is an error in the system that prevents the notification facility from being accessed.
Recommended Action No action is required.


%CHASFS-3-NORESOLVE_LOCAL_OBJECT : Error resolving local FRU object: [chars]
Explanation An application was not able to create a reference to an object in its local chassis file system.
Recommended Action If this message recurs, 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.


%CHASFS-3-NOOPEN_PROPERTY : Error opening chassis file system object [chars]: [chars]
Explanation An application was not able to open a an object in its local chassis file system.
Recommended Action If this message recurs, 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.


CHAT

%CHAT-3-CANTRUN : %t in use, can't run startup script
Explanation When the startup script attempted to run, it found another process had Already been started on the line
Recommended Action Remove startup script from line configuration if it's inappropriate. Report to cisco.


CISCO_STUN through CMCC

CISCO_STUN

%CISCO_STUN-3-QUEUE_ERROR : Unable to enqueue event [chars] ([dec]) to a process watched queue. Current size: [dec], max size: [dec]
Explanation An internal or external event was dropped because it could not be added to the queue, probably because the queue is full. The result may be minor (retransmission of a STUN message) or major (dropped call), depending on the event which was lost. This error may indicate that the call rate is exceeding the capacity of the gateway. If this is the case, the CPU utilization will be excessively high (above 75%).
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show process cpu command to gather data that may help identify the nature of the error. Also 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.


CLEAR

%CLEAR-5-COUNTERS : Clear counter on [chars] [chars] by [chars]
Explanation The counters have been cleared on the interface(s)
Recommended Action No action is required.


%CLEAR-5-EXT_COUNT : Clear extended [chars] counters on [chars] by [chars]
Explanation The extended counters have been cleared on the interface(s)
Recommended Action No action is required.


CLOCK_RECOVERY

%CLOCK_RECOVERY-4-CLOCK_FAILED : [chars] on module [dec]/[dec] failed
Explanation This message indicates that an active recovered or enhanced clock has failed
Recommended Action No action is required.


%CLOCK_RECOVERY-6-CLOCK_ACTIVE : [chars] on module [dec]/[dec] is now active
Explanation This message indicates that a recovered or enhanced clock has become active
Recommended Action No action is required.


CLS

%CLS-3-CLSFAIL : CLS: Assertion failed: [chars]
Explanation A software or hardware 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.


%CLS-3-CLSMSG : [chars]
Explanation A software error detected while manipulating CLSIMsg objects.
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.


%CLS-3-BOGUSOP : Unknown CLS verb for [chars] context, DlcOpcodeT=[hex]
Explanation A bad opcode was generated by the DLC for the STN or CEP.
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.


CLSDR

%CLSDR-3-NOINIT : CLSDRIVER not initialized
Explanation A CLSDRIVER initialization failed earlier. Trying to use the driver now results in an error condition.
Recommended Action Remove and then restore the destination logical unit (DLU) in the configuration file and try and reboot the system. LOG_STD_ACTION


%CLSDR-3-NOREMOVEPORT : RemovePort: port [hex] not on list
Explanation The destination logical unit (DLU) is trying to remove an nonexistent port from the list of active ports because it does not have the correct list of active ports.
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.


%CLSDR-3-NOREMOVECEP : RemoveCep : Cep [hex] not on list
Explanation The destination logical unit (DLU) is trying to remove a nonexistent connection end point from the internal data structure. This creates a problem in the connection end point (CEP) maintenance logic.
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.


%CLSDR-3-NODLUCREATE : Cannot create DLU for this type [dec]
Explanation The CLSDRIVER does not understand the destination logical unit (DLU) type. Currently, only STUN uses the CLSDRIVER. Any other value results in an 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.


%CLSDR-3-NOPORTCREATE : Cannot create PORT structure
Explanation The CLSDRIVER cannot enable this port for processing.
Recommended Action Try rebooting the router. LOG_STD_ACTION


%CLSDR-3-NOCLSSERVER : unable to start the Server process
Explanation Could not start the CLSDRIVER process, possibly due to a resource problem. The subsystem using CLSDRIVER does not work.
Recommended Action Remove and then restore the destination logical unit (DLU) in the configuration file and try and reboot the system. LOG_STD_ACTION


%CLSDR-3-INCORRECTPORT : Incorrect port pointer in USapId
Explanation Cisco Link Services I (CLSI) returned an incorrect port pointer in the USapID.
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.


%CLSDR-3-NOCEP : Cannot found cep in free pool
Explanation A software or hardware 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.


%CLSDR-3-WRONGMSG : Should never be here, cls message type unknown [hex]
Explanation The CLS message type is unknown to the destination logical unit (DLU).
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.


%CLSDR-3-MSGERR : [chars] couldn't get a message
Explanation The destination logical unit (DLU) could not send a correct message to Cisco Link Services I (CLSI) because the message was formed incorrectly. CLSI will not perform the desired action.
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.


%CLSDR-3-ERRRTN : [chars] failed error [hex]
Explanation An error was returned from Cisco Link Services I (CLSI) to the destination logical unit (DLU) because CLSI did not perform the action desired by the DLU.
Recommended Action Refer to CLSI software documentation for more information about this error. Report this error to your technical support representative.


CMANRP

%CMANRP-3-MSGDISPATCHNULL : Received NULL TDL message from IOS
Explanation An unexpected condition in which IOS has received a NULL TDL message from Chassis 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.


%CMANRP-3-MSGDISPATCH : Unable to dispatch received TDL message '[chars]' from Chassis Manager. LUID: [chars]
Explanation An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages from Chassis 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.


%CMANRP-3-MSGIPCERR : Unable to process received IPC messages from Chassis Manager, error: [chars]
Explanation An unexpected condition has occurred while IOS is trying to process a received IPC message from Chassis 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.


%CMANRP-3-INVERR : Unable to process chassis inventory for file [chars], slot [dec], [chars], error [dec]. Some SPA's may not be fully configured
Explanation An unexpected condition has occurred while IOS is trying to process the chassis inventory on startup. IOS can not determine the type and number of all Carrier Cards and SPA's present in the system. Some configuration relating to these SPA's may not be applied and leave the system in an inconsistent state.
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.


%CMANRP-3-INVERRSPA : Unable to process chassis inventory for file [chars], SPA subslot [dec]/[dec], [chars], error [dec]. Some SPA's may not be fully configured
Explanation An unexpected condition has occurred while IOS is trying to process the chassis inventory on startup. IOS can not determine the type and number of all Carrier Cards and SPA's present in the system. Some configuration relating to these SPA's may not be applied and leave the system in an inconsistent state.
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.


%CMANRP-2-CRASHDUMP : Fatal error, calling crashdump, error: [dec] [chars]
Explanation A fatal condition has occurred causing IOS to crashdump.
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.


%CMANRP-6-CMSTATUS : Chassis Manager Process is [chars]
Explanation The current status of Chassis Manager Process.
Recommended Action No action is required.


%CMANRP-6-CMHASTATUS : RP switchover, [chars]
Explanation RP switchover events received by chassis manager.
Recommended Action No action is required.


%CMANRP-6-CMSWREAD : RP switchover event triggered
Explanation RP switchover event triggered by IOS fastpath.
Recommended Action No action is required.


%CMANRP-3-CMREADFAIL : Read from cpld_ha fd [dec] failed, errno [dec], event cnt [dec]
Explanation Read from cpld_ha device returned 0 bytes.
Recommended Action No action is required.


%CMANRP-6-CMNOTSWITCH : RP is not doing switchover
Explanation Read from cpld_ha device indicate no switchover event.
Recommended Action No action is required.


%CMANRP-3-CMSWVERINFO : Unable to process software version information using file [chars]. Reason: [chars]. Error: [dec]
Explanation An unexpected condition has occurred while IOS was trying to process the software version information file. As a result, version information may not be available to an SNMP Manager
Recommended Action No action is required.


%CMANRP-3-UDEVPERMS : An invalid permissions value, [chars], was found in a udev file
Explanation The udev files for a particular filesystem contain a description the file system. If the permissions attribute is not recognized then this file system may run with incorrect permissions.
Recommended Action No action is required.


%CMANRP-4-SMU_UNCOMMITTED : There are uncommitted SMU, abort reload and 'install commit' if required
Explanation There are uncommitted SMU activity in the system, reload will remove this SMU activity, use 'install commit' to make it persistent.
Recommended Action No action is required.


%CMANRP-6-SMU_COMMITTED : 'install commit' is success.
Explanation There were uncommitted SMU activity in the system, reload will remove this SMU activity, with user input install commit is done.
Recommended Action No action is required.


%CMANRP-3-SMU_COMMITTED_FAILED : 'install commit' failed [dec] during reload.
Explanation There are uncommitted SMU activity in the system, reload will remove this SMU activity, with user input install commit is tried but failed with the error code mentioned in message.
Recommended Action No action is required.


CMAN_IDPROM_ENVMON

%CMAN_IDPROM_ENVMON-3-CMAN_IDPROM_FIELD_INVALID : The idprom contains an invalid environmental monitoring field.
Explanation If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either incomplete or absent entirely.
Recommended Action If this message recurs, 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.


CMAN_LED

%CMAN_LED-6-BEACON_LED_TURNED : Slot [dec] Beacon LED turned [chars]
Explanation Beacon LED turned ON/OFF. This is a notification message only.No action is required.
Recommended Action This is a notification message only. No action is required.


CMAPP

%CMAPP-6-INTERNAL_ERROR : MGCP fallback is in process, retry later
Explanation
Recommended Action


%CMAPP-6-PROCESS_CREATION_FAILED : Cannot create Call Manager Application process
Explanation Failed to create the Call Manager Application process.
Recommended Action Check the size of free memory to make sure there is enough memory.


%CMAPP-6-CONFIG_DONE : Configuration by CCM is done
Explanation The gateway's configuration has been changed by CCM
Recommended Action This is an informational message only. No action is required.


CMCC

%CMCC-3-DDR_SINGLE_BIT_ERROR : Single-bit DRAM ECC error: mme: [int], sbe: [int], address: [hex], pid: [int], name: [chars]
Explanation The SIP DRAM experienced a single-bit error checking code (ECC) error.
Recommended Action No action is required. This error is usually self-correcting. If the problem persists, you may need to replace the SIP.


%CMCC-0-CPLD_INITIALIZATION : The SIP CPLD has failed initialization :[chars]
Explanation A SIP complex programmable logic device (CPLD) failed to initialize. This error could be caused by a hardware or software driver defect.
Recommended Action Examine the logs for CPLD driver or hardware errors. Verify that the software and CPLD versions are compatible.


%CMCC-0-FPGA_INITIALIZATION : The CC has failed initialization because [chars]. Reloading the card
Explanation The FPGA on the carrier card has failed to initialize. This error could be caused by a hardware
Recommended Action Examine the driver logs or hardware errors. Decode the core accompanied with this error.


%CMCC-0-CPLD_IOCTL : A CPLD driver I/O control has failed because [chars]
Explanation A complex programmable logic device (CPLD) I/O driver control has failed. This error could be caused by a hardware or software driver defect.
Recommended Action Examine the logs for CPLD driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information


%CMCC-0-C2W_INITIALIZATION : The SIP C2W has failed initialization because [chars]
Explanation The C2W bus on the SIP is used to read the shared port adapter (SPA) IDPROM. This error indicates that the SIP C2W bus failed to initialize.
Recommended Action Examine the logs for C2W driver errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-3-C2W_READ : An C2W read has failed because [chars]
Explanation An attempt to read the C2W bus has failed. This error could be caused by a hardware or software defect.
Recommended Action Examine the logs for C2W driver errors.


%CMCC-3-C2W_WRITE : An I2C write has failed because [chars]
Explanation An attempt to write to the inter-integrated circuit (I2C) has failed. This error could be caused by a hardware or software defect.
Recommended Action Examine the logs for I2C driver errors.


%CMCC-0-SERDES_INITIALIZATION : The SIP Serial Bridge ASIC has failed initialization because [chars]
Explanation The SIP serial bridge ASIC failed to initialize. This error could be caused by a hardware defect, software driver defect, or improper internal configuration.
Recommended Action Examine the logs for serial bridge ASIC driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information


%CMCC-5-SERDES_BLOCK_EVENT : A SerDes link informational error [chars], block [hex] count [hex]
Explanation A serial bridge I/O event has occurred. This event is not serious but is logged for diagnostic purposes.
Recommended Action No user action is required.


%CMCC-0-HT_INITIALIZATION : The SIP HyperTransport has failed initialization because [chars]
Explanation A SIP HyperTransport (HT) CPU bus failed to initialize. This error could be caused by a hardware defect or HT driver defect.
Recommended Action Examine the logs for HT driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-HT_IOCTL : A SIP HyperTransport driver I/O control has failed because [chars]
Explanation A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or HT driver defect.
Recommended Action Examine the logs for HT driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-PLIM_INITIALIZATION : The PLIM has failed initialization because [chars]
Explanation The physical layer interface module (PLIM) failed to initialize. This error could be caused by a hardware defect or a PLIM driver defect.
Recommended Action Examine the logs for PLIM driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-HTDP_ENABLE : The HTDP initialization has failed because [chars]
Explanation The Hypertransort datapath failed to initialize. This error could be caused by a hardware defect or HTDP driver defect.
Recommended Action Examine the logs for HTDP driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-CPLD_INTR_ENABLE : The CPLD initialization has failed because [chars]
Explanation The CPLD interrupt enable failed to initialize. This error could be caused by a hardware defect or CPLD driver defect.
Recommended Action Examine the logs for CPLD driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-PLIM_IOCTL : A PLIM driver I/O control has failed because [chars]
Explanation A physical layer interface module (PLIM) driver I/O has failed. This error could be caused by a hardware defect or a PLIM driver defect.
Recommended Action Examine the logs for PLIM driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-PLIM_HALT : A PLIM driver has critical error [chars], [dec], param [hex] param [hex]
Explanation A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or an HT driver defect.
Recommended Action Restart the SIP. If the problem persists, you may need to replace the PLIM.


%CMCC-3-PLIM_STATUS : A PLIM driver informational error [chars], block [hex] count [hex]
Explanation A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or an HT driver defect.
Recommended Action Examine the logs for PLIM or hardware errors.


%CMCC-3-IDPROM_ACCESS : Failed access or process an IDPROM because [chars]
Explanation The system failed to access an IDPROM or an IDPROM process failed. This error could be caused by a hardware defect, software defect, or incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM or hardware errors.


%CMCC-3-IDPROM_SENSOR : One or more sensor fields from the idprom failed to parse properly because [chars].
Explanation One or more IDPROM sensors failed to parse. This error most likely occurred because of a checksum failure in the IDPROM.
Recommended Action Examine the logs for IDPROM or hardware errors.


%CMCC-0-CHASSIS_TYPE : The chassis type [chars] is invalid.
Explanation The system has detected an invalid chassis type. This error could be caused by a hardware defect, software defect, or incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-CHASFS_OBJECT_CREATE : Failed to create chassis filesystem object [chars] because [chars]
Explanation The system failed to create a chassis filesystem object. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-CHASFS_PROPERTY_CREATE : Failed to create chassis filesystem object [chars] property [chars] because [chars]
Explanation The system failed to create a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-CHASFS_PROPERTY_GET : Failed to read chassis filesystem object [chars] property [chars] because [chars]
Explanation The system failed to read a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-CHASFS_PROPERTY_SET : Failed to write chassis filesystem object [chars] property [chars] because [chars]
Explanation The system failed to write a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-CHASFS_OBJECT_WATCH : Failed to watch chassis filesystem object [chars] because [chars]
Explanation The system failed to watch a chassis filesystem object. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-CHASFS_OBJECT_NOT_PRESENT : Expected chassis filesystem object [chars] not present.
Explanation The system was unable to find an expected chassis filesystem object. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-CHASFS_PROPERTY_NOT_PRESENT : Expected chassis filesystem object [chars] property [chars] not present.
Explanation The system cannot locate a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-CHASFS_LOCATION_TRANSLATE : Failed to translate a location to a chasfs object name because [chars]
Explanation The system failed to translate a data sensor location to the chassis filesystem (CHASFS) module. This error could be caused by a software defect.
Recommended Action Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMCC-0-PEER_INVALID : A peer table entry has invalid state.
Explanation An invalid state occurred in a peer table entry. This error could be caused by a software defect or system resource limitation.
Recommended Action Restart the SIP.


%CMCC-0-UIPEER_CREATE : Failed to create user interface peer.
Explanation The system failed to create a user interface peer. This error could be caused by a software defect or system resource limitation.
Recommended Action Restart the SIP.


%CMCC-0-SERVICES_INITIALIZATION : Failed to initialize general application services because [chars]
Explanation The system failed to initialize certain application services. This error could be caused by a software defect or system resource limitation.
Recommended Action Restart the SIP.


%CMCC-0-IPC_INITIALIZATION : IPC initialization failed because [chars]
Explanation An inter-process communication (IPC) initialization failed. This error could be caused by a software defect or system resource limitation.
Recommended Action Restart the SIP.


%CMCC-0-IPC_CONNECT_MASTER : IPC connection to the active RP failed because [chars]
Explanation The inter-process communication (IPC) connection to the active route processor (RP) failed. This error could be caused by a software defect or system resources limitation.
Recommended Action Restart the SIP.


%CMCC-0-IPC_CONNECTION_INVALID : An IPC connection has invalid state.
Explanation An inter-process communication (IPC) connection has an invalid state. This error could be caused by a software defect or system resource limitation.
Recommended Action Restart the SIP.


%CMCC-3-NETWORK_CLOCK_LOS : The SIP network clock jitter attenuator has lost signal
Explanation A SIP network clock jitter attenuator has lost signal from the WAN PLL and certain SPAs may report LOS alarms.
Recommended Action Restart the SIP.


%CMCC-3-NETWORK_CLOCK_DH : The SIP network clock jitter attenuator has entered digital holdover
Explanation A SIP network clock jitter attenuator has entered digital holdover mode and certain SPAs may report LOS alarms.
Recommended Action Restart the SIP.


%CMCC-3-NETWORK_CLOCK_CAL_START : The SIP network clock jitter attenuator is calibrating
Explanation The SIP network clock jitter attenuator is calibrating after device initilization stage.
Recommended Action Restart the SIP if SPA LOS alarms are seen after this.


%CMCC-3-NETWORK_CLOCK_CAL_FAIL : The SIP network clock jitter attenuator calibration fails
Explanation The SIP network clock jitter attenuator calibration can not complete within certain time. This would incur some SPA LOS alarms or other error events for some SPA port types.
Recommended Action Restart the SIP


%CMCC-3-CC_HOTSWAP_CKT_FAIL : Hot Swap Circuit has failed for bay [int]
Explanation The Hot Swap Circuit for the SPA bay has been tripped. This error could be caused by bad SPA or CC hardware.
Recommended Action Examine the CMCC and PSM OIR logs. Verify whether the recovery reload could bring up the SPA


%CMCC-3-SPA_HOTSWAP_CKT_FAIL : SPA on bay [int] has tripped the Hot Swap Circuit during power-up.
Explanation The Hot Swap Circuit for te SPA bay has been tripped. This error could be caused by bad SPA hardware.
Recommended Action Examine the CMCC and PSM OIR logs. Verify whether the recovery reload could bring up the SPA


%CMCC-3-HB_TIMEOUT : Peroidic Heartbeat message from RP timed out.
Explanation RP sends peroidic heartbeat message to the SIP. The SIP did not receive this heartbeat message for last timeout period.
Recommended Action Examine the system logs for errors.


%CMCC-3-STANDBY_EOBC_LINK_ERROR : Standby EOBC link error detected.
Explanation Standby EOBC link error: either link state is down, or duplexity is not full, or speed is not 1Gbps.
Recommended Action Examine the system hardware. Re-seat and securely screw in all FRUs. If the problem persists, please contact TAC support.


%CMCC-5-SPA_MDR_INIT : SPA[int] initiated Minimal Disruptive Restart
Explanation Informational message that the Minimal Disriptive Restart of a particular SPA has begun.
Recommended Action Informational notification. No action is required.


%CMCC-5-SPA_MDR_DONE : SPA[int] completed Minimal Disruptive Restart
Explanation Informational message that the Minimal Disriptive Restart of a particular SPA has completed.
Recommended Action Informational notification. No action is required.


%CMCC-3-SPA_MDR_FAIL : The SPA in bay [int] failed Minimal Disruptive Restart because [chars]
Explanation The SPA in bay %u failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SPA by resetting the SPA hardware.
Recommended Action Examine the system logs for errors.


%CMCC-3-SPA_SOFT_STOP_FAIL : The SPA in bay [int] could not be soft stopped because [chars]
Explanation The SPA in bay %u could not be soft stopped. An attempt will be made to recover the SPA by resetting the SPA hardware.
Recommended Action Examine the system logs for errors.


%CMCC-3-SIP_MDR_FAIL : The SIP failed Minimal Disruptive Restart because [chars]
Explanation The SIP failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SIP by resetting the SIP hardware.
Recommended Action Examine the system logs for errors.


%CMCC-3-HT_DETACH : The SIP HyperTransport has failed detachment because [chars]
Explanation A SIP HyperTransport (HT) CPU bus failed to detach from software during SIP MDR. This error could be caused by a hardware defect or HT driver defect.
Recommended Action Examine the system logs for errors.


%CMCC-3-PLIM_DETACH : The PLIM has failed detachment from software because [chars]
Explanation The physical layer interface module (PLIM) failed to detach from software. This error could be caused by a hardware defect or a PLIM driver defect.
Recommended Action Examine the system logs for errors.


%CMCC-3-PLIM_RESTART : The PLIM has failed to restart because [chars]
Explanation The physical layer interface module (PLIM) failed to restart during SIP MDR. This error could be caused by a hardware defect or a PLIM driver defect.
Recommended Action Examine the system logs for errors.


%CMCC-0-EVENT_LIBRARY : An event facility initialization or maintenance function failed because [chars]
Explanation An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMCC-3-SSD_PIDA_OIR : Hot insertion/removal of SSD module in [dec]/[dec] not supported. Please reload the router with SSD module installed in bay 3
Explanation Hot swapping of SSD is not supported
Recommended Action Reload the router with SSD module installed in bay 3.


%CMCC-5-SERDES_RX_RESET_EVENT : Interlaken Rx Alignment Status [chars], Retry Count [dec]
Explanation Rx Sync Failed for Interlaken, Status Timer Expired. So, Resetting the Rx Interlaken Core
Recommended Action No user action is required.


%CMCC-0-PCI_RESCAN : The PCIE bus could not be rescanned because [chars]
Explanation The PCIE bus failed to rescan. This error could be caused by a hardware defect, software driver defect, or improper internal configuration.
Recommended Action Examine the logs for PCIE bus driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information


%CMCC-3-FPGA_FAIL : [chars] FPGA error detected: [chars]
Explanation A SIP field programmable logic device failure detected. This error could be caused by a hardware or software driver defect.
Recommended Action Examine the logs for FPGA driver or hardware errors. Verify that the software and firmware versions are compatible.


%CMCC-3-SCOOBY_ILAK_FAIL : Failed to bringup the Interlaken interface. Cause: [chars]
Explanation Interlaken Rx or Tx failed for this card. This error could be caused by a hardware or software driver defect.
Recommended Action Reload the Linecard. If the problem still persists, replace the Linecard.


%CMCC-2-BAD_ID_HW_SLOT_STR : Failed Identification Test in [chars]. The module [chars] on the [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program.
Explanation Hardware in the specified location could not be identified as a genuine Cisco product
Recommended Action Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information


%CMCC-2-BAD_ID_HW : Failed Identification Test in [chars]. The module [chars] on the slot [dec] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program.
Explanation Hardware in the specified location could not be identified as a genuine Cisco product
Recommended Action Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information


%CMCC-6-FRU_HWPRG_UPG_PSOC_START : Hardware programmable PSOCs on [chars] in slot [chars] are upgrading, \ please don't reload or power-cycle this card. \ It will take about 2 mins to finish.
Explanation The hw-programmable PSOC is upgrading
Recommended Action No action is required. This is informational message


%CMCC-6-FRU_HWPRG_UPG_PSOC_SUCCESS : Hardware programmable PSOCs on [chars] in slot [chars] were successfully programmed. The card will reload to make new firmware work.
Explanation The hw-programmable PSOC was upgraded succesfully
Recommended Action No action is required. This is informational message


%CMCC-6-FRU_HWPRG_UPG_PSOC_PREPARE : Hardware programmable PSOCs on [chars] in slot [chars] were set in the golden mode. The card will reload to finish the upgrading
Explanation The hw-programmable PSOCs were set in the golden mode for FPD
Recommended Action No action is required. This is informational message


%CMCC-6-FRU_HWPRG_UPG_ADM1266_CFG_SUCCESS : Hardware programmable ADM1266 Configurations on [chars] in slot [chars] were successfully programmed.
Explanation The hw-programmable ADM1266 configuration was upgraded succesfully
Recommended Action No action is required. This is informational message


%CMCC-6-FRU_HWPRG_UPG_LMK03328_CFG_RESET : Hardware programmable LMK03328 Configurations on [chars] in slot [chars] were successfully partially programmed, please reload it to continue programming.
Explanation The hw-programmable LMK03328 configuration was partially upgraded succesfully
Recommended Action No action is required. This is informational message


%CMCC-6-FRU_HWPRG_UPG_LMK03328_CFG_SUCCESS : Hardware programmable LMK03328 Configurations on [chars] in slot [chars] were successfully programmed.
Explanation The hw-programmable LMK03328 configuration was upgraded succesfully
Recommended Action No action is required. This is informational message


%CMCC-6-FRU_HWPRG_UPG_TPS40422_CFG_RESET : Hardware programmable TPS40422 Configurations on [chars] in slot [chars] were successfully partially programmed, please reload it to continue programming.
Explanation The hw-programmable TPS40422 configuration was partially upgraded succesfully
Recommended Action No action is required. This is informational message


%CMCC-6-FRU_HWPRG_UPG_TPS40422_CFG_SUCCESS : Hardware programmable TPS40422 Configurations on [chars] in slot [chars] were successfully programmed.
Explanation The hw-programmable TPS40422 configuration was upgraded succesfully
Recommended Action No action is required. This is informational message


%CMCC-2-FRU_HWPRG_UPG_FAILED : Failed to [chars] [chars] hardware programmable on [chars] in [chars].
Explanation Upgrade hw-programmable failed to upgrade the CPLD/FPGA firmware on the given FRU
Recommended Action Reload the card and retry to program the hw-programmable. If the card fails to come up please contact TAC


%CMCC-2-FRU_HWPRG_UPG_SUCCESS : Success to [chars] [chars] hardware programmable on [chars]. Please execute the POST Upgrade CLI: upgrade hw-programmable cable <r0/r1> daybreak post-upgrade slot <slot> to finish the upgrade process
Explanation Upgrade hw-programmable success to upgrade the CPLD/FPGA firmware on the given FRU
Recommended Action No action is required. This is informational message


%CMCC-5-CMCC_EZMAN_HB_MISS_EXCEED : CMCC Missed [int] Heartbeats from EZMAN, Reloading the Line Card
Explanation CMCC Monitors the Health of the EZMAN by keeping a track of the Heartbeat messages. In case the EZMAN gets stuck in a event under watchdog disable context (sw_wdog_disbale), then the CMCC will stop getting these updates. The CMCC after a certain period of time would reset the card, since EZMAN is unresponsive
Recommended Action Reload the card, a software initated to restart the EZMAN


%CMCC-3-CARD_MISMATCH : The CONFIG&PICTYPE in slot [dec] mismatch : CONFIG : [chars], PIC : [chars]
Explanation The CMD and PIC in the slot mismatch.
Recommended Action Shut down the LC and change the card mode or remove the pic card.


%CMCC-3-SPA_PSEUDO_HARD_OIR_VFT_NOT_IMPLEMENTED : The PSEUDO OIR VFT is not implemented for bay [dec]
Explanation The pseudo OIR vft not implemented for this platform
Recommended Action Do nothing


%CMCC-6-FLOW_CONTROL_OTHER : Flow control error seen, Cause [chars]
Explanation Flow control error is detected in the FPGA
Recommended Action Appropriate action is taken in software to correct this error. If the problem persists, the MIP100 hardware may need to be replaced.


%CMCC-3-FLOW_CONTROL_SBE : Single-bit ECC error seen, Cause [chars]
Explanation Self correctable single bit errors were detected in the FPGA
Recommended Action This error is usually self-correcting. If the problem persists, the MIP100 hardware may need to be replaced.


%CMCC-0-FLOW_CONTROL_MBE : Multi-bit ECC error seen, Cause [chars], MIP100 is going to be reloaded to recover
Explanation Non correctable multi bit errors were detected in the FPGA.
Recommended Action MIP100 is reloaded to correct the error. If the problem persists, the MIP100 hardware may need to be replaced.


%CMCC-6-MGMT_SFP_INSERT : transceiver module inserted in [chars]
Explanation The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the error message.
Recommended Action No action required.


%CMCC-6-MGMT_SFP_REMOVED : Transceiver module removed from [chars]
Explanation The online insertion and removal (OIR) facility detected the removal of a transceiver module from the interface specified in the error message.
Recommended Action No action required.


%CMCC-3-UNKNOWN_SPA_LC : Unknown SPA was inserted in slot [dec]
Explanation Unknown SPA was inserted in the given slot.
Recommended Action Remove the unsupported SPA line card and upgrade the software as needed.


%CMCC-6-FRU_IOFPGA_UPG_START : Field programmable device on [chars] in slot [dec] is being upgraded. \ It will take about 2 mins to finish the upgrade. Please do \ not reload or power-cycle this card while upgrade is in \ progress.
Explanation The field programmable device on the FRU is upgrading
Recommended Action No action is required. This is informational message


%CMCC-2-FRU_IOFPGA_UPG_FAILED : Failed to upgrade field programmable device on [chars] in slot [dec].
Explanation Upgrade of field programmable device failed
Recommended Action Reload the card and retry to program the field programmable \ device. If the card fails to come up please contact TAC


%CMCC-2-FRU_IOFPGA_UPG_SUCCESS : Successfully upgraded the field programmable device on [chars] in \ slot [dec]. Power-cycling the line card.
Explanation Upgrade field programmable device was successful on the \ given FRU. Line card needs to be power-cycled or removed \ and re-inserted for upgrade to take effect.
Recommended Action Line card needs to be power cycled or removed and re-inserted \ for the upgrade to take effect.


%CMCC-2-FRU_IOFPGA_UPG_LC_PWR_CYCLE_DONE : Power cycled the [chars] in slot [dec], after FPGA upgrade.
Explanation Power cycled the card after FPGA upgrade.
Recommended Action Line card has been power cycled after FPGA upgrade.


%CMCC-3-MESSAGE_RESPONSE : An invalid message response was received because [chars]
Explanation An invalid message response was received. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMCC-2-FRU_LC_PWR_RESET : ***** Detected power reset for the Line card in slot [dec].\ To recover from the error, Line card will brought up shortly
Explanation Detected Auto power reset(may be HW issue) for the Linecard.
Recommended Action Pseudo OIR of the Line card has been to recover/bring up the card.


%CMCC-6-FRU_LC_UPGRADE_REQD : Found mismatch between the Line card FPGA versions \ bundled in Software and programmed in Hardware in slot [dec]. \ FPGA version bundled in SW: [hex], present in HW: [hex]. To upgrade \ the FPGA to version bundled in SW, perform physical OIR of the \ line card or run the CLI: \ hw-module subslot <slot>/<SPA no.> oir power-cycle
Explanation New FPGA is bundled in SW. FPGA upgrade is needed.
Recommended Action To upgrade to latest FPGA, do physical OIR Line card or do Pseudo \ OIR of the line card using CLI: hw-module subslot <slot>/<SPA no.> \ oir power-cycle To view the present FPGA versions in chassis, use \


CMEM through COMPILED_ACL

CMEM

%CMEM-3-SENSOR_INIT_FAILED : Sensor ([chars]) initialization failed due to [chars].
Explanation This error indicates that environmental monitor software cannot initialize the sensor. The software will not register and monitor this sensor. This could occur when the IDPROM has a bad I2C address for this sensor.
Recommended Action If this message recurs, 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.


%CMEM-4-OBFL_INIT_FAILED : OBFL initialization failed.
Explanation This error indicates the OBFL dedicated filesystem is not mounted. OBFL diagnostic information will not be retained for customer troubleshooting.
Recommended Action If this message recurs, 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.


CMFP

%CMFP-3-DDR_SINGLE_BIT_ERROR : Single-bit DRAM ECC error: mme: [int], sbe: [int], address: [hex], pid: [int], name: [chars]
Explanation A single-bit data corruption error has occurred in the forwarding processor (FP).
Recommended Action These errors are self-correcting. If the problem persists, the FP hardware may need to be replaced.


%CMFP-3-IDPROM_ACCESS : Failed access or process an IDPROM because [chars]
Explanation Access to an IDPROM failed due to a hardware or software defect, or incorrect IDPROM content.
Recommended Action Examine the system logs for IDPROM and hardware errors. Copy the error message and related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered nformation.


%CMFP-3-IDPROM_SENSOR : One or more sensor fields from the idprom failed to parse properly because [chars].
Explanation Output from the IDPROM sensors failed to parse, commonly caused by a checksum failure in the IDPROM.
Recommended Action Examine the system logs for IDPROM and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information.


%CMFP-3-MASTERSHIP_UPDATE : An error ([chars]) has occurred while communicating the mastership role of this FP to the CPP. The FP is currently [chars]
Explanation An error occurred while communicating a change in the state (Active, Active with a Standby, or Standby) of the forwarding processor (FP). The error can cause an inconsistency of expected states between FPs and could affect the replication of state between the FPs.
Recommended Action Examine the system logs for errors. This error is usually temporary.


%CMFP-0-SPI4_MUX_HALT : SPI4 MUX driver has detected a critical error [chars]
Explanation A SPI4 MUX driver has failed or detected a critical hardware fault. This could be due to a hardware defect or driver defect.
Recommended Action The only corrective action is to restart the FP


%CMFP-3-SPI4_MUX_STATUS : SPI4 MUX driver has detected a informational error [chars] (occurred [dec] time(s))
Explanation A SPI4 MUX driver has failed or detected a information hardware fault. This could be due to a hardware defect or driver defect.
Recommended Action Examine the logs for SPI4 MUX and hardware errors.


%CMFP-3-CPLD_ECSR_ERROR :
Explanation An error has been detected on the ECSR bus. This may cause problems when accessing the fowarding processor
Recommended Action Some of these errors are catastrophic and others are not. If the FRU did not restart assume corrective action was taken. Please check the chassis-manager logs for errors.


%CMFP-3-CPLD_ERP_ERROR :
Explanation An error has been detected on the ERP bus. This may cause problems when accessing the fowarding processor
Recommended Action Some of these errors are catastrophic and others are not. If the FRU did not restart assume corrective action was taken. Please check the chassis-manager logs for errors.


%CMFP-3-N2_DDR_MBE : The encryption processor has detected an uncorrectable multi-bit error in memory at address [dec]
Explanation The encryption processor has detected an uncorrectable multi-bit in memory. This could be due to a hardware defect.
Recommended Action Examine the logs for encryption processor hardware errors.


%CMFP-6-N2_DRV_UPDATE : Hardware crypto device disabled. [chars]: [chars]
Explanation A crypto device driver has failed or detected a hardware fault. This could be due to a hardware defect or driver defect.
Recommended Action The only corrective action is to restart the ESP


%CMFP-3-N2_FATAL_ERROR :
Explanation An error has been detected on encryption processor.
Recommended Action Please check the chassis-manager logs for errors.


%CMFP-3-N2_INPUT_EXCEPT :
Explanation An exception has been detected on encryption processor.
Recommended Action Please lower crypto traffic rate. If the error still happens, encryption processor may stop processing. Need to reload ESP.


%CMFP-3-OCT_DRV_ERROR :
Explanation An error has been detected on encryption processor.
Recommended Action Please check the chassis-manager logs for errors.


%CMFP-3-HT_FATAL_ERROR : Failed to initialize the HyperTransport interface to the QFP
Explanation The HyperTransport interface to the QFP failed to initialize completely. Software will restart the ESP to recover
Recommended Action No action is required.


%CMFP-3-HB_TIMEOUT : Peroidic Heartbeat message from RP timed out.
Explanation RP sends peroidic heartbeat message to the ESP. The ESP did not receive this heartbeat message for last timeout period.
Recommended Action Examine the system logs for errors.


%CMFP-3-STANDBY_EOBC_LINK_ERROR : Standby EOBC link error detected.
Explanation Standby EOBC link error: either link state is down, or duplexity is not full, or speed is not 1Gbps.
Recommended Action Examine the system hardware. Re-seat and securely screw in all FRUs. If the problem persists, please contact TAC support.


%CMFP-0-CPLD_INITIALIZATION : CPLD initialization has failed because [chars]
Explanation The CPLD has failed to initialize. This could be due to a hardware or software driver defect.
Recommended Action Examine the hardware and CPLD driver logs and see if the logs provide information about a correctable problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMFP-0-CPLD_IOCTL : A CPLD driver I/O control has failed because [chars]
Explanation A complex programmable logic device (CPLD) I/O driver control has failed. This error could be caused by a hardware or software driver defect.
Recommended Action Examine the logs for CPLD driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at https://mycase.cloudapps.cisco.com/case, or contact your Cisco technical support representative and provide the representative with the gathered information


%CMFP-0-EVENT_LIBRARY : An event facility initialization or maintenance function failed because [chars]
Explanation An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMFP-2-BAD_ID_HW : Failed Identification Test in [chars]. The module [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program.
Explanation Hardware in the specified location could not be identified as a genuine Cisco product
Recommended Action Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information.


%CMFP-3-SIF_SERDES_SYNC_ERROR : Sif Serdes Sync Failed for Supervisor Failure Bitmap [hex]
Explanation One of more Supervisor ASIC Sif Serdes failed to sync, This could be due to a hardeware defect.
Recommended Action Note the time of the error message and examine the show hardware platform cman fp for detailed Sif Serdes Report.


%CMFP-4-UADP_EVENT : UADP EVENT (ASIC #[dec] [chars])
Explanation Unified Access Datapath ASIC Event
Recommended Action Copy the message exactly as it appears on the console or in the system log.


%CMFP-3-DPP_SERDES_SYNC_ERROR : UADP fabric interface synchronisation [chars]
Explanation One of more UADP fabric interface Serdes failed to sync, This could be due to a hardware defect.
Recommended Action No action is required.


%CMFP-3-SBUS_FATAL_ERROR : SBUS Controller not responding, bringing down [chars]
Explanation Spico SBUS controller fails to repsond, This could be due to a hardware defect. Reset the CHIP
Recommended Action No action is required.


%CMFP-6-CRYPTO_MODULE : Crypto Hardware Module is [chars]
Explanation The log is to indicate whether Crypto Hardware Module IPSECHW is physically inserted in the chassis.
Recommended Action No action is required.


CMLIB

%CMLIB-6-THROUGHPUT_VALUE : Throughput [chars] [chars], throughput set to [chars] kbps
Explanation Status indicating whether appropriate throughput is found or enabled and ensuring the value is used to configure the CPP hardware.
Recommended Action No user action is necessary. This is an informational message indicating that the throughput is configured.


%CMLIB-3-THROUGHPUT_VALUE_SETUP_FAILED : Throughput [chars] [chars], throughput set to [chars] kbps. Error: [chars]
Explanation Status indicating that a failure was observed during the setup of the throughput. The error reason may shed light on the cause. The set value is used to configure the CPP hardware.
Recommended Action Examine the ios, chassis-manager and license-manager logs for possible clues.


%CMLIB-3-THROUGHPUT_VALUE_APPLY_FAILED : Throughput [chars] [chars] - failed to persist throughput of [chars] kbps. Error: [chars]
Explanation Status indicating that a failure was observed during the writing of the throughput to persistent store. The error reason may shed light on the cause. The throughput value may have be used to configure the CPP hardware.
Recommended Action Examine the ios, chassis-manager and license-manager logs for possible clues.


%CMLIB-2-IDPROM_INVALID : Invalid IDPROM assembly number [hex]. IDPROM update required
Explanation IDPROM assembly number is not supported.
Recommended Action IDPROM update is required


%CMLIB-4-FW_CHECK : slot [chars]: [chars] current firmware version is [chars], while the minimum \ required version is [chars]. Please upgrade it to minimum required version or higher.
Explanation Firmware version in the specified location is lower than minimum required version
Recommended Action Upgrade firmware version to latest.


CMRP

%CMRP-0-CPLD_INITIALIZATION : The RP CPLD has failed initialization because [chars]
Explanation The RP CPLD has failed to initialize. This could be due to a hardware or software driver defect.
Recommended Action Examine the hardware and CPLD driver logs and see if the logs provide information about a correctable problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CPLD_IOCTL : A CPLD driver I/O control has failed because [chars]
Explanation A CPLD driver I/O control has failed. This could be due to a hardware or software driver defect.
Recommended Action Examine the hardware and CPLD driver logs and see if the logs provide information about a correctable problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-I2C_INITIALIZATION : The RP I2C has failed initialization because [chars]
Explanation The RP I2C has failed to initialize. These components provide low-level communications between the RP and the other cards in the system.
Recommended Action Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-I2C_READ : An I2C read has failed because [chars]
Explanation An I2C read has failed. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-I2C_WRITE : An I2C write has failed because [chars]
Explanation An I2C write has failed. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-BITS_INITIALIZATION : The RP BITS E1/T1 interface has failed initialization because [chars]
Explanation The RP BITS E1/T1 interface has failed to initialize. This could be due to a hardware defect, a software driver defect or improper configuration.
Recommended Action Note the time of the error message and examine the logs for BITS driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative


%CMRP-0-WANPLL_INITIALIZATION : The RP WAN PLL has failed initialization because [chars]
Explanation The RP WAN PLL has failed to initialize. This could be due to a hardware or software driver defect.
Recommended Action Note the time of the error message and examine the logs for WAN PLL or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-WANPLL_SETUP : Failed to setup the [chars] of the RP WAN PLL because [chars]
Explanation Failed to setup the RP WAN PLL appropriately. This could be due to a hardware defect of the device.
Recommended Action Note the time of the error message and examine the logs for WAN PLL related hardware errors. Check if the issue is transient or repeatable. If the problem is not recoverable collect the output of the error message and the chassis- manager and IOS logs. Provide the gathered information to a Cisco technical support representative.


%CMRP-0-DDR_INITIALIZATION : The RP DDR has failed initialization because [chars]
Explanation The RP DDR has failed to initialize. This could be due to a hardware or software driver defect.
Recommended Action Note the time of the error message and examine the logs for DDR or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-DDR_SINGLE_BIT_ERROR : Single-bit DRAM ECC error: mme: [int], sbe: [int], address: [hex], pid: [int], name: [chars]
Explanation The RP DRAM has single-bit ECC errors.
Recommended Action In most cases, the system self-corrects these single-bit ECC errors and no user action is necessary. If the problem persists, gather the console output with the error message along with the show tech-support command output and provide the gathered information to a Cisco technical support representative.


%CMRP-0-SERDES_INITIALIZATION : The RP Serial Bridge ASIC has failed initialization because [chars]
Explanation The RP Serial Bridge ASIC has failed to initialize. This could be due to a hardware defect, software driver defect or improper internal configuration.
Recommended Action Note the time of the error message and examine the logs for Serial Bridge ASIC and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-HWLIB_INITIALIZATION : The hardware library has failed to initialize because [chars]
Explanation This could be due to a hardware defect, software driver defect or improper internal configuration.
Recommended Action Note the time of the error message and examine the logs for CPLD hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-SERDES_IOCTL : A Serial Bridge driver I/O control has failed because [chars]
Explanation A Serial Bridge driver I/O control has failed. This could be due to a hardware or software driver defect.
Recommended Action Note the time of the error message and examine the logs for Serial Bridge driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-SERDES_INTERRUPT_DISPATCH : Serial Bridge interrupt dispatch error: [chars]
Explanation Failed to dispatch an error interrupt from the Serial Bridge. This could be due to a software defect or inconsistent internal state.
Recommended Action Note the time of the error message and examine the logs for Serial Bridge errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-SERDES_ESI_LOCK_FAIL : Serial Bridge ESI link [chars] between [chars] and [chars] failed to lock
Explanation A Serial Bridge ESI link did not lock. This could be due to a hardware defect or a software configuration error.
Recommended Action Note the time of the error message and examine the logs for Serial Bridge and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-SERDES_ESI_INIT_FAIL : Serial Bridge ESI link [chars] between [chars] and [chars] failed to config
Explanation A Serial Bridge ESI link did not configure. This could be due to a software error.
Recommended Action Note the time of the error message and examine the logs for Serial Bridge and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-PFU_INITIALIZATION : The RP has failed to initialize a Power Supply/Fan module controller because [chars]
Explanation The RP failed to initialize a Power Supply or Fan module controller. This could be due to a hardware defect or C2W access failure.
Recommended Action Note the time of the error message and examine the logs for C2W and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-FAN_INITIALIZATION : The RP has failed to initialize Fan [dec] module controller because [chars]
Explanation The RP failed to initialize the Fan. This could be due to a software defect.
Recommended Action Note the time of the error message and examine the logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-HT_INITIALIZATION : The RP HyperTransport has failed initialization because [chars]
Explanation The RP HyperTransport has failed initialization. This could be due to a hardware defect or HT driver defect.
Recommended Action Note the time of the error message and examine the logs for HT driver and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-HT_IOCTL : A RP HyperTransport driver I/O control has failed because [chars]
Explanation A RP HyperTransport driver I/O has failed. This could be due to a hardware defect or HT driver defect.
Recommended Action Note the time of the error message and examine the logs for HT driver and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-6-HT_STATUS : R[dec] hypertransport configured for F[dec] active
Explanation The RP HyperTransport driver was properly configured for a newly active FP.
Recommended Action No user action is necessary. This is as informational message indicating normal system operation.


%CMRP-6-HT_CLOSURE_MODE : The HTPI driver failed to set it's closure mode properly
Explanation This is not a critical error, but it will result in possible traffic interruption during certain software failure cases or ISSU operations.
Recommended Action Note the error message and contact a Cisco technical support representative.


%CMRP-0-EHSA_INITIALIZATION : EHSA initialization has failed because [chars]
Explanation EHSA has failed initialization. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-EHSA_STATE_GET : Failed to get EHSA state because [chars]
Explanation Failed to get EHSA state. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-EHSA_STATE_SET : Failed to set EHSA state because [chars]
Explanation Failed to set EHSA state. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-IDPROM_ACCESS : Failed to access or process IDPROM '[chars]': [chars]
Explanation Failed access or process an IDPROM. This could be due to a hardware defect, software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-IDPROM_SENSOR : One or more sensor fields from the idprom failed to parse properly because [chars].
Explanation One or more sensor fields from the IDPROM failed to parse properly. This problem is often the result of a checksum failure in the IDPROM.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CHASSIS_TYPE : The chassis type [chars] is invalid.
Explanation The chassis type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CHASSIS_ID : Error while updating chassis id, Error: [chars]
Explanation The chassis Id is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-PLATFORM_FAMILY_TYPE : The platform family type [chars] is invalid.
Explanation The platform family type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CHASSIS_STATUS : Failed to get chassis hardware status because [chars]
Explanation The system failed to get the chassis hardware status.
Recommended Action Note the time of the error message and examine the logs for CPLD driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-SENSOR_INITIALIZATION : Failed to initialize sensor monitoring because [chars].
Explanation Sensor monitoring failed to initialize.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-SENSOR_TYPE : The sensor type is [dec] is invalid.
Explanation A sensor type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CHASFS_OBJECT_CREATE : Failed to create chassis filesystem object [chars] because [chars]
Explanation The hardware failed to create a chassis filesystem object.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-CHASFS_OBJECT_DESTROY : Failed to destroy chassis filesystem object [chars] because [chars]
Explanation A chassis filesystem object that should have been destroyed was not destroyed.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CHASFS_PROPERTY_CREATE : Failed to create chassis filesystem object [chars] property [chars] because [chars]
Explanation A chassis filesystem property was not properly created.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-CHASFS_PROPERTY_DESTROY : Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars]
Explanation A chassis filesystem property that should have been destroyed was not destroyed.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CHASFS_PROPERTY_GET : Failed to read chassis filesystem object [chars] property [chars] because [chars]
Explanation A chassis filesystem property was not properly read by the system.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CHASFS_PROPERTY_SET : Failed to write chassis filesystem object [chars] property [chars] because [chars]
Explanation A chassis filesystem property failed to write.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CHASFS_OBJECT_WATCH : Failed to watch chassis filesystem object [chars] because [chars]
Explanation A chassis filesystem object was not watched because of the reason stated in the error message.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CHASFS_OBJECT_NOT_PRESENT : Expected chassis filesystem object [chars] not present.
Explanation A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CHASFS_PROPERTY_NOT_PRESENT : Expected chassis filesystem object [chars] property [chars] not present.
Explanation A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-CHASFS_LOCATION_TRANSLATE : Failed to translate a location to a chasfs object name because [chars]
Explanation The chassis manager failed to translate a location to a chasfs object name.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-INVALID_ARGUMENT : A system function was given an invalid argument.
Explanation A system function was given an invalid argument. This is due to a software defect.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-ROLE_ADDRESS_UPDATE : Failed to update role-based EOBC IP addresses because [chars].
Explanation The system failed to update a role-based EOBC IP address for the reason stated in the message line.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-4-ACTIVE_SLOTBAY_BIAS : The configured active slot/bay bias [dec] is invalid.
Explanation The configured active slot/bay bias is not 0 or 1. The default value of 0 is used.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-EVENT_LIBRARY : An event facility initialization or maintenance function failed because [chars]
Explanation An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-PEER_TABLE : A peer table initialization or maintenance function failed because [chars]
Explanation A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-PEER_INVALID : A peer table entry has invalid state.
Explanation A peer table entry has an invalid state. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-UIPEER_CREATE : Failed to create user interface peer.
Explanation The system failed to create a user interface peer.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-SLOTS_INITIALIZATION : Failed to initialize chassis slot information because [chars]
Explanation The system failed to initialize the chassis slot information.
Recommended Action Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-SLOT_INVALID : A card absolute slot number cannot be determined for this chassis type
Explanation An absolute slot number is invalid. This could be due to a software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-SIGNAL_INITIALIZATION : Failed to initialize signals because [chars]
Explanation The system failed to initialize signals.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-SERVICES_INITIALIZATION : Failed to initialize general application services because [chars]
Explanation The system failed to initialize application services.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-INTERNALS_INITIALIZATION : Failed to initialize internal state because [chars]
Explanation The system failed to initilize the internal state for the reason mentioned in the error message.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-FP_MASTERSHIP_SET : Failed to set FP mastership because [chars]
Explanation The router failed to establish ESP mastership.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-RP_MASTERSHIP_SET : Failed to set RP mastership [chars] because [chars]
Explanation The router failed to establish RP mastership.
Recommended Action Reload the router.


%CMRP-0-RESOLVE_FRU : Failed to determine [chars] card because [chars]
Explanation The router failed to determine a FRU state.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-IPC_INITIALIZATION : IPC initialization failed because [chars]
Explanation IPC initialization failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-IPC_CONNECT_MASTER : IPC connection to the active RP failed because [chars]
Explanation IPC connection to the active RP failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-IPC_CONNECT_REMOTE_IOS : IPC connection to a remote IOSd failed because [chars]
Explanation IPC connection to a remote IOSd failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-IPC_CONNECTION_INVALID : An IPC connection has invalid state.
Explanation An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-MQIPC_INITIALIZATION : MQIPC initialization failed because [chars]
Explanation MQIPC initialization failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-MQIPC_ADVANCE : Failed to advance MQIPC queue because [chars]
Explanation The MQIPC initialization failed.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-MESSAGE_REGISTER : Failed to register with active RP because [chars]
Explanation The active RP failed to register.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-MESSAGE_RESPONSE : An invalid message response was received because [chars]
Explanation An invalid message response was received. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-MESSAGE_RELAY : Failed to relay a message because [chars]
Explanation Failed to relay a message. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-PFU_MISSING : The platform does not detect a power supply in slot [dec]
Explanation There is no power supply in one of the power supply slots.
Recommended Action Insert a power supply into the empty slot. The router requires two power supplies because the fans in the power supply are needed to cool the router.


%CMRP-3-PFU_OIR : Failed to handle a [chars] oir event for PEM in slot [dec], [chars]
Explanation A power supply was inserted or removed into or from a router and the software did not properly handle the event.
Recommended Action Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue.


%CMRP-3-PFU_FAN : Failed to handle fan failure for [chars] in slot [dec], [chars]
Explanation One or more fans have failed and the system is unable to properly handle the fan failure.
Recommended Action Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue.


%CMRP-3-PFU_FAILURE : Failed to handle power supply failure for [chars] in slot [dec], [chars]
Explanation A power supply has failed and the system is unable to properly handle the failure.
Recommended Action Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue.


%CMRP-3-PEM_REMOVE_SHUT : The system will shut down in [dec] minutes
Explanation A power supply has been removed and the router will shutdown to protect itself from overheating in the amount of time stated in the error message.
Recommended Action Reinsert a power supply into the power supply slot as soon as possible. The second power supply is required because the fans in the power supply are essential in monitoring router temperature.


%CMRP-6-FP_HA_STATUS : F[dec] redundancy state is [chars]
Explanation The ESP has transitioned into a new High Availability state.
Recommended Action No user action is necessary. This is an informational message.


%CMRP-6-FP_HA_SB_NOTREADY : FP switchover: F[dec] [chars]
Explanation The standby ESP is not ready for a switchover.
Recommended Action No user action is necessary.


%CMRP-3-FRU_NOPARTNUM : Cannot get part number from IDPROM for [chars]: [chars].
Explanation The FRU IDPROM cannot be read or does not contain a valid part number field.
Recommended Action The FRU IDPROM should be repaired.


%CMRP-3-FRU_INVPARTNUM : [chars] has been held in reset because the part number [hex] is invalid.
Explanation The FRU IDPROM contains an invalid part number.
Recommended Action The FRU IDPROM should be repaired or the board replaced.


%CMRP-3-FRU_INCOMPATIBLE : [chars] has been held in reset: [chars] is incompatible with [chars]
Explanation The part number read from the FRU IDPROM is invalid for this chassis type.
Recommended Action Remove the FRU from the chassis.


%CMRP-3-INCOMPATIBLE_FRU : [chars] in slot [chars] is not compatible with [chars] and so it is disabled
Explanation The Product ID read from the FRU IDPROM is invalid for this hardware configuration.
Recommended Action Remove the FRU from the chassis. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations.


%CMRP-3-UNSUPPORTED_FRU : [chars] in slot [chars] is not supported with [chars] and so it is disabled
Explanation The Product ID read from the FRU IDPROM is not supported in this router. This is due to either Hardware or Software compatibility limitation indicated in the console log
Recommended Action Remove the FRU from the chassis. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations.


%CMRP-6-REDT_RP_UNSUPPORTED_IN_INTER_CHASSIS_MODE : [chars] redundant RP in slot [chars] is not supported in inter-chassis redundancy mode. Please remove it for inter-chassis redundancy to work properly on system reload.
Explanation Because the system is configured in box-to-box or inter-chassis redundancy mode, the intra chassis redundancy mode is not supported and redundant RP, if any, will be disabled.
Recommended Action No user action is necessary.


%CMRP-6-REDT_FP_UNSUPPORTED_IN_INTER_CHASSIS_MODE : [chars] redundant FP in slot [chars] is not supported in inter-chassis redundancy mode
Explanation Because the system is configured in box-to-box or inter-chassis redundancy mode, the intra chassis redundancy mode is not supported and redundant FP, if any, will be disabled.
Recommended Action No user action is necessary.


%CMRP-3-UNSUPPORTED_PEM : [chars] in slot [chars] is not supported with [chars] and it needs to be replaced immediately
Explanation The Product ID read from the PEM IDPROM is not supported in this hardware configuration. It will be allowed to continue but immediate replacement is required
Recommended Action Remove the PEM from the chassis and replace it with a supported PEM. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations.


%CMRP-2-FRU_CPLD_INCOMPATIBLE : [chars] in slot [chars] has been held in reset as its CPLD firmware version is incompatible with [chars]
Explanation This FRU requires a newer CPLD firmware to function properly in this chassis
Recommended Action Upgrade the CPLD firmware on this FRU using the <b> upgrade hw-programmable CPLD file <pkg_file> slot <fru_slot> </b> command. Please see http://www.cisco.com/en/US/docs/routers /asr1000/cpld/hw_fp_upgrade.html for more details.


%CMRP-2-RP_CPLD_INCOMPATIBLE : All other cards in the system have been held in reset as the Active RP [chars] in slot [chars] has CPLD firmware version that is incompatible with [chars]
Explanation Active RP requires a newer CPLD firmware to function properly in this chassis
Recommended Action Upgrade the CPLD firmware on this FRU using the <b> upgrade hw-programmable CPLD file <pkg_file> slot <fru_slot> </b> command. Please see http://www.cisco.com/en/US/docs/routers /asr1000/cpld/hw_fp_upgrade.html for more details.


%CMRP-2-RP_CPLD_INCOMPATIBLE_OTHER : [chars] in slot [chars] has been held in reset because [chars]
Explanation Active RP requires a newer CPLD firmware to function properly in this chassis.
Recommended Action Upgrade the CPLD firmware on this FRU using the <b> upgrade hw-programmable CPLD file <pkg_file> slot <fru_slot> </b> command. Please see http://www.cisco.com/en/US/docs/routers /asr1000/cpld/hw_fp_upgrade.html for more details.


%CMRP-2-FRU_HWPRG_UPG_FAILED : Failed to [chars] [chars] hardware programmable on [chars] in [chars].
Explanation Upgrade hw-programmable failed to upgrade the CPLD/FPGA firmware on the given FRU
Recommended Action Reload the card and retry to program the hw-programmable. If the card fails to come up please contact TAC


%CMRP-3-FRU_HWPRG_UPG_SUCCESS : Hardware programmable [chars] on [chars] in slot [chars] was successfully programmed. The card will now be power-cycled or reset.
Explanation The hw-programmable CPLD/FPGA was upgraded succesfully
Recommended Action No action is required. This is informational message


%CMRP-3-FRU_HWPRG_UPG_UNSUPP : Upgrade of hardware programmable [chars] on [chars] in slot [chars] is not supported. Card will now be powered down.
Explanation upgrade of hw-programmable CPLD/FPGA not supported.
Recommended Action No action is required. This is informational message


%CMRP-3-FRU_HWPRG_NO_FILE_ENTRY : Cannot find file or directory on [chars] in slot [chars].
Explanation Cannot find a file or a directory when upgrade CPLD or FPGA.
Recommended Action No action is required. This is an informational message


%CMRP-3-FRU_HWPRG_BAD_DEVICE : Invalid HW programming device for [chars] in slot [chars].
Explanation The device is not supported in hardware programming.
Recommended Action No action is required. This is an informational message


%CMRP-3-FRU_HWPRG_LOAD_KMODULE_FAIL : Cannot load a kernel module on [chars] in slot [chars].
Explanation Cannot load a Kernel module when upgrade CPLD or FPGA.
Recommended Action Reload the card and retry to program the hw-programmable. If you get the same error, please contact TAC


%CMRP-3-HWPRG_UPG_UNSUPP_SLOT : upgrade of hardware programmables on [chars] is not supported while in slot [chars]. Card will now be powered down.
Explanation upgrade of hw-programmable CPLD/FPGA not supported in the given slot. Move the card to a different slot and perform the upgrade
Recommended Action Move the card to a different slot and perform the upgrade


%CMRP-3-FRU_HWPRG_RESTART_ERROR : Error [chars] when Chassis Manager restarts [chars] in slot [chars].
Explanation Restart procedure has an error after upgrade.
Recommended Action Try hw-module command to reload the FRU.


%CMRP-3-FRU_HWPRG_UPG_PS_FAILED : Power-Supply Module MCU [chars] in slot [chars] program failed
Explanation The hw-programmable power-supply upgrade failed
Recommended Action Please check Power-Supply model and PKG file.


%CMRP-6-FRU_HWPRG_UPG_PS_SUCCESS : Power-Supply Module MCUs in slot [chars] were successfully programmed.
Explanation The hw-programmable power-supply was upgraded succesfully
Recommended Action No action is required. This is informational message


%CMRP-6-FRU_HWPRG_UPG_PSOC_START : Hardware programmable PSOCs on [chars] in slot [chars] are upgrading, \ please don't reload or power-cycle this card. \ It will take about 10 mins to finish.
Explanation The hw-programmable PSOC is upgrading
Recommended Action No action is required. This is informational message


%CMRP-6-FRU_HWPRG_UPG_PSOC_SUCCESS : Hardware programmable PSOCs on [chars] in slot [chars] were successfully programmed. Please power-cycle or OIR the card to make them work
Explanation The hw-programmable PSOC was upgraded succesfully
Recommended Action No action is required. This is informational message


%CMRP-6-FRU_HWPRG_UPG_PSOC_PREPARE : Hardware programmable PSOCs on [chars] in slot [chars] were set in the golden mode. Please power-cycle or OIR the card to finish the upgrading
Explanation The hw-programmable PSOCs were set in the golden mode for FPD
Recommended Action No action is required. This is informational message


%CMRP-6-FRU_HWPRG_UPG_PSOC_DONE : Hardware programmable PSOCs on [chars] in slot [chars] were upgraded successfully
Explanation The hw-programmable PSOC was upgraded succesfully
Recommended Action No action is required. This is informational message


%CMRP-6-FRU_HWPRG_UPG_ADM1266_FM_START : Hardware programmable ADM1266s on [chars] in slot [chars] are upgrading, \ please don't reload or power-cycle this card. \ It will take about 10 mins to finish.
Explanation The hw-programmable ADM1266 Firmware is upgrading
Recommended Action No action is required. This is informational message


%CMRP-6-FRU_HWPRG_UPG_ADM1266_FM_SUCCESS : Hardware programmable ADM1266s on [chars] in slot [chars] were successfully programmed. The card is reloading to make them work
Explanation The hw-programmable ADM1266 fimware was upgraded succesfully
Recommended Action No action is required. This is informational message


%CMRP-3-RP_MISMATCH : [chars] has been held in reset because the part number differs from that of the active RP
Explanation The part number read from the FRU IDPROM is not compatible with part number of the active RP therefore, it may not
Recommended Action Remove the FRU from the chassis.


%CMRP-3-FP_DOWNREV : [chars] has been held in reset because it is down-rev to the previous FP ([hex] -> [hex]) in the chassis. Reboot the router to bring it up.
Explanation The FP inserted is a lower version than the previous Active FP in the router. Downrev of FP is not supported.
Recommended Action Reboot the router.


%CMRP-3-FP_UNSUPP_UPREV : [chars] has been held in reset because of an upsupported upgrade of FP ([hex] -> [hex]) in the chassis. Reboot the router to bring it up.
Explanation The FP inserted is a higher version than the previous Active FP in the router but this upgrade of FP is not supported.
Recommended Action Reboot the router.


%CMRP-3-FP_LESSTHAN : [chars] has been held in reset because it is down-rev to the active and cannot act as a standby.
Explanation The part number read from the FP IDPROM is not compatible with part number of the active FP therefore, it may not
Recommended Action Remove the FP from the chassis.


%CMRP-3-PWR_FAULT : Shutting down [chars] because power fault on primary is [chars] and secondary is [chars]
Explanation The FRU has been shutdown as a result of a power issue.
Recommended Action Check to ensure the router is receiving power. Otherwise, note the time of the error message and examine the logs for power-related errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-PWR_FAULT_INITIALIZATION : Power fault monitor initialization has failed because [chars]
Explanation The power fault monitor has failed to initialize.
Recommended Action Note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-0-RESOURSE : Resource allocation failed in [chars] because [chars]
Explanation The system is unable to allocate the requested resource.
Recommended Action In most cases, this message is seen as a result of a temporary resource issue. Retry the request for the resource when the system is experiencing lower traffic volumes. If the message persists, reload the router using the reload command.


%CMRP-6-RP_SWITCH_SB_SYNC : RP switchover: [chars]
Explanation The RP switch synchronization timer expired.
Recommended Action No user action is necessary.


%CMRP-3-RP_SWITCH_SB_NOT_READY : RP switchover: [chars]
Explanation An RP switchover occurred when the standby RP was not ready. The standby RP reset.
Recommended Action No user action is necessary. Allow the standby RP to reset.


%CMRP-0-SYSPAGE_WRITE_ERROR : The syspage chassis-type write has failed because [chars]
Explanation The syapge chassis-type write failed. This could be due to a software defect.
Recommended Action Note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-HWMOD_FAIL : hw-module [chars] command for slot [chars] failed ([chars])
Explanation The last hw-module command that was entered failed to complete
Recommended Action Retry the command. If the retry of the command fails, reload the router. If reloading the router fails to resolve the problem, note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-RP_SB_RELOAD : Reload of Standby RP failed: [chars]
Explanation A request to reload the standby RP failed.
Recommended Action Manually reload the standby RP. If that fails, configure SSO or RPR and then attempt the reload. If the problem persists, note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, show redundancy state, and the output of show tech-support and provide the gathered information to a Cisco technical support representative


%CMRP-6-RP_SB_RELOAD_REQ : Reloading Standby RP: [chars]
Explanation A reload of Standby RP has been requested.
Recommended Action No action is necessary.


%CMRP-3-RP_RESET : RP is resetting : [chars]
Explanation This RP is resetting due to the reason specified.
Recommended Action No action is necessary.


%CMRP-6-FP_SB_RELOAD_REQ : Reloading Standby FP: [chars]
Explanation A reload of Standby FP has been requested.
Recommended Action No action is necessary.


%CMRP-6-DUAL_IOS_STARTING : Software redundant IOS configured starting standby
Explanation Chassis manager received notification that IOS software redundancy has been configured. The standby IOS will be started in the time specified.
Recommended Action No action is necessary.


%CMRP-6-DUAL_IOS_STOPPING : Bringing down standby IOS
Explanation Chassis manager received notification to stop the standby IOS instance. This may be for a redundancy mode change. Depending on the reason, the standby may be subsequently restarted.
Recommended Action No action is necessary.


%CMRP-6-DUAL_IOS_REBOOT_REQUIRED : Configuration must be saved and the chassis must be rebooted for IOS redundancy changes to take effect
Explanation Chassis manager received notification that IOS software redundancy has been configured. For these changes to take effect, the system must be restarted.
Recommended Action Reload the chassis.


%CMRP-6-SINGLE_IOS_REBOOT_RECOMMENDED : Configuration must be saved and the chassis should be rebooted for optimal single-IOS execution
Explanation Chassis manager received notification that IOS software redundancy has been unconfigured. For optimal runtime resource allocation, the system must be restarted.
Recommended Action Reload the chassis.


%CMRP-3-CHASSIS_MONITOR_FRU_BOOT_STATUS : Reloading [chars] because the FRU boot status is unknown
Explanation The time at which the FRU started booing is not available. This time is used to check the boot status of the FRU.
Recommended Action Remove the FRU from the chassis if the FRU is continously reloaded.


%CMRP-3-CHASSIS_MONITOR_FRU_BOOT_RETRIES_EXCEEDED : [chars] has been held in reset because it has failed to successfully boot in [dec] tries
Explanation The FRU has failed to successfully boot in the maximum allowable attempts and is held in reset.
Recommended Action Remove the FRU from the chassis if the FRU continously fails to boot.


%CMRP-3-CHASSIS_MONITOR_ONLINE_TIME_EXCEEDED : Reloading [chars] because it has failed to come online
Explanation A FRU has failed to come online within the maximum boot time.
Recommended Action Remove the FRU from the chassis if the FRU is continously reloaded.


%CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED : Reloading [chars] because it has failed to become ready for packet processing
Explanation The FRU failed to become ready within the maximum ready time. This message applies to FP FRUs. A switchover will be performed if another FP is available.
Recommended Action Remove the FRU from the chassis if the FRU is continously reloaded.


%CMRP-3-CHASSIS_MONITOR_ONLINE_TIME_IGNORED : [chars] exceeded online time but will not be reset because fault ignore is configured
Explanation The FRU failed to come online within the maximum online time. This message applies to all FRUs. A reload will not be performed because fault ignore is configured.
Recommended Action No action is necessary.


%CMRP-3-CHASSIS_MONITOR_READY_TIME_IGNORED : [chars] exceeded ready time but will not be reset because fault ignore is configured
Explanation The FRU failed to become ready within the maximum ready time. This message applies to FP FRUs. A switchover and/or reload will not be performed because fault ignore is configured.
Recommended Action No action is necessary.


%CMRP-3-CHASSIS_FRU_FAULT_IGNORED_ISSET : CMAN_IGNORE_FRU_FAULTS is set. Some FRU faults will be ignored and FRU may not restart due to a fault
Explanation Debug variable will prevent a FRU from being restarted due to some faults.
Recommended Action No action is necessary.


%CMRP-3-CHASSIS_FRU_FAULT_IGNORED : CMAN_IGNORE_FRU_FAULTS is set. [chars]: [chars]
Explanation Debug variable will prevent a FRU from being restarted due to some faults.
Recommended Action No action is necessary.


%CMRP-6-TEST_SPA_OIR_ONLINE_OPS : SPA [dec]/[dec] oir online status is set to [chars]
Explanation test command executed to either allow/deny the spa coming online.
Recommended Action oir online action If the card does not come online, execute the test command to allow the spa to come online.


%CMRP-6-TEST_SPA_OIR_ONLINE_INSERT_DENIED : SPA [dec]/[dec] oir insert is denied
Explanation test command executed disallowing the spa to be inserted.
Recommended Action Execute the test command allowing the insertion of the spa for normal operation


%CMRP-2-CRYPTOGRAPHIC_HW_MISMATCH : ESP[dec] does not support strong cryptography. Chassis will reload.
Explanation IOS software featuring strong cryptography is invalid for use with any non-strong-cryptography Embedded Service Processor. The router node will reload if this combination is encountered.
Recommended Action Install a non-strong-cryptography image of the RP IOS package or replace the indicated Embedded Service Processor with one that supports strong-cryptography


%CMRP-3-INVENTORY_INITIALIZATION : [chars] inventory file could not be read. FRU may need a reload to initialize properly, [chars]
Explanation The FRU inventory file could not be read. The file can possibly be corrupt. The FRU will possibly not initialize properly. The FRU should reset automatically. If it does not, it should be reloaded manually. If the error persists, the FRU will need to be replaced.
Recommended Action Wait a few minutes. If FRU does not reset automatically, it should be manually reloaded. If error persists, the FRU needs to be replaced.


%CMRP-5-PRERELEASE_HARDWARE : [chars] is pre-release hardware
Explanation The board does have an official production part number.
Recommended Action Immediately contact Cisco for a replacement board.


%CMRP-6-RFROLE : RP switchover, [chars]
Explanation On RP switchover chasfs rfrole property has been changed.
Recommended Action No user action is necessary.


%CMRP-3-DUAL_IOS_STANDBY_BAY : Standby bay cannot be launched due to failure in bringing down existing processes (Attempts: [dec])
Explanation During standby bay shutdown, some related processes still remain running for an unexpectedly prolonged period of time. Chassis-manager has timed-out waiting for all related processes to shutdown. As a result, it is unable to notify Process-manager to restart the bay
Recommended Action Examine the logs for standby bay's Forwarding-manager (fman), Interface-manager (iman), Pluggable-Service-Daemon (psd) and IOS. Ascertain which of these processes is taking too long to shutdown and note the reason. Take corrective action based on the error noted in the log


%CMRP-3-INCOMPATIBLE_STANDBY_SUPERVISOR :
Explanation Supervisor found in Standby slot may not be fully compatible with the active supervisor and may cause issues.
Recommended Action Use supervisors with the same specifications to enable High Availablitly features.


%CMRP-6-THROUGHPUT_LICENSE : Throughput license [chars], throughput set to [chars]
Explanation Status indicating whether throughput license is found and the corresponding througput the CPP hardware is configured to provide.
Recommended Action No user action is necessary. This is an informational message indicating throughput configured.


%CMRP-3-THROUGHPUT_LICENSE_APPLY_FAILED : Throughput license look-up failed due to '[chars]'
Explanation This message is to notify the user that a license look-up did not succeed because license manager process could not be contacted. This is a rare case but is due to either a crashed license daemon(licensed) or it encountered an internal error.
Recommended Action No user action is necessary. However, it is possible that a re-boot of the box may correct this behavior.


%CMRP-3-UDI_AUTH : Quack Unique Device Identifier authentication failed
Explanation This chassis seems to be compromised or tampered with. UDI burned on to the Quack chip and the one read from chassis EEPROM do not match. It can also be a case of either EEPROM or Quack device failure. More details about which specific field failed to match are logged in license daemon log file (licensed_R0.log).
Recommended Action User immediately needs to contact Cisco support. This device appears to be tampered with or is a counterfeit device or had a system failure.


%CMRP-3-SIP_MDR_FAIL : The SIP[dec] failed Minimal Disruptive Restart because [chars]
Explanation The SIP failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SIP by resetting the SIP hardware.
Recommended Action Examine the system logs for errors.


%CMRP-3-INTERNAL_HW_ERROR : An nternal error condition was detected and resolved.
Explanation An internal error condition was detected, and affected part of hardware was reset. If this error condition reoccurs, the hardware may need to be replaced.
Recommended Action If this message recurs, 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.


%CMRP-0-INTERNAL_HW_SHUTDOWN : Internal unrecoverable error condition was detected. System is being reset.
Explanation Internal unrecoverable error condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced.
Recommended Action If this message recurs, 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.


%CMRP-4-SYSTEM_OVER_CURRENT : Overall system over-current has been detected. System will be reset.
Explanation Internal error (system over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced.
Recommended Action If this message recurs, 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.


%CMRP-4-NGWICS_OVER_CURRENT : A NIM over-current condition has been detected. System will be reset.
Explanation Internal error (NIM over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced.
Recommended Action If this message recurs, 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.


%CMRP-4-FAN_TRAY_OVER_CURRENT : A Fan Tray over-current has been detected. System will be reset.
Explanation Internal error (Fan Tray over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced.
Recommended Action If this message recurs, 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.


%CMRP-4-MOTHERBOARD_OVER_CURRENT : Motherboard over-current has been detected. System will be reset.
Explanation Internal error (Motherboard over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced.
Recommended Action If this message recurs, 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.


%CMRP-2-FRU_FPGA_INCOMPATIBLE : [chars] in slot [chars] has been held in reset as its FPGA firmware version is incompatible with [chars]
Explanation This FRU requires a newer FPGA firmware to function properly in this chassis
Recommended Action Upgrade the FPGA firmware on this FRU using the <b> upgrade hw-programmable FPGA file <pkg_file> slot <fru_slot> </b> command.


%CMRP-6-FRU_FPGA_UPG_REQUIRED : [chars] in slot [chars] has INCOMPATIBLE FPGA firmware version with [chars]. Upgrade the FPGA firmware
Explanation This FRU requires a newer FPGA firmware to function properly in this chassis
Recommended Action Upgrade the FPGA firmware on this FRU using the <b> upgrade hw-programmable FPGA file <pkg_file> slot <fru_slot> </b> command.


%CMRP-3-FAN_REMOVE_IM_SHUT : The Interface Modules (IM's) may shutdown in [dec] minutes [dec] seconds.
Explanation Fan tray has been removed and the router will shutdown to protect itself from overheating in the amount of time stated in the error message.
Recommended Action Reinsert a fan tray into the fan tray slot as soon as possible.


%CMRP-3-FAN_REMOVE_SHUT : The system will shut down in [dec] minutes [dec] seconds
Explanation Fan tray has been removed and the router will shutdown to protect itself from overheating in the amount of time stated in the error message.
Recommended Action Reinsert a fan tray into the fan tray slot as soon as possible.


%CMRP-3-FAN_REMOVE_RSP3_SHUT : System received fan tray removal notification, Reinsert or service the faulty fan tray to avoid system shutdown due to high temperature. System will shutdown in [dec] minutes [dec] seconds based on current ambient temperature.
Explanation Fan tray has been removed and the router will shutdown when the ARAD temp reaches Critical temperature i.e 105C to protect itself from overheating.
Recommended Action Reinsert a fan tray into the fan tray slot as soon as possible.


%CMRP-3-FAN_REMOVE_RSP2_SHUT : The system will shut down when CYLON temp reaches 105C
Explanation Fan tray has been removed and the router will shutdown when cylon temperature reaches critical temperature i.e. 105C to protect itself from overheating in the amount of time stated in the error message.
Recommended Action Reinsert a fan tray into the fan tray slot as soon as possible.


%CMRP-3-FAN_REMOVE_SYS_SHUTDOWN_PENDING : System shutdown will occur in [dec] minutes.
Explanation The FRU is overheating and will be shut down in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP-3-EXT_ALARM_INTERRUPT : Alarm [chars]:external alarm contact [dec]
Explanation There is an external alarm on the line.
Recommended Action If alarm is asserted, then clear at the source.


%CMRP-3-FAN_FAILURE_SYS_SHUTDOWN : WARNING: More than one Fan Failure detected and shutdown SYS state. System shutdown now TRUE:[hex].
Explanation More than one fan failures are identified this causing overheating the system and will be shut down in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP-3-POWERBUDGET : not enough power budget left for : [chars]:[dec]
Explanation The system do not have enough power budget for the new card.
Recommended Action the message will be displayed when not enough power budget left for the new card inserted.


%CMRP-2-BAD_ID_HW : Failed Identification Test in [chars]. The module [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program.
Explanation Hardware in the specified location could not be identified as a genuine Cisco product
Recommended Action Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information.


%CMRP-2-ACT2_UDI_DATA_INVALID : The act2 udi secure area format mismatch with unsecure area
Explanation This Router may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information.
Recommended Action Replace the current product with a Cisco authorised product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information.


%CMRP-5-PEM_OUTPUT_DETECT : Output of PEM [dec] is [dec] V
Explanation Value of Output of PEM.
Recommended Action If PEM Output is 0, check Power Cable.


%CMRP-0-CLOCK_MASTERSHIP_SET : Failed to set CLOCK mastership because [chars]
Explanation The router failed to establish CLOCK mastership.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-OOD_OPR : An OOD operation has failed because [chars]
Explanation An OOD opearion has failed. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for OOD errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-6-STBY_HARDDISK_UNAVAIL : stby-harddisk is offline
Explanation The stby-harddisk is not available.
Recommended Action No user action is necessary. This is an informational message.


%CMRP-3-LICENSE_TIMEOUT : Throughput license request timed out. Throughput level set to default
Explanation Throughput license was never received from lman
Recommended Action Examine logs for error messages


%CMRP-5-UNSUPPORTED_MODULE : Unsupported Module inserted. The module [chars] on the slot [dec] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program.
Explanation Hardware in the specified location could not be identified as a genuine Cisco product
Recommended Action If this message recurs, 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.


%CMRP-3-SERDES_NSTEP_SYNC_ERROR : Link down in Slot=[int], Link-Type=[int], Link-Status=[hex], Link=[int]
Explanation One or more Backplane Link didn't come up. This could be due to a hardware defect.
Recommended Action Note the time of the error message and examine the logs for repeated SYNC errors after repeated retries. If the logs, provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-SOFT_ERROR_RELOAD : Uncorrected Soft error on [chars], reloading RP to recover
Explanation Uncorrected Soft error on critical module, reloading the RP to recover
Recommended Action If this reoccures frequently, contact asr903-system


%CMRP-3-SOFT_ERROR_RELOAD_RECOMMENDED : Uncorrected Soft error on [chars], reload is recommended to recover.
Explanation Uncorrected Soft error on critical module, reload is recommended to recover
Recommended Action If this reoccures frequently, contact asr903-system


%CMRP-3-SOFT_ERROR_WAIT : Uncorrected Soft error on [chars], waiting for standby to switchover
Explanation Uncorrected Soft error on critical module, waiting for standby to reach SSO to switchover
Recommended Action If this reoccures frequently, contact asr903-system


%CMRP-3-SOFT_ERROR_UPDATE : Critical soft error on [chars]
Explanation Update for each soft error on different components
Recommended Action If this reoccures frequently, contact asr903-system


%CMRP-6-FRU_HWPRG_CPLD_POSTUPG_SUCCESS : Hardware CPLD postupgrade on CLC[dec] was successfully programmed.The LC is reloading to make it take effect.
Explanation The hw-programmable CPLD postupgrade was upgraded succesfully
Recommended Action No action is required. This is informational message


%CMRP-3-PSU_INCOMPATIBLE : The combination of Power Supply in P0: [chars] and P1: [chars] is not supported in power [chars] mode
Explanation An incompatible power supplies combination has been identified in P0 and P1 power supply slots. This could cause unpredictable behavior in power management in the router.
Recommended Action This error indicates that the combination of the two power supplies in P0 and P1 is an unsupported combination. In order to fix this issue, please review the installation guide, plug out one of the power supplies based on the requirement. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-3-FAN_INCOMPATIBLE : The combination of Power Supply and Fan Tray is incompatible
Explanation The combination of Fan tray and one of the power supply slots is not supported. This could cause unpredictable system behavior.
Recommended Action This error indicates that the combination of one of the power supplies in P0 or P1 is not supported with the Fan Tray. In order to fix this issue, please review the installation guide, replace the fan tray or the power supply based on the requirement. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.


%CMRP-6-FRU_HWPRG_UPG_START : Hardware programmable [chars] on [chars] in slot [chars] is upgrading. please don't reload or power-cycle this card. It will take about 5 mins to finish.
Explanation The hw-programmable was upgrading
Recommended Action No action is required. This is informational message


CMRP_ENVMON

%CMRP_ENVMON-3-TEMP_FRU_SHUTDOWN_PENDING : WARNING: [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown will occur in [dec] minutes.
Explanation The FRU is overheating and will be shut down in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP_ENVMON-3-TEMP_SYS_SHUTDOWN_PENDING : WARNING: [chars] temperature sensor on [chars] is in a shutdown SYS state. System shutdown will occur in [dec] minutes.
Explanation The FRU is overheating and will be shut down in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP_ENVMON-3-TEMP_FRU_SHUTDOWN_NOW : WARNING: [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown now.
Explanation The FRU is overheating and will be shut down in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP_ENVMON-3-TEMP_PSU_SHUTDOWN_NOW : WARNING: [chars] temperature sensor on [chars] is in a shutdown PSU state. PSU shutdown now.
Explanation The PSU is overheating and will be shut down in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP_ENVMON-3-TEMP_SYS_SHUTDOWN_NOW : WARNING: [chars] temperature sensor on [chars] is in a shutdown SYS state. System shutdown now.
Explanation The FRU is overheating and will be shut down in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP_ENVMON-3-TEMP_WARN_CRITICAL : WARNING: [chars] temperature sensor on [chars] is in a critical state reading [dec]
Explanation The FRU is overheating and will be shut down in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP_ENVMON-3-TRANSCEIVER_TEMP_SYS_SHUTDOWN_NOW : WARNING: transceiver temperature sensor is in a shutdown SYS state. System shutdown now [hex].
Explanation The Transceiver is overheating and will be shut down in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP_ENVMON-3-TEMP_FRU_HW_AUTO_SHUTDOWN : WARNING: The card on slot [dec] is overheating. it has been auto-shutdown by hardware for protection
Explanation The FRU is overheating and has been auto-shutdown in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP_ENVMON-3-PWR_FRU_HW_AUTO_SHUTDOWN : WARNING: The card on slot [dec] hit abnormal voltage or current. it has been auto-shutdown by hardware for protection
Explanation The FRU hit abnormal voltage or current and has been auto-shutdown in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP_ENVMON-6-TEMP_SYS_SHUTDOWN_DISABLED : WARNING: System is in a thermal shutdown disabled state. System won't shut down now.
Explanation Thermal shutdown disable is configured to bypass system shutdown.
Recommended Action If this message recurs, 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.


CMRP_PFU

%CMRP_PFU-6-PFU_INSERTED : [chars] inserted. System shutdown aborted.
Explanation When either a PEM or a FM are removed, the system lacks sufficient cooling capacity. To prevent damage, the system will automatically shut down unless it is replaced.This message serves as notice that the module has been replaced within the required time
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PFU_SHUTDOWN : Shutting down system now because the PEM in slot [dec] was removed or not seated correctly.
Explanation When either a PEM or a FM are removed, the system lacks sufficient cooling capacity. To prevent damage, the system will automatically shut down unless it is replaced.
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PFU_SLOT_VACANT : The platform does not detect a power supply in slot [dec]
Explanation There is no power supply in one of the power supply slots.
Recommended Action Insert a power supply into the empty slot.


%CMRP_PFU-3-PFU_FANS_DEAD_SHUTDOWN : Shutting down system now because the fans in slot [dec] have all failed.
Explanation When the fans fail then system does not have sufficient cooling capacity. To prevent damage, the system will automatically shut down.
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-TEMP_FRU_SHUTDOWN : [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown will occur in [dec] minutes.
Explanation The FRU is overheating and will be shut down in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-TEMP_SYSTEM_SHUTDOWN : [chars] temperature sensor is in a shutdown system state. System shutdown will occur in [dec] minutes.
Explanation The system is overheating and will be shut down in order to protect the components.
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PFU_FANS_DEAD : The fans in the [chars] in slot [dec] have all failed.
Explanation The system is in danger of overheating because none of the fans in one of the PEMs are working properly.
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PFU_FAN_DEAD : WARNING: Fan [dec] in the [chars] in slot [dec] has failed.
Explanation A fan is not functioning properly.
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PFU_IDPROM_READ_ERR : Could not read the PEM/FM idprom in slot P[dec]. The system will run without environmental monitoring for this component
Explanation The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place.
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PFU_IDPROM_CORRUPT : The PEM/FM idprom could be read, but is corrupt in slot P[dec] The system will run without environmental monitoring for this component
Explanation The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place.
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-SHUTDOWN_FAILURE : The system attempted to shut itself down, but failed because [chars]
Explanation The system reached a condition where it should be shut down, but the shutdown call failed. The system should be manually rebooted.
Recommended Action If this message recurs, 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.


%CMRP_PFU-6-PEM_INSERTED : PEM in slot [dec] not operational.
Explanation A PEM seems to be inserted without the power cable connected. This message is a notice that the power supply is not operational, will not provide power to the system, and may not be completely detected by the software until the power cable is connected and the PEM is supplied with the power.
Recommended Action Insert the power supply cable in the PEM and provide power.


%CMRP_PFU-3-FANASSY_REMOVED : Fan Assembly is removed. Please insert to avoid system from heating.
Explanation Fan Assembly has been removed from the system. It needs to be inserted back to prevent system from heating. If the system over heats, parts of the system will not function normally and system may shut itself down.
Recommended Action Insert the fan assembly in the system to prevent system from over heating.


%CMRP_PFU-6-FANASSY_INSERTED : Fan Assembly is inserted.
Explanation Fan Assembly that was previously removed has been inserted in the system. Preventing the system from over heating is important. So fan assembly should not be removed for extended period of time during normal operation.
Recommended Action No further action is necessary.


%CMRP_PFU-3-PFU_FAN_ERR : WARNING: Fan [dec] in slot [dec] has the error: [chars], Please replace it with a new fan.
Explanation A fan is not functioning properly.
Recommended Action If this message recurs, 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.


%CMRP_PFU-4-PFU_FAN_WARN : WARNING: Fan [dec] in slot [dec] has the error: [chars].
Explanation A fan is not functioning properly.
Recommended Action If this message recurs, 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.


%CMRP_PFU-6-PFU_FAN_RECOVERED : Fan in slot [dec] has been recovered from error conditions, Now it's working normally.
Explanation Fans are just recovered from an error condition,
Recommended Action If this message recurs, 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.


%CMRP_PFU-6-PFU_FAN_RECOVERED_I2C : Successfully restored I2C communication to PSoC [dec] on fan module in slot [dec].
Explanation Fans are just recovered from an I2C communcation.
Recommended Action If this message recurs, 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.


%CMRP_PFU-4-PFU_FAN_INSUFFICIENT : WARNING: Insufficient number of fan modules installed. There are only [dec] fan modules, expecting [dec]
Explanation Insufficient number of fan modules installed, should insert new fans as soon as possible to avoid system from over heating.
Recommended Action If this message recurs, 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.


%CMRP_PFU-6-PWR_MGMT_OK : Sufficient number of power supplies ([dec]) are installed for power redundancy mode [chars] (excess power [dec] watts).
Explanation Sufficient number of power supplies are installed.
Recommended Action If this message recurs, 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.


%CMRP_PFU-4-PWR_MGMT_WARN : WARNING: Insufficient number of power supplies ([dec]) are installed for power redundancy mode [chars]. The system needs [dec] watts additional power.
Explanation Insufficient number of power supplies are installed. Should insert new power supplies as soon as possible
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PWR_MGMT_ALARM : WARNING: System does not have sufficient input power for minimum reliable operation requiring [dec] watts. The system needs [dec] watts of additional power.
Explanation System power does not meet minimum requirements. Insert additional power supplies or provide current power supplies with a greater input voltage source if applicable.
Recommended Action If this message recurs, 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.


%CMRP_PFU-4-PWR_MGMT_CAPACITY_MIXED : System contains power supplies of mixed power capacity. Redundancy operating mode Full protected is not supported with this configuration. System will run in Normal protected state.
Explanation HW does not support Full protected mode with mixed capacity power supplies. This is due to current sharing specifically
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PWR_REDUN_ALARM_STATE : WARNING: An active power supply has failed and the system has entered alarm state. The system is operating without power redundancy and has [dec] watts of power remaining
Explanation An active power supplied failed while in redundant power mode.
Recommended Action If this message recurs, 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.


%CMRP_PFU-6-PWR_REDUN_RECOVERED : System has recovered from the alarm state and has [dec] watts of power remaining
Explanation User has recovered the system from the alarm state triggered by a power failure
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PWR_MGMT_LC_SHUTDOWN : WARNING: Linecard in slot [dec] with priority [dec] and a power requirement of [dec] watts has shutdown.
Explanation A LC was shutdown due to a power loss.
Recommended Action If this message recurs, 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.


%CMRP_PFU-6-PWR_MGMT_LC_RECOVERED : Linecard in slot [dec] with priority [dec] has been recovered from shutdown
Explanation A LC was recovered from a shutdown
Recommended Action If this message recurs, 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.


%CMRP_PFU-6-PWR_MGMT_SINGLE_SUP_NOTICE : NOTICE([dec] of [dec]): System is now running in SINGLE-SUP power budget mode. Insertion of the remote supervisor is not supported in this power mode. System may shutdown if second supervisor is inserted.
Explanation User needs to be notified that single-sup mode is enabled
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PWR_MGMT_SINGLE_SUP_ERROR : ERROR: Remote supervisor has been detected in slot [dec]. System is configured to SINGLE-SUP power mode. Remove remote supervisor IMMEDIATELY.
Explanation User inserted a second supervisor in a single-sup power mode.
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-DCPOWERREDUNDANCY : dc input [chars] failed for pem: [dec]
Explanation The DC input failed for pem module.
Recommended Action the message will be displayed when DC input failed.


%CMRP_PFU-5-DCPOWERINPUT : dc input [chars] recovered for pem: [dec]
Explanation The DC input recovered for pem module.
Recommended Action the message will be displayed when DC input recovered.


%CMRP_PFU-3-PEM_STATUS : WARNING: The power supply module on slot [dec] hits [chars],
Explanation The power supply module are not functioning properly.
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PEM_VOLTAGENOTSUPPORTED : WARNING: Input voltage of power supply module on PS[dec] is not supported. Please use the supported range of either [dec]-[dec] volts for [dec]W or [dec]-[dec] volts for [dec]W
Explanation The input voltage of the power supply module is out of range
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PWR_PROTECTION_MODE : WARNING: Detected low input voltage ([dec]V) on the power supply in slot P[dec], the power budget may not be enough, some cards may be shutdown due to the power budget reduction. Please check the power input.
Explanation Input voltage of power supply is too low.
Recommended Action If this message recurs, 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.


%CMRP_PFU-6-PWR_PROTECTION_RECOVERED : The power supply in slot P[dec] has been recovered from the power protection mode.
Explanation Power supply input are just recovered from an error condition,
Recommended Action If this message recurs, 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.


%CMRP_PFU-3-PWR_PROTECTION_ACTION : Shutdown the card [chars] due to insufficient power budget.
Explanation The total power is not enough, shutdown FRUs for power protection.
Recommended Action If this message recurs, 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.


%CMRP_PFU-6-PWR_UP_FRU : Power up the card [chars] due to power budget change.
Explanation The total power become enough, power FRUs.
Recommended Action If this message recurs, 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.


%CMRP_PFU-6-PFU_BEACON_LED_ON_OFF : [chars] beacon LED for PFU[dec] is TURNED [chars].
Explanation Power Supply or Fan-tray, Beacon LED turned ON/OFF. This is a notification message only.No action is required.
Recommended Action This is a notification message only. No action is required.


%CMRP_PFU-1-PFU_FAN_FAILED : System detected fan tray removal or fan failure, reinsert or service the faulty fan tray to avoid system shutdown due to high temperature.
Explanation Fan tray has been removed or one of the fan failed and the router will shutdown when the temp reaches Critical temperature to protect itself from overheating.
Recommended Action Reinsert a fan tray into the fan tray slot as soon as possible.


COMMON_FIB

%COMMON_FIB-3-NOMEM : Memory allocation failure for [chars] in [chars] CEF [[hex]] ([chars])[chars].
Explanation An attempt to allocate memory has failed. Depending on the criticality of the data to be stored, CEF operation may be impacted.
Recommended Action Verify that the configuration is supported by the memory present in the system. Copy the message exactly as it appears, and report it to your technical support representative.


%COMMON_FIB-4-UNEQUAL : Ratio of unequal path weightings ([chars]) prevents oce [chars] from being used.
Explanation When attempting to setup the load balancing infrastructure for a prefix with unequal path weightings, CEF discovered that the range of weightings caused one or more paths to be excluded from the final set of load balancing paths. Load balancing will continue with the remaining paths.
Recommended Action Reduce the range of weightings to allow all the paths to be used.


%COMMON_FIB-3-ILLEGALARGS : Illegal arguments - [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-ILIST_OP : Manipulating interest list - [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-NOBROKER : [chars] distribution broker not found - distributing [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-BROKER_ENCODE : [chars] broker failed to encode msg type [dec] for slot(s) [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBXDRINV : Invalid XDR format. [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBXDRLEN : Invalid XDR length. Type [dec] ([chars]). XDR/buffer len [dec]/[dec]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBXDRCLIENT : FIB XDR Client error detected, invalid wkid: ([int])
Explanation COMMON_FIB_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.


%COMMON_FIB-4-LCPREFIXINCONST1 : Slot [chars] missing prefix entry for [chars] in FIB table [chars] when looking up [chars] [[chars]]
Explanation A packet arrived on the linecard, but the lookup of the destination IP address failed to find this prefix in the forwarding table. However the prefix is present on the RP. This may be a transient condition.
Recommended Action If the same prefix gives repeated errors check the CEF prefix on the RP and linecard. If necessary, a clear cef linecard <slot> will download a new CEF table to the linecard. You can also try a clear adjacency command to reload host prefixes.


%COMMON_FIB-4-LCPREFIXINCONST2 : Slot [chars] prefix entry for [chars]/[dec] in FIB table [chars] [[chars]] reason: [chars]
Explanation A passive consistency checker discovered a prefix that is present on the RP, but is inconsistent in the forwarding table of the linecard. This may be a transient condition.
Recommended Action If the same prefix gives repeated errors check the CEF prefix on the RP and linecard. If necessary, a clear cef linecard <slot> will download a new CEF table to the linecard. You can also try a clear adjacency command to reload host prefixes.


%COMMON_FIB-4-RPPREFIXINCONST1 : RP prefix for [chars]/[dec] in FIB table [chars] (inconsistent on slot [chars] - [chars]) [[chars]]
Explanation A passive consistency checker discovered a prefix in the forwarding table of the linecard which is inconsistent on the RP. This may be a transient condition.
Recommended Action If the same prefix gives repeated errors check the CEF prefix on the RP and linecard. If necessary, a clear cef linecard <slot> will download a new CEF table to the linecard.


%COMMON_FIB-4-RPPREFIXINCONST2 : RP missing prefix for [IP_address]%m in FIB table [chars] (present in routing table) [[chars]]
Explanation A passive consistency checker discovered a prefix in the routing table which is not present in the CEF forwarding table on the RP. This may be a transient condition.
Recommended Action If the same prefix gives repeated errors check the prefix in CEF and routing table. Try disable/enable CEF if the prefix is missing.


%COMMON_FIB-4-RPPREFIXINCONST3 : RP has prefix [chars]/[dec] in FIB table [chars] (missing in routing table) [[chars]]
Explanation A passive consistency checker discovered a prefix in the CEF forwarding table which is not present in the routing table. This may be a transient condition.
Recommended Action If the same prefix gives repeated errors check the prefix in CEF and routing table. Try disable/enable CEF if the prefix is missing.


%COMMON_FIB-4-HWPREFIXINCONST1 : Hardware on RP missing prefix for [chars]/[dec] in FIB table [chars] (present in RP FIB) [[chars]]
Explanation A passive consistency checker discovered a prefix in the RP FIB table which is not present in the hardware forwarding table on the RP. This may be a transient condition.
Recommended Action If the same prefix gives repeated errors check the prefix in CEF and routing table. Try disable/enable CEF if the prefix is missing.


%COMMON_FIB-4-HWPREFIXINCONST2 : Hardware in slot [chars] missing prefix for [chars]/[dec] in FIB table [chars] (present in LC FIB) [[chars]]
Explanation A passive consistency checker discovered a prefix in the LC FIB table which is not present in the hardware forwarding table on this linecard. This may be a transient condition.
Recommended Action If the same prefix gives repeated errors check the prefix in CEF and routing table. Try disable/enable CEF if the prefix is missing.


%COMMON_FIB-4-HWPREFIXINCONST3 : RP missing prefix for [chars]/[dec] in FIB table [chars] (present in RP hardware) [[chars]]
Explanation A passive consistency checker discovered a prefix in the hardware table which is not present in the FIB forwarding table on the RP. This may be a transient condition.
Recommended Action If the same prefix gives repeated errors check the prefix in CEF and routing table. Try disable/enable CEF if the prefix is missing.


%COMMON_FIB-4-HWPREFIXINCONST4 : Slot [chars] missing prefix for [chars]/[dec] in FIB table [chars] (present in LC hardware) [[chars]]
Explanation A passive consistency checker discovered a prefix in the LC hardware table which is not present in the FIB forwarding table on this linecard. This may be a transient condition.
Recommended Action If the same prefix gives repeated errors check the prefix in CEF and routing table. Try disable/enable CEF if the prefix is missing.


%COMMON_FIB-4-AUTOREPAIR : CEF [chars] database auto-repair executed
Explanation The CEF consistency checkers have detected an inconsistent prefix in one of the CEF forwarding databases. The auto-repair function has been executed to repair the problem. Details of the prefix can be found using the 'show cef table consistency' command.
Recommended Action Copy the message exactly as it appears, together with the output of the 'show cef table consistency' command and report it to your technical support representative,


%COMMON_FIB-3-TABLE : [chars]: [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_GSB : Generic subblock error: [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_GSB2 : Generic subblock error: [chars][chars][chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-6-FIB_GSB_TEST_MSG : Test subblock error: [chars]
Explanation The subblock test command could not be completed successfully
Recommended Action No action is required.


%COMMON_FIB-3-FIB_ATTACHED_EXPORT : Attached export tracking error: [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_FIB_SOURCE : [chars] for [chars] - [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_FIB_SOURCE_NULL_FIBIDB : [chars] NULL fibidb in broadcast sb
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_FIB_SOURCE_IPL_SB : [chars] - [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-6-FIB_RECURSION : [chars] has too many ([int]) levels of recursion during [chars]
Explanation CEF discovered that the routing for a prefix involved excessive many levels of recursion and was forced to terminate an operation on the entry for that prefix. This is likely to be caused by a recursion loop
Recommended Action If the problem persists use show commands show ip route A.B.C.D and show ip cef A.B.C.D <mask> internal or the ipv6 equivalents show ipv6 route X:X:X:X::X and show ipv6 cef X:X:X:X::X/<0-128> internal to display the RIB and CEF information for the prefix in question and check its configuration. If this prefix is in a VRF, please also check show ip cef vrf <VRF> A.B.C.D/mask internal or show ipv6 cef vrf <VRF> X:X:X:X::X/<0-128> internal. If there is still a problem, please contact the technical support center with the output of these commands and show tech.


%COMMON_FIB-4-BADXDRHWSBDECODE : HW subblock decode ([chars] / [dec]) - wrong length read (expected [dec], decoded [dec])
Explanation The given HW subblock is not being processed correctly on the linecard. The error has been corrected, but should be reported in case there are related problems that need to be addressed.
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.


%COMMON_FIB-4-BADXDRSWSBDECODE : SW subblock decode ([chars] / [dec]) - wrong length read (expected [dec], decoded [dec])
Explanation The given SW subblock is not being processed correctly on the linecard. The error has been corrected, but should be reported in case there are related problems that need to be addressed.
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.


%COMMON_FIB-3-SBWITHOUTISSUSUPPORT : [chars] [chars] subblock doesn't support ISSU and can't be used.
Explanation The given SW subblock doesn't support ISSU so may not be processed correctly on the LC. It has not been registered by the CEF component.
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.


%COMMON_FIB-3-ILLEGAL_MSG_TYPE : Cannot find ISSU message type for FIB [chars] ([dec]) [chars]SB [chars] msg
Explanation The given SW subblock is being sent to an ISSU aware endpoint but CEF cannot verify that this message has been negotiated successfully and cannot send it. This is a coding 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.


%COMMON_FIB-4-FIBIDB : No fibidb found for [chars] during [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-4-FIBHWIDB : No fibhwidb for [chars] found during [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-4-FIBXDR_REGISTRATION : Unable to register XDR client ([chars]).
Explanation COMMON_FIB_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.


%COMMON_FIB-3-ASSERT : Assertion '[chars]' failed in [chars] CEF [[hex]]: [chars] ([chars])[chars].
Explanation COMMON_FIB_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.


%COMMON_FIB-3-ASSERT_RL : Assertion '[chars]' failed in [chars] CEF [[hex]]: [chars] ([chars])[chars].
Explanation COMMON_FIB_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.


%COMMON_FIB-4-DISABLING : [chars] CEF is being disabled due to a fatal error.
Explanation COMMON_FIB_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.


%COMMON_FIB-3-DEPENDENCY_WALK : Walk specification [IPV6 address] missing handler for type [dec] dependency
Explanation COMMON_FIB_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.


%COMMON_FIB-3-DEPENDENCY_CHAIN : Missing handler for type [dec] dependency
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBDEPDUMP : [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBPLDEPDUMP : [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBCOVEREDDEPDUMP : [chars] [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-4-BROKERINVMSG : Invalid message: [chars], type [chars], len [dec]
Explanation An invalid message has been received by this broker.
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.


%COMMON_FIB-4-ISSUBUFFERTOOSHORTMSG : Message [chars] for slots [chars] is too large ([dec] bytes, max [dec])
Explanation There is not enough buffer space for ISSU transformations. The message must not proceed any further or a buffer overrun may result.
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.


%COMMON_FIB-4-ISSUENCODEWRONGLEN : Message [chars] for slots [chars] is wrong length ([dec], should be [dec])
Explanation The encoded message length doesn't match the expected length. Message will not be sent.
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.


%COMMON_FIB-3-SBNOTISSUAWARE : Subblock [chars] is not ISSU aware and should be!
Explanation ALL FIB subblocks must be ISSU aware. The subblock code must be rewritten for ISSU. Otherwise this may lead to unpredictable behaviour when running in SSO mode with two different versions of IOS.
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.


%COMMON_FIB-3-MSGISSUAWARE : Message [chars] ([dec]) is ISSU aware so cannot use old FIB API.
Explanation ALL FIB subblocks must be ISSU aware. The subblock code must be rewritten for ISSU. Otherwise this may lead to unpredictable behaviour when running in SSO mode with two different versions of IOS.
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.


%COMMON_FIB-4-SB_STAT_ENCODE : Encoding of [chars] [chars] stats XDR too big
Explanation COMMON_FIB_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.


%COMMON_FIB-4-CHAIN_INSERT_INCONS1 : Attempting to insert [IPV6 address] after [IPV6 address] but it is still pointed at by [IPV6 address]
Explanation COMMON_FIB_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.


%COMMON_FIB-4-CHAIN_INSERT_INCONS2 : Attempting to insert [IPV6 address] after [IPV6 address] but it has prev set to [IPV6 address]
Explanation COMMON_FIB_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.


%COMMON_FIB-4-CHAIN_REMOVE_INCONS1 : Attempting to remove [IPV6 address] but prev [IPV6 address] points at [IPV6 address] instead
Explanation COMMON_FIB_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.


%COMMON_FIB-4-CHAIN_REMOVE_INCONS2 : Attempting to remove [IPV6 address] but it has no prev (next is [IPV6 address])
Explanation COMMON_FIB_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.


%COMMON_FIB-4-CHAIN_REMOVE_INCONS3 : Attempting to remove [IPV6 address] with next [IPV6 address] thinks its prev is [IPV6 address]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-CHAIN_BAD_MAGIC : Bad magic for element [IPV6 address] ([hex] != [hex])
Explanation COMMON_FIB_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.


%COMMON_FIB-3-DQUEUE_BAD_PREV : elem [IPV6 address] type [hex] elem->prev [IPV6 address] elem->prev_type [hex] elem->prev->next [IPV6 address]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-DQUEUE_BAD_NEXT : elem [IPV6 address] type [hex] elem->next [IPV6 address] elem->next_type [hex] elem->next->prev [IPV6 address]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBIDB_DB_MEM : [chars] chunk pool could not be [chars]. Possible memory leak.
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBIDB_DB_INTERNAL : fibidb [chars] if_nb [dec] could not be [chars] db
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBIDB_DB_NULL_FIBIDB : API called with NULL fibidb
Explanation COMMON_FIB_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.


%COMMON_FIB-3-EPOCH : Failed to start [chars] of [chars]entries in table [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-IPMFI_TIMING_PRESENT : IPMFI Timing Tool present in image - performance will be degraded
Explanation COMMON_FIB_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.


%COMMON_FIB-4-FIBMSG : Invalid message received. Type [chars], event/sub-type [dec], length [dec]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-ILLEGAL_TABLEID : Attempt to create [chars] table with illegal tableid [dec] ([chars]:[chars])
Explanation COMMON_FIB_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.


%COMMON_FIB-3-NO_TABLE_NAME : Attempt to clear the name of [chars] table with tableid [dec], previous name [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-2-FIBTABLEILLEGAL : Attempt to used uninitialized CEF data structure.
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBIDBEARLYCALL : Attempt to update fibidb prior to completion of idb initialization.
Explanation COMMON_FIB_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.


%COMMON_FIB-2-IFINDEXBOUNDS : Attempt to use out of bounds interface index: [dec]
Explanation COMMON_FIB_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.


%COMMON_FIB-2-HW_IF_INDEX_ILLEGAL : Attempt to create CEF interface for [chars] with illegal index: [dec]
Explanation COMMON_FIB_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.


%COMMON_FIB-2-IF_NUMBER_ILLEGAL : Attempt to create CEF interface for [chars] with illegal if_number: [dec]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBIDBINCONS1 : An internal software error occurred. [chars] should be first fibidb
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBIDBINCONS2 : An internal software error occurred. [chars] linked to wrong idb [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBHWIDBINCONS : An internal software error occurred. [chars] linked to wrong hwidb [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-4-FIBIDBMISMATCH : Mis-match between idb [chars] (if_number [dec]) and fibidb [chars] (if_number [dec])
Explanation COMMON_FIB_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.


%COMMON_FIB-4-FIBHWIDBMISMATCH : Mis-match between hwidb [chars] (ifindex [dec]) and fibhwidb [chars] (ifindex [dec])
Explanation COMMON_FIB_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.


%COMMON_FIB-4-FIBNULLIDB : Missing idb for fibidb [chars] (if_number [dec]).
Explanation COMMON_FIB_INTERNAL_ERROR
Recommended Action Please check Bug Toolkit BUG_TOOLKIT on the Cisco web-site for existing bugs and upgrade your software accordingly. If you do not find an existing bug, please contact technical support TAC_CASE_OPEN with the contents of the message log and the output of the 'show tech' command.


%COMMON_FIB-4-FIBNULLHWIDB : Missing hwidb for fibhwidb [chars] (ifindex [dec])
Explanation COMMON_FIB_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.


%COMMON_FIB-4-FIBMISSINGHWIDB : No fibhwidb while initializing fibidb for [chars] (if_number [dec])
Explanation COMMON_FIB_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.


%COMMON_FIB-3-HW_API : HW API failure for [chars] CEF [[hex]]: [chars] ([chars])[chars].
Explanation COMMON_FIB_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.


%COMMON_FIB-3-TABLE_CONCURRENT_UPDATE : [chars]: [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBTOPO : Error for topology [dec]: [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBTOPOSTAT : Error pulling topology stats [chars][chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_MPLS_EXT_FIND_OCE : Unable to find MPLS oce for [chars] IP oce
Explanation COMMON_FIB_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.


%COMMON_FIB-3-INVALID_AF : Invalid address family [dec][chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBIDBNONBASETABLE : interface [chars] being set with non-base table: [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-DQUEUE_ACTIVE_COLLECTION : dqueue has an active collection just prior to destruction
Explanation COMMON_FIB_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.


%COMMON_FIB-3-INVALID_ADDR_TYPE : Invalid address type [dec][chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-DQUEUE_NON_EMPTY : dqueue is not empty just prior to destruction
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBHWIDB_NONAME : Missing name for fibhwidb (ifindex [dec])
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBSUBTREECONTEXT : Subtree context unexpected error: app [chars]: [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-NOHWSBDECODE : No [chars] subblock control decode function for [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-NOSWSBDECODE : No [chars] subblock control decode function for [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-NOLABELNOLABEL : Unexpected disposition information for [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-NOPATHFIBIDB : No fibidb for [chars] (ignoring path) during path no [dec] update for [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-4-TOPO_STAT_ID_MGR : Id manager error [chars]. Topology statistics accounting may not show the correct result
Explanation COMMON_FIB_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.


%COMMON_FIB-3-UNHANDLED_UNITS : No handler for units ([chars]) - from slot [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-NAMETOOLONG : FIB[chars]IDB name [chars] error (lengths [dec] ([dec]), short [dec] ([dec]))
Explanation COMMON_FIB_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.


%COMMON_FIB-4-FIB_SB_ADD_FAIL : Attempted add of subblock of type '[chars]' ([dec]) for [chars] failed[chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_LOADBALANCE_MAP : [chars] map [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_LOADBALANCE_MAP_NO_USEABLE_CHOICES : No useable choices [hex] bucket count [int]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_LOADBALANCE_USAGE : Unhandled usage flag [hex]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_PATH_LIST_DB : [chars] path list [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-NO_VALID_PATHS : No valid paths for prefix [chars] in vrf [chars].
Explanation COMMON_FIB_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.


%COMMON_FIB-3-DQUEUE_BAD_ELEM : Unexpected element type [int]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-VRFID_INVALID : Error invalid vrfid [chars][chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-ACL_PBR_NAMETOOLONG : IPV6_SWSB_CTRL name length error, [chars] (acl_in [dec] ([dec]), acl_out [dec] ([dec]), pbr [dec] ([dec]))
Explanation IPv6 in/out ACL and IPv6 PBR name lengths for/from an IPC XDR message are invalid. The names will not be used so as to prevent any buffer overrun errors. There is a possibility that either the XDR message or an internal IPv6 FIB structure is corrupted
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.


%COMMON_FIB-3-BFD_SESS : [chars]:[chars] failed to [chars] BFD session, error [[chars]]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-BFD : [chars][chars][chars][chars][chars][chars][chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-NOSUCHCAPTURE : Error finding capture point.
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIBTABLE : Error for table [dec]: [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-VRFMGR_INVALID : Error invalid [chars] [int]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_NON_IP_ENTRY_INCR : [chars] non-ip entry [hex], path list [chars]
Explanation COMMON_FIB_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.


%COMMON_FIB-3-PATH_EXT_ENCODE : Failed to encode [chars] path extension [chars]
Explanation One or more path extensions could not be encoded for distribution and will not be sent. This indicates an internal code error and may impact CEF operation for prefixes using the affected path extensions.
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.


%COMMON_FIB-3-PATH_INVALID_REPAIR : Primary or repair paths configured by RIB are of invalid type: primary: [chars] repair: [chars]
Explanation Either the primary path or the repair path is not of the correct type, i.e. an attached nexthop, that provides both interface and nexthop
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.


%COMMON_FIB-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.


%COMMON_FIB-3-ISSU_ENUM_ERROR : Enum for [chars] is not ISSU-compliant: [chars]
Explanation The given enumeration is not ISSU-compliant for the reason given. Unpredictable behaviour will result when interoperating with different IOS versions.
Recommended Action This requires a code fix before the image can be shipped or ISSU will be broken.


%COMMON_FIB-3-FIBINVPEXTLEN : [chars] ext, attempt to decode beyond XDR buffer, cp_cur [hex], cp_end [hex], num_ext [dec], curr_ext_idx [dec]
Explanation The path extension decode logic is trying to access memory beyond XDR buffer, which can lead to memory corruption.
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.


%COMMON_FIB-3-PATH_EXT_ISSU_SR_LDP : Dowgrading to a version that doesn't support Segment Routing and LDP on the same path, labels [[dec]|[dec]].
Explanation This indicates there's an issue in ISSU transformation when downgrading to a lower version. Configuration changes might be required to avoid this issue. See recommended action.
Recommended Action Find out the prefix which is using the two outgoing labels as shown in the message with 'show mpls forwarding-table'. Check IGP configuration and disable either LDP or SR on that prefix.


%COMMON_FIB-4-MAX_PATHS_EXCEEDED : Prefix [chars] in vrf [chars] has paths in excess of the maximum. Some may be dropped.
Explanation COMMON_FIB_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.


%COMMON_FIB-3-PATH_EXT_DUPLICATE : Detected identical [chars] path extension [chars] (ext [IPV6 address]) - replacing.
Explanation COMMON_FIB_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.


%COMMON_FIB-3-PATH_EXT_PLIST_CHG_DUP_SHORT : Detected identical short path extension following path list change idx [dec] type [int] [[chars] --> [chars]] conv [int], renum [int], total short [int] (ext list [IPV6 address]).
Explanation COMMON_FIB_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.


%COMMON_FIB-3-FIB_XDR_BUF_OVERFLOW : FIB XDR buffer overflow while encoding [chars] [[chars]]
Explanation COMMON_FIB_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.


COMMON_MFIB

%COMMON_MFIB-3-NOMEM : Memory allocation failure for [chars] in [chars] MFIB [[hex]].
Explanation An attempt to allocate memory has failed. Depending on the criticality of the data to be stored, MFIB operation may be impacted.
Recommended Action Verify that the configuration is supported by the memory present in the system. Copy the message exactly as it appears, and report it to your technical support representative.


%COMMON_MFIB-3-ILLEGALARGS : Illegal arguments - [chars]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-NOBROKER : [chars] distribution broker not found - distributing [chars]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-BROKERINITFAIL : Failed to initialise [chars] RP broker facility
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-BROKER_ENCODE : [chars] broker failed to encode msg type [dec] for slot(s) [chars]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-MFIBXDRINV : Invalid XDR format. [chars]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-MFIBXDRLEN : Invalid XDR length. Type [dec] [chars]. XDR/buffer len [dec]/[dec]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-TABLE : [chars]: [chars]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-MFIB_GSB : Generic subblock error: [chars]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-4-MFIBXDR_REGISTRATION : Unable to register XDR client ([chars]).
Explanation COMMON_MFIB_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.


%COMMON_MFIB-4-MFIBXDR_NOTREG : XDR client ([chars]) should be registered.
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-MFIBXDR_ISSUREGERROR : ISSU client [chars] ([dec]), entity [dec], failed ISSU registration: [chars]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-ASSERT : Assertion '[chars]' failed in [chars] MFIB [[hex]]: [chars] ([chars])[chars].
Explanation COMMON_MFIB_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.


%COMMON_MFIB-4-DISABLING : [chars] MFIB is being disabled due to a fatal error.
Explanation COMMON_MFIB_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.


%COMMON_MFIB-4-BROKERINVMSG : Invalid message: [chars], type [chars], len [dec]
Explanation An invalid message has been received by this broker.
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.


%COMMON_MFIB-3-EPOCH : Failed to [chars] table [chars][chars]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-4-MFIBTABLE : Failed to [chars] table [chars] [chars]
Explanation An MFIB table was found to be missing when attempting to perform a change to it. This may be a transient condition
Recommended Action If the same table gives repeated warnings or generates more serious errors, copy the message exactly as it appears and report it to your technical support representative


%COMMON_MFIB-4-MFIBMSG : Invalid message received. Type [chars], event/sub-type [dec], length [dec]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-ILLEGAL_TABLEID : Attempt to create [chars] table with illegal tableid [dec] ([chars])
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-NO_TABLE_NAME : Attempt to clear the name of [chars] table with tableid [IPV6 address], previous name [chars]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-INVALID_AF : Invalid address family [dec][chars]
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-MFIBISSU_REGISTRATION : Unable to register [chars] ISSU client([int]).
Explanation COMMON_MFIB_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.


%COMMON_MFIB-3-BG_POPULATE : MFIB master background process failed to populate tables for [chars]
Explanation COMMON_MFIB_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.


COMP

%COMP-5-NOBUF : Interface [chars] [chars]
Explanation Interface serial0 compression getbuffer failed, causing Link Access Procedure, Balanced (LAPB) retransmissions.
Recommended Action Configure additional large and big buffers.


%COMP-3-SYNCBAD : Interface [chars] Decompression sync error
Explanation One interface is configured for predictor compression, the other is not.
Recommended Action Configure both interfaces for predictor compression.


%COMP-3-VERSIONBAD : Interface [chars] Compression Version mismatch expected [hex] received [hex]
Explanation One interface is configured for predictor compression, the other is not.
Recommended Action Configure both interfaces for predictor compression.


%COMP-3-SIZEBAD : Interface [chars] Decompression size error
Explanation One interface is configured for predictor compression, the other is not.
Recommended Action Configure both interfaces for predictor compression.


%COMP-3-COMPERR : [chars]: COMPRESS: (stac error!) status: [dec], size in: [dec], size out: [dec]
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%COMP-3-CONFIGBAD : Interface [chars] Compression internal configuration error
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%COMP-3-BADCOMP : Interface [chars] Bad status returned from packet compression operation
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


%COMP-3-SUBBLOCKERR : Interface [chars] compression subblock creation failed.
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.


COMPILED_ACL

%COMPILED_ACL-3-INTERNAL_ERROR : an unexpected internal error occured: [chars]
Explanation An unexpected internal error occurred. This error may result in one or more flows being punted to the RP or in Turbo ACL not functioning.
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BACKPOINTER_WRONG : [chars]: entry at row [int], column [int] in node [int] does not reference row [int] in the node's child
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BACKPOINTER_PROCESSING_OVERFLOWED : [chars]: processing back-pointers in row [int] in node [int] but the list is marked as overflowed
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BACKPOINTER_OVERFLOWED_NOT_EMPTY : [chars]: the back-pointer list for row [int] in node [int] is marked as overflowed but is not empty
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BACKPOINTER_OVERFLOWED_NOT_EMPTY_REFERENCES : [chars]: the back-pointer list for row [int] in node [int] is marked as overflowed but is not empty
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BAD_PROCESS_REFERENCES : [chars]: error while processing references for row [int] in node [int]: [chars]
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-DEFERRED_ENTRY_CONSISTENCY : [chars]: while [chars] in row [int] in node [int], found deferred entry bitmap is [chars] but count is [int]
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-ROW_UPDATE : [chars]: cannot process row queue update for row [int] in node [int]: [chars]
Explanation EXPLANATION_INTERNAL_ERROR EXPLANATION_IMPACT_POSSIBLE_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-ROW_UPDATE_ENQUEUE : [chars]: cannot process row queue update for row [int] in node [int]: enqueue failed ([int]/[int] entries, list is [chars]valid, entry is [chars]enqueued)
Explanation EXPLANATION_INTERNAL_ERROR EXPLANATION_IMPACT_POSSIBLE_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-ROW_THROTTLE : [chars]: unable to re-queue row [int] on row queue for node [int]; node should not have been freed as it was written to only [int] ms ago
Explanation EXPLANATION_INTERNAL_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-2-LIST_CREATE : [chars]: failed to create row queue for node [int], Turbo ACL has been disabled temporarily
Explanation The system encountered an error while initializing a data structure required for the correct operation of Turbo ACL processing. Turbo ACL will be disabled until another recompilation has completed successfully.
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-2-QUEUE_INIT : [chars]: failed to initialize back-pointer list for row [int] in node [int], Turbo ACL has been disabled temporarily
Explanation The system encountered an error while initializing a data structure required for the correct operation of Turbo ACL processing. Turbo ACL will be disabled until another recompilation has completed successfully.
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-5-LIST_INFO : [chars]: failed to set list information function for node [int]'s row queue (ID [int])
Explanation The system encountered an error while initializing a function vector used for debugging purposes. Turbo ACL will continue to function correctly, but the show list ID command will not show Turbo ACL-specific information for the specified list ID number.
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-BAD_ROW_FREE : [chars]: cannot free row [int] in node [int]: [chars]
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION


%COMPILED_ACL-4-ENTRY_COUNT : [chars]: row entry counters not allocated for node [int] while freeing row [int]
Explanation EXPLANATION_INTERNAL_CONSISTENCY_ERROR EXPLANATION_IMPACT_PUNTING
Recommended Action RECOMMENDED_ACTION